From: Dave Young <dyoung@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Matt Fleming <matt@console-pimps.org>,
matt.fleming@intel.com, hpa@zytor.com, akpm@linux-foundation.org,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-efi@vger.kernel.org
Subject: Re: [PATCH] ignore ,keep for efi earlyprintk
Date: Wed, 30 Apr 2014 09:12:50 +0800 [thread overview]
Message-ID: <20140430011250.GB1959@darkstar.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1404291217380.6261@ionos.tec.linutronix.de>
On 04/29/14 at 12:21pm, Thomas Gleixner wrote:
> On Tue, 29 Apr 2014, Matt Fleming wrote:
> > I would just replace the existing calls to early_ioremap() with
> > efi_ioremap() and implement it like so (all in
> > arch/x86/platform/efi/early_printk.c),
> >
> > static void *efi_ioremap(resource_size_t phys_addr, unsigned long size)
> > {
> > if (system_state == SYSTEM_BOOTING)
> > return early_ioremap(phys_addr, size);
> >
> > return ioremap(phys_addr, size);
> > }
> >
> > At least I think SYSTEM_BOOTING is the correct way to figure out when to
> > use early_ioremap(), I'm open to other suggestions though.
>
> ioremap() is available after paging_init() has been called.
>
> Just x86 has this extra bits so you can use early_ioremap/unmap
> _AFTER_ paging_init(). No idea why, but probably to cope with some
> brilliant init calls which run pre and post paging_init().
Good idea, will use an initcall function for this purpose.
Thanks a lot.
Dave
prev parent reply other threads:[~2014-04-30 1:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 9:36 Dave Young
2014-04-24 10:45 ` Ingo Molnar
2014-04-25 1:53 ` Dave Young
2014-04-25 11:53 ` Matt Fleming
2014-04-26 7:28 ` Dave Young
2014-04-29 9:45 ` Matt Fleming
2014-04-29 10:03 ` Dave Young
2014-04-29 10:21 ` Thomas Gleixner
2014-04-30 1:12 ` Dave Young [this message]
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=20140430011250.GB1959@darkstar.redhat.com \
--to=dyoung@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
Powered by JetHome