> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-boun...@osuosl.org> On Behalf Of
> Wander Lairson Costa
> Sent: Wednesday, December 4, 2024 12:42 PM
> To: Nguyen, Anthony L <anthony.l.ngu...@intel.com>; Kitszel, Przemyslaw
> <przemyslaw.kits...@intel.com>; Andrew Lunn <andrew+net...@lunn.ch>;
> David S. Miller <da...@davemloft.net>; Eric Dumazet
> <eduma...@google.com>; Jakub Kicinski <k...@kernel.org>; Paolo Abeni
> <pab...@redhat.com>; Sebastian Andrzej Siewior <bige...@linutronix.de>; Clark
> Williams <clrkwl...@kernel.org>; Steven Rostedt <rost...@goodmis.org>; Auke
> Kok <auke-jan.h....@intel.com>; Jeff Garzik <jgar...@redhat.com>; moderated
> list:INTEL ETHERNET DRIVERS <intel-wired-...@lists.osuosl.org>; open
> list:NETWORKING DRIVERS <net...@vger.kernel.org>; open list <linux-
> ker...@vger.kernel.org>; open list:Real-time Linux
> (PREEMPT_RT):Keyword:PREEMPT_RT <linux-rt-de...@lists.linux.dev>
> Cc: Wander Lairson Costa <wan...@redhat.com>
> Subject: [Intel-wired-lan] [PATCH iwl-net 3/4] igb: split igb_msg_task()
> 
> From the perspective of PREEMPT_RT, igb_msg_task() invokes functions that are
> a mix of IRQ-safe and non-IRQ-safe operations.
> 
> To address this, we separate igb_msg_task() into distinct IRQ-safe and
> preemptible-safe components. This is a preparatory step for upcoming commits,
> where the igb_msix_other interrupt handler will be split into IRQ and threaded
> handlers, each invoking the appropriate part of the newly divided 
> igb_msg_task().
> 
> Signed-off-by: Wander Lairson Costa <wan...@redhat.com>
> ---
>  drivers/net/ethernet/intel/igb/igb_main.c | 88 +++++++++++++++++++++--
>  1 file changed, 81 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/net/ethernet/intel/igb/igb_main.c
> b/drivers/net/ethernet/intel/igb/igb_main.c
> index 9b4235ec226df..5828831fd29c2 100644
> --- a/drivers/net/ethernet/intel/igb/igb_main.c
> +++ b/drivers/net/ethernet/intel/igb/igb_main.c
> @@ -149,6 +149,8 @@ static int igb_vlan_rx_kill_vid(struct net_device *,


Tested-by: Rafal Romanowski <rafal.romanow...@intel.com>

Reply via email to