From: <wang.yi59@zte.com.cn>
To: imammedo@redhat.com, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, rth@twiddle.net, ehabkost@redhat.com,
dgilbert@redhat.com, liu.yunh@zte.com.cn,
Liu.Jianjun3@zte.com.cn
Subject: Re: [Qemu-devel] [PATCH v2] hmp: allow cpu index for "info lapic"
Date: Wed, 19 Jul 2017 12:25:53 +0800 (CST) [thread overview]
Message-ID: <201707191225539935494@zte.com.cn> (raw)
>On Mon, 17 Jul 2017 21:49:37 -0400
>Yi Wang <address@hidden> wrote:
>
>> Add [vcpu] index support for hmp command "info lapic", which is
>> useful when debugging ipi and so on. Current behavior is not
>> changed when the parameter isn't specified.
>we shouldn't expose cpu_index to users anymore,
>
>I would suggest using to use real APIC ID here but we don't
>have monitor command that returns APIC IDs for present cpus.
Would you like to explain the reason we shouldn't use cpu_index any
more, which is more straightforward than socket-id/core-id/thread-id?
As Eduardo wrote in the next reply, "CPU #<n>" is already a perfectly
good identifier for a human interface :-)
Many thanks.
---
Best wishes
Yi Wang
next reply other threads:[~2017-07-19 4:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 4:25 wang.yi59 [this message]
2017-07-19 7:36 ` [Qemu-devel] [PATCH v2] hmp: allow cpu index for "info lapic" Igor Mammedov
-- strict thread matches above, loose matches on Subject: below --
2017-07-20 4:41 wang.yi59
2017-07-19 8:48 wang.yi59
2017-07-19 9:16 ` Igor Mammedov
2017-07-19 4:47 wang.yi59
2017-07-19 6:16 ` Eduardo Habkost
2017-07-19 12:16 ` Dr. David Alan Gilbert
2017-07-19 12:41 ` Eduardo Habkost
2017-07-19 15:02 ` Eric Blake
2017-07-19 15:07 ` Daniel P. Berrange
2017-07-19 15:17 ` Eric Blake
2017-07-19 18:32 ` Eduardo Habkost
2017-07-19 19:17 ` Dr. David Alan Gilbert
2017-07-19 19:46 ` Eduardo Habkost
2017-07-19 8:10 ` Dr. David Alan Gilbert
2017-07-18 1:49 Yi Wang
2017-07-18 14:54 ` Igor Mammedov
2017-07-18 23:26 ` Eduardo Habkost
2017-07-19 7:39 ` Igor Mammedov
2017-07-18 23:25 ` 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=201707191225539935494@zte.com.cn \
--to=wang.yi59@zte.com.cn \
--cc=Liu.Jianjun3@zte.com.cn \
--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 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.