From: Tony Krowiak <akrowiak@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>,
Tony Krowiak <akrowiak@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com, borntraeger@de.ibm.com,
cohuck@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,
fiuczy@linux.ibm.com, mimu@linux.ibm.com
Subject: Re: [Qemu-devel] [PATCH v10 5/6] s390x/vfio: ap: Introduce VFIO AP device
Date: Wed, 10 Oct 2018 10:04:03 -0400 [thread overview]
Message-ID: <00b3fde5-2cd5-1b4d-85b3-4178c0070dbd@linux.ibm.com> (raw)
In-Reply-To: <cd6e06e4-0549-3c1a-96e4-2b2354b9866d@redhat.com>
On 10/09/2018 03:51 PM, David Hildenbrand wrote:
>
>> +static void vfio_ap_realize(DeviceState *dev, Error **errp)
>> +{
>> + int ret;
>> + char *mdevid;
>> + Error *local_err = NULL;
>> + VFIOGroup *vfio_group;
>> + APDevice *apdev = AP_DEVICE(dev);
>> + VFIOAPDevice *vapdev = VFIO_AP_DEVICE(apdev);
>> +
>> + vfio_group = vfio_ap_get_group(vapdev, &local_err);
>> + if (!vfio_group) {
>> + goto out_err;
>> + }
>> +
>> + vapdev->vdev.ops = &vfio_ap_ops;
>> + vapdev->vdev.type = VFIO_DEVICE_TYPE_AP;
>> + mdevid = basename(vapdev->vdev.sysfsdev);
>> + vapdev->vdev.name = g_strdup_printf("%s", mdevid);
>> + vapdev->vdev.dev = dev;
>> +
>> + ret = vfio_get_device(vfio_group, mdevid, &vapdev->vdev, &local_err);
>> + if (ret) {
>> + goto out_get_dev_err;
>> + }
>> +
>> + /* Enable hardware to intepret AP instructions executed on the guest */
>> + object_property_set_bool(OBJECT(qdev_get_machine()), true, "apie", NULL);
>> +
>
> I commented on the old version that this is wrong (if I am not starting
> to lose my memory). This has to go. (there is no such property, this
> will simply report an error we ignore)
>
> (can most probably be fixed when applying)
I don't recall whether you mentioned it, but I will fix it, or it can be
fixed when applied .... Connie?
>
next prev parent reply other threads:[~2018-10-10 14:04 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 17:52 [Qemu-devel] [PATCH v10 0/6] s390x: vfio-ap: guest dedicated crypto adapters Tony Krowiak
2018-10-09 17:52 ` [Qemu-devel] [PATCH v10 1/6] linux-headers: linux header updates for AP support Tony Krowiak
2018-10-10 8:01 ` Cornelia Huck
2018-10-09 17:52 ` [Qemu-devel] [PATCH v10 2/6] s390x/cpumodel: Set up CPU model for AP device support Tony Krowiak
2018-10-09 19:14 ` Christian Borntraeger
2018-10-09 19:48 ` David Hildenbrand
2018-10-10 13:50 ` Tony Krowiak
2018-10-10 8:11 ` Cornelia Huck
2018-10-10 8:12 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-10-10 11:31 ` [Qemu-devel] " Halil Pasic
2018-10-09 17:52 ` [Qemu-devel] [PATCH v10 3/6] s390x/kvm: enable AP instruction interpretation for guest Tony Krowiak
2018-10-09 19:48 ` David Hildenbrand
2018-10-10 7:19 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2018-10-10 8:12 ` Christian Borntraeger
2018-10-10 11:38 ` Halil Pasic
2018-10-10 11:53 ` Cornelia Huck
2018-10-09 17:52 ` [Qemu-devel] [PATCH v10 4/6] s390x/ap: base Adjunct Processor (AP) object model Tony Krowiak
2018-10-10 7:28 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2018-10-10 8:14 ` [Qemu-devel] " Cornelia Huck
2018-10-10 13:59 ` Tony Krowiak
2018-10-10 14:16 ` Cornelia Huck
2018-10-10 11:45 ` [Qemu-devel] [qemu-s390x] " Halil Pasic
2018-10-09 17:52 ` [Qemu-devel] [PATCH v10 5/6] s390x/vfio: ap: Introduce VFIO AP device Tony Krowiak
2018-10-09 19:51 ` David Hildenbrand
2018-10-10 7:29 ` Pierre Morel
2018-10-10 7:55 ` Cornelia Huck
2018-10-10 14:04 ` Tony Krowiak [this message]
2018-10-10 8:25 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2018-10-10 8:52 ` Cornelia Huck
2018-10-10 14:13 ` Tony Krowiak
2018-10-10 14:12 ` Tony Krowiak
2018-10-10 9:21 ` [Qemu-devel] " Cornelia Huck
2018-10-10 15:49 ` Tony Krowiak
2018-10-10 11:52 ` Halil Pasic
2018-10-10 12:33 ` Pierre Morel
2018-10-10 12:37 ` Pierre Morel
2018-10-10 12:49 ` Christian Borntraeger
2018-10-10 14:20 ` Tony Krowiak
2018-10-09 17:52 ` [Qemu-devel] [PATCH v10 6/6] s390: doc: detailed specifications for AP virtualization Tony Krowiak
2018-10-10 8:14 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2018-10-10 14:23 ` Tony Krowiak
2018-10-10 9:23 ` [Qemu-devel] " 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=00b3fde5-2cd5-1b4d-85b3-4178c0070dbd@linux.ibm.com \
--to=akrowiak@linux.ibm.com \
--cc=agraf@suse.de \
--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=cohuck@redhat.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).