From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 0/4] x86: update AMD CPUID bits
Date: Sun, 05 Sep 2010 11:07:24 +0300 [thread overview]
Message-ID: <4C834FBC.1020901@redhat.com> (raw)
In-Reply-To: <1283506069-1096-1-git-send-email-andre.przywara@amd.com>
On 09/03/2010 12:27 PM, Andre Przywara wrote:
> (resent to add kvm@vger)
What about linux-kernel? These patches should go in via the x86 tree.
> Recently the public AMD CPUID specification
> http://support.amd.com/us/Processor_TechDocs/25481.pdf
> has been updated and revealed new CPUID flag feature names.
> The following patches introduce them to the kernel to properly
> display them in /proc/cpuinfo and allows KVM guests to use them.
> Note: One bit has been renamed, so I propose patch 1/4 for inclusion
> in the stable series.
>
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-09-05 8:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 9:27 [PATCH 0/4] x86: update AMD CPUID bits Andre Przywara
2010-09-03 9:27 ` [PATCH 1/4] x86: Fix misnamed AMD CPUID feature bit Andre Przywara
2010-09-05 8:07 ` Avi Kivity
2010-09-05 15:37 ` Andre Przywara
2010-09-05 15:53 ` Avi Kivity
2010-09-03 9:27 ` [PATCH 2/4] x86: Update AMD CPUID feature bits Andre Przywara
2010-09-03 9:27 ` [PATCH 3/4] x86: Fix allowed CPUID bits for KVM guests Andre Przywara
2010-09-05 8:11 ` Avi Kivity
2010-09-06 12:05 ` Andre Przywara
2010-09-06 12:14 ` Avi Kivity
2010-09-03 9:27 ` [PATCH 4/4] x86, kvm: add new AMD SVM feature bits Andre Przywara
2010-09-05 8:07 ` Avi Kivity [this message]
2010-09-05 8:13 ` [PATCH 0/4] x86: update AMD CPUID bits Avi Kivity
2010-09-05 15:10 ` Andre Przywara
2010-09-05 15:14 ` Avi Kivity
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=4C834FBC.1020901@redhat.com \
--to=avi@redhat.com \
--cc=andre.przywara@amd.com \
--cc=kvm@vger.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).