From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 20 18:23:39 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72B7116A41C for ; Mon, 20 Jun 2005 18:23:39 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18F3C43D48 for ; Mon, 20 Jun 2005 18:23:39 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from [10.50.41.231] (Not Verified[216.133.140.1]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Mon, 20 Jun 2005 14:37:04 -0400 From: John Baldwin To: freebsd-hackers@freebsd.org, Aziz Kezzou Date: Mon, 20 Jun 2005 10:37:42 -0400 User-Agent: KMail/1.8 References: <37273927050614012154fdb80b@mail.gmail.com> <20050614120706.GA539@pm514-9.comsys.ntu-kpi.kiev.ua> <3727392705061919494ea7e0ad@mail.gmail.com> In-Reply-To: <3727392705061919494ea7e0ad@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506201037.43599.jhb@FreeBSD.org> Cc: Andrey Simonenko Subject: Re: FreeBSD Memory Management questions ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jun 2005 18:23:39 -0000 On Sunday 19 June 2005 10:49 pm, Aziz Kezzou wrote: > > On Tue, Jun 14, 2005 at 04:21:41AM -0400, Aziz Kezzou wrote: > > > 1 - Right now to access the memory address space of a user process > > > from kernel mode, I only have to set, on x86 systems, the register CR3 > > > to the right value. How can I do that on other architectures ? is > > > there an architecture-independant way of doing that ? > > > > Addition to the previous answer. It is also possible to temporally > > map several pages of user memory into the kernel address space. > > Check pmap_qenter(9) and see physio -> vmapbuf, for example, how to > > use it. Another method, it is possible to COW a single user page and > > then use it in the kernel, but with this method an user process will > > not see any modification in this page made by the kernel and vice > > versa. Check socow_setup -> vm_page_cowsetup, for example, how to > > use it. > > Very interesting ! > > Right now I am using the fact that the kernel address space is maped > on i386 machines into the user address space. So when I am executing a > system call I can access kernel memory. > I am wondering if there is an architecture-independant way of doing > that ? (Notice that I need not only read kernel memory but also free > it. e.g, mbufs ) or at least could you tell me if that's possible on > other architectures ? Are you modifying kernel memory from userland or are you trying to access user memory from kernel code? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org