From: Huacai Chen <chenhuacai@kernel.org>
To: Bibo Mao <maobibo@loongson.cn>
Cc: Tianrui Zhao <zhaotianrui@loongson.cn>,
WANG Xuerui <kernel@xen0n.name>,
kvm@vger.kernel.org, loongarch@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] LoongArch: KVM: Do not flush tlb if HW PTW supported
Date: Sat, 17 May 2025 17:41:50 +0800 [thread overview]
Message-ID: <CAAhV-H4hry0LfUwbPmURc+bbcAXG13wO2cHfdjcoijeezNhO5Q@mail.gmail.com> (raw)
In-Reply-To: <20250427024505.129383-1-maobibo@loongson.cn>
Applied, thanks.
Huacai
On Sun, Apr 27, 2025 at 10:45 AM Bibo Mao <maobibo@loongson.cn> wrote:
>
> With HW PTW supported, stale TLB is not added if page fault happens. With
> EXCCODE_TLBM exception, stale TLB may exist because last read access, tlb
> flush operation is necessary with EXCCODE_TLBM exception, and not necessary
> with other memory page fault exceptions.
>
> With SW PTW supported, invalid TLB is added in TLB refill exception.
> TLB flush operation is necessary with all page fault exceptions.
>
> ---
> v1 ... v2:
> 1. Add kernel doc notation since new parameter ecode is added, which is
> reported from LKP.
> ---
>
> Bibo Mao (2):
> LoongArch: KVM: Add parameter exception code with exception handler
> LoongArch: KVM: Do not flush tlb if HW PTW supported
>
> arch/loongarch/include/asm/kvm_host.h | 2 +-
> arch/loongarch/include/asm/kvm_vcpu.h | 2 +-
> arch/loongarch/kvm/exit.c | 37 ++++++++++++++-------------
> arch/loongarch/kvm/mmu.c | 18 ++++++++++---
> 4 files changed, 35 insertions(+), 24 deletions(-)
>
>
> base-commit: 5bc1018675ec28a8a60d83b378d8c3991faa5a27
> --
> 2.39.3
>
prev parent reply other threads:[~2025-05-17 9:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 2:45 Bibo Mao
2025-04-27 2:45 ` [PATCH v2 1/2] LoongArch: KVM: Add parameter exception code with exception handler Bibo Mao
2025-04-27 2:45 ` [PATCH v2 2/2] LoongArch: KVM: Do not flush tlb if HW PTW supported Bibo Mao
2025-05-17 9:41 ` Huacai Chen [this message]
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=CAAhV-H4hry0LfUwbPmURc+bbcAXG13wO2cHfdjcoijeezNhO5Q@mail.gmail.com \
--to=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=maobibo@loongson.cn \
--cc=zhaotianrui@loongson.cn \
/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
all inboxes | Powered by JetHome®