Avi Kivity wrote:
> Jerone Young wrote:
>> Hmm,
>> The problem here is in the case of kvm_create_phys_mem &
>> kvm_create_default_phys_mem, most archs from now on should always be
>> allocating guest memory from userspace (at least I think this
>> correct).
>>
>> Now if this is not the
Jerone Young wrote:
> Hmm,
> The problem here is in the case of kvm_create_phys_mem &
> kvm_create_default_phys_mem, most archs from now on should always be
> allocating guest memory from userspace (at least I think this correct).
>
> Now if this is not the case then really adding an ar
alf Of Jerone Young
> Sent: 2007年11月1日 1:05
> To: kvm-devel@lists.sourceforge.net
> Cc: [EMAIL PROTECTED]
> Subject: [kvm-devel] [PATCH 00 of 27] Refactor libkvm code Phase 1
>
> Kaniciwa!
> I am here to once again bring great honorable patches to refactor
> libk
EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jerone Young
Sent: 2007年11月1日 1:05
To: kvm-devel@lists.sourceforge.net
Cc: [EMAIL PROTECTED]
Subject: [kvm-devel] [PATCH 00 of 27] Refactor libkvm code Phase 1
Kaniciwa!
I am here to once again bring great honorable patches to refactor
libkv
Jerone Young wrote:
> Kaniciwa!
> I am here to once again bring great honorable patches to refactor
> libkvm x86 code. Patches that I sent in the past for this really took
> the wrong approach, and also many variables that I was splitting out actually
> could be shared amongst many architec
Kaniciwa!
I am here to once again bring great honorable patches to refactor
libkvm x86 code. Patches that I sent in the past for this really took
the wrong approach, and also many variables that I was splitting out actually
could be shared amongst many architectures.
This is the fi
