From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH] xen: clarify locking used when pinning a pagetable.
Date: Wed, 20 Aug 2008 12:41:04 +0200 [thread overview]
Message-ID: <20080820104104.GE2816@elte.hu> (raw)
In-Reply-To: <48AB2DF3.1020207@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Add some comments explaining the locking and pinning algorithm when
> using split pte locks. Also implement a minor optimisation of not
> pinning the PTE when not using split pte locks.
applied these commits to tip/x86/xen:
7708ad6: xen: add xen_ prefixes to make tracing with ftrace easier
11ad93e: xen: clarify locking used when pinning a pagetable.
63d3a75: x86/paravirt: add spin_lock_flags lock op
6e83358: xen: clean up domain mode predicates
Thanks,
Ingo
prev parent reply other threads:[~2008-08-20 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 20:32 Jeremy Fitzhardinge
2008-08-20 10:41 ` Ingo Molnar [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=20080820104104.GE2816@elte.hu \
--to=mingo@elte.hu \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
--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
all inboxes | Powered by JetHome®