qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH, RFC 0/4] monitor device info infrastructure
Date: Thu, 13 May 2010 09:40:21 +0200	[thread overview]
Message-ID: <4BEBACE5.4010306@web.de> (raw)
In-Reply-To: <AANLkTil-VFu1P4q_4athK2r1XkBgZh47NGjj2wtZw3G9@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]

Blue Swirl wrote:
> Hi all,
> 
> I finally refreshed some of my monitor patches. PCI and HPET patches
> (attached, they don't apply anymore) need more work because of the new
> monitor design.
> 
> The patches provide a method for devices to register new monitor
> commands. This fixes some design problems, like useless
> pic_info/irq_info functions for most architectures.
> 
> I think automation via qdev field was requested the last time. I added
> something like this, though it doesn't fit the cases where several
> functions need to be registered.
> 
> Comments?

I'll soon send out a series that adds "device_show <qdev-path>" to
visualize the full state, something that will at least obsolete "info
pic" and "info hpet" sooner or later, maybe even more. Also, I would
like to qdev'ify CPUs in order to make them reachable for device_show
(which evaluates qdev->info.vmstate).

I'm not sure: How many use cases for a "dev_info" would remain?
Moreover, to dump statistics, we should rather add some "device_stats
<qdev-path>" command instead of mixing both usages under an info command.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2010-05-13 11:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12 20:56 [Qemu-devel] [PATCH, RFC 0/4] monitor device info infrastructure Blue Swirl
2010-05-13  7:40 ` Jan Kiszka [this message]
2010-05-13 18:50   ` [Qemu-devel] " Blue Swirl
2010-05-13 19:38     ` Jan Kiszka
2010-05-13 20:01       ` Blue Swirl

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=4BEBACE5.4010306@web.de \
    --to=jan.kiszka@web.de \
    --cc=blauwirbel@gmail.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).