From: Laurent Vivier <lvivier@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P . Berrange" <berrange@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
Thomas Huth <thuth@redhat.com>,
qemu-arm@nongnu.org, qemu-ppc@nongnu.org,
Peter Maydell <peter.maydell@linaro.org>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Greg Kurz <groug@kaod.org>, Laurent Vivier <lvivier@redhat.com>
Subject: [Qemu-devel] [PATCH v2 1/3] hmp: fix "dump-quest-memory" segfault (ppc)
Date: Mon, 11 Sep 2017 16:20:54 +0200 [thread overview]
Message-ID: <20170911142056.15643-2-lvivier@redhat.com> (raw)
In-Reply-To: <20170911142056.15643-1-lvivier@redhat.com>
Commit fd5d23babf (hmp: fix "dump-quest-memory" segfault)
fixes the problem for i386, do the same for ppc.
Running QEMU with
qemu-system-ppc64 -M none -nographic -m 256
and executing
dump-guest-memory /dev/null 0 8192
results in segfault
Fix by checking if we have CPU.
Signed-off-by: Laurent Vivier <lvivier@redhat.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
---
target/ppc/arch_dump.c | 17 +++++++++++------
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/target/ppc/arch_dump.c b/target/ppc/arch_dump.c
index 8e9397aa58..dcb7b19950 100644
--- a/target/ppc/arch_dump.c
+++ b/target/ppc/arch_dump.c
@@ -224,17 +224,22 @@ typedef struct NoteFuncDescStruct NoteFuncDesc;
int cpu_get_dump_info(ArchDumpInfo *info,
const struct GuestPhysBlockList *guest_phys_blocks)
{
- PowerPCCPU *cpu = POWERPC_CPU(first_cpu);
- PowerPCCPUClass *pcc = POWERPC_CPU_GET_CLASS(cpu);
-
info->d_machine = PPC_ELF_MACHINE;
info->d_class = ELFCLASS;
- if ((*pcc->interrupts_big_endian)(cpu)) {
- info->d_endian = ELFDATA2MSB;
+ if (first_cpu) {
+ PowerPCCPU *cpu = POWERPC_CPU(first_cpu);
+ PowerPCCPUClass *pcc = POWERPC_CPU_GET_CLASS(cpu);
+
+ if ((*pcc->interrupts_big_endian)(cpu)) {
+ info->d_endian = ELFDATA2MSB;
+ } else {
+ info->d_endian = ELFDATA2LSB;
+ }
} else {
- info->d_endian = ELFDATA2LSB;
+ info->d_endian = ELFDATA2MSB;
}
+
/* 64KB is the max page size for pseries kernel */
if (strncmp(object_get_typename(qdev_get_machine()),
"pseries-", 8) == 0) {
--
2.13.5
next prev parent reply other threads:[~2017-09-11 14:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 14:20 [Qemu-devel] [PATCH v2 0/3] hmp: fix "dump-quest-memory" segfault Laurent Vivier
2017-09-11 14:20 ` Laurent Vivier [this message]
2017-09-11 14:20 ` [Qemu-devel] [PATCH v2 2/3] hmp: fix "dump-quest-memory" segfault (arm) Laurent Vivier
2017-09-11 14:39 ` Peter Maydell
2017-09-11 14:45 ` Thomas Huth
2017-09-11 16:40 ` Peter Maydell
2017-09-11 17:06 ` Thomas Huth
2017-09-12 8:11 ` Laurent Vivier
2017-09-11 15:35 ` Laurent Vivier
2017-09-11 15:08 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2017-09-11 15:25 ` Laurent Vivier
2017-09-11 15:38 ` Greg Kurz
2017-09-11 14:20 ` [Qemu-devel] [PATCH v2 3/3] tests/hmp: test "none" machine with memory Laurent Vivier
2017-09-11 14:51 ` Thomas Huth
2017-09-11 15:39 ` Laurent Vivier
2017-09-12 12:15 ` [Qemu-devel] [Qemu-arm] " Philippe Mathieu-Daudé
2017-09-11 14:34 ` [Qemu-devel] [PATCH v2 0/3] hmp: fix "dump-quest-memory" segfault no-reply
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=20170911142056.15643-2-lvivier@redhat.com \
--to=lvivier@redhat.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgilbert@redhat.com \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@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).