From: Marc Zyngier <maz@kernel.org>
To: Alexandru Elisei <alexandru.elisei@arm.com>
Cc: will@kernel.org, julien.thierry.kdev@gmail.com,
kvm@vger.kernel.org, oupton@kernel.org, fuad.tabba@linux.dev,
joey.gouly@arm.com, seiden@linux.ibm.com, suzuki.poulose@arm.com,
yuzenghui@huawei.com, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.linux.dev
Subject: Re: [PATCH kvmtool 0/7] Fix --vcpu-affinity
Date: Fri, 18 Sep 2026 13:22:17 +0100 [thread overview]
Message-ID: <86zexe4ume.wl-maz@kernel.org> (raw)
In-Reply-To: <20260917154932.193943-1-alexandru.elisei@arm.com>
On Thu, 17 Sep 2026 16:49:25 +0100,
Alexandru Elisei <alexandru.elisei@arm.com> wrote:
>
> Tested on an Orion board and a x86 machine. On the x86 machine, there's was this
> one thread called 'kvm-nx-lpage-re' which had affinity of the VCPUs, but I
> couldn't figure out where it was created. I grep'ed for each part of the name in
> the source node, no luck. I used strace, and couldn't see a clone call that
> returned the corresponding pid. Any clues would be appreciated.
This is a KVM internal thread, from what I can tell. See
arch/x86/kvm/mmu/mmu.c::kvm_mmu_start_lpage_recovery().
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-09-18 12:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 15:49 [PATCH kvmtool 0/7] Fix --vcpu-affinity Alexandru Elisei
2026-09-17 15:49 ` [PATCH kvmtool 1/7] arm64: Pass the number of elements as the first argument to calloc() Alexandru Elisei
2026-09-17 15:49 ` [PATCH kvmtool 2/7] arm64: Consistently treat vcpu_affinity_cpuset as dynamically allocated Alexandru Elisei
2026-09-17 15:49 ` [PATCH kvmtool 3/7] arm64: Free the temporary cpumask in vcpu_affinity_parser() Alexandru Elisei
2026-09-17 15:49 ` [PATCH kvmtool 4/7] arm64/pmu: Consider kvmtool's affinity when searching for a PMU Alexandru Elisei
2026-09-17 15:49 ` [PATCH kvmtool 5/7] Correctly apply --vcpu-affinity to the VCPU threads Alexandru Elisei
2026-09-17 15:49 ` [RFC PATCH kvmtool 6/7] Introduce kvm_create_thread() Alexandru Elisei
2026-09-17 15:49 ` [RFC PATCH kvmtool 7/7] Don't apply --vcpu-affinity to threads spawned from VCPUs Alexandru Elisei
2026-09-18 12:22 ` Marc Zyngier [this message]
2026-09-21 8:59 ` [PATCH kvmtool 0/7] Fix --vcpu-affinity Alexandru Elisei
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=86zexe4ume.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oupton@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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