All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Alexander Graf <agraf@suse.de>,
	Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Jens Freimann <jfrei@linux.vnet.ibm.com>,
	Ekaterina Tumanova <tumanova@linux.vnet.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v4] s390: Implement dump-guest-memory support for target s390x
Date: Wed, 10 Jul 2013 14:15:14 +0200	[thread overview]
Message-ID: <51DD5052.1040706@suse.de> (raw)
In-Reply-To: <6A1648DC-7BA6-4101-9B5F-BA241A56156B@suse.de>

Am 10.07.2013 12:37, schrieb Alexander Graf:
> On 10.07.2013, at 12:27, Christian Borntraeger wrote:
>> On 05/07/13 14:02, Jens Freimann wrote:
>>> With this patch dump-guest-memory on s390 produces an ELF formatted,
>>> crash-readable dump.
>>> In order to implement this, the arch-specific part of dump-guest-memory
>>> was added:
>>> target-s390x/arch_dump.c contains the whole set of function for writing
>>> Elf note sections of all types for s390x.
>>>
>>> Signed-off-by: Ekaterina Tumanova <tumanova@linux.vnet.ibm.com>
>>> Signed-off-by: Jens Freimann <jfrei@linux.vnet.ibm.com>
>> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
>>
>> I can confirm that this patch creates proper dumps readable by crash with valid
>> memory and valid register content. Would be good to see this upstream.
>>
>> Meanwhile this patch no longer cleanly applies due to
>> commit 878096eeb278a8ac1ccd6667af73e026f29b4cf5
>>    cpu: Turn cpu_dump_{state,statistics}() into CPUState hooks
>>
>> The fixup is trivial.
>> Alex, please apply.
> 
> I'd like to get an Ack from Andreas too :). But then I'll happily apply it.

I am mostly happy and had offered Alex to reply with a fixup patch to
squash on top, but am still buried in downstream work and didn't get to
preparing that yet: v4 started #including cpu-qom.h, which it shouldn't
(only cpu.h does in the tree) - if Alex wants to drop that line himself,
please add my Reviewed-by on top, Alex. I did not check whether the
s390x implementation is functionally correct, just the changed API and
any style issues.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-07-10 12:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05 12:02 [Qemu-devel] [PATCH v4] s390: Implement dump-guest-memory support for target s390x Jens Freimann
2013-07-10 10:27 ` Christian Borntraeger
2013-07-10 10:37   ` Alexander Graf
2013-07-10 12:15     ` Andreas Färber [this message]
2013-07-10 12:16       ` Alexander Graf
  -- strict thread matches above, loose matches on Subject: below --
2013-06-25 15:39 [Qemu-devel] [PATCH v3] " Andreas Färber
2013-06-26 14:46 ` [Qemu-devel] [PATCH v4] " Jens Freimann

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=51DD5052.1040706@suse.de \
    --to=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=jfrei@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tumanova@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.