mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@kernel.org>
To: Maxi Saparov <maxi.saparov@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Seth Forshee <sforshee@nvidia.com>,
	Serapheim Dimitropoulos <sdimitropoulos@coreweave.com>,
	Maxi Saparov <masaparov@coreweave.com>
Subject: Re: [PATCH] firmware: arm_ffa: Unmap RxTx buffers on device shutdown
Date: Tue, 1 Sep 2026 08:25:23 +0100	[thread overview]
Message-ID: <20260901-wild-parrot-from-uranus-e0c9ee@sudeepholla> (raw)
In-Reply-To: <ao9sWrszkXwj5-PK@CW-D0XG2Q16P7-L>

On Wed, Aug 26, 2026 at 06:47:11PM -0400, Maxi Saparov wrote:
> Apologies, I failed to spot Carol's earlier patch for the same
> problem before sending this:
> 
>   https://lore.kernel.org/all/20260818224404.3694580-1-csoto@nvidia.com/
> 
> Please disregard my patch in favor of that one. It covers more than
> mine does.
> 
> Some corroborating data from our side, in case it helps that patch
> along. We hit this on NVIDIA GB200 systems in production diagnostics:
> after a kexec from a kernel with FF-A active, the next kernel's
> FFA_RXTX_MAP is denied and the driver fails to probe until a full
> system reset. I can also confirm Carol's observation that unmapping
> the buffers alone is not enough. The notification bitmap is retained
> by the SPMC in the same way, so the cleanup has to cover both.
> 
> Happy to provide Tested-by on the next revision of Carol's patch.
> 

I had replied to Carol with reference to [1]. I prefer that approach, see if
that helps.

-- 
Regards,
Sudeep


[1] https://lore.kernel.org/all/20260729-nostalgic-accurate-raccoon-ab7d7e@sudeepholla/

      reply	other threads:[~2026-09-01  7:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 22:23 Maxi Saparov
2026-08-26 22:47 ` Maxi Saparov
2026-09-01  7:25   ` Sudeep Holla [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=20260901-wild-parrot-from-uranus-e0c9ee@sudeepholla \
    --to=sudeep.holla@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masaparov@coreweave.com \
    --cc=maxi.saparov@gmail.com \
    --cc=sdimitropoulos@coreweave.com \
    --cc=sforshee@nvidia.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

all inboxes | Powered by JetHome®