From: Avi Kivity <avi@redhat.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 26/27] Enable 32bit dirty log pointers on 64bit host
Date: Wed, 30 Sep 2009 13:29:12 +0000 [thread overview]
Message-ID: <4AC35D28.5000103@redhat.com> (raw)
In-Reply-To: <1254212303-8737-27-git-send-email-agraf@suse.de>
On 09/30/2009 03:17 PM, Avi Kivity wrote:
>> {
>> struct page *page[1];
>> @@ -2331,7 +2374,7 @@ static int kvm_vm_mmap(struct file *file,
>> struct vm_area_struct *vma)
>> static struct file_operations kvm_vm_fops = {
>> .release = kvm_vm_release,
>> .unlocked_ioctl = kvm_vm_ioctl,
>> - .compat_ioctl = kvm_vm_ioctl,
>> + .compat_ioctl = kvm_vm_compat_ioctl,
>> .mmap = kvm_vm_mmap,
>> };
> static int kvm_vm_fault(struct vm_area_struct *vma, struct vm_fault
> *vmf)
>
> This is a bit painful - I tried to avoid compat_ioctl. Maybe it's
> better to have dirty_bitmap_virt, given no existing users are impacted.
>
But that misses compat_ptr(). So it looks like we'll need compat_ioctl.
Patch looks fine, except s/log.log/log/. I'd also sizeof(compat_log)
instead of sizeof(log) to avoid frightening reviewers.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-09-30 13:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 8:18 [PATCH 26/27] Enable 32bit dirty log pointers on 64bit host Alexander Graf
2009-09-29 9:14 ` Avi Kivity
2009-09-29 9:17 ` Alexander Graf
2009-09-29 13:25 ` Avi Kivity
2009-09-29 14:08 ` Alexander Graf
2009-09-29 16:29 ` Alexander Graf
2009-09-29 16:42 ` Avi Kivity
2009-09-29 17:09 ` Alexander Graf
2009-09-30 12:04 ` Arnd Bergmann
2009-09-30 13:17 ` Avi Kivity
2009-09-30 13:29 ` Avi Kivity [this message]
2009-10-20 10:09 ` Alexander Graf
2009-10-20 13:23 ` Avi Kivity
2009-10-20 13:28 ` Alexander Graf
2009-10-20 13:32 ` Avi Kivity
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=4AC35D28.5000103@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ppc@vger.kernel.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