Date: Tue, 2 Mar 2010 12:04:26 +0100 From: Giovanni Trematerra <giovanni.trematerra@gmail.com> To: Alexander Eichner <alexeichi@yahoo.de> Cc: freebsd-hackers@freebsd.org Subject: Re: Allocating physical memory without a kernel mapping Message-ID: <4e6cba831003020304u2a2dc8ceobb594ebe58744ef5@mail.gmail.com> In-Reply-To: <1267518879.2794.14.camel@Prometheus> References: <317657.30145.qm@web27603.mail.ukl.yahoo.com> <4e6cba831003010619j560f5b92n4c63ab2520cff7db@mail.gmail.com> <1267518879.2794.14.camel@Prometheus>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 2, 2010 at 9:34 AM, Alexander Eichner <alexeichi@yahoo.de> wrote: > Giovanni Trematerra wrote: >> On Mon, Mar 1, 2010 at 10:59 AM, Alexander Eichner <alexeichi@yahoo.de> wrote: >> > Hi, >> > > > Thanks for your help but I don't see how that patch could help with my > problem. rtR0MemObjNativeAllocPage allocates pages with a kernel > mapping but the problem appears when using rtR0MemObjNativeAllocPhysNC > + rtR0MemObjNativeMapUser and freeing the pages later. > rtR0MemObjNativeAllocPage is used if I use the old allocation mode which > does not use rtR0MemObjNativeAllocPhysNC and this works fine here. > The double wiring problem should also be solved with the latest source. Sorry, the patch was intended *only* as alternative way to resolve double wired paging issue. I don't know if the patch is correct though. Maybe you can attach a textdump of your panic(or at least a bt), that might be useful to understand the problem. Thank you. -- Gianni
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e6cba831003020304u2a2dc8ceobb594ebe58744ef5>