From: Tim Deegan <Tim.Deegan@citrix.com>
To: xen-devel@lists.xensource.com
Cc: Christoph Egger <Christoph.Egger@amd.com>
Subject: [PATCH 0 of 4] RFC: Nested-p2m cleanups and locking changes
Date: Wed, 22 Jun 2011 17:10:26 +0100 [thread overview]
Message-ID: <patchbomb.1308759026@whitby.uk.xensource.com> (raw)
This patch series tidies up a few bits ofthe nested p2m code.
The main thing it does is reorganize the locking so that most of the
changes to nested p2m tables happen only under the p2m lock, and the
nestedp2m lock is only needed to reassign p2m tables to new cr3 values.
Unfortunately I'm having terrible trouble trying to run Xen under Xen
to test these, so this version of the series is only compile-tested.
I'm just posting them for feedback from Christoph on whether this approach
seems reasonable.
Cheers,
Tim.
next reply other threads:[~2011-06-22 16:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 16:10 Tim Deegan [this message]
2011-06-22 16:10 ` [PATCH 1 of 4] Nested p2m: implement "flush" as a first-class action Tim Deegan
2011-06-23 12:50 ` Christoph Egger
2011-06-23 12:56 ` Christoph Egger
2011-06-23 15:04 ` Christoph Egger
2011-06-23 15:21 ` Christoph Egger
2011-06-24 9:07 ` Tim Deegan
2011-06-22 16:10 ` [PATCH 2 of 4] Nested p2m: remove bogus check of CR3 value Tim Deegan
2011-06-22 16:10 ` [PATCH 3 of 4] Nested p2m: clarify logic in p2m_get_nestedp2m() Tim Deegan
2011-06-24 14:25 ` Christoph Egger
2011-06-24 14:37 ` Tim Deegan
2011-06-24 14:53 ` Christoph Egger
2011-06-24 15:05 ` Tim Deegan
2011-06-27 9:46 ` Christoph Egger
2011-06-22 16:10 ` [PATCH 4 of 4] Nested p2m: rework locking around nested-p2m flushes and updates Tim Deegan
2011-06-23 15:08 ` Christoph Egger
2011-06-24 10:45 ` Tim Deegan
2011-06-24 11:08 ` Christoph Egger
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=patchbomb.1308759026@whitby.uk.xensource.com \
--to=tim.deegan@citrix.com \
--cc=Christoph.Egger@amd.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.