All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: xen-devel@lists.xensource.com
Subject: TLB flushing in x86's map_pages_to_xen()
Date: Tue, 15 May 2007 09:20:56 +0200	[thread overview]
Message-ID: <46497B78.76E4.0078.0@novell.com> (raw)

While I realize that the local-flush-only approach attempts to minimize overhead,
I have some difficulty understanding how this can properly deal with the effects
of speculation on remote processors. I believe this will get even worse when
considering cacheability changes, in which case it is not only an immediate TLB
flush that is needed, but also an immediate cache flush.

Thanks for any clarification, Jan

             reply	other threads:[~2007-05-15  7:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15  7:20 Jan Beulich [this message]
2007-05-15  7:45 ` TLB flushing in x86's map_pages_to_xen() Keir Fraser

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=46497B78.76E4.0078.0@novell.com \
    --to=jbeulich@novell.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.