From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 6287CCEE350 for ; Wed, 9 Oct 2024 21:16:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:In-Reply-To:From:References:Cc:To:Subject:MIME-Version:Date: Message-ID:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=QC4iyrQCc29xqoyIK8hs1g1UmoTbdeAtwVRtUIjdovM=; b=LXcK5+f+te0c73Z2qxzFZX8m2q +46BYS9eWwbOQ4KmlPexjjqZu6FoK/Wjy61LqszDYVtZ8dlItIANgqPpC+0GfpQ3IfuNnUX1l1Tn8 Mpbeyi4edt650UYuJENG96WZFZ0Um+vcXSPs6U/VgHUfaqycE/OgWGKNgaNl5kYXvhoLrJ2vIOTod qOguy9EJtEZ38QJ7YzkJAeblHSWqEFHrlWP+VoWE0X+hDQiioIeTQyeV49PnRkqx1DhfNtWLIuU8k jF0lZHMwqY8fJOQIjvbVrfSWmojXbrdFmtorGkFGQv88Sa+7VLrjw8LMZFwd2WjNVC4DXJaTx2EZV 353NB2bA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1sye2K-0000000AkLA-0CoA; Wed, 09 Oct 2024 21:16:00 +0000 Received: from mail-qt1-x844.google.com ([2607:f8b0:4864:20::844]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1sycEr-0000000AUIP-1s7k for linux-arm-kernel@lists.infradead.org; Wed, 09 Oct 2024 19:20:51 +0000 Received: by mail-qt1-x844.google.com with SMTP id d75a77b69052e-45effbc3348so1596771cf.2 for ; Wed, 09 Oct 2024 12:20:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; t=1728501648; x=1729106448; darn=lists.infradead.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=QC4iyrQCc29xqoyIK8hs1g1UmoTbdeAtwVRtUIjdovM=; b=KkVGWNhTgGjHSTNR5SLP54O1xhQyDRVUd3hZGo+O4H4Pr51MS9FXswbZ/mkrZD54lr Ba2aXhv0EIlpHg/qAqa4bV7eUirZPiAdaKl9gaSBo3tJsj0hlYB76f2afw1PsmIukPx4 eHmJ7JT0IX6FcZ0tFZR6Qbuex3+vjr0pKK02Y= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728501648; x=1729106448; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=QC4iyrQCc29xqoyIK8hs1g1UmoTbdeAtwVRtUIjdovM=; b=Ani/rGhtjg/gJFugViIOCOoXgU8y9y+WmUjFuDCswLgRSkhFOkkTWGlOx4pBfn2brG 9ieGABqSn1WlkcOn8BAGnTPvIAE2JL5kKGhqayxIAGXX0+s1Qqsj7JxQfVx0qavwBM9S cBHYr/yXpMsclUqyoZdJg/AUMDGsvvvx/0p1nOKlIOOwOwVH91GRh65VWJhu2luV3ekF h5gNlfe4h5cwpuuJ5oOgnPj1iM585btspQ0QsD5DiTkvkJrVtAOMX5P1hJUW9agM5dQP CxtW/AcGy1DVlwkjoxr2W3KWfVuJ8ag6N8ZE21BeBSSRAju81++9LD6YeU4A2QpG/2rw DihQ== X-Forwarded-Encrypted: i=1; AJvYcCVqt6Ipaau8TDXYVIjTb3hTk8PdQiOTDiU6tzeGQ2sw3bMlEAyi+4chdBop/qH9YP1DSUaPJ2rlT3iZzv/rWxoJ@lists.infradead.org X-Gm-Message-State: AOJu0YyJwA2cc8sBdsbDWvIFoeJLEKkT0d7mPJ9kJSpq4IBtdVhGoSWC TLXtRv/C+fY957IQgobEojD6RO8UogW5jyJk5xt8USLxisUjA9DECbWFdyDkxQ== X-Google-Smtp-Source: AGHT+IEHkpKuLHIzweOclcuS1w+ydNVY+EW5dw1R/cdDKBZgrPXGHLcodKF5UpmacARcyrjJxiRQ5Q== X-Received: by 2002:a05:622a:2b09:b0:45e:f2df:2ed3 with SMTP id d75a77b69052e-45fa5f03547mr62390651cf.32.1728501648020; Wed, 09 Oct 2024 12:20:48 -0700 (PDT) Received: from [10.69.69.40] ([192.19.223.252]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-45da74b3f6csm49226581cf.16.2024.10.09.12.20.46 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 09 Oct 2024 12:20:47 -0700 (PDT) Message-ID: <73c69285-57ad-4628-b72e-9cae4ebff574@broadcom.com> Date: Wed, 9 Oct 2024 12:20:45 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] firmware: arm_scmi: Queue in scmi layer for mailbox implementation To: Cristian Marussi Cc: Sudeep Holla , arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org, peng.fan@nxp.com, bcm-kernel-feedback-list@broadcom.com, florian.fainelli@broadcom.com References: <20241004221257.2888603-1-justin.chen@broadcom.com> <1ad5c4e9-9f98-40ab-afa4-a7939781e8cc@broadcom.com> Content-Language: en-US From: Justin Chen In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20241009_122049_615077_A1E73598 X-CRM114-Status: GOOD ( 28.51 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 10/9/24 1:32 AM, Cristian Marussi wrote: > On Tue, Oct 08, 2024 at 12:23:28PM -0700, Justin Chen wrote: >> >> >> On 10/8/24 6:37 AM, Cristian Marussi wrote: >>> On Tue, Oct 08, 2024 at 02:34:59PM +0100, Sudeep Holla wrote: >>>> On Tue, Oct 08, 2024 at 02:23:00PM +0100, Sudeep Holla wrote: >>>>> On Tue, Oct 08, 2024 at 01:10:39PM +0100, Cristian Marussi wrote: >>>>>> On Mon, Oct 07, 2024 at 10:58:47AM -0700, Justin Chen wrote: >>>>>>> Thanks for the response. I'll try to elaborate. >>>>>>> >>>>>>> When comparing SMC and mailbox transport, we noticed mailbox transport >>>>>>> timesout much quicker when under load. Originally we thought this was the >>>>>>> latency of the mailbox implementation, but after debugging we noticed a >>>>>>> weird behavior. We saw SMCI transactions timing out before the mailbox even >>>>>>> transmitted the message. >>>>>>> >>>>>>> This issue lies in the SCMI layer. drivers/firmware/arm_scmi/driver.c >>>>>>> do_xfer() function. >>>>>>> >>>>>>> The fundamental issue is send_message() blocks for SMC transport, but >>>>>>> doesn't block for mailbox transport. So if send_message() doesn't block we >>>>>>> can have multiple messages waiting at scmi_wait_for_message_response(). >>>>>>> >>>>>> >>>>>> oh...yes...now I can see it...tx_prepare is really never called given >>>>>> how the mailbox subsystem de-queues messages once at time...so we end up >>>>>> waiting for a reply to some message that is still to be sent...so the >>>>>> message inflight is really NOT corrupted because the next remain pending >>>>>> until the reply in the shmem is read back , BUT the timeout will drift away >>>>>> if you multiple inflights are pending to be sent... >>>>>> >>>>> >>>>> Indeed. >>>>> >>>>>>> SMC looks like this >>>>>>> CPU #0 SCMI message 0 -> calls send_message() then calls >>>>>>> scmi_wait_for_message_response(), timesout after 30ms. >>>>>>> CPU #1 SCMI message 1 -> blocks at send_message() waiting for SCMI message 0 >>>>>>> to complete. >>>>>>> >>>>>>> Mailbox looks like this >>>>>>> CPU #0 SCMI message 0 -> calls send_message(), mailbox layer queues up >>>>>>> message, mailbox layer sees no message is outgoing and sends it. CPU waits >>>>>>> at scmi_wait_for_message_response(), timesout after 30ms >>>>>>> CPU #1 SCMI message 1 -> calls send_message(), mailbox layer queues up >>>>>>> message, mailbox layer sees message pending, hold message in queue. CPU >>>>>>> waits at scmi_wait_for_message_response(), timesout after 30ms. >>>>>>> >>>>>>> Lets say if transport takes 25ms. The first message would succeed, the >>>>>>> second message would timeout after 5ms. >>>>>>> >>>>>>> Hopefully this makes sense. >>>>>> >>>>>> Yes, of course, thanks, for reporting this, and taking time to >>>>>> explain... >>>>>> >>>>>> ...in general the patch LGTM...I think your patch is good also because it >>>>>> could be easily backported as a fix....can you add a Fixes tag in your >>>>>> next version ? >>>>>> >>>>> >>>>> Are you seeing this issue a lot ? IOW, do we need this to be backported ? >>>>> >> >> I wouldn't say a lot. But we are seeing it with standard use of our devices >> running over an extended amount of time. Yes we would like this backported. >> >>>>>> Also can you explain in more detail the issue and the solution in the commit >>>>>> message....that will help having it merged as a Fix in stables... >>>>>> >>>>>> ...for the future (definitely NOT in this series) we could probably think to >>>>>> get rid of the sleeping mutex in favour of some other non-sleeping form of >>>>>> mutual exclusion around the channnel (like in SMC transport) and enable >>>>>> (optionally) Atomic transmission support AND also review if the shmem >>>>>> layer busy-waiting in txprepare is anymore needed at all... >>>>>> >>>>> >>>>> Agreed, if we are locking the channel in SCMI, we can drop the busy-waiting >>>>> in tx_prepare and the associated details in the comment as this locking >>>>> voids that. It is better have both the changes in the same patch to indicate >>>>> the relation between them. >>>> >>>> Actually scratch that last point. The waiting in tx_prepare until the platform >>>> marks it free for agent to use is still needed. One usecase is when agent/OS >>>> times out but platform continues to process and eventually releases the shmem. >>>> Sorry I completely forgot about that. >>>> >>> >>> Yes indeed it is the mechanism that we avoid to reclaim forcibly anyway the shmem >>> if the transmission times out...and we should keep that to avoid >>> corruption of newer messages by late replies from the earlier ones that >>> have timed out. >>> >> >> Yup. I saw an interesting interaction from this. Since modifying shmem and >> ringing the doorbell are often two different task. The modification of shmem >> can race with processing of timed out messages from the platform. This >> usually leads to an early ACK and spurious interrupt. Mostly harmless. We >> did see lockups when multiple timeouts occur, but it was unclear if this was >> an issue with the SCMI transport layer or our driver/platform. >> > > Are you talking about something similar to this: > > https://lore.kernel.org/all/20231220172112.763539-1-cristian.marussi@arm.com/ > > ... reported as a side effect of a spurious IRQ on late timed-out > replies, it should have been fixed with the above commit in v6.8. > I had these fixes and saw these warning message. With these locking changes, I no longer see the lock up. Guess they were related somehow. Either way, Thanks for the review. v2 incoming. Justin > Thanks, > Cristian