From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: x86@kernel.org, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>
Subject: [PATCH RFC 0/6] KVM: x86: Interrupt-based mechanism for async_pf 'page present' notifications
Date: Wed, 29 Apr 2020 11:36:28 +0200 [thread overview]
Message-ID: <20200429093634.1514902-1-vkuznets@redhat.com> (raw)
Concerns were expressed around (ab)using #PF for KVM's async_pf mechanism,
it seems that re-using #PF exception for a PV mechanism wasn't a great
idea after all. The Grand Plan is to switch to using e.g. #VE for 'page
not present' events and normal APIC interrupts for 'page present' events.
This RFC does the later.
Please let me know what you think about the idea in general and the
selected approach in particular.
Vitaly Kuznetsov (6):
Revert "KVM: async_pf: Fix #DF due to inject "Page not Present" and
"Page Ready" exceptions simultaneously"
KVM: x86: extend struct kvm_vcpu_pv_apf_data with token info
KVM: x86: interrupt based APF page-ready event delivery
KVM: x86: acknowledgment mechanism for async pf page ready
notifications
KVM: x86: announce KVM_FEATURE_ASYNC_PF_INT
KVM: x86: Switch KVM guest to using interrupts for page ready APF
delivery
Documentation/virt/kvm/cpuid.rst | 6 ++
Documentation/virt/kvm/msr.rst | 52 +++++++++++--
arch/x86/entry/entry_32.S | 5 ++
arch/x86/entry/entry_64.S | 5 ++
arch/x86/include/asm/hardirq.h | 3 +
arch/x86/include/asm/irq_vectors.h | 6 +-
arch/x86/include/asm/kvm_host.h | 5 +-
arch/x86/include/asm/kvm_para.h | 6 ++
arch/x86/include/uapi/asm/kvm_para.h | 11 ++-
arch/x86/kernel/irq.c | 9 +++
arch/x86/kernel/kvm.c | 42 +++++++++++
arch/x86/kvm/cpuid.c | 3 +-
arch/x86/kvm/x86.c | 107 +++++++++++++++++++++------
include/uapi/linux/kvm.h | 1 +
14 files changed, 228 insertions(+), 33 deletions(-)
--
2.25.3
next reply other threads:[~2020-04-29 9:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 9:36 Vitaly Kuznetsov [this message]
2020-04-29 9:36 ` [PATCH RFC 1/6] Revert "KVM: async_pf: Fix #DF due to inject "Page not Present" and "Page Ready" exceptions simultaneously" Vitaly Kuznetsov
2020-05-05 1:22 ` Gavin Shan
2020-05-05 14:16 ` Vivek Goyal
2020-05-06 15:17 ` Vitaly Kuznetsov
2020-05-11 19:17 ` Vivek Goyal
2020-04-29 9:36 ` [PATCH RFC 2/6] KVM: x86: extend struct kvm_vcpu_pv_apf_data with token info Vitaly Kuznetsov
2020-05-04 23:52 ` Gavin Shan
2020-05-05 8:08 ` Vitaly Kuznetsov
2020-04-29 9:36 ` [PATCH RFC 3/6] KVM: x86: interrupt based APF page-ready event delivery Vitaly Kuznetsov
2020-04-29 10:54 ` Paolo Bonzini
2020-04-29 12:40 ` Vitaly Kuznetsov
2020-04-29 13:21 ` Paolo Bonzini
2020-04-29 21:27 ` Peter Xu
2020-04-30 8:31 ` Vitaly Kuznetsov
2020-04-30 13:28 ` Peter Xu
2020-04-30 13:49 ` Vitaly Kuznetsov
2020-05-05 15:22 ` Vivek Goyal
2020-04-29 9:36 ` [PATCH RFC 4/6] KVM: x86: acknowledgment mechanism for async pf page ready notifications Vitaly Kuznetsov
2020-04-29 17:28 ` Andy Lutomirski
2020-04-29 17:40 ` Paolo Bonzini
2020-04-30 0:45 ` Andy Lutomirski
2020-04-30 6:46 ` Paolo Bonzini
2020-04-30 6:49 ` Paolo Bonzini
2020-04-30 8:40 ` Vitaly Kuznetsov
2020-04-30 9:27 ` Paolo Bonzini
2020-04-30 11:33 ` Vitaly Kuznetsov
2020-04-30 11:43 ` Paolo Bonzini
2020-05-05 0:36 ` Gavin Shan
2020-05-05 8:16 ` Vitaly Kuznetsov
2020-05-05 8:51 ` Gavin Shan
2020-05-05 9:54 ` Paolo Bonzini
2020-04-29 9:36 ` [PATCH RFC 5/6] KVM: x86: announce KVM_FEATURE_ASYNC_PF_INT Vitaly Kuznetsov
2020-04-29 10:40 ` Peter Zijlstra
2020-04-29 9:36 ` [PATCH RFC 6/6] KVM: x86: Switch KVM guest to using interrupts for page ready APF delivery Vitaly Kuznetsov
2020-04-29 10:53 ` Paolo Bonzini
2020-04-29 12:44 ` Vitaly Kuznetsov
2020-04-29 13:19 ` Paolo Bonzini
2020-04-29 14:34 ` Vitaly Kuznetsov
2020-05-05 18:59 ` Vivek Goyal
2020-05-05 0:42 ` Gavin Shan
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=20200429093634.1514902-1-vkuznets@redhat.com \
--to=vkuznets@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--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 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.