All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>, qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 6/6] hw/pci-bridge: set explicit OFW unit address for TYPE_PXB_HOST
Date: Thu, 11 Jun 2015 12:45:16 +0200	[thread overview]
Message-ID: <557966BC.5000704@redhat.com> (raw)
In-Reply-To: <557962FA.4010208@redhat.com>

On 06/11/15 12:29, Marcel Apfelbaum wrote:
> On 06/11/2015 01:26 PM, Laszlo Ersek wrote:
>> On 06/11/15 12:21, Marcel Apfelbaum wrote:
>>> On 06/11/2015 03:38 AM, Laszlo Ersek wrote:
>>>> The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot
>>>> off devices behind the PXB. This happens because the
>>>> sysbus_get_fw_dev_path() function in "hw/core/sysbus.c" doesn't have
>>>> enough information to format a unique identifier for the PXB in
>>>> question,
>>>> and consequently the OpenFirmware device path passed down to the guest
>>>> firmware in the "bootorder" fw_cfg file is unusable for identifying the
>>>> boot device.
>>>>
>>>> For example, the command line fragment
>>>>
>>>>     -device pxb,id=bridge1,bus_nr=4 \
>>>>     \
>>>>     -netdev user,id=netdev0 \
>>>>     -device e1000,netdev=netdev0,bus=bridge1,addr=2,bootindex=0
>>>>
>>>> results in the following "bootorder" entry:
>>>>
>>>>     /pci/pci-bridge@0/ethernet@2/ethernet-phy@0
>>>>
>>>> The initial "pci" node is formatted by sysbus_get_fw_dev_path(), and
>>>> the
>>>> resultant OpenFirmware device path is independent of bus_nr=4 -- and
>>>> therefore it is useless for identifying the device.
>>>>
>>>> In this patch we change the fw_name device class member of
>>>> TYPE_PXB_HOST
>>>> from "pci" to "pci-root", and set each instance's explicit OFW unit
>>>> address to the PXB bus number. The same command line fragment
>>>> results in
>>>> the following OpenFirmware device path in the "bootorder" fw_cfg file:
>>>>
>>>>     /pci-root@4/pci-bridge@0/ethernet@2/ethernet-phy@0
>>> Hi Laszlo,
>>>
>>> I applied your patches but I still get
>>> /pci@i0cf8/ethernet@5/ethernet-phy@0
>>> in the boot list
>>>
>>> I checked and  the code enters only once in sysbus_get_fw_dev_path
>>> for pci@i0cf8 and goes for pio branch.
>>>
>>> Do you know maybe what I missed?
>>
>> I think so, yes: you added the ...,bootorder=N property to a device that
>> is *not* behind a PXB. :) You forgot the ...,bus=bridgeX property.
> 
> Actually:
> -device pxb,id=bridge1,bus_nr=4 -netdev user,id=u \
> -device
> e1000,id=net2,bus=bridge1,netdev=u,addr=0x5,bootindex=0,romfile=../pc-bios/efi-e1000.rom,bus=pci.0
> 
> 
> Hmm :(

Count the "bus=" substrings on your command line :)

Laszlo

  reply	other threads:[~2015-06-11 10:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11  0:37 [Qemu-devel] [PATCH v3 0/6] PXB tweaks and fixes Laszlo Ersek
2015-06-11  0:37 ` [Qemu-devel] [PATCH v3 1/6] i386/acpi-build: more traditional _UID and _HID for PXB root buses Laszlo Ersek
2015-06-11  0:37 ` [Qemu-devel] [PATCH v3 2/6] i386/acpi-build: fix PXB workarounds for unsupported BIOSes Laszlo Ersek
2015-06-11  0:38 ` [Qemu-devel] [PATCH v3 3/6] hw/pci-bridge: create interrupt-less, hotplug-less bridge for PXB Laszlo Ersek
2015-06-11  0:38 ` [Qemu-devel] [PATCH v3 4/6] hw/core: rebase sysbus_get_fw_dev_path() to g_strdup_printf() Laszlo Ersek
2015-06-11  9:08   ` Marcel Apfelbaum
2015-06-11  0:38 ` [Qemu-devel] [PATCH v3 5/6] hw/core: explicit OFW unit address property for SysBusDevice Laszlo Ersek
2015-06-11  9:12   ` Marcel Apfelbaum
2015-06-11  0:38 ` [Qemu-devel] [PATCH v3 6/6] hw/pci-bridge: set explicit OFW unit address for TYPE_PXB_HOST Laszlo Ersek
2015-06-11  9:15   ` Marcel Apfelbaum
2015-06-11  9:50     ` Laszlo Ersek
2015-06-11 10:21   ` Marcel Apfelbaum
2015-06-11 10:26     ` Laszlo Ersek
2015-06-11 10:29       ` Marcel Apfelbaum
2015-06-11 10:45         ` Laszlo Ersek [this message]
2015-06-11 10:55           ` Marcel Apfelbaum

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=557966BC.5000704@redhat.com \
    --to=lersek@redhat.com \
    --cc=armbru@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.