Date: Mon, 22 Nov 2004 07:39:48 -0800
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
Message-ID: <20041122153948.GF2714@holomorphy.com>
References: <41A1FDA0.1070204@ens-lyon.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <41A1FDA0.1070204@ens-lyon.fr>
Organization: The Domain of Holomorphy
User-Agent: Mutt/1.5.6+20040722i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1079
Lines: 23

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/