From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH] ohci: Stop OHCI bus when PCI bus master is disabled
Date: Fri, 12 Sep 2014 14:09:24 +1000 [thread overview]
Message-ID: <541271F4.6080206@ozlabs.ru> (raw)
In-Reply-To: <54118137.9050305@ozlabs.ru>
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
prev parent reply other threads:[~2014-09-12 4:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 7:11 [Qemu-devel] [PATCH] ohci: Stop OHCI bus when PCI bus master is disabled Alexey Kardashevskiy
2014-09-11 7:22 ` Gerd Hoffmann
2014-09-11 8:18 ` Alexey Kardashevskiy
2014-09-11 10:15 ` Gerd Hoffmann
2014-09-11 10:30 ` Alexey Kardashevskiy
2014-09-11 10:38 ` Gerd Hoffmann
2014-09-11 11:02 ` Alexey Kardashevskiy
2014-09-12 4:09 ` Alexey Kardashevskiy [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=541271F4.6080206@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=agraf@suse.de \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).