From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Chenyi Qiang <chenyi.qiang@intel.com>, Peter Xu <peterx@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCH v6 2/2] i386: Add notify VM exit support
Date: Mon, 19 Sep 2022 14:11:24 +0800 [thread overview]
Message-ID: <a224206a-c5db-18a4-ecad-2c7132e12452@intel.com> (raw)
In-Reply-To: <5beb9f1c-a419-94f7-a1b9-4aeb281baa41@intel.com>
On 9/19/2022 1:46 PM, Chenyi Qiang wrote:
>> Not sure some warning would be also useful here, but I really don't know
>> the whole context so I can't tell whether there can easily be false
>> positives to pollute qemu log.
>>
>
> The false positive case is not easy to happen unless some potential
> issues in silicon. But in case of it, to avoid polluting qemu log, how
> about:
>
> diff --git a/target/i386/kvm/kvm.c b/target/i386/kvm/kvm.c
> index ae7fb2c495..8f97133cbf 100644
> --- a/target/i386/kvm/kvm.c
> +++ b/target/i386/kvm/kvm.c
> @@ -5213,6 +5213,7 @@ int kvm_arch_handle_exit(CPUState *cs, struct
> kvm_run *run)
> break;
> case KVM_EXIT_NOTIFY:
> ret = 0;
> + warn_report_once("KVM: notify window was exceeded in guest");
> if (run->notify.flags & KVM_NOTIFY_CONTEXT_INVALID) {
> warn_report("KVM: invalid context due to notify vmexit");
> if (has_triple_fault_event) {
how about this
case KVM_EXIT_NOTIFY:
bool ctx_invalid = run->notify.flags & KVM_NOTIFY_CONTEXT_INVALID;
ret = 0;
warn_report_once("KVM: Encounter notify exit with %svalid context",
ctx_invalid ? "in" : "");
if (ctx_invalid) {
...
}
next prev parent reply other threads:[~2022-09-19 6:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 9:28 [PATCH v6 0/2] Enable notify VM exit Chenyi Qiang
2022-09-15 9:28 ` [PATCH v6 1/2] i386: kvm: extend kvm_{get, put}_vcpu_events to support pending triple fault Chenyi Qiang
2022-09-15 9:28 ` [PATCH v6 2/2] i386: Add notify VM exit support Chenyi Qiang
2022-09-16 21:57 ` Peter Xu
2022-09-19 5:46 ` Chenyi Qiang
2022-09-19 6:11 ` Xiaoyao Li [this message]
2022-09-19 15:53 ` Peter Xu
2022-09-20 5:55 ` Chenyi Qiang
2022-09-20 13:59 ` Peter Xu
2022-09-21 3:07 ` Chenyi Qiang
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=a224206a-c5db-18a4-ecad-2c7132e12452@intel.com \
--to=xiaoyao.li@intel.com \
--cc=chenyi.qiang@intel.com \
--cc=eduardo@habkost.net \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).