xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Oleksandr Andrushchenko <Oleksandr_Andrushchenko@epam.com>
To: Wei Liu <wl@xen.org>
Cc: Paul Durrant <paul@xen.org>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Paul Durrant <pdurrant@amazon.com>
Subject: Re: [PATCH v7 0/7] xl / libxl: named PCI pass-through devices
Date: Wed, 13 Jan 2021 08:05:30 +0000	[thread overview]
Message-ID: <28193c3e-9bea-134c-878b-e04a93d793cd@epam.com> (raw)
In-Reply-To: <20210105174642.2754-1-paul@xen.org>

Hi, Wei!

Is this series good to go? Could you please tell if it breaks anything?

Thank you in advance,

Oleksandr

On 1/5/21 7:46 PM, Paul Durrant wrote:
> From: Paul Durrant <pdurrant@amazon.com>
>
> These are re-worked versions of the remaining patches from v6 of the series
> that were reverted by commit ac6a0af3870b "Revert patches that break libxl
> API".
>
> Paul Durrant (7):
>    docs/man: modify xl(1) in preparation for naming of assignable devices
>    libxlu: introduce xlu_pci_parse_spec_string()
>    libxl: stop setting 'vdevfn' in pci_struct_fill()
>    libxl: add 'name' field to 'libxl_device_pci' in the IDL...
>    xl: support naming of assignable devices
>    docs/man: modify xl-pci-configuration(5) to add 'name' field to
>      PCI_SPEC_STRING
>    libxl / libxlu: support 'xl pci-attach/detach' by name
>
>   docs/man/xl-pci-configuration.5.pod |  25 ++-
>   docs/man/xl.1.pod.in                |  19 +-
>   tools/include/libxl.h               |   6 +
>   tools/include/libxlutil.h           |   8 +-
>   tools/libs/light/libxl_pci.c        | 133 ++++++++++++--
>   tools/libs/light/libxl_types.idl    |  13 +-
>   tools/libs/util/libxlu_pci.c        | 353 +++++++++++++++++++-----------------
>   tools/xl/xl_cmdtable.c              |  16 +-
>   tools/xl/xl_parse.c                 |   4 +-
>   tools/xl/xl_pci.c                   | 120 ++++++++----
>   10 files changed, 457 insertions(+), 240 deletions(-)
>

  parent reply	other threads:[~2021-01-13  8:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 17:46 [PATCH v7 0/7] xl / libxl: named PCI pass-through devices Paul Durrant
2021-01-05 17:46 ` [PATCH v7 1/7] docs/man: modify xl(1) in preparation for naming of assignable devices Paul Durrant
2021-01-05 17:46 ` [PATCH v7 2/7] libxlu: introduce xlu_pci_parse_spec_string() Paul Durrant
2021-01-05 17:46 ` [PATCH v7 3/7] libxl: stop setting 'vdevfn' in pci_struct_fill() Paul Durrant
2021-01-21 14:42   ` Wei Liu
2021-01-05 17:46 ` [PATCH v7 4/7] libxl: add 'name' field to 'libxl_device_pci' in the IDL Paul Durrant
2021-01-21 14:45   ` Wei Liu
2021-01-05 17:46 ` [PATCH v7 5/7] xl: support naming of assignable devices Paul Durrant
2021-01-21 14:49   ` Wei Liu
2021-01-05 17:46 ` [PATCH v7 6/7] docs/man: modify xl-pci-configuration(5) to add 'name' field to PCI_SPEC_STRING Paul Durrant
2021-01-05 17:46 ` [PATCH v7 7/7] libxl / libxlu: support 'xl pci-attach/detach' by name Paul Durrant
2021-01-21 14:50   ` Wei Liu
2021-01-13  8:05 ` Oleksandr Andrushchenko [this message]
2021-01-21 12:14 [PATCH v7 0/7] xl / libxl: named PCI pass-through devices Nastya Vicodin

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=28193c3e-9bea-134c-878b-e04a93d793cd@epam.com \
    --to=oleksandr_andrushchenko@epam.com \
    --cc=paul@xen.org \
    --cc=pdurrant@amazon.com \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    /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).