From: "Lluís Vilanova" <vilanova@ac.upc.edu>
To: "Emilio G. Cota" <cota@braap.org>
Cc: qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v8 2/7] cpu: allocate cpu->trace_dstate in place
Date: Sun, 25 Jun 2017 12:41:57 +0300 [thread overview]
Message-ID: <87zicwieu2.fsf@frigg.lan> (raw)
In-Reply-To: <87poeaog5b.fsf@frigg.lan> ("Lluís Vilanova"'s message of "Sun, 11 Jun 2017 15:36:16 +0300")
Lluís Vilanova writes:
> Emilio G Cota writes:
>> There's little point in dynamically allocating the bitmap if we
>> know at compile-time the max number of events we want to support.
>> Thus, make room in the struct for the bitmap, which will make things
>> easier later: this paves the way for upcoming changes, in which
>> we'll use a u32 to fully capture cpu->trace_dstate.
>> This change also increases performance by saving a dereference and
>> improving locality--note that this is important since upcoming work
>> makes reading this bitmap fairly common.
>> Signed-off-by: Emilio G. Cota <cota@braap.org>
> Reviewed-by: Lluís Vilanova <vilanova@ac.upc.edu>
BTW, I think this partially undoes Daniel's changes in
b7d48952c375842bd669460fd8384d90cc12286c.
You should check with him (CC'ed).
Lluis
>> ---
>> include/qom/cpu.h | 9 +++------
>> qom/cpu.c | 8 --------
>> trace/control.c | 9 ++++++++-
>> 3 files changed, 11 insertions(+), 15 deletions(-)
>> diff --git a/include/qom/cpu.h b/include/qom/cpu.h
>> index 89ddb68..bc6e20f 100644
>> --- a/include/qom/cpu.h
>> +++ b/include/qom/cpu.h
>> @@ -259,6 +259,7 @@ typedef void (*run_on_cpu_func)(CPUState *cpu, run_on_cpu_data data);
>> struct qemu_work_item;
>> #define CPU_UNSET_NUMA_NODE_ID -1
>> +#define CPU_TRACE_DSTATE_MAX_EVENTS 32
>> /**
>> * CPUState:
>> @@ -373,12 +374,8 @@ struct CPUState {
>> struct KVMState *kvm_state;
>> struct kvm_run *kvm_run;
>> - /*
>> - * Used for events with 'vcpu' and *without* the 'disabled' properties.
>> - * Dynamically allocated based on bitmap requried to hold up to
>> - * trace_get_vcpu_event_count() entries.
>> - */
>> - unsigned long *trace_dstate;
>> + /* Used for events with 'vcpu' and *without* the 'disabled' properties */
>> + DECLARE_BITMAP(trace_dstate, CPU_TRACE_DSTATE_MAX_EVENTS);
>> /* TODO Move common fields from CPUArchState here. */
>> int cpu_index; /* used by alpha TCG */
>> diff --git a/qom/cpu.c b/qom/cpu.c
>> index 5069876..69fbb9c 100644
>> --- a/qom/cpu.c
>> +++ b/qom/cpu.c
>> @@ -382,7 +382,6 @@ static void cpu_common_unrealizefn(DeviceState *dev, Error **errp)
>> static void cpu_common_initfn(Object *obj)
>> {
>> - uint32_t count;
>> CPUState *cpu = CPU(obj);
>> CPUClass *cc = CPU_GET_CLASS(obj);
>> @@ -397,18 +396,11 @@ static void cpu_common_initfn(Object *obj)
>> QTAILQ_INIT(&cpu->breakpoints);
>> QTAILQ_INIT(&cpu->watchpoints);
>> - count = trace_get_vcpu_event_count();
>> - if (count) {
>> - cpu->trace_dstate = bitmap_new(count);
>> - }
>> -
>> cpu_exec_initfn(cpu);
>> }
>> static void cpu_common_finalize(Object *obj)
>> {
>> - CPUState *cpu = CPU(obj);
>> - g_free(cpu->trace_dstate);
>> }
>> static int64_t cpu_common_get_arch_id(CPUState *cpu)
>> diff --git a/trace/control.c b/trace/control.c
>> index 9b157b0..83740aa 100644
>> --- a/trace/control.c
>> +++ b/trace/control.c
>> @@ -65,8 +65,15 @@ void trace_event_register_group(TraceEvent **events)
>> size_t i;
>> for (i = 0; events[i] != NULL; i++) {
>> events[i]->id = next_id++;
>> - if (events[i]->vcpu_id != TRACE_VCPU_EVENT_NONE) {
>> + if (events[i]->vcpu_id == TRACE_VCPU_EVENT_NONE) {
>> + continue;
>> + }
>> +
>> + if (likely(next_vcpu_id < CPU_TRACE_DSTATE_MAX_EVENTS)) {
>> events[i]->vcpu_id = next_vcpu_id++;
>> + } else {
>> + error_report("WARNING: too many vcpu trace events; dropping '%s'",
>> + events[i]->name);
>> }
>> }
>> event_groups = g_renew(TraceEventGroup, event_groups, nevent_groups + 1);
>> --
>> 2.7.4
next prev parent reply other threads:[~2017-06-25 9:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 2:25 [Qemu-devel] [PATCH v8 0/7] trace: [tcg] Optimize per-vCPU tracing states Emilio G. Cota
2017-06-09 2:25 ` [Qemu-devel] [PATCH v8 1/7] exec: [tcg] Refactor flush of per-CPU virtual TB cache Emilio G. Cota
2017-06-09 2:25 ` [Qemu-devel] [PATCH v8 2/7] cpu: allocate cpu->trace_dstate in place Emilio G. Cota
2017-06-11 12:36 ` Lluís Vilanova
2017-06-25 9:41 ` Lluís Vilanova [this message]
2017-06-26 8:26 ` Daniel P. Berrange
2017-06-09 2:25 ` [Qemu-devel] [PATCH v8 3/7] trace: [tcg] Delay changes to dynamic state when translating Emilio G. Cota
2017-06-09 2:25 ` [Qemu-devel] [PATCH v8 4/7] exec: [tcg] Use different TBs according to the vCPU's dynamic tracing state Emilio G. Cota
2017-06-09 2:25 ` [Qemu-devel] [PATCH v8 5/7] trace: [tcg] Do not generate TCG code to trace dinamically-disabled events Emilio G. Cota
2017-06-09 2:25 ` [Qemu-devel] [PATCH v8 6/7] trace: [tcg, trivial] Re-align generated code Emilio G. Cota
2017-06-09 2:25 ` [Qemu-devel] [PATCH v8 7/7] trace: [trivial] Statically enable all guest events Emilio G. Cota
2017-06-26 8:28 ` Daniel P. Berrange
2017-06-26 9:18 ` Lluís Vilanova
2017-06-26 9:26 ` Daniel P. Berrange
2017-06-26 9:32 ` Laurent Desnogues
2017-06-26 16:22 ` Lluís Vilanova
2017-06-26 16:26 ` Daniel P. Berrange
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=87zicwieu2.fsf@frigg.lan \
--to=vilanova@ac.upc.edu \
--cc=berrange@redhat.com \
--cc=cota@braap.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.com \
/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.