From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: <bp@suse.de>
Cc: <konrad.wilk@oracle.com>, <x86@kernel.org>,
<gregkh@linuxfoundation.org>, <stable@vger.kernel.org>,
<david.vrabel@citrix.com>, <rshendershot@mchsi.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3.17 100/141] x86, microcode: Fix accessing dis_ucode_ldr on 32-bit
Date: Thu, 27 Nov 2014 09:14:11 -0800 (PST) [thread overview]
Message-ID: <5a9dde8d-1936-4910-a78a-15d4f9bfffc2@default> (raw)
----- bp@suse.de wrote:
> On Thu, Nov 27, 2014 at 11:21:19AM -0500, Konrad Rzeszutek Wilk
> wrote:
> > > Ok, but let's have a clean design: maybe have a weak default stub
> which
> > > returns false when PARAVIRT is not enabled in the .config and then
> add
> > > an override in, say, arch/x86/kernel/paravirt.c which returns true
> when
> > > running as a guest. Something like that, at least.
> >
> > You are describing 'paravirt_enabled()' :-)
>
> Haha.
>
> Although I have a suspicion this won't work either because we're
> loading
> microcode very early on 32-bit, before paging has been enabled, and
> accessing pv_info.paravirt_enabled will probably go boom. AFAICT, from
> a
> quick glance.
The overnight tests passed. This includes baremetal, HVM and PV(H), 32- and 64-bit.
-boris
next reply other threads:[~2014-11-27 17:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 17:14 Boris Ostrovsky [this message]
2014-11-27 17:20 ` [PATCH 3.17 100/141] x86, microcode: Fix accessing dis_ucode_ldr on 32-bit Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2014-11-27 23:33 Boris Ostrovsky
2014-11-27 3:13 Boris Ostrovsky
2014-11-27 9:12 ` Borislav Petkov
2014-11-27 16:21 ` Konrad Rzeszutek Wilk
2014-11-27 16:36 ` Borislav Petkov
2014-11-19 20:50 [PATCH 3.17 000/141] 3.17.4-stable review Greg Kroah-Hartman
2014-11-19 20:52 ` [PATCH 3.17 100/141] x86, microcode: Fix accessing dis_ucode_ldr on 32-bit Greg Kroah-Hartman
2014-11-25 18:12 ` Boris Ostrovsky
2014-11-25 18:24 ` Borislav Petkov
2014-11-25 18:43 ` Boris Ostrovsky
2014-11-25 18:43 ` Borislav Petkov
2014-11-25 18:55 ` Boris Ostrovsky
2014-11-25 19:03 ` Borislav Petkov
2014-11-25 19:23 ` Boris Ostrovsky
2014-11-25 19:08 ` Borislav Petkov
2014-11-25 19:28 ` Boris Ostrovsky
2014-11-25 20:26 ` Borislav Petkov
2014-11-25 20:36 ` Konrad Rzeszutek Wilk
2014-11-25 21:17 ` Borislav Petkov
2014-11-25 21:59 ` Boris Ostrovsky
2014-11-25 22:18 ` Borislav Petkov
2014-11-26 5:00 ` Boris Ostrovsky
2014-11-26 10:55 ` Borislav Petkov
2014-11-26 12:39 ` boris ostrovsky
2014-11-26 14:44 ` Borislav Petkov
2014-11-25 18:45 ` Greg Kroah-Hartman
2014-11-25 18:47 ` Borislav Petkov
2014-11-25 18:50 ` Boris Ostrovsky
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=5a9dde8d-1936-4910-a78a-15d4f9bfffc2@default \
--to=boris.ostrovsky@oracle.com \
--cc=bp@suse.de \
--cc=david.vrabel@citrix.com \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rshendershot@mchsi.com \
--cc=stable@vger.kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).