From: Baolu Lu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Ravi Shankar <ravi.v.shankar@intel.com>,
iommu@lists.linux-foundation.org,
Jacob jun Pan <jacob.jun.pan@intel.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] iommu/vt-d: Fix PCI bus rescan device hot add
Date: Fri, 24 Jun 2022 14:12:28 +0800 [thread overview]
Message-ID: <1036ab2c-f854-9746-ddc7-e9fe20cd3d40@linux.intel.com> (raw)
In-Reply-To: <YrVPelnOi9nql/8C@8bytes.org>
Hi Joerg,
On 2022/6/24 13:45, Joerg Roedel wrote:
> Hi Baolu,
>
> On Wed, May 25, 2022 at 09:40:26AM +0800, Baolu Lu wrote:
>> How do you like it? If you agree, I can queue it in my next pull request
>> for fixes.
>
> Would it help to tie DMAR and IOMMU components together, so that
> selecting DMAR for IRQ remapping also selects IOMMU? The IOMMU can be in
> PT mode and I think it would simplify a lot of things.
It makes sense as far as I am aware. By putting IOMMUs in pass-through
mode, there will be no run-time costs and things could be simplified a
lot.
Besides the refactoring efforts, we still need this quick fix so that
the fix could be propagated to various stable and vendors' downstream trees.
Best regards,
baolu
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2022-06-24 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 0:21 [PATCH] iommu/vt-d: Fix PCI bus rescan device hot add Yian Chen
2022-05-25 1:40 ` Baolu Lu
2022-06-24 5:45 ` Joerg Roedel
2022-06-24 6:12 ` Baolu Lu [this message]
2022-07-06 10:46 ` Joerg Roedel
-- strict thread matches above, loose matches on Subject: below --
2022-01-13 13:23 Jacob Pan
2022-01-14 0:58 ` Lu Baolu
2022-01-14 3:11 ` Jacob Pan
2022-01-14 3:12 ` Lu Baolu
2022-01-14 15:24 ` Jacob Pan
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=1036ab2c-f854-9746-ddc7-e9fe20cd3d40@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=joro@8bytes.org \
--cc=ravi.v.shankar@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;
as well as URLs for NNTP newsgroup(s).