[Qemu-devel] Re: KQEMU code organization

[Jan Kiszka <jan.kiszka@siemens.com>]

Fabrice Bellard wrote:
> Jan Kiszka wrote:
>> Hi,
>>
>> is there a technical reason why the kqemu kernel module is built out of
>> a binary blob (monitor-image.bin->monitor-image.h)? Does this simply
>> date back to the time when wrapper and core were distributed under
>> different licenses?
> 
> This is a technical reason: the "blob" is run in an address space
> different from the host kernel.

Well, easy to claim, I know, but I don't think this is a hard reason.
However, as overcoming genmon and genoffset may require quite some
refactoring, I'm not sure if it's worth it.

For debugging purposes I meanwhile created my own build system anyway.
gdb fortunately accepts an monitor-image.out built with -g so that
source level debugging of the monitor is possible as well.

/me now needs to understand how this thing works...

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux