From: Anish Moorthy <amoorthy@google.com>
To: seanjc@google.com, oliver.upton@linux.dev, kvm@vger.kernel.org,
kvmarm@lists.linux.dev
Cc: jthoughton@google.com, amoorthy@google.com, rananta@google.com
Subject: [PATCH v2 0/3] Set up KVM_EXIT_MEMORY_FAULTs when arm64/x86 stage-2 fault handlers fail
Date: Fri, 9 Aug 2024 20:51:55 +0000 [thread overview]
Message-ID: <20240809205158.1340255-1-amoorthy@google.com> (raw)
v2:
- x86 patch unchanged
- Arm patches merged [Oliver]
- Do memory fault exits in *all* EFAULT cases of user_mem_abort()
[Oliver]
- Add patch to tweak docs for KVM_CAP_MEMORY_FAULT_INFO
v1: https://lore.kernel.org/kvm/20240215235405.368539-1-amoorthy@google.com/
Anish Moorthy (3):
KVM: Documentation: Clarify docs for KVM_CAP_MEMORY_FAULT_INFO
KVM: x86: Do a KVM_MEMORY_FAULT EXIT when stage-2 fault handler
EFAULTs
KVM: arm64: Perform memory fault exits when stage-2 handler EFAULTs
Documentation/virt/kvm/api.rst | 7 ++++---
arch/arm64/kvm/arm.c | 1 +
arch/arm64/kvm/mmu.c | 11 ++++++++++-
arch/x86/kvm/mmu/mmu.c | 1 +
4 files changed, 16 insertions(+), 4 deletions(-)
base-commit: 332d2c1d713e232e163386c35a3ba0c1b90df83f
--
2.46.0.76.ge559c4bf1a-goog
next reply other threads:[~2024-08-09 20:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 20:51 Anish Moorthy [this message]
2024-08-09 20:51 ` [PATCH v2 1/3] KVM: Documentation: Clarify docs for KVM_CAP_MEMORY_FAULT_INFO Anish Moorthy
2024-08-16 20:53 ` Sean Christopherson
2024-08-09 20:51 ` [PATCH v2 2/3] KVM: x86: Do a KVM_MEMORY_FAULT EXIT when stage-2 fault handler EFAULTs Anish Moorthy
2024-08-16 20:57 ` Sean Christopherson
2024-08-09 20:51 ` [PATCH v2 3/3] KVM: arm64: Perform memory fault exits when stage-2 " Anish Moorthy
2024-08-12 7:51 ` Aneesh Kumar K.V
2024-08-13 14:26 ` Sean Christopherson
2024-08-14 8:02 ` Aneesh Kumar K.V
2024-08-14 14:49 ` Sean Christopherson
2024-08-16 21:22 ` Sean Christopherson
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=20240809205158.1340255-1-amoorthy@google.com \
--to=amoorthy@google.com \
--cc=jthoughton@google.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=oliver.upton@linux.dev \
--cc=rananta@google.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.