From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Eric Blake" <eblake@redhat.com>,
"Stefan Fritsch" <sf@sfritsch.de>,
qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Add chardev-send-break monitor command
Date: Tue, 06 Jun 2017 18:19:00 +0200 [thread overview]
Message-ID: <87a85ljdhn.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <39506179-0abd-5bba-89a2-fe89e6f3a167@redhat.com> (Paolo Bonzini's message of "Tue, 6 Jun 2017 16:17:42 +0200")
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 05/06/2017 14:24, Eric Blake wrote:
>> On 06/05/2017 03:52 AM, Stefan Fritsch wrote:
>>> Sending a break on a serial console can be useful for debugging the
>>> guest. But not all chardev backends support sending breaks (only telnet
>>> and mux do). The chardev-send-break command allows to send a break even
>>> if using other backends.
>>>
>>> Signed-off-by: Stefan Fritsch <sf@sfritsch.de>
>>> ---
>>> chardev/char.c | 12 ++++++++++++
>>> hmp-commands.hx | 16 ++++++++++++++++
>>> hmp.c | 8 ++++++++
>>> hmp.h | 1 +
>>> qapi-schema.json | 20 ++++++++++++++++++++
>>> 5 files changed, 57 insertions(+)
>>
>> Is there an obvious test that we can enhance to add coverage of the new
>> QMP command?
>
> You could have a new test covering hw/char/serial.c, but I wouldn't let
> that hold the patch.
Holding patches is pretty much the only leverage I have to get tests for
new stuff :)
Asking for tests that cover all of serial.c wouldn't be fair. But I am
asking for basic test coverage of new QMP commands.
Message-ID: <871sugkrw5.fsf@dusky.pond.sub.org>
https://lists.gnu.org/archive/html/qemu-devel/2017-03/msg00296.html
next prev parent reply other threads:[~2017-06-06 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 8:52 [Qemu-devel] [PATCH] Add chardev-send-break monitor command Stefan Fritsch
2017-06-05 12:24 ` Eric Blake
2017-06-06 14:17 ` Paolo Bonzini
2017-06-06 16:19 ` Markus Armbruster [this message]
2017-06-06 19:47 ` Stefan Fritsch
2017-06-06 22:44 ` Paolo Bonzini
2017-06-07 7:06 ` Markus Armbruster
2017-06-07 7:10 ` Paolo Bonzini
2017-06-08 9:31 ` Dr. David Alan Gilbert
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=87a85ljdhn.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sf@sfritsch.de \
/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.