From: 毛碧波 <maobibo@loongson.cn>
To: jiaxun.yang@flygoat.com
Cc: "WANG Xuerui" <git@xen0n.name>, linux-mips@vger.kernel.org
Subject: Re: Re: [PATCH v3 0/1] CPUCFG emulation on older Loongson64 cores
Date: Fri, 22 May 2020 22:14:02 +0800 (GMT+08:00) [thread overview]
Message-ID: <42b4126b.f787.1723cbbd44e.Coremail.maobibo@loongson.cn> (raw)
In-Reply-To: <B61EB510-C793-492B-8A3F-4C340190DC21@flygoat.com>
> -----原始邮件-----
> 发件人: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
> 发送时间: 2020-05-22 20:57:33 (星期五)
> 收件人: "毛碧波" <maobibo@loongson.cn>, "WANG Xuerui" <git@xen0n.name>
> 抄送: linux-mips@vger.kernel.org
> 主题: Re: [PATCH v3 0/1] CPUCFG emulation on older Loongson64 cores
>
>
>
> 于 2020年5月22日 GMT+08:00 下午8:06:01, "毛碧波" <maobibo@loongson.cn> 写到:
> >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?
>
> Application can firstly probe if CPUCFG is supported by kernel & hardware
> by fork a thread and catch SIGILL signal or HWCAP.
> Then decide use legacy methods or CPUCFG to probe other features.
>
> Similar method have been proofed on Arm.
Sure, if that works, what is the purpose of this patch? Do we need cpucfg
simulation on older machine since there is proper method already?
> --
> Jiaxun Yang
</maobibo@loongson.cn></git@xen0n.name></maobibo@loongson.cn></jiaxun.yang@flygoat.com>
next prev parent reply other threads:[~2020-05-22 14:14 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 ` [PATCH v3 0/1] CPUCFG emulation " 毛碧波
2020-05-22 12:57 ` Jiaxun Yang
2020-05-22 14:14 ` 毛碧波 [this message]
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=42b4126b.f787.1723cbbd44e.Coremail.maobibo@loongson.cn \
--to=maobibo@loongson.cn \
--cc=git@xen0n.name \
--cc=jiaxun.yang@flygoat.com \
--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