From: Borislav Petkov <bp@suse.de>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, david.vrabel@citrix.com,
konrad.wilk@oracle.com, pbonzini@redhat.com, gleb@kernel.org,
kvm@vger.kernel.org
Subject: Re: [PATCH] x86, microcode: Don't initialize microcode code on paravirt
Date: Mon, 1 Dec 2014 23:37:08 +0100 [thread overview]
Message-ID: <20141201223708.GF4730@pd.tnic> (raw)
In-Reply-To: <547CEC5C.9070201@oracle.com>
On Mon, Dec 01, 2014 at 05:31:56PM -0500, Boris Ostrovsky wrote:
> I think so. The problem we have now is __pa() macro that we only use
> on 32-bit. I'll queue this for overnight tests to make sure and if it
> indeed works then 3.19 should be fine.
Cool, thanks.
I'd still take your patch for 3.19 though because I'm fixing the 32-bit
reloading path properly and will remove the ifdef afterwards.
And even then, I'd like to prevent loading the module on a paravirt
guest if it is totally unneeded there.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-12-01 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1417469264-31470-1-git-send-email-boris.ostrovsky@oracle.com>
2014-12-01 21:57 ` [PATCH] x86, microcode: Don't initialize microcode code on paravirt Konrad Rzeszutek Wilk
2014-12-01 22:12 ` Paolo Bonzini
2014-12-01 22:31 ` Borislav Petkov
[not found] ` <20141201220057.GC4730@pd.tnic>
2014-12-01 22:31 ` Boris Ostrovsky
2014-12-01 22:37 ` Borislav Petkov [this message]
2014-12-02 14:36 ` Boris Ostrovsky
2014-12-02 14:58 ` Borislav Petkov
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=20141201223708.GF4730@pd.tnic \
--to=bp@suse.de \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=gleb@kernel.org \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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).