From: Sean Christopherson <seanjc@google.com>
To: Anup Patel <anup.patel@wdc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Cc: Atish Patra <atish.patra@wdc.com>,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>
Subject: [PATCH 0/2] KVM: RISC-V: MMU bug fix and cleanup
Date: Thu, 4 Nov 2021 16:41:05 +0000 [thread overview]
Message-ID: <20211104164107.1291793-1-seanjc@google.com> (raw)
Bug fix and a cleanup for things I noticed by inspection when working on
the scalable memslots series. Regarding the fix, unless there's a magic
unmapping hiding in the corners of the MMU, RISC-V completely fails to
handle memslot DELETE or MOVE.
Compile tested only.
Sean Christopherson (2):
KVM: RISC-V: Unmap stage2 mapping when deleting/moving a memslot
KVM: RISC-V: Use common KVM implementation of MMU memory caches
arch/riscv/include/asm/kvm_host.h | 10 +----
arch/riscv/include/asm/kvm_types.h | 2 +-
arch/riscv/kvm/mmu.c | 70 ++++++++----------------------
arch/riscv/kvm/vcpu.c | 5 ++-
4 files changed, 22 insertions(+), 65 deletions(-)
--
2.34.0.rc0.344.g81b53c2807-goog
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2021-11-04 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 16:41 Sean Christopherson [this message]
2021-11-04 16:41 ` [PATCH 1/2] KVM: RISC-V: Unmap stage2 mapping when deleting/moving a memslot Sean Christopherson
2021-11-16 14:17 ` Anup Patel
2021-11-04 16:41 ` [PATCH 2/2] KVM: RISC-V: Use common KVM implementation of MMU memory caches Sean Christopherson
2021-11-23 5:14 ` Anup Patel
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=20211104164107.1291793-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=anup.patel@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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