[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140825143256.GB11024@potion.brq.redhat.com>
Date: Mon, 25 Aug 2014 16:32:57 +0200
From: Radim Krčmář <rkrcmar@...hat.com>
To: Sabrina Dubroca <sd@...asysnail.net>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
Paolo Bonzini <pbonzini@...hat.com>,
Gleb Natapov <gleb@...nel.org>,
Raghavendra KT <raghavendra.kt@...ux.vnet.ibm.com>,
Vinod Chegu <chegu_vinod@...com>,
Hui-Zhi Zhao <hui-zhi.zhao@...com>,
Christian Borntraeger <borntraeger@...ibm.com>,
Lisa Mitchell <lisa.mitchell@...com>
Subject: Re: [PATCH v3 5/7] KVM: trace kvm_ple_window grow/shrink
2014-08-25 15:53+0200, Sabrina Dubroca:
> Hello,
>
> 2014-08-21, 18:08:09 +0200, Radim Krčmář wrote:
> > Tracepoint for dynamic PLE window, fired on every potential change.
> > +#define trace_kvm_ple_window_grow(vcpu_id, new, old) \
> > + trace_kvm_ple_window(true, vcpu_id, new, old)
> > +#define trace_kvm_ple_window_shrink(vcpu_id, new, old) \
> > + trace_kvm_ple_window(false, vcpu_id, new, old)
> > +
> > #endif /* CONFIG_X86_64 */
>
> Looks like these are needed on 32-bit as well.
> Today's linux-next doesn't build:
>
> [...]
>
> I moved the line
>
> #endif /* CONFIG_X86_64 */
>
> above
>
> TRACE_EVENT(kvm_ple_window,
>
> and it builds.
Thanks!
Paolo, can you still fix this "just" by rebasing?
---
diff --git a/arch/x86/kvm/trace.h b/arch/x86/kvm/trace.h
index 1742dfb..4c2868f 100644
--- a/arch/x86/kvm/trace.h
+++ b/arch/x86/kvm/trace.h
@@ -848,6 +848,8 @@ TRACE_EVENT(kvm_track_tsc,
__print_symbolic(__entry->host_clock, host_clocks))
);
+#endif /* CONFIG_X86_64 */
+
TRACE_EVENT(kvm_ple_window,
TP_PROTO(bool grow, unsigned int vcpu_id, int new, int old),
TP_ARGS(grow, vcpu_id, new, old),
@@ -878,8 +880,6 @@ TRACE_EVENT(kvm_ple_window,
#define trace_kvm_ple_window_shrink(vcpu_id, new, old) \
trace_kvm_ple_window(false, vcpu_id, new, old)
-#endif /* CONFIG_X86_64 */
-
#endif /* _TRACE_KVM_H */
#undef TRACE_INCLUDE_PATH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists