qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia.com>
To: Mostafa Saleh <smostafa@google.com>
Cc: Eric Auger <eric.auger@redhat.com>,
	Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
	<qemu-arm@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: Fri, 6 Sep 2024 11:54:33 -0700	[thread overview]
Message-ID: <ZttP6WDbrjwG46HJ@nvidia.com> (raw)
In-Reply-To: <ZtrsjoCvwZFYFEjS@google.com>

Hi Mostafa,

On Fri, Sep 06, 2024 at 11:50:38AM +0000, Mostafa Saleh wrote:

> > <-- 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.
> 
> I don’t have plans to work on qemu in the next months, most of my
> upstream focus will be on pKVM SMMUv3 support[1] in Linux which might
> overlap with some of the vSMMU work but in the kernel side.

Oh, that's a big work. I'll keep that under my radar.

> Otherwise, I’d be happy to review patches.

That'd be helpful indeed!

Thanks
Nicolin


      reply	other threads:[~2024-09-06 18:55 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
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 [this message]

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=ZttP6WDbrjwG46HJ@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).