From: Ralf Baechle <ralf@linux-mips.org>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: Peter Horton <pdh@colonel-panic.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH Cobalt 1/1] 64-bit fix
Date: Tue, 17 Jan 2006 13:29:31 +0000 [thread overview]
Message-ID: <20060117132931.GB3336@linux-mips.org> (raw)
In-Reply-To: <20060116154543.GA26771@deprecation.cyrius.com>
On Mon, Jan 16, 2006 at 03:45:43PM +0000, Martin Michlmayr wrote:
> * Peter Horton <pdh@colonel-panic.org> [2005-04-14 19:59]:
> > This patch adds detection of broken 64-bit mode LL/SC on Cobalt units.
> > With this patch my Qube2700 boots a 64-bit build fine. The later units
> > have some problems with the Tulip driver.
>
> Ralf, is this patch appropriate? Can you please apply it or provide
> some feedback.
Runtime testing for that bug is fairly expensive as it adds a branch to
every instance of every type of atomic operation. So we really want
cpu_has_llsc to be a constant so the compiler can optimize that.
So I suggest something like this in cpu-feature-overrides.h:
[...]
/*
* R5000 has an interesting "restriction": ll(d)/sc(d)
* instructions to XKPHYS region simply do uncached bus
* requests. This breaks all the atomic bitops functions.
* so, for 64bit IP32 kernel we just don't use ll/sc.
* This does not affect luserland.
*/
#ifdef CONFIG_64BIT
#define cpu_has_llsc 0
#else
#define cpu_has_llsc 1
#endif
[...]
The probe would upset the IP27 cache coherency logic and crash them btw.
Ralf
prev parent reply other threads:[~2006-01-17 13:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 18:59 [PATCH Cobalt 1/1] 64-bit fix Peter Horton
2005-04-15 9:20 ` [OFF-TOPIC] Cobalt 64-bit, what for? (was: 64-bit fix) Dominique Quatravaux
2005-04-15 10:14 ` Ralf Baechle
2005-04-15 10:18 ` Dominic Sweetman
2005-04-15 10:25 ` Ralf Baechle
2006-01-16 15:45 ` [PATCH Cobalt 1/1] 64-bit fix Martin Michlmayr
2006-01-16 16:32 ` Jim Gifford
2006-01-16 16:50 ` Martin Michlmayr
2006-01-16 16:50 ` Martin Michlmayr
2006-01-17 13:51 ` Ralf Baechle
2006-01-17 14:23 ` Atsushi Nemoto
2006-01-18 17:59 ` Jim Gifford
2006-01-19 16:35 ` Atsushi Nemoto
2006-01-17 17:09 ` Jim Gifford
2006-01-17 13:29 ` Ralf Baechle [this message]
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=20060117132931.GB3336@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=pdh@colonel-panic.org \
--cc=tbm@cyrius.com \
/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