From: Nicolin Chen <nicolinc@nvidia.com>
To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
Cc: Eric Auger <eric.auger@redhat.com>,
Mostafa Saleh <smostafa@google.com>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>,
"Jason Gunthorpe" <jgg@nvidia.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Moritz Fischer <mdf@kernel.org>,
Michael Shavit <mshavit@google.com>,
"Andrea Bolognani" <abologna@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Peter Xu" <peterx@redhat.com>
Subject: Re: nested-smmuv3 topic, Sep 2024
Date: Thu, 5 Sep 2024 13:36:38 -0700 [thread overview]
Message-ID: <ZtoWVjmSXfQStlkF@nvidia.com> (raw)
In-Reply-To: <d0e3a60713da4ff1bb10245e789ecf24@huawei.com>
Hi Shameer,
Thanks for the reply!
On Thu, Sep 05, 2024 at 12:55:52PM +0000, Shameerali Kolothum Thodi wrote:
> > The main takeaway from the discussion is to
> > 1) Turn the vSMMU module into a pluggable one, like intel-iommu
> > 2) Move the per-SMMU pxb bus and device auto-assign into libvirt
> >
> > Apart from the multi-vSMMU thing, there's basic nesting series:
> > 0) Keep updating to the latest kernel uAPIs to support nesting
>
> By this you mean the old HWPT based nested-smmuv3 support?
HWPT + vIOMMU. The for-viommu/virq branches that I shared in my
kernel series have those changes. Invalidations is done via the
vIOMMU infrastructure.
> >
> > I was trying to do all these three, but apparently too ambitious.
> > The kernel side of work is still taking a lot of my bandwidth. So
> > far I had almost-zero progress on task (1) and completely-zero on
> > task (2).
> >
> > <-- Help Needed --->
> > So, I'm wondering if anyone(s) might have some extra bandwidth in
> > the following months helping these two tasks, either of which can
> > be a standalone project I think.
> >
> > For task (0), I think I can keep updating the uAPI part, although
> > it'd need some help for reviews, which I was hoping to occur after
> > Intel sends the QEMU nesting backend patches. Once we know how big
> > the rework is going to be, we may need to borrow some help at that
> > point once again..
>
> I might have some bandwidth starting October and can take a look at
> task 1 above. I haven't gone through the VIOMMU API model completely
> yet and plan to do that soon.
Thank you! That'd be helpful! The major effort I think is in the
VIRT code also, where "-device nested-smmuv3" must tell the info
to build Device Tree or IORT.
The vIOMMU uAPI is not that complicated. That being said, I am
trying to add some kernel documentation for nested translation,
so hopefully this would be helpful in the near future.
> Also I am planning to attend KVM forum, so if there are anyone interested
> to have a chat on this, please let me know.
Wish I could make it to that. I think we will need another Oct
thread to get all of us aligned once again.
Regards
Nicolin
next prev parent reply other threads:[~2024-09-05 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 8:26 nested-smmuv3 topic, Sep 2024 Nicolin Chen
2024-09-05 12:55 ` Shameerali Kolothum Thodi via
2024-09-05 20:36 ` Nicolin Chen [this message]
2024-09-30 10:45 ` Shameerali Kolothum Thodi via
2024-09-30 19:43 ` Nicolin Chen
2024-09-06 11:50 ` Mostafa Saleh
2024-09-06 18:54 ` Nicolin Chen
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=ZtoWVjmSXfQStlkF@nvidia.com \
--to=nicolinc@nvidia.com \
--cc=abologna@redhat.com \
--cc=eric.auger@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=jgg@nvidia.com \
--cc=mdf@kernel.org \
--cc=mshavit@google.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=smostafa@google.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;
as well as URLs for NNTP newsgroup(s).