From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Carlos O'Donell" <carlos@baldric.uwo.ca>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] [RFC] Revamp exception handling in the kernel
Date: 12 Sep 2004 09:58:15 -0400 [thread overview]
Message-ID: <1094997501.1714.4.camel@mulgrave> (raw)
In-Reply-To: <20040912134707.GL1854@baldric.uwo.ca>
On Sun, 2004-09-12 at 09:47, Carlos O'Donell wrote:
> I'm looking through the module loading code and worrying about how
> absolute fixups works when a module needs a fixup?
It should work identically to non-module code ... what specifically is
worrying you?
> How are we handling module fixups with absolute fixup addresses?
The same way we do in the regular kernel ... jump to the absolute
address.
James
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2004-09-12 13:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-11 16:53 [parisc-linux] [RFC] Revamp exception handling in the kernel Randolph Chung
2004-09-11 22:49 ` John David Anglin
2004-09-12 13:10 ` Carlos O'Donell
2004-09-12 13:47 ` Carlos O'Donell
2004-09-12 13:58 ` James Bottomley [this message]
2004-09-12 14:29 ` Carlos O'Donell
2004-09-12 15:03 ` James Bottomley
2004-09-12 16:15 ` Randolph Chung
2004-09-12 17:54 ` Carlos O'Donell
2004-09-12 18:48 ` Randolph Chung
2004-09-12 19:19 ` Carlos O'Donell
2004-09-13 23:37 ` Randolph Chung
2004-09-14 2:37 ` Randolph Chung
2004-09-14 18:52 ` Joel Soete
[not found] <20040914160613.GA28659@tausq.org>
2004-09-14 22:36 ` Carlos O'Donell
[not found] ` <41487C05.3010606@tiscali.be>
[not found] ` <41487D4C.2020004@tiscali.be>
2004-09-16 14:31 ` Carlos O'Donell
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=1094997501.1714.4.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.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