All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gianluca Guida <gianluca.guida@eu.citrix.com>
To: Keir Fraser <Keir.Fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: INVVPID question.
Date: Tue, 28 Apr 2009 13:49:47 +0100	[thread overview]
Message-ID: <49F6FB6B.5020504@eu.citrix.com> (raw)
In-Reply-To: <C61CBAAB.5C6E%keir.fraser@eu.citrix.com>

Keir Fraser wrote:
> The instruction reference manual explicitly states that it is not guaranteed
> to flush VPID 0 (but also says that it 'might'). Can't be relied on.

Yes, this is why I was asking about current implementation.

I've been recently playing with shadows and separate (guest/host) tlb 
flushing, and from what I've understood this is what is going on.
Since we use it in vmx_flush_guest_tlbs(), we could perhaps find a way, 
in case tlb flushing optimizations are important to fix this (e.g. using 
vpid_sync_vcpu_all() when current is defined and we're sure there are no 
other vpid-tagged entries in the processor tlb).

Gianluca


> 
>  -- Keir
> 
> On 28/04/2009 13:18, "Gianluca Guida" <gianluca.guida@eu.citrix.com> wrote:
> 
>> Hello,
>>
>> I have a simple question for the Intel EPT/VPID experts: do current
>> implementation of invvpid flushes also VPID 0 when 2 is the first
>> argument (as in vpid_sync_all() in Xen)?
>>
>> Thanks in advance,
>> Gianluca
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> 

      reply	other threads:[~2009-04-28 12:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 12:18 INVVPID question Gianluca Guida
2009-04-28 12:52 ` Keir Fraser
2009-04-28 12:49   ` Gianluca Guida [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=49F6FB6B.5020504@eu.citrix.com \
    --to=gianluca.guida@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.