public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [CFT][PATCH] 2.6.4-rc1 remove x86 boot page tables
Date: Mon, 01 Mar 2004 11:05:38 -0800	[thread overview]
Message-ID: <1078167938.27444.43.camel@nighthawk> (raw)
In-Reply-To: <m1vflp81kq.fsf@ebiederm.dsl.xmission.com>

On Sun, 2004-02-29 at 23:32, Eric W. Biederman wrote:
> I have rewritten and compiled tested the boot_ioremap code but I don't
> have a configuration to test it. This effects the EFI code and the
> numa srat code.   It might be worth replacing boot_ioremap with __va()
> to reduce the amount of error checking necessary.

I can probably have someone test it, but you're right, we don't really
need boot_ioremap() if we're going to map in all 4G at boot time.  I'd
just prefer that you remove it completely in your patch.  

I can test it on some SRAT hardware if you'd like.  

-- dave


  reply	other threads:[~2004-03-01 19:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-01  7:32 [CFT][PATCH] 2.6.4-rc1 remove x86 boot page tables Eric W. Biederman
2004-03-01 19:05 ` Dave Hansen [this message]
2004-03-02  5:29   ` Eric W. Biederman
2004-03-02  6:47 ` H. Peter Anvin
2004-03-02 12:53   ` [PATCH] Clean up empty_zero_page abuse Brian Gerst
2004-03-02 17:56   ` [CFT][PATCH] 2.6.4-rc1 remove x86 boot page tables Eric W. Biederman
2004-03-02  9:21 ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2004-03-01 18:13 Tolentino, Matthew E
2004-03-02  5:36 ` Eric W. Biederman
2004-03-03  6:47 ` Eric W. Biederman
2004-03-03  8:15 ` Eric W. Biederman
2004-03-03 19:45 Tolentino, Matthew E
2004-03-05 14:23 ` Eric W. Biederman

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=1078167938.27444.43.camel@nighthawk \
    --to=haveblue@us.ibm.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.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