From: Bibo Mao <maobibo@loongson.cn>
To: liushuyu <liushuyu@aosc.io>, WANG Xuerui <kernel@xen0n.name>,
Huacai Chen <chenhuacai@kernel.org>
Cc: "Kexy Biscuit" <kexybiscuit@aosc.io>,
"Mingcong Bai" <jeffbai@aosc.io>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Tianrui Zhao" <zhaotianrui@loongson.cn>,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
kvm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
linux-riscv@lists.infradead.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH 1/1] KVM: Add KVM_GET_REG_LIST ioctl for LoongArch
Date: Mon, 26 Jan 2026 11:57:31 +0800 [thread overview]
Message-ID: <29565e27-f153-c2c5-cbc3-e0457d45f094@loongson.cn> (raw)
In-Reply-To: <972430be-d2f3-49b6-851b-a057ddfcafec@aosc.io>
On 2026/1/26 上午11:38, liushuyu wrote:
> Hi Bibo,
>>
>>
>> On 2026/1/25 下午1:43, Zixing Liu wrote:
>>> This ioctl can be used by userspace applications to determine which
>>> (special) registers are get/set-able.
>>>
>>> This can be very useful for cross-platform VMMs so that they do not have
>>> to hardcode register indices for each supported architectures.
>>>
>>> Signed-off-by: Zixing Liu <liushuyu@aosc.io>
>>> ---
>>>
>>> For example, this ioctl could be used by rust-vmm/rust-kvm or maybe
>>> VirtualBox-kvm in the future.
>>>
>>> Documentation/virt/kvm/api.rst | 2 +-
>>> arch/loongarch/kvm/vcpu.c | 69 ++++++++++++++++++++++++++++++++++
>>> 2 files changed, 70 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/Documentation/virt/kvm/api.rst
>>> b/Documentation/virt/kvm/api.rst
>>> index 01a3abef8abb..f46dd8be282f 100644
>>> --- a/Documentation/virt/kvm/api.rst
>>> +++ b/Documentation/virt/kvm/api.rst
>>> @@ -3603,7 +3603,7 @@ VCPU matching underlying host.
>>> ---------------------
>>> :Capability: basic
>>> -:Architectures: arm64, mips, riscv, x86 (if KVM_CAP_ONE_REG)
>>> +:Architectures: arm64, loongarch, mips, riscv, x86 (if KVM_CAP_ONE_REG)
>>> :Type: vcpu ioctl
>>> :Parameters: struct kvm_reg_list (in/out)
>>> :Returns: 0 on success; -1 on error
>>> diff --git a/arch/loongarch/kvm/vcpu.c b/arch/loongarch/kvm/vcpu.c
>>> index 656b954c1134..b884eb9c76aa 100644
>>> --- a/arch/loongarch/kvm/vcpu.c
>>> +++ b/arch/loongarch/kvm/vcpu.c
>>> @@ -1186,6 +1186,57 @@ static int kvm_loongarch_vcpu_set_attr(struct
>>> kvm_vcpu *vcpu,
>>> return ret;
>>> }
>>> +static unsigned long kvm_loongarch_num_lbt_regs(void)
>>> +{
>>> + /* +1 for the LBT_FTOP flag (inside arch.fpu) */
>>> + return sizeof(struct loongarch_lbt) / sizeof(unsigned long) + 1;
>>> +}
>>> +
>>> +static unsigned long kvm_loongarch_num_regs(struct kvm_vcpu *vcpu)
>>> +{
>>> + /* +1 for the KVM_REG_LOONGARCH_COUNTER register */
>>> + unsigned long res = CSR_MAX_NUMS + KVM_MAX_CPUCFG_REGS + 1;
>>> +
>>> + if (kvm_guest_has_lbt(&vcpu->arch))
>>> + res += kvm_loongarch_num_lbt_regs();
>>> +
>>> + return res;
>>> +}
>>> +
>>> +static int kvm_loongarch_copy_reg_indices(struct kvm_vcpu *vcpu,
>>> + u64 __user *uindices)
>>> +{
>>> + u64 reg;
>>> + unsigned int i;
>>> +
>>> + for (i = 0; i < CSR_MAX_NUMS; i++) {
>>> + reg = KVM_IOC_CSRID(i);
>>> + if (put_user(reg, uindices++))
>>> + return -EFAULT;
>>> + }
>> CSR_MAX_NUMS is max number of accessible CSR registers, instead only
>> part of them is used by vCPU model. By my understanding, there will be
>> no much meaning if CSR_MAX_NUMS is returned. And I think it will be
>> better if real CSR register id and number is returned.
>>
> Did you mean we should only return the CSR registers initialized in this
> function
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/loongarch/kvm/main.c?id=63804fed149a6750ffd28610c5c1c98cce6bd377#n48
> ?
>
> That looks like a very large list and the values of the register IDs are
> not fully continuous. If that is the case, how do we maintain the
> get/set-able CSR register list?
It will be better if CSR register list can be categorized, for example
with LoongArch CPU manual CSR register is split into 8 types from
chapter 7.4 -- 7.11
At the beginning, there is big array with size CSR_MAX_NUMS without any
category, it can be fine-gained in late.
Regards
Bibo Mao
>
>> Regards
>> Bibo Mao
>>> +
>>> + for (i = 0; i < KVM_MAX_CPUCFG_REGS; i++) {
>>> + reg = KVM_IOC_CPUCFG(i);
>>> + if (put_user(reg, uindices++))
>>> + return -EFAULT;
>>> + }
>>> +
>>> + reg = KVM_REG_LOONGARCH_COUNTER;
>>> + if (put_user(reg, uindices++))
>>> + return -EFAULT;
>>> +
>>> + if (!kvm_guest_has_lbt(&vcpu->arch))
>>> + return 0;
>>> +
>>> + for (i = 1; i <= kvm_loongarch_num_lbt_regs(); i++) {
>>> + reg = (KVM_REG_LOONGARCH_LBT | KVM_REG_SIZE_U64 | i);
>>> + if (put_user(reg, uindices++))
>>> + return -EFAULT;
>>> + }
>>> +
>>> + return 0;
>>> +}
>>> +
>>> long kvm_arch_vcpu_ioctl(struct file *filp,
>>> unsigned int ioctl, unsigned long arg)
>>> {
>>> @@ -1251,6 +1302,24 @@ long kvm_arch_vcpu_ioctl(struct file *filp,
>>> r = kvm_loongarch_vcpu_set_attr(vcpu, &attr);
>>> break;
>>> }
>>> + case KVM_GET_REG_LIST: {
>>> + struct kvm_reg_list __user *user_list = argp;
>>> + struct kvm_reg_list reg_list;
>>> + unsigned n;
>>> +
>>> + r = -EFAULT;
>>> + if (copy_from_user(®_list, user_list, sizeof(reg_list)))
>>> + break;
>>> + n = reg_list.n;
>>> + reg_list.n = kvm_loongarch_num_regs(vcpu);
>>> + if (copy_to_user(user_list, ®_list, sizeof(reg_list)))
>>> + break;
>>> + r = -E2BIG;
>>> + if (n < reg_list.n)
>>> + break;
>>> + r = kvm_loongarch_copy_reg_indices(vcpu, user_list->reg);
>>> + break;
>>> + }
>>> default:
>>> r = -ENOIOCTLCMD;
>>> break;
>>>
>>
> Thanks,
> Zixing
>
next prev parent reply other threads:[~2026-01-26 4:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 5:43 Zixing Liu
2026-01-26 2:09 ` Bibo Mao
2026-01-26 3:38 ` liushuyu
2026-01-26 3:57 ` Bibo Mao [this message]
2026-01-26 4:22 ` liushuyu
2026-01-26 8:36 ` Bibo Mao
2026-01-26 8:54 ` liushuyu
2026-01-26 9:35 ` Bibo Mao
2026-01-26 10:03 ` liushuyu
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=29565e27-f153-c2c5-cbc3-e0457d45f094@loongson.cn \
--to=maobibo@loongson.cn \
--cc=a.hindborg@kernel.org \
--cc=alex@ghiti.fr \
--cc=aliceryhl@google.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=jeffbai@aosc.io \
--cc=kernel@xen0n.name \
--cc=kexybiscuit@aosc.io \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=liushuyu@aosc.io \
--cc=loongarch@lists.linux.dev \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=pjw@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--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®