From: Yu Zhang <yu.c.zhang@linux.intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
seanjc@google.com, Michal Luczaj <mhal@rbox.co>,
David Woodhouse <dwmw@amazon.co.uk>
Subject: Re: [PATCH] KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET
Date: Thu, 19 Jan 2023 23:58:00 +0800 [thread overview]
Message-ID: <20230119155800.fiypvvzoalnfavse@linux.intel.com> (raw)
In-Reply-To: <20221228110410.1682852-1-pbonzini@redhat.com>
Hi Paolo,
> diff --git a/tools/testing/selftests/kvm/x86_64/xen_shinfo_test.c b/tools/testing/selftests/kvm/x86_64/xen_shinfo_test.c
> index 721f6a693799..dae510c263b4 100644
> --- a/tools/testing/selftests/kvm/x86_64/xen_shinfo_test.c
> +++ b/tools/testing/selftests/kvm/x86_64/xen_shinfo_test.c
> @@ -962,6 +962,12 @@ int main(int argc, char *argv[])
> }
>
> done:
> + struct kvm_xen_hvm_attr evt_reset = {
> + .type = KVM_XEN_ATTR_TYPE_EVTCHN,
> + .u.evtchn.flags = KVM_XEN_EVTCHN_RESET,
> + };
> + vm_ioctl(vm, KVM_XEN_HVM_SET_ATTR, &evt_reset);
> +
> alarm(0);
> clock_gettime(CLOCK_REALTIME, &max_ts);
>
This change generates a build failure with error message:
"error: a label can only be part of a statement and a declaration is not a statement".
Moving the definition of evt_reset to the beginning of main() can fix it:
diff --git a/tools/testing/selftests/kvm/x86_64/xen_shinfo_test.c b/tools/testing/selftests/kvm/x86_64/xen_shinfo_test.c
index dae510c263b4..d71f1508bb21 100644
--- a/tools/testing/selftests/kvm/x86_64/xen_shinfo_test.c
+++ b/tools/testing/selftests/kvm/x86_64/xen_shinfo_test.c
@@ -623,6 +623,10 @@ int main(int argc, char *argv[])
rs->state = 0x5a;
bool evtchn_irq_expected = false;
+ struct kvm_xen_hvm_attr evt_reset = {
+ .type = KVM_XEN_ATTR_TYPE_EVTCHN,
+ .u.evtchn.flags = KVM_XEN_EVTCHN_RESET,
+ };
for (;;) {
volatile struct kvm_run *run = vcpu->run;
@@ -962,10 +966,6 @@ int main(int argc, char *argv[])
}
done:
- struct kvm_xen_hvm_attr evt_reset = {
- .type = KVM_XEN_ATTR_TYPE_EVTCHN,
- .u.evtchn.flags = KVM_XEN_EVTCHN_RESET,
- };
vm_ioctl(vm, KVM_XEN_HVM_SET_ATTR, &evt_reset);
alarm(0);
B.R.
Yu
next prev parent reply other threads:[~2023-01-19 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 11:04 [PATCH] KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET Paolo Bonzini
2023-01-19 15:58 ` Yu Zhang [this message]
2023-01-19 17:57 ` Sean Christopherson
2023-01-19 18:00 ` Paolo Bonzini
2023-01-19 18:04 ` Sean Christopherson
2023-01-19 18:12 ` Paolo Bonzini
2023-01-19 18:14 ` Sean Christopherson
2023-01-19 18:16 ` Paolo Bonzini
2023-02-24 18:18 ` Michal Luczaj
[not found] <62d7c91f-1486-4aea-8764-352efb383326@email.android.com>
2022-12-28 13:21 ` 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=20230119155800.fiypvvzoalnfavse@linux.intel.com \
--to=yu.c.zhang@linux.intel.com \
--cc=dwmw@amazon.co.uk \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhal@rbox.co \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.