Received-SPF: pass (google.com: domain of linux-kernel+bounces-123126-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Message-ID: <d6a8c1c8-258a-447b-b6cd-199f33199388@linux.dev>
Date: Thu, 28 Mar 2024 11:00:24 -0400
Precedence: bulk
MIME-Version: 1.0
Subject: Re: [PATCH 2/3] dma: xilinx_dpdma: Remove unnecessary use of
 irqsave/restore
Content-Language: en-US
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: Michal Simek <michal.simek@amd.com>, linux-kernel@vger.kernel.org,
 linux-arm-kernel@lists.infradead.org,
 Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
 Vinod Koul <vkoul@kernel.org>, dmaengine@vger.kernel.org
References: <20240308210034.3634938-1-sean.anderson@linux.dev>
 <20240308210034.3634938-3-sean.anderson@linux.dev>
 <0652c82f-b0a2-4881-ac51-38399b180ad4@ideasonboard.com>
From: Sean Anderson <sean.anderson@linux.dev>
In-Reply-To: <0652c82f-b0a2-4881-ac51-38399b180ad4@ideasonboard.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 3/27/24 08:27, Tomi Valkeinen wrote:
> Hi,
> 
> On 08/03/2024 23:00, Sean Anderson wrote:
>> xilinx_dpdma_chan_done_irq and xilinx_dpdma_chan_vsync_irq are always
>> called with IRQs disabled from xilinx_dpdma_irq_handler. Therefore we
>> don't need to save/restore the IRQ flags.
> 
> I think this is fine, but a few thoughts:
> 
> - Is spin_lock clearly faster than the irqsave variant, or is this a pointless optimization? It's safer to just use irqsave variant, instead of making sure the code is always called from the expected contexts.

It's not an optimization. Technically this will save a few instructions,
but...

> - Is this style documented/recommended anywhere? Going through docs, I only found docs telling to use irqsave when mixing irq and non-irq contexts.

The purpose is mainly to make it clear that this is meant to be called
in IRQ context. With irqsave, there's an implication that this could be
called in non-IRQ context, which it never is.

> - Does this cause issues on PREEMPT_RT?

Why would it?

--Sean

> 
>  Tomi
> 
>> Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
>> ---
>>
>>   drivers/dma/xilinx/xilinx_dpdma.c | 10 ++++------
>>   1 file changed, 4 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/dma/xilinx/xilinx_dpdma.c b/drivers/dma/xilinx/xilinx_dpdma.c
>> index eb0637d90342..36bd4825d389 100644
>> --- a/drivers/dma/xilinx/xilinx_dpdma.c
>> +++ b/drivers/dma/xilinx/xilinx_dpdma.c
>> @@ -1043,9 +1043,8 @@ static int xilinx_dpdma_chan_stop(struct xilinx_dpdma_chan *chan)
>>   static void xilinx_dpdma_chan_done_irq(struct xilinx_dpdma_chan *chan)
>>   {
>>       struct xilinx_dpdma_tx_desc *active;
>> -    unsigned long flags;
>>   -    spin_lock_irqsave(&chan->lock, flags);
>> +    spin_lock(&chan->lock);
>>         xilinx_dpdma_debugfs_desc_done_irq(chan);
>>   @@ -1057,7 +1056,7 @@ static void xilinx_dpdma_chan_done_irq(struct xilinx_dpdma_chan *chan)
>>                "chan%u: DONE IRQ with no active descriptor!\n",
>>                chan->id);
>>   -    spin_unlock_irqrestore(&chan->lock, flags);
>> +    spin_unlock(&chan->lock);
>>   }
>>     /**
>> @@ -1072,10 +1071,9 @@ static void xilinx_dpdma_chan_vsync_irq(struct  xilinx_dpdma_chan *chan)
>>   {
>>       struct xilinx_dpdma_tx_desc *pending;
>>       struct xilinx_dpdma_sw_desc *sw_desc;
>> -    unsigned long flags;
>>       u32 desc_id;
>>   -    spin_lock_irqsave(&chan->lock, flags);
>> +    spin_lock(&chan->lock);
>>         pending = chan->desc.pending;
>>       if (!chan->running || !pending)
>> @@ -1108,7 +1106,7 @@ static void xilinx_dpdma_chan_vsync_irq(struct  xilinx_dpdma_chan *chan)
>>       spin_unlock(&chan->vchan.lock);
>>     out:
>> -    spin_unlock_irqrestore(&chan->lock, flags);
>> +    spin_unlock(&chan->lock);
>>   }
>>     /**
>