From: maobibo <maobibo@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Huacai Chen <chenhuacai@kernel.org>
Cc: Tianrui Zhao <zhaotianrui@loongson.cn>,
Juergen Gross <jgross@suse.com>,
Paolo Bonzini <pbonzini@redhat.com>,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
virtualization@lists.linux.dev, kvm@vger.kernel.org
Subject: Re: [PATCH v5 3/6] LoongArch: KVM: Add cpucfg area for kvm hypervisor
Date: Tue, 27 Feb 2024 17:52:33 +0800 [thread overview]
Message-ID: <e04a527b-2d9d-cfcd-e6ed-e8bd390649dd@loongson.cn> (raw)
In-Reply-To: <f1ba53fd2a99949187ca392c6d4488d3d5aeaf88.camel@xry111.site>
On 2024/2/27 下午5:05, Xi Ruoyao wrote:
> On Tue, 2024-02-27 at 15:09 +0800, maobibo wrote:
>
>> It is difficult to find an area unused by HW for CSR method since the
>> small CSR ID range.
>
> We may use IOCSR instead. In kernel/cpu-probe.c there are already some
> IOCSR reads.
yes, IOCSR can be used and one IOCSR area will be reserved for software.
In general CSR/CPUCFG is to describe CPU features and IOCSR is to
describe board/device features.
CSR area is limited to 16K, it is difficult for HW guys to reserve
special area for software usage. IOCSR/CPUCFG is possible however.
Regards
Bibo Mao
>
>> It is difficult to find an area unused by HW for CSR method since the
>> small CSR ID range. However it is easy for cpucfg. Here I doubt whether
>> you really know about LoongArch LVZ.
>
> It's unfair to accuse the others for not knowing about LVZ considering
> the lack of public documentation.
>
next prev parent reply other threads:[~2024-02-27 9:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 3:27 [PATCH v5 0/6] LoongArch: Add pv ipi support on LoongArch VM Bibo Mao
2024-02-22 3:27 ` [PATCH v5 1/6] LoongArch/smp: Refine some ipi functions on LoongArch platform Bibo Mao
2024-02-22 3:27 ` [PATCH v5 2/6] LoongArch: KVM: Add hypercall instruction emulation support Bibo Mao
2024-02-22 3:28 ` [PATCH v5 3/6] LoongArch: KVM: Add cpucfg area for kvm hypervisor Bibo Mao
2024-02-24 9:13 ` Huacai Chen
2024-02-26 2:04 ` maobibo
2024-02-26 5:25 ` WANG Xuerui
2024-02-26 8:00 ` maobibo
2024-02-26 8:07 ` WANG Xuerui
2024-02-26 6:12 ` Huacai Chen
2024-02-26 8:04 ` maobibo
2024-02-26 20:02 ` Jiaxun Yang
2024-02-27 3:14 ` maobibo
2024-02-27 5:23 ` Jiaxun Yang
2024-02-27 7:09 ` maobibo
2024-02-27 9:05 ` Xi Ruoyao
2024-02-27 9:52 ` maobibo [this message]
2024-02-27 9:10 ` WANG Xuerui
2024-02-27 10:12 ` maobibo
2024-02-27 10:19 ` WANG Xuerui
2024-02-27 14:57 ` Huacai Chen
2024-03-02 2:57 ` maobibo
2024-02-26 2:07 ` maobibo
2024-02-22 3:28 ` [PATCH v5 4/6] LoongArch: Add paravirt interface for guest kernel Bibo Mao
2024-02-24 9:15 ` Huacai Chen
2024-02-26 2:27 ` maobibo
2024-02-22 3:28 ` [PATCH v5 5/6] LoongArch: KVM: Add vcpu search support from physical cpuid Bibo Mao
2024-02-22 3:28 ` [PATCH v5 6/6] LoongArch: Add pv ipi support on LoongArch system Bibo Mao
2024-02-24 9:19 ` Huacai Chen
2024-02-26 2:30 ` maobibo
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=e04a527b-2d9d-cfcd-e6ed-e8bd390649dd@loongson.cn \
--to=maobibo@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=jgross@suse.com \
--cc=jiaxun.yang@flygoat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xry111@xry111.site \
--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®