From: Aurelien Jarno <aurelien@aurel32.net>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Robert Millan <rmh@gnu.org>, Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] Enable AT_PLATFORM for Loongson 2F CPU
Date: Thu, 04 Nov 2010 18:33:24 +0100 [thread overview]
Message-ID: <4CD2EE64.5060404@aurel32.net> (raw)
In-Reply-To: <4CD2E2F7.4090701@caviumnetworks.com>
David Daney a écrit :
> On 11/04/2010 05:18 AM, Robert Millan wrote:
>> Please consider this patch, it enables AT_PLATFORM for Loongson 2F CPU.
>>
>>
> [...]
>> diff --git a/arch/mips/kernel/cpu-probe.c b/arch/mips/kernel/cpu-probe.c
>> index 71620e1..504f3b1 100644
>> --- a/arch/mips/kernel/cpu-probe.c
>> +++ b/arch/mips/kernel/cpu-probe.c
>> @@ -614,6 +614,8 @@ static inline void cpu_probe_legacy(struct cpuinfo_mips *c, unsigned int cpu)
>> case PRID_IMP_LOONGSON2:
>> c->cputype = CPU_LOONGSON2;
>> __cpu_name[cpu] = "ICT Loongson-2";
>> + if (cpu == 0)
>> + __elf_platform = "loongson-2f";
>> c->isa_level = MIPS_CPU_ISA_III;
>> c->options = R4K_OPTS |
>> MIPS_CPU_FPU | MIPS_CPU_LLSC |
>
> This doesn't look right to me.
>
> You are claiming that all loongson2 are loongson-2f. Is that really
> true? Or are there other types of loongson2 that are not loongson-2f?
>
> You need to be very careful here. This is part of the userspace ABI, so
> if you get it wrong, you are stuck with it forever.
>
> One question you didn't address is why userspace would care that it is
> running on exactly "loongson-2f" instead of just mips4.
>
> The __elf_platform gets converted to a directory name by ld.so, so you
> may want to choose a value without '-' in it.
>
> My suggestion would be to set "loongson2" for the generic CPU_LOONGSON2,
> and if there is a good reason for it, "loongson2f" for the 'f' variant.
>
You should definitely define here loongson-2e and loongson-2f
separately. They have the same instruction set, but different opcodes
for the loongson specific instructions, hence they are not compatible.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2010-11-04 17:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 12:18 [PATCH] Enable AT_PLATFORM for Loongson 2F CPU Robert Millan
2010-11-04 16:44 ` David Daney
2010-11-04 17:33 ` Aurelien Jarno [this message]
2010-11-04 18:43 ` Robert Millan
2010-11-04 19:11 ` David Daney
2010-11-04 19:29 ` Ralf Baechle
2010-11-07 12:30 ` Robert Millan
2010-11-08 19:13 ` David Daney
2010-11-08 22:27 ` Robert Millan
2010-11-08 22:50 ` David Daney
2010-11-08 23:02 ` Robert Millan
2010-11-09 9:48 ` wu zhangjin
2010-11-09 12:24 ` Robert Millan
2010-11-09 15:40 ` Ralf Baechle
2010-11-11 14:47 ` Robert Millan
2010-11-15 23:50 ` Robert Millan
2010-11-15 23:59 ` David Daney
2010-11-22 12:44 ` Robert Millan
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=4CD2EE64.5060404@aurel32.net \
--to=aurelien@aurel32.net \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=rmh@gnu.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