From: Marek Vasut <marex@nabladev.com>
To: Nicolai Buchwitz <nb@tipi-net.de>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Ronald Wahl <ronald.wahl@raritan.com>,
Yicong Hui <yiconghui@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [net,PATCH] net: ks8851: Reinstate disabling of BHs around IRQ handler
Date: Wed, 8 Apr 2026 23:21:14 +0200 [thread overview]
Message-ID: <a36f6c1a-85aa-4547-be29-daf56b438aaa@nabladev.com> (raw)
In-Reply-To: <215ad1cc5db3f352ac2a130c07dbd830@tipi-net.de>
On 4/8/26 9:15 PM, Nicolai Buchwitz wrote:
> On 8.4.2026 17:41, Marek Vasut wrote:
>> On 4/8/26 12:54 PM, Nicolai Buchwitz wrote:
>>
>> Hello Nicolai,
>>
>> thank you for testing on the SPI variant, that helped a lot.
>>
>>> In order to make this work I would propose something like this (which
>>> works in my SPI setup):
>>>
>>> --- a/drivers/net/ethernet/micrel/ks8851_par.c
>>> +++ b/drivers/net/ethernet/micrel/ks8851_par.c
>>> @@ -60,12 +60,14 @@ static void ks8851_lock_par(struct ks8851_net
>>> *ks, unsigned long *flags)
>>> {
>>> struct ks8851_net_par *ksp = to_ks8851_par(ks);
>>>
>>> + local_bh_disable();
>>> spin_lock_irqsave(&ksp->lock, *flags);
>>> }
>>>
>>> static void ks8851_unlock_par(struct ks8851_net *ks, unsigned long
>>> *flags)
>>> {
>>> struct ks8851_net_par *ksp = to_ks8851_par(ks);
>>>
>>> spin_unlock_irqrestore(&ksp->lock, *flags);
>>> + local_bh_enable();
>>> }
>>>
>>> Tested-by: Nicolai Buchwitz <nb@tipi-net.de> # KS8851 SPI, non-RT
>>> (regression + proposed fix)
>>
>> Are you also able to test the KS8851 driver with PREEMPT_RT enabled
>> and heavy iperf3 traffic on the SPI variant ? Does that trigger any
>> issues ? I ran 'iperf3 -s' on the KS8851 end and 'iperf3 -c
>> 192.168.1.300 -t 0 --bidir' on the host PC side.
>
> Successfully tested with both PREEMPT_RT and non-RT kernels using the
> iperf3 command above - no issues observed. Both builds included the fix
> from my previous message.
> If there is anything else worth testing on the KS8851 SPI variant,
> please let me know.
Thank you for that. Could you please add the TB to v2 too ?
prev parent reply other threads:[~2026-04-08 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 21:23 [net,PATCH] net: ks8851: Reinstate disabling of BHs around IRQ handler Marek Vasut
2026-04-08 7:51 ` Nicolai Buchwitz
2026-04-08 10:54 ` Nicolai Buchwitz
2026-04-08 15:41 ` Marek Vasut
2026-04-08 19:15 ` Nicolai Buchwitz
2026-04-08 21:21 ` Marek Vasut [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=a36f6c1a-85aa-4547-be29-daf56b438aaa@nabladev.com \
--to=marex@nabladev.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ronald.wahl@raritan.com \
--cc=stable@vger.kernel.org \
--cc=yiconghui@gmail.com \
/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