From: Hubertus Franke <frankeh@watson.ibm.com>
To: Mark Mielke <mark@mark.mielke.cc>
Cc: "Bill Abt" <babt@us.ibm.com>,
drepper@redhat.com, linux-kernel@vger.kernel.org,
Martin.Wirth@dlr.de, "Peter Wächtler" <pwaechtler@loewe-komp.de>,
"Rusty Russell" <rusty@rustcorp.com.au>
Subject: Re: [PATCH] Futex Generalization Patch
Date: Mon, 15 Apr 2002 16:46:24 -0400 [thread overview]
Message-ID: <20020415214532.1F3553FE06@smtp.linux.ibm.com> (raw)
In-Reply-To: <OF24E0B753.2B92A422-ON85256B9C.00512368@raleigh.ibm.com> <20020415172204.4B6073FE08@smtp.linux.ibm.com> <20020415165740.A28056@mark.mielke.cc>
On Monday 15 April 2002 04:57 pm, Mark Mielke wrote:
> On Mon, Apr 15, 2002 at 12:22:59PM -0400, Hubertus Franke wrote:
> > typedef struct siginfo {
> > ...
> > union {
> > int _pad[SI_PAD_SIZE];
> >
> > struct {
> > ...
> > } _kill;
> > ...
> >
> > I'd suggest we tag along the _sigfault semantics.
> > We don't need to know who woke us up, just which <addr> got signalled.
>
> Is there issues with creating a new struct in the union that represents
> exactly what you wish it to represent?
>
> mark
No, but then again there seems to be no need either.
All we need is the <addr> that is to be woken up, which
carries similarity to a SEGV signal handler.
--
-- Hubertus Franke (frankeh@watson.ibm.com)
next prev parent reply other threads:[~2002-04-15 21:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 14:49 [PATCH] Futex Generalization Patch Bill Abt
2002-04-15 16:22 ` Hubertus Franke
2002-04-15 20:57 ` Mark Mielke
2002-04-15 20:46 ` Hubertus Franke [this message]
2002-04-16 20:03 ` Peter Wächtler
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 19:59 Bill Abt
2002-04-10 20:14 ` Hubertus Franke
2002-04-11 13:55 ` Rusty Russell
2002-04-10 19:30 Bill Abt
2002-04-10 18:47 ` Hubertus Franke
2002-04-12 15:36 ` Peter Wächtler
2002-04-12 18:48 ` Hubertus Franke
2002-04-13 13:52 ` Peter Wächtler
2002-04-15 13:28 ` Hubertus Franke
2002-04-10 18:09 Bill Abt
2002-04-10 18:10 ` Hubertus Franke
2002-04-04 7:52 Rusty Russell
2002-04-04 16:28 ` Hubertus Franke
2002-04-06 9:48 ` Rusty Russell
2002-04-10 14:24 ` Hubertus Franke
2002-04-10 16:37 ` Rusty Russell
2002-04-10 16:37 ` Hubertus Franke
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=20020415214532.1F3553FE06@smtp.linux.ibm.com \
--to=frankeh@watson.ibm.com \
--cc=Martin.Wirth@dlr.de \
--cc=babt@us.ibm.com \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mark.mielke.cc \
--cc=pwaechtler@loewe-komp.de \
--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