public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Bert Karwatzki <spasswolf@web.de>
Cc: baolu.lu@linux.intel.com, haifeng.zhao@linux.intel.com,
	iommu@lists.linux.dev, jgg@ziepe.ca, jiaqing.huang@intel.com,
	joro@8bytes.org, kevin.tian@intel.com,
	linux-kernel@vger.kernel.org, robin.murphy@arm.com,
	will@kernel.org
Subject: Re: [PATCH] iommu: fix compilation without CONFIG_IOMMU_INTEL
Date: Fri, 8 Mar 2024 09:40:30 +0800	[thread overview]
Message-ID: <6afb82b4-379d-4a6c-8cc0-00fc72caa72e@linux.intel.com> (raw)
In-Reply-To: <20240307194419.15801-1-spasswolf@web.de>

On 3/8/24 3:44 AM, Bert Karwatzki wrote:
> When the kernel is comiled with CONFIG_IRQ_REMAP=y but without
> CONFIG_IOMMU_INTEL compilation fails since commit def054b01a8678 with an
> undefined reference to device_rbtree_find(). This patch makes sure that
> intel specific code is only compiled with CONFIG_IOMMU_INTEL=y.
> 
> Fixes: def054b01a8678 ("iommu/vt-d: Use device rbtree in iopf reporting path")

I think it should fix below commit:

Fixes: 80a9b50c0b9e ("iommu/vt-d: Improve ITE fault handling if target 
device isn't present")

> 
> Signed-off-by: Bert Karwatzki<spasswolf@web.de>

For users who want a configuration with interrupt remapping and without
DMA remapping, they can achieve this by selecting
IOMMU_DEFAULT_PASSTHROUGH or using kernel command "iommu.passthrough=1".

Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>

Best regards,
baolu



  reply	other threads:[~2024-03-08  1:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 19:44 [PATCH] iommu: fix compilation without CONFIG_IOMMU_INTEL Bert Karwatzki
2024-03-08  1:40 ` Baolu Lu [this message]
2024-03-08  8:04 ` 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=6afb82b4-379d-4a6c-8cc0-00fc72caa72e@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=haifeng.zhao@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=jiaqing.huang@intel.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=spasswolf@web.de \
    --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