From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: stsp <stsp2@yandex.ru>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: X86: Fix exception untrigger on ret to user
Date: Mon, 28 Jun 2021 13:00:32 +0200 [thread overview]
Message-ID: <87im1y2qzz.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <87lf6u2r6v.fsf@vitty.brq.redhat.com>
Vitaly Kuznetsov <vkuznets@redhat.com> writes:
> stsp <stsp2@yandex.ru> writes:
>
...
> I wrote a
>> test-case for it, but it involves the entire
>> buildroot setup and you need to wait
>> a bit while it is trying to trigger the race.
>
> Maybe there's an easier way to trigger imminent exit to userspace which
> doesn't involve
[my test editor swallowed the ending of the phrase, sorry about that]
Maybe there's an easier way to trigger imminent exit to userspace which
doesn't involve signals.
--
Vitaly
next prev parent reply other threads:[~2021-06-28 11:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 23:38 [PATCH] KVM: X86: Fix exception untrigger on ret to user Stas Sergeev
2021-06-28 7:20 ` Vitaly Kuznetsov
2021-06-28 9:12 ` stsp
2021-06-28 10:07 ` Vitaly Kuznetsov
2021-06-28 10:32 ` stsp
2021-06-28 10:56 ` Vitaly Kuznetsov
2021-06-28 11:00 ` Vitaly Kuznetsov [this message]
2021-06-28 11:27 ` stsp
2021-06-28 16:39 ` Jim Mattson
2021-06-28 16:57 ` stsp
2021-06-28 16:19 ` Jim Mattson
2021-06-28 17:06 ` stsp
2021-06-28 17:44 ` Jim Mattson
2021-06-28 22:23 ` stsp
2021-06-28 22:35 ` Jim Mattson
2021-06-28 22:52 ` stsp
-- strict thread matches above, loose matches on Subject: below --
2021-06-28 12:46 Stas Sergeev
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=87im1y2qzz.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=stsp2@yandex.ru \
--cc=tglx@linutronix.de \
--cc=wanpengli@tencent.com \
--cc=x86@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