- Original Message -
> From: "Peng Hao"
> To: pbonz...@redhat.com, rkrc...@redhat.com
> Cc: k...@vger.kernel.org, linux-kernel@vger.kernel.org, "Peng Hao"
>
> Sent: Saturday, August 12, 2017 2:06:51 PM
> Subject: [RFC PATCH] kvm: x86: reduce
some versions of windows guest access rtc frequently because of
rtc as system tick.guest access rtc like this: write register index
to 0x70, then write or read data from 0x71. writing 0x70 port is
just as index and do nothing else. So we can use coalesced mmio to
handle this scene to reduce VM-EXIT
On 02/08/2017 11:02, peng.h...@zte.com.cn wrote:
>
>> On 02/08/2017 10:45, peng.h...@zte.com.cn wrote:
>> >>On 02/08/2017 17:24, Peng Hao wrote:
>> > coalesced MMIO is async and io port should be sync . I don't need to
>> > coalese io port access.
>
>> Coalesced MMIO access is resolved on the ne
On 02/08/2017 10:45, peng.h...@zte.com.cn wrote:
>>On 02/08/2017 17:24, Peng Hao wrote:
> coalesced MMIO is async and io port should be sync . I don't need to
> coalese io port access.
Coalesced MMIO access is resolved on the next read from a coalesced MMIO
address or the next write to a non-coal
On 02/08/2017 17:24, Peng Hao wrote:
> some versions of windows guest access rtc frequently because of
> rtc as system tick.guest access rtc like this: write register index
> to 0x70, then write or read data from 0x71. writing 0x70 port is
> just as index and do nothing else. So writing 0x70 is
some versions of windows guest access rtc frequently because of
rtc as system tick.guest access rtc like this: write register index
to 0x70, then write or read data from 0x71. writing 0x70 port is
just as index and do nothing else. So writing 0x70 is not necessory
to exit to userspace every tim
6 matches
Mail list logo
