iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Baolu Lu <baolu.lu@linux.intel.com>
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: Wed, 6 Jul 2022 12:46:54 +0200	[thread overview]
Message-ID: <YsVoHtiNIhvrN+Zd@8bytes.org> (raw)
In-Reply-To: <1036ab2c-f854-9746-ddc7-e9fe20cd3d40@linux.intel.com>

On Fri, Jun 24, 2022 at 02:12:28PM +0800, Baolu Lu wrote:
> 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.

Patch is applied now for 5.19.

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

  reply	other threads:[~2022-07-06 10:47 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
2022-07-06 10:46       ` Joerg Roedel [this message]
  -- 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=YsVoHtiNIhvrN+Zd@8bytes.org \
    --to=joro@8bytes.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jacob.jun.pan@intel.com \
    --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).