From: Tao Cui <cui.tao@linux.dev>
To: maobibo@loongson.cn
Cc: chenhuacai@kernel.org, cui.tao@linux.dev, cuitao@kylinos.cn,
kernel@xen0n.name, kvm@vger.kernel.org,
loongarch@lists.linux.dev, zhaotianrui@loongson.cn
Subject: Re: [PATCH v4 3/3] KVM: selftests: loongarch: Add PV TLB flush performance test
Date: Tue, 16 Jun 2026 23:42:31 +0800 [thread overview]
Message-ID: <20260616154231.10982-1-cui.tao@linux.dev> (raw)
In-Reply-To: <4efcc81b-bf7e-4d78-ba82-9f4590673486@loongson.cn>
From: Tao Cui <cuitao@kylinos.cn>
Thanks, and I share the stability concern. I don't want to land something
that adds risk for a feature that isn't clearly earning its place yet.
> Do you have real workload to show the benefits of the PV TLB flush,
> and which TLB APIs should be hooked.
Completely fair, and to be upfront I don't have a large-scale real-world
workload to point to yet. So my plan is to build a set of local test
scripts that simulate as many usage scenarios as possible: mmap/fork-heavy
paths, kernel-range flushes, and an overcommitted setup where vCPU
preemption is frequent. I'll report the IPI and TLB-flush overhead with
and without the feature, broken down per flush API. The coverage is
synthetic rather than a single flagship workload, but hopefully it can at
least give us a rough, preliminary sense of whether the feature is worth
pursuing.
Thanks,
Tao
prev parent reply other threads:[~2026-06-16 15:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 8:21 [PATCH v4 0/3] LoongArch: KVM: Add PV TLB flush support Tao Cui
2026-06-15 8:21 ` [PATCH v4 1/3] LoongArch: KVM: Add PV TLB flush support via steal-time shared memory Tao Cui
2026-06-15 8:35 ` sashiko-bot
2026-06-16 1:03 ` Bibo Mao
2026-06-16 14:14 ` Tao Cui
2026-06-15 8:21 ` [PATCH v4 2/3] LoongArch: KVM: Implement guest-side PV TLB flush Tao Cui
2026-06-16 1:14 ` Bibo Mao
2026-06-16 15:08 ` Tao Cui
2026-06-16 2:19 ` Bibo Mao
2026-06-15 8:21 ` [PATCH v4 3/3] KVM: selftests: loongarch: Add PV TLB flush performance test Tao Cui
2026-06-15 8:29 ` sashiko-bot
2026-06-15 9:24 ` Bibo Mao
2026-06-16 15:42 ` Tao Cui [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=20260616154231.10982-1-cui.tao@linux.dev \
--to=cui.tao@linux.dev \
--cc=chenhuacai@kernel.org \
--cc=cuitao@kylinos.cn \
--cc=kernel@xen0n.name \
--cc=kvm@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 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.