From: Dave Jones <davej@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, "Paul E. McKenney" <paulmck@us.ibm.com>
Subject: Re: [DOCUMENTATION] Revised Unreliable Kernel Locking Guide
Date: Fri, 12 Dec 2003 15:44:01 +0000 [thread overview]
Message-ID: <20031212154401.GA10584@redhat.com> (raw)
In-Reply-To: <20031212052812.E80972C085@lists.samba.org>
On Fri, Dec 12, 2003 at 04:24:18PM +1100, Rusty Russell wrote:
> OK, I've put the html version up for your reading pleasure: the diff
> is quite extensive and hard to read.
>
> http://www.kernel.org/pub/linux/kernel/people/rusty/kernel-locking/
>
> Feedback welcome,
Hi Rusty,
Might be worth mentioning in the Per-CPU data section that code doing
operations on CPU registers (MSRs and the like) needs to be protected
by an explicit preempt_disable() / preempt_enable() pair if it's doing
operations that it expects to run on a specific CPU.
For examples, see arch/i386/kernel/msr.c & cpuid.c
Dave
next prev parent reply other threads:[~2003-12-12 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 5:24 [DOCUMENTATION] Revised Unreliable Kernel Locking Guide Rusty Russell
2003-12-12 15:44 ` Dave Jones [this message]
2003-12-12 16:25 ` Keith Owens
2003-12-12 18:25 ` Dave Jones
2003-12-13 0:28 ` Keith Owens
2003-12-12 21:05 ` Rob Love
2003-12-15 2:28 ` Rusty Russell
2003-12-12 19:35 ` Paul E. McKenney
2003-12-13 3:16 ` Zwane Mwaikambo
2003-12-15 5:17 ` Rusty Russell
2003-12-15 5:17 ` Rusty Russell
2003-12-15 22:22 ` Paul E. McKenney
2003-12-16 6:32 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2003-12-13 3:15 Manfred Spraul
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=20031212154401.GA10584@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.com \
--cc=rusty@rustcorp.com.au \
/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