From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Zachary Amsden <zach@vmware.com>
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:08:10 -0700 [thread overview]
Message-ID: <45384BAA.5070303@goop.org> (raw)
In-Reply-To: <4538121E.7090607@vmware.com>
Zachary Amsden wrote:
> No, I don't mean the Linux PDA - how do you access the Xen PDA? Or
> have they conjoined somehow?
You could put it that way I guess. There's a generic Linux PDA; a
paravirt patch adds a union for pv use, and a Xen patch adds a
Xen-specific element to that union. That's how it has been from the
start, so there wasn't really anything to conjoin (there was never a Xen
PDA per se).
> So your invalidate "IPI" is actually a hypercall, and you can use the
> existing flush_tlb interface for the most part. You just need a
> paravirt-op then for the IPI itself, which takes a CPU mask - and this
> seems to match nicely onto your hypercall.
Yep. There are calls for flushing the whole tlb, and for just a page;
both take CPU masks.
> 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.
> 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.
J
next prev parent reply other threads:[~2006-10-20 4:08 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 [this message]
2006-10-20 4:48 ` Zachary Amsden
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=45384BAA.5070303@goop.org \
--to=jeremy@goop.org \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.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.