All of lore.kernel.org
 help / color / mirror / Atom feed
* [Qemu-devel] [PATCH v2] Add chardev-send-break monitor command
@ 2017-06-11  7:48 Stefan Fritsch
  2017-06-27 19:40 ` Eric Blake
  2017-07-19 15:01 ` Thomas Huth
  0 siblings, 2 replies; 8+ messages in thread
From: Stefan Fritsch @ 2017-06-11  7:48 UTC (permalink / raw)
  To: qemu-devel
  Cc: Stefan Fritsch, Paolo Bonzini, Marc-André Lureau,
	Dr. David Alan Gilbert, Eric Blake, Markus Armbruster

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>
Acked-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
---
v2: added tests and Acked-by line

 chardev/char.c    | 12 ++++++++++++
 hmp-commands.hx   | 16 ++++++++++++++++
 hmp.c             |  8 ++++++++
 hmp.h             |  1 +
 qapi-schema.json  | 20 ++++++++++++++++++++
 tests/test-char.c | 12 ++++++++++--
 tests/test-hmp.c  |  1 +
 7 files changed, 68 insertions(+), 2 deletions(-)

diff --git a/chardev/char.c b/chardev/char.c
index 7aa0210765..cc56bca672 100644
--- a/chardev/char.c
+++ b/chardev/char.c
@@ -951,6 +951,18 @@ void qmp_chardev_remove(const char *id, Error **errp)
     object_unparent(OBJECT(chr));
 }
 
+void qmp_chardev_send_break(const char *id, Error **errp)
+{
+    Chardev *chr;
+
+    chr = qemu_chr_find(id);
+    if (chr == NULL) {
+        error_setg(errp, "Chardev '%s' not found", id);
+        return;
+    }
+    qemu_chr_be_event(chr, CHR_EVENT_BREAK);
+}
+
 void qemu_chr_cleanup(void)
 {
     object_unparent(get_chardevs_root());
diff --git a/hmp-commands.hx b/hmp-commands.hx
index e763606fe5..fc8d54b52a 100644
--- a/hmp-commands.hx
+++ b/hmp-commands.hx
@@ -1745,6 +1745,22 @@ Removes the chardev @var{id}.
 ETEXI
 
     {
+        .name       = "chardev-send-break",
+        .args_type  = "id:s",
+        .params     = "id",
+        .help       = "send break on chardev",
+        .cmd        = hmp_chardev_send_break,
+        .command_completion = chardev_remove_completion,
+    },
+
+STEXI
+@item chardev-send-break id
+@findex chardev-send-break
+Sends break on the chardev @var{id}.
+
+ETEXI
+
+    {
         .name       = "qemu-io",
         .args_type  = "device:B,command:s",
         .params     = "[device] \"[command]\"",
diff --git a/hmp.c b/hmp.c
index 8c72c58b20..94cafe970e 100644
--- a/hmp.c
+++ b/hmp.c
@@ -2233,6 +2233,14 @@ void hmp_chardev_remove(Monitor *mon, const QDict *qdict)
     hmp_handle_error(mon, &local_err);
 }
 
+void hmp_chardev_send_break(Monitor *mon, const QDict *qdict)
+{
+    Error *local_err = NULL;
+
+    qmp_chardev_send_break(qdict_get_str(qdict, "id"), &local_err);
+    hmp_handle_error(mon, &local_err);
+}
+
 void hmp_qemu_io(Monitor *mon, const QDict *qdict)
 {
     BlockBackend *blk;
diff --git a/hmp.h b/hmp.h
index d8b94ce9dc..214b2617e7 100644
--- a/hmp.h
+++ b/hmp.h
@@ -103,6 +103,7 @@ void hmp_nbd_server_add(Monitor *mon, const QDict *qdict);
 void hmp_nbd_server_stop(Monitor *mon, const QDict *qdict);
 void hmp_chardev_add(Monitor *mon, const QDict *qdict);
 void hmp_chardev_remove(Monitor *mon, const QDict *qdict);
+void hmp_chardev_send_break(Monitor *mon, const QDict *qdict);
 void hmp_qemu_io(Monitor *mon, const QDict *qdict);
 void hmp_cpu_add(Monitor *mon, const QDict *qdict);
 void hmp_object_add(Monitor *mon, const QDict *qdict);
diff --git a/qapi-schema.json b/qapi-schema.json
index 4b50b652d3..e01dd83dd9 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -5114,6 +5114,26 @@
 { 'command': 'chardev-remove', 'data': {'id': 'str'} }
 
 ##
+# @chardev-send-break:
+#
+# Send a break to a character device
+#
+# @id: the chardev's ID, must exist
+#
+# Returns: Nothing on success
+#
+# Since: 2.10
+#
+# Example:
+#
+# -> { "execute": "chardev-send-break", "arguments": { "id" : "foo" } }
+# <- { "return": {} }
+#
+##
+{ 'command': 'chardev-send-break', 'data': {'id': 'str'} }
+
+
+##
 # @TpmModel:
 #
 # An enumeration of TPM models
diff --git a/tests/test-char.c b/tests/test-char.c
index dfe856cb85..c7f7ec1798 100644
--- a/tests/test-char.c
+++ b/tests/test-char.c
@@ -53,7 +53,9 @@ static void fe_event(void *opaque, int event)
     FeHandler *h = opaque;
 
     h->last_event = event;
-    quit = true;
+    if (event != CHR_EVENT_BREAK) {
+        quit = true;
+    }
 }
 
 #ifdef CONFIG_HAS_GLIB_SUBPROCESS_TESTS
@@ -491,7 +493,7 @@ static void char_file_test(void)
 
         file.in = fifo;
         file.has_in = true;
-        chr = qemu_chardev_new(NULL, TYPE_CHARDEV_FILE, &backend,
+        chr = qemu_chardev_new("label-file", TYPE_CHARDEV_FILE, &backend,
                                &error_abort);
 
         qemu_chr_fe_init(&be, chr, &error_abort);
@@ -501,6 +503,12 @@ static void char_file_test(void)
                                  fe_event,
                                  &fe, NULL, true);
 
+        g_assert_cmpint(fe.last_event, !=, CHR_EVENT_BREAK);
+        qmp_chardev_send_break("label-foo", NULL);
+        g_assert_cmpint(fe.last_event, !=, CHR_EVENT_BREAK);
+        qmp_chardev_send_break("label-file", NULL);
+        g_assert_cmpint(fe.last_event, ==, CHR_EVENT_BREAK);
+
         main_loop();
 
         close(fd);
diff --git a/tests/test-hmp.c b/tests/test-hmp.c
index 99e35ec15a..6dfa0c36e2 100644
--- a/tests/test-hmp.c
+++ b/tests/test-hmp.c
@@ -22,6 +22,7 @@ static int verbose;
 static const char *hmp_cmds[] = {
     "boot_set ndc",
     "chardev-add null,id=testchardev1",
+    "chardev-send-break testchardev2",
     "chardev-remove testchardev1",
     "commit all",
     "cpu-add 1",
-- 
2.11.0

^ permalink raw reply related	[flat|nested] 8+ messages in thread

* Re: [Qemu-devel] [PATCH v2] Add chardev-send-break monitor command
  2017-06-11  7:48 [Qemu-devel] [PATCH v2] Add chardev-send-break monitor command Stefan Fritsch
@ 2017-06-27 19:40 ` Eric Blake
  2017-06-29 14:27   ` Marc-André Lureau
  2017-06-29 15:00   ` Dr. David Alan Gilbert
  2017-07-19 15:01 ` Thomas Huth
  1 sibling, 2 replies; 8+ messages in thread
From: Eric Blake @ 2017-06-27 19:40 UTC (permalink / raw)
  To: Stefan Fritsch, qemu-devel
  Cc: Paolo Bonzini, Marc-André Lureau, Dr. David Alan Gilbert,
	Markus Armbruster

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

On 06/11/2017 02:48 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>
> Acked-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> v2: added tests and Acked-by line
> 

> +++ b/hmp-commands.hx
> @@ -1745,6 +1745,22 @@ Removes the chardev @var{id}.
>  ETEXI
>  
>      {
> +        .name       = "chardev-send-break",
> +        .args_type  = "id:s",
> +        .params     = "id",
> +        .help       = "send break on chardev",

Compare this wording,...

> +STEXI
> +@item chardev-send-break id
> +@findex chardev-send-break
> +Sends break on the chardev @var{id}.

repeated here,

> +++ b/qapi-schema.json
> @@ -5114,6 +5114,26 @@
>  { 'command': 'chardev-remove', 'data': {'id': 'str'} }
>  
>  ##
> +# @chardev-send-break:
> +#
> +# Send a break to a character device

...with this wording.  I like 'send a break' better than 'send break',
but even better might be 'send a break sequence' or even 'emulate a
break sequence' (by definition, a break is NOT a character, but on bare
metal character devices it IS a defined electrical sequence distinct
from characters to make the recipient aware that the sender is trying to
get attention).

Otherwise, the patch looks fine to me.  If all that changes is some
word-smithing (and the maintainer may be willing to do that), you can add:
Reviewed-by: Eric Blake <eblake@redhat.com>

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Qemu-devel] [PATCH v2] Add chardev-send-break monitor command
  2017-06-27 19:40 ` Eric Blake
@ 2017-06-29 14:27   ` Marc-André Lureau
  2017-06-29 14:41     ` Dr. David Alan Gilbert
  2017-06-29 15:00   ` Dr. David Alan Gilbert
  1 sibling, 1 reply; 8+ messages in thread
From: Marc-André Lureau @ 2017-06-29 14:27 UTC (permalink / raw)
  To: Eric Blake, Stefan Fritsch, qemu-devel
  Cc: Paolo Bonzini, Dr. David Alan Gilbert, Markus Armbruster

On Tue, Jun 27, 2017 at 9:46 PM Eric Blake <eblake@redhat.com> wrote:

> On 06/11/2017 02:48 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>
> > Acked-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>

Looks good to me,
 Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>


> ---
> > v2: added tests and Acked-by line
> >
>
> > +++ b/hmp-commands.hx
> > @@ -1745,6 +1745,22 @@ Removes the chardev @var{id}.
> >  ETEXI
> >
> >      {
> > +        .name       = "chardev-send-break",
> > +        .args_type  = "id:s",
> > +        .params     = "id",
> > +        .help       = "send break on chardev",
>
> Compare this wording,...
>
> > +STEXI
> > +@item chardev-send-break id
> > +@findex chardev-send-break
> > +Sends break on the chardev @var{id}.
>
> repeated here,
>
> > +++ b/qapi-schema.json
> > @@ -5114,6 +5114,26 @@
> >  { 'command': 'chardev-remove', 'data': {'id': 'str'} }
> >
> >  ##
> > +# @chardev-send-break:
> > +#
> > +# Send a break to a character device
>
> ...with this wording.  I like 'send a break' better than 'send break',
> but even better might be 'send a break sequence' or even 'emulate a
> break sequence' (by definition, a break is NOT a character, but on bare
> metal character devices it IS a defined electrical sequence distinct
> from characters to make the recipient aware that the sender is trying to
> get attention).
>
> Otherwise, the patch looks fine to me.  If all that changes is some
> word-smithing (and the maintainer may be willing to do that), you can add:
> Reviewed-by: Eric Blake <eblake@redhat.com>
>

Paolo would you take it (perhaps on the next iteration)?

thanks
-- 
Marc-André Lureau

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Qemu-devel] [PATCH v2] Add chardev-send-break monitor command
  2017-06-29 14:27   ` Marc-André Lureau
@ 2017-06-29 14:41     ` Dr. David Alan Gilbert
  0 siblings, 0 replies; 8+ messages in thread
From: Dr. David Alan Gilbert @ 2017-06-29 14:41 UTC (permalink / raw)
  To: Marc-André Lureau
  Cc: Eric Blake, Stefan Fritsch, qemu-devel, Paolo Bonzini, Markus Armbruster

* Marc-André Lureau (marcandre.lureau@gmail.com) wrote:
> On Tue, Jun 27, 2017 at 9:46 PM Eric Blake <eblake@redhat.com> wrote:
> 
> > On 06/11/2017 02:48 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>
> > > Acked-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> >
> 
> Looks good to me,
>  Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> 
> 
> > ---
> > > v2: added tests and Acked-by line
> > >
> >
> > > +++ b/hmp-commands.hx
> > > @@ -1745,6 +1745,22 @@ Removes the chardev @var{id}.
> > >  ETEXI
> > >
> > >      {
> > > +        .name       = "chardev-send-break",
> > > +        .args_type  = "id:s",
> > > +        .params     = "id",
> > > +        .help       = "send break on chardev",
> >
> > Compare this wording,...
> >
> > > +STEXI
> > > +@item chardev-send-break id
> > > +@findex chardev-send-break
> > > +Sends break on the chardev @var{id}.
> >
> > repeated here,
> >
> > > +++ b/qapi-schema.json
> > > @@ -5114,6 +5114,26 @@
> > >  { 'command': 'chardev-remove', 'data': {'id': 'str'} }
> > >
> > >  ##
> > > +# @chardev-send-break:
> > > +#
> > > +# Send a break to a character device
> >
> > ...with this wording.  I like 'send a break' better than 'send break',
> > but even better might be 'send a break sequence' or even 'emulate a
> > break sequence' (by definition, a break is NOT a character, but on bare
> > metal character devices it IS a defined electrical sequence distinct
> > from characters to make the recipient aware that the sender is trying to
> > get attention).
> >
> > Otherwise, the patch looks fine to me.  If all that changes is some
> > word-smithing (and the maintainer may be willing to do that), you can add:
> > Reviewed-by: Eric Blake <eblake@redhat.com>
> >
> 
> Paolo would you take it (perhaps on the next iteration)?

I can take it through HMP; I'm just doing a pull now.

Dave

> thanks
> -- 
> Marc-André Lureau
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Qemu-devel] [PATCH v2] Add chardev-send-break monitor command
  2017-06-27 19:40 ` Eric Blake
  2017-06-29 14:27   ` Marc-André Lureau
@ 2017-06-29 15:00   ` Dr. David Alan Gilbert
  2017-06-30 15:53     ` Stefan Fritsch
  1 sibling, 1 reply; 8+ messages in thread
From: Dr. David Alan Gilbert @ 2017-06-29 15:00 UTC (permalink / raw)
  To: Eric Blake
  Cc: Stefan Fritsch, qemu-devel, Paolo Bonzini,
	Marc-André Lureau, Markus Armbruster

* Eric Blake (eblake@redhat.com) wrote:
> On 06/11/2017 02:48 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>
> > Acked-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> > ---
> > v2: added tests and Acked-by line
> > 
> 
> > +++ b/hmp-commands.hx
> > @@ -1745,6 +1745,22 @@ Removes the chardev @var{id}.
> >  ETEXI
> >  
> >      {
> > +        .name       = "chardev-send-break",
> > +        .args_type  = "id:s",
> > +        .params     = "id",
> > +        .help       = "send break on chardev",
> 
> Compare this wording,...
> 
> > +STEXI
> > +@item chardev-send-break id
> > +@findex chardev-send-break
> > +Sends break on the chardev @var{id}.
> 
> repeated here,
> 
> > +++ b/qapi-schema.json
> > @@ -5114,6 +5114,26 @@
> >  { 'command': 'chardev-remove', 'data': {'id': 'str'} }
> >  
> >  ##
> > +# @chardev-send-break:
> > +#
> > +# Send a break to a character device
> 
> ...with this wording.  I like 'send a break' better than 'send break',
> but even better might be 'send a break sequence' or even 'emulate a
> break sequence' (by definition, a break is NOT a character, but on bare
> metal character devices it IS a defined electrical sequence distinct
> from characters to make the recipient aware that the sender is trying to
> get attention).
> 
> Otherwise, the patch looks fine to me.  If all that changes is some
> word-smithing (and the maintainer may be willing to do that), you can add:
> Reviewed-by: Eric Blake <eblake@redhat.com>

I'll go with the 'send a break' - the official terminology seems to
be a 'break condition', but I've never heard anyone say that,
it's always been 'send a break'.

diff --git a/hmp-commands.hx b/hmp-commands.hx
index fc8d54b52a..275ccdfbc7 100644
--- a/hmp-commands.hx
+++ b/hmp-commands.hx
@@ -1748,7 +1748,7 @@ ETEXI
         .name       = "chardev-send-break",
         .args_type  = "id:s",
         .params     = "id",
-        .help       = "send break on chardev",
+        .help       = "send a break on chardev",
         .cmd        = hmp_chardev_send_break,
         .command_completion = chardev_remove_completion,
     },
@@ -1756,7 +1756,7 @@ ETEXI
 STEXI
 @item chardev-send-break id
 @findex chardev-send-break
-Sends break on the chardev @var{id}.
+Send a break on the chardev @var{id}.

 ETEXI


Queued to HMP

Dave

> 
> -- 
> Eric Blake, Principal Software Engineer
> Red Hat, Inc.           +1-919-301-3266
> Virtualization:  qemu.org | libvirt.org
> 



--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

^ permalink raw reply related	[flat|nested] 8+ messages in thread

* Re: [Qemu-devel] [PATCH v2] Add chardev-send-break monitor command
  2017-06-29 15:00   ` Dr. David Alan Gilbert
@ 2017-06-30 15:53     ` Stefan Fritsch
  0 siblings, 0 replies; 8+ messages in thread
From: Stefan Fritsch @ 2017-06-30 15:53 UTC (permalink / raw)
  To: Dr. David Alan Gilbert
  Cc: Eric Blake, qemu-devel, Paolo Bonzini, Marc-André Lureau,
	Markus Armbruster

On Thursday, 29 June 2017 16:00:54 CEST Dr. David Alan Gilbert wrote:
> * Eric Blake (eblake@redhat.com) wrote:
> > On 06/11/2017 02:48 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>
> > > Acked-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> > > ---
> > > v2: added tests and Acked-by line
> > > 
> > > 
> > > +++ b/hmp-commands.hx
> > > @@ -1745,6 +1745,22 @@ Removes the chardev @var{id}.
> > > 
> > >  ETEXI
> > >  
> > >      {
> > > 
> > > +        .name       = "chardev-send-break",
> > > +        .args_type  = "id:s",
> > > +        .params     = "id",
> > > +        .help       = "send break on chardev",
> > 
> > Compare this wording,...
> > 
> > > +STEXI
> > > +@item chardev-send-break id
> > > +@findex chardev-send-break
> > > +Sends break on the chardev @var{id}.
> > 
> > repeated here,
> > 
> > > +++ b/qapi-schema.json
> > > @@ -5114,6 +5114,26 @@
> > > 
> > >  { 'command': 'chardev-remove', 'data': {'id': 'str'} }
> > >  
> > >  ##
> > > 
> > > +# @chardev-send-break:
> > > +#
> > > +# Send a break to a character device
> > 
> > ...with this wording.  I like 'send a break' better than 'send break',
> > but even better might be 'send a break sequence' or even 'emulate a
> > break sequence' (by definition, a break is NOT a character, but on bare
> > metal character devices it IS a defined electrical sequence distinct
> > from characters to make the recipient aware that the sender is trying to
> > get attention).
> > 
> > Otherwise, the patch looks fine to me.  If all that changes is some
> > word-smithing (and the maintainer may be willing to do that), you can add:
> > Reviewed-by: Eric Blake <eblake@redhat.com>
> 
> I'll go with the 'send a break' - the official terminology seems to
> be a 'break condition', but I've never heard anyone say that,
> it's always been 'send a break'.

I also think that "send a break" is best for people who google for it.

Thanks.

Cheers,
Stefan

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Qemu-devel] [PATCH v2] Add chardev-send-break monitor command
  2017-06-11  7:48 [Qemu-devel] [PATCH v2] Add chardev-send-break monitor command Stefan Fritsch
  2017-06-27 19:40 ` Eric Blake
@ 2017-07-19 15:01 ` Thomas Huth
  2017-07-19 15:14   ` Stefan Fritsch
  1 sibling, 1 reply; 8+ messages in thread
From: Thomas Huth @ 2017-07-19 15:01 UTC (permalink / raw)
  To: Stefan Fritsch, qemu-devel
  Cc: Markus Armbruster, Dr. David Alan Gilbert,
	Marc-André Lureau, Paolo Bonzini

 Hi,

On 11.06.2017 09:48, 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>
> Acked-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> v2: added tests and Acked-by line
[...]
> diff --git a/tests/test-hmp.c b/tests/test-hmp.c
> index 99e35ec15a..6dfa0c36e2 100644
> --- a/tests/test-hmp.c
> +++ b/tests/test-hmp.c
> @@ -22,6 +22,7 @@ static int verbose;
>  static const char *hmp_cmds[] = {
>      "boot_set ndc",
>      "chardev-add null,id=testchardev1",
> +    "chardev-send-break testchardev2",
>      "chardev-remove testchardev1",
>      "commit all",
>      "cpu-add 1",

Did you use "testchardev2" here on purpose, or should that have been a
"testchardev1" instead? "testchardev2" is not a valid identifier in the
HMP test, so this might not exercise the code path that you might have
intended?

 Thomas

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Qemu-devel] [PATCH v2] Add chardev-send-break monitor command
  2017-07-19 15:01 ` Thomas Huth
@ 2017-07-19 15:14   ` Stefan Fritsch
  0 siblings, 0 replies; 8+ messages in thread
From: Stefan Fritsch @ 2017-07-19 15:14 UTC (permalink / raw)
  To: Thomas Huth
  Cc: qemu-devel, Marc-André Lureau, Paolo Bonzini,
	Markus Armbruster, Dr. David Alan Gilbert

On Wed, 19 Jul 2017, Thomas Huth wrote:
> On 11.06.2017 09:48, 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>
> > Acked-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> > ---
> > v2: added tests and Acked-by line
> [...]
> > diff --git a/tests/test-hmp.c b/tests/test-hmp.c
> > index 99e35ec15a..6dfa0c36e2 100644
> > --- a/tests/test-hmp.c
> > +++ b/tests/test-hmp.c
> > @@ -22,6 +22,7 @@ static int verbose;
> >  static const char *hmp_cmds[] = {
> >      "boot_set ndc",
> >      "chardev-add null,id=testchardev1",
> > +    "chardev-send-break testchardev2",
> >      "chardev-remove testchardev1",
> >      "commit all",
> >      "cpu-add 1",
> 
> Did you use "testchardev2" here on purpose, or should that have been a
> "testchardev1" instead? "testchardev2" is not a valid identifier in the
> HMP test, so this might not exercise the code path that you might have
> intended?

You are right, this should have been "testchardev1". Actually, one could 
do both, which would then exercise two different code paths.

Cheers,
Stefan

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2017-07-19 15:14 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-11  7:48 [Qemu-devel] [PATCH v2] Add chardev-send-break monitor command Stefan Fritsch
2017-06-27 19:40 ` Eric Blake
2017-06-29 14:27   ` Marc-André Lureau
2017-06-29 14:41     ` Dr. David Alan Gilbert
2017-06-29 15:00   ` Dr. David Alan Gilbert
2017-06-30 15:53     ` Stefan Fritsch
2017-07-19 15:01 ` Thomas Huth
2017-07-19 15:14   ` Stefan Fritsch

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.