xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Tim Deegan <tim@xen.org>
To: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Cc: george.dunlap@eu.citrix.com, andres@gridcentric.ca,
	xen-devel@lists.xensource.com, keir.xen@gmail.com,
	adin@gridcentric.ca
Subject: Re: [PATCH 0 of 7] Synchronized p2m lookups v2
Date: Fri, 10 Feb 2012 16:10:23 +0000	[thread overview]
Message-ID: <20120210161023.GE32107@ocelot.phlegethon.org> (raw)
In-Reply-To: <patchbomb.1328766345@xdev.gridcentric.ca>

At 00:45 -0500 on 09 Feb (1328748345), Andres Lagar-Cavilla wrote:
> Up until now, p2m lookups (get_gfn*) in the x86 architecture were not
> synchronized against concurrent updates. With the addition of sharing and
> paging subsystems that can dynamically modify the p2m, the need for
> synchronized lookups becomes more pressing.
> 
> Without synchronized lookups, we've encountered host crashes triggered by race
> conditions, particularly when exercising the sharing subsystem.
> 
> In this patch series we make p2m lookups fully synchronized. We still use a
> single per-domain p2m lock (profiling work tbd may or may not indicate the need
> for fine-grained locking).
> 
> We only enforce locking of p2m queries for hap-assisted domains. These are the
> domains (in the case of EPT) that can exercise the paging and sharing
> subsystems and thus most in need of synchronized lookups.
> 
> While the code *should* work for domains relying on shadow paging, it has not
> been tested, hence we do not enable this at the moment.
> 
> Finally, the locking discipline in the PoD subsystem has been updated, since
> PoD relied on some assumptions about the way the p2m lock is used.
> 
> Signed-off-by: Andres Lagar-Cavilla <andres@lagarcavilla.org>
> Signed-off-by: Adin Scannell <adin@scannell.ca>

Applied, thanks.

Tim.

      parent reply	other threads:[~2012-02-10 16:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09  5:45 [PATCH 0 of 7] Synchronized p2m lookups v2 Andres Lagar-Cavilla
2012-02-09  5:45 ` [PATCH 1 of 7] Make p2m lookups fully synchronized wrt modifications Andres Lagar-Cavilla
2012-02-10 15:33   ` Tim Deegan
2012-02-09  5:45 ` [PATCH 2 of 7] Clean up locking now that p2m lockups are fully synchronized Andres Lagar-Cavilla
2012-02-09  5:45 ` [PATCH 3 of 7] Rework locking in the PoD layer Andres Lagar-Cavilla
2012-02-09 12:07   ` George Dunlap
2012-02-09 14:45     ` Andres Lagar-Cavilla
2012-02-10 15:36       ` Tim Deegan
2012-02-10 15:43         ` Tim Deegan
2012-02-10 15:47           ` Andres Lagar-Cavilla
2012-02-10 15:59       ` George Dunlap
2012-02-09  5:45 ` [PATCH 4 of 7] Re-order calls to put_gfn() around wait queue invocations Andres Lagar-Cavilla
2012-02-09  5:45 ` [PATCH 5 of 7] x86/mm: Revert changeset 24582:f6c33cfe7333 Andres Lagar-Cavilla
2012-02-09  5:45 ` [PATCH 6 of 7] x86/mm: Refactor possibly deadlocking get_gfn calls Andres Lagar-Cavilla
2012-02-09  5:45 ` [PATCH 7 of 7] x86/mm: When removing/adding a page from/to the physmap, keep in mind it could be shared Andres Lagar-Cavilla
2012-02-10 15:38   ` Tim Deegan
2012-02-10 16:10 ` Tim Deegan [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=20120210161023.GE32107@ocelot.phlegethon.org \
    --to=tim@xen.org \
    --cc=adin@gridcentric.ca \
    --cc=andres@gridcentric.ca \
    --cc=andres@lagarcavilla.org \
    --cc=george.dunlap@eu.citrix.com \
    --cc=keir.xen@gmail.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 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).