2020年5月18日(月) 14:47 Brennan Ashton <bash...@brennanashton.com>: > > On Sun, May 17, 2020, 10:36 PM Takashi Yamamoto > <yamam...@midokura.com.invalid> wrote: > > > hi, > > > > this is just a curious question. > > why do we use the name "intel64" for qemu things? > > i thought it was from qemu, but qemu seems to use x86_64 or amd64. > > i think "amd64" is more commonly used as it's from amd. > > do we want to help intel marketing for some reasons? > > > > I think it's mostly because the initial port was done against Intel > hardware. I believe that there are some dependencies directly on Intel > features as well right now (those could go away). x86_64 is probably most > appropriate since it covers amd64 and em64t (Intel). > > There are also bits identified as QEMU that are more generic that should > probably be moved. > > Personally I would be in favor of just leaving for things to settle on the > port a bit (a few of us have patches in the works) and then see what feels > right. But if someone wants to take it on now I would not be opposed to it, > and would review and test. > > --Brennan
I did it. Because I ported it against a Xeon 2650v4. The original port includes something related to features which is Intel processor only. However, I am still meshing that port up, removing GPL code etc. I have only done the PR of a flat memory version of the port. This guess this one is clean from Intel only features. If anyone do PR to change it to amd64 or x86_64, I won't oppose. Regarding Qemu, I named it because I have only tested on qemu and boches. Qemu is more easy to use and available to everyone. I found it quite difficult to apply the ARM ecosystem idea to x86, which have very different boards. I guess "generic" is a more appropriate name perhaps? -- Yang
