From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Carsten Otte <cotte@de.ibm.com>,
linux390@de.ibm.com, Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
lguest@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [RFC][PATCH] virtio: 64 bit features
Date: Tue, 12 Apr 2011 17:45:04 +0300 [thread overview]
Message-ID: <20110412144504.GB13850@redhat.com> (raw)
In-Reply-To: <4DA45C08.4070304@de.ibm.com>
On Tue, Apr 12, 2011 at 04:04:56PM +0200, Christian Borntraeger wrote:
> Am 11.04.2011 18:55, schrieb Michael S. Tsirkin:
>
> Looks mostly good, but
>
>
> > --- a/drivers/s390/kvm/kvm_virtio.c
> > +++ b/drivers/s390/kvm/kvm_virtio.c
> > @@ -82,13 +82,13 @@ static unsigned desc_size(const struct kvm_device_desc *desc)
> > static u32 kvm_get_features(struct virtio_device *vdev)
>
> This should be u64.
>
Ugh. Sure. Will fix, thanks!
> > {
> > unsigned int i;
> > - u32 features = 0;
> > + u64 features = 0;
> > struct kvm_device_desc *desc = to_kvmdev(vdev)->desc;
> > u8 *in_features = kvm_vq_features(desc);
> >
> > - for (i = 0; i < min(desc->feature_len * 8, 32); i++)
> > + for (i = 0; i < min(desc->feature_len * 8, 64); i++)
> > if (in_features[i / 8] & (1 << (i % 8)))
> > - features |= (1 << i);
> > + features |= (1ull << i);
> > return features;
> > }
prev parent reply other threads:[~2011-04-12 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 16:55 [RFC][PATCH] virtio: 64 bit features Michael S. Tsirkin
2011-04-12 3:25 ` Rusty Russell
2011-04-12 14:04 ` Christian Borntraeger
2011-04-12 14:45 ` Michael S. Tsirkin [this message]
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=20110412144504.GB13850@redhat.com \
--to=mst@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=lguest@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=rusty@rustcorp.com.au \
--cc=schwidefsky@de.ibm.com \
--cc=virtualization@lists.linux-foundation.org \
/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