From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cindy Lu <lulu@redhat.com>
Cc: yi.l.liu@intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, jgg@nvidia.com
Subject: Re: [RFC 0/7] vdpa: Add support for iommufd
Date: Thu, 26 Oct 2023 02:42:31 -0400 [thread overview]
Message-ID: <20231026024147-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230923170540.1447301-1-lulu@redhat.com>
On Sun, Sep 24, 2023 at 01:05:33AM +0800, Cindy Lu wrote:
> Hi All
> Really apologize for the delay, this is the draft RFC for
> iommufd support for vdpa, This code provides the basic function
> for iommufd support
>
> The code was tested and passed in device vdpa_sim_net
> The qemu code is
> https://gitlab.com/lulu6/gitlabqemutmp/-/tree/iommufdRFC
> The kernel code is
> https://gitlab.com/lulu6/vhost/-/tree/iommufdRFC
>
> ToDo
> 1. this code is out of date and needs to clean and rebase on the latest code
> 2. this code has some workaround, I Skip the check for
> iommu_group and CACHE_COHERENCY, also some misc issues like need to add
> mutex for iommfd operations
> 3. only test in emulated device, other modes not tested yet
>
> After addressed these problems I will send out a new version for RFC. I will
> provide the code in 3 weeks
What's the status here?
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2023-10-26 6:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230923170540.1447301-1-lulu@redhat.com>
2023-09-26 2:46 ` [RFC 0/7] vdpa: Add support for iommufd Jason Wang
[not found] ` <20230923170540.1447301-6-lulu@redhat.com>
2023-09-26 2:47 ` [RFC 5/7] vdpa: Add new vdpa_config_ops Jason Wang
[not found] ` <20230923170540.1447301-4-lulu@redhat.com>
2023-09-26 2:47 ` [RFC 3/7] vhost: Add 3 new uapi to support iommufd Jason Wang
[not found] ` <20230923170540.1447301-2-lulu@redhat.com>
2023-09-26 2:47 ` [RFC 1/7] vhost/iommufd: Add the functions " Jason Wang
2023-10-26 6:42 ` Michael S. Tsirkin [this message]
[not found] ` <CACLfguXstNSC20x=acDx20CXU3UksURDY04Z89DM_sNbGeTELQ@mail.gmail.com>
2023-10-26 6:49 ` [RFC 0/7] vdpa: Add support for iommufd Michael S. Tsirkin
2023-11-02 10:02 ` Michael S. Tsirkin
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=20231026024147-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=yi.l.liu@intel.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).