From: Florian Manschwetus <florianmanschwetus@gmx.de>
To: xen-devel@lists.xensource.com
Subject: Re: Xen 4.1: x86/ucode: fix for AMD Fam15 CPUs
Date: Wed, 04 Jan 2012 17:50:48 +0100 [thread overview]
Message-ID: <4F048368.2000204@gmx.de> (raw)
In-Reply-To: <4F047035.1060304@amd.com>
[-- Attachment #1.1: Type: text/plain, Size: 797 bytes --]
Am 04.01.2012 16:28, schrieb Christoph Egger:
>
> x86/ucode: fix for AMD Fam15 CPUs
>
> Remove hardcoded maximum size a microcode patch can have. This is
> dynamic now.
>
> The microcode patch for family15h can be larger than 2048 bytes and
> gets silently truncated.
>
> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
> Backport from xen-unstable changeset 24411:ca5f588bd203 to Xen 4.1
>
Could this fix my xen boot problem on athlon x2 (fam 15 according to
cpuinfo)
See xen-devel post:
[Xen-devel] [Xen-users] Problem booting xen 4.1.2 on Athlon 64 X2
from 22.12.2011 ff
Regards,
Florian
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
[-- Attachment #1.2: S/MIME Kryptografische Unterschrift --]
[-- Type: application/pkcs7-signature, Size: 2332 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-01-04 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 15:28 Xen 4.1: x86/ucode: fix for AMD Fam15 CPUs Christoph Egger
2012-01-04 16:50 ` Florian Manschwetus [this message]
2012-01-04 19:31 ` Wei Huang
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=4F048368.2000204@gmx.de \
--to=florianmanschwetus@gmx.de \
--cc=xen-devel@lists.xensource.com \
/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.