Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: John David Anglin <dave.anglin@bell.net>
Cc: linux-parisc <linux-parisc@vger.kernel.org>,
	Helge Deller <deller@gmx.de>, Deller <deller@kernel.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [PATCH v2] parisc: Rewrite light-weight syscall and futex code
Date: Thu, 23 Dec 2021 19:47:22 +0100	[thread overview]
Message-ID: <YcTEOhVnmT8kQRmf@ls3530> (raw)
In-Reply-To: <YcScAR4cPgyI5B6d@mx3210.localdomain>

...
> In order to do this, we need a mechanism to trigger COW breaks outside the
> critical region. Fortunately, parisc has the "stbys,e" instruction. When
> the leftmost byte of a word is addressed, this instruction triggers all
> the exceptions of a normal store but it does not write to memory. Thus,
> we can use it to trigger COW breaks outside the critical region without
> modifying the data that is to be updated atomically.
...
> diff --git a/arch/parisc/include/asm/futex.h b/arch/parisc/include/asm/futex.h
> index 9cd4dd6e63ad..8f97db995b04 100644
> --- a/arch/parisc/include/asm/futex.h
> +++ b/arch/parisc/include/asm/futex.h
...
> +static inline bool _futex_force_interruptions(unsigned long ua)
> +{
> +	bool result;
> +
> +	__asm__ __volatile__(
> +		"1:\tldw 0(%1), %0\n"
> +		"2:\tstbys,e %%r0, 0(%1)\n"
> +		"\tcomclr,= %%r0, %%r0, %0\n"
> +		"3:\tldi 1, %0\n"
> +		ASM_EXCEPTIONTABLE_ENTRY(1b, 3b)
> +		ASM_EXCEPTIONTABLE_ENTRY(2b, 3b)
> +		: "=&r" (result) : "r" (ua) : "memory"
> +	);
> +	return result;

I wonder if we can get rid of the comclr,= instruction by using
ASM_EXCEPTIONTABLE_ENTRY_EFAULT instead of ASM_EXCEPTIONTABLE_ENTRY,
e.g.:

diff --git a/arch/parisc/include/asm/futex.h b/arch/parisc/include/asm/futex.h
index 8f97db995b04..ea052f013865 100644
--- a/arch/parisc/include/asm/futex.h
+++ b/arch/parisc/include/asm/futex.h
@@ -21,20 +21,21 @@ static inline unsigned long _futex_hash_index(unsigned long ua)
  * if load and store fault.
  */

-static inline bool _futex_force_interruptions(unsigned long ua)
+static inline unsigned long _futex_force_interruptions(unsigned long ua)
 {
-	bool result;
+	register unsigned long error __asm__ ("r8") = 0;
+	register unsigned long temp;

 	__asm__ __volatile__(
-		"1:\tldw 0(%1), %0\n"
-		"2:\tstbys,e %%r0, 0(%1)\n"
-		"\tcomclr,= %%r0, %%r0, %0\n"
-		"3:\tldi 1, %0\n"
-		ASM_EXCEPTIONTABLE_ENTRY(1b, 3b)
-		ASM_EXCEPTIONTABLE_ENTRY(2b, 3b)
-		: "=&r" (result) : "r" (ua) : "memory"
+		"1:\tldw 0(%2), %0\n"
+		"2:\tstbys,e %%r0, 0(%2)\n"
+		"3:\n"
+		ASM_EXCEPTIONTABLE_ENTRY_EFAULT(1b, 3b)
+		ASM_EXCEPTIONTABLE_ENTRY_EFAULT(2b, 3b)
+		: "=r" (temp), "=r" (error)
+		: "r" (ua), "1" (error) : "memory"
 	);
-	return result;
+	return error;
 }


Helge

  reply	other threads:[~2021-12-23 18:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 15:55 [PATCH v2] parisc: Rewrite light-weight syscall and futex code John David Anglin
2021-12-23 18:47 ` Helge Deller [this message]
2021-12-23 19:17   ` John David Anglin
2021-12-23 19:31     ` Helge Deller
2021-12-23 19:58       ` Helge Deller
2021-12-23 20:04         ` John David Anglin
2021-12-23 20:14       ` John David Anglin
2021-12-23 20:19         ` John David Anglin
2021-12-23 21:13         ` Helge Deller
2021-12-23 21:36           ` John David Anglin

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=YcTEOhVnmT8kQRmf@ls3530 \
    --to=deller@gmx.de \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dave.anglin@bell.net \
    --cc=deller@kernel.org \
    --cc=linux-parisc@vger.kernel.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