From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH common v5 2/2] sysfstools: fix regression on binding to vfio-pci
Date: Mon, 11 Nov 2024 12:05:19 +0100 [thread overview]
Message-ID: <20241111110520.1803627-3-d.csapak@proxmox.com> (raw)
In-Reply-To: <20241111110520.1803627-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, by adding
a new parameter to file_write for this.
If we need to ignore other errors in the future, we can still make this
more generic.
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
changes from v4:
* adapt to $! extraction
src/PVE/SysFSTools.pm | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/src/PVE/SysFSTools.pm b/src/PVE/SysFSTools.pm
index 428e6ec..74f3242 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);
@@ -212,8 +213,9 @@ sub check_iommu_support{
}
# writes $buf into $filename, on success returns 1, on error returns 0 and warns
+# if $allow_existing is set, an EEXIST error will be handled as success
sub file_write {
- my ($filename, $buf) = @_;
+ my ($filename, $buf, $allow_existing) = @_;
my $fh = IO::File->new($filename, "w");
return undef if !$fh;
@@ -225,6 +227,7 @@ sub file_write {
if (defined($res)) {
return 1;
} elsif ($syserr) {
+ return 1 if $allow_existing && $syserr == EEXIST;
warn "error writing '$buf' to '$filename': $syserr\n";
}
@@ -310,7 +313,8 @@ 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);
+ # allow EEXIST for multiple devices with the same vendor/modelid
+ return undef if !file_write("$vfio_basedir/new_id", $data, 1);
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 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 11:05 [pve-devel] [PATCH common/qemu-server v5] improve sysfs write behaviour Dominik Csapak
2024-11-11 11:05 ` [pve-devel] [PATCH common v5 1/2] sysfstools: file_write: extend with logging Dominik Csapak
2024-11-11 11:05 ` Dominik Csapak [this message]
2024-11-11 11:05 ` [pve-devel] [PATCH qemu-server v5 1/1] pci: don't hard require resetting devices for passthrough Dominik Csapak
2024-11-11 19:34 ` [pve-devel] applied-series: [PATCH common/qemu-server v5] improve sysfs write behaviour Thomas Lamprecht
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=20241111110520.1803627-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