public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: ehrhardt@linux.vnet.ibm.com, kvm@vger.kernel.org,
	borntraeger@de.ibm.com, cotte@de.ibm.com,
	heiko.carstens@de.ibm.com, schwidefsky@de.ibm.com
Subject: Re: [PATCH 4/4] kvm-s390: streamline memslot handling - v6
Date: Tue, 2 Jun 2009 09:32:56 -0300	[thread overview]
Message-ID: <20090602123256.GB4099@amt.cnet> (raw)
In-Reply-To: <4A223E62.3000204@redhat.com>

On Sun, May 31, 2009 at 11:22:58AM +0300, Avi Kivity wrote:
> ehrhardt@linux.vnet.ibm.com wrote:
>> From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
>>
>> *updates in v6*
>> - ensure the wait_on_bit waiter is notified
>> - move the reset of requests to kvm_vcpu_release to drop them early
>>
>> *updates in v5*
>> - ensure dropping vcpu all requests while freeing a vcpu
>>
>> *updates in v4*
>> - kickout only scheduled vcpus (its superfluous and wait might hang forever on
>>   not running vcpus)
>>
>>   
>
> v3 is already in (and pushed so I can't unapply), so please rebase on  
> top of current git.

Christian, 

Seems a good step toward further unification. Can you please rebase as
requested? 


  reply	other threads:[~2009-06-02 12:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 10:58 [PATCH 1/4] kvm-s390: infrastructure to kick vcpus out of guest state - v3 ehrhardt
2009-05-29 10:58 ` [PATCH 2/4] kvm-s390: fix interruption caused by signal - v2 ehrhardt
2009-05-29 10:58 ` [PATCH 3/4] kvm-s390: update vcpu->cpu ehrhardt
2009-05-29 10:58 ` [PATCH 4/4] kvm-s390: streamline memslot handling - v6 ehrhardt
2009-05-31  8:22   ` Avi Kivity
2009-06-02 12:32     ` Marcelo Tosatti [this message]
2009-06-02 14:23       ` Christian Ehrhardt

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=20090602123256.GB4099@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=avi@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cotte@de.ibm.com \
    --cc=ehrhardt@linux.vnet.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=schwidefsky@de.ibm.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