From: Keith Owens <kaos@ocs.com.au>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.4.9-ac12 ppc ftr_fixup
Date: Mon, 27 Aug 2001 13:13:42 +1000 [thread overview]
Message-ID: <21473.998882022@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 26 Aug 2001 20:04:04 MST." <20010826200404.E1481@cpe-24-221-152-185.az.sprintbbd.net>
On Sun, 26 Aug 2001 20:04:04 -0700,
Tom Rini <trini@kernel.crashing.org> wrote:
>On Mon, Aug 27, 2001 at 12:47:57PM +1000, Keith Owens wrote:
>> do_cpu_ftr_fixups() replaces unsupported code with NOP, based on the
>> table from __start___ftr_fixup to __stop___ftr_fixup which contains all
>> the data marked as section(__ftr_fixup). Fine, but it only handles
>> section __ftr_fixup data in the kernel, it does not write NOP over
>> __ftr_fixup data in modules. So any code marked as section __ftr_fixup
>> in a module executes unchanged. Unless I am missing something, that is
>> a problem.
>
>After a bit more digging, I'm pretty sure it's not much of a problem.
>get_cycles seems to be either a) SMP or b) DRM or c) arcnet related.
>a and b aren't an issue for 601 (no SMP and possible but unlikely that
>DRM will work on a machine w/ a 601). If there's an arcnet PCI card, I suppose
>it could be an issue then... Anyhow...
It is more than just get_cycles(). Look at the places that ftr is used,
fgrep -r BEGIN_FTR_SECTION include/asm-ppc* arch/ppc*
If any of that code ends up in a module then the problem exists.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-27 3:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010826191536.C1481@cpe-24-221-152-185.az.sprintbbd.net>
[not found] ` <20783.998880477@kao2.melbourne.sgi.com>
2001-08-27 3:04 ` 2.4.9-ac12 ppc ftr_fixup Tom Rini
2001-08-27 3:13 ` Keith Owens [this message]
2001-08-27 3:45 ` Keith Owens
2001-08-27 4:24 ` Tom Rini
2001-08-27 4:31 ` Keith Owens
2001-08-27 4:54 ` Tom Rini
2001-08-27 5:10 ` Keith Owens
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=21473.998882022@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).