From: Joerg Roedel <joro@8bytes.org>
To: Jacob Pan <jacob.jun.pan@linux.intel.com>
Cc: iommu@lists.linux-foundation.org,
Robin Murphy <robin.murphy@arm.com>,
Guoqing Jiang <guoqing.jiang@linux.dev>,
Bernice <bernice.zhang@intel.com>,
"Raj, Ashok" <ashok.raj@intel.com>
Subject: Re: [PATCH 1/2] iommu/vt-d: Fix PCI bus rescan device hot add
Date: Mon, 14 Feb 2022 11:31:03 +0100 [thread overview]
Message-ID: <YgovZzFR1HNQP2Nk@8bytes.org> (raw)
In-Reply-To: <20220209135249.690b8a08@jacob-builder>
Hi Jacob,
On Wed, Feb 09, 2022 at 01:52:49PM -0800, Jacob Pan wrote:
> Another option Ashok and I discussed is that we can make DMAR cache persist
> (which should be for explicitly listed devices in each DRHD) across PCI
> remove-rescan cycle, then we don't need the DMAR PCI bus notifier at all.
>
> This bug only impacts RCIEP device hotplug, which is not the most reasonable
> use case, we have the space to look into a proper fix.
Even better if you can make the notifier obsolete. Looking forward to
the fix.
Regards,
Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2022-02-14 10:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 3:10 [PATCH 0/2] iommu/vt-d: Fixes for v5.17-rc2 Lu Baolu
2022-01-28 3:10 ` [PATCH 1/2] iommu/vt-d: Fix PCI bus rescan device hot add Lu Baolu
2022-01-30 7:43 ` Joerg Roedel
2022-01-31 13:53 ` Robin Murphy
2022-01-31 15:52 ` Joerg Roedel
2022-02-01 19:19 ` Jacob Pan
2022-02-03 8:25 ` Joerg Roedel
2022-02-09 21:52 ` Jacob Pan
2022-02-14 10:31 ` Joerg Roedel [this message]
2022-02-01 18:55 ` Jacob Pan
2022-01-28 3:10 ` [PATCH 2/2] iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping() Lu Baolu
2022-01-31 15:53 ` 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=YgovZzFR1HNQP2Nk@8bytes.org \
--to=joro@8bytes.org \
--cc=ashok.raj@intel.com \
--cc=bernice.zhang@intel.com \
--cc=guoqing.jiang@linux.dev \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=robin.murphy@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.