From: Sean Christopherson <seanjc@google.com>
To: Thorsten Glaser <t.glaser@tarent.de>
Cc: kvm <kvm@vger.kernel.org>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] KVM: VMX: Require KVM_SET_TSS_ADDR being called prior to running a VCPU
Date: Wed, 28 Jun 2023 12:07:18 -0700 [thread overview]
Message-ID: <ZJyE5jXfYu2bXeVo@google.com> (raw)
In-Reply-To: <ed1914ca-bb4d-78e4-8af-432a5829739@tarent.de>
On Wed, Jun 28, 2023, Thorsten Glaser wrote:
> On Wed, 28 Jun 2023, Sean Christopherson wrote:
> >So long as the VMs you care about don't have issues, the message is completely
> >benign, and expected since you are running on Nehalem, which doesn't support
> >unrestricted guest.
>
> OK, thanks.
>
> Might want to make that more well-known… though I don’t have a
> good idea how.
I'm leaning toward deleting the message entirely. It was placed there 10+ years
ago to alert users that they needed to upgrade QEMU. At this point, if someone
files a bug report against a 10+ year old QEMU build, the very first question is
going to be if the issue reproduces on a more recent build. The only possible
benefit I can think of is for people writing new VMMs from scratch, but any benefit
there is also dubious for a variety of reasons.
prev parent reply other threads:[~2023-06-28 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 7:38 [PATCH] KVM: VMX: Require KVM_SET_TSS_ADDR being called prior to running a VCPU Jan Kiszka
2013-03-15 11:43 ` Gleb Natapov
2013-03-18 16:50 ` Marcelo Tosatti
2023-06-28 1:29 ` Thorsten Glaser
2023-06-28 16:21 ` Sean Christopherson
2023-06-28 17:53 ` Thorsten Glaser
2023-06-28 19:07 ` Sean Christopherson [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=ZJyE5jXfYu2bXeVo@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=t.glaser@tarent.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