From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH common v3 2/2] sysfstools: fix regression on binding to vfio-pci
Date: Mon, 11 Nov 2024 09:12:27 +0100 [thread overview]
Message-ID: <20241111081228.375675-3-d.csapak@proxmox.com> (raw)
In-Reply-To: <20241111081228.375675-1-d.csapak@proxmox.com>
when starting a vm with passthrough, we have to bind all normal pci
devices to vfio-pci. This happens by
* unbinding from current driver
* telling vfio-pci the 'vendorid modelid' combo so it knows this device
class can use the driver (by writing to 'new_id')
* actually binding the device to vfio-pci
if there are multiple devices of the same 'vendorid modelid' class on
the host (and passed through), only the first write to 'new_id' is
successful, all subsequent ones return EEXIST.
This could happen e.g. for setups with multiple GPUs that have the same
audio chip.
To fix this, ignore the EEXIST error for this write to new_id
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
changes from v2:
* fix typo in commit message
src/PVE/SysFSTools.pm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/PVE/SysFSTools.pm b/src/PVE/SysFSTools.pm
index 0aeff5f..c0a1b76 100644
--- a/src/PVE/SysFSTools.pm
+++ b/src/PVE/SysFSTools.pm
@@ -4,6 +4,7 @@ use strict;
use warnings;
use IO::File;
+use POSIX qw(EEXIST);
use PVE::Tools qw(file_read_firstline dir_glob_foreach);
@@ -314,7 +315,7 @@ sub pci_dev_bind_to_vfio {
return 1 if -d $testdir;
my $data = "$dev->{vendor} $dev->{device}";
- return undef if !file_write("$vfio_basedir/new_id", $data);
+ return undef if !file_write("$vfio_basedir/new_id", $data, [EEXIST]);
my $fn = "$pcisysfs/devices/$name/driver/unbind";
if (!file_write($fn, $name)) {
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-11-11 8:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 8:12 [pve-devel] [PATCH common/qemu-server v3] improve sysfs write behaviour Dominik Csapak
2024-11-11 8:12 ` [pve-devel] [PATCH common v3 1/2] sysfstools: file_write: extend with logging and ignore list Dominik Csapak
2024-11-11 9:02 ` Thomas Lamprecht
2024-11-11 8:12 ` Dominik Csapak [this message]
2024-11-11 8:12 ` [pve-devel] [PATCH qemu-server v3 1/1] pci: don't hard require resetting devices for passthrough Dominik Csapak
2024-11-11 9:05 ` Thomas Lamprecht
2024-11-11 10:20 ` [pve-devel] [PATCH common/qemu-server v3] improve sysfs write behaviour Dominik Csapak
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=20241111081228.375675-3-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.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