Date: Tue, 16 Feb 2010 09:41:10 +0100
From: Andi Kleen <andi@firstfloor.org>
To: Nameer Yarkon <nameer.yarkon@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
       Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
       Andi Kleen <andi@firstfloor.org>, Robert Hancock <hancockrwd@gmail.com>,
       "Anton D. Kachalov" <mouse@mayc.ru>, linux-kernel@vger.kernel.org
Subject: Re: Reading /dev/mem by dd
Message-ID: <20100216084110.GK21783@one.firstfloor.org>
References: <bec9a5871002160035v63cce8ck9ecb9252b2f162a6@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <bec9a5871002160035v63cce8ck9ecb9252b2f162a6@mail.gmail.com>
User-Agent: Mutt/1.4.2.2i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1204
Lines: 32

On Tue, Feb 16, 2010 at 10:35:40AM +0200, Nameer Yarkon wrote:
> On Thu, Nov 12, 2009 at 8:13 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> >> Is that the only valid use of /dev/mem, or even its main use?
> >
> > These days it is the primary use. Things like X11 were historically
> > probably the biggest user of it, and things like LRMI sometimes need that
> > sort of stuff.
> 
> how does X11 get now direct access to the physical memory (instead of
> /dev/mem) ?

The classic X server doesn't use main memory, typically just mapped
graphic card resources
(if you don't count BIOS tables and memory accessed by the video bios
running in emulation, but that is typically excluded by the check)  

In fact it can't because it doesn't know the physical
addresses of its process memory.

Modern X does it through kernel modules (DRM, GEM etc.)

One reason it's needed to do it this way is IOMMUs.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.
--
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/