From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Dong, Eddie" <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] KVM: VMX: Enable memory mappedTPR shadow(FlexPriority)
Date: Tue, 30 Oct 2007 13:46:41 +0200 [thread overview]
Message-ID: <472719A1.6070709@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A024CEC5E-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]
Dong, Eddie wrote:
>>
>>> From: Sheng Yang <sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
>>> 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.
>
Yes. FlexPriority will be both faster and safer for those who have it
than my hack.
It may turn out that patching can improve performance even with
FlexPriority: we can patch the APIC EOI write to look if any interrupts
are pending, and only exit if the EOI will result in a new interrupt
being injected. But it is very possible that this will not be necessary
if we can achieve good interrupt mitigation with virtio.
--
Any sufficiently difficult bug is indistinguishable from a feature.
[-- Attachment #2: Type: text/plain, Size: 314 bytes --]
-------------------------------------------------------------------------
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/
[-- Attachment #3: Type: text/plain, Size: 186 bytes --]
_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel
next prev parent reply other threads:[~2007-10-30 11:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 4:55 [PATCH] KVM: VMX: Enable memory mapped TPR shadow(FlexPriority) Yang, Sheng
[not found] ` <DB3BD37E3533EE46BED2FBA80995557FA15F3E-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-29 11:35 ` Izik Eidus
[not found] ` <1193657732.4484.17.camel-siXIhNkUrCXckEVJwWePHtCfPAL7FxvL@public.gmane.org>
2007-10-30 11:40 ` [PATCH] KVM: VMX: Enable memory mappedTPR shadow(FlexPriority) Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A024CEC5E-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-30 11:46 ` Avi Kivity [this message]
[not found] ` <472719A1.6070709-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-30 15:07 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A024CECAA-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-31 0:47 ` Avi Kivity
[not found] ` <4727D09E.2040008-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-31 13:08 ` Dor Laor
2007-10-31 14:26 ` Dong, Eddie
2007-10-30 3:25 ` [PATCH] KVM: VMX: Enable memory mapped TPR shadow(FlexPriority) Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=472719A1.6070709@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox