From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] kvm-unit-tests: Check CPUID level/xlevel before using CPUID data
Date: Fri, 29 Aug 2014 09:54:12 +0200 [thread overview]
Message-ID: <540031A4.3000505@redhat.com> (raw)
In-Reply-To: <1409248950-16268-1-git-send-email-ehabkost@redhat.com>
Il 28/08/2014 20:02, Eduardo Habkost ha scritto:
> Change the kvm-unit-tests x86 code to always check CPUID level/xlevel before
> looking at CPUID data. Otherwise, the test code will be looking at bogus data.
>
> Eduardo Habkost (3):
> x86: apic: Look up MAXPHYADDR on CPUID correctly
> x86: vmx: Use cpuid_maxphyaddr()
> x86: Check level, xlevel before returning CPUID data
>
> lib/x86/processor.h | 18 +++++++++++++++++-
> x86/apic.c | 2 +-
> x86/vmx.c | 6 +++---
> 3 files changed, 21 insertions(+), 5 deletions(-)
>
Applying this series, thanks.
Paolo
prev parent reply other threads:[~2014-08-29 7:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 18:02 [PATCH 0/3] kvm-unit-tests: Check CPUID level/xlevel before using CPUID data Eduardo Habkost
2014-08-28 18:02 ` [PATCH 1/3] x86: apic: Look up MAXPHYADDR on CPUID correctly Eduardo Habkost
2014-08-28 18:02 ` [PATCH 2/3] x86: vmx: Use cpuid_maxphyaddr() Eduardo Habkost
2014-08-28 18:02 ` [PATCH 3/3] x86: Check level, xlevel before returning CPUID data Eduardo Habkost
2014-08-29 7:54 ` Paolo Bonzini [this message]
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=540031A4.3000505@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.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