From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Alexander Graf <agraf@suse.de>, Michael Walle <michael@walle.cc>,
qemu-ppc@nongnu.org, David Gibson <dgibson@redhat.com>,
Leon Alrae <leon.alrae@imgtec.com>,
Aurelien Jarno <aurelien@aurel32.net>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] Are "info pic" and "info irq" still of any use?
Date: Tue, 31 Mar 2015 12:03:10 +0200 [thread overview]
Message-ID: <551A70DE.1030508@redhat.com> (raw)
In-Reply-To: <87pp7pa3sa.fsf@blackfin.pond.sub.org>
On 31/03/2015 11:56, Markus Armbruster wrote:
> These commands look like bit-rotted development aids to me.
>
> They're limited to just a few interrupt controllers. For the most
> common machine types and accelerators, they do nothing.
>
> They complicate David Gibson's work on disentangling dependencies on
> ISA.
>
> I'm cc'ing the maintainers of all machines that can be configured in a
> way that makes these commands do something. Please speak up if you
> think they provide value.
For x86, they can be removed. However, it would be nice to provide
access to the same information via QOM, especially for "info pic". This
is the old QIDL project.
Paolo
next prev parent reply other threads:[~2015-03-31 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 9:56 [Qemu-devel] Are "info pic" and "info irq" still of any use? Markus Armbruster
2015-03-31 10:03 ` Paolo Bonzini [this message]
2015-03-31 11:19 ` Markus Armbruster
2015-03-31 11:16 ` Michael Walle
2015-04-01 9:07 ` Kevin Wolf
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=551A70DE.1030508@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=aurelien@aurel32.net \
--cc=dgibson@redhat.com \
--cc=leon.alrae@imgtec.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=michael@walle.cc \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rth@twiddle.net \
/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.