qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	patches@linaro.org, "Julia Suvorova" <jusual@mail.ru>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Jim Mussared" <jim@groklearning.com>,
	"Steffen Görtz" <mail@steffen-goertz.de>
Subject: Re: [Qemu-devel] [PATCH 2/2] hw/arm/armv7m: Remove unused armv7m_init() function
Date: Sun, 3 Jun 2018 10:18:35 +0930	[thread overview]
Message-ID: <CACPK8XfOZezMM2fL1aNoPx7Gjc1zeCJf5MNaS4FOPfZ5XABB2w@mail.gmail.com> (raw)
In-Reply-To: <20180601144328.23817-3-peter.maydell@linaro.org>

Hi Peter,

On 2 June 2018 at 00:13, Peter Maydell <peter.maydell@linaro.org> wrote:
> Remove the now-unused armv7m_init() function. This was a legacy from
> before we properly QOMified ARMv7M, and it has some flaws:
>
>  * it combines work that needs to be done by an SoC object (creating
>    and initializing the TYPE_ARMV7M object) with work that needs to
>    be done by the board model (setting the system up to load the ELF
>    file specified with -kernel)
>  * TYPE_ARMV7M creation failure is fatal, but an SoC object wants to
>    arrange to propagate the failure outward
>  * it uses allocate-and-create via qdev_create() whereas the current
>    preferred style for SoC objects is to do creation in-place
>
> Board and SoC models can instead do the two jobs this function
> was doing themselves, in the right places and with whatever their
> preferred style/error handling is.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
>  include/hw/arm/arm.h |  8 ++------
>  hw/arm/armv7m.c      | 21 ---------------------
>  2 files changed, 2 insertions(+), 27 deletions(-)
>
> diff --git a/include/hw/arm/arm.h b/include/hw/arm/arm.h
> index 70fa2287e2..ffed39252d 100644
> --- a/include/hw/arm/arm.h
> +++ b/include/hw/arm/arm.h
> @@ -23,9 +23,6 @@ typedef enum {
>      ARM_ENDIANNESS_BE32,
>  } arm_endianness;
>
> -/* armv7m.c */
> -DeviceState *armv7m_init(MemoryRegion *system_memory, int mem_size, int num_irq,
> -                         const char *kernel_filename, const char *cpu_type);
>  /**
>   * armv7m_load_kernel:
>   * @cpu: CPU
> @@ -33,9 +30,8 @@ DeviceState *armv7m_init(MemoryRegion *system_memory, int mem_size, int num_irq,
>   * @mem_size: mem_size: maximum image size to load
>   *
>   * Load the guest image for an ARMv7M system. This must be called by
> - * any ARMv7M board, either directly or via armv7m_init(). (This is
> - * necessary to ensure that the CPU resets correctly on system reset,
> - * as well as for kernel loading.)
> + * any ARMv7M board. (This is necessary to ensure that the CPU resets
> + * correctly on system reset, as well as for kernel loading.)
>   */
>  void armv7m_load_kernel(ARMCPU *cpu, const char *kernel_filename, int mem_size);
>
> diff --git a/hw/arm/armv7m.c b/hw/arm/armv7m.c
> index f123cc7d3d..a4ab7d2069 100644
> --- a/hw/arm/armv7m.c
> +++ b/hw/arm/armv7m.c
> @@ -261,27 +261,6 @@ static void armv7m_reset(void *opaque)
>      cpu_reset(CPU(cpu));
>  }
>
> -/* Init CPU and memory for a v7-M based board.
> -   mem_size is in bytes.
> -   Returns the ARMv7M device.  */
> -
> -DeviceState *armv7m_init(MemoryRegion *system_memory, int mem_size, int num_irq,
> -                         const char *kernel_filename, const char *cpu_type)
> -{
> -    DeviceState *armv7m;
> -
> -    armv7m = qdev_create(NULL, TYPE_ARMV7M);
> -    qdev_prop_set_uint32(armv7m, "num-irq", num_irq);
> -    qdev_prop_set_string(armv7m, "cpu-type", cpu_type);
> -    object_property_set_link(OBJECT(armv7m), OBJECT(get_system_memory()),
> -                                     "memory", &error_abort);

It looks like the snippet above is going to be a cut/paste for all v7m machines.

Would it achieve your goal by instead removing the armv7m_load_kernel
call from this function?

Cheers,

Joel

> -    /* This will exit with an error if the user passed us a bad cpu_type */
> -    qdev_init_nofail(armv7m);
> -
> -    armv7m_load_kernel(ARM_CPU(first_cpu), kernel_filename, mem_size);
> -    return armv7m;
> -}
> -
>  void armv7m_load_kernel(ARMCPU *cpu, const char *kernel_filename, int mem_size)
>  {
>      int image_size;
> --
> 2.17.1
>

  reply	other threads:[~2018-06-03  0:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 14:43 [Qemu-devel] [PATCH 0/2] armv7m: Remove armv7m_init() function Peter Maydell
2018-06-01 14:43 ` [Qemu-devel] [PATCH 1/2] stellaris: Stop using armv7m_init() Peter Maydell
2018-06-13 14:38   ` Stefan Hajnoczi
2018-06-01 14:43 ` [Qemu-devel] [PATCH 2/2] hw/arm/armv7m: Remove unused armv7m_init() function Peter Maydell
2018-06-03  0:48   ` Joel Stanley [this message]
2018-06-03 12:14     ` Peter Maydell
2018-06-13 14:39   ` Stefan Hajnoczi
2018-06-11 14:04 ` [Qemu-devel] [Qemu-arm] [PATCH 0/2] armv7m: Remove " Peter Maydell
2018-06-11 15:15   ` Philippe Mathieu-Daudé

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=CACPK8XfOZezMM2fL1aNoPx7Gjc1zeCJf5MNaS4FOPfZ5XABB2w@mail.gmail.com \
    --to=joel@jms.id.au \
    --cc=jim@groklearning.com \
    --cc=jusual@mail.ru \
    --cc=mail@steffen-goertz.de \
    --cc=patches@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).