[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210204125123.GI4247@nvidia.com>
Date: Thu, 4 Feb 2021 08:51:23 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: Alexey Kardashevskiy <aik@...abs.ru>
CC: Max Gurtovoy <mgurtovoy@...dia.com>,
Cornelia Huck <cohuck@...hat.com>,
Alex Williamson <alex.williamson@...hat.com>,
Matthew Rosato <mjrosato@...ux.ibm.com>, <kvm@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <liranl@...dia.com>,
<oren@...dia.com>, <tzahio@...dia.com>, <leonro@...dia.com>,
<yarong@...dia.com>, <aviadye@...dia.com>, <shahafs@...dia.com>,
<artemp@...dia.com>, <kwankhede@...dia.com>, <ACurrid@...dia.com>,
<gmataev@...dia.com>, <cjia@...dia.com>, <yishaih@...dia.com>
Subject: Re: [PATCH 8/9] vfio/pci: use x86 naming instead of igd
On Thu, Feb 04, 2021 at 12:05:22PM +1100, Alexey Kardashevskiy wrote:
> It is system firmware (==bios) which puts stuff in the device tree. The
> stuff is:
> 1. emulated pci devices (custom pci bridges), one per nvlink, emulated by
> the firmware, the driver is "ibmnpu" and it is a part on the nvidia driver;
> these are basically config space proxies to the cpu's side of nvlink.
> 2. interconnect information - which of 6 gpus nvlinks connected to which
> nvlink on the cpu side, and memory ranges.
So what is this vfio_nvlink driver supposed to be bound to?
The "emulated pci devices"?
A real GPU function?
A real nvswitch function?
Something else?
Jason
Powered by blists - more mailing lists