From: David Vrabel <david.vrabel@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>,
David Vrabel <david.vrabel@citrix.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>,
George Dunlap <george.dunlap@citrix.com>,
Jun Nakajima <jun.nakajima@intel.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCHv3 1/2] x86/ept: invalidate guest physical mappings on VMENTER
Date: Mon, 14 Dec 2015 14:41:43 +0000 [thread overview]
Message-ID: <566ED527.8020007@citrix.com> (raw)
In-Reply-To: <CAFLBxZb=Zpp775pt3g-ZSMig+GsB_QJ7e97-mumzYacxqP1VKA@mail.gmail.com>
On 07/12/15 10:25, George Dunlap wrote:
>
> I took the past tense ("synced") to mean, "These CPUs have been
> brought into sync (or are no longer out of sync)". So they start out
> not-synced, so you initialize the bit to be clear; when an INVEPT is
> executed, they become synced, so you set the bit; and when you change
> the EPT tables, they are no longer synced so you clear the bit.
It didn't work like that though. I have retained the changed name and
meaning.
David
next prev parent reply other threads:[~2015-12-14 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 16:42 [PATCHv3 0/2] x86/ept: reduce translation invalidation impact David Vrabel
2015-12-03 16:42 ` [PATCHv3 1/2] x86/ept: invalidate guest physical mappings on VMENTER David Vrabel
2015-12-04 11:00 ` George Dunlap
2015-12-04 13:39 ` David Vrabel
2015-12-07 10:25 ` George Dunlap
2015-12-14 14:41 ` David Vrabel [this message]
2015-12-16 16:04 ` George Dunlap
2015-12-03 16:42 ` [PATCHv3 2/2] x86/ept: defer the invalidation until the p2m lock is released David Vrabel
2015-12-04 11:51 ` George Dunlap
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=566ED527.8020007@citrix.com \
--to=david.vrabel@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.