From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42994) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XSIB7-000802-Rx for qemu-devel@nongnu.org; Fri, 12 Sep 2014 00:09:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XSIB0-0006pR-CR for qemu-devel@nongnu.org; Fri, 12 Sep 2014 00:09:45 -0400 Received: from mail-pa0-f49.google.com ([209.85.220.49]:38562) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XSIB0-0006oH-6f for qemu-devel@nongnu.org; Fri, 12 Sep 2014 00:09:38 -0400 Received: by mail-pa0-f49.google.com with SMTP id lf10so326639pab.8 for ; Thu, 11 Sep 2014 21:09:36 -0700 (PDT) Message-ID: <541271F4.6080206@ozlabs.ru> Date: Fri, 12 Sep 2014 14:09:24 +1000 From: Alexey Kardashevskiy MIME-Version: 1.0 References: <1410419467-9932-1-git-send-email-aik@ozlabs.ru> <1410420145.6138.7.camel@nilsson.home.kraxel.org> <54115AB9.8080700@ozlabs.ru> <1410430546.6138.9.camel@nilsson.home.kraxel.org> <541179CF.3080501@ozlabs.ru> <1410431916.6138.13.camel@nilsson.home.kraxel.org> <54118137.9050305@ozlabs.ru> In-Reply-To: <54118137.9050305@ozlabs.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] ohci: Stop OHCI bus when PCI bus master is disabled List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org, Alexander Graf On 09/11/2014 09:02 PM, Alexey Kardashevskiy wrote: > On 09/11/2014 08:38 PM, Gerd Hoffmann wrote: >> Hi, >> >>> Another question - I noticed that XHCI migration is broken in quite recent >>> upstream QEMU, smells like memory corruption. Is it just me or just PPC or >>> is it known issue? >> >> 2.0 -> 2.1 migration being broken is a known issue (patch for that one >> was on the list earlier this week, unfortunately missed 2.1.1). >> >> Other that that I'm not aware of any issues. > > My bad, it was me. > > I enabled 64bit DMA on pseries (the guest ram is mapped at > 8000.0000.0000.0000 on the pci bus) and somehow this causes migration > errors. I thought there is no 64bit DMA-capable device in QEMU, and I was > wrong :) > > /me is debugging After all, my issue has nothing to do with XHCI itself. I am implementing another DMA window (64bit, maps entire guest) which is yet another child object on the PHB device but it is dynamic - it is created by request from the guest. And XHCI driver does it so I end up with source QEMU which has this object and destination QEMU which does not and when I try creating this object during migration (and this adds yet another SaveStateEntry), something goes very wrong. QOM puzzle. -- Alexey