Re: [PATCH 00/10] Enhance /dev/mem to allow read/write of arbitrary physical addresses
From: Petr Tesarik
Date: Fri Jun 17 2011 - 05:55:43 EST
Dne PÃ 17. Äervna 2011 11:30:32 Ingo Molnar napsal(a):
> * Petr Tesarik <ptesarik@xxxxxxx> wrote:
> > This patch series enhances /dev/mem, so that read and write is
> > possible at any address. The patchset includes actual
> > implementation for x86.
> This series lacks a description of why this is desired.
> My strong opinion is that it's not desired at all: /dev/mem never
> worked beyond 4G addresses so by today it has become largely obsolete
> and is on the way out really.
> I'm aware of these current /dev/mem uses:
> - Xorg maps below 4G non-RAM addresses and the video BIOS
> - It used to have some debugging role but these days kexec and kgdb
> has largely taken over that role - partly due to the 4G limit.
It is still used as a "memory source" by Dave Anderson's crash utility for
live examination of a running system. Redhat has "overcome" the /dev/mem
deficiencies by writing an out-of-tree re-implementation of /dev/mem, which
uses /dev/crash instead. As it is an "unnecessary duplication of an existing
driver", this method was rejected by the project manager here at SUSE.
The suggested alternative was to enhance (or fix) the existing driver. Without
this patch series there is no way to access high memory. In conjunction with
CONFIG_HIGHPTE, it makes the crash utility near to useless on anything with
high memory, because crash can no longer translate virtual to physical
> - there's some really horrible out-of-tree drivers that do mmap()s
> via /dev/mem, those should be fixed if they want to move beyond
> 4G: their char device should be mmap()able.
> - all distro kernel's i'm aware of use CONFIG_STRICT_DEVMEM=y, which
> restricts /dev/mem to non-RAM pages of physical memory.
> [ With the sad inclusion of the first 1MB, which Xorg needs. ]
Well, there's one (quite unimportant) distro that doesn't compile with
CONFIG_STRICT_DEVMEM: openSUSE (and SLES, consequently).
> Are you aware of any legitimate usecases?
See above - live crash sessions on i586 (or any other arch that has high
> Frankly, i dont think we ever *want* to 'fix' /dev/mem to support
> addresses beyond 4G and grow messy userspace (and kernelspace) that
> somehow relies on that. Thank goodness that we never supported it ...
Let me put it differently. Do you think that an out-of-tree duplicated effort
(the crash.ko module) offered by Redhat is somehow superior to enhancing the
in-tree /dev/mem driver?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/