From: Jan Kiszka <jan.kiszka@siemens.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [Bug 54471] New: nVMX: TRUE* MSRs unnecessary
Date: Mon, 25 Feb 2013 15:29:05 +0100 [thread overview]
Message-ID: <512B7531.4050407@siemens.com> (raw)
In-Reply-To: <bug-54471-28872@https.bugzilla.kernel.org/>
On 2013-02-25 15:04, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=54471
>
> Summary: nVMX: TRUE* MSRs unnecessary
> Product: Virtualization
> Version: unspecified
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: enhancement
> Priority: P1
> Component: kvm
> AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
> ReportedBy: nyh@math.technion.ac.il
> Regression: No
>
>
> According to the spec, the TRUE* MSRs are only necessary if bit 55 of VMX_BASIC
> is on. Since we don't set this bit, we don't need to provide these MSRs...
> So probably we shouldn't.
I tend to say we should (i.e. set bit 55) as there is the risk that
buggy guests could needlessly get confused when we expose very recent
features (like EPT) and do not provide such "old-fashioned" stuff.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-02-25 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 14:04 [Bug 54471] New: nVMX: TRUE* MSRs unnecessary bugzilla-daemon
2013-02-25 14:05 ` [Bug 54471] " bugzilla-daemon
2013-02-25 14:29 ` Jan Kiszka [this message]
2013-02-25 14:29 ` bugzilla-daemon
2015-03-17 3:53 ` bugzilla-daemon
2015-04-08 8:57 ` bugzilla-daemon
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=512B7531.4050407@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--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).