From: Anthony PERARD <anthony.perard@citrix.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: xen-devel@lists.xen.org,
"Vincent Guittot" <vincent.guittot@linaro.org>,
stratos-dev@op-lists.linaro.org,
"Alex Bennée" <alex.bennee@linaro.org>,
"Stefano Stabellini" <stefano.stabellini@xilinx.com>,
"Mathieu Poirier" <mathieu.poirier@linaro.com>,
"Mike Holmes" <mike.holmes@linaro.org>,
"Oleksandr Tyshchenko" <olekstysh@gmail.com>,
"Wei Liu" <wl@xen.org>, "Juergen Gross" <jgross@suse.com>,
"Julien Grall" <julien@xen.org>
Subject: Re: [PATCH V6.1 3/3] libxl: arm: make creation of iommu node independent of disk device
Date: Fri, 9 Sep 2022 16:02:38 +0100 [thread overview]
Message-ID: <YxtVjpDU1HOrhiAE@perard.uk.xensource.com> (raw)
In-Reply-To: <ebcf40f0d5dfe6bfa27c11dc2fe3e65df48772fe.1662734469.git.viresh.kumar@linaro.org>
On Fri, Sep 09, 2022 at 08:13:28PM +0530, Viresh Kumar wrote:
> The iommu node will be required for other virtio device types too, not
> just disk device.
>
> Move the call to make_xen_iommu_node(), out of the disk device specific
> block and rename "iommu_created" variable to "iommu_needed", and set it
> to true for virtio disk device.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Reviewed-by: Anthony PERARD <anthony.perard@citrix.com>
Thanks,
--
Anthony PERARD
next prev parent reply other threads:[~2022-09-09 15:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 8:52 [PATCH V6 0/3] libxl: arm: Make generic code independent of disk device Viresh Kumar
2022-09-08 8:52 ` [PATCH V6 1/3] libxl: arm: Create alloc_virtio_mmio_params() Viresh Kumar
2022-09-09 13:19 ` Anthony PERARD
2022-09-08 8:53 ` [PATCH V6 2/3] libxl: arm: Split make_virtio_mmio_node() Viresh Kumar
2022-09-09 13:21 ` Anthony PERARD
2022-09-08 8:53 ` [PATCH V6 3/3] libxl: arm: make creation of iommu node independent of disk device Viresh Kumar
2022-09-09 13:47 ` Anthony PERARD
2022-09-09 14:43 ` [PATCH V6.1 " Viresh Kumar
2022-09-09 15:02 ` Anthony PERARD [this message]
2022-09-20 10:29 ` Viresh Kumar
2022-10-04 9:59 ` Julien Grall
2022-11-24 19:19 ` Julien Grall
2022-11-25 5:45 ` Viresh Kumar
2022-11-28 9:31 ` Julien Grall
2022-09-16 10:21 ` Oleksandr
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=YxtVjpDU1HOrhiAE@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=alex.bennee@linaro.org \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=mathieu.poirier@linaro.com \
--cc=mike.holmes@linaro.org \
--cc=olekstysh@gmail.com \
--cc=stefano.stabellini@xilinx.com \
--cc=stratos-dev@op-lists.linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).