LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC] Attempt to clean up sigsuspend et al
Date: Sat, 12 Nov 2005 11:28:31 +1100	[thread overview]
Message-ID: <17269.14127.936147.778781@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <1131745047.21212.194.camel@hades.cambridge.redhat.com>

David Woodhouse writes:

> This is an attempt to get rid of it all, motivated mostly because I want
> to add two _new_ functions which would need such treatment (pselect,
> ppoll).
> 
> We define a new thread flag TIF_RESTOREALL which is set by the syscall
> which needs this treatment, and make the syscall return path honour it.
> This seems to work as far as I've tested it (i.e. the system boots) for
> ppc64, but I haven't even attempted to compile the 32-bit version yet.

Ummm, I don't see where you save the non-volatile GPRs to the
exception frame _before_ do_signal (called from within *_sigsuspend)
copies them to the user stack...

Paul.

  reply	other threads:[~2005-11-12  0:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-11 21:37 [RFC] Attempt to clean up sigsuspend et al David Woodhouse
2005-11-12  0:28 ` Paul Mackerras [this message]
2005-11-12  0:48   ` David Woodhouse
2005-11-13  6:58     ` Paul Mackerras
2005-11-13  9:41       ` David Woodhouse
2005-11-13 10:09         ` Paul Mackerras
2005-11-13 11:58           ` David Woodhouse
2005-11-14  4:43             ` Paul Mackerras
2005-11-14 20:05               ` David Woodhouse
2005-11-15  0:19       ` David Woodhouse

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=17269.14127.936147.778781@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=dwmw2@infradead.org \
    --cc=linuxppc-dev@ozlabs.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