From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Riccardo Mancini <mancio@amazon.com>
Cc: bataloe@amazon.com, graf@amazon.de, kvm@vger.kernel.org,
Greg Farrell <gffarre@amazon.com>
Subject: Re: [RFC PATCH 4.14] KVM: x86: Backport support for interrupt-based APF page-ready delivery in guest
Date: Tue, 17 Oct 2023 13:22:55 +0200 [thread overview]
Message-ID: <87v8b57asw.fsf@redhat.com> (raw)
In-Reply-To: <62e17c67-953d-469f-84cf-a998a15a8926@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 10/16/23 16:18, Vitaly Kuznetsov wrote:
>> In case keeping legacy mechanism is a must, I would suggest you somehow
>> record the fact that the guest has opted for interrupt-based delivery
>> (e.g. set a global variable or use a static key) and short-circuit
>> do_async_page_fault() to immediately return and not do anything in this
>> case.
>
> I guess you mean "not do anything for KVM_PV_REASON_PAGE_READY in this
> case"?
Yes, of course: KVM_PV_REASON_PAGE_NOT_PRESENT is always a #PF.
--
Vitaly
next prev parent reply other threads:[~2023-10-17 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 15:08 Bug? Incompatible APF for 4.14 guest on 5.10 and later host Mancini, Riccardo
2023-10-05 15:38 ` Vitaly Kuznetsov
2023-10-13 16:36 ` [RFC PATCH 4.14] KVM: x86: Backport support for interrupt-based APF page-ready delivery in guest Riccardo Mancini
2023-10-16 14:18 ` Vitaly Kuznetsov
2023-10-16 21:57 ` Paolo Bonzini
2023-10-17 11:22 ` Vitaly Kuznetsov [this message]
2023-10-05 16:15 ` Bug? Incompatible APF for 4.14 guest on 5.10 and later host Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2023-10-17 13:44 [RFC PATCH 4.14] KVM: x86: Backport support for interrupt-based APF page-ready delivery in guest Mancini, Riccardo
2023-10-17 14:06 ` Vitaly Kuznetsov
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=87v8b57asw.fsf@redhat.com \
--to=vkuznets@redhat.com \
--cc=bataloe@amazon.com \
--cc=gffarre@amazon.com \
--cc=graf@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=mancio@amazon.com \
--cc=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox