All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
	andi@firstfloor.org, mingo@redhat.com, tglx@linutronix.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86 boot: add E820_RESVD_KERN
Date: Tue, 01 Jul 2008 09:09:42 +0800	[thread overview]
Message-ID: <1214874582.27760.0.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <86802c440806301620hafa3ee3k8c5dbe6c45188d69@mail.gmail.com>

Hi, Yinghai,

On Mon, 2008-06-30 at 16:20 -0700, Yinghai Lu wrote:
> On Mon, Jun 30, 2008 at 3:53 PM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> > On Mon, Jun 30, 2008 at 12:16 PM, Ingo Molnar <mingo@elte.hu> wrote:
> >>
> >> * Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> >>
> >>> > For find_e820_area, this is safe enough. But what about conflict
> >>> > between setup_data and ebda or ramdisk?
> >>>
> >>> can you have setup_data and ebda at the same time?
> >>>
> >>> setup_data and ramdisk should be ok, because bootloader is supposed to
> >>> make them not to be conflicts.
> >>
> >> the more sanity checks we do before relying on some crutial data, the
> >> better. It's easier to panic or sanitize data in some structured way and
> >> complain about it in the syslog than to let things get corrupted. Boot
> >> loaders are ... not unknown to be have bugs too, at times.
> >
> > to address Ying's concern, we could let reserve_setup_data
> > call reserve_early in addition to e820_update_range...
> >
> > reserve_early will panic if RAMDISK overlap efi setup_data...
> >
> 
> Ying,
> please check the attached patch

Which git-x86 head should I use to test the patch? It can not be applied
to x86/master.

Best Regards,
Huang Ying


  reply	other threads:[~2008-07-01  1:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26  6:32 [PATCH 1/2] x86 boot: add E820_RESVD_KERN Huang, Ying
2008-06-26  7:25 ` Yinghai Lu
2008-06-26  7:48   ` Huang, Ying
2008-06-26  9:47     ` Yinghai Lu
2008-06-27  2:22       ` Yinghai Lu
2008-06-27  2:48         ` Huang, Ying
2008-06-27  2:52           ` Yinghai Lu
2008-06-27  3:03             ` Huang, Ying
2008-06-27  5:36               ` Yinghai Lu
2008-06-27 22:05           ` Yinghai Lu
2008-06-30  7:03             ` Huang, Ying
2008-06-30  7:34               ` Yinghai Lu
2008-06-30  7:51                 ` Huang, Ying
2008-06-30  9:15                   ` Yinghai Lu
2008-06-30  9:31                     ` Yinghai Lu
2008-06-30  9:38                     ` Huang, Ying
2008-06-30 19:05                       ` Yinghai Lu
2008-06-30 19:16                         ` Ingo Molnar
2008-06-30 22:53                           ` Yinghai Lu
2008-06-30 23:20                             ` Yinghai Lu
2008-07-01  1:09                               ` Huang, Ying [this message]
2008-07-01  1:21                                 ` Yinghai Lu
2008-07-01  8:34                                   ` Ingo Molnar
2008-07-01  2:45                               ` Huang, Ying
2008-07-01  8:39                                 ` Ingo Molnar
2008-06-30  8:28             ` Ingo Molnar

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=1214874582.27760.0.camel@caritas-dev.intel.com \
    --to=ying.huang@intel.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 \
    /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.