Avi,
That's why I also attached the mmx-qemu.patch for user space...
Wei
On 3/28/11 2:23 AM, "Avi Kivity" <avi@xxxxxxxxxx> wrote:
> On 03/28/2011 02:53 AM, Wei Xu wrote:
>>>> +++ linux/contents/include/linux/kvm.h 2011-03-21 09:16:39.000000000 -0700
>>>> @@ -152,7 +152,7 @@
>>>> /* KVM_EXIT_MMIO */
>>>> struct {
>>>> __u64 phys_addr;
>>>> - __u8 data[8];
>>>> + __u8 data[16];
>>>> __u32 len;
>>>> __u8 is_write;
>>>> } mmio;
>>>
>>> This breaks the userspace interface. My implementation split the I/O
>>> into two separate 64-bit writes.
>>
>> Wei>>It will not break the user interface -- the "len" tells user space qemu
>> how many bytes need to be copied; and qemu mmio logic can handle more than
>> 64-bit writes.
>
> But the location of the 'len' field changes. You have to recompile your
> userspace so the code is aware of the new location.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
