From: Andrew Cooper <andrew.cooper3@citrix.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v2 1/4] L1TF KVM ARCH_CAPABILITIES #1
Date: Wed, 25 Jul 2018 20:43:09 +0100 [thread overview]
Message-ID: <0d41452e-4b21-866d-87f0-f4295c410b48@citrix.com> (raw)
In-Reply-To: <20180725143100.16309-2-pbonzini@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
On 25/07/2018 15:30, speck for Paolo Bonzini wrote:
> @@ -1106,7 +1107,8 @@ static int kvm_get_msr_feature(struct kvm_msr_entry *msr)
> {
> switch (msr->index) {
> case MSR_IA32_UCODE_REV:
> - rdmsrl(msr->index, msr->data);
You'll be wanting a break in here.
~Andrew
> + case MSR_IA32_ARCH_CAPABILITIES:
> + rdmsrl_safe(msr->index, &msr->data);
> break;
> default:
> if (kvm_x86_ops->get_msr_feature(msr))
next prev parent reply other threads:[~2018-07-25 19:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 14:30 [MODERATED] [PATCH v2 0/4] L1TF KVM ARCH_CAPABILITIES #0 Paolo Bonzini
2018-07-25 14:30 ` [MODERATED] [PATCH v2 1/4] L1TF KVM ARCH_CAPABILITIES #1 Paolo Bonzini
2018-07-25 19:43 ` Andrew Cooper [this message]
2018-07-26 8:15 ` [MODERATED] " Paolo Bonzini
2018-07-25 14:30 ` [MODERATED] [PATCH v2 2/4] L1TF KVM ARCH_CAPABILITIES #2 Paolo Bonzini
2018-07-30 21:27 ` Thomas Gleixner
2018-07-31 8:22 ` [MODERATED] " Paolo Bonzini
2018-07-31 9:15 ` Thomas Gleixner
2018-07-31 9:35 ` [MODERATED] " Paolo Bonzini
2018-07-25 14:30 ` [MODERATED] [PATCH v2 3/4] L1TF KVM ARCH_CAPABILITIES #3 Paolo Bonzini
2018-07-25 14:31 ` [MODERATED] [PATCH v2 4/4] L1TF KVM ARCH_CAPABILITIES #4 Paolo Bonzini
2018-07-30 21:36 ` Thomas Gleixner
2018-07-31 7:39 ` [MODERATED] " Paolo Bonzini
2018-07-31 7:59 ` Thomas Gleixner
2018-07-25 15:52 ` [MODERATED] Re: [PATCH v2 0/4] L1TF KVM ARCH_CAPABILITIES #0 Greg KH
2018-07-26 8:12 ` Paolo Bonzini
2018-07-26 10:04 ` Greg KH
2018-07-26 10:41 ` Paolo Bonzini
2018-07-30 21:40 ` Thomas Gleixner
2018-08-02 2:51 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-08-02 12:07 ` Paolo Bonzini
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=0d41452e-4b21-866d-87f0-f4295c410b48@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=speck@linutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).