iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Koba Ko <koba.ko@canonical.com>,
	iommu@lists.linux-foundation.org, Ashok Raj <ashok.raj@intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH 1/1] iommu/vt-d: Skip TE disabling on quirky gfx dedicated iommu
Date: Wed, 22 Jul 2020 12:15:07 +0000	[thread overview]
Message-ID: <20200722121508.6BF4520787@mail.kernel.org> (raw)
In-Reply-To: <20200721001713.24282-1-baolu.lu@linux.intel.com>

Hi

[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag
fixing commit: .

The bot has tested the following trees: v5.7.9, v5.4.52, v4.19.133, v4.14.188, v4.9.230, v4.4.230.

v5.7.9: Failed to apply! Possible dependencies:
    Unable to calculate

v5.4.52: Failed to apply! Possible dependencies:
    Unable to calculate

v4.19.133: Failed to apply! Possible dependencies:
    e5e04d051979d ("iommu/vt-d: Check whether device requires bounce buffer")

v4.14.188: Failed to apply! Possible dependencies:
    85319dcc8955f ("iommu/vt-d: Add for_each_device_domain() helper")
    9ddbfb42138d8 ("iommu/vt-d: Move device_domain_info to header")
    e5e04d051979d ("iommu/vt-d: Check whether device requires bounce buffer")

v4.9.230: Failed to apply! Possible dependencies:
    161b28aae1651 ("iommu/vt-d: Make sure IOMMUs are off when intel_iommu=off")
    61012985eb132 ("iommu/vt-d: Use lo_hi_readq() / lo_hi_writeq()")
    85319dcc8955f ("iommu/vt-d: Add for_each_device_domain() helper")
    9ddbfb42138d8 ("iommu/vt-d: Move device_domain_info to header")
    a7fdb6e648fb1 ("iommu/vt-d: Fix crash when accessing VT-d sysfs entries")
    b0119e870837d ("iommu: Introduce new 'struct iommu_device'")
    b316d02a13c3a ("iommu/vt-d: Unwrap __get_valid_domain_for_dev()")
    bfd20f1cc8501 ("x86, iommu/vt-d: Add an option to disable Intel IOMMU force on")
    e5e04d051979d ("iommu/vt-d: Check whether device requires bounce buffer")

v4.4.230: Failed to apply! Possible dependencies:
    0824c5920b16f ("iommu/vt-d: avoid dev iotlb logic for domains with no dev iotlbs")
    161b28aae1651 ("iommu/vt-d: Make sure IOMMUs are off when intel_iommu=off")
    314f1dc140844 ("iommu/vt-d: refactoring of deferred flush entries")
    53c92d793395f ("iommu: of: enforce const-ness of struct iommu_ops")
    57f98d2f61e19 ("iommu: Introduce iommu_fwspec")
    592033790e827 ("iommu/vt-d: Check the return value of iommu_device_create()")
    85319dcc8955f ("iommu/vt-d: Add for_each_device_domain() helper")
    8d54d6c8b8f3e ("iommu/amd: Implement apply_dm_region call-back")
    9ddbfb42138d8 ("iommu/vt-d: Move device_domain_info to header")
    a7fdb6e648fb1 ("iommu/vt-d: Fix crash when accessing VT-d sysfs entries")
    aa4732406e129 ("iommu/vt-d: per-cpu deferred invalidation queues")
    b0119e870837d ("iommu: Introduce new 'struct iommu_device'")
    b996444cf35e7 ("iommu/of: Handle iommu-map property for PCI")
    bc8474549e94e ("iommu/vt-d: Fix up error handling in alloc_iommu")
    bfd20f1cc8501 ("x86, iommu/vt-d: Add an option to disable Intel IOMMU force on")
    e5e04d051979d ("iommu/vt-d: Check whether device requires bounce buffer")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

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

      parent reply	other threads:[~2020-07-22 12:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21  0:17 [PATCH 1/1] iommu/vt-d: Skip TE disabling on quirky gfx dedicated iommu Lu Baolu
2020-07-21 14:44 ` Limonciello, Mario
2020-07-21 23:06   ` Lu Baolu
2020-07-21 23:45     ` Limonciello, Mario
2020-07-23  1:38       ` Lu Baolu
2020-07-22 12:15 ` Sasha Levin [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=20200722121508.6BF4520787@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=ashok.raj@intel.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=koba.ko@canonical.com \
    --cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).