From: Avi Kivity <avi@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] qemu-kvm: fix __user export
Date: Wed, 02 Dec 2009 15:16:47 +0200 [thread overview]
Message-ID: <4B1668BF.5@redhat.com> (raw)
In-Reply-To: <200912021409.28573.borntraeger@de.ibm.com>
On 12/02/2009 03:09 PM, Christian Borntraeger wrote:
> Am Montag 30 November 2009 13:02:08 schrieb Michael S. Tsirkin:
>
>> __user macro does not appear in exported headers
>> and should not be in headers qemu-kvm includes.
>>
>> Signed-off-by: Michael S. Tsirkin<mst@redhat.com>
>> ---
>> kvm/include/linux/kvm.h | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/kvm/include/linux/kvm.h b/kvm/include/linux/kvm.h
>> index 92045a9..db10887 100644
>> --- a/kvm/include/linux/kvm.h
>> +++ b/kvm/include/linux/kvm.h
>> @@ -309,7 +309,7 @@ struct kvm_dirty_log {
>> __u32 slot;
>> __u32 padding1;
>> union {
>> - void __user *dirty_bitmap; /* one bit per page */
>> + void *dirty_bitmap; /* one bit per page */
>> __u64 padding2;
>> };
>> };
>>
>>
> Huh?
> Doesnt that create a sparse warning? You already mention that the exported
> header does not contain __user and that is perfectly ok:
> - for the kernel dirty_bitmap is in the user address space, so we need the __user
> - userspace does not know and need the __user so it is removed during
> headers_install.
>
>
This is in the copy of the headers that qemu-kvm.git carries, not the
kernel master.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-12-02 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 12:02 [PATCH] qemu-kvm: fix __user export Michael S. Tsirkin
2009-12-02 13:04 ` Avi Kivity
2009-12-02 13:09 ` Christian Borntraeger
2009-12-02 13:16 ` Avi Kivity [this message]
2009-12-02 13:20 ` Christian Borntraeger
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=4B1668BF.5@redhat.com \
--to=avi@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.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