From: Boris Ostrovsky <boris.ostrovsky@amd.com>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <JBeulich@suse.com>,
debian-kernel <debian-kernel@lists.debian.org>
Subject: Re: pvops microcode support for AMD FAM >= 15
Date: Mon, 26 Nov 2012 09:58:58 -0500 [thread overview]
Message-ID: <50B383B2.9060503@amd.com> (raw)
In-Reply-To: <1353939218.5830.34.camel@zakaz.uk.xensource.com>
On 11/26/2012 09:13 AM, Ian Campbell wrote:
> On Mon, 2012-11-26 at 13:44 +0000, Jan Beulich wrote:
>>>>> On 26.11.12 at 14:21, Ian Campbell <ijc@hellion.org.uk> wrote:
>>> Debian has decided to take Jeremy's microcode patch [0] as an interim
>>> measure for their next release. (TL;DR -- Debian is shipping pvops Linux
>>> 3.2 and Xen 4.1 in the next release. See http://bugs.debian.org/693053
>>> and https://lists.debian.org/debian-devel/2012/11/msg00141.html for some
>>> more background).
>>>
>>> However the patch is a bit old and predates the use introduction of
>>> separate firmware files for AMD family >= 15h. Looking at the SuSE
>>> forward ported classic Xen patches it seems like the following patch is
>>> all that is required. But it seems a little too simple to be true and I
>>> don't have any such processors to test on.
>>>
>>> Jan, can you recall if it really is that easy on the kernel side ;-)
>>
>> While so far I didn't myself run anything on post-Fam10 systems
>> either, it really ought to be that easy - the patch format didn't
>> change, it's just that they decided to spit the files by family to
>> keep them manageable.
>>
>> The only other thing to check for is that you don't have any
>> artificial size restriction left in that code (I think patch files early
>> on were limited to 4k in size, and that got lifted during the last
>> couple of years).
>
> I can't find one by inspection, it uses the standard request_firmware
> interface and stashes the result in a valloc'd buffer, neither of which
> suffer from any 4K related limitations AFAIK.
>
> I'll try and track something more recent down to test but the worst
> downside of applying this patch seems to be that something which doesn't
> work still doesn't work.
I submitted a fix for fam 16h to Linux right before the Thanksgiving
break in US and was planning to look at Xen as well. Give me a day or
two to test it.
-boris
>
>> The hypervisor is really going to take care of all other aspects
>> here.
>
> Sweet, thanks.
>
> Ian.
>
next prev parent reply other threads:[~2012-11-26 14:58 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 [this message]
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
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=50B383B2.9060503@amd.com \
--to=boris.ostrovsky@amd.com \
--cc=JBeulich@suse.com \
--cc=debian-kernel@lists.debian.org \
--cc=ijc@hellion.org.uk \
--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 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.