public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH common v2 2/2] sysfstools: fix regression on binding to vfio-pci
Date: Fri, 8 Nov 2024 11:26:06 +0100	[thread overview]
Message-ID: <20241108112606.0d47d65d@rosa.proxmox.com> (raw)
In-Reply-To: <20241108093300.1023657-3-d.csapak@proxmox.com>

On Fri,  8 Nov 2024 10:32:59 +0100
Dominik Csapak <d.csapak@proxmox.com> wrote:

> 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 to it know this device
s/to it know/so it knows/ ?
>   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>
> ---
>  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 156fee6..569693e 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);
>  
> @@ -317,7 +318,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)) {



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2024-11-08 10:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08  9:32 [pve-devel] [PATCH common/qemu-server v2] improve sysfs write behaviour Dominik Csapak
2024-11-08  9:32 ` [pve-devel] [PATCH common v2 1/2] sysfstools: file_write: extend with logging and ignore list Dominik Csapak
2024-11-08 10:24   ` Stoiko Ivanov
2024-11-08  9:32 ` [pve-devel] [PATCH common v2 2/2] sysfstools: fix regression on binding to vfio-pci Dominik Csapak
2024-11-08 10:26   ` Stoiko Ivanov [this message]
2024-11-08  9:33 ` [pve-devel] [PATCH qemu-server v2 1/1] pci: don't hard require resetting devices for passthrough Dominik Csapak
2024-11-08 10:28 ` [pve-devel] [PATCH common/qemu-server v2] improve sysfs write behaviour Stoiko Ivanov
2024-11-11  8:13 ` 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=20241108112606.0d47d65d@rosa.proxmox.com \
    --to=s.ivanov@proxmox.com \
    --cc=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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal