kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Paul Mackerras <paulus@ozlabs.org>,
	kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [GIT PULL] Please pull my kvm-ppc-fixes branch
Date: Thu, 12 Nov 2015 10:11:35 +0100	[thread overview]
Message-ID: <564457C7.5030102@redhat.com> (raw)
In-Reply-To: <20151112053542.GA22330@fergus.ozlabs.ibm.com>



On 12/11/2015 06:35, Paul Mackerras wrote:
> Paolo,
> 
> I have two fixes for HV KVM which I would like to have included in
> v4.4-rc1.  The first one is a fix for a bug identified by Red Hat
> which causes occasional guest crashes.  The second one fixes a bug
> which causes host stalls and timeouts under certain circumstances when
> the host is configured for static 2-way micro-threading mode.
> 
> Thanks,
> Paul.
> 
> The following changes since commit a3eaa8649e4c6a6afdafaa04b9114fb230617bb1:
> 
>   KVM: VMX: Fix commit which broke PML (2015-11-05 11:34:11 +0100)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git kvm-ppc-fixes
> 
> for you to fetch changes up to f74f2e2e26199f695ca3df94f29e9ab7cb707ea4:
> 
>   KVM: PPC: Book3S HV: Don't dynamically split core when already split (2015-11-06 16:02:59 +1100)
> 
> ----------------------------------------------------------------
> Paul Mackerras (2):
>       KVM: PPC: Book3S HV: Synthesize segment fault if SLB lookup fails
>       KVM: PPC: Book3S HV: Don't dynamically split core when already split
> 
>  arch/powerpc/kvm/book3s_hv.c            |  2 +-
>  arch/powerpc/kvm/book3s_hv_rmhandlers.S | 20 ++++++++++++--------
>  2 files changed, 13 insertions(+), 9 deletions(-)
> 

Pulled, thanks.

Paolo

  reply	other threads:[~2015-11-12  9:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12  5:35 [GIT PULL] Please pull my kvm-ppc-fixes branch Paul Mackerras
2015-11-12  9:11 ` Paolo Bonzini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-12-10  3:12 Paul Mackerras
2015-12-11 11:30 ` Paolo Bonzini
2016-03-08 10:54 Paul Mackerras
2017-03-02  1:55 Paul Mackerras
2017-03-02 11:00 ` Paolo Bonzini
2017-03-02 21:04 ` Radim Krčmář
2017-04-06  6:28 Paul Mackerras
2017-04-06 14:37 ` Radim Krčmář
2017-05-15  8:16 Paul Mackerras
2017-05-15  8:32 ` Christian Zigotzky
2017-05-16 13:52 ` Radim Krčmář
2017-06-20  4:30 Paul Mackerras
2017-06-20 12:39 ` Radim Krčmář
2017-06-20 12:55   ` Paolo Bonzini
2017-06-20 15:17     ` Radim Krčmář
2017-06-20 23:37       ` Paul Mackerras
2017-06-21 10:30         ` Paolo Bonzini
2017-07-26  4:43 Paul Mackerras
2017-08-25  1:38 Paul Mackerras
2017-08-25  7:02 ` Paolo Bonzini
2017-08-25  9:06   ` Paul Mackerras
2017-08-30  6:21 Paul Mackerras
2017-09-08 14:37 ` Radim Krčmář
2017-09-09 13:38   ` Paolo Bonzini
2017-09-12  4:01     ` Paul Mackerras
2017-09-14  4:06 Paul Mackerras
2017-10-19  4:20 Paul Mackerras
2017-10-19 13:11 ` Radim Krčmář

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=564457C7.5030102@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=paulus@ozlabs.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;
as well as URLs for NNTP newsgroup(s).