From: Pierre Morel <pmorel@linux.ibm.com>
To: Tony Krowiak <akrowiak@linux.ibm.com>, borntraeger@de.ibm.com
Cc: cohuck@redhat.com, agraf@suse.de, rth@twiddle.net,
david@redhat.com, qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
peter.maydell@linaro.org, pbonzini@redhat.com, mst@redhat.com,
eric.auger@redhat.com, pasic@linux.ibm.com
Subject: Re: [Qemu-devel] [PATCH v2 2/6] s390x/vfio: ap: Use the APdevice as a child of the APBus
Date: Fri, 30 Nov 2018 10:31:00 +0100 [thread overview]
Message-ID: <b2e78d9d-a939-1b5f-df6d-cdc143dfe380@linux.ibm.com> (raw)
In-Reply-To: <07102a0f-d37e-b9a6-047e-370bc3209686@linux.ibm.com>
On 29/11/2018 21:42, Tony Krowiak wrote:
> On 11/22/18 11:35 AM, Pierre Morel wrote:
>> Two good reasons to use the base device as a child of the
>> AP BUS:
>> - We can easily find the device without traversing the qtree.
>> - In case we have different APdevice instantiation, VFIO with
>> interception or emulation, we will need the APDevice as
>> a parent device.
>>
>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
>> ---
>> hw/s390x/ap-device.c | 22 ++++++++++++++++++++++
>> hw/vfio/ap.c | 16 ++++++----------
>> include/hw/s390x/ap-device.h | 2 ++
>> 3 files changed, 30 insertions(+), 10 deletions(-)
>>
>> diff --git a/hw/s390x/ap-device.c b/hw/s390x/ap-device.c
>> index f5ac8db..554d5aa 100644
>> --- a/hw/s390x/ap-device.c
>> +++ b/hw/s390x/ap-device.c
>> @@ -11,13 +11,35 @@
>> #include "qemu/module.h"
>> #include "qapi/error.h"
>> #include "hw/qdev.h"
>> +#include "hw/s390x/ap-bridge.h"
>> #include "hw/s390x/ap-device.h"
>> +APDevice *s390_get_ap(void)
>
> How about ap_get_device(void)?
Yes, keep same conventions.
>
>> +{
>> + static DeviceState *apb;
>
> Why static if you call s390_get_ap_bridge()
> to retrieve it without first checking for NULL?
static are initialized as NULL.
>
>> + BusState *bus;
>> + BusChild *child;
>> + static APDevice *ap;
>> +
>> + if (ap) {
>> + return ap;
>> + }
>> +
>> + apb = s390_get_ap_bridge();
>> + /* We have only a single child on the BUS */
>> + bus = qdev_get_child_bus(apb, TYPE_AP_BUS
>> + child = QTAILQ_FIRST(&bus->children);
>> + assert(child != NULL);
>> + ap = DO_UPCAST(APDevice, parent_obj, child->child);
>
> I received a comment from Thomas Huth in Message ID
> <2291104a-4cbf-e4fd-3496-fa0910beb96a@redhat.com>
> that DO_UPCAST should be avoided in new code. You should
> create an AP_DEVICE macro for this in ap-device.h
>
Thanks I will do.
Regards,
Pierre
--
Pierre Morel
Linux/KVM/QEMU in Böblingen - Germany
next prev parent reply other threads:[~2018-11-30 9:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 16:35 [Qemu-devel] [PATCH v2 0/6] s390x/vfio: VFIO-AP interrupt control interception Pierre Morel
2018-11-22 16:35 ` [Qemu-devel] [PATCH v2 1/6] s390x/vfio: ap: Finding the AP bridge Pierre Morel
2018-11-29 11:41 ` Cornelia Huck
2018-11-29 20:30 ` Tony Krowiak
2018-11-30 9:09 ` Pierre Morel
2018-11-22 16:35 ` [Qemu-devel] [PATCH v2 2/6] s390x/vfio: ap: Use the APdevice as a child of the APBus Pierre Morel
2018-11-29 11:45 ` Cornelia Huck
2018-11-29 12:36 ` Pierre Morel
2018-11-29 15:02 ` Tony Krowiak
2018-11-29 15:11 ` Cornelia Huck
2018-11-29 16:26 ` Pierre Morel
2018-11-29 20:42 ` Tony Krowiak
2018-11-30 9:31 ` Pierre Morel [this message]
2018-11-30 12:03 ` Pierre Morel
2018-11-30 15:58 ` Tony Krowiak
2018-12-03 8:02 ` Pierre Morel
2018-12-05 17:22 ` [Qemu-devel] [qemu-s390x] " Halil Pasic
2018-11-22 16:35 ` [Qemu-devel] [PATCH v2 3/6] s390x/vfio: ap: Linux uapi VFIO place holder Pierre Morel
2018-11-22 16:35 ` [Qemu-devel] [PATCH v2 4/6] s390x/cpumodel: Set up CPU model for AQIC interception Pierre Morel
2018-11-29 20:43 ` Tony Krowiak
2018-11-22 16:35 ` [Qemu-devel] [PATCH v2 5/6] s390x/vfio: ap: Definition for AP Adapter type Pierre Morel
2018-11-22 16:35 ` [Qemu-devel] [PATCH v2 6/6] s390x/vfio: ap: Implementing AP Queue Interrupt Control Pierre Morel
2018-11-29 21:53 ` Tony Krowiak
2018-11-30 8:36 ` Cornelia Huck
2018-11-30 11:54 ` Pierre Morel
2018-11-29 15:55 ` [Qemu-devel] [PATCH v2 0/6] s390x/vfio: VFIO-AP interrupt control interception Halil Pasic
2018-11-30 13:01 ` Pierre Morel
2018-11-30 13:31 ` Halil Pasic
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=b2e78d9d-a939-1b5f-df6d-cdc143dfe380@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=agraf@suse.de \
--cc=akrowiak@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=eric.auger@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
/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).