From: Joerg Roedel <joro@8bytes.org>
To: Lianbo Jiang <lijiang@redhat.com>
Cc: thomas.lendacky@amd.com, will@kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
robin.murphy@arm.com
Subject: Re: [PATCH 0/2 v2] iommu: fix the failure of deferred attach for iommu attach device
Date: Thu, 28 Jan 2021 12:04:11 +0100 [thread overview]
Message-ID: <20210128110411.GJ32671@8bytes.org> (raw)
In-Reply-To: <20210119111616.12761-1-lijiang@redhat.com>
On Tue, Jan 19, 2021 at 07:16:14PM +0800, Lianbo Jiang wrote:
> Lianbo Jiang (2):
> dma-iommu: use static-key to minimize the impact in the fast-path
> iommu: use the __iommu_attach_device() directly for deferred attach
>
> drivers/iommu/dma-iommu.c | 29 +++++++++++------------------
> drivers/iommu/iommu.c | 12 ++++++++++++
> include/linux/iommu.h | 2 ++
> 3 files changed, 25 insertions(+), 18 deletions(-)
Applied, thanks.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Lianbo Jiang <lijiang@redhat.com>
Cc: linux-kernel@vger.kernel.org, will@kernel.org,
iommu@lists.linux-foundation.org, jsnitsel@redhat.com,
thomas.lendacky@amd.com, robin.murphy@arm.com, bhe@redhat.com
Subject: Re: [PATCH 0/2 v2] iommu: fix the failure of deferred attach for iommu attach device
Date: Thu, 28 Jan 2021 12:04:11 +0100 [thread overview]
Message-ID: <20210128110411.GJ32671@8bytes.org> (raw)
In-Reply-To: <20210119111616.12761-1-lijiang@redhat.com>
On Tue, Jan 19, 2021 at 07:16:14PM +0800, Lianbo Jiang wrote:
> Lianbo Jiang (2):
> dma-iommu: use static-key to minimize the impact in the fast-path
> iommu: use the __iommu_attach_device() directly for deferred attach
>
> drivers/iommu/dma-iommu.c | 29 +++++++++++------------------
> drivers/iommu/iommu.c | 12 ++++++++++++
> include/linux/iommu.h | 2 ++
> 3 files changed, 25 insertions(+), 18 deletions(-)
Applied, thanks.
next prev parent reply other threads:[~2021-01-28 11:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 11:16 [PATCH 0/2 v2] iommu: fix the failure of deferred attach for iommu attach device Lianbo Jiang
2021-01-19 11:16 ` Lianbo Jiang
2021-01-19 11:16 ` [PATCH 1/2 v2] dma-iommu: use static-key to minimize the impact in the fast-path Lianbo Jiang
2021-01-19 11:16 ` Lianbo Jiang
2021-01-19 15:26 ` Christoph Hellwig
2021-01-19 15:26 ` Christoph Hellwig
2021-01-19 15:52 ` Robin Murphy
2021-01-19 15:52 ` Robin Murphy
2021-01-21 12:21 ` lijiang
2021-01-21 12:21 ` lijiang
2021-01-19 11:16 ` [PATCH 2/2 v2] iommu: use the __iommu_attach_device() directly for deferred attach Lianbo Jiang
2021-01-19 11:16 ` Lianbo Jiang
2021-01-19 13:40 ` Robin Murphy
2021-01-19 13:40 ` Robin Murphy
2021-01-19 15:29 ` Christoph Hellwig
2021-01-19 15:29 ` Christoph Hellwig
2021-01-21 12:57 ` lijiang
2021-01-21 12:57 ` lijiang
2021-01-19 13:46 ` [PATCH 0/2 v2] iommu: fix the failure of deferred attach for iommu attach device Lu Baolu
2021-01-19 13:46 ` Lu Baolu
2021-01-28 11:04 ` Joerg Roedel [this message]
2021-01-28 11: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=20210128110411.GJ32671@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=lijiang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=thomas.lendacky@amd.com \
--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 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.