From: Yi Wang <wang.yi59@zte.com.cn>
To: dgilbert@redhat.com, armbru@redhat.com, pbonzini@redhat.com,
rth@twiddle.net, ehabkost@redhat.com, imammedo@redhat.com,
qemu-devel@nongnu.org
Cc: wang.yi59@zte.com.cn, Liu.Jianjun3@zte.com.cn, liu.yunh@zte.com.cn
Subject: [Qemu-devel] [PATCH v2 0/2] hmp: support querying lapic through apic-id for 'info lapic'
Date: Wed, 26 Jul 2017 02:18:35 -0400 [thread overview]
Message-ID: <1501049917-4701-1-git-send-email-wang.yi59@zte.com.cn> (raw)
This series add support querying local apic through apic-id for 'info
lapic'.
As cpu_index will not be used afterwards, so extend 'info registers'
firstly to get apic-id through monitor commands.
v1 -> v2:
* PATCH 01: Make the code simpler [Igor]
* PATCH 02: use cpu_by_arch_id() to obtain CPU [Eduardo]
Yi Wang (2):
hmp: dump ids including socket-id, core-id and so on for 'info registers'
hmp: allow apic-id for "info lapic"
hmp-commands-info.hx | 7 ++++---
include/qom/cpu.h | 10 ++++++++++
qom/cpu.c | 11 ++++++++---
target/i386/helper.c | 8 ++++++++
target/i386/monitor.c | 10 +++++++++-
5 files changed, 39 insertions(+), 7 deletions(-)
next reply other threads:[~2017-07-26 6:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 6:18 Yi Wang [this message]
2017-07-26 6:18 ` [Qemu-devel] [PATCH v2 0/2] hmp: support querying lapic through apic-id for 'info lapic' no-reply
2017-07-26 6:18 ` [Qemu-devel] [PATCH v2 1/2] hmp: dump ids including socket-id, core-id and so on for 'info registers' Yi Wang
2017-07-26 14:01 ` Eduardo Habkost
2017-07-26 14:27 ` Igor Mammedov
2017-07-26 17:50 ` Eduardo Habkost
2017-07-27 15:12 ` Igor Mammedov
2017-07-27 16:46 ` Eduardo Habkost
2017-07-26 14:29 ` Igor Mammedov
2017-07-26 6:18 ` [Qemu-devel] [PATCH v2 2/2] hmp: allow apic-id for "info lapic" Yi Wang
2017-07-26 17:36 ` Eduardo Habkost
2017-07-26 18:53 ` [Qemu-devel] [PATCH] cpu: cpu_by_arch_id() helper Eduardo Habkost
2017-07-26 18:53 ` [Qemu-devel] [PATCH v2 2/2] hmp: allow apic-id for "info lapic" Eduardo Habkost
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=1501049917-4701-1-git-send-email-wang.yi59@zte.com.cn \
--to=wang.yi59@zte.com.cn \
--cc=Liu.Jianjun3@zte.com.cn \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=liu.yunh@zte.com.cn \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).