From: "BillXiang" <xiangwencheng@dayudpu.com>
To: "David Marchand" <david.marchand@redhat.com>
Cc: "Tyler Retzlaff" <roretzla@linux.microsoft.com>,
"Anatoly Burakov" <anatoly.burakov@intel.com>, <dev@dpdk.org>
Subject: Re: [PATCH v3] vfio: combine container_create and group_bind
Date: Wed, 10 Jul 2024 15:09:08 +0800 [thread overview]
Message-ID: <fba0cfc406f202976ef5ac5d129e08524ce06bbf.e9beb525.7e82.483d.bdfa.3e1fa847858a@feishu.cn> (raw)
In-Reply-To: <CAJFAV8wokT1NEWk4LD7nn_ydc9_HbsvkPo3Cn0m7Eq_w7w31BA@mail.gmail.com>
> From: "David Marchand"<david.marchand@redhat.com>
> Date: Tue, Jul 9, 2024, 16:49
> Subject: Re: [PATCH v3] vfio: combine container_create and group_bind
> To: "BillXiang"<xiangwencheng@dayudpu.com>
> Cc: "Tyler Retzlaff"<roretzla@linux.microsoft.com>, "Anatoly Burakov"<anatoly.burakov@intel.com>, <dev@dpdk.org>
> On Thu, Jul 4, 2024 at 9:48 AM BillXiang <xiangwencheng@dayudpu.com> wrote:
> >
> > From: BillXiang <xiangwencheng@dayudpu.com>
> >
> > For multi-devices in one group we can only create and bind to one
> > container. With this new function, device driver does not need to
> > save the binding info additionally between different devices.
> >
> > Signed-off-by: BillXiang <xiangwencheng@dayudpu.com>
>
> Thanks for the patch (don't forget to register to the dev@ mailing
> list when submitting patches).
>
> Could you please describe which driver benefits from it?
>
>
> --
> David Marchand
Thanks for your replay. I have registered now.
This patch addresses the issue for PCIe devices that have multiple PFs within
the same IOMMU group, a situation arising from the absence of ACS support.
If we want to use these PFs in vDPA, we have to know if the group has been
bound to a container by other PF upon each probe.
prev parent reply other threads:[~2024-07-10 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 11:59 BillXiang
2024-07-09 8:49 ` David Marchand
2024-07-10 7:09 ` BillXiang [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=fba0cfc406f202976ef5ac5d129e08524ce06bbf.e9beb525.7e82.483d.bdfa.3e1fa847858a@feishu.cn \
--to=xiangwencheng@dayudpu.com \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=roretzla@linux.microsoft.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).