qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cyril Bur <cyrilbur@gmail.com>
To: Alexander Graf <agraf@suse.de>, Eric Blake <eblake@redhat.com>,
	qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH for-2.2] spapr: add host Linux version information to device tree
Date: Wed, 23 Jul 2014 08:35:34 +1000	[thread overview]
Message-ID: <53CEE736.5020103@gmail.com> (raw)
In-Reply-To: <53C90CA6.3060308@suse.de>


On 18/07/14 22:01, Alexander Graf wrote:
>
> On 18.07.14 13:59, Eric Blake wrote:
>> On 07/17/2014 10:31 PM, cyrilbur@gmail.com wrote:
>>> It may prove useful know which Linux distribution version the host 
>>> machine
>>> is running when an issue in the guest arises but a user cannot access
>>> the host.
>>>
>>> Signed-off-by: Cyril Bur <cyril.bur@au1.ibm.com>
>>> ---
>>>   hw/ppc/spapr.c       |  8 +++++++
>>>   target-ppc/kvm.c     | 62 
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>   target-ppc/kvm_ppc.h |  6 +++++
>>>   3 files changed, 76 insertions(+)
>>>
>>> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
>>> index 6b48a26..391d47a 100644
>>> --- a/hw/ppc/spapr.c
>>> +++ b/hw/ppc/spapr.c
>>> @@ -375,6 +375,14 @@ static void *spapr_create_fdt_skel(hwaddr 
>>> initrd_base,
>>>       _FDT((fdt_property_string(fdt, "vm,uuid", buf)));
>>>       g_free(buf);
>>>   +    /*
>>> +     * Add info to the guest FDT to tell it what linux the host is
>>> +     */
>>> +    if (kvmppc_get_linux_host(&buf)) {
>>> +        _FDT((fdt_property_string(fdt, "linux,host", buf)));
>>> +        g_free(buf);
>>> +    }
>> Ouch.  What does this do for migration?  By exposing it to the guest,
>> you have made it part of the guest ABI, and now you have limited
>> yourself to migrate only when the destination host is identical to the
>> source if you don't want to risk breaking the guest.  Without this, it
>> seems feasible to migrate from a machine on an older host to another
>> machine on a newer host.
>
> sPAPR has a mechanism to inject a "post-migration" interrupt into the 
> guest and provide a device tree diff. That way we can change these 
> host specific values on the fly after migration happened.
>
> Maybe it makes sense to hold off these host specific device tree 
> chunks until after we have that mechanism implemented though.

Indeed and the ability to do this is in the kernel but it had not been 
implemented in qemu yet. Probably not worth doing just for this patch 
but having this does open the doors to quite a few other things, I'll 
investigate.

Cyril
>
> Alex
>

  reply	other threads:[~2014-07-22 22:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18  4:31 [Qemu-devel] [PATCH for-2.2] spapr: add host Linux version information to device tree cyrilbur
2014-07-18 11:59 ` Eric Blake
2014-07-18 12:01   ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-07-22 22:35     ` Cyril Bur [this message]
2014-07-24 13:15 ` Alexander Graf
2014-07-28  6:47   ` Alexey Kardashevskiy
2014-07-28  7:50     ` Alexander Graf

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=53CEE736.5020103@gmail.com \
    --to=cyrilbur@gmail.com \
    --cc=agraf@suse.de \
    --cc=eblake@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).