From: Paolo Bonzini <pbonzini@redhat.com>
To: Bandan Das <bsd@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Robert Hoo <robert.hu@linux.intel.com>,
balducci@units.it, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] 3.1.0-rc{0,1} doesn't start
Date: Wed, 21 Nov 2018 14:59:15 +0100 [thread overview]
Message-ID: <f9115bcb-deec-2382-2cc2-48c166029f53@redhat.com> (raw)
In-Reply-To: <jpgo9aj3wji.fsf@linux.bootlegged.copy>
On 21/11/18 05:05, Bandan Das wrote:
>> Oh, wait. I didn't understand that. Then yeah, fixing QEMU is enough.
>> KVM is not reporting the MSR in the list on AMD, but it should (and it
>> should implement the MSR, of course!).
>>
> Until AMD implements somethinig, on the KVM side, shouldn't we let
> kvm_x86_ops->get_msr_feature(msr)) handle MSR_IA32_ARCH_CAPABILITIES ?
>
Either is okay. But the MSR is not really vendor dependent, and can be
added even to older models. So it may make sense to move it to generic
code.
Paolo
next prev parent reply other threads:[~2018-11-21 13:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 16:40 [Qemu-devel] 3.1.0-rc{0,1} doesn't start balducci
2018-11-19 10:43 ` Dr. David Alan Gilbert
2018-11-19 12:54 ` balducci
2018-11-19 14:16 ` Dr. David Alan Gilbert
2018-11-19 18:35 ` Dr. David Alan Gilbert
2018-11-19 18:54 ` balducci
2018-11-19 18:56 ` Dr. David Alan Gilbert
2018-11-19 20:43 ` Cole Robinson
2018-11-19 21:55 ` Bandan Das
2018-11-19 23:00 ` Eduardo Habkost
2018-11-20 18:40 ` Paolo Bonzini
2018-11-20 18:48 ` Eduardo Habkost
2018-11-20 19:34 ` Paolo Bonzini
2018-11-21 4:05 ` Bandan Das
2018-11-21 13:59 ` Paolo Bonzini [this message]
2018-11-20 8:27 ` balducci
2018-11-21 4:28 ` Bandan Das
2018-11-21 7:48 ` balducci
2018-11-21 12:50 ` Eduardo Habkost
2018-11-26 4:17 ` [Qemu-devel] [PATCH] kvm: Use KVM_GET_MSR_INDEX_LIST for MSR_IA32_ARCH_CAPABILITIES support Bandan Das
2018-11-26 16:34 ` Eduardo Habkost
2018-12-11 10:54 ` Hu, Robert
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=f9115bcb-deec-2382-2cc2-48c166029f53@redhat.com \
--to=pbonzini@redhat.com \
--cc=balducci@units.it \
--cc=bsd@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robert.hu@linux.intel.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 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).