From: Alexander Graf <agraf@suse.de>
To: Paul Mackerras <paulus@samba.org>
Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] KVM: PPC: Memslot handling improvements
Date: Thu, 13 Sep 2012 16:43:12 +0000 [thread overview]
Message-ID: <50520D20.3000609@suse.de> (raw)
In-Reply-To: <20120911232614.GA32642@bloggs.ozlabs.ibm.com>
On 09/12/2012 01:26 AM, Paul Mackerras wrote:
> This series of 3 patches fixes up the memslot handling for Book3S HV
> style KVM on powerpc, making slot deletion and modification work and
> making sure we have the appropriate SRCU synchronization against
> updates.
>
> The series is against the next branch of the kvm tree. These patches
> have all been posted before, but I am reposting them now because
> Marcelo's patches that are a prerequisite for the third patch
> (2df72e9bc4, "KVM: split kvm_arch_flush_shadow" and 12d6e7538e, "KVM:
> perform an invalid memslot step for gpa base change") have now gone
> into the kvm next branch.
Thanks, applied all to kvm-ppc-next.
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Graf <agraf@suse.de>
To: Paul Mackerras <paulus@samba.org>
Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] KVM: PPC: Memslot handling improvements
Date: Thu, 13 Sep 2012 18:43:12 +0200 [thread overview]
Message-ID: <50520D20.3000609@suse.de> (raw)
In-Reply-To: <20120911232614.GA32642@bloggs.ozlabs.ibm.com>
On 09/12/2012 01:26 AM, Paul Mackerras wrote:
> This series of 3 patches fixes up the memslot handling for Book3S HV
> style KVM on powerpc, making slot deletion and modification work and
> making sure we have the appropriate SRCU synchronization against
> updates.
>
> The series is against the next branch of the kvm tree. These patches
> have all been posted before, but I am reposting them now because
> Marcelo's patches that are a prerequisite for the third patch
> (2df72e9bc4, "KVM: split kvm_arch_flush_shadow" and 12d6e7538e, "KVM:
> perform an invalid memslot step for gpa base change") have now gone
> into the kvm next branch.
Thanks, applied all to kvm-ppc-next.
Alex
next prev parent reply other threads:[~2012-09-13 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 23:26 [PATCH 0/3] KVM: PPC: Memslot handling improvements Paul Mackerras
2012-09-11 23:26 ` Paul Mackerras
2012-09-11 23:27 ` [PATCH 1/3] KVM: PPC: Book3S HV: Take the SRCU read lock before looking up memslots Paul Mackerras
2012-09-11 23:27 ` Paul Mackerras
2012-09-11 23:27 ` [PATCH 2/3] KVM: PPC: Move kvm->arch.slot_phys into memslot.arch Paul Mackerras
2012-09-11 23:27 ` Paul Mackerras
2012-09-11 23:28 ` [PATCH 3/3] KVM: PPC: Book3S HV: Handle memory slot deletion and modification correctly Paul Mackerras
2012-09-11 23:28 ` Paul Mackerras
2012-09-13 16:43 ` Alexander Graf [this message]
2012-09-13 16:43 ` [PATCH 0/3] KVM: PPC: Memslot handling improvements Alexander Graf
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=50520D20.3000609@suse.de \
--to=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=paulus@samba.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 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.