From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Laurent Vivier" <laurent@vivier.eu>,
"Peter Xu" <peterx@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: [PATCH 0/3] m68k: virt: fix reboot
Date: Sat, 15 Jan 2022 21:37:22 +0100 [thread overview]
Message-ID: <20220115203725.3834712-1-laurent@vivier.eu> (raw)
This series fixes the reboot of the virt-m68k machine
by correctly initializing the start address and fixing
the ELF kernel image.
The two first patches were already sent last year and
never merged:
https://patchwork.kernel.org/project/qemu-devel/cover/20210429141326.69245-1-laurent@vivier.eu/
Thanks,
Laurent
Laurent Vivier (2):
hw/elf_ops: clear uninitialized segment space
m68k: virt: correctly set the initial PC
Philippe Mathieu-Daudé (1):
exec/memory: Extract address_space_set() from dma_memory_set()
include/exec/memory.h | 16 ++++++++++++++++
include/hw/elf_ops.h | 13 +++++++++++++
hw/core/loader.c | 4 ++++
hw/m68k/virt.c | 22 +++++++++++++++++-----
softmmu/dma-helpers.c | 15 +--------------
softmmu/physmem.c | 19 +++++++++++++++++++
6 files changed, 70 insertions(+), 19 deletions(-)
--
2.34.1
next reply other threads:[~2022-01-15 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 20:37 Laurent Vivier [this message]
2022-01-15 20:37 ` [PATCH 1/3] exec/memory: Extract address_space_set() from dma_memory_set() Laurent Vivier
2022-01-17 8:23 ` David Hildenbrand
2022-01-17 8:57 ` Peter Xu
2022-01-15 20:37 ` [PATCH 2/3] hw/elf_ops: clear uninitialized segment space Laurent Vivier
2022-01-15 20:37 ` [PATCH 3/3] m68k: virt: correctly set the initial PC Laurent Vivier
2022-01-20 8:11 ` [PATCH 0/3] m68k: virt: fix reboot Laurent Vivier
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=20220115203725.3834712-1-laurent@vivier.eu \
--to=laurent@vivier.eu \
--cc=david@redhat.com \
--cc=f4bug@amsat.org \
--cc=pbonzini@redhat.com \
--cc=peterx@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 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).