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
-
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,
VIRTIO_GPU_CMD_GET_CAPSET,
VIRTIO_GPU_CMD_GET_EDID,
+V
On Wed, 27 Nov 2019 16:33:07 -0500
"Michael S. Tsirkin" wrote:
> When we mean PCI register we should say BAR.
> When we mean a virtio config register we should say \field{cap.bar}.
>
> Finally, offset_hi/length_hi are not within the cap structure.
>
> Tweak wording slightly: "A,B,C" are fields,
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 at
Add some notes about fetching the EDID information.
Signed-off-by: Gerd Hoffmann
---
virtio-gpu.tex | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/virtio-gpu.tex b/virtio-gpu.tex
index af4ca610d235..15dbf9f2ec82 100644
--- a/virtio-gpu.tex
+++ b/virtio-gpu.tex
Hi,
> Is the intent that any virtio device has to support all the same formats?
No.
> So it looks to me like all the formats should be part of the spec, and some
> device capabilities should indicate which ones the device accepts.
There is a per-stream bitmask in device config indicating whic
