From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
qemu-devel@nongnu.org, Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org, Claudio Imbrenda <imbrenda@linux.ibm.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH RFC 4/5] s390x: implement virtio-mem-ccw
Date: Thu, 9 Jul 2020 11:24:36 +0200 [thread overview]
Message-ID: <20200709112436.0ca1e95f.cohuck@redhat.com> (raw)
In-Reply-To: <20200708185135.46694-5-david@redhat.com>
On Wed, 8 Jul 2020 20:51:34 +0200
David Hildenbrand <david@redhat.com> wrote:
> Add a proper CCW proxy device, similar to the PCI variant.
>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
> hw/s390x/virtio-ccw-mem.c | 165 ++++++++++++++++++++++++++++++++++++++
> hw/s390x/virtio-ccw.h | 13 +++
> 2 files changed, 178 insertions(+)
> create mode 100644 hw/s390x/virtio-ccw-mem.c
(...)
> +static void virtio_ccw_mem_instance_init(Object *obj)
> +{
> + VirtIOMEMCcw *ccw_mem = VIRTIO_MEM_CCW(obj);
> + VirtIOMEMClass *vmc;
> + VirtIOMEM *vmem;
> +
I think you want
ccw_dev->force_revision_1 = true;
here (similar to forcing virtio-pci to modern-only.)
> + virtio_instance_init_common(obj, &ccw_mem->vdev, sizeof(ccw_mem->vdev),
> + TYPE_VIRTIO_MEM);
> +
> + ccw_mem->size_change_notifier.notify = virtio_ccw_mem_size_change_notify;
> + vmem = VIRTIO_MEM(&ccw_mem->vdev);
> + vmc = VIRTIO_MEM_GET_CLASS(vmem);
> + /*
> + * We never remove the notifier again, as we expect both devices to
> + * disappear at the same time.
> + */
> + vmc->add_size_change_notifier(vmem, &ccw_mem->size_change_notifier);
> +
> + object_property_add_alias(obj, VIRTIO_MEM_BLOCK_SIZE_PROP,
> + OBJECT(&ccw_mem->vdev),
> + VIRTIO_MEM_BLOCK_SIZE_PROP);
> + object_property_add_alias(obj, VIRTIO_MEM_SIZE_PROP, OBJECT(&ccw_mem->vdev),
> + VIRTIO_MEM_SIZE_PROP);
> + object_property_add_alias(obj, VIRTIO_MEM_REQUESTED_SIZE_PROP,
> + OBJECT(&ccw_mem->vdev),
> + VIRTIO_MEM_REQUESTED_SIZE_PROP);
> +}
(...)
(have not looked at the rest yet)
next prev parent reply other threads:[~2020-07-09 9:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 18:51 [PATCH RFC 0/5] s390x: initial support for virtio-mem David Hildenbrand
2020-07-08 18:51 ` [PATCH RFC 1/5] s390x: move setting of maximum ram size to machine init David Hildenbrand
2020-07-08 18:51 ` [PATCH RFC 2/5] s390x: implement diag260 David Hildenbrand
2020-07-09 10:37 ` Cornelia Huck
2020-07-09 17:54 ` David Hildenbrand
2020-07-10 8:32 ` David Hildenbrand
2020-07-10 8:41 ` David Hildenbrand
2020-07-10 9:19 ` Cornelia Huck
2020-07-13 11:54 ` Christian Borntraeger
2020-07-13 12:11 ` Cornelia Huck
2020-07-13 12:13 ` Christian Borntraeger
2020-07-09 10:52 ` Christian Borntraeger
2020-07-09 18:15 ` David Hildenbrand
2020-07-10 9:17 ` David Hildenbrand
2020-07-10 12:12 ` David Hildenbrand
2020-07-10 15:18 ` Heiko Carstens
2020-07-10 15:24 ` David Hildenbrand
2020-07-10 15:43 ` Heiko Carstens
2020-07-10 15:45 ` David Hildenbrand
2020-07-13 9:12 ` Heiko Carstens
2020-07-13 10:27 ` David Hildenbrand
2020-07-13 11:08 ` Christian Borntraeger
2020-07-15 9:42 ` David Hildenbrand
2020-07-15 10:43 ` Heiko Carstens
2020-07-15 11:21 ` David Hildenbrand
2020-07-15 11:34 ` Heiko Carstens
2020-07-15 11:42 ` David Hildenbrand
2020-07-15 16:14 ` Heiko Carstens
2020-07-15 17:38 ` David Hildenbrand
2020-07-15 17:51 ` David Hildenbrand
2020-07-20 14:43 ` Heiko Carstens
2020-07-20 15:43 ` David Hildenbrand
2020-07-08 18:51 ` [PATCH RFC 3/5] s390x: prepare device memory address space David Hildenbrand
2020-07-09 10:59 ` Cornelia Huck
2020-07-10 7:46 ` David Hildenbrand
2020-07-08 18:51 ` [PATCH RFC 4/5] s390x: implement virtio-mem-ccw David Hildenbrand
2020-07-09 9:24 ` Cornelia Huck [this message]
2020-07-09 9:26 ` David Hildenbrand
2020-07-08 18:51 ` [PATCH RFC 5/5] s390x: initial support for virtio-mem David Hildenbrand
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=20200709112436.0ca1e95f.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.