public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Roger Larsson <roger.larsson@norran.net>,
	linux-kernel@vger.kernel.org, nigel@nrg.org
Subject: Re: [SMP lock BUG?] Re: Feedback on preemptible kernel patch
Date: 08 Sep 2001 23:44:27 -0400	[thread overview]
Message-ID: <1000007070.836.14.camel@phantasy> (raw)
In-Reply-To: <000901c138bb$8e151270$010411ac@local>
In-Reply-To: <000901c138bb$8e151270$010411ac@local>

On Sat, 2001-09-08 at 19:11, Manfred Spraul wrote:
> No.
> It seems to be a missing ctx_sw_off() in highmem.h:
> kmap_atomic uses a per-cpu variable, thus ctx_sw_off() is needed in
> kmap_atomic, and ctx_sw_on() in kunmap_atomic().

in my tree, kmap_atomic and kunmap_atomic are just defined to
kmap/kunmap.  are you suggesting something like this?

#define kmap_atomic(page,idx)	ctx_sw_off(); kmap(page);
#define kunmap_atomic(page,idx)	ctx_sw_on(); kunmap(page);

-- 
Robert M. Love
rml at ufl.edu
rml at tech9.net


  reply	other threads:[~2001-09-09  3:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-08 23:11 [SMP lock BUG?] Re: Feedback on preemptible kernel patch Manfred Spraul
2001-09-09  3:44 ` Robert Love [this message]
2001-09-09  7:38   ` Manfred Spraul
     [not found]   ` <001a01c1390262c7f30/mnt/sendme10411ac@local>
2001-09-14  9:15     ` Pavel Machek
2001-09-17 22:40       ` Manfred Spraul
2001-09-18  0:19         ` Robert Love
2001-09-17 22:41       ` Robert Love
  -- strict thread matches above, loose matches on Subject: below --
2001-09-08 17:33 Arjan Filius
2001-09-08 20:58 ` [SMP lock BUG?] " Roger Larsson
2001-09-08 22:18   ` Arjan Filius
2001-09-09 14:55   ` george anzinger
2001-09-09 22:25     ` Arjan Filius

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=1000007070.836.14.camel@phantasy \
    --to=rml@tech9.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=nigel@nrg.org \
    --cc=roger.larsson@norran.net \
    /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