Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262323AbUK3V2Q (ORCPT ); Tue, 30 Nov 2004 16:28:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262326AbUK3V2Q (ORCPT ); Tue, 30 Nov 2004 16:28:16 -0500 Received: from linux01.gwdg.de ([134.76.13.21]:4774 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S262323AbUK3V2M (ORCPT ); Tue, 30 Nov 2004 16:28:12 -0500 Date: Tue, 30 Nov 2004 22:28:08 +0100 (MET) From: Jan Engelhardt To: "Hanson, Jonathan M" cc: linux-kernel@vger.kernel.org Subject: RE: Walking all the physical memory in an x86 system In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 653 Lines: 17 >[Jon M. Hanson] I can read /dev/mem from a userspace application as root >with no problems and print out what it sees. However, things are not so >simple from a kernel module as I just can't call open() and read() on >/dev/mem because no such functions are exported from the kernel. Is >there a way to read the contents of /dev/mem from a kernel module? You can use filp_open(). Jan Engelhardt -- ENOSPC - 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/