qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: qemu-devel@nongnu.org
Cc: Thomas Huth <thuth@redhat.com>,
	qemu-ppc@nongnu.org,
	Suraj Jitindar Singh <sjitindarsingh@gmail.com>,
	David Gibson <david@gibson.dropbear.id.au>,
	Sam Bobroff <sam.bobroff@au1.ibm.com>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 0/4] ppc: fix migration with KVM PR (nested)
Date: Tue, 5 Sep 2017 16:36:56 +0200	[thread overview]
Message-ID: <20170905163656.73d98e23@bahia> (raw)
In-Reply-To: <150456160452.17000.3290192176290246589.stgit@bahia.lan>

[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]

I wanted to Cc Sam also but it was late and I forgot :)

On Mon, 04 Sep 2017 23:46:44 +0200
Greg Kurz <groug@kaod.org> wrote:

> A guest running with KVM PR ends up irresponsive after migration most of the
> time. This happens because the HPT allocated by QEMU is likely to have a
> different address on the destination than it had on the source, but we push
> the source address to KVM.
> 
> This series does a little cleanup and fixes the issue. I could successfully
> test it with a nested setup (KVM PR running in KVM HV).
> 
> However, this isn't enough to fix migration when using KVM PR on baremetal...
> CPUs seem to end up looping on H_CEDE in the guest. I can't figure out what's
> happening... Any suggestion would be appreciated.
> 
> Cheers,
> 
> --
> Greg
> 
> ---
> 
> Greg Kurz (4):
>       spapr: only update SDR1 once per-cpu during CAS
>       spapr: introduce a helper to compute the address of the HPT
>       ppc: kvm: introduce a helper to update SDR1 for a single CPU
>       ppc: kvm: update HPT pointer in KVM PR after migration
> 
> 
>  hw/ppc/spapr.c          |   15 +++++++++++++++
>  hw/ppc/spapr_cpu_core.c |    8 +++-----
>  hw/ppc/spapr_hcall.c    |   20 +++++++++-----------
>  include/hw/ppc/spapr.h  |    1 +
>  target/ppc/cpu.h        |    1 +
>  target/ppc/kvm.c        |   12 ++++++++----
>  target/ppc/kvm_ppc.h    |    3 ++-
>  target/ppc/machine.c    |    7 +++++++
>  8 files changed, 46 insertions(+), 21 deletions(-)
> 
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      parent reply	other threads:[~2017-09-05 14:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04 21:46 [Qemu-devel] [PATCH 0/4] ppc: fix migration with KVM PR (nested) Greg Kurz
2017-09-04 21:46 ` [Qemu-devel] [PATCH 1/4] spapr: only update SDR1 once per-cpu during CAS Greg Kurz
2017-09-10  1:58   ` David Gibson
2017-09-04 21:47 ` [Qemu-devel] [PATCH 2/4] spapr: introduce a helper to compute the address of the HPT Greg Kurz
2017-09-10  3:41   ` David Gibson
2017-09-11 12:04     ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2017-09-11 12:50       ` David Gibson
2017-09-11 13:54         ` Greg Kurz
2017-09-04 21:47 ` [Qemu-devel] [PATCH 3/4] ppc: kvm: introduce a helper to update SDR1 for a single CPU Greg Kurz
2017-09-10  3:56   ` David Gibson
2017-09-04 21:47 ` [Qemu-devel] [PATCH 4/4] ppc: kvm: update HPT pointer in KVM PR after migration Greg Kurz
2017-09-05 14:36 ` Greg Kurz [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=20170905163656.73d98e23@bahia \
    --to=groug@kaod.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=sam.bobroff@au1.ibm.com \
    --cc=sjitindarsingh@gmail.com \
    --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).