qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: marcel.apfelbaum@gmail.com, lersek@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] sysbus: always allow explicit_ofw_unit_address() to override address generation
Date: Mon, 6 Aug 2018 17:06:35 -0300	[thread overview]
Message-ID: <20180806200635.GA12341@localhost.localdomain> (raw)
In-Reply-To: <20180805112850.26063-2-mark.cave-ayland@ilande.co.uk>

On Sun, Aug 05, 2018 at 12:28:49PM +0100, Mark Cave-Ayland wrote:
> Some SysBusDevices either use sysbus_init_mmio() without
> sysbus_mmio_map() or the first MMIO memory region doesn't represent the
> bus address, causing a firmware device path with an invalid address to
> be generated.
> 
> SysBusDeviceClass does provide a virtual explicit_ofw_unit_address()
> method that can be used to override this process, but it was originally intended
> only as as a fallback option meaning that any existing MMIO memory regions still
> take priority whilst determining the firmware device address.
> 
> There is currently only one user of explicit_ofw_unit_address() and that
> is the PCI expander bridge (PXB) device which has no MMIO/PIO resources
> defined. This enables us to allow explicit_ofw_unit_address() to take
> priority without affecting backwards compatibility, allowing the address
> to be customised as required.
> 
> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>

Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>

Queueing for 3.1.

-- 
Eduardo

  parent reply	other threads:[~2018-08-06 20:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-05 11:28 [Qemu-devel] [PATCH 0/2] machine: preparation for adding SPARC64/PPC bootindex support Mark Cave-Ayland
2018-08-05 11:28 ` [Qemu-devel] [PATCH 1/2] sysbus: always allow explicit_ofw_unit_address() to override address generation Mark Cave-Ayland
2018-08-06  5:46   ` Thomas Huth
2018-08-06 20:06   ` Eduardo Habkost [this message]
2018-08-05 11:28 ` [Qemu-devel] [PATCH 2/2] fw_cfg: set the get_boot_devices_list() ignore_suffixes parameter from machine property Mark Cave-Ayland
2018-08-06  5:50   ` Thomas Huth
2018-08-06 12:26     ` Laszlo Ersek
2018-08-06 20:11   ` Eduardo Habkost
2018-08-07 10:28     ` Laszlo Ersek
2018-08-07 19:27     ` Mark Cave-Ayland
2018-08-07 19:45       ` Eduardo Habkost
2018-08-08 19:11         ` Mark Cave-Ayland
  -- strict thread matches above, loose matches on Subject: below --
2018-06-23  8:50 [Qemu-devel] [PATCH 0/2] sysbus/pci: allow better customisation of firmware device paths Mark Cave-Ayland
2018-06-23  8:50 ` [Qemu-devel] [PATCH 1/2] sysbus: always allow explicit_ofw_unit_address() to override address generation Mark Cave-Ayland
2018-06-25  7:32   ` Laszlo Ersek
2018-06-27 19:59     ` Mark Cave-Ayland
2018-06-28  9:35       ` Laszlo Ersek

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=20180806200635.GA12341@localhost.localdomain \
    --to=ehabkost@redhat.com \
    --cc=lersek@redhat.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --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 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).