From: Thomas Gleixner <tglx@linutronix.de>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] x86: add executable mapping support to ioremap
Date: Thu, 31 Jan 2008 14:00:34 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.1.00.0801311324270.9204@apollo.tec.linutronix.de> (raw)
In-Reply-To: <1201764967.12950.25.camel@caritas-dev.intel.com>
On Thu, 31 Jan 2008, Huang, Ying wrote:
> This patch makes ioremap() can be used to map pages as executable,
> this is needed by EFI support.
> +extern void __iomem *__ioremap(unsigned long phys_addr, unsigned long size,
> + enum ioremap_mode mode,
> + enum ioremap_xmode xmode);
> +
Why do you want to add a new API?
addr = ioremap(phys_addr, len);
set_memory_x(addr);
should do what you want already. I think Arjan was not very clear in
his reply yesterday.
We tried to avoid the intermingling of ioremap and the page attribute
settings. We just kept the cached/uncached part.
Now thinking about it further, we should probably fully decouple the
mapping and the attribute change and remove the enum argument from
__ioremap and change the implementations of ioremap_cached and
ioremap_uncached to do the attribute setting after the remap.
That way ioremap_chached and ioremap_uncached just would become what
they should be: conveniance functions for the developers.
Thanks,
tglx
next prev parent reply other threads:[~2008-01-31 13:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 7:36 Huang, Ying
2008-01-31 13:00 ` Thomas Gleixner [this message]
2008-01-31 13:22 ` huang ying
2008-01-31 13:27 ` Andi Kleen
2008-01-31 16:30 ` Thomas Gleixner
2008-01-31 16:28 ` Thomas Gleixner
2008-01-31 16:30 ` Andi Kleen
2008-01-31 16:37 ` Thomas Gleixner
2008-01-31 16:44 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.1.00.0801311324270.9204@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=ak@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®