[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080130094427.720fdae7@laptopd505.fenrus.org>
Date: Wed, 30 Jan 2008 09:44:27 -0800
From: Arjan van de Ven <arjan@...radead.org>
To: Andi Kleen <ak@...e.de>
Cc: "Huang, Ying" <ying.huang@...el.com>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>, Andi Kleen <ak@...e.de>,
linux-kernel@...r.kernel.org
Subject: Re: ioremap_xxx() with EXEC enabled
On Wed, 30 Jan 2008 18:30:48 +0100
Andi Kleen <ak@...e.de> wrote:
> On Wed, Jan 30, 2008 at 07:45:40AM -0800, Arjan van de Ven wrote:
> > On Wed, 30 Jan 2008 17:32:10 +0800
> > "Huang, Ying" <ying.huang@...el.com> wrote:
> >
> > > Hi,
> > >
> > > On i386, EFI may need to map EFI runtime code area as EXEC enabled
> > > with ioremap(). But, I found that the memory are mapped as EXEC
> > > disabled when mapped with ioremap() now. I think we may need a
> > > method to map memory area as EXEC enabled with ioremap_xxx().
> > > Some possible interface schemes for mapping as EXEC enabled are
> > > as follow:
> > >
> > > - Interface scheme 1:
> >
> > scheme 3:
> >
> > set_memory_x(... )
>
> On i386 EFI is unlikely to be in the direct mapping ...
1) 32 bit EFI is totally irrelevant.
2) set_memory_ and set_pages_ API is not restricted to direct mapping. That's why they take a virtual address / struct page
>
> -Andi
>
--
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists