From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>,
debian-kernel <debian-kernel@lists.debian.org>,
Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: pvops microcode support for AMD FAM >= 15
Date: Wed, 19 Dec 2012 15:28:28 -0500 [thread overview]
Message-ID: <20121219202828.GL15037@phenom.dumpdata.com> (raw)
In-Reply-To: <1354782871.28777.12.camel@dagon.hellion.org.uk>
On Thu, Dec 06, 2012 at 08:34:31AM +0000, Ian Campbell wrote:
> (trim quote please...)
> On Wed, 2012-12-05 at 21:47 +0000, Konrad Rzeszutek Wilk wrote:
> > Do you want to prep a patch that I can stick in my 'microcode' branch?
> > .. That I will at some point try to upstream.
>
> You might want to look back at the archives when Jeremy first tried to
> upstream this work, it was a vehement "No" and the resulting thread was
> not pretty.
>
> Now that we have early loading via the hypervisor in 4.2 and Linux is
> finally in the process of growing its own early microcode loading
> solution I suspect the No would be even firmer.
>
> It is on xenbits if you want it anyway:
>
> git://xenbits.xen.org/people/ianc/linux-2.6.git debian/wheezy/microcode
Thx. Pulled it in my stable/misc branch.
>
> About the only argument I can see for continuing to try upstreaming this
> stuff is that in
> http://www.gossamer-threads.com/lists/linux/kernel/1583630 Fenghua says:
>
> Note, however, that Linux users have gotten used to being able
> to install a microcode patch in the field without having a
> reboot; we support that model too.
>
> i.e. this is an argument for keeping the previous scheme in parallel,
> which I suppose is an argument for supporting the same under Xen (I
> don't know if its a good one though.
>
> Ian.
>
> --
> Ian Campbell
>
>
> All the existing 2.0.x kernels are to buggy for 2.1.x to be the
> main goal.
> -- Alan Cox
>
next prev parent reply other threads:[~2012-12-19 20:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1353936077.5830.30.camel@zakaz.uk.xensource.com>
2012-11-26 13:44 ` pvops microcode support for AMD FAM >= 15 Jan Beulich
2012-11-26 14:13 ` Ian Campbell
[not found] ` <1353939218.5830.34.camel@zakaz.uk.xensource.com>
2012-11-26 14:58 ` Boris Ostrovsky
2012-11-26 23:47 ` Boris Ostrovsky
2012-12-05 12:43 ` Ian Campbell
[not found] ` <1354711402.15296.188.camel@zakaz.uk.xensource.com>
2012-12-05 14:01 ` Ian Campbell
2012-12-05 16:48 ` Boris Ostrovsky
2012-12-05 17:02 ` Jan Beulich
2012-12-05 17:27 ` Boris Ostrovsky
2012-12-05 17:53 ` Ian Campbell
[not found] ` <1354730007.17165.31.camel@zakaz.uk.xensource.com>
2012-12-06 10:08 ` Ian Campbell
2012-12-06 11:13 ` Jan Beulich
2012-12-06 13:08 ` Boris Ostrovsky
2012-12-06 13:17 ` Jan Beulich
2012-12-05 17:05 ` Ian Campbell
[not found] ` <1354727148.17165.23.camel@zakaz.uk.xensource.com>
2012-12-05 17:33 ` Boris Ostrovsky
2012-12-05 12:46 ` Ian Campbell
[not found] ` <1354711599.15296.191.camel@zakaz.uk.xensource.com>
2012-12-05 21:47 ` Konrad Rzeszutek Wilk
2012-12-06 8:34 ` Ian Campbell
[not found] ` <1354782871.28777.12.camel@dagon.hellion.org.uk>
2012-12-06 10:59 ` Jan Beulich
2012-12-19 20:28 ` Konrad Rzeszutek Wilk [this message]
2012-12-05 13:10 ` Ben Guthro
2012-11-26 13:21 Ian Campbell
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=20121219202828.GL15037@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=debian-kernel@lists.debian.org \
--cc=ijc@hellion.org.uk \
--cc=konrad@kernel.org \
--cc=xen-devel@lists.xen.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).