From: Gerd Hoffmann <kraxel@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>,
qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hw/ppc/spapr: Fix boot path of usb-host storage devices
Date: Thu, 15 Dec 2016 10:28:17 +0100 [thread overview]
Message-ID: <1481794097.21413.11.camel@redhat.com> (raw)
In-Reply-To: <421b6da7-1197-83a4-a8a1-e34bcf15904e@redhat.com>
Hi,
> That's true for the default case, but for the pseries machine, there is
> already code that changes the boot path for virtual usb-storage devices,
> see the function spapr_get_fw_dev_path() :
>
> ... else if (usb) {
> /*
> * We use SRP luns of the form 01000000 | (usb-port << 16) | lun
> * in the top 32 bits of the 64-bit LUN
> */
> unsigned usb_port = atoi(usb->port->path);
> unsigned id = 0x1000000 | (usb_port << 16) | d->lun;
> return g_strdup_printf("%s@%"PRIX64, qdev_fw_name(dev),
> (uint64_t)id << 32);
> }
Hmm, I thought the point of using standard open firmware paths was that
we don't need hacks like this. Looks like things are not *that*
standardized then if some archs need extra tweaks ...
But if that is needed for pseries *anyway* it doesn't hurt to do the
same for usb-host.
> > If usb-host (and usb-redir too btw) create paths identical to the ones
> > created by usb-storage. Existing firmware should cope just fine
> > (assuming bootindex for usb-storage works).
>
> Which firmware can deal with these original device paths with "channel@0"
> in it? Certainly not SLOF. Maybe OpenBIOS? Does OpenBIOS support USB storage
> devices?
seabios does, and I expect ovmf too (didn't test though).
cheers,
Gerd
next prev parent reply other threads:[~2016-12-15 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 12:44 [Qemu-devel] [PATCH] hw/ppc/spapr: Fix boot path of usb-host storage devices Thomas Huth
2016-12-13 13:52 ` Gerd Hoffmann
2016-12-13 14:29 ` Thomas Huth
2016-12-14 9:36 ` Gerd Hoffmann
2016-12-14 21:33 ` Thomas Huth
2016-12-15 9:28 ` Gerd Hoffmann [this message]
2016-12-15 11:47 ` [Qemu-devel] [Qemu-ppc] " BALATON Zoltan
2016-12-14 0:14 ` [Qemu-devel] " David Gibson
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=1481794097.21413.11.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/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).