From: Christoffer Dall <christoffer.dall@linaro.org>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
'Marc Zyngier' <marc.zyngier@arm.com>
Subject: Re: [PATCH 1/3] KVM: arm64: Implement vGICv3 distributor and redistributor access from userspace
Date: Mon, 31 Aug 2015 10:59:15 +0200 [thread overview]
Message-ID: <20150831085915.GI24113@cbox> (raw)
In-Reply-To: <013f01d0e3bf$8ed1fed0$ac75fc70$@samsung.com>
On Mon, Aug 31, 2015 at 10:35:05AM +0300, Pavel Fedin wrote:
> Hello!
>
> > > + len = vgic_v3_get_reg_size(attr);
> > > + if (len < 0)
> > > + return len;
> > >
> > > - return -ENXIO;
> > > + ret = vgic_v3_attr_regs_access(dev, attr, (len == 8) ? (void *)®64 :
> > > + (void *)®, len, false);
> >
> > this use of the ternary operator is terrible, but it should be solved if
> > you always use a u64 for the reg parameter.
>
> I also dislike this, but this is the best thing i could invent. This is dictated by put_user() and
> get_user(), which rely on typeof() of their arguments. Well, i could do some castings, but they are
> no less ugly, and would give more headache to bigendian systems.
> However, what about doing the same thing as GET/SET_ONE_REG does by just assuming that everything is
> 64-bit wide? This would automatically resolve two other issues you have commented on. By the way,
> handling it in userspace would also be simpler.
>
Sounds fine to me, definitely if you must do a cast doing it in a
function between typed variables is strictly preferred to passing void *
values between functions.
-Christoffer
next prev parent reply other threads:[~2015-08-31 8:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 12:56 [PATCH 0/3] KVM: arm64: Implement API for vGICv3 live migration Pavel Fedin
2015-08-28 12:56 ` [PATCH 1/3] KVM: arm64: Implement vGICv3 distributor and redistributor access from userspace Pavel Fedin
2015-08-30 16:42 ` Christoffer Dall
2015-08-31 7:35 ` Pavel Fedin
2015-08-31 8:59 ` Christoffer Dall [this message]
2015-09-01 13:52 ` Andre Przywara
2015-09-01 14:27 ` Pavel Fedin
2015-09-01 14:46 ` Peter Maydell
2015-08-28 12:56 ` [PATCH 2/3] KVM: arm64: Allow to use accessors in KVM_SET_ONE_REG and KVM_GET_ONE_REG Pavel Fedin
2015-08-28 12:56 ` [PATCH 3/3] KVM: arm64: Implement accessors for vGIC CPU interface registers Pavel Fedin
2015-08-30 16:50 ` Christoffer Dall
2015-08-30 18:39 ` Peter Maydell
2015-08-31 7:43 ` Pavel Fedin
2015-08-31 9:03 ` Christoffer Dall
2015-08-31 11:49 ` Pavel Fedin
2015-08-31 9:01 ` Christoffer Dall
2015-09-01 13:09 ` Pavel Fedin
2015-09-01 14:06 ` Christoffer Dall
2015-08-30 16:29 ` [PATCH 0/3] KVM: arm64: Implement API for vGICv3 live migration Christoffer Dall
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=20150831085915.GI24113@cbox \
--to=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=p.fedin@samsung.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).