On 03/15/2012 04:55 AM, Avi Kivity wrote:
On 03/14/2012 10:33 PM, Anthony Liguori wrote:
On 03/06/2012 09:50 AM, Avi Kivity wrote:
The kvmvapic code remaps a section of ROM as RAM to allow the guest to
maintain state there. It is careful to align the section size to a page
boundary, to avoid c
On 03/14/2012 10:33 PM, Anthony Liguori wrote:
> On 03/06/2012 09:50 AM, Avi Kivity wrote:
>> The kvmvapic code remaps a section of ROM as RAM to allow the guest to
>> maintain state there. It is careful to align the section size to a page
>> boundary, to avoid creating subpages, but neglects to d
On 03/06/2012 09:50 AM, Avi Kivity wrote:
The kvmvapic code remaps a section of ROM as RAM to allow the guest to
maintain state there. It is careful to align the section size to a page
boundary, to avoid creating subpages, but neglects to do the same for
the start address. These leads to an ass
On 03/06/2012 09:50 AM, Avi Kivity wrote:
The kvmvapic code remaps a section of ROM as RAM to allow the guest to
maintain state there. It is careful to align the section size to a page
boundary, to avoid creating subpages, but neglects to do the same for
the start address. These leads to an ass
On 2012-03-06 16:50, Avi Kivity wrote:
> The kvmvapic code remaps a section of ROM as RAM to allow the guest to
> maintain state there. It is careful to align the section size to a page
> boundary, to avoid creating subpages, but neglects to do the same for
> the start address. These leads to an
The kvmvapic code remaps a section of ROM as RAM to allow the guest to
maintain state there. It is careful to align the section size to a page
boundary, to avoid creating subpages, but neglects to do the same for
the start address. These leads to an assert later on when the memory
core tries to c
