All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Peter Cheung <mcheung63@hotmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Adding another debug protocol
Date: Wed, 14 Nov 2012 16:13:30 +0100	[thread overview]
Message-ID: <50A3B51A.2080004@siemens.com> (raw)
In-Reply-To: <BAY002-W13CD0451F5AD35B1067FE3B5530@phx.gbl>

On 2012-11-14 15:40, Peter Cheung wrote:
> Hi   Cannot use gdb protocol, because it is slow.

For any practical purpose I came across so far while debugging guest
kernels, that is not true when running against QEMU. Sure, if you want
to dump gigabytes of RAM this way, it will be a bottleneck. But when do
you have to do this while interactively debugging? Printing the content
will still take longer than transmitting it.

> Also, the original gdb stub can dump out GDT/IDT/CR0 directly.

That is true, but it should be addressed in gdb. Folks there are aware
of the issue and will happily discuss extension proposals and likely
also take the necessary patches. It will be trivial to adapt QEMU to
such an extension afterward.

Also, this is a temporary, just too long pending issue for x86. I'm not
aware of such limitations for other architectures.

And there is actually workaround for the meantime: issue "monitor info
registers" in the gdb session to obtain also those registers. "monitor
cpu N" will allow you to switch between CPUs. It's not nice but saved my
days a few times already.

Jan

> 
> Thanksfrom Peter
> 
>> Date: Wed, 14 Nov 2012 10:54:02 +0000
>> From: peter.maydell@linaro.org
>> To: mcheung63@hotmail.com
>> CC: qemu-devel@nongnu.org
>> Subject: Re: [Qemu-devel] Adding another debug protocol
>>
>> On 14 November 2012 10:45, Peter Cheung <mcheung63@hotmail.com> wrote:
>>> Dear All
>>>     I am going to add another debugger server into QEMU, so i need to
>>> 1) create another socket server, similar than gdbserver, to receive the
>>> command from debugger
>>> 2) add another option, such as "--start-debugger-server" to start the socket
>>> server.
>>>
>>> After I work out the whole thing, how can i ask for the qemu maintainer to
>>> accept my code? I believe i should write a proposal first.
>>
>> Probably worth including a summary of why your second debug protocol
>> couldn't be implemented as a translation layer between gdbserver
>> protocol and whatever it is you need.
>>
>> -- PMM
>>
>  		 	   		  
> 

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2012-11-14 15:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 10:45 [Qemu-devel] Adding another debug protocol Peter Cheung
2012-11-14 10:54 ` Peter Maydell
2012-11-14 14:40   ` Peter Cheung
2012-11-14 15:13     ` Jan Kiszka [this message]
2012-11-14 16:28       ` Peter Cheung
2012-11-14 16:43         ` Jan Kiszka
2012-11-15  1:58           ` Peter Cheung
2012-11-15  8:02             ` Jan Kiszka
2012-11-15  8:44               ` Peter Cheung

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50A3B51A.2080004@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=mcheung63@hotmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.