qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Gleb Natapov" <gleb@redhat.com>,
	qemu-devel@nongnu.org, "Alexander Graf" <agraf@suse.de>,
	"Paul Mackerras" <paulus@samba.org>,
	qemu-ppc@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v3 1/5] boot: extend get_boot_devices_list() to ignore suffixes
Date: Wed, 11 Dec 2013 14:56:06 +1100	[thread overview]
Message-ID: <52A7E256.4050006@ozlabs.ru> (raw)
In-Reply-To: <52A6DD35.5020302@redhat.com>

On 12/10/2013 08:21 PM, Paolo Bonzini wrote:
> Il 10/12/2013 08:32, Alexey Kardashevskiy ha scritto:
>> As suffixes do not make sense for sPAPR's device tree and
>> there is no way to filter them out on the BusState::get_fw_dev_path
>> level, let's add an ability for the external caller to specify
>> whether to apply suffixes or not.
>>
>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> 
> SeaBIOS simply ignores unknown suffixes once it has recognized a part of
> the path.  Could SLOF do the same?

SeaBIOS does not need it. SLOF does not need it either. Who does need it?
What is it for after all? Commit 1ca4d09ae0bcc2fdd6aeef0fdc11f82394f7e757
"Add bootindex parameter to net/block/fd device" does not explain that at all.

SLOF cannot just ignore this, why? It is a part of a path, it should parse
tree to find the node OR if it fails, find the closest matching node and
pass the rest of the path as a package parameter. And we do not really plan
to implement this (no use) as this is purely QEMU stuff which we do not
really want to carry to SLOF.

I'd stick to my original patch (please :) ) or add yet another Interface
just to ignore the suffix or method (ugly as it will be called from a place
different than hw/core/qdev.c).


-- 
Alexey

  reply	other threads:[~2013-12-11  3:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10  7:32 [Qemu-devel] [PATCH v3 0/5] spapr: add bootindex support Alexey Kardashevskiy
2013-12-10  7:32 ` [Qemu-devel] [PATCH v3 1/5] boot: extend get_boot_devices_list() to ignore suffixes Alexey Kardashevskiy
2013-12-10  9:21   ` Paolo Bonzini
2013-12-11  3:56     ` Alexey Kardashevskiy [this message]
2013-12-10  7:32 ` [Qemu-devel] [PATCH v3 2/5] spapr-llan: add to boot device list Alexey Kardashevskiy
2013-12-10  7:32 ` [Qemu-devel] [PATCH v3 3/5] spapr-vio: fix firmware names Alexey Kardashevskiy
2013-12-10  7:32 ` [Qemu-devel] [PATCH v3 4/5] qdev: introduce get_fw_dev_path() callback Alexey Kardashevskiy
2013-12-10  7:32 ` [Qemu-devel] [PATCH v3 5/5] spapr: define interface to fix device pathname 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=52A7E256.4050006@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=gleb@redhat.com \
    --cc=paulus@samba.org \
    --cc=pbonzini@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).