[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fe018236-35b5-3bc1-6984-fca9537e47c7@linux.microsoft.com>
Date: Wed, 2 Mar 2022 10:13:34 -0800
From: Iouri Tarassov <iourit@...ux.microsoft.com>
To: Wei Liu <wei.liu@...nel.org>
Cc: kys@...rosoft.com, haiyangz@...rosoft.com, sthemmin@...rosoft.com,
linux-hyperv@...r.kernel.org, linux-kernel@...r.kernel.org,
spronovo@...rosoft.com, spronovo@...ux.microsoft.com,
gregkh@...uxfoundation.org
Subject: Re: [PATCH v3 26/30] drivers: hv: dxgkrnl: Offer and reclaim
allocations
On 3/2/2022 6:25 AM, Wei Liu wrote:
> On Tue, Mar 01, 2022 at 11:46:13AM -0800, Iouri Tarassov wrote:
> > Implement ioctls to offer and reclaim compute device allocations:
> > - LX_DXOFFERALLOCATIONS,
> > - LX_DXRECLAIMALLOCATIONS2
> >
> > When a user mode driver (UMD) does not need to access an allocation,
>
> What is a "user mode driver" in this context? Is that something that
> runs inside the guest?
Hi Wei,
The user mode driver runs inside the guest. This driver is written by
hardware vendors.
For example, the NVIDIA's Cuda runtime is considered a user mode driver.
The driver
provides a specific API to applications (like the Cuda API).
The cover letter explains the design of the virtual compute device
paravirtualization
model and describes all components, which are involved. I feel that I do
not need to
include explanation to every patch.
Thanks
Iouri
Powered by blists - more mailing lists