From: David Vrabel <david.vrabel@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xenproject.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Kevin Tian <kevin.tian@intel.com>, Tim Deegan <tim@xen.org>,
Jan Beulich <jbeulich@suse.com>,
Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [PATCHv4 1/2] x86/ept: invalidate guest physical mappings on VMENTER
Date: Mon, 14 Dec 2015 15:00:33 +0000 [thread overview]
Message-ID: <566ED991.9030906@citrix.com> (raw)
In-Reply-To: <566ED7CB.4090009@citrix.com>
On 14/12/15 14:52, Andrew Cooper wrote:
> On 14/12/15 14:39, David Vrabel wrote:
>> diff --git a/xen/arch/x86/mm/p2m-ept.c b/xen/arch/x86/mm/p2m-ept.c
>> index eef0372..6e0cf89 100644
>> --- a/xen/arch/x86/mm/p2m-ept.c
>> +++ b/xen/arch/x86/mm/p2m-ept.c
[...]
>> + on_selected_cpus(d->domain_dirty_cpumask,
>> __ept_sync_domain, p2m, 1);
>
> You can drop __ept_sync_domain() entirely by using
> smp_send_event_check_mask() instead, which is a no-op IPI (and slightly
> less overhead while holding the IPI lock).
We need to wait until the IPI has been handled on the remote PCPUs since
we may immediately free a page table page. If a VCPU was still running
it may use paging-structure-cache entries referring to that freed page.
>> - cpumask_var_t synced_mask;
>> + cpumask_var_t invalidate;
>
> Could you include a small comment here to describe the behaviour? Perhaps:
>
> /* Whether an INVEPT should be issued on VMENTER? */
Good point.
David
next prev parent reply other threads:[~2015-12-14 15:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 14:39 [PATCHv4 0/2] x86/ept: reduce translation invalidation impact David Vrabel
2015-12-14 14:39 ` [PATCHv4 1/2] x86/ept: invalidate guest physical mappings on VMENTER David Vrabel
2015-12-14 14:52 ` Andrew Cooper
2015-12-14 15:00 ` David Vrabel [this message]
2015-12-14 15:09 ` Andrew Cooper
2015-12-14 15:39 ` George Dunlap
2015-12-15 15:59 ` George Dunlap
2015-12-14 14:39 ` [PATCHv4 2/2] x86/ept: defer the invalidation until the p2m lock is released David Vrabel
2015-12-15 16:00 ` George Dunlap
2015-12-16 17:55 ` David Vrabel
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=566ED991.9030906@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=tim@xen.org \
--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).