public inbox for kvm-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH v2 3/4] KVM: cleanup: remove kvm_get_dirty_log()
Date: Sun, 27 Jun 2010 07:32:11 +0000	[thread overview]
Message-ID: <4C26FE7B.9090406@redhat.com> (raw)
In-Reply-To: <20100623150134.9fb5915b.yoshikawa.takuya@oss.ntt.co.jp>

On 06/25/2010 10:25 PM, Alexander Graf wrote:
> On 23.06.2010, at 08:01, Takuya Yoshikawa wrote:
>
>    
>> kvm_get_dirty_log() is a helper function for kvm_vm_ioctl_get_dirty_log() which
>> is currently used by ia64 and ppc and the following is what it is doing:
>>
>>   - sanity checks
>>   - bitmap scan to check if the slot is dirty
>>   - copy_to_user()
>>
>> Considering the fact that x86 is not using this anymore and sanity checks must
>> be done before kvm_ia64_sync_dirty_log(), we can say that this is not working
>> for code sharing effectively. So we just remove this.
>>      
> This patch plus 4/4 broke dirty bitmap updating on PPC. I didn't get around to track down why, but I figured you should now. Is there any way to get you a PPC development box? A simple G4 or G5 should be 200$ on ebay by now :).
>    

Best to revert these patches and re-apply when fixed.

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2010-06-27  7:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23  6:01 [PATCH v2 3/4] KVM: cleanup: remove kvm_get_dirty_log() Takuya Yoshikawa
2010-06-23  8:48 ` Avi Kivity
2010-06-23  8:56 ` Takuya Yoshikawa
2010-06-23  9:00 ` Avi Kivity
2010-06-24  0:58 ` Marcelo Tosatti
2010-06-24  8:10 ` Avi Kivity
2010-06-25 19:25 ` Alexander Graf
2010-06-26  0:38 ` Takuya Yoshikawa
2010-06-26  0:55 ` Takuya Yoshikawa
2010-06-26  9:38 ` Alexander Graf
2010-06-27  7:32 ` Avi Kivity [this message]
2010-06-28  8:14 ` Takuya Yoshikawa
2010-06-28  9:36 ` 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=4C26FE7B.9090406@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm-ia64@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