From: "huang ying" <huang.ying.caritas@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Huang, Ying" <ying.huang@intel.com>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Thomas Gleixner" <tglx@linutronix.de>, "Andi Kleen" <ak@suse.de>,
linux-kernel@vger.kernel.org,
"Arjan van de Ven" <arjan@infradead.org>
Subject: Re: [PATCH 5/5] x86: EFI memory mapping changes according to changes to ioremap and c_p_a
Date: Thu, 31 Jan 2008 21:30:19 +0800 [thread overview]
Message-ID: <851fc09e0801310530p5f5839aat141ae9fcb6713b25@mail.gmail.com> (raw)
In-Reply-To: <20080131121823.GF12571@elte.hu>
Jan 31, 2008 8:18 PM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Huang, Ying <ying.huang@intel.com> wrote:
>
> > + /* Assume pages are mapped as WB */
> > + if (mode == IOR_MODE_UNCACHED)
> > + set_memory_uc(md->virt_addr, md->num_pages);
> > + /* Assume pages are mapped as unexecutable */
> > + if ((__supported_pte_mask & _PAGE_NX) &&
> > + xmode == IOR_XMODE_EXEC)
> > + set_memory_x(md->virt_addr, md->num_pages);
>
> hm, why is the check for __supported_pte_mask needed? That is already
> listened to in set_memory_x(). [if not then it's an ioremap bug that we
> want to fix.]
OK, I will check it.
> > -static int ioremap_change_attr(unsigned long paddr, unsigned long size,
> > - enum ioremap_mode mode,
> > - enum ioremap_xmode xmode)
> > +int ioremap_change_attr(unsigned long paddr, unsigned long size,
> > + enum ioremap_mode mode,
> > + enum ioremap_xmode xmode)
>
> hm, there should be no need to use this raw API.
Oh, you are right. __efi_ioremap() is only used when there is no
identity map. So ioremap_change_attr() need not to be called in
__efi_ioremap().
Best Regards,
Huang Ying
next prev parent reply other threads:[~2008-01-31 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 7:36 Huang, Ying
2008-01-31 12:18 ` Ingo Molnar
2008-01-31 13:30 ` huang ying [this message]
2008-01-31 14:36 ` Arjan van de Ven
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=851fc09e0801310530p5f5839aat141ae9fcb6713b25@mail.gmail.com \
--to=huang.ying.caritas@gmail.com \
--cc=ak@suse.de \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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®