qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Re: [RESEND][PATCH] gdbstub: Add vCont support


From: Jan Kiszka
Subject: [Qemu-devel] Re: [RESEND][PATCH] gdbstub: Add vCont support
Date: Thu, 15 Jan 2009 22:27:57 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666

Anthony Liguori wrote:
> Jan Kiszka wrote:
>> [ Also available via git://git.kiszka.org/qemu.git queue/gdb ]
>>
>> In order to set the VCPU for the next single-step command, you need gdb
>> 6.8 or better - and this patch. It enhances the existing support for
>> representing VCPUs as threads to the gdb frontend by introducing the
>> vCont remote gdb command. This is used by gdb to switch the debugging
>> focus for single-stepping multi-threaded targets.
>>
>> Signed-off-by: Jan Kiszka <address@hidden>
>>   
> 
> I think the consensus from the last posting of this was that modeling
> threads was pretty broken and that we should model as processes.  Did I
> miss something there?

There was this concern brought up by Paul Brook. I looked into this
again, but the picture didn't change for me:

 a) Modeling cpus as processes buys us nothing compared to threads given
    the fact that we cannot provide a stable memory mapping to the gdb
    frontend anyway. (*)

 b) The model is already part of mainline qemu. This patch is just
    about adding even more usefulness to it.

Jan

(*) Process abstraction is, if used at all, guest business. At best we
could try to invent (likely OS-specific) heuristics to identify
identical mappings and call them processes. I don't see a reasonable
benefit compared to the expected effort and unreliability.

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]