Linux IOMMU Development
 help / color / mirror / Atom feed
From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Zhang@8bytes.org, iommu@lists.linux-foundation.org,
	Guoqing Jiang <guoqing.jiang@linux.dev>,
	Bernice <bernice.zhang@intel.com>,
	Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH 1/2] iommu/vt-d: Fix PCI bus rescan device hot add
Date: Tue, 1 Feb 2022 11:19:18 -0800	[thread overview]
Message-ID: <20220201111918.48aadfdf@jacob-builder> (raw)
In-Reply-To: <YfgFqp+lR9wRdUWn@8bytes.org>

Hi Joerg,

On Mon, 31 Jan 2022 16:52:10 +0100, Joerg Roedel <joro@8bytes.org> wrote:

> On Mon, Jan 31, 2022 at 01:53:06PM +0000, Robin Murphy wrote:
> > Indeed I very nearly asked whether we couldn't just call these from
> > intel_iommu_{probe,release}_device() directly, but it looks like they
> > also interact with the interrupt remapping stuff which can be built
> > independently of the IOMMU API :(  
> 
> Okay, but having two notifiers is still ugly. Can we only register a
> notifier when IRQ-remapping is used without IOMMU-API? In this case a
> single notifier be sufficient.
> 
Do you mean having an IRQ remapping notifier regardless IOMMU-API is
enabled, right?
It make sense, I will give it a try.

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


Thanks,

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

  reply	other threads:[~2022-02-01 19:16 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 [this message]
2022-02-03  8:25           ` Joerg Roedel
2022-02-09 21:52             ` Jacob Pan
2022-02-14 10:31               ` Joerg Roedel
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=20220201111918.48aadfdf@jacob-builder \
    --to=jacob.jun.pan@linux.intel.com \
    --cc=Zhang@8bytes.org \
    --cc=bernice.zhang@intel.com \
    --cc=guoqing.jiang@linux.dev \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox