From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>
Cc: "Jonas Gorski" <jonas.gorski@gmail.com>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] MIPS: Introduce config options for LLSC availability
Date: Thu, 20 Jun 2024 17:30:48 +0100 [thread overview]
Message-ID: <743a2297-ff4a-4cb3-ae61-8cd4956aa565@app.fastmail.com> (raw)
In-Reply-To: <ZnRThFlqqyDEprGz@alpha.franken.de>
在2024年6月20日六月 下午5:06，Thomas Bogendoerfer写道：
[...]
> do you have an user manual stating that the R5k bug is fixed on this CPUs ?
I actually investigated R5500 a little bit.
There is no explicit document mentioned this bug is fixed on R5500, but it's not
mentioned on "VR Series 64-/32-Bit Microprocessor Programming Guide" [1] either,
while some other hardware limitations are mentioned in that guide.
Plus EMMA platform, which was removed form the kernel, doesn't have
cpu-feature-overrides.h. This means that the platform was running with LLSC
enabled.
So I think this CPU is not affected.
[1]: https://repo.oss.cipunited.com/archives/docs/NEC/U10710EJ5V0AN00.pdf
>
> Thomas.
>
> --
> Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
> good idea. [ RFC1925, 2.3 ]
--
- Jiaxun
next prev parent reply other threads:[~2024-06-20 16:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 9:53 [PATCH v2 0/4] MIPS: Enable ARCH_SUPPORTS_ATOMIC_RMW Jiaxun Yang
2024-06-12 9:53 ` [PATCH v2 1/4] MIPS: Introduce WAR_4KC_LLSC config option Jiaxun Yang
2024-06-12 9:53 ` [PATCH v2 2/4] MIPS: Introduce config options for LLSC availability Jiaxun Yang
2024-06-20 16:06 ` Thomas Bogendoerfer
2024-06-20 16:30 ` Jiaxun Yang [this message]
2024-06-20 17:41 ` Thomas Bogendoerfer
2024-06-21 0:00 ` Maciej W. Rozycki
2024-06-21 10:45 ` Jiaxun Yang
2024-06-21 13:57 ` Maciej W. Rozycki
2024-06-21 15:21 ` Jiaxun Yang
2024-06-21 17:40 ` Maciej W. Rozycki
2024-06-21 20:31 ` Thomas Bogendoerfer
2024-06-12 9:53 ` [PATCH v2 3/4] MIPS: Select ARCH_SUPPORTS_ATOMIC_RMW when possible Jiaxun Yang
2024-06-12 9:53 ` [PATCH v2 4/4] MIPS: Select ARCH_HAVE_NMI_SAFE_CMPXCHG " Jiaxun Yang
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=743a2297-ff4a-4cb3-ae61-8cd4956aa565@app.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=tsbogend@alpha.franken.de \
/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