From: Thomas Huth <thuth@redhat.com>
To: Greg Kurz <groug@kaod.org>, Laurent Vivier <lvivier@redhat.com>
Cc: qemu-devel@nongnu.org,
"Daniel P . Berrange" <berrange@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
qemu-arm@nongnu.org, qemu-ppc@nongnu.org,
Peter Maydell <peter.maydell@linaro.org>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/3] hmp: fix "dump-quest-memory" segfault
Date: Tue, 12 Sep 2017 16:51:46 +0200 [thread overview]
Message-ID: <6198350f-a694-cf1b-ec00-4c42ccce39a6@redhat.com> (raw)
In-Reply-To: <20170912164644.2a0b6977@bahia.lan>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
On 12.09.2017 16:46, Greg Kurz wrote:
> On Tue, 12 Sep 2017 16:01:46 +0200
> Laurent Vivier <lvivier@redhat.com> wrote:
>
>> Fix aarch64 and ppc when dump-guest-memory is
>> used with none machine type and no CPU.
>>
>> The other machine types don't have the problem.
>>
>> Update test-hmp, to test none machine type
>> with (2 MB) and without memory, and add a test
>> to test dump-quest-memory without filter parameters
>> (it needs the fix from Cornelia Huck to work)
>>
>> v3:
>> - remove blank line after a comment
>> - forbid memory dump when there is no CPU
>>
>
> So in the end, we would forbid dump on aarch64 and
> ppc, while it is allowed on i386... I don't really
> care about which behavior is more appropriate but
> I guess they should be consistent at least.
It's kind of consistent: Allow it on architectures with fixed endianess,
but disallow it on architectures without fixed endianess ;-)
Honestly, it should not matter - we're talking here about the "none"
machine without a CPU ... as long as it does not crash, there is no need
for a working "dump-guest-memory" function here.
Thomas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-09-12 14:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 14:01 [Qemu-devel] [PATCH v3 0/3] hmp: fix "dump-quest-memory" segfault Laurent Vivier
2017-09-12 14:01 ` [Qemu-devel] [PATCH v3 1/3] hmp: fix "dump-quest-memory" segfault (ppc) Laurent Vivier
2017-09-12 14:10 ` Thomas Huth
2017-09-12 14:48 ` Greg Kurz
2017-09-13 5:35 ` David Gibson
2017-09-13 12:44 ` Dr. David Alan Gilbert
2017-09-13 12:48 ` Cornelia Huck
2017-09-13 12:49 ` Laurent Vivier
2017-09-13 13:19 ` Dr. David Alan Gilbert
2017-09-13 13:23 ` Laurent Vivier
2017-09-13 13:40 ` Dr. David Alan Gilbert
2017-09-13 12:54 ` David Gibson
2017-09-12 14:01 ` [Qemu-devel] [PATCH v3 2/3] hmp: fix "dump-quest-memory" segfault (arm) Laurent Vivier
2017-09-12 14:11 ` Thomas Huth
2017-09-12 14:50 ` Greg Kurz
2017-09-12 14:01 ` [Qemu-devel] [PATCH v3 3/3] tests/hmp: test "none" machine with memory Laurent Vivier
2017-09-12 14:13 ` Thomas Huth
2017-09-13 7:53 ` Cornelia Huck
2017-09-12 14:17 ` [Qemu-devel] [PATCH v3 0/3] hmp: fix "dump-quest-memory" segfault no-reply
2017-09-12 14:46 ` Greg Kurz
2017-09-12 14:51 ` Thomas Huth [this message]
2017-09-12 15:26 ` Greg Kurz
2017-09-12 15:36 ` Dr. David Alan Gilbert
2017-09-13 5:34 ` David Gibson
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=6198350f-a694-cf1b-ec00-4c42ccce39a6@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=groug@kaod.org \
--cc=lvivier@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).