From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: pbonzini@redhat.com, lersek@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/3] Add 'namethreads' suboption to --name
Date: Tue, 28 Jan 2014 17:53:52 +0200 [thread overview]
Message-ID: <20140128155352.GA19526@redhat.com> (raw)
In-Reply-To: <1390922439-30750-3-git-send-email-dgilbert@redhat.com>
On Tue, Jan 28, 2014 at 03:20:38PM +0000, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> Add flag storage to qemu-thread-* to store the namethreads flag
>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
How about a pattern? threads='vmfoo-%s' and have qemu fill in
specific strings for %s.
> ---
> include/qemu/thread.h | 1 +
> qemu-options.hx | 6 ++++--
> util/qemu-thread-posix.c | 7 +++++++
> util/qemu-thread-win32.c | 8 ++++++++
> vl.c | 7 +++++++
> 5 files changed, 27 insertions(+), 2 deletions(-)
>
> diff --git a/include/qemu/thread.h b/include/qemu/thread.h
> index 3e32c65..bf1e110 100644
> --- a/include/qemu/thread.h
> +++ b/include/qemu/thread.h
> @@ -59,5 +59,6 @@ void *qemu_thread_join(QemuThread *thread);
> void qemu_thread_get_self(QemuThread *thread);
> bool qemu_thread_is_self(QemuThread *thread);
> void qemu_thread_exit(void *retval);
> +void qemu_thread_naming(bool enable);
>
> #endif
> diff --git a/qemu-options.hx b/qemu-options.hx
> index 56e5fdf..d53343a 100644
> --- a/qemu-options.hx
> +++ b/qemu-options.hx
> @@ -328,9 +328,10 @@ possible drivers and properties, use @code{-device help} and
> ETEXI
>
> DEF("name", HAS_ARG, QEMU_OPTION_name,
> - "-name string1[,process=string2]\n"
> + "-name string1[,process=string2][,namethreads=on|off]\n"
> " set the name of the guest\n"
> - " string1 sets the window title and string2 the process name (on Linux)\n",
> + " string1 sets the window title and string2 the process name (on Linux)\n"
> + " When namethreads is enabled, individual threads are given a separate name (on Linux)\n",
> QEMU_ARCH_ALL)
> STEXI
> @item -name @var{name}
> @@ -339,6 +340,7 @@ Sets the @var{name} of the guest.
> This name will be displayed in the SDL window caption.
> The @var{name} will also be used for the VNC server.
> Also optionally set the top visible process name in Linux.
> +Naming of individual threads can also be enabled on Linux.
> ETEXI
>
> DEF("uuid", HAS_ARG, QEMU_OPTION_uuid,
> diff --git a/util/qemu-thread-posix.c b/util/qemu-thread-posix.c
> index 37dd298..0fa6c81 100644
> --- a/util/qemu-thread-posix.c
> +++ b/util/qemu-thread-posix.c
> @@ -27,6 +27,13 @@
> #include "qemu/thread.h"
> #include "qemu/atomic.h"
>
> +static bool name_threads;
> +
> +void qemu_thread_naming(bool enable)
> +{
> + name_threads = enable;
> +}
> +
> static void error_exit(int err, const char *msg)
> {
> fprintf(stderr, "qemu: %s: %s\n", msg, strerror(err));
> diff --git a/util/qemu-thread-win32.c b/util/qemu-thread-win32.c
> index 27a5217..e42cb77 100644
> --- a/util/qemu-thread-win32.c
> +++ b/util/qemu-thread-win32.c
> @@ -16,6 +16,14 @@
> #include <assert.h>
> #include <limits.h>
>
> +static bool name_threads;
> +
> +void qemu_thread_naming(bool enable)
> +{
> + /* But note we don't actually name them on Windows yet */
> + name_threads = enable;
> +}
> +
> static void error_exit(int err, const char *msg)
> {
> char *pstr;
> diff --git a/vl.c b/vl.c
> index 5f993e4..8c515ae 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -547,6 +547,10 @@ static QemuOptsList qemu_name_opts = {
> .name = "process",
> .type = QEMU_OPT_STRING,
> .help = "Sets the name of the QEMU process, as shown in top etc",
> + }, {
> + .name = "namethreads",
> + .type = QEMU_OPT_BOOL,
> + .help = "When enabled, name the individual threads; defaults off",
> },
> { /* End of list */ }
> },
> @@ -1006,6 +1010,9 @@ static void parse_name(QemuOpts *opts)
> {
> const char *proc_name;
>
> + if (qemu_opt_get(opts, "namethreads")) {
> + qemu_thread_naming(qemu_opt_get_bool(opts, "namethreads", false));
> + }
> qemu_name = qemu_opt_get(opts, "guest");
>
> proc_name = qemu_opt_get(opts, "process");
> --
> 1.8.5.3
next prev parent reply other threads:[~2014-01-28 17:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 15:20 [Qemu-devel] [PATCH 0/3] Name threads Dr. David Alan Gilbert (git)
2014-01-28 15:20 ` [Qemu-devel] [PATCH 1/3] Rework --name to use QemuOpts Dr. David Alan Gilbert (git)
2014-01-29 8:49 ` Alex Bennée
2014-01-28 15:20 ` [Qemu-devel] [PATCH 2/3] Add 'namethreads' suboption to --name Dr. David Alan Gilbert (git)
2014-01-28 15:53 ` Michael S. Tsirkin [this message]
2014-01-28 18:09 ` Dr. David Alan Gilbert
2014-01-28 19:01 ` Michael S. Tsirkin
2014-01-28 15:20 ` [Qemu-devel] [PATCH 3/3] Add a 'name' parameter to qemu_thread_create Dr. David Alan Gilbert (git)
2014-01-28 15:56 ` Michael S. Tsirkin
2014-01-28 16:12 ` Dr. David Alan Gilbert
2014-01-28 16:21 ` Laszlo Ersek
2014-01-28 16:44 ` Michael S. Tsirkin
2014-01-28 15:41 ` [Qemu-devel] [PATCH 0/3] Name threads Paolo Bonzini
2014-01-28 16:31 ` Dr. David Alan Gilbert
2014-01-28 16:33 ` Paolo Bonzini
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=20140128155352.GA19526@redhat.com \
--to=mst@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.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 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).