From: Ralf Baechle <ralf@linux-mips.org>
To: Jonas Bonn <jonas@southpole.se>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-mips@linux-mips.org
Subject: Re: [PATCH RFC 4/8] mips: implement syscall restart generically
Date: Fri, 4 Nov 2011 09:32:22 +0000 [thread overview]
Message-ID: <20111104093222.GA1633@linux-mips.org> (raw)
In-Reply-To: <04ce50ed7e9e9a949a3c0b447c3aec0a8c6face4.1319364492.git.jonas@southpole.se>
On Sun, Oct 23, 2011 at 12:19:58PM +0200, Jonas Bonn wrote:
> Manipulating task state to effect re-execution of an interrupted syscall
> used to be purely architecture specific code. However, as most arch's
> were essentially just making minor adjustments to almost identical logic,
> this code could be moved to a common implementation.
>
> The generic variant introduces the function handle_syscall_restart() to be
> called after get_signal_to_deliver(). The architecture specific register
> manipulations required to effect the actual restart are now implemented
> in the generic syscall interface found in asm/syscall.h
>
> This patch transitions this architecture's signal handling code over to
> using the generic syscall restart code by:
>
> i) Implementing the register manipulations in asm/syscall.h
> ii) Replacing the restart logic with a call to handle_syscall_restart
Nice cleanup.
Any reason why you add empty version of syscall_get_arguments and
syscall_set_version? A non-functional version that causes a silent
failure is way worse than something that fails at compile time.
Ralf
next prev parent reply other threads:[~2011-11-04 9:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 10:19 [PATCH RFC 0/8] Signal: harmonize syscall restart logic Jonas Bonn
2011-10-23 10:19 ` Jonas Bonn
2011-10-23 10:19 ` [PATCH RFC 1/8] signal: introduce generic " Jonas Bonn
2011-10-23 10:19 ` Jonas Bonn
2011-10-23 10:19 ` [PATCH RFC 2/8] blackfin: implement syscall restart generically Jonas Bonn
2011-10-26 0:01 ` Mike Frysinger
2011-10-26 6:16 ` Jonas Bonn
2011-10-26 7:35 ` [uclinux-dist-devel] " Mike Frysinger
2011-10-26 7:35 ` Mike Frysinger
2011-10-23 10:19 ` [PATCH RFC 3/8] frv: " Jonas Bonn
2011-10-23 10:19 ` [PATCH RFC 4/8] mips: " Jonas Bonn
2011-10-23 10:19 ` Jonas Bonn
2011-11-04 9:32 ` Ralf Baechle [this message]
2011-11-04 9:32 ` Ralf Baechle
2011-11-04 9:50 ` Jonas Bonn
2011-10-23 10:19 ` [PATCH RFC 5/8] x86: " Jonas Bonn
2011-10-23 10:20 ` [PATCH RFC 6/8] m68k: " Jonas Bonn
2011-10-23 10:20 ` Jonas Bonn
2011-10-23 10:20 ` [PATCH RFC 7/8] ia64: " Jonas Bonn
2011-10-23 10:20 ` [PATCH RFC 8/8] tile: " Jonas Bonn
2011-10-23 10:20 ` Jonas Bonn
2011-10-31 15:48 ` Chris Metcalf
2011-10-31 15:48 ` Chris Metcalf
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=20111104093222.GA1633@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=jonas@southpole.se \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.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;
as well as URLs for NNTP newsgroup(s).