Linux IOMMU Development
 help / color / mirror / Atom feed
From: Vasant Hegde <vasant.hegde@amd.com>
To: iommu@lists.linux.dev, joro@8bytes.org
Cc: suravee.suthikulpanit@amd.com, jgg@nvidia.com, dmarcovitch@nvidia.com
Subject: Re: [PATCH v2 0/2] iommu/amd/iommu_v2: Fix refcount related issues
Date: Wed, 5 Jul 2023 10:05:33 +0530	[thread overview]
Message-ID: <ab7edcb8-99fe-7c38-d98c-d0681649532f@amd.com> (raw)
In-Reply-To: <20230609105146.7773-1-vasant.hegde@amd.com>

HI Joerg,

On 6/9/2023 4:21 PM, Vasant Hegde wrote:
> This patch series fixes the refcount warning and pasid state in free
> path.
> 
> V1 : https://lore.kernel.org/linux-iommu/20230124104355.119166-1-vasant.hegde@amd.com/

Ping. Did you get a chance to look into this series?


-Vasant

> 
> @Jason, Joerg,
>   During v1 series review Jason had suggested few things including
>   moving to xarray to handle PASID. We are planning to implement
>   xarray as separate series.
> 
>   This series fixes the kernel warning we are seeing because of
>   commit 8bc54824da4e. I am keeping changes as minimal so that
>   its easy to backport.
> 
> Base commit: d11370bf64c57a (iommu/next branch)
> 
> Daniel Marcovitch (1):
>   iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind
> 
> Vasant Hegde (1):
>   iommu/amd/iommu_v2: Clear pasid state in free path
> 
>  drivers/iommu/amd/iommu_v2.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 


  parent reply	other threads:[~2023-07-05  4:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 10:51 [PATCH v2 0/2] iommu/amd/iommu_v2: Fix refcount related issues Vasant Hegde
2023-06-09 10:51 ` [PATCH v2 1/2] iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind Vasant Hegde
2023-06-09 10:51 ` [PATCH v2 2/2] iommu/amd/iommu_v2: Clear pasid state in free path Vasant Hegde
2023-07-05  4:35 ` Vasant Hegde [this message]
2023-07-14 14:17 ` [PATCH v2 0/2] iommu/amd/iommu_v2: Fix refcount related issues Joerg Roedel

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=ab7edcb8-99fe-7c38-d98c-d0681649532f@amd.com \
    --to=vasant.hegde@amd.com \
    --cc=dmarcovitch@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=suravee.suthikulpanit@amd.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