virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Chris Wright <chrisw@sous-sol.org>,
	Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: pv_ops smp support
Date: Thu, 19 Oct 2006 21:48:27 -0700	[thread overview]
Message-ID: <4538551B.9080009@vmware.com> (raw)
In-Reply-To: <45384BAA.5070303@goop.org>

Jeremy Fitzhardinge wrote:
>
>> I think you might want to optimize this a bit more, however, since in 
>> some cases you will issue implicit shootdown IPIs during a pte update 
>> hypercall.
>
> Not that I've seen, at least none that doesn't also exist in baseline.

But if Xen uses direct page tables, the update to a page table through a 
hypercall can cause other CPUs with that direct page table loaded to 
require an invalidation.  <Pauses>.  Never mind, I see that you don't 
require an immediate invalidation.  Instead, you use page type 
enforcement to guarantee that page remappings can not be used to subvert 
hypervisor protection, and would either disallow or issue TLB 
invalidations on page type changes from PT to writable pages.  In that 
case, the guest must use TLB shootdown to guarantee correctness, but no 
extra TLB shootdowns are required to guarantee hypervisor security, as I 
had feared.

>
>> This seems much cleaner than designing the shootdown semantic 
>> directly into such PTE updates, which is I believe what some of the 
>> older Xen patches did, although I could have misread them.
>
> I was starting on SMP with the idea that it would be relatively 
> isolated and simple, but it seems I should probably do the MMU stuff 
> first to see what impact it has on SMP.

I think I was imagining some complications which really don't exist, but 
it certainly doesn't hurt to consider the Xen MMU interfaces as you iron 
out the SMP issues.

So perhaps SMP will be more straightforward than I expected.

Zach

      reply	other threads:[~2006-10-20  4:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19 23:09 pv_ops smp support Jeremy Fitzhardinge
2006-10-19 23:34 ` Zachary Amsden
2006-10-19 23:48   ` Jeremy Fitzhardinge
2006-10-20  0:02     ` Zachary Amsden
2006-10-20  4:08       ` Jeremy Fitzhardinge
2006-10-20  4:48         ` Zachary Amsden [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=4538551B.9080009@vmware.com \
    --to=zach@vmware.com \
    --cc=chrisw@sous-sol.org \
    --cc=jeremy@goop.org \
    --cc=virtualization@lists.osdl.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).