All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "Surendrakumar Upadhyay,
	TejaskumarX" <tejaskumarx.surendrakumar.upadhyay@intel.com>,
	"baolu.lu@linux.intel.com" <baolu.lu@linux.intel.com>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>
Cc: "Talla, RavitejaX Goud" <ravitejax.goud.talla@intel.com>
Subject: Re: [PATCH] iommu/vt-d: Add RPLS to quirk list to skip TE disabling
Date: Thu, 24 Feb 2022 13:39:59 +0000	[thread overview]
Message-ID: <2eb4e522d6294a6ade91b89ea1c5cc7c8dac1e51.camel@intel.com> (raw)
In-Reply-To: <8dcb852f-ef40-5b93-3713-a2d701d90320@linux.intel.com>

On Thu, 2022-02-24 at 13:42 +0800, Lu Baolu wrote:
> On 2/23/22 2:29 PM, Tejas Upadhyay wrote:
> > The VT-d spec requires (10.4.4 Global Command Register, TE
> > field) that:
> > 
> > Hardware implementations supporting DMA draining must drain
> > any in-flight DMA read/write requests queued within the
> > Root-Complex before completing the translation enable
> > command and reflecting the status of the command through
> > the TES field in the Global Status register.
> > 
> > Unfortunately, some integrated graphic devices fail to do
> > so after some kind of power state transition. As the
> > result, the system might stuck in iommu_disable_translati
> > on(), waiting for the completion of TE transition.
> > 
> > This adds RPLS to a quirk list for those devices and skips
> > TE disabling if the qurik hits.
> > 
> > Fixes: https://gitlab.freedesktop.org/drm/intel/-/issues/4898
> > Fixes: LCK-10789
> 
> Remove this please.

good catch. Wrong use of Fixes tag.
"Fixes:" should only be used for patches fixing other patches and
mentioning the commit id.

Baolu,
could you mind if we use

Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/4898

or maybe

References: https://gitlab.freedesktop.org/drm/intel/-/issues/4898

This last one seems to be the one use in drivers/iommu
and the Closes is what we use in drm-intel, hence the one used
with gitlab.freedesktop links in general.

> 
> > Tested-by: Raviteja Goud Talla <ravitejax.goud.talla@intel.com>
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Signed-off-by: Tejas Upadhyay
> > <tejaskumarx.surendrakumar.upadhyay@intel.com>

you can keep my rv-b

> > ---
> >   drivers/iommu/intel/iommu.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/iommu/intel/iommu.c
> > b/drivers/iommu/intel/iommu.c
> > index 92fea3fbbb11..be9487516617 100644
> > --- a/drivers/iommu/intel/iommu.c
> > +++ b/drivers/iommu/intel/iommu.c
> > @@ -5743,7 +5743,7 @@ static void quirk_igfx_skip_te_disable(struct
> > pci_dev *dev)
> >         ver = (dev->device >> 8) & 0xff;
> >         if (ver != 0x45 && ver != 0x46 && ver != 0x4c &&
> >             ver != 0x4e && ver != 0x8a && ver != 0x98 &&
> > -           ver != 0x9a)
> > +           ver != 0x9a && ver != 0xa7)
> >                 return;
> >   
> >         if (risky_device(dev))
> 
> This is a quirk for integrated graphic device. Rodrigo, does this
> hardware needs this quirk as well?

Yes, 0xa7* are RPL-S that are integrated and very similar to 0x46*
(ADL-S)

I would prefer to have a more expanded list instead of group or at
least some defines with the platform names.

Thanks,
Rodrigo.

> 
> Best regards,
> baolu

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2022-02-24 13:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23  6:29 [PATCH] iommu/vt-d: Add RPLS to quirk list to skip TE disabling Tejas Upadhyay
2022-02-24  5:42 ` Lu Baolu
2022-02-24 13:39   ` Vivi, Rodrigo [this message]
2022-02-25  2:20     ` Lu Baolu
2022-02-25 14:12       ` Vivi, Rodrigo
2022-02-26  6:40         ` Lu Baolu
2022-02-28 20:58           ` Vivi, Rodrigo
  -- strict thread matches above, loose matches on Subject: below --
2022-03-02  4:29 Tejas Upadhyay
2022-03-02  4:47 ` Surendrakumar Upadhyay, TejaskumarX
2022-03-02  4:32 Tejas Upadhyay

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=2eb4e522d6294a6ade91b89ea1c5cc7c8dac1e51.camel@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=ravitejax.goud.talla@intel.com \
    --cc=tejaskumarx.surendrakumar.upadhyay@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 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.