From: David Mosberger <davidm@napali.hpl.hp.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: return-type for search_extable()
Date: Fri, 24 Jan 2003 10:23:31 -0800 [thread overview]
Message-ID: <15921.33955.645830.709868@napali.hpl.hp.com> (raw)
In-Reply-To: <20030114025453.5ECBB2C440@lists.samba.org>
Hi Rusty,
Could you please change the return-type of search_extable() to
something that allows a bit more flexibility? The value returned by
this function is "something that lets architecture-specific code
recover from a memory-managment-fault". This may or may not be the
same as an exception_table_entry. For example, on ia64, I want to
return an already-relocated fixup-word. Perhaps the cleanest way to
fix this would be to have:
exception_fixup_t search_extable (...);
By default, you could then use
typedef struct exception_table_entry *exception_fixup_t;
and on ia64 I could use:
typedef long exception_fixup_t.
The only restriction on exception_fixup_t would be that it's a type
that can be tested for being equal to zero and, if it is zero, it
would mean that there is no exception-table entry.
Alternatively, we could make search_extable() just always return a
"void *" or a "long", but that's less clear and less type-safe.
--david
next prev parent reply other threads:[~2003-01-24 18:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 2:27 Userspace Test Framework for module loader porting Rusty Russell
2003-01-06 19:38 ` David Mosberger
2003-01-06 22:41 ` Richard Henderson
2003-01-07 0:37 ` David Mosberger
2003-01-08 11:44 ` Rusty Russell
2003-01-11 1:47 ` David Mosberger
2003-01-13 0:27 ` Rusty Russell
2003-01-13 13:20 ` Maciej W. Rozycki
2003-01-14 0:01 ` Rusty Russell
2003-01-24 18:23 ` David Mosberger [this message]
2003-01-28 4:53 ` return-type for search_extable() Rusty Russell
2003-01-28 6:14 ` David Mosberger
2003-01-08 11:21 ` Userspace Test Framework for module loader porting Rusty Russell
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=15921.33955.645830.709868@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®