From: Markus Armbruster <armbru@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Dor Laor <dlaor@redhat.com>, Glauber Costa <glommer@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 0/5] Refactor and enhance RTC configuration
Date: Wed, 09 Sep 2009 20:03:44 +0200 [thread overview]
Message-ID: <874orcov0f.fsf@pike.pond.sub.org> (raw)
In-Reply-To: <4AA7DAA8.6030403@siemens.com> (Jan Kiszka's message of "Wed\, 09 Sep 2009 18\:41\:12 +0200")
Jan Kiszka <jan.kiszka@siemens.com> writes:
> Thinking further: Is there a way to discover the available qdev device
> parameters via the command line?
Not that I know of. Sounds quite feasible.
Monitor command "info qdm" and command line switch "-device \?" list
available devices. Make "info qdm DEVNAME" list device properties?
next prev parent reply other threads:[~2009-09-09 18:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 15:11 [Qemu-devel] [PATCH 0/5] Refactor and enhance RTC configuration Jan Kiszka
2009-09-09 15:11 ` [Qemu-devel] [PATCH 1/5] Rename QEMU_TIMER_* to QEMU_CLOCK_* Jan Kiszka
2009-09-09 15:11 ` [Qemu-devel] [PATCH 5/5] Enable host-clock-based RTC Jan Kiszka
2009-09-09 15:11 ` [Qemu-devel] [PATCH 4/5] Refactor RTC command line switches Jan Kiszka
2009-09-09 15:11 ` [Qemu-devel] [PATCH 3/5] Introduce QEMU_CLOCK_HOST Jan Kiszka
2009-09-09 15:11 ` [Qemu-devel] [PATCH 2/5] win32: Drop dead dyntick timer code Jan Kiszka
2009-09-09 15:40 ` [Qemu-devel] Re: [PATCH 0/5] Refactor and enhance RTC configuration Anthony Liguori
2009-09-09 16:24 ` Jan Kiszka
2009-09-09 16:41 ` Jan Kiszka
2009-09-09 18:03 ` Markus Armbruster [this message]
2009-09-09 17:59 ` Anthony Liguori
2009-09-09 20:00 ` Jan Kiszka
2009-09-09 20:18 ` Anthony Liguori
2009-09-09 22:23 ` Jamie Lokier
2009-09-11 8:54 ` Jan Kiszka
2009-09-13 15:08 ` Dor Laor
2009-09-13 15:37 ` Jan Kiszka
2009-09-14 13:36 ` Anthony Liguori
2009-09-14 15:40 ` Jan Kiszka
2009-09-09 17:59 ` Markus Armbruster
2009-09-10 10:41 ` Gerd Hoffmann
2009-09-09 17:33 ` Blue Swirl
2009-09-09 19:13 ` Jan Kiszka
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=874orcov0f.fsf@pike.pond.sub.org \
--to=armbru@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=dlaor@redhat.com \
--cc=glommer@redhat.com \
--cc=jan.kiszka@siemens.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.