All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Hao Sun <sunhao.th@gmail.com>
Subject: Re: [PATCH 0/3] KVM: Fixes and a cleanup for coalesced MMIO
Date: Sat, 17 Apr 2021 15:11:15 +0200	[thread overview]
Message-ID: <159d0b9c-c50b-3829-0212-acb30d6c1ae0@redhat.com> (raw)
In-Reply-To: <20210412222050.876100-1-seanjc@google.com>

On 13/04/21 00:20, Sean Christopherson wrote:
> Fix two bugs that are exposed if unregistered a device on an I/O bus fails
> due to OOM.  Tack on opportunistic cleanup in the related code.
>   
> Sean Christopherson (3):
>    KVM: Destroy I/O bus devices on unregister failure _after_ sync'ing
>      SRCU
>    KVM: Stop looking for coalesced MMIO zones if the bus is destroyed
>    KVM: Add proper lockdep assertion in I/O bus unregister
> 
>   include/linux/kvm_host.h  |  4 ++--
>   virt/kvm/coalesced_mmio.c | 19 +++++++++++++++++--
>   virt/kvm/kvm_main.c       | 26 ++++++++++++++++----------
>   3 files changed, 35 insertions(+), 14 deletions(-)
> 

Queued, thanks.

Paolo


      parent reply	other threads:[~2021-04-17 13:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 22:20 [PATCH 0/3] KVM: Fixes and a cleanup for coalesced MMIO Sean Christopherson
2021-04-12 22:20 ` [PATCH 1/3] KVM: Destroy I/O bus devices on unregister failure _after_ sync'ing SRCU Sean Christopherson
2021-04-15 21:50   ` Jim Mattson
2021-04-12 22:20 ` [PATCH 2/3] KVM: Stop looking for coalesced MMIO zones if the bus is destroyed Sean Christopherson
2021-04-15 22:22   ` Jim Mattson
2021-04-12 22:20 ` [PATCH 3/3] KVM: Add proper lockdep assertion in I/O bus unregister Sean Christopherson
2021-04-15 21:58   ` Jim Mattson
2021-04-15 22:15     ` Sean Christopherson
2021-04-17 13:11 ` Paolo Bonzini [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=159d0b9c-c50b-3829-0212-acb30d6c1ae0@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanjc@google.com \
    --cc=sunhao.th@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.