Hi,
> > > Do we already have a mechanism
> > > to import memory to virtio-gpu via importing a bo handle from somewhere
> > > else?
> >
> > Inside the guest? Import is not working yet, that needs another update
> > (blob resources) due to current virtio-gpu resources requiring a format
> > at
On Tue, Dec 3, 2019 at 1:33 AM Gerd Hoffmann wrote:
> On Mon, Dec 02, 2019 at 09:24:31AM -0800, Frank Yang wrote:
> > Interesting; what's the use case for this?
>
> Mostly reduce data copying.
>
> > Do we already have a mechanism
> > to import memory to virtio-gpu via importing a bo handle from
On Mon, Dec 02, 2019 at 09:24:31AM -0800, Frank Yang wrote:
> Interesting; what's the use case for this?
Mostly reduce data copying.
> Do we already have a mechanism
> to import memory to virtio-gpu via importing a bo handle from somewhere
> else?
Inside the guest? Import is not working yet,
Interesting; what's the use case for this? Do we already have a mechanism
to import memory to virtio-gpu via importing a bo handle from somewhere
else?
On Thu, Nov 28, 2019 at 9:37 PM Gerd Hoffmann wrote:
> On Thu, Nov 28, 2019 at 07:04:23PM +0100, Matti Moell wrote:
> > Hi Gerd,
> >
> > I
On Thu, Nov 28, 2019 at 07:04:23PM +0100, Matti Moell wrote:
> Hi Gerd,
>
> I really like this!
>
> On 28.11.19 14:19, Gerd Hoffmann wrote:
> > @@ -186,6 +211,7 @@ \subsubsection{Device Operation: Request
> > header}\label{sec:Device Types / GPU De
> > VIRTIO_GPU_CMD_GET_CAPSET_INFO,
On 11/28/19 14:19, Gerd Hoffmann wrote:
> +resources. Normal resources have both a guest buffer and host buffer
> +buffer for the resource and the VIRTIO_GPU_CMD_TRANSFER_* commands are
typo: "buffer\nbuffer"
Thanks
Laszlo
-
This patch adds a new virtio feature for shared resources.
Shared resources are allocated by the guest from normal ram, like
traditional resources. They can be used by the guest almost like
traditional resources, the only exception is that shared resources can
only be used with backing storage
