public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: mingo@elte.hu, hpa@zytor.com, andi@firstfloor.org,
	mingo@redhat.com, tglx@linutronix.de,
	linux-kernel@vger.kernel.org, yhlu.kernel@gmail.com
Subject: Re: [PATCH] x86 boot: Pass E820 memory map entries more than 128 via linked list of setup data
Date: Mon, 23 Jun 2008 04:48:13 -0500	[thread overview]
Message-ID: <20080623044813.d2fee3a0.pj@sgi.com> (raw)
In-Reply-To: <1214212441.27182.4.camel@caritas-dev.intel.com>

Huang wrote:
> 4. Current EFI memmap based code does not work properly in all
> situation, for example it can not works with kernel parameter:
> "memmap=exactmap, memmap=<xxx>, ...", "mem=<xxx>" or "noefi".

With "noefi" parameter, my EFI memmap based code is not supposed
to do anything.  The "noefi" parameter asks the kernel to ignore
any EFI support in the firmware it is booting from.

Could you tell me more what you mean by "does not work properly?"

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.940.382.4214

  reply	other threads:[~2008-06-23  9:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11  3:33 [PATCH] x86 boot: Pass E820 memory map entries more than 128 via linked list of setup data Huang, Ying
2008-06-18 11:45 ` Ingo Molnar
2008-06-23  5:54   ` Huang, Ying
2008-06-23  6:53     ` Paul Jackson
2008-06-23  7:21       ` Huang, Ying
2008-06-23  8:47         ` Paul Jackson
2008-06-23  9:14           ` Huang, Ying
2008-06-23  9:48             ` Paul Jackson [this message]
2008-06-24  1:09               ` Huang, Ying
2008-06-24  5:45                 ` H. Peter Anvin
2008-06-24  7:03                   ` Huang, Ying

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=20080623044813.d2fee3a0.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=yhlu.kernel@gmail.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