public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Huang Ying <ying.huang@intel.com>
Cc: Brian Maly <bmaly@redhat.com>, Yinghai Lu <yinghai@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix DMI for EFI
Date: Thu, 5 Mar 2009 11:05:15 +0100	[thread overview]
Message-ID: <20090305100515.GA29499@elte.hu> (raw)
In-Reply-To: <1236216818.24215.24.camel@yhuang-dev.sh.intel.com>


* Huang Ying <ying.huang@intel.com> wrote:

> On Thu, 2009-03-05 at 01:54 +0800, Ingo Molnar wrote:
> > * Brian Maly <bmaly@redhat.com> wrote:
> > 
> > >
> > >
> > >> Hm, could we ever find ourselves in the positition of having to access 
> > >> the DMI strings table in the EFI init code, to implement a quirk? I 
> > >> think that's quite plausible.
> > >
> > >> OTOH, with some DMI quirks in EFI tables it's a bit of a chicken and 
> > >> egg problem. Can DMI strings ever be outside of EFI tables on EFI 
> > >> systems?
> > >
> > >> 	Ingo
> > >
> > > Right now it is EFI that loads the dmi tables (and all other 
> > > tables such as ACPI), so it is a chicken and the egg. I think 
> > > that if dmi is ever needed by EFI, the dmi scan will have to 
> > > be moved inside efi_init. We could move the dmi scan into 
> > > efi_init and do the dmi scan the moment we have the dmi table. 
> > > Thats really the soonest point we could scan on EFI systems. 
> > > Im OK with moving dmi to efi_init if you prefer.
> > 
> > Your patch looks fine, but i'd like to hear the opinion of Ying 
> > Huang as well.
> 
> This patch is OK for me.

thanks. There are two EFI patches queued up for .29:

dd39ecf: x86: EFI: Back efi_ioremap with init_memory_mapping instead of FIX_MAP
ff0c087: x86: fix DMI on EFI

	Ingo

  reply	other threads:[~2009-03-05 10:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-01  2:40 [PATCH] fix DMI for EFI Brian Maly
2009-03-01  2:56 ` Yinghai Lu
2009-03-01  3:11   ` Brian Maly
2009-03-01  3:25     ` Yinghai Lu
2009-03-01  3:58       ` Brian Maly
2009-03-04  2:55   ` Brian Maly
2009-03-04 11:00     ` Ingo Molnar
2009-03-04 15:03       ` Brian Maly
2009-03-04 17:54         ` Ingo Molnar
2009-03-04 18:00           ` Brian Maly
2009-03-04 18:02             ` Ingo Molnar
2009-03-05  1:33           ` Huang Ying
2009-03-05 10:05             ` Ingo Molnar [this message]
2009-03-04 17:57     ` [tip:x86/urgent] x86: fix DMI on EFI Brian Maly
  -- strict thread matches above, loose matches on Subject: below --
2009-03-01  1:33 [PATCH] fix DMI for EFI Brian Maly
2009-03-01  2:01 ` Kyle McMartin

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=20090305100515.GA29499@elte.hu \
    --to=mingo@elte.hu \
    --cc=bmaly@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ying.huang@intel.com \
    --cc=yinghai@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