[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090901133110.GO19719@n2100.arm.linux.org.uk>
Date: Tue, 1 Sep 2009 14:31:11 +0100
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: David Xiao <dxiao@...adcom.com>
Cc: Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Steven Walter <stevenrwalter@...il.com>,
Ben Dooks <ben-linux@...ff.org>,
Hugh Dickins <hugh.dickins@...cali.co.uk>,
Robin Holt <holt@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
v4l2_linux <linux-media@...r.kernel.org>,
"linux-arm-kernel@...ts.arm.linux.org.uk"
<linux-arm-kernel@...ts.arm.linux.org.uk>
Subject: Re: How to efficiently handle DMA and cache on ARMv7 ? (was "Is
get_user_pages() enough to prevent pages from being swapped out ?")
On Wed, Aug 26, 2009 at 10:22:11AM -0700, David Xiao wrote:
> Sorry for the confusion, page_address() indeed only returns kernel
> virtual address; and in order to support VIVT cache maintenance for the
> user space mappings, the dma_map_sg/dma_map_page() functions or even the
> struct scatterlist do seem to have to be modified to pass in virtual
> address, I think.
That's the wrong answer. When DMA happens (and therefore these functions
are called) the userspace context could already have been switched away,
which means that any userspace address information is useless.
Adding support to the existing DMA API functions so they can be used for
userspace mapped pages is simply the wrong approach - most users of those
functions are not concerned with userspace mapped pages at all, and adding
that burden onto all those users is clearly sub-optimal.
The right answer? I don't think there is one (see my previous mail.)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists