From: William Lee Irwin III <wli@holomorphy.com>
To: Brice.Goglin@ens-lyon.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: kmap_atomic
Date: Mon, 22 Nov 2004 07:39:48 -0800 [thread overview]
Message-ID: <20041122153948.GF2714@holomorphy.com> (raw)
In-Reply-To: <41A1FDA0.1070204@ens-lyon.fr>
On Mon, Nov 22, 2004 at 03:54:24PM +0100, Brice Goglin wrote:
> I would like to know if I can use kmap_atomic with KM_USER[01] type
> within a non-interrupt context. Looking at comments near kmap_atomic
> declarations on sparc or ppc, it seems that this is discouraged.
> But lots of code (like filesystem stuff) are currently using it
> outside of interrupt context.
> Are there special requirements about KM_USER[01] usage in interrupt
> or non-interrupt contexts ?
> Is it documented somewhere how we can use it ?
> What I want to do is just kmap_atomic, copy and kunmap_atomic.
Those comments are stale. This varies by km_type. A given km_type may
only be used in one context. KM_USER0/KM_USER1 are specifically
dedicated to process context copying. KM_IRQ0/KM_IRQ1 are specifically
devoted to interrupt-context copying.
-- wli
next prev parent reply other threads:[~2004-11-22 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 14:54 kmap_atomic Brice Goglin
2004-11-22 15:39 ` William Lee Irwin III [this message]
2004-11-23 0:03 ` kmap_atomic Andrew Morton
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=20041122153948.GF2714@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Brice.Goglin@ens-lyon.org \
--cc=linux-kernel@vger.kernel.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