All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, Markus Armbruster <armbru@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-arm] [PATCH 2/4] loader: Add load_image_mr() to load ROM image to a MemoryRegion
Date: Thu, 3 Mar 2016 17:46:28 +0100	[thread overview]
Message-ID: <56D86A64.1040909@redhat.com> (raw)
In-Reply-To: <1455288361-30117-3-git-send-email-peter.maydell@linaro.org>



On 12/02/2016 15:45, Peter Maydell wrote:
> Add a new function load_image_mr(), which behaves like
> load_image_targphys() except that it loads the ROM image to
> a specified MemoryRegion rather than to a specified physical
> address. This is useful when a ROM blob needs to be loaded
> to a particular flash or ROM device but the address of that
> device in the machine's address space is not known. (For
> instance, ROMs in devices, or ROMs which might exist in
> a different address space to the system address space.)
> 
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>

The patch looks good, in particular it should be fine for the non-fw_cfg
uses of rom->mr.

The fw_cfg interface to loader.c indeed should be turned upside-down so
that the knowledge moves outside rom_add_file (to a rom_add_fwcfg
function for example) and rom_add_file doesn't need to call rom_set_mr.
 Your patch is at least a step in the right direction, because it adds
memory region support in the !fw_cfg case.

So,

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

Thanks,

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, Markus Armbruster <armbru@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/4] loader: Add load_image_mr() to load ROM image to a MemoryRegion
Date: Thu, 3 Mar 2016 17:46:28 +0100	[thread overview]
Message-ID: <56D86A64.1040909@redhat.com> (raw)
In-Reply-To: <1455288361-30117-3-git-send-email-peter.maydell@linaro.org>



On 12/02/2016 15:45, Peter Maydell wrote:
> Add a new function load_image_mr(), which behaves like
> load_image_targphys() except that it loads the ROM image to
> a specified MemoryRegion rather than to a specified physical
> address. This is useful when a ROM blob needs to be loaded
> to a particular flash or ROM device but the address of that
> device in the machine's address space is not known. (For
> instance, ROMs in devices, or ROMs which might exist in
> a different address space to the system address space.)
> 
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>

The patch looks good, in particular it should be fine for the non-fw_cfg
uses of rom->mr.

The fw_cfg interface to loader.c indeed should be turned upside-down so
that the knowledge moves outside rom_add_file (to a rom_add_fwcfg
function for example) and rom_add_file doesn't need to call rom_set_mr.
 Your patch is at least a step in the right direction, because it adds
memory region support in the !fw_cfg case.

So,

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

Thanks,

Paolo

  reply	other threads:[~2016-03-03 16:46 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12 14:45 [Qemu-devel] [PATCH 0/4] virt: provide secure-only RAM and first flash Peter Maydell
2016-02-12 14:45 ` [Qemu-devel] [PATCH 1/4] hw/arm/virt: Provide a secure-only RAM if booting in Secure mode Peter Maydell
2016-02-12 14:45 ` [Qemu-arm] [PATCH 2/4] loader: Add load_image_mr() to load ROM image to a MemoryRegion Peter Maydell
2016-02-12 14:45   ` [Qemu-devel] " Peter Maydell
2016-03-03 16:46   ` Paolo Bonzini [this message]
2016-03-03 16:46     ` Paolo Bonzini
2016-03-04  7:42     ` [Qemu-arm] " Michael S. Tsirkin
2016-03-04  7:42       ` [Qemu-devel] " Michael S. Tsirkin
2016-02-12 14:46 ` [Qemu-devel] [PATCH 3/4] hw/arm/virt: Load bios image to MemoryRegion, not physaddr Peter Maydell
2016-02-12 14:46 ` [Qemu-arm] [PATCH 4/4] hw/arm/virt: Make first flash device Secure-only if booting secure Peter Maydell
2016-02-12 14:46   ` [Qemu-devel] " Peter Maydell
2016-02-12 22:54 ` [Qemu-devel] [PATCH 0/4] virt: provide secure-only RAM and first flash Mark Cave-Ayland
2016-02-25 16:47 ` [Qemu-arm] " Peter Maydell
2016-02-25 16:47   ` Peter Maydell
2016-03-07 15:20 ` [Qemu-arm] " Paolo Bonzini
2016-03-07 15:20   ` [Qemu-devel] " Paolo Bonzini
2016-03-07 23:34   ` Peter Maydell
2016-03-08 12:02     ` [Qemu-arm] " Paolo Bonzini
2016-03-08 12:02       ` [Qemu-devel] " Paolo Bonzini
2016-03-08 12:10       ` [Qemu-arm] " Ard Biesheuvel
2016-03-08 12:10         ` [Qemu-devel] " Ard Biesheuvel
2016-03-08 12:13         ` Ard Biesheuvel
2016-03-08 12:14           ` [Qemu-arm] " Paolo Bonzini
2016-03-08 12:14             ` [Qemu-devel] " Paolo Bonzini
2016-03-08 12:16             ` [Qemu-arm] " Ard Biesheuvel
2016-03-08 12:16               ` [Qemu-devel] " Ard Biesheuvel
2016-03-08 12:41               ` [Qemu-arm] " Paolo Bonzini
2016-03-08 12:41                 ` [Qemu-devel] " Paolo Bonzini
2016-03-08 12:50                 ` Ard Biesheuvel
2016-03-08 13:06                   ` [Qemu-arm] " Paolo Bonzini
2016-03-08 13:06                     ` [Qemu-devel] " Paolo Bonzini
2016-03-08 13:46                     ` [Qemu-arm] " Peter Maydell
2016-03-08 13:46                       ` [Qemu-devel] " Peter Maydell
2016-03-09 14:06                     ` [Qemu-arm] " Laszlo Ersek
2016-03-09 14:06                       ` Laszlo Ersek
2016-03-09 14:07                       ` [Qemu-arm] " Paolo Bonzini
2016-03-09 14:07                         ` Paolo Bonzini
2016-03-09 14:21                         ` [Qemu-arm] " Laszlo Ersek
2016-03-09 14:21                           ` Laszlo Ersek
2016-03-08 13:49               ` [Qemu-arm] " Peter Maydell
2016-03-08 13:49                 ` [Qemu-devel] " Peter Maydell

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=56D86A64.1040909@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --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.