linux-kernel - Re: [PATCH v2] virtio-gpu: add VIRTIO_GPU_F

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1BA83F18-87E5-4B01-A2D9-01777078B637@redhat.com>
Date:   Fri, 5 Oct 2018 16:38:11 +0200
From:   Christophe de Dinechin <cdupontd@...hat.com>
To:     Gerd Hoffmann <kraxel@...hat.com>
Cc:     virtio-dev@...hat.com, kvm@...r.kernel.org,
        dri-devel@...ts.freedesktop.org, David Airlie <airlied@...ux.ie>,
        "Michael S. Tsirkin" <mst@...hat.com>,
        Jason Wang <jasowang@...hat.com>,
        "open list:VIRTIO GPU DRIVER" 
        <virtualization@...ts.linux-foundation.org>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] virtio-gpu: add VIRTIO_GPU_F_EDID feature



> On 5 Oct 2018, at 14:51, Gerd Hoffmann <kraxel@...hat.com> wrote:
> 
> The feature allows the guest request an EDID blob (describing monitor
> capabilities) for a given scanout (aka virtual monitor connector).
> 
> It brings a new command message, which has just a scanout field (beside
> the standard virtio-gpu header) and a response message which carries the
> EDID data.
> 
> Signed-off-by: Gerd Hoffmann <kraxel@...hat.com>
> ---
> include/uapi/linux/virtio_gpu.h | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
> 
> diff --git a/include/uapi/linux/virtio_gpu.h b/include/uapi/linux/virtio_gpu.h
> index f43c3c6171..1cef1ff339 100644
> --- a/include/uapi/linux/virtio_gpu.h
> +++ b/include/uapi/linux/virtio_gpu.h
> @@ -41,6 +41,7 @@
> #include <linux/types.h>
> 
> #define VIRTIO_GPU_F_VIRGL 0
> +#define VIRTIO_GPU_F_EDID  1
> 
> enum virtio_gpu_ctrl_type {
> 	VIRTIO_GPU_UNDEFINED = 0,
> @@ -56,6 +57,7 @@ enum virtio_gpu_ctrl_type {
> 	VIRTIO_GPU_CMD_RESOURCE_DETACH_BACKING,
> 	VIRTIO_GPU_CMD_GET_CAPSET_INFO,
> 	VIRTIO_GPU_CMD_GET_CAPSET,
> +	VIRTIO_GPU_CMD_GET_EDID,
> 
> 	/* 3d commands */
> 	VIRTIO_GPU_CMD_CTX_CREATE = 0x0200,
> @@ -76,6 +78,7 @@ enum virtio_gpu_ctrl_type {
> 	VIRTIO_GPU_RESP_OK_DISPLAY_INFO,
> 	VIRTIO_GPU_RESP_OK_CAPSET_INFO,
> 	VIRTIO_GPU_RESP_OK_CAPSET,
> +	VIRTIO_GPU_RESP_OK_EDID,
> 
> 	/* error responses */
> 	VIRTIO_GPU_RESP_ERR_UNSPEC = 0x1200,
> @@ -291,6 +294,20 @@ struct virtio_gpu_resp_capset {
> 	__u8 capset_data[];
> };
> 
> +/* VIRTIO_GPU_CMD_GET_EDID */
> +struct virtio_gpu_get_edid {
> +	struct virtio_gpu_ctrl_hdr hdr;
> +	__le32 scanout;
> +};
> +
> +/* VIRTIO_GPU_RESP_OK_EDID */
> +struct virtio_gpu_resp_edid {
> +	struct virtio_gpu_ctrl_hdr hdr;
> +	__le32 scanout;
> +	__le32 size;
> +	__u8 edid[1024];

Wouldn’t it be enough to stick to EDID 2.0 (256 bytes)?

If not, maybe add comment to explain why you chose 1024.

> +};
> +
> #define VIRTIO_GPU_EVENT_DISPLAY (1 << 0)
> 
> struct virtio_gpu_config {
> -- 
> 2.9.3
>