From: David Vrabel <david.vrabel@citrix.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
David Vrabel <david.vrabel@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCHv5 0/2] x86/ept: reduce translation invalidation impact
Date: Fri, 18 Dec 2015 10:12:09 +0000 [thread overview]
Message-ID: <5673DBF9.8030409@citrix.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D15F74E098@SHSMSX101.ccr.corp.intel.com>
On 18/12/15 07:46, Tian, Kevin wrote:
>> From: David Vrabel [mailto:david.vrabel@citrix.com]
>> Sent: Thursday, December 17, 2015 11:17 PM
>>
>> This series improves the performance of EPT by further reducing the
>> impact of the translation invalidations (ept_sync_domain()). By:
>>
>> a) Deferring invalidations until the p2m write lock is released.
>
> This is only for PATCH 2/2 right? No description of PATCH 1/2 in this summary.
Yes. Patch 1/2 is a prerequisite. I think the description makes this
clear.
David
prev parent reply other threads:[~2015-12-18 10:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 15:17 [PATCHv5 0/2] x86/ept: reduce translation invalidation impact David Vrabel
2015-12-17 15:17 ` [PATCHv5 1/2] x86/ept: invalidate guest physical mappings on VMENTER David Vrabel
2015-12-17 15:56 ` Andrew Cooper
2015-12-18 7:53 ` Tian, Kevin
2015-12-18 10:18 ` David Vrabel
2015-12-18 10:24 ` George Dunlap
2015-12-18 10:30 ` David Vrabel
2015-12-18 10:32 ` Jan Beulich
2015-12-18 11:37 ` David Vrabel
2015-12-17 15:17 ` [PATCHv5 2/2] x86/ept: defer the invalidation until the p2m lock is released David Vrabel
2015-12-18 7:46 ` [PATCHv5 0/2] x86/ept: reduce translation invalidation impact Tian, Kevin
2015-12-18 10:12 ` David Vrabel [this message]
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=5673DBF9.8030409@citrix.com \
--to=david.vrabel@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).