All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>, Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: ioremap_xxx() with EXEC enabled
Date: Wed, 30 Jan 2008 17:32:10 +0800	[thread overview]
Message-ID: <1201685530.17912.11.camel@caritas-dev.intel.com> (raw)

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:

ioremap_cache_exec()
ioremap_uncache_exec()

- Interface scheme 2:

enum ioremap_mode {
	IOR_MODE_UNCACHED,
	IOR_MODE_CACHED,
};

enum ioremap_xmode {
	IOR_XMODE_UNEXEC,
	IOR_XMODE_EXEC,
};

void __iomem *__ioremap(unsigned long phys_addr, unsigned long size,
			enum ioremap_mode mode,
			enum ioremap_xmode xmode);


Which one do you think is better? Or we should use some other interface
or method?

Best Regards,
Huang Ying


             reply	other threads:[~2008-01-30  9:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30  9:32 Huang, Ying [this message]
2008-01-30  9:59 ` ioremap_xxx() with EXEC enabled Andi Kleen
2008-01-30 13:00   ` huang ying
2008-01-30 13:22     ` Andi Kleen
2008-01-30 15:45 ` Arjan van de Ven
2008-01-30 17:30   ` Andi Kleen
2008-01-30 17:44     ` Arjan van de Ven
2008-01-30 18:35       ` 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=1201685530.17912.11.camel@caritas-dev.intel.com \
    --to=ying.huang@intel.com \
    --cc=ak@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.