From: Alex Williamson <alex.williamson@redhat.com>
To: Major Saheb <majosaheb@gmail.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Cornelia Huck <cohuck@redhat.com>,
Zhenzhong Duan <zhenzhong.duan@gmail.com>,
kvm@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: vfio-pci rejects binding to devices having same pcie vendor id and device id
Date: Thu, 8 Dec 2022 11:21:33 -0700 [thread overview]
Message-ID: <20221208112133.36efe5ff.alex.williamson@redhat.com> (raw)
In-Reply-To: <CANBBZXPBRr6On_3q0Ac0iQtrV5Bs84=GuHNvLz527T3ohHSuCw@mail.gmail.com>
On Thu, 8 Dec 2022 23:25:07 +0530
Major Saheb <majosaheb@gmail.com> wrote:
> Thanks Alex ,
> That works for me
>
> ~$ sudo driverctl --nosave set-override 0000:00:05.0 vfio-pci
> ~$ sudo driverctl --nosave set-override 0000:00:06.0 vfio-pci
> ~$ sudo driverctl --nosave set-override 0000:00:07.0 vfio-pci
> admin@node-1:~$ sudo nvme list
> Node SN Model
> Namespace Usage Format FW
> Rev
> --------------------- --------------------
> ---------------------------------------- ---------
> -------------------------- ---------------- --------
> /dev/nvme10n1 akqvf2-0_10 QEMU NVMe Ctrl
> 1 274.88 GB / 274.88 GB 512 B + 0 B 1.0
> /dev/nvme11n1 akqvf2-0_11 QEMU NVMe Ctrl
> 1 274.88 GB / 274.88 GB 512 B + 0 B 1.0
> /dev/nvme5n1 akqvf2-0_5 QEMU NVMe Ctrl
> 1 274.88 GB / 274.88 GB 512 B + 0 B 1.0
> /dev/nvme6n1 akqvf2-0_6 QEMU NVMe Ctrl
> 1 274.88 GB / 274.88 GB 512 B + 0 B 1.0
> /dev/nvme7n1 akqvf2-0_7 QEMU NVMe Ctrl
> 1 274.88 GB / 274.88 GB 512 B + 0 B 1.0
> /dev/nvme8n1 akqvf2-0_8 QEMU NVMe Ctrl
> 1 274.88 GB / 274.88 GB 512 B + 0 B 1.0
> /dev/nvme9n1 akqvf2-0_9 QEMU NVMe Ctrl
> 1 274.88 GB / 274.88 GB 512 B + 0 B 1.0
>
> I came across you blogspot after I fired the mail
> http://vfio.blogspot.com/2015/05/vfio-gpu-how-to-series-part-3-host.html
> Some should update https://docs.kernel.org/driver-api/vfio.html in
> public interest , If I knew how to do that I would do it,
Yes, that documentation is from before the driver_override method was
introduced. There's some non vfio specific documentation of
driver_override here:
https://docs.kernel.org/admin-guide/abi-testing.html?highlight=driver_override#abi-sys-bus-pci-devices-driver-override
Otherwise, documentation updates gladly accepted. This documentation
is part of the kernel source tree and follows the same process as
submitting code changes, outlined here:
https://docs.kernel.org/process/submitting-patches.html
The kvm@vger.kernel.org mailing list handles patches for vfio, but
please keep me in Cc if you submit something. Thanks,
Alex
next prev parent reply other threads:[~2022-12-08 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANBBZXPWe56VYJtzXdimEnkFgF+A=G15TXrd8Z5kBcUOGgHeRw@mail.gmail.com>
2022-12-08 16:50 ` vfio-pci rejects binding to devices having same pcie vendor id and device id Bjorn Helgaas
2022-12-08 17:25 ` Alex Williamson
2022-12-08 17:55 ` Major Saheb
2022-12-08 18:21 ` Alex Williamson [this message]
2022-12-08 18:48 ` Major Saheb
2022-12-12 4:44 ` Zhenzhong Duan
2022-12-12 9:26 ` Major Saheb
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=20221208112133.36efe5ff.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=helgaas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=majosaheb@gmail.com \
--cc=zhenzhong.duan@gmail.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