From: stsp <stsp2@yandex.ru>
To: Jim Mattson <jmattson@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.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: Tue, 29 Jun 2021 01:52:19 +0300 [thread overview]
Message-ID: <b019a84a-fa9e-314c-93cd-4e2031fc10d4@yandex.ru> (raw)
In-Reply-To: <CALMp9eSW6ZuLbbrosJtG=ejjQCRDuPBs_g4j3SXPZXHjQ7zqDg@mail.gmail.com>
29.06.2021 01:35, Jim Mattson пишет:
> How long are you willing to defer the EINTR? What if you're running at
> the target of a live migration, and the guest's IDT page needs to be
> demand-fetched over the network? It may be quite some time before you
> can actually deliver that exception.
OK, understood, thank you.
I wonder how many other non-atomic
things are there in KVM, but probably
that doesn't matter much, if
run->ready_for_injection covers them
all at once...
next prev parent reply other threads:[~2021-06-28 22:52 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
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 [this message]
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=b019a84a-fa9e-314c-93cd-4e2031fc10d4@yandex.ru \
--to=stsp2@yandex.ru \
--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=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--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 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.