qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Paul Brook <paul@codesourcery.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] monitor: Add port write command
Date: Wed, 15 Jul 2009 10:34:51 +0300	[thread overview]
Message-ID: <20090715073451.GF28046@redhat.com> (raw)
In-Reply-To: <200907142030.27019.paul@codesourcery.com>

On Tue, Jul 14, 2009 at 08:30:25PM +0100, Paul Brook wrote:
> > What would be really cool about this change is that we could introduce a
> > new set of commands to manipulate device state.  We could save/restore
> > individual device state and that would allow us to dump device state via
> > the monitor and to manipulate individual fields of the device state.  I
> > think this could be pretty useful for debugging.
> 
> I'd be reluctant to expose the savevm state to the user.
> 
> For debugging qemu I don't see it providing any real benefit over firing up 
> GDB and poking directly at the device directly.
> 
Not all environments where you need to debug things have gdb, qemu
sources or even non striped qemu binary.

> For debugging the guest there is some argument for exposing the device state 
> (preferably via the gdb stub). However I think the savevm data tends to expose 
> too many internal implementation details, rather than the interesting guest 
> state. For most devices I'd expect the IO regions to be a better fit, 
> especially if you want to prevent qemu crashing when the user does invalid 
> writes.
> 
> Paul
> 

--
			Gleb.

  parent reply	other threads:[~2009-07-15  7:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14  8:20 [Qemu-devel] [PATCH] monitor: Add port write command Jan Kiszka
2009-07-14 15:06 ` Anthony Liguori
     [not found]   ` <m31voj47ht.fsf@neno.mitica>
2009-07-14 15:49     ` [Qemu-devel] " Anthony Liguori
2009-07-14 18:57   ` [Qemu-devel] " Blue Swirl
2009-07-14 19:30   ` Paul Brook
2009-07-14 20:03     ` Anthony Liguori
2009-07-14 20:37       ` [Qemu-devel] " Jan Kiszka
2009-07-15  7:34     ` Gleb Natapov [this message]
2009-07-15 10:14       ` [Qemu-devel] " Paul Brook
2009-07-15 10:40         ` Jan Kiszka
2009-07-15 11:14           ` Gleb Natapov
2009-07-15 11:12         ` Gleb Natapov
2009-07-15 12:36         ` Anthony Liguori
2009-07-15 14:38           ` Paul Brook

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=20090715073451.GF28046@redhat.com \
    --to=gleb@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=jan.kiszka@siemens.com \
    --cc=paul@codesourcery.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).