From: 毛碧波 <maobibo@loongson.cn>
To: "WANG Xuerui" <git@xen0n.name>
Cc: linux-mips@vger.kernel.org
Subject: Re: [PATCH v3 0/1] CPUCFG emulation on older Loongson64 cores
Date: Fri, 22 May 2020 20:06:01 +0800 (GMT+08:00) [thread overview]
Message-ID: <4701b93c.f740.1723c46a295.Coremail.maobibo@loongson.cn> (raw)
In-Reply-To: <20200521181403.6078-1-git@xen0n.name>
Sorry for late reponse.
I just want to know how to solve compatibility on older kernel.
It is ok to run user application with cpucfg instr on new kernel with this
patch, however what if the application is running on older kernel without
cpucfg simulation?
regards
bibo,mao
> -----原始邮件-----
> 发件人: "WANG Xuerui" <git@xen0n.name>
> 发送时间: 2020-05-22 02:14:02 (星期五)
> 收件人: linux-mips@vger.kernel.org
> 抄送: "WANG Xuerui" <git@xen0n.name>
> 主题: [PATCH v3 0/1] CPUCFG emulation on older Loongson64 cores
>
> This patch brings the CPUCFG instruction to older Loongson64 cores,
> enabling a unified way to query processor characteristics on Loongson64
> systems. Previous question of how to best integrate machtype-specific
> and machtype-agnostic cpu probe logic is resolved. (thanks Thomas for
> reviewing!)
>
> Tested on Loongson-3A3000.
>
> Also, to aid userspace in determining CPUCFG availability without having
> to handle SIGILL or parse /proc/cpuinfo, a new HWCAP flag is to be added
> in a later patch. I am waiting for consensus before implementing this,
> as it would be part of userspace ABI.
>
> v3:
> - Fixed build on !CONFIG_MACH_LOONGSON64
> - Refactored to minimize intrusion to machtype-agnostic cpu probe logic
> - Minor tweaks to comment and Kconfig wording
> - Dropped Reviewed-by and Tested-by from Jiaxun as the code is
> refactored significantly
>
> v2:
> - Fixed one more typo in loongson_regs.h
> - Merged simulate_loongson3_csr and simulate_loongson3_csr_cpucfg into
> one (simulate_loongson3_cpucfg), per Huacai's suggestion
>
> WANG Xuerui (1):
> MIPS: emulate CPUCFG instruction on older Loongson64 cores
>
> arch/mips/Kconfig | 12 +
> arch/mips/include/asm/cpu-info.h | 9 +
> .../include/asm/mach-loongson64/cpucfg-emul.h | 65 ++++++
> arch/mips/kernel/cpu-probe.c | 9 +
> arch/mips/kernel/traps.c | 45 ++++
> arch/mips/loongson64/Makefile | 1 +
> arch/mips/loongson64/cpucfg-emul.c | 217 ++++++++++++++++++
> 7 files changed, 358 insertions(+)
> create mode 100644 arch/mips/include/asm/mach-loongson64/cpucfg-emul.h
> create mode 100644 arch/mips/loongson64/cpucfg-emul.c
>
> --
> 2.21.0
</git@xen0n.name></git@xen0n.name>
next prev parent reply other threads:[~2020-05-22 12:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 18:14 [PATCH v3 0/1] CPUCFG emulation on older Loongson64 cores WANG Xuerui
2020-05-21 18:14 ` [PATCH v3 1/1] MIPS: emulate CPUCFG instruction " WANG Xuerui
2020-05-22 3:34 ` Jiaxun Yang
2020-05-22 4:39 ` Huacai Chen
2020-05-23 4:07 ` WANG Xuerui
2020-05-22 12:06 ` 毛碧波 [this message]
2020-05-22 12:57 ` [PATCH v3 0/1] CPUCFG emulation " Jiaxun Yang
2020-05-22 14:14 ` 毛碧波
2020-05-22 14:34 ` Jiaxun Yang
2020-05-23 2:10 ` maobibo
2020-05-23 2:30 ` Jiaxun Yang
2020-05-23 2:48 ` WANG Xuerui
2020-05-23 3:10 ` WANG Xuerui
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=4701b93c.f740.1723c46a295.Coremail.maobibo@loongson.cn \
--to=maobibo@loongson.cn \
--cc=git@xen0n.name \
--cc=linux-mips@vger.kernel.org \
/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