>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of
>Izik Eidus
>Sent: 2007年10月29日 19:36
>To: Yang, Sheng
>Cc: kvm-devel@lists.sourceforge.net
>Subject: Re: [kvm-devel] [PATCH] KVM: VMX: Enable memory
>mappedTPR shadow(FlexPriority)
>
>On Mon, 2007-10-29 at 12:55 +0800, Yang, Sheng wrote:
>> >From 34ee5ae67ff5d3f4b8a0b9313dd80980f57705eb Mon Sep 17
>00:00:00 2001
>> From: Sheng Yang <[EMAIL PROTECTED]>
>> Date: Mon, 29 Oct 2007 09:40:42 +0800
>> Subject: [PATCH] KVM: VMX: Enable memory mapped TPR
>shadow(FlexPriority)
>>
>> This patch based on CR8/TPR patch, and enable the TPR
>> shadow(FlexPriority)
>> for 32bit Windows. Since TPR is accessed very frequently by 32bit
>> Windows,
>> especially SMP guest, with FlexPriority enabled, we saw significant
>> performance gain.
>patch look much better, and everything seems to be fine as i
>look at it.
>lets wait avi to review it
>
Ack too :-)
Basically this patch will have same functionality/result with what Avi
did for optimizing Windows. Dynamic patch works on all HWs, but
may crash the guest if guest kernel has integrity check or patch
guard. This one avoid this issue, but require new HWs :-)
I assume all comming processor will have this feature, some existing
processor also has this feature, so now we can have whole bunch of
solution: new HW will use HW features + any modern OSes;
old HWs will use dynamic patching with assumption no patch guard in guest
which is true so far.
thx,eddie
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
