[{"id":1763407,"web_url":"http://patchwork.ozlabs.org/comment/1763407/","msgid":"<20170905163656.73d98e23@bahia>","list_archive_url":null,"date":"2017-09-05T14:36:56","subject":"Re: [Qemu-devel] [Qemu-ppc] [PATCH 0/4] ppc: fix migration with KVM\n\tPR (nested)","submitter":{"id":69178,"url":"http://patchwork.ozlabs.org/api/people/69178/","name":"Greg Kurz","email":"groug@kaod.org"},"content":"I wanted to Cc Sam also but it was late and I forgot :)\n\nOn Mon, 04 Sep 2017 23:46:44 +0200\nGreg Kurz <groug@kaod.org> wrote:\n\n> A guest running with KVM PR ends up irresponsive after migration most of the\n> time. This happens because the HPT allocated by QEMU is likely to have a\n> different address on the destination than it had on the source, but we push\n> the source address to KVM.\n> \n> This series does a little cleanup and fixes the issue. I could successfully\n> test it with a nested setup (KVM PR running in KVM HV).\n> \n> However, this isn't enough to fix migration when using KVM PR on baremetal...\n> CPUs seem to end up looping on H_CEDE in the guest. I can't figure out what's\n> happening... Any suggestion would be appreciated.\n> \n> Cheers,\n> \n> --\n> Greg\n> \n> ---\n> \n> Greg Kurz (4):\n>       spapr: only update SDR1 once per-cpu during CAS\n>       spapr: introduce a helper to compute the address of the HPT\n>       ppc: kvm: introduce a helper to update SDR1 for a single CPU\n>       ppc: kvm: update HPT pointer in KVM PR after migration\n> \n> \n>  hw/ppc/spapr.c          |   15 +++++++++++++++\n>  hw/ppc/spapr_cpu_core.c |    8 +++-----\n>  hw/ppc/spapr_hcall.c    |   20 +++++++++-----------\n>  include/hw/ppc/spapr.h  |    1 +\n>  target/ppc/cpu.h        |    1 +\n>  target/ppc/kvm.c        |   12 ++++++++----\n>  target/ppc/kvm_ppc.h    |    3 ++-\n>  target/ppc/machine.c    |    7 +++++++\n>  8 files changed, 46 insertions(+), 21 deletions(-)\n> \n>","headers":{"Return-Path":"<qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org>","X-Original-To":"incoming@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming@bilbo.ozlabs.org","Authentication-Results":"ozlabs.org;\n\tspf=pass (mailfrom) smtp.mailfrom=nongnu.org\n\t(client-ip=2001:4830:134:3::11; helo=lists.gnu.org;\n\tenvelope-from=qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org;\n\treceiver=<UNKNOWN>)","Received":["from lists.gnu.org (lists.gnu.org [IPv6:2001:4830:134:3::11])\n\t(using TLSv1 with cipher AES256-SHA (256/256 bits))\n\t(No client certificate requested)\n\tby ozlabs.org (Postfix) with ESMTPS id 3xmq7z4hscz9t1t\n\tfor <incoming@patchwork.ozlabs.org>;\n\tWed,  6 Sep 2017 00:38:07 +1000 (AEST)","from localhost ([::1]:59376 helo=lists.gnu.org)\n\tby lists.gnu.org with esmtp (Exim 4.71) (envelope-from\n\t<qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org>)\n\tid 1dpEzN-0006YD-Ff\n\tfor incoming@patchwork.ozlabs.org; Tue, 05 Sep 2017 10:38:05 -0400","from eggs.gnu.org ([2001:4830:134:3::10]:52250)\n\tby lists.gnu.org with esmtp (Exim 4.71)\n\t(envelope-from <groug@kaod.org>) id 1dpEyV-0006KN-VG\n\tfor qemu-devel@nongnu.org; Tue, 05 Sep 2017 10:37:21 -0400","from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)\n\t(envelope-from <groug@kaod.org>) id 1dpEyR-00036P-Ba\n\tfor qemu-devel@nongnu.org; Tue, 05 Sep 2017 10:37:11 -0400","from 3.mo2.mail-out.ovh.net ([46.105.58.226]:47086)\n\tby eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)\n\t(Exim 4.71) (envelope-from <groug@kaod.org>) id 1dpEyR-00034e-4U\n\tfor qemu-devel@nongnu.org; Tue, 05 Sep 2017 10:37:07 -0400","from player157.ha.ovh.net (b9.ovh.net [213.186.33.59])\n\tby mo2.mail-out.ovh.net (Postfix) with ESMTP id CFCBBA96CE\n\tfor <qemu-devel@nongnu.org>; Tue,  5 Sep 2017 16:37:04 +0200 (CEST)","from bahia (deibp9eh1--blueice1n7.emea.ibm.com [195.212.29.161])\n\t(Authenticated sender: groug@kaod.org)\n\tby player157.ha.ovh.net (Postfix) with ESMTPSA id 882145000A5;\n\tTue,  5 Sep 2017 16:36:57 +0200 (CEST)"],"Date":"Tue, 5 Sep 2017 16:36:56 +0200","From":"Greg Kurz <groug@kaod.org>","To":"qemu-devel@nongnu.org","Message-ID":"<20170905163656.73d98e23@bahia>","In-Reply-To":"<150456160452.17000.3290192176290246589.stgit@bahia.lan>","References":"<150456160452.17000.3290192176290246589.stgit@bahia.lan>","X-Mailer":"Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu)","MIME-Version":"1.0","Content-Type":"multipart/signed; micalg=pgp-sha1;\n\tboundary=\"Sig_/NUr1VY6uRxecSU3O5pE22QN\";\n\tprotocol=\"application/pgp-signature\"","X-Ovh-Tracer-Id":"13155014512460667200","X-VR-SPAMSTATE":"OK","X-VR-SPAMSCORE":"-100","X-VR-SPAMCAUSE":"gggruggvucftvghtrhhoucdtuddrfeelledrvdekgdejgecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd","X-detected-operating-system":"by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]\n\t[fuzzy]","X-Received-From":"46.105.58.226","Subject":"Re: [Qemu-devel] [Qemu-ppc] [PATCH 0/4] ppc: fix migration with KVM\n\tPR (nested)","X-BeenThere":"qemu-devel@nongnu.org","X-Mailman-Version":"2.1.21","Precedence":"list","List-Id":"<qemu-devel.nongnu.org>","List-Unsubscribe":"<https://lists.nongnu.org/mailman/options/qemu-devel>,\n\t<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>","List-Archive":"<http://lists.nongnu.org/archive/html/qemu-devel/>","List-Post":"<mailto:qemu-devel@nongnu.org>","List-Help":"<mailto:qemu-devel-request@nongnu.org?subject=help>","List-Subscribe":"<https://lists.nongnu.org/mailman/listinfo/qemu-devel>,\n\t<mailto:qemu-devel-request@nongnu.org?subject=subscribe>","Cc":"Thomas Huth <thuth@redhat.com>, qemu-ppc@nongnu.org,\n\tSam Bobroff <sam.bobroff@au1.ibm.com>,\n\tSuraj Jitindar Singh <sjitindarsingh@gmail.com>,\n\tDavid Gibson <david@gibson.dropbear.id.au>","Errors-To":"qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org","Sender":"\"Qemu-devel\"\n\t<qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org>"}}]