From: Tao Cui <cui.tao@linux.dev>
To: zhaotianrui@loongson.cn, maobibo@loongson.cn
Cc: chenhuacai@kernel.org, kernel@xen0n.name, kvm@vger.kernel.org,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
cui.tao@linux.dev
Subject: [PATCH] LoongArch: KVM: Advertise already-supported capabilities
Date: Tue, 4 Aug 2026 16:26:04 +0800 [thread overview]
Message-ID: <20260804082604.178092-1-cui.tao@linux.dev> (raw)
Several LoongArch KVM features are fully implemented but were never
reported through their standard KVM_CHECK_EXTENSION probes, so userspace
cannot discover them and either ignores them or takes a slower path.
Advertise the ones that already work:
- KVM_CAP_STEAL_TIME: steal time is fully implemented (host-side
record plus guest paravirt), gated on kvm_pvtime_supported().
- KVM_CAP_IRQFD_RESAMPLE: the resampler is generic code backed by the
in-kernel irqchip; advertise it so userspace can use irqfd with
resample for level-triggered interrupts.
- KVM_CAP_VM_GPA_BITS: the guest physical address width is already
computed as BIT(cpu_vabits), so return cpu_vabits directly.
- KVM_CAP_VCPU_ATTRIBUTES: per-vCPU device-attribute ioctls are
implemented (CPUCFG, PVTIME control); advertise the discovery cap.
This adds no new functionality; it only makes existing features
discoverable via the standard probe.
Signed-off-by: Tao Cui <cui.tao@linux.dev>
---
arch/loongarch/kvm/vm.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/loongarch/kvm/vm.c b/arch/loongarch/kvm/vm.c
index 1317c718f896..d7dd08d9be5b 100644
--- a/arch/loongarch/kvm/vm.c
+++ b/arch/loongarch/kvm/vm.c
@@ -120,8 +120,10 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
case KVM_CAP_READONLY_MEM:
case KVM_CAP_IMMEDIATE_EXIT:
case KVM_CAP_IOEVENTFD:
+ case KVM_CAP_IRQFD_RESAMPLE:
case KVM_CAP_MP_STATE:
case KVM_CAP_SET_GUEST_DEBUG:
+ case KVM_CAP_VCPU_ATTRIBUTES:
r = 1;
break;
case KVM_CAP_NR_VCPUS:
@@ -136,6 +138,12 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
case KVM_CAP_NR_MEMSLOTS:
r = KVM_USER_MEM_SLOTS;
break;
+ case KVM_CAP_STEAL_TIME:
+ r = kvm_pvtime_supported();
+ break;
+ case KVM_CAP_VM_GPA_BITS:
+ r = cpu_vabits;
+ break;
default:
r = 0;
break;
next reply other threads:[~2026-08-04 8:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 8:26 Tao Cui [this message]
2026-08-04 8:40 ` [PATCH] LoongArch: KVM: Advertise already-supported capabilities sashiko-bot
2026-08-05 2:36 ` Bibo Mao
2026-08-05 5:18 ` Tao Cui
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=20260804082604.178092-1-cui.tao@linux.dev \
--to=cui.tao@linux.dev \
--cc=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 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.