Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Kyle McMartin <kyle@parisc-linux.org>
Cc: klibc@zytor.com, parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: [klibc] [PATCH] vfork() for parisc
Date: Tue, 25 Jul 2006 15:28:32 -0700	[thread overview]
Message-ID: <44C69B10.7050203@zytor.com> (raw)
In-Reply-To: <20060725221524.GA5625@athena.road.mcmartin.ca>

Kyle McMartin wrote:
> On Tue, Jul 25, 2006 at 02:58:02PM -0700, H. Peter Anvin wrote:
>> Kyle McMartin wrote:
>>> Implement "pid_t vfork(void)" for parisc.
>>>
>> Dumb question... where does %r20 get set?  This isn't invoked by a 
>> system call stub; it's the entire function.
>>
> 
> Oh. Nowhere then. We can set it in the branch delay slot.
> 

Cool.  Could you do a "make test" and run usr/klibc/tests/vfork to verify?

(For completeness sake: klibc supports generating stubs for alternate 
system call conventions by using the following syntax in SYSCALLS.def:

returntype syscall@convention(args...);

The string "convention" gets passed to sysstub.ph; on most architectures 
it simply replaces the string "common" in "__syscall_common".

However, there isn't exactly any point to do that for single-shot system 
  call conventions, like vfork() and pipe() on many platforms.

	-hpa
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

      parent reply	other threads:[~2006-07-25 22:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-24  3:14 [parisc-linux] [PATCH] vfork() for parisc Kyle McMartin
     [not found] ` <44C693EA.5080704@zytor.com>
     [not found]   ` <20060725221524.GA5625@athena.road.mcmartin.ca>
2006-07-25 22:28     ` H. Peter Anvin [this message]

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=44C69B10.7050203@zytor.com \
    --to=hpa@zytor.com \
    --cc=klibc@zytor.com \
    --cc=kyle@parisc-linux.org \
    --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