Carlo Marcelo Arenas Belon wrote:
>> #ifdef is okay for this. Actually we can probably remove abi 10 support
>> since the F7 kernel now supports the modern ABI (I don't think anybody
>> else uses abi 10, which is pre 2.6.22 when we announced ABI compatibility.
>>
>
> ubuntu feisty uses
Avi Kivity wrote:
> Zhang, Xiantao wrote:
>> Jeremy Katz wrote:
>>
>>> On Sat, 2007-12-01 at 12:10 +0200, Avi Kivity wrote:
>>>
Zhang, Xiantao wrote:
> I think new archs for kvm doesn't need to care about kvm-abi
> case in their code, since current abi is bigger than 10. But
On Sat, Dec 01, 2007 at 12:10:16PM +0200, Avi Kivity wrote:
> Zhang, Xiantao wrote:
> > Hi, Avi
> > I think new archs for kvm doesn't need to care about kvm-abi
> > case in their code, since current abi is bigger than 10. But in current
> > libkvm.c, we can see that many abi-specific code in it
Zhang, Xiantao wrote:
> Jeremy Katz wrote:
>
>> On Sat, 2007-12-01 at 12:10 +0200, Avi Kivity wrote:
>>
>>> Zhang, Xiantao wrote:
>>>
I think new archs for kvm doesn't need to care about kvm-abi
case in their code, since current abi is bigger than 10. But in
current
Jeremy Katz wrote:
> On Sat, 2007-12-01 at 12:10 +0200, Avi Kivity wrote:
>> Zhang, Xiantao wrote:
>>> I think new archs for kvm doesn't need to care about kvm-abi
>>> case in their code, since current abi is bigger than 10. But in
>>> current libkvm.c, we can see that many abi-specific code in
On Sat, 2007-12-01 at 12:10 +0200, Avi Kivity wrote:
> Zhang, Xiantao wrote:
> > I think new archs for kvm doesn't need to care about kvm-abi
> > case in their code, since current abi is bigger than 10. But in current
> > libkvm.c, we can see that many abi-specific code in it. How to handle it
Zhang, Xiantao wrote:
> Hi, Avi
> I think new archs for kvm doesn't need to care about kvm-abi
> case in their code, since current abi is bigger than 10. But in current
> libkvm.c, we can see that many abi-specific code in it. How to handle it
> ? Can we use __x86__ macro to make it sightles
Hi, Avi
I think new archs for kvm doesn't need to care about kvm-abi
case in their code, since current abi is bigger than 10. But in current
libkvm.c, we can see that many abi-specific code in it. How to handle it
? Can we use __x86__ macro to make it sightless for other archs or
other goo
