From: Glauber Costa <gcosta@redhat.com>
To: kvm-devel@lists.sourceforge.net
Cc: glommer@gmail.com, qemu-devel@nongnu.org,
Glauber Costa <gcosta@redhat.com>,
chrisw@sous-sol.org
Subject: [Qemu-devel] [PATCH] augment info cpus
Date: Wed, 5 Mar 2008 17:01:10 -0300 [thread overview]
Message-ID: <12047472823266-git-send-email-gcosta@redhat.com> (raw)
In-Reply-To: <12047472772114-git-send-email-gcosta@redhat.com>
This patch exposes the thread id associated with each
cpu through the already well known info cpus interface.
Signed-off-by: Glauber Costa <gcosta@redhat.com>
---
qemu/monitor.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/qemu/monitor.c b/qemu/monitor.c
index 0874671..4ee0b19 100644
--- a/qemu/monitor.c
+++ b/qemu/monitor.c
@@ -335,6 +335,7 @@ static void do_info_cpus(void)
if (env->halted)
term_printf(" (halted)");
#endif
+ term_printf(" thread_id=%d", env->thread_id);
term_printf("\n");
}
}
--
1.5.0.6
next prev parent reply other threads:[~2008-03-05 20:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 20:01 [Qemu-devel] [PATCH 0/3] Expose thread id through info cpus Glauber Costa
2008-03-05 20:01 ` [Qemu-devel] [PATCH] use a thread id variable Glauber Costa
2008-03-05 20:01 ` Glauber Costa [this message]
2008-03-05 20:01 ` [Qemu-devel] [PATCH] KVM: use actual thread id for vcpus Glauber Costa
2008-03-09 9:26 ` [Qemu-devel] [PATCH] use a thread id variable Gilad Ben-Yossef
2008-03-09 11:58 ` Jamie Lokier
2008-03-09 14:52 ` Gilad Ben-Yossef
2008-03-09 16:12 ` M. Warner Losh
2008-03-17 17:55 ` Glauber Costa
2008-03-09 16:09 ` M. Warner Losh
2008-03-09 20:01 ` Jamie Lokier
2008-03-09 16:23 ` [kvm-devel] " Daniel P. Berrange
2008-03-05 20:07 ` [Qemu-devel] Re: [PATCH 0/3] Expose thread id through info cpus Glauber Costa
2008-03-06 6:55 ` Avi Kivity
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=12047472823266-git-send-email-gcosta@redhat.com \
--to=gcosta@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=glommer@gmail.com \
--cc=kvm-devel@lists.sourceforge.net \
--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).