From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@amd64.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [GIT PULL] x86, microcode fixes for 3.2
Date: Mon, 26 Mar 2012 07:52:45 -0700 [thread overview]
Message-ID: <4F7082BD.9030107@zytor.com> (raw)
In-Reply-To: <20120326084810.GA31480@aftab>
On 03/26/2012 01:48 AM, Borislav Petkov wrote:
> On Sun, Mar 25, 2012 at 12:27:23PM -0700, H. Peter Anvin wrote:
>> I keep wondering if we couldn't have the early-static trap handlers be
>> aware of exception tables, too; they wouldn't have to worry about
>> modules and so it would be reasonably easy.
>
> Well, we talked about this recently and then we decided we needed the
> extable-sorting-at-build-time patches before we make those static trap
> handlers aware of extables. What happened to those patches, btw? See
> thread at http://marc.info/?l=linux-kernel&m=132196692827070
>
Hm... I hope that didn't stall out because of me... the amount of
overload I have been under lately is a bit scary.
I was going to dredge out the perfect hash stuff that I had, but the
sorting stuff could be done without that.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-03-26 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 20:43 [GIT PULL] x86, microcode fixes for 3.2 Borislav Petkov
2011-12-02 19:46 ` Borislav Petkov
2011-12-05 9:26 ` Ingo Molnar
2011-12-05 15:10 ` Borislav Petkov
2012-03-25 19:27 ` H. Peter Anvin
2012-03-26 8:48 ` Borislav Petkov
2012-03-26 14:52 ` H. Peter Anvin [this message]
2012-03-26 15:25 ` Borislav Petkov
2012-03-26 17:56 ` H. Peter Anvin
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=4F7082BD.9030107@zytor.com \
--to=hpa@zytor.com \
--cc=JBeulich@suse.com \
--cc=bp@amd64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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.