All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Paul Brook <paul@codesourcery.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] monitor: Add port write command
Date: Tue, 14 Jul 2009 15:03:55 -0500	[thread overview]
Message-ID: <4A5CE4AB.3090708@us.ibm.com> (raw)
In-Reply-To: <200907142030.27019.paul@codesourcery.com>

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.
>
> 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,

That sounds like an issue with the devices.

The savevm state should not contain internal implementation details as 
that makes backwards compatibility hard to maintain.  I think for a 
large class of devices, the savevm state almost perfectly matches the 
device register state and having a nice interface to that seems like a 
useful thing.

-- 
Regards,

Anthony Liguori

  reply	other threads:[~2009-07-14 20:04 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 [this message]
2009-07-14 20:37       ` [Qemu-devel] " Jan Kiszka
2009-07-15  7:34     ` [Qemu-devel] " Gleb Natapov
2009-07-15 10:14       ` 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=4A5CE4AB.3090708@us.ibm.com \
    --to=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 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.