From: Joerg Roedel <joro@8bytes.org>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: iommu@lists.linux-foundation.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] iommu/virtio: Build virtio-iommu as module
Date: Wed, 19 Feb 2020 12:16:04 +0100 [thread overview]
Message-ID: <20200219111604.GH1961@8bytes.org> (raw)
In-Reply-To: <20200214163827.1606668-1-jean-philippe@linaro.org>
On Fri, Feb 14, 2020 at 05:38:27PM +0100, Jean-Philippe Brucker wrote:
> From: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
>
> Now that the infrastructure changes are in place, enable virtio-iommu to
> be built as a module. Remove the redundant pci_request_acs() call, since
> it's not exported but is already invoked during DMA setup.
Which infrastructure changes do you mean? Does this depend on the x86
enablement patch-set in any way?
Regards,
Joerg
_______________________________________________
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-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Jean-Philippe Brucker
<jean-philippe-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [PATCH] iommu/virtio: Build virtio-iommu as module
Date: Wed, 19 Feb 2020 12:16:04 +0100 [thread overview]
Message-ID: <20200219111604.GH1961@8bytes.org> (raw)
In-Reply-To: <20200214163827.1606668-1-jean-philippe-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
On Fri, Feb 14, 2020 at 05:38:27PM +0100, Jean-Philippe Brucker wrote:
> From: Jean-Philippe Brucker <jean-philippe.brucker-5wv7dgnIgG8@public.gmane.org>
>
> Now that the infrastructure changes are in place, enable virtio-iommu to
> be built as a module. Remove the redundant pci_request_acs() call, since
> it's not exported but is already invoked during DMA setup.
Which infrastructure changes do you mean? Does this depend on the x86
enablement patch-set in any way?
Regards,
Joerg
next prev parent reply other threads:[~2020-02-19 11:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 16:38 [PATCH] iommu/virtio: Build virtio-iommu as module Jean-Philippe Brucker
2020-02-14 16:38 ` Jean-Philippe Brucker
2020-02-19 11:16 ` Joerg Roedel [this message]
2020-02-19 11:16 ` Joerg Roedel
2020-02-19 11:41 ` Jean-Philippe Brucker
2020-02-19 11:41 ` Jean-Philippe Brucker
2020-02-19 12:33 ` Joerg Roedel
2020-02-19 12:33 ` 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=20200219111604.GH1961@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.org \
--cc=virtualization@lists.linux-foundation.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.