On 30.04.2013, at 12:20, Ekaterina Tumanova wrote:
> On 04/30/2013 02:02 PM, Alexander Graf wrote:
>> On 29.04.2013, at 13:39, Ekaterina Tumanova wrote:
>>
>>> On 04/26/2013 09:12 PM, Alexander Graf wrote:
On 23.04.2013, at 17:30, Jens Freimann wrote:
> Implement dump-guest-memory
On 04/30/2013 02:02 PM, Alexander Graf wrote:
On 29.04.2013, at 13:39, Ekaterina Tumanova wrote:
On 04/26/2013 09:12 PM, Alexander Graf wrote:
On 23.04.2013, at 17:30, Jens Freimann wrote:
Implement dump-guest-memory support for target s390x.
dump-guest-memory QEMU monitor command didn't wo
On 29.04.2013, at 13:39, Ekaterina Tumanova wrote:
> On 04/26/2013 09:12 PM, Alexander Graf wrote:
>> On 23.04.2013, at 17:30, Jens Freimann wrote:
>>
>>> Implement dump-guest-memory support for target s390x.
>>>
>>> dump-guest-memory QEMU monitor command didn't work for s390 architecture.
>>>
On 04/26/2013 09:12 PM, Alexander Graf wrote:
On 23.04.2013, at 17:30, Jens Freimann wrote:
Implement dump-guest-memory support for target s390x.
dump-guest-memory QEMU monitor command didn't work for s390 architecture.
The result of the command is supposed to be ELF format crash-readable
dump
On 23.04.2013, at 17:30, Jens Freimann wrote:
> Implement dump-guest-memory support for target s390x.
>
> dump-guest-memory QEMU monitor command didn't work for s390 architecture.
> The result of the command is supposed to be ELF format crash-readable
> dump.
> In order to implement this, the ar
Implement dump-guest-memory support for target s390x.
dump-guest-memory QEMU monitor command didn't work for s390 architecture.
The result of the command is supposed to be ELF format crash-readable
dump.
In order to implement this, the arch-specific part of dump-guest-memory
was added:
target-s390
