All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: <will@kernel.org>, <robin.murphy@arm.com>, <joro@8bytes.org>,
	<praan@google.com>, <kevin.tian@intel.com>, <smostafa@google.com>,
	<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>, <jamien@nvidia.com>
Subject: Re: [PATCH v9 07/12] iommu/arm-smmu-v3-kexec: Add ASID/VMID reservation helpers
Date: Sat, 22 Aug 2026 13:21:25 -0700	[thread overview]
Message-ID: <aooExTciU6EJTM8J@nvidia.com> (raw)
In-Reply-To: <20260822195954.GN244917@nvidia.com>

On Sat, Aug 22, 2026 at 04:59:54PM -0300, Jason Gunthorpe wrote:
> On Sat, Aug 22, 2026 at 11:51:58AM -0700, Nicolin Chen wrote:
> > On Fri, Aug 21, 2026 at 08:15:26PM -0300, Jason Gunthorpe wrote:
> > > > +/**
> > > > + * arm_smmu_kexec_unresv_ids() - Roll back a failing reservation scan
> > > > + * @smmu: SMMU device of this kernel that failed its reservation scan
> > > 
> > > And wouldn't need this either.
> > > 
> > > Actually I think this is overkill regardless, just leave the xarray with ASIDs
> > > reserved. Who cares?
> > 
> > ASID might be 8-bit that would have limited ASID slots. And it's
> > a quite small step, so I think it might be worth keeping it.
> 
> Once you have it per smmu just clear the entire xarray on some
> failure

Yes, there are only two destroy() in the function now.

Nicolin


  reply	other threads:[~2026-08-22 20:21 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 19:48 [PATCH v9 00/12] iommu/arm-smmu-v3: Adopt the crashed kernel's stream table for kdump Nicolin Chen
2026-07-21 19:48 ` [PATCH v9 01/12] iommu/arm-smmu-v3: Do not enable EVTQ/PRIQ interrupts in kdump kernel Nicolin Chen
2026-08-21 23:15   ` Jason Gunthorpe
2026-08-22 18:12     ` Nicolin Chen
2026-07-21 19:48 ` [PATCH v9 02/12] iommu/arm-smmu-v3: Skip EVTQ/PRIQ setup " Nicolin Chen
2026-08-21 23:15   ` Jason Gunthorpe
2026-08-22 18:22     ` Nicolin Chen
2026-07-21 19:48 ` [PATCH v9 03/12] iommu/arm-smmu-v3: Add strtab parse helpers to a new arm-smmu-v3-kexec.c Nicolin Chen
2026-08-21 23:15   ` Jason Gunthorpe
2026-07-21 19:48 ` [PATCH v9 04/12] iommu/arm-smmu-v3: Destroy vmid_map ida via devres Nicolin Chen
2026-08-21 23:15   ` Jason Gunthorpe
2026-07-21 19:48 ` [PATCH v9 05/12] iommu/arm-smmu-v3: Add ARM_SMMU_OPT_KDUMP_ADOPT for kdump kernel Nicolin Chen
2026-08-21 23:15   ` Jason Gunthorpe
2026-07-21 19:48 ` [PATCH v9 06/12] iommu/arm-smmu-v3-kexec: Add a CD table parse helper Nicolin Chen
2026-08-21 23:15   ` Jason Gunthorpe
2026-07-21 19:48 ` [PATCH v9 07/12] iommu/arm-smmu-v3-kexec: Add ASID/VMID reservation helpers Nicolin Chen
2026-08-21 23:15   ` Jason Gunthorpe
2026-08-22  2:07     ` Nicolin Chen
2026-08-22 18:51     ` Nicolin Chen
2026-08-22 19:59       ` Jason Gunthorpe
2026-08-22 20:21         ` Nicolin Chen [this message]
2026-07-21 19:48 ` [PATCH v9 08/12] iommu/arm-smmu-v3-kdump: Reserve crashed kernel's ASIDs and VMIDs Nicolin Chen
2026-08-21 23:15   ` Jason Gunthorpe
2026-08-22 18:14     ` Nicolin Chen
2026-07-21 19:48 ` [PATCH v9 09/12] iommu/arm-smmu-v3-kdump: Implement is_attach_deferred() Nicolin Chen
2026-08-21 23:15   ` Jason Gunthorpe
2026-08-22 18:16     ` Nicolin Chen
2026-08-22 20:02       ` Jason Gunthorpe
2026-08-22 20:26         ` Nicolin Chen
2026-08-25 20:08         ` Konstantin Ryabitsev
2026-07-21 21:38 ` [PATCH v9 10/12] iommu/arm-smmu-v3: Retain CR0_SMMUEN during kdump device reset Nicolin Chen
2026-07-21 21:38 ` [PATCH v9 11/12] iommu/arm-smmu-v3: Skip RMR bypass for kdump adoption Nicolin Chen
2026-08-21 23:15   ` Jason Gunthorpe
2026-07-21 21:38 ` [PATCH v9 12/12] iommu/arm-smmu-v3: Detect ARM_SMMU_OPT_KDUMP_ADOPT in probe() Nicolin Chen
2026-08-21 23:15   ` Jason Gunthorpe

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=aooExTciU6EJTM8J@nvidia.com \
    --to=nicolinc@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=jamien@nvidia.com \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=praan@google.com \
    --cc=robin.murphy@arm.com \
    --cc=smostafa@google.com \
    --cc=will@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.