linux-kernel - Re: [PATCH 3/9] x86/moorestown: add moorestown platform flags

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090626184536.GA30885@elte.hu>
Date:	Fri, 26 Jun 2009 20:45:36 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	"Pan, Jacob jun" <jacob.jun.pan@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...ux.intel.com>
Subject: Re: [PATCH 3/9] x86/moorestown: add moorestown platform flags


* Jesse Barnes <jbarnes@...tuousgeek.org> wrote:

> On Fri, 26 Jun 2009 09:19:55 +0200
> Ingo Molnar <mingo@...e.hu> wrote:
> > >  void platform_feature_init_default(int subarch_id)
> > >  {
> > > -	printk(KERN_INFO "Use default X86 platform feature set\n");
> > > +	if ((subarch_id >= 0) && (subarch_id < N_X86_SUBARCHS)) {
> > > +		if (subarch_id == X86_SUBARCH_MRST) {
> > > +			setup_mrst_default_feature();
> > > +			return;
> > > +		}
> > > +	} else {
> > > +		printk(KERN_INFO "Use default X86 platform feature
> > > set\n");
> > > +	}
> > >  }
> > 
> > Why dont we have some clean and robust PCI config space based 
> > enumeration instead of this boot ID based thing?
> 
> MRST has special PCI support that depends on having the platform 
> identified already, so if you want to use something other than a 
> flag here, maybe we could use an SFI string instead.

An SFI flag would be nicer than any PCI space method i guess - if it 
can be accessed early enough.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/