Re: [PATCH 1/4] virpci: changed the work with PCI via libpciaccess

2025-03-15 Thread Martin Kletzander
On Wed, Feb 12, 2025 at 09:42:44AM +0300, Alexander Shursha wrote: Sponsored by: Future Crew, LLC Signed-off-by: Alexander Shursha Hi, thanks for your contribution, but please be aware of our contribution guidelines: https://libvirt.org/hacking.html and some pages linked from there: https:/

Re: [PATCH 1/4] virpci: changed the work with PCI via libpciaccess

2025-03-07 Thread Martin Kletzander
On Fri, Mar 07, 2025 at 08:46:23AM +0300, Alexander Shursha wrote: Martin Kletzander writes: I understand you are switching to libpciaccess APIs from our manual handling of PCI devices. That does have the added benefit of working on FreeBSD, but adds a new dependency where it might not have b

Re: [PATCH 1/4] virpci: changed the work with PCI via libpciaccess

2025-03-06 Thread Alexander Shursha
Martin Kletzander writes: > I understand you are switching to libpciaccess APIs from our manual > handling of PCI devices. That does have the added benefit of working on > FreeBSD, but adds a new dependency where it might not have been. That > is probably fine, but some more explanation and rea

Re: [PATCH 1/4] virpci: changed the work with PCI via libpciaccess

2025-02-13 Thread Alexander Shursha
Daniel P. Berrangé writes: Done. > Please provide a commit message that describes the problem > you're solving with this refactoring. Likewise for other > commits in this series which all have empty commit messages. > >> Sponsored by: Future Crew, LLC > > While it is nice that they're sponsoring

[PATCH 1/4] virpci: changed the work with PCI via libpciaccess

2025-02-13 Thread Alexander Shursha
sysfs is used to get a list of PCI devices. It doesn't work under FreeBSD. The libpciaccess library provides cross-platform functions for accessing the PCI bus. Signed-off-by: Alexander Shursha --- src/meson.build | 1 + src/util/virpci.c | 465 ++-

Re: [PATCH 1/4] virpci: changed the work with PCI via libpciaccess

2025-02-12 Thread Daniel P . Berrangé
On Wed, Feb 12, 2025 at 02:54:17PM +0300, Alexander Shursha wrote: > Daniel P. Berrangé writes: > > Should I remove Sponsored from the commit log and add Copyright to the > file? > > * virpci.c: helper APIs for managing host PCI devices > * > * Copyright (C) 2009-2015 Red Hat, Inc. > + * C

Re: [PATCH 1/4] virpci: changed the work with PCI via libpciaccess

2025-02-12 Thread Alexander Shursha
Daniel P. Berrangé writes: Should I remove Sponsored from the commit log and add Copyright to the file? * virpci.c: helper APIs for managing host PCI devices * * Copyright (C) 2009-2015 Red Hat, Inc. + * Copyright (C) 2024-2025 Future Crew, LLC * * This library is free software; you ca

Re: [PATCH 1/4] virpci: changed the work with PCI via libpciaccess

2025-02-12 Thread Daniel P . Berrangé
On Wed, Feb 12, 2025 at 09:46:07AM +0300, Alexander Shursha wrote: Please provide a commit message that describes the problem you're solving with this refactoring. Likewise for other commits in this series which all have empty commit messages. > Sponsored by: Future Crew, LLC While it is nice th

Re: [PATCH 1/4] virpci: changed the work with PCI via libpciaccess

2025-02-12 Thread Peter Krempa
On Wed, Feb 12, 2025 at 09:46:07 +0300, Alexander Shursha wrote: > Sponsored by: Future Crew, LLC > Signed-off-by: Alexander Shursha As mentioned in the PR upstream the commit message serves as a place to describe the patch and most importantly the justification/why it's done, rather than serving

[PATCH 1/4] virpci: changed the work with PCI via libpciaccess

2025-02-11 Thread Alexander Shursha
Sponsored by: Future Crew, LLC Signed-off-by: Alexander Shursha --- src/meson.build | 1 + src/util/virpci.c | 464 ++-- tests/qemuhotplugtest.c | 11 +- tests/qemumemlocktest.c | 9 + tests/qemuxmlconftest.c | 9 + tests/virpcimock.c