On Tue, Sep 23, 2008 at 10:31:30AM +0300, Avi Kivity wrote:
> Glauber Costa wrote:
>> On Sat, Sep 20, 2008 at 11:38:22AM -0700, Avi Kivity wrote:
>>
>>> Glauber Costa wrote:
>>>
By analysing phys_offset, we know whether a region is an mmio region
or not. If it is, register it as s
Glauber Costa wrote:
On Sat, Sep 20, 2008 at 11:38:22AM -0700, Avi Kivity wrote:
Glauber Costa wrote:
By analysing phys_offset, we know whether a region is an mmio region
or not. If it is, register it as so. We don't reuse the same slot
infrastructure already existant, because there is
On Sat, Sep 20, 2008 at 11:38:22AM -0700, Avi Kivity wrote:
> Glauber Costa wrote:
>> By analysing phys_offset, we know whether a region is an mmio region
>> or not. If it is, register it as so. We don't reuse the same slot
>> infrastructure already existant, because there is a relationship between
Glauber Costa wrote:
By analysing phys_offset, we know whether a region is an mmio region
or not. If it is, register it as so. We don't reuse the same slot
infrastructure already existant, because there is a relationship between
the slot number for kvm the kernel module, and the index in the slot
By analysing phys_offset, we know whether a region is an mmio region
or not. If it is, register it as so. We don't reuse the same slot
infrastructure already existant, because there is a relationship between
the slot number for kvm the kernel module, and the index in the slots vector
for libkvm. Ho
