From: Sven Schnelle <svens@stackframe.org>
To: Helge Deller <deller@gmx.de>
Cc: John David Anglin <dave.anglin@bell.net>,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH v2] parisc: Don't disable interrupts in cmpxchg and futex operations
Date: Wed, 03 Nov 2021 18:10:41 +0100 [thread overview]
Message-ID: <87k0hpjhbi.fsf@x1.stackframe.org> (raw)
In-Reply-To: <YYKf5XA4fVeo/02l@ls3530> (Helge Deller's message of "Wed, 3 Nov 2021 15:42:45 +0100")
Helge Deller <deller@gmx.de> writes:
> * Sven Schnelle <svens@stackframe.org>:
>> John David Anglin <dave.anglin@bell.net> writes:
>>
>> > On 2021-10-17 12:30 p.m., Helge Deller wrote:
>> >> It seems the warnings are gone if I remove the irq masking.
>> >> I see the options:
>> >> a) revert the irq masking in syscall.S. Not sure if it really hurts performance.
>> >> b) revert the patch from Sven.
>> >> c) insert code to turn back irq on in the fault handler if we are on the gateway page.
>> >> What is your thought?
>> >
>> > After some thought, I believe option a) is the best. I no longer think interrupts can be
>> > disabled in the futex and cmpxchg operations because of COW breaks. This not ideal but
>> > I suspect it's the best we can do.
>> >
>> > For the cmpxchg operations in syscall.S, we rely on the code to not schedule off the gateway
>> > page. For the futex, I added code to disable preemption.
>> >
>> > So far, I haven't seen the warnings with the attached change but the change is only lightly tested.
>>
>> Thanks Dave. I just applied it to my tree and will give it a spin.
>
> Sven, did you had some outcome?
The outcome is that i haven't seen any problems yet.
> I've cleaned up Daves patch and applied it to my for-next tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/commit/?h=for-next&id=b7cd8a368c986abf184e609772b083f43e5d522d
> together with this patch from Sven ("parisc: don't enable irqs
> unconditionally in handle_interruption()"):
> https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/commit/?h=for-next&id=493f84fcb3a791350ffaa2fa2984a0815a924e39
>
> When not applying to master branch from Linus, this patch is needed as well:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1030d681319b43869e0d5b568b9d0226652d1a6f
>
> All is in my for-next tree.
> Testing seems that those are OK and I don't see any
> "BUG: using __this_cpu_add() in preemptible [00000000] code" warnings
> any more.
>
> Any objections if I push those patches to Linus soon?
No objections.
Sven
prev parent reply other threads:[~2021-11-03 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 19:56 [PATCH] parisc: don't enable irqs unconditionally in handle_interruption() Sven Schnelle
[not found] ` <969e8f20-d27c-77cd-62c1-ddb86213ddec@gmx.de>
[not found] ` <a5030b48-b6bc-639c-5360-0389103c228e@bell.net>
[not found] ` <ac539330-bdc2-1bba-e2c2-78d29614864f@bell.net>
[not found] ` <8bef26c2-daee-2a6c-1828-100a5b27e205@gmx.de>
[not found] ` <28325394-99de-67f4-dcca-b1caf1105df2@bell.net>
[not found] ` <87o87oxhhf.fsf@x1.stackframe.org>
[not found] ` <48780780-0f8c-5aa9-d362-a9b9ddeaeedb@gmx.de>
2021-10-20 18:32 ` [PATCH] parisc: Don't disable interrupts in cmpxchg and futex operations John David Anglin
2021-10-20 19:05 ` Sven Schnelle
2021-11-03 14:42 ` [PATCH v2] " Helge Deller
2021-11-03 15:41 ` John David Anglin
2021-11-03 17:10 ` Sven Schnelle [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=87k0hpjhbi.fsf@x1.stackframe.org \
--to=svens@stackframe.org \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.