From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
tina.zhang@intel.com, Gerd Hoffmann <kraxel@redhat.com>,
vivek.kasireddy@intel.com, "Michael S. Tsirkin" <mst@redhat.com>
Subject: [PATCH v2 10/16] virtio-gpu: drop VIRGL() macro
Date: Fri, 30 Apr 2021 13:35:41 +0200 [thread overview]
Message-ID: <20210430113547.1816178-11-kraxel@redhat.com> (raw)
In-Reply-To: <20210430113547.1816178-1-kraxel@redhat.com>
Drops last virgl/opengl dependency from virtio-gpu-device.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
hw/display/virtio-gpu.c | 17 -----------------
1 file changed, 17 deletions(-)
diff --git a/hw/display/virtio-gpu.c b/hw/display/virtio-gpu.c
index 2c0065277ffd..34cf35127a3d 100644
--- a/hw/display/virtio-gpu.c
+++ b/hw/display/virtio-gpu.c
@@ -39,23 +39,6 @@ virtio_gpu_find_resource(VirtIOGPU *g, uint32_t resource_id);
static void virtio_gpu_cleanup_mapping(VirtIOGPU *g,
struct virtio_gpu_simple_resource *res);
-#ifdef CONFIG_VIRGL
-#include <virglrenderer.h>
-#define VIRGL(_g, _virgl, _simple, ...) \
- do { \
- if (_g->parent_obj.use_virgl_renderer) { \
- _virgl(__VA_ARGS__); \
- } else { \
- _simple(__VA_ARGS__); \
- } \
- } while (0)
-#else
-#define VIRGL(_g, _virgl, _simple, ...) \
- do { \
- _simple(__VA_ARGS__); \
- } while (0)
-#endif
-
void virtio_gpu_update_cursor_data(VirtIOGPU *g,
struct virtio_gpu_scanout *s,
uint32_t resource_id)
--
2.30.2
next prev parent reply other threads:[~2021-04-30 12:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 11:35 [PATCH v2 00/16] virtio-gpu: split into two devices Gerd Hoffmann
2021-04-30 11:35 ` [PATCH v2 01/16] virtio-gpu: rename virgl source file Gerd Hoffmann
2021-04-30 11:35 ` [PATCH v2 02/16] virtio-gpu: add virtio-gpu-gl-device Gerd Hoffmann
2021-04-30 11:35 ` [PATCH v2 03/16] virtio-gpu: move virgl realize + properties Gerd Hoffmann
2021-04-30 11:35 ` [PATCH v2 04/16] virtio-gpu: move virgl reset Gerd Hoffmann
2021-04-30 11:35 ` [PATCH v2 05/16] virtio-gpu: use class function for ctrl queue handlers Gerd Hoffmann
2021-04-30 11:35 ` [PATCH v2 06/16] virtio-gpu: move virgl handle_ctrl Gerd Hoffmann
2021-04-30 11:35 ` [PATCH v2 07/16] virtio-gpu: move virgl gl_flushed Gerd Hoffmann
2021-04-30 11:35 ` [PATCH v2 08/16] virtio-gpu: move virgl process_cmd Gerd Hoffmann
2021-04-30 11:35 ` [PATCH v2 09/16] virtio-gpu: move update_cursor_data Gerd Hoffmann
2021-04-30 11:35 ` Gerd Hoffmann [this message]
2021-04-30 11:35 ` [PATCH v2 11/16] virtio-gpu: move virtio-gpu-gl-device to separate module Gerd Hoffmann
2021-04-30 11:35 ` [PATCH v2 12/16] virtio-gpu: drop use_virgl_renderer Gerd Hoffmann
2021-04-30 11:35 ` [PATCH v2 13/16] virtio-gpu: move fields to struct VirtIOGPUGL Gerd Hoffmann
2021-04-30 11:35 ` [PATCH v2 14/16] virtio-gpu: add virtio-gpu-gl-pci Gerd Hoffmann
2021-04-30 11:35 ` [PATCH v2 15/16] modules: add have_vga Gerd Hoffmann
2021-04-30 11:35 ` [PATCH v2 16/16] virtio-gpu: add virtio-vga-gl Gerd Hoffmann
2021-04-30 13:03 ` [PATCH v2 00/16] virtio-gpu: split into two devices no-reply
2021-04-30 15:32 ` Marc-André Lureau
2021-05-03 9:32 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210430113547.1816178-11-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tina.zhang@intel.com \
--cc=vivek.kasireddy@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).