Kwanan nan an saki imel ta hanyar jerin sakonnin Linux Kernel kuma wannan imel ɗin yana da babban maƙasudin sa cire lambar daga aiwatar da ƙaddamarwar sub x x32 (kada a rude shi da x86 IA-32).
Wanne zai ba ka damar amfani da samfurin magance ƙwaƙwalwar 32-bit (matasan x86 da x86_64) akan tsarin x86 64-bit.
Menene ginin x32?
Yana da mahimmanci a ambaci cewa ƙananan ƙananan ƙananan x32 hadedde ne x86_64 ABI, wanda ke ba da damar yin amfani da samfurin magance ƙwaƙwalwar 32-bit mai amfani akan tsarin 64-bit (mai sarrafawa yana aiki a cikin yanayin 64-bit, amma yana amfani da alamun 32-bit da ayyukan lissafi).
ABI X32 damar aikace-aikace suyi cikakken fa'idar ginin x86_64, kamar ƙarin rajista da umarnin sauri, PIC ABI.
A lokaci guda, ABI X32 yana goyan bayan alamun 32-bit na ƙwaƙwalwar ajiya, wanda ke adana ƙwaƙwalwar ajiya, yana ba da gudummawa wajen cika cache na processor, kuma yana da sakamako mai kyau akan saurin saurin aiwatar da lambar.
Iyakancin ABI X32 rashin yuwuwar jagorancin fiye da 4 GB na ƙwaƙwalwar ajiya daga aikace-aikacen.
Taimakon X32 ya kasance ɓangare na Linux Kernel tun lokacin da aka saki 3.4, wanda aka kafa a watan Mayu 2012.
Masu haɓakawa za su yi mahawara ko za su ci gaba da kula da wannan gine-ginen ko a'a
A cewar mai haɓakawa wanda ke ba da shawarar cire fasahar x32 ba a huce shi ba kuma bai sami aikace-aikace a aikace ba a cikin tsarin masana'antu na zamani.
Bayan haka, kumal x32 lambar yana amfani da hanyar rikice-rikice na aiki tare da kiran tsarin, wanda ke haifar da haɗarin katse aikin yau da kullun bayan aiwatar da tsarin aiwatar da kira.
Linus Torvalds ya ce zai yarda a cire x32 idan ba a gabatar da hujjoji ba ko kuma idan ba a gabatar da tsarin da aka yi amfani da subarchitecture x32 ba.
Linus Har ila yau, ya lura cewa amfani da gine-ginen x32 a bayyane yake an iyakance ga gwaji mai matuƙar gwajis, kamar yadda tallafi ga wannan tsarin mulkin yana da alaƙa da babbar matsala wajen kiyaye rarrabawa da yanayin ci gaba.
Wasikun:
Sannun ku.
Ina matukar nazarin ƙaddamar da faci don cire tallafi x32 daga Linux. Ga wasu batutuwa tare da wannan:
- Ba a bayyana gaba ɗaya cewa yana da masu amfani ba. Kamar yadda na sani, ana tallafawa akan Gentoo da Debian
- Hanyar tsarin kira yana da ban mamaki sosai. Yawancin waƙoƙin bazara akan x32 suna shiga ta hanyar * yan asalin su (watau ba COMPAT_SYSCALL_DEFINE) tare da mashigar shiga ba, kuma wannan da gangan ne.
Misali, adjtimex () yana amfani da shigarwar 'yan qasar, ba shigar da abubuwan da suka dace ba, saboda xx tsarin xx yayi daidai da shimfidar x32_86. Amma ƙananan syscalls suna da wuraren shigarwa daban - waɗannan syscalls ɗin da suka fara daga 64.
Waɗannan suna shiga ta wuraren shigar da COMPAT_SYSCALL_DEFINE.
X32 syscalls waɗanda * ba * a cikin zangon 512 sun keta kowane irin kamannin taron kernel syscall.
A cikin syscall handlers, in_compat_syscall () ya dawo gaskiya, amma ba a kira shigar COMPAT_SYSCALL_DEFINE wannan ba mahaukaci bane kuma kuna cikin haɗarin fasa abubuwa lokacin da mutane ke aiwatar da aiwatarwar syscall ɗin su.
Kuma mafi girma duka, babu wanda yayi kokarin waɗannan abubuwan.
A wani lokaci Lokacin gwajin x32, ɗaya daga cikin masu haɓaka Gentoo ya yanke shawarar cewa haɓaka aikin yayin canzawa zuwa ABI x32 ba shi da girma kamar yadda gwajin roba ya nuna Daga masu yin ABI x32:
Ana ganin babban ci gaba ne kawai idan aka kwatanta shi da gine-ginen x86 da ya gabata, amma idan aka kwatanta shi da gine-ginen x86-64 na yanzu, ribar ba zata da amfani ba (Gwajin SPEC ta mahaliccin x32 ya nuna har zuwa kashi 40% na hanzari idan aka kwatanta da na ABI x86_64 na zamani, gwaje-gwaje tare da lambar H.264 ta nuna saurin 15-20%).