qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Joe Clifford <joeclifford@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	David Hildenbrand <david@redhat.com>,
	qemu-devel@nongnu.org
Cc: Thomas Huth <thuth@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1 0/7] kvm: slot handling fixes (and small cleanups)
Date: Tue, 17 Oct 2017 01:06:01 +0100	[thread overview]
Message-ID: <aa684e24-d432-7cb9-3638-0ac802dffdda@gmail.com> (raw)
In-Reply-To: <3fea07b0-e3b6-c880-f7d2-ca152874ac7e@redhat.com>

On 16/10/17 17:20, Paolo Bonzini wrote:
> On 16/10/2017 16:42, David Hildenbrand wrote:
>> Hopefully this is the last bunch of fixes for the cleanup series.
>>
>> 1. log_start() was called before region_add(), which is wrong.
>> 2. I messed up the calculation of the delta when aligning the ram address
>>     (maybe we should simply also use ROUND_UP there ...).
>> 3. I think we could get log_start/log_stop/log_sync when we actually
>>     haven't registered a slot (due to trapping).
>> 4. Some further cleanups
>>
>> Available on: https://github.com/davidhildenbrand/qemu/commits/kvm_slot
>>
>> @Joe, if you could retest, this would be great! I updated the branch.
>>
>> David Hildenbrand (7):
>>    memory: call log_start after region_add
>>    kvm: fix alignment of ram address
>>    kvm: tolerate non-existing slot for log_start/log_stop/log_sync
>>    kvm: fix error message when failing to unregister slot
>>    kvm: region_add and region_del is not called on updates
>>    kvm: simplify kvm_align_section()
>>    memory: reuse section_from_flat_range()
>>
>>   accel/kvm/kvm-all.c | 39 ++++++++++++++-------------------------
>>   memory.c            | 16 +++++-----------
>>   2 files changed, 19 insertions(+), 36 deletions(-)
>>
> 
> Looks good!  I'll wait for testing results if they come soon.
> 
> Paolo
> 

Hi,

I've pulled the updates from David's repo and tested the same branch 
(kvm_slot) and they work beautifully for me. Thanks for fixing this David!

Joe

      reply	other threads:[~2017-10-17  0:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 14:42 [Qemu-devel] [PATCH v1 0/7] kvm: slot handling fixes (and small cleanups) David Hildenbrand
2017-10-16 14:42 ` [Qemu-devel] [PATCH v1 1/7] memory: call log_start after region_add David Hildenbrand
2017-10-16 14:42 ` [Qemu-devel] [PATCH v1 2/7] kvm: fix alignment of ram address David Hildenbrand
2017-10-16 14:42 ` [Qemu-devel] [PATCH v1 3/7] kvm: tolerate non-existing slot for log_start/log_stop/log_sync David Hildenbrand
2017-10-16 14:42 ` [Qemu-devel] [PATCH v1 4/7] kvm: fix error message when failing to unregister slot David Hildenbrand
2017-10-16 14:43 ` [Qemu-devel] [PATCH v1 5/7] kvm: region_add and region_del is not called on updates David Hildenbrand
2017-10-16 14:43 ` [Qemu-devel] [PATCH v1 6/7] kvm: simplify kvm_align_section() David Hildenbrand
2017-10-16 14:43 ` [Qemu-devel] [PATCH v1 7/7] memory: reuse section_from_flat_range() David Hildenbrand
2017-10-16 16:20 ` [Qemu-devel] [PATCH v1 0/7] kvm: slot handling fixes (and small cleanups) Paolo Bonzini
2017-10-17  0:06   ` Joe Clifford [this message]

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=aa684e24-d432-7cb9-3638-0ac802dffdda@gmail.com \
    --to=joeclifford@gmail.com \
    --cc=david@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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;
as well as URLs for NNTP newsgroup(s).