mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Oliver Lin <oliver@liuxiaozhen.dev>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
	joro@8bytes.org, robin.murphy@arm.com, will@kernel.org
Subject: Re: [PATCH] iommu/vt-d: respect user override for intel_iommu=on on Lenovo ThinkPad P50s
Date: Fri, 3 Jul 2026 09:26:37 +0800	[thread overview]
Message-ID: <b744ef83-6cab-4f4f-a22a-251e08b62656@linux.intel.com> (raw)
In-Reply-To: <20260702103137.508709-1-oliver@liuxiaozhen.dev>

On 7/2/26 18:31, Oliver Lin wrote:
> From: oliver<oliver@liuxiaozhen.dev>
> 
> The current DMI quirk disables VT-d on ThinkPad P50s unconditionally,
> even when intel_iommu=on is explicitly requested via kernel command line.

The current driver doesn't have the DMI quirk, so this patch cannot be
applied to the tree as-is.

> This breaks kernel parameter precedence and user intent.
> 
> Make the quirk conditional so that it does not override explicit user
> enabling of Intel IOMMU.
> 
> Signed-off-by: Oliver<oliver@liuxiaozhen.dev>
> ---
>   drivers/iommu/intel/iommu.c | 6 +++++-
>   1 file changed, 5 insertions(+), 1 deletion(-)

Thanks,
baolu

  reply	other threads:[~2026-07-03  1:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-20 19:22 [PATCH] iommu/vt-d: Disable IOMMU " Oliver Lin
2026-06-21  1:29 ` Baolu Lu
     [not found]   ` <e4deced7-aabf-44d2-859c-d0b0add48d76@liuxiaozhen.dev>
2026-07-01 17:03     ` Oliver Lin
2026-07-02 10:31       ` [PATCH] iommu/vt-d: respect user override for intel_iommu=on " Oliver Lin
2026-07-03  1:26         ` Baolu Lu [this message]
2026-07-03  9:23           ` [PATCH v3] iommu/vt-d: Disable IOMMU by default " Oliver Lin
2026-07-13  1:55             ` Baolu Lu
2026-07-13  2:27               ` Oliver Lin

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=b744ef83-6cab-4f4f-a22a-251e08b62656@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@liuxiaozhen.dev \
    --cc=robin.murphy@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox