qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-ppc@nongnu.org, Alexander Graf <agraf@suse.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH qemu] spapr: Add /system-id
Date: Fri, 27 Nov 2015 10:46:20 +1100	[thread overview]
Message-ID: <20151126234620.GB25500@voom.redhat.com> (raw)
In-Reply-To: <56568A93.6090307@ozlabs.ru>

[-- Attachment #1: Type: text/plain, Size: 2154 bytes --]

On Thu, Nov 26, 2015 at 03:29:07PM +1100, Alexey Kardashevskiy wrote:
> On 11/26/2015 11:49 AM, David Gibson wrote:
> >On Wed, Nov 25, 2015 at 04:15:01PM +0100, Alexander Graf wrote:
> >>
> >>
> >>On 18.11.15 11:49, David Gibson wrote:
> >>>On Wed, Nov 18, 2015 at 06:45:39PM +1100, Alexey Kardashevskiy wrote:
> >>>>On 11/09/2015 07:47 PM, David Gibson wrote:
> >>>>>On Mon, Nov 09, 2015 at 05:47:17PM +1100, Alexey Kardashevskiy wrote:
> >>>>>>Section B.6.2.1 Root Node Properties of PAPR specification defines
> >>>>>>a set of properties which shall be present in the device tree root,
> >>>>>>one of these properties is "system-id" which "should be unique across
> >>>>>>all systems and all manufacturers". Since UUID is meant to be unique,
> >>>>>>it makes sense to use it as "system-id".
> >>>>>>
> >>>>>>This adds "system-id" property to the device tree root when not empty.
> >>>>>>
> >>>>>>Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> >>>>>>---
> >>>>>>
> >>>>>>This might be expected by AIX so here is the patch.
> >>>>>>I am really not sure if it makes sense to initialize property when
> >>>>>>UUID is all zeroes as the requirement is "unique" and zero-uuid is
> >>>>>>not.
> >>>>>
> >>>>>Yeah, I think it would be better to omit system-id entirely when a
> >>>>>UUID hasn't been supplied.
> >>>>
> >>>>
> >>>>so this did not go anywhere yet, did it?
> >>>
> >>>No.
> >>
> >>So where is it stuck?
> >
> >I was waiting for a respin which didn't set the property when a UUID
> >hadn't been given.
> >
> 
> This is the original patch:
> 
> 
> +    if (qemu_uuid_set) {
> +        _FDT((fdt_property_string(fdt, "system-id", buf)));
> +    }
> 
> I does not set property if qemu_uuid_set==false already. What did I miss?

Oh, sorry, I misread the original patch.  I thought you were saying
that if UUID wasn't specified, it would appear as a system-id of all
0s.

Applied to ppc-for-2.6.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2015-11-26 23:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09  6:47 [Qemu-devel] [PATCH qemu] spapr: Add /system-id Alexey Kardashevskiy
2015-11-09  8:47 ` David Gibson
2015-11-18  7:45   ` Alexey Kardashevskiy
2015-11-18 10:49     ` David Gibson
2015-11-25 15:15       ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2015-11-26  0:49         ` David Gibson
2015-11-26  4:29           ` Alexey Kardashevskiy
2015-11-26 11:04             ` Greg Kurz
2015-11-26 23:46             ` David Gibson [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=20151126234620.GB25500@voom.redhat.com \
    --to=david@gibson.dropbear.id.au \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --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).