From: Gleb Natapov <gleb@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@trasno.org>
Subject: Re: [Qemu-devel] [PATCH] add "info ioapic" monitor command
Date: Fri, 1 Jan 2010 12:23:11 +0200 [thread overview]
Message-ID: <20100101102311.GE9233@redhat.com> (raw)
In-Reply-To: <4B3CF428.7080806@codemonkey.ws>
On Thu, Dec 31, 2009 at 12:57:44PM -0600, Anthony Liguori wrote:
> On 12/31/2009 09:33 AM, Gleb Natapov wrote:
> >On Thu, Dec 31, 2009 at 08:15:29AM -0600, Anthony Liguori wrote:
> >>On 12/30/2009 06:16 PM, Gleb Natapov wrote:
> >>>It helps debug problems and it is not intrusive. Since 0.12 will be used
> >>>for a long time I want to add it there for convenience.
> >>
> >>stable is for bug fixes only.
> >>
> >This is to close minded. Not able to debug hard to reproduce problems when they appear
> >at the environment you can't replicate is a bug.
>
>
> Every feature is important to someone and there is at least someone
> who wants just about every feature backported to stable.
>
Agree and that is why practical judgment is needed. Humans, not binary
algorithm decides what to port and what not too.
> Looking at this patch, it adds a new monitor command which
> potentially means that the QMP protocol is changing (as there is now
> a new command). This is definitely not something we want to do in
> stable.
>
Does QMP expose list of available command through QMP protocol? Because if
it is not, there is no such issues as you describe at all, but event if it
is isn't the goal of QMP to make handling of such cases transparent for
management software. There will be one more element returned in command
list that is all.
--
Gleb.
next parent reply other threads:[~2010-01-01 10:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091224150242.GD5691@redhat.com>
[not found] ` <4B3AB429.5090303@codemonkey.ws>
[not found] ` <20091230092728.GB26899@redhat.com>
[not found] ` <4B3B60BE.8000302@codemonkey.ws>
[not found] ` <20091230142611.GB26626@redhat.com>
[not found] ` <20091230143019.GC26626@redhat.com>
[not found] ` <4B3BD891.1030102@codemonkey.ws>
[not found] ` <20091231001601.GF26626@redhat.com>
[not found] ` <4B3CB201.2070102@codemonkey.ws>
[not found] ` <20091231153305.GB9233@redhat.com>
[not found] ` <4B3CF428.7080806@codemonkey.ws>
2010-01-01 10:23 ` Gleb Natapov [this message]
[not found] ` <4B3AF8EE.8050106@redhat.com>
[not found] ` <4B3B610A.8060801@codemonkey.ws>
[not found] ` <4B3B618D.8080407@redhat.com>
[not found] ` <4B3BD838.3030200@codemonkey.ws>
[not found] ` <4B3C46DF.6010606@redhat.com>
[not found] ` <4B3CB2C0.5050205@codemonkey.ws>
[not found] ` <20091231153950.GC9233@redhat.com>
[not found] ` <4B3CF51E.8030404@codemonkey.ws>
2010-01-01 10:37 ` [Qemu-devel] [PATCH] add "info ioapic" monitor command Gleb Natapov
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=20100101102311.GE9233@redhat.com \
--to=gleb@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=quintela@trasno.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).