qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Igor Mammedov" <imammedo@redhat.com>,
	"Alistair Francis" <alistair@alistair23.me>,
	"Gavin Shan" <gshan@redhat.com>,
	"Andrew Jeffery" <andrew@codeconstruct.com.au>,
	"Cédric Le Goater" <clg@kaod.org>,
	qemu-arm@nongnu.org, "Igor Mitsyanko" <i.mitsyanko@gmail.com>,
	"Joel Stanley" <joel@jms.id.au>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	"Rob Herring" <robh@kernel.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH 0/8] hw/arm/cortex-a: Check for CPU types in machine_run_board_init()
Date: Tue, 23 Jan 2024 07:38:34 +0100	[thread overview]
Message-ID: <20240123063842.35255-1-philmd@linaro.org> (raw)

Following Gavin recent CPU type enforcement cleanups,
restrict more single-CPU ARM machines (here Cortex-A SoC).

Based-on: <20240118200643.29037-1-philmd@linaro.org> (arm-next)

Philippe Mathieu-Daudé (8):
  hw/arm/exynos: Check for CPU types in machine_run_board_init()
  hw/arm/highbank: Check for CPU types in machine_run_board_init()
  hw/arm/vexpress: Check for CPU types in machine_run_board_init()
  hw/arm/aspeed/2400: Check for CPU types in machine_run_board_init()
  hw/arm/aspeed/2500: Check for CPU types in machine_run_board_init()
  hw/arm/aspeed/2600: Check for CPU types in machine_run_board_init()
  hw/arm/aspeed/1030: Check for CPU types in machine_run_board_init()
  hw/arm/zynq: Check for CPU types in machine_run_board_init()

 hw/arm/aspeed.c         | 40 ++++++++++++++++++++++++++++++++++++++++
 hw/arm/exynos4_boards.c |  8 ++++++++
 hw/arm/highbank.c       | 10 ++++++++++
 hw/arm/vexpress.c       | 10 ++++++++++
 hw/arm/xilinx_zynq.c    |  5 +++++
 5 files changed, 73 insertions(+)

-- 
2.41.0



             reply	other threads:[~2024-01-23  6:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23  6:38 Philippe Mathieu-Daudé [this message]
2024-01-23  6:38 ` [PATCH 1/8] hw/arm/exynos: Check for CPU types in machine_run_board_init() Philippe Mathieu-Daudé
2024-01-23  6:38 ` [PATCH 2/8] hw/arm/highbank: " Philippe Mathieu-Daudé
2024-01-23  6:38 ` [PATCH 3/8] hw/arm/vexpress: " Philippe Mathieu-Daudé
2024-01-23  6:38 ` [PATCH 4/8] hw/arm/aspeed/2400: " Philippe Mathieu-Daudé
2024-01-23  9:03   ` Cédric Le Goater
2024-01-23  6:38 ` [PATCH 5/8] hw/arm/aspeed/2500: " Philippe Mathieu-Daudé
2024-01-23  9:03   ` Cédric Le Goater
2024-01-23  6:38 ` [PATCH 6/8] hw/arm/aspeed/2600: " Philippe Mathieu-Daudé
2024-01-23  9:27   ` Cédric Le Goater
2024-01-23  9:35     ` Cédric Le Goater
2024-01-23  6:38 ` [PATCH 7/8] hw/arm/aspeed/1030: " Philippe Mathieu-Daudé
2024-01-23  6:38 ` [PATCH 8/8] hw/arm/zynq: " 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=20240123063842.35255-1-philmd@linaro.org \
    --to=philmd@linaro.org \
    --cc=alistair@alistair23.me \
    --cc=andrew@codeconstruct.com.au \
    --cc=clg@kaod.org \
    --cc=edgar.iglesias@gmail.com \
    --cc=gshan@redhat.com \
    --cc=i.mitsyanko@gmail.com \
    --cc=imammedo@redhat.com \
    --cc=joel@jms.id.au \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=robh@kernel.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).