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, hch@infradead.org,
iommu@lists.linux-foundation.org, robin.murphy@arm.com
Subject: Re: [PATCH v3 0/2] iommu: fix the failure of deferred attach for iommu attach device
Date: Thu, 28 Jan 2021 13:28:04 +0100 [thread overview]
Message-ID: <20210128122804.GM32671@8bytes.org> (raw)
In-Reply-To: <20210126115337.20068-1-lijiang@redhat.com>
On Tue, Jan 26, 2021 at 07:53:35PM +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 | 10 ++++++++++
> include/linux/iommu.h | 1 +
> 3 files changed, 22 insertions(+), 18 deletions(-)
Sorry, missed that there was a newer version. Applied this instead of
v2.
_______________________________________________
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,
hch@infradead.org, baolu.lu@linux.intel.com
Subject: Re: [PATCH v3 0/2] iommu: fix the failure of deferred attach for iommu attach device
Date: Thu, 28 Jan 2021 13:28:04 +0100 [thread overview]
Message-ID: <20210128122804.GM32671@8bytes.org> (raw)
In-Reply-To: <20210126115337.20068-1-lijiang@redhat.com>
On Tue, Jan 26, 2021 at 07:53:35PM +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 | 10 ++++++++++
> include/linux/iommu.h | 1 +
> 3 files changed, 22 insertions(+), 18 deletions(-)
Sorry, missed that there was a newer version. Applied this instead of
v2.
next prev parent reply other threads:[~2021-01-28 12:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 11:53 [PATCH v3 0/2] iommu: fix the failure of deferred attach for iommu attach device Lianbo Jiang
2021-01-26 11:53 ` Lianbo Jiang
2021-01-26 11:53 ` [PATCH v3 1/2] dma-iommu: use static-key to minimize the impact in the fast-path Lianbo Jiang
2021-01-26 11:53 ` Lianbo Jiang
2021-01-26 11:53 ` [PATCH v3 2/2] iommu: use the __iommu_attach_device() directly for deferred attach Lianbo Jiang
2021-01-26 11:53 ` Lianbo Jiang
2021-01-26 12:12 ` Robin Murphy
2021-01-26 12:12 ` Robin Murphy
2021-01-28 12:28 ` Joerg Roedel [this message]
2021-01-28 12:28 ` [PATCH v3 0/2] iommu: fix the failure of deferred attach for iommu attach device 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=20210128122804.GM32671@8bytes.org \
--to=joro@8bytes.org \
--cc=hch@infradead.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.