xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Tim Deegan <tim@xen.org>
To: xen-devel@lists.xen.org
Cc: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Subject: [PATCH 00 of 11] Use a reader-writer lock for the p2m
Date: Thu, 10 May 2012 15:59:44 +0100	[thread overview]
Message-ID: <patchbomb.1336661984@whitby.uk.xensource.com> (raw)

This is a cleaned-up version of my patch of two weeks ago to make the 
p2m lock into an rwlock, with some updates from Andres folded in.
With these applied, p2m lookups are no longer serialized in the 
common case (where there are few updates).

I hope to check these in next week, before we branch for 4.2.

Signed-off-by: Tim Deegan <tim@xen.org>
Signed-off-by: Andres Lagar-Cavilla <andres@lagarcavilla.org>

             reply	other threads:[~2012-05-10 14:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 14:59 Tim Deegan [this message]
2012-05-10 14:59 ` [PATCH 01 of 11] x86/mm: make p2m lock into an rwlock Tim Deegan
2012-05-10 14:59 ` [PATCH 02 of 11] x86/mm: Introduce get_page_from_gfn() Tim Deegan
2012-05-10 14:59 ` [PATCH 03 of 11] arm: Implement get_page_from_gfn() Tim Deegan
2012-05-10 15:21   ` Ian Campbell
2012-05-10 14:59 ` [PATCH 04 of 11] x86/hvm: Use get_page_from_gfn() instead of get_gfn()/put_gfn Tim Deegan
2012-05-10 14:59 ` [PATCH 05 of 11] x86/mm: " Tim Deegan
2012-05-10 14:59 ` [PATCH 06 of 11] x86: " Tim Deegan
2012-05-10 14:59 ` [PATCH 07 of 11] common: " Tim Deegan
2012-05-10 14:59 ` [PATCH 08 of 11] grant-tables: " Tim Deegan
2012-05-10 14:59 ` [PATCH 09 of 11] x86/hvm: use unlocked p2m lookups in hvmemul_rep_movs() Tim Deegan
2012-05-10 14:59 ` [PATCH 10 of 11] x86/hvm/svm: used unlocked p2m lookups in trace and error paths Tim Deegan
2012-05-10 14:59 ` [PATCH 11 of 11] x86/p2m, arm/p2m: remove get_gfn_untyped() Tim Deegan
2012-05-10 15:24   ` Ian Campbell
2012-05-16 13:53 ` [PATCH 00 of 11] Use a reader-writer lock for the p2m Andres Lagar-Cavilla

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.1336661984@whitby.uk.xensource.com \
    --to=tim@xen.org \
    --cc=andres@lagarcavilla.org \
    --cc=xen-devel@lists.xen.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).