Re: [Qemu-devel] [PATCH 1/2] Split out dump-guest-memory memory mapping code

2013-05-17 Thread Andreas Färber
Am 23.04.2013 17:54, schrieb Jens Freimann: > On Tue, Apr 23, 2013 at 09:41:43AM -0600, Eric Blake wrote: >> On 04/23/2013 09:30 AM, Jens Freimann wrote: >>> Split out dump-guest-memory memory mapping code to allow dumping without >>> memory mapping >>> >>> The qemu dump.c code currently requires C

Re: [Qemu-devel] [PATCH 1/2] Split out dump-guest-memory memory mapping code

2013-04-24 Thread Ekaterina Tumanova
On 04/23/2013 07:41 PM, Eric Blake wrote: On 04/23/2013 09:30 AM, Jens Freimann wrote: Split out dump-guest-memory memory mapping code to allow dumping without memory mapping The qemu dump.c code currently requires CONFIG_HAVE_CORE_DUMP as well as CONFIG_HAVE_GET_MEMORY_MAPPING. This allows for

Re: [Qemu-devel] [PATCH 1/2] Split out dump-guest-memory memory mapping code

2013-04-24 Thread Eric Blake
On 04/24/2013 11:07 AM, Ekaterina Tumanova wrote: >> This raises an interesting question about introspection - how will >> management apps (such as libvirt) be able to determine whether the >> paging command is supported for a given architecture? Do we need to >> expand the 'MachineInfo' QMP datat

Re: [Qemu-devel] [PATCH 1/2] Split out dump-guest-memory memory mapping code

2013-04-24 Thread Luiz Capitulino
On Wed, 24 Apr 2013 10:23:58 -0600 Eric Blake wrote: > On 04/24/2013 09:50 AM, Luiz Capitulino wrote: > >> This raises an interesting question about introspection - how will > >> management apps (such as libvirt) be able to determine whether the > >> paging command is supported for a given archit

Re: [Qemu-devel] [PATCH 1/2] Split out dump-guest-memory memory mapping code

2013-04-24 Thread Eric Blake
On 04/24/2013 09:50 AM, Luiz Capitulino wrote: >> This raises an interesting question about introspection - how will >> management apps (such as libvirt) be able to determine whether the >> paging command is supported for a given architecture? Do we need to >> expand the 'MachineInfo' QMP datatype

Re: [Qemu-devel] [PATCH 1/2] Split out dump-guest-memory memory mapping code

2013-04-24 Thread Luiz Capitulino
On Tue, 23 Apr 2013 09:41:43 -0600 Eric Blake wrote: > On 04/23/2013 09:30 AM, Jens Freimann wrote: > > Split out dump-guest-memory memory mapping code to allow dumping without > > memory mapping > > > > The qemu dump.c code currently requires CONFIG_HAVE_CORE_DUMP as well as > > CONFIG_HAVE_GET

Re: [Qemu-devel] [PATCH 1/2] Split out dump-guest-memory memory mapping code

2013-04-23 Thread Jens Freimann
On Tue, Apr 23, 2013 at 09:41:43AM -0600, Eric Blake wrote: > On 04/23/2013 09:30 AM, Jens Freimann wrote: > > Split out dump-guest-memory memory mapping code to allow dumping without > > memory mapping > > > > The qemu dump.c code currently requires CONFIG_HAVE_CORE_DUMP as well as > > CONFIG_HAV

Re: [Qemu-devel] [PATCH 1/2] Split out dump-guest-memory memory mapping code

2013-04-23 Thread Eric Blake
On 04/23/2013 09:30 AM, Jens Freimann wrote: > Split out dump-guest-memory memory mapping code to allow dumping without > memory mapping > > The qemu dump.c code currently requires CONFIG_HAVE_CORE_DUMP as well as > CONFIG_HAVE_GET_MEMORY_MAPPING. This allows for dumping with and without > paging

[Qemu-devel] [PATCH 1/2] Split out dump-guest-memory memory mapping code

2013-04-23 Thread Jens Freimann
Split out dump-guest-memory memory mapping code to allow dumping without memory mapping The qemu dump.c code currently requires CONFIG_HAVE_CORE_DUMP as well as CONFIG_HAVE_GET_MEMORY_MAPPING. This allows for dumping with and without paging. Some architectures will provide only the non-paging case