From: Suresh Siddha <suresh.b.siddha@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Andi Kleen <andi@firstfloor.org>,
Avuton Olrich <avuton@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Fail to early boot with v2.6.27-rc2 to at least v2.6.29-rc2 due to dc1e35c
Date: Thu, 22 Jan 2009 14:56:18 -0800 [thread overview]
Message-ID: <20090122225618.GA16033@linux-os.sc.intel.com> (raw)
In-Reply-To: <4978F5F8.1040103@zytor.com>
On Thu, Jan 22, 2009 at 02:40:56PM -0800, H. Peter Anvin wrote:
> Suresh Siddha wrote:
> > Ok. Here is the patch for this aswell. Thanks.
>
> I wonder if it wouldn't be better to do this in the CPUID code rather
> than in the xsave code...
We can do this in the cpuid code aswell, but the dependency information
varies from feature to feature and there are no architectural methods here.
So I think its better to keep it near the code enabling that feaure.
thanks,
suresh
next prev parent reply other threads:[~2009-01-22 22:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 14:04 Fail to early boot with v2.6.27-rc2 to at least v2.6.29-rc2 due to dc1e35c Avuton Olrich
2009-01-19 14:28 ` Avuton Olrich
2009-01-19 18:55 ` H. Peter Anvin
2009-01-19 19:31 ` Avuton Olrich
2009-01-19 20:07 ` H. Peter Anvin
2009-01-19 20:11 ` Suresh Siddha
2009-01-19 21:46 ` Avuton Olrich
2009-01-19 21:57 ` Suresh Siddha
2009-01-19 22:07 ` H. Peter Anvin
2009-01-19 22:14 ` Suresh Siddha
2009-01-19 22:24 ` H. Peter Anvin
2009-01-21 5:20 ` Andi Kleen
2009-01-22 22:22 ` Suresh Siddha
2009-01-22 22:40 ` H. Peter Anvin
2009-01-22 22:56 ` Suresh Siddha [this message]
2009-01-20 3:35 ` Valdis.Kletnieks
2009-01-20 6:36 ` H. Peter Anvin
2009-01-22 0:38 ` H. Peter Anvin
2009-01-22 2:26 ` Avuton Olrich
2009-01-22 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=20090122225618.GA16033@linux-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=andi@firstfloor.org \
--cc=avuton@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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