Re: [Qemu-devel] Kernel memory allocation debugging with Qemu

2008-02-08 Thread Blue Swirl
On 2/8/08, Paul Brook [EMAIL PROTECTED] wrote: The patch takes a half of the memory and slows down the system. I think Qemu could be used instead. A channel (IO/MMIO) is created between the memory allocator in target kernel and Qemu running in the host. Memory allocator tells the allocated

Re: [Qemu-devel] Kernel memory allocation debugging with Qemu

2008-02-08 Thread Paul Brook
On Friday 08 February 2008, Blue Swirl wrote: On 2/8/08, Paul Brook [EMAIL PROTECTED] wrote: The patch takes a half of the memory and slows down the system. I think Qemu could be used instead. A channel (IO/MMIO) is created between the memory allocator in target kernel and Qemu running

Re: [Qemu-devel] Kernel memory allocation debugging with Qemu

2008-02-08 Thread Paul Brook
The patch takes a half of the memory and slows down the system. I think Qemu could be used instead. A channel (IO/MMIO) is created between the memory allocator in target kernel and Qemu running in the host. Memory allocator tells the allocated area to Qemu using the channel. Qemu changes the

[Qemu-devel] Kernel memory allocation debugging with Qemu

2008-02-08 Thread Blue Swirl
On KernelTrap there is a story about Linux kernel memory allocation debugging patch that allows detection of reads from uninitialized memory (http://kerneltrap.org/Linux/Debugging_With_kmemcheck). The patch takes a half of the memory and slows down the system. I think Qemu could be used instead.