Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Saarinen, Jani" <jani.saarinen@intel.com>,
	"Nikula, Jani" <jani.nikula@intel.com>,
	"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
	"De Marchi, Lucas" <lucas.demarchi@intel.com>,
	"iommu@lists.linux.dev" <iommu@lists.linux.dev>
Subject: Re: [REGRESSION] on linux-next (next-20250507)
Date: Sun, 18 May 2025 09:17:03 +0300	[thread overview]
Message-ID: <20250518061703.GB7435@unreal> (raw)
In-Reply-To: <SJ1PR11MB61292A304C9FA6BF92B568A3B991A@SJ1PR11MB6129.namprd11.prod.outlook.com>

On Wed, May 14, 2025 at 12:40:02PM +0000, Borah, Chaitanya Kumar wrote:
> 
> 
> > -----Original Message-----
> > From: Jason Gunthorpe <jgg@nvidia.com>
> > Sent: Monday, May 12, 2025 5:51 PM
> > To: Borah, Chaitanya Kumar <chaitanya.kumar.borah@intel.com>
> > Cc: intel-xe@lists.freedesktop.org; intel-gfx@lists.freedesktop.org; Saarinen,
> > Jani <jani.saarinen@intel.com>; Nikula, Jani <jani.nikula@intel.com>; Kurmi,
> > Suresh Kumar <suresh.kumar.kurmi@intel.com>; De Marchi, Lucas
> > <lucas.demarchi@intel.com>; iommu@lists.linux.dev
> > Subject: Re: [REGRESSION] on linux-next (next-20250507)
> > 
> > On Mon, May 12, 2025 at 06:00:39AM +0000, Borah, Chaitanya Kumar
> > wrote:
> > 
> > > ``````````````````````````````````````````````````````````````````````
> > > ```````````````````````````````````
> > > commit 13f43d7cf3e0570004a0d960bc1be23db827c2ff
> > > Author: Jason Gunthorpe mailto:jgg@nvidia.com
> > > Date:   Tue Apr 8 13:53:56 2025 -0300
> > >
> > >     iommu/pages: Formalize the freelist API
> > > ``````````````````````````````````````````````````````````````````````
> > > ```````````````````````````````````
> > >
> > > We could not revert the patch because of merge conflicts but resetting to the
> > parent of the commit seems to fix the issue.
> > >
> > > Could you please check why the patch causes this regression and provide a
> > fix if necessary?
> > 
> > Could this be the solution?
> 
> Apologies for the delay, this change seems to solve the issue. Can we expect a patch soon?

Jason is on vacation this week. I recommend to submit the patch by itself.

Thanks

> 
> Regards
> 
> Chaitanya
> 
> > 
> > diff --git a/drivers/iommu/dma-iommu.c b/drivers/iommu/dma-iommu.c
> > index 0af1ab36283cba..7d2b51a890c75a 100644
> > --- a/drivers/iommu/dma-iommu.c
> > +++ b/drivers/iommu/dma-iommu.c
> > @@ -154,6 +154,8 @@ static void fq_ring_free_locked(struct
> > iommu_dma_cookie *cookie, struct iova_fq
> >  			       fq->entries[idx].iova_pfn,
> >  			       fq->entries[idx].pages);
> > 
> > +		fq->entries[idx].freelist =
> > +			IOMMU_PAGES_LIST_INIT(fq->entries[idx].freelist);
> >  		fq->head = (fq->head + 1) & fq->mod_mask;
> >  	}
> >  }
> > 
> > Jason

  reply	other threads:[~2025-05-18  6:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12  6:00 [REGRESSION] on linux-next (next-20250507) Borah, Chaitanya Kumar
2025-05-12 12:21 ` Jason Gunthorpe
2025-05-14 12:40   ` Borah, Chaitanya Kumar
2025-05-18  6:17     ` Leon Romanovsky [this message]
2025-05-18  6:45       ` Leon Romanovsky
2025-05-12 13:53 ` ✓ CI.Patch_applied: success for " Patchwork
2025-05-12 13:53 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-12 13:54 ` ✓ CI.KUnit: success " Patchwork
2025-05-12 13:59 ` ✗ CI.Build: failure " Patchwork
2025-05-26 20:59 ` ✓ CI.Patch_applied: success " Patchwork
2025-05-26 20:59 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-26 21:00 ` ✓ CI.KUnit: success " Patchwork
2025-05-26 21:05 ` ✗ CI.Build: failure " Patchwork

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=20250518061703.GB7435@unreal \
    --to=leon@kernel.org \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=iommu@lists.linux.dev \
    --cc=jani.nikula@intel.com \
    --cc=jani.saarinen@intel.com \
    --cc=jgg@nvidia.com \
    --cc=lucas.demarchi@intel.com \
    --cc=suresh.kumar.kurmi@intel.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