From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Alexander Graf <agraf@suse.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
Paul Mackerras <paulus@samba.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH] powerpc iommu: enable multiple TCE requests
Date: Mon, 19 Aug 2013 11:47:23 +0200 [thread overview]
Message-ID: <5211E9AB.7050700@redhat.com> (raw)
In-Reply-To: <5211DAD3.1050602@ozlabs.ru>
Il 19/08/2013 10:44, Alexey Kardashevskiy ha scritto:
>> > It means that if you use the same QEMU version with the same command
>> > line on a different kernel version, your guest looks different because
>> > we generate the dtb differently.
> Oh. Sorry for my ignorance again, I am not playing dump or anything like
> that - I do not understand how the device tree (which we cook in QEMU) on
> the destination can possibly survive migration and not to be overwritten by
> the one from the source. What was in the destination RAM before migration
> does not matter at all (including dt), QEMU device tree is what matters but
> this does not change. As it is "the same QEMU version", hypercalls are
> supported anyway, the only difference where they will be handled - in the
> host kernel or QEMU. What do I miss?
Nothing, I just asked to test that handling the hypercall in QEMU works.
On x86 we have a similar problem, though with cpuid bits instead of the
device tree. An older kernel might not support some cpuid bits, thus
"-cpu SandyBridge" might have different cpuid bits depending on the host
processor and kernel version. This is handled by having an "enforce"
mode where "-cpu SandyBridge,enforce" will fail to start if the host
processor or the kernel is not new enough.
But in this case, you do not need this because the hypercall works if
emulated by QEMU. I like Alex's solution of making it universally
available in the dtb.
Paolo
next prev parent reply other threads:[~2013-08-19 9:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 8:08 [Qemu-devel] [PATCH] powerpc iommu: enable multiple TCE requests Alexey Kardashevskiy
2013-08-16 9:49 ` Alexey Kardashevskiy
2013-08-18 15:22 ` Paolo Bonzini
2013-08-19 7:30 ` Alexey Kardashevskiy
2013-08-19 8:01 ` Alexander Graf
2013-08-19 8:44 ` Alexey Kardashevskiy
2013-08-19 9:47 ` Paolo Bonzini [this message]
2013-08-20 1:36 ` Alexey Kardashevskiy
2013-08-20 6:55 ` Alexander Graf
2013-08-20 8:39 ` Paolo Bonzini
2013-08-20 8:49 ` Alexey Kardashevskiy
2013-08-20 9:09 ` Paolo Bonzini
2013-08-20 9:13 ` Benjamin Herrenschmidt
2013-08-20 9:15 ` Paolo Bonzini
2013-08-20 9:20 ` Benjamin Herrenschmidt
2013-08-20 9:22 ` Paolo Bonzini
2013-08-20 9:26 ` Benjamin Herrenschmidt
2013-08-20 10:14 ` Paolo Bonzini
2013-08-20 11:38 ` Benjamin Herrenschmidt
2013-08-21 7:11 ` Alexander Graf
2013-08-21 7:29 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2013-08-16 13:15 ` [Qemu-devel] " Alexander Graf
2013-08-19 9:01 ` Alexey Kardashevskiy
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=5211E9AB.7050700@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=paulus@samba.org \
--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).