public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@amd64.org>
Cc: Daniel Drake <dsd@laptop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Geode LX boot fails after x86 microcode revision change
Date: Tue, 22 Nov 2011 10:54:03 -0800	[thread overview]
Message-ID: <4ECBEFCB.6010905@zytor.com> (raw)
In-Reply-To: <20111122130048.GB11020@aftab>

On 11/22/2011 05:00 AM, Borislav Petkov wrote:
> 
> Also, we might need the patches which sort extable at build time too,
> which are floating around lkml currently.
> 
> Hmm...
> 

Yes, with the extable set up at build time there isn't really any strong
reason why we couldn't take exceptions very early.

I am supposed to dredge up the perfect hash code I already have for this
(I'm away from work this and next week to deal with personal stuff, so
it might be a bit slow.)

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


      reply	other threads:[~2011-11-22 18:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 19:59 Geode LX boot fails after x86 microcode revision change Daniel Drake
2011-11-08 20:31 ` Borislav Petkov
2011-11-08 22:01   ` H. Peter Anvin
2011-11-08 22:13     ` Petkov, Borislav
2011-11-08 22:17       ` Daniel Drake
2011-11-08 22:37         ` Borislav Petkov
2011-11-08 22:59           ` Daniel Drake
2011-11-09 17:34             ` Borislav Petkov
2011-11-10 13:05               ` Srivatsa S. Bhat
2011-11-10 13:28                 ` Borislav Petkov
2011-11-10 13:37                   ` Srivatsa S. Bhat
2011-11-10 13:34               ` Srivatsa S. Bhat
2011-11-11 18:40               ` Daniel Drake
2011-11-12 13:50                 ` Borislav Petkov
2011-11-08 22:19       ` H. Peter Anvin
2011-11-08 22:40         ` Borislav Petkov
2011-11-22 13:00         ` Borislav Petkov
2011-11-22 18:54           ` H. Peter Anvin [this message]

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=4ECBEFCB.6010905@zytor.com \
    --to=hpa@zytor.com \
    --cc=bp@amd64.org \
    --cc=dsd@laptop.org \
    --cc=linux-kernel@vger.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