From: Victor Yodaiken <yodaiken@fsmlabs.com>
To: george anzinger <george@mvista.com>
Cc: "Russell King" <rmk@arm.linux.org.uk>,
"christophe barbé" <christophe.barbe@lineo.fr>,
linux-kernel@vger.kernel.org
Subject: Re: How should nano_sleep be fixed (was: ptrace(), fork(), sleep(), exit(), SIGCHLD)
Date: Fri, 17 Aug 2001 12:57:27 -0600 [thread overview]
Message-ID: <20010817125727.A16475@hq2> (raw)
In-Reply-To: <3B7D61A6.AF988634@mvista.com>
On Fri, Aug 17, 2001 at 11:25:42AM -0700, george anzinger wrote:
> >
> How about something like:
>
> In ../asm/signal.h (for i386)
>
> #define PT_REGS_ENTRY(type,name,p1_type,p1, p2_type,p2) \
> type name(p1_type p1,p2_typ p2)\
> { struct pt_regs *regs = (struct pt_regs *)&p1;
In RTLinux we define MACHDEPREGS as an arch dependent type. PPC defines
this as a pointer and x87 as the structure etc. The small number of functions
that actually need to manipulate this can be made machine dependent too.
Came in handy during the port to BSD too.
next prev parent reply other threads:[~2001-08-17 19:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 8:29 ptrace(), fork(), sleep(), exit(), SIGCHLD Bruce Janson
2001-08-14 7:28 ` christophe barbé
2001-08-14 15:06 ` Bruce Janson
2001-08-15 15:46 ` george anzinger
2001-08-15 17:53 ` george anzinger
2001-08-15 18:02 ` george anzinger
2001-08-16 0:59 ` How should nano_sleep be fixed (was: ptrace(), fork(), sleep(), exit(), SIGCHLD) george anzinger
2001-08-16 10:17 ` christophe barbé
2001-08-16 10:29 ` Russell King
2001-08-16 14:16 ` george anzinger
2001-08-16 16:00 ` christophe barbé
2001-08-16 16:12 ` Russell King
2001-08-16 18:17 ` george anzinger
2001-08-17 18:25 ` george anzinger
2001-08-17 18:57 ` Victor Yodaiken [this message]
2001-08-17 19:56 ` george anzinger
2001-08-22 18:40 ` Russell King
2001-08-23 20:04 ` george anzinger
2001-08-23 20:11 ` Russell King
2001-08-23 21:13 ` george anzinger
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=20010817125727.A16475@hq2 \
--to=yodaiken@fsmlabs.com \
--cc=christophe.barbe@lineo.fr \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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