From: Cornelia Huck <cohuck@redhat.com>
To: Tony Krowiak <akrowiak@linux.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
borntraeger@de.ibm.com, david@redhat.com,
bjsdjshi@linux.vnet.ibm.com, pmorel@linux.vnet.ibm.com,
alifm@linux.vnet.ibm.com, mjrosato@linux.vnet.ibm.com,
jjherne@linux.vnet.ibm.com, pasic@linux.vnet.ibm.com,
eskultet@redhat.com, berrange@redhat.com,
alex.williamson@redhat.com, eric.auger@redhat.com,
pbonzini@redhat.com, peter.maydell@linaro.org, agraf@suse.de,
rth@twiddle.net, akrowiak@linux.vnet.ibm.com,
fiuczy@linux.ibm.com, mimu@linux.ibm.com
Subject: Re: [Qemu-devel] [PATCH v11 5/6] s390x/vfio: ap: Introduce VFIO AP device
Date: Thu, 11 Oct 2018 12:30:35 +0200 [thread overview]
Message-ID: <20181011123035.5d97de0d.cohuck@redhat.com> (raw)
In-Reply-To: <20181010170309.12045-6-akrowiak@linux.ibm.com>
On Wed, 10 Oct 2018 13:03:07 -0400
Tony Krowiak <akrowiak@linux.ibm.com> wrote:
> +static void vfio_ap_class_init(ObjectClass *klass, void *data)
> +{
> + DeviceClass *dc = DEVICE_CLASS(klass);
> +
> + dc->props = vfio_ap_properties;
> + dc->vmsd = &vfio_ap_vmstate;
> + dc->desc = "VFIO-based AP device assignment";
> + dc->realize = vfio_ap_realize;
> + dc->unrealize = vfio_ap_unrealize;
> + dc->hotpluggable = false;
> + dc->reset = vfio_ap_reset;
> + dc->bus_type = TYPE_AP_BUS;
> +}
> +
> +static const TypeInfo vfio_ap_info = {
> + .name = VFIO_AP_DEVICE_TYPE,
> + .parent = AP_DEVICE_TYPE,
> + .instance_size = sizeof(VFIOAPDevice),
> + .class_init = vfio_ap_class_init,
> +};
> +
> +static void vfio_ap_type_init(void)
> +{
> + type_register_static(&vfio_ap_info);
> +}
> +
> +type_init(vfio_ap_type_init)
This device is missing the categorization, which was already requested
in a previous version. I added it to the misc category myself.
next prev parent reply other threads:[~2018-10-11 10:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 17:03 [Qemu-devel] [PATCH v11 0/6] s390x: vfio-ap: guest dedicated crypto adapters Tony Krowiak
2018-10-10 17:03 ` [Qemu-devel] [PATCH v11 1/6] linux-headers: linux header updates for AP support Tony Krowiak
2018-10-10 17:03 ` [Qemu-devel] [PATCH v11 2/6] s390x/cpumodel: Set up CPU model for AP device support Tony Krowiak
2018-10-10 17:03 ` [Qemu-devel] [PATCH v11 3/6] s390x/kvm: enable AP instruction interpretation for guest Tony Krowiak
2018-10-10 17:03 ` [Qemu-devel] [PATCH v11 4/6] s390x/ap: base Adjunct Processor (AP) object model Tony Krowiak
2018-10-10 17:03 ` [Qemu-devel] [PATCH v11 5/6] s390x/vfio: ap: Introduce VFIO AP device Tony Krowiak
2018-10-11 9:11 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2018-10-11 10:30 ` Cornelia Huck [this message]
2018-10-10 17:03 ` [Qemu-devel] [PATCH v11 6/6] s390: doc: detailed specifications for AP virtualization Tony Krowiak
2018-10-10 18:15 ` [Qemu-devel] [PATCH v11 0/6] s390x: vfio-ap: guest dedicated crypto adapters Christian Borntraeger
2018-10-11 8:12 ` [Qemu-devel] [qemu-s390x] " David Hildenbrand
2018-10-11 9:32 ` Thomas Huth
2018-10-11 9:48 ` [Qemu-devel] " Cornelia Huck
2018-10-11 10:00 ` Christian Borntraeger
2018-10-11 11:21 ` Pierre Morel
2018-10-11 11:41 ` Cornelia Huck
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=20181011123035.5d97de0d.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=akrowiak@linux.ibm.com \
--cc=akrowiak@linux.vnet.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=alifm@linux.vnet.ibm.com \
--cc=berrange@redhat.com \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=eric.auger@redhat.com \
--cc=eskultet@redhat.com \
--cc=fiuczy@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=mimu@linux.ibm.com \
--cc=mjrosato@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=schwidefsky@de.ibm.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).