From: Rusty Russell <rusty@rustcorp.com.au>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] /proc/ksyms change for IA64
Date: Mon, 06 Aug 2001 00:02:51 +1000 [thread overview]
Message-ID: <E15TOUV-00012J-00@localhost> (raw)
In-Reply-To: Your message of "Sun, 05 Aug 2001 17:16:33 +1000." <13470.996995793@ocs3.ocs-net>
In message <13470.996995793@ocs3.ocs-net> you write:
> >Eewwww....
> >
> > How about just adding /proc/ksyms-ia64 with the code pointers
> >which contains the ia64 code addresses required by ksymoops and
> >debuggers. These are, after all, less vital than insmod.
>
> That requires changes to every kernel debugger, oops decoder etc. I
> don't control all of Linux debugging yet ;). It is also more work
> because it requires kernel changes as well as lots of user space.
For ia64 only. IMHO, that's a better line to draw.
Rusty.
--
Premature optmztion is rt of all evl. --DK
next prev parent reply other threads:[~2001-08-05 14:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 3:22 [RFC] /proc/ksyms change for IA64 Keith Owens
2001-08-05 5:44 ` Rusty Russell
2001-08-05 7:16 ` Keith Owens
2001-08-05 14:02 ` Rusty Russell [this message]
2001-08-05 14:51 ` Keith Owens
2001-08-05 9:29 ` PPC? (Was: Re: [RFC] /proc/ksyms change for IA64) Kai Henningsen
2001-08-05 19:41 ` Keith Owens
2001-08-05 20:26 ` Peter A. Castro
2001-08-06 3:05 ` Brad Boyer
2001-08-06 22:43 ` Rob Barris
2001-08-07 3:47 ` Anton Blanchard
2001-08-19 1:27 ` [RFC] /proc/ksyms change for IA64 Richard Henderson
2001-08-21 6:53 ` Keith Owens
2001-08-21 17:47 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2001-08-02 12:42 [Linux-ia64] [RFC] /proc/ksyms change for IA64 (fwd) Jack Steiner
2001-08-02 13:25 ` [RFC] /proc/ksyms change for IA64 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=E15TOUV-00012J-00@localhost \
--to=rusty@rustcorp.com.au \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@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