On 04/03/2013 05:07:30 PM, Scott Wood wrote:
On 04/03/2013 04:58:56 PM, Alexander Graf wrote:
Am 03.04.2013 um 23:38 schrieb Scott Wood <scottw...@freescale.com>:
> On 04/03/2013 11:19:42 AM, Alexander Graf wrote:
>> On 03.04.2013, at 03:57, Scott Wood wrote:
>> > + switch (attr->group) {
>> > + case KVM_DEV_MPIC_GRP_MISC:
>> > + switch (attr->attr) {
>> > + case KVM_DEV_MPIC_BASE_ADDR:
>> > + mutex_lock(&opp->kvm->slots_lock);
>> > + attr64 = opp->reg_base;
>> > + mutex_unlock(&opp->kvm->slots_lock);
>> > +
>> > + if (copy_to_user((u64 __user *)(long)attr->addr,
>> > + &attr64, sizeof(u64)))
>> u64 is tricky with put_user on 32bit hosts, so here copy_to_user
makes sense
>
> What are the issues with put_user? It looks like it's supported
with a pair of "stw" instructions.
Oh? Last time I tried to use get/put_user for one_reg it failed on
ppc32. So maybe the u64 support is new?
Not new according to git -- though I haven't tried to use it yet;
maybe it's broken.
Yeah, it's broken. :-P
__get_user_size() looks OK, but __get_user_check/nocheck() goes through
an intermediary "unsigned long __gu_val".
There's a separate __get_user64_nocheck() that uses "long long", but no
"check" variant, no "put", and it's only available in 32-bit builds.
And it's not used anywhere (barring ungreppable token-pasting magic).
Sigh.
-Scott
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
