From: Alexander Graf <agraf@suse.de>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>, KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Carsten Otte <cotte@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Sebastian Ott <sebott@linux.vnet.ibm.com>
Subject: Re: [PATCH 4/5] KVM: s390: Add a channel I/O based virtio transport driver.
Date: Tue, 30 Oct 2012 14:41:46 +0100 [thread overview]
Message-ID: <508FD91A.4060704@suse.de> (raw)
In-Reply-To: <20121030140304.3bcd3863@BR9GNB5Z>
On 10/30/2012 02:03 PM, Cornelia Huck wrote:
> On Mon, 29 Oct 2012 19:37:10 +0100
> Alexander Graf<agraf@suse.de> wrote:
>
>> On 29.10.2012, at 19:34, Cornelia Huck wrote:
>>
>>> On Mon, 29 Oct 2012 19:12:54 +0100
>>> Alexander Graf<agraf@suse.de> wrote:
>>>
>>>> On 29.10.2012, at 14:07, Cornelia Huck wrote:
>>>>> +static void virtio_ccw_kvm_notify(struct virtqueue *vq)
>>>>> +{
>>>>> + struct virtio_ccw_vq_info *info = vq->priv;
>>>>> + struct virtio_ccw_device *vcdev;
>>>>> + struct subchannel_id schid;
>>>>> + __u32 reg2;
>>>>> +
>>>>> + vcdev = to_vc_device(info->vq->vdev);
>>>>> + ccw_device_get_schid(vcdev->cdev,&schid);
>>>>> + reg2 = *(__u32 *)&schid;
>>>> That cast looks quite ugly. Can't you just access the field in there you need? Or if it's multiple fields do a union over them? Or assemble them by hand in C?
>>> I think the cast looks less ugly than using a union to morph it around.
>>> I want the schid with all fields filled out anyway, since this is what
>>> identifies the subchannel.
>> How about a helper function that returns a u32 for a struct subchannel_id in arch/s390/include/asm/schid.h then?
> This would just move the cast around, no? I don't think that would
> improve readability.
It would take it from the user of that struct close to the definition of
the struct. The fact that it's an ugly cast by then is an implementation
detail. This way it's a public API.
Alex
next prev parent reply other threads:[~2012-10-30 13:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 13:07 [PATCH 0/5] s390: Guest support for virtio-ccw Cornelia Huck
2012-10-29 13:07 ` [PATCH 1/5] KVM: s390: Handle hosts not supporting s390-virtio Cornelia Huck
2012-10-29 13:07 ` [PATCH 2/5] s390: Move css limits from drivers/s390/cio/ to include/asm/ Cornelia Huck
2012-10-29 13:07 ` [PATCH 3/5] s390: Add a mechanism to get the subchannel id Cornelia Huck
2012-10-29 13:07 ` [PATCH 4/5] KVM: s390: Add a channel I/O based virtio transport driver Cornelia Huck
2012-10-29 18:12 ` Alexander Graf
2012-10-29 18:34 ` Cornelia Huck
2012-10-29 18:37 ` Alexander Graf
2012-10-30 13:03 ` Cornelia Huck
2012-10-30 13:41 ` Alexander Graf [this message]
2012-10-30 14:00 ` Cornelia Huck
2012-10-30 14:05 ` Alexander Graf
2012-10-30 14:35 ` Cornelia Huck
2012-10-30 15:11 ` Alexander Graf
2012-10-29 13:07 ` [PATCH 5/5] KVM: s390: Split out early console code Cornelia Huck
2012-10-29 18:14 ` Alexander Graf
2012-10-30 12:59 ` Cornelia Huck
2012-10-30 13:43 ` Alexander Graf
2012-10-30 14:29 ` Cornelia Huck
2012-10-30 15:12 ` Alexander Graf
2012-10-30 15:35 ` Cornelia Huck
2012-10-30 15:42 ` Alexander Graf
2012-10-29 17:55 ` [PATCH 0/5] s390: Guest support for virtio-ccw Alexander Graf
2012-10-29 18:15 ` Cornelia Huck
2012-10-29 18:33 ` Alexander Graf
2012-10-30 13:04 ` Cornelia Huck
2012-10-30 13:43 ` Alexander Graf
-- strict thread matches above, loose matches on Subject: below --
2012-12-07 12:29 [PATCH v3 " Cornelia Huck
2012-12-07 12:29 ` [PATCH 4/5] KVM: s390: Add a channel I/O based virtio transport driver 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=508FD91A.4060704@suse.de \
--to=agraf@suse.de \
--cc=avi@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=schwidefsky@de.ibm.com \
--cc=sebott@linux.vnet.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).