DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Dimon <dimon.zhao@nebula-matrix.com>, dev <dev@dpdk.org>
Cc: Sam <sam.chen@nebula-matrix.com>, Alvin <alvin.wang@nebula-matrix.com>
Subject: Re: 回复:[PATCH v1 0/8] Support VFIO cdev API in DPDK
Date: Wed, 29 Oct 2025 13:03:57 +0100	[thread overview]
Message-ID: <58ed8304-fecc-44c2-8926-97d9acfc9df3@intel.com> (raw)
In-Reply-To: <8659bfe9-b12c-4263-a130-01fdbb76d7fe.dimon.zhao@nebula-matrix.com>

On 10/29/2025 10:50 AM, Dimon wrote:
> Hello Anatoly,
> 
> I tested this patch series and encountered the same error on both Intel 
> E810 and Nebulamatrix NICs, as follows:
> 
> I used GDB for tracing and debugging, and found that there might be a 
> slight issue with the code of vfio_group_assign_device function? I won't 
> insist.
> 
> (1) vfio_device_create will alloc a vfio_device dev
> 
> (2) vfio_group_setup_device_fd will set dev->fd
> 
> (3) DEVICE_FOREACH_ACTIVE(cfg, idev) iterates through each idev->fd in 
> cfg to check if it is the same as dev->fd, but at this point idev is 
> actually dev.
> 
>       So it will report the error "Device 0000:08:00.0 already assigned 
> to this container".
> 

Hi Dimon,

Thank you for testing it! You're correct, of course. I shall fix it in 
v2, along with other planned fixes.

-- 
Thanks,
Anatoly

  reply	other threads:[~2025-10-29 12:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 16:43 [PATCH " Anatoly Burakov
2025-10-28 16:43 ` [PATCH v1 1/8] uapi: update to v6.17 and add iommufd.h Anatoly Burakov
2025-10-28 16:43 ` [PATCH v1 2/8] vfio: add container device assignment API Anatoly Burakov
2025-10-28 16:43 ` [PATCH v1 3/8] vhost: remove group-related API from drivers Anatoly Burakov
2025-10-28 16:43 ` [PATCH v1 4/8] vfio: do not setup the device on get device info Anatoly Burakov
2025-10-28 16:43 ` [PATCH v1 5/8] vfio: cleanup and refactor Anatoly Burakov
2025-10-28 16:43 ` [PATCH v1 6/8] vfio: introduce cdev mode Anatoly Burakov
2025-10-28 16:43 ` [PATCH v1 7/8] doc: deprecate VFIO group-based APIs Anatoly Burakov
2025-10-28 16:43 ` [PATCH v1 8/8] vfio: deprecate group-based API Anatoly Burakov
2025-10-29  9:50 ` 回复:[PATCH v1 0/8] Support VFIO cdev API in DPDK Dimon
2025-10-29 12:03   ` Burakov, Anatoly [this message]
2025-10-30  9:21 ` [PATCH " David Marchand
2025-10-30 10:11   ` Burakov, Anatoly

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=58ed8304-fecc-44c2-8926-97d9acfc9df3@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=alvin.wang@nebula-matrix.com \
    --cc=dev@dpdk.org \
    --cc=dimon.zhao@nebula-matrix.com \
    --cc=sam.chen@nebula-matrix.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).