From: David Hildenbrand <david@redhat.com>
To: Farhan Ali <alifm@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: borntraeger@de.ibm.com, thuth@redhat.com, cohuck@redhat.com,
kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v1 2/2] virtio-gpu-ccw: Create a virtio gpu device for the ccw bus
Date: Wed, 13 Sep 2017 14:09:15 +0200 [thread overview]
Message-ID: <4c65d9e0-df2c-6838-22dc-46415cdd82f1@redhat.com> (raw)
In-Reply-To: <a30f50d543182914e83cba5501f615a8ded2b858.1505225353.git.alifm@linux.vnet.ibm.com>
On 12.09.2017 16:26, Farhan Ali wrote:
> Wire up the virtio-gpu device for the CCW bus. The virtio-gpu
> is a virtio-1 device, so disable revision 0.
>
> Signed-off-by: Farhan Ali <alifm@linux.vnet.ibm.com>
> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
> ---
> hw/s390x/virtio-ccw.c | 54 +++++++++++++++++++++++++++++++++++++++++++++++++++
> hw/s390x/virtio-ccw.h | 10 ++++++++++
> 2 files changed, 64 insertions(+)
>
> diff --git a/hw/s390x/virtio-ccw.c b/hw/s390x/virtio-ccw.c
> index b1976fd..3078bf0 100644
> --- a/hw/s390x/virtio-ccw.c
> +++ b/hw/s390x/virtio-ccw.c
> @@ -1007,6 +1007,20 @@ static void virtio_ccw_crypto_realize(VirtioCcwDevice *ccw_dev, Error **errp)
> NULL);
> }
>
> +static void virtio_ccw_gpu_realize(VirtioCcwDevice *ccw_dev, Error **errp)
> +{
> + VirtIOGPUCcw *dev = VIRTIO_GPU_CCW(ccw_dev);
> + DeviceState *vdev = DEVICE(&dev->vdev);
> + Error *err = NULL;
> +
> + qdev_set_parent_bus(vdev, BUS(&ccw_dev->bus));
> + object_property_set_bool(OBJECT(vdev), true, "realized", &err);
> + if (err) {
> + error_propagate(errp, err);
> + return;
> + }
You can call error_propagate() unconditionally, it can deal with !err.
> +}
> +
> /* DeviceState to VirtioCcwDevice. Note: used on datapath,
> * be careful and test performance if you change this.
> */
> @@ -1616,6 +1630,45 @@ static const TypeInfo virtio_ccw_crypto = {
> .class_init = virtio_ccw_crypto_class_init,
> };
>
> +static Property virtio_ccw_gpu_properties[] = {
> + DEFINE_PROP_BIT("ioeventfd", VirtioCcwDevice, flags,
> + VIRTIO_CCW_FLAG_USE_IOEVENTFD_BIT, true),
> + DEFINE_PROP_UINT32("max_revision", VirtioCcwDevice, max_rev,
> + VIRTIO_CCW_MAX_REV),
> + DEFINE_PROP_END_OF_LIST(),
> +};
> +
> +static void virtio_ccw_gpu_instance_init(Object *obj)
> +{
> + VirtIOGPUCcw *dev = VIRTIO_GPU_CCW(obj);
> + VirtioCcwDevice *ccw_dev = VIRTIO_CCW_DEVICE(obj);
> +
> + ccw_dev->force_revision_1 = true;
> + virtio_instance_init_common(obj, &dev->vdev, sizeof(dev->vdev),
> + TYPE_VIRTIO_GPU);
> +}
> +
> +static void virtio_ccw_gpu_class_init(ObjectClass *klass, void *data)
> +{
> + DeviceClass *dc = DEVICE_CLASS(klass);
> + VirtIOCCWDeviceClass *k = VIRTIO_CCW_DEVICE_CLASS(klass);
> +
> + k->realize = virtio_ccw_gpu_realize;
> + k->exit = virtio_ccw_exit;
> + dc->reset = virtio_ccw_reset;
> + dc->props = virtio_ccw_gpu_properties;
> + dc->hotpluggable = false;
Wonder if hotplug could work?
--
Thanks,
David
next prev parent reply other threads:[~2017-09-13 12:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 14:26 [Qemu-devel] [PATCH v1 0/2] Virtio GPU for S390 Farhan Ali
2017-09-12 14:26 ` [Qemu-devel] [PATCH v1 1/2] virtio_gpu: Handle endian conversion Farhan Ali
2017-09-13 8:13 ` Gerd Hoffmann
2017-09-13 15:53 ` Farhan Ali
2017-09-14 8:44 ` Gerd Hoffmann
2017-09-12 14:26 ` [Qemu-devel] [PATCH v1 2/2] virtio-gpu-ccw: Create a virtio gpu device for the ccw bus Farhan Ali
2017-09-13 12:09 ` David Hildenbrand [this message]
2017-09-13 14:53 ` Gerd Hoffmann
2017-09-13 18:22 ` Thomas Huth
2017-09-13 14:31 ` Halil Pasic
2017-09-13 19:00 ` [Qemu-devel] [PATCH v1 0/2] Virtio GPU for S390 Thomas Huth
2017-09-13 19:11 ` Farhan Ali
2017-09-14 8:46 ` 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=4c65d9e0-df2c-6838-22dc-46415cdd82f1@redhat.com \
--to=david@redhat.com \
--cc=alifm@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).