From: Anju T Sudhakar <anju@linux.vnet.ibm.com>
To: mpe@ellerman.id.au, acme@kernel.org, jolsa@redhat.com
Cc: ravi.bangoria@linux.ibm.com, maddy@linux.vnet.ibm.com,
peterz@infradead.org, linux-kernel@vger.kernel.org,
alexander.shishkin@linux.intel.com, anju@linux.vnet.ibm.com,
namhyung@kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: [PATCH v2 1/3] tools/perf: Move kvm-stat header file from conditional inclusion to common include section
Date: Thu, 18 Jul 2019 23:47:47 +0530 [thread overview]
Message-ID: <20190718181749.30612-1-anju@linux.vnet.ibm.com> (raw)
Move kvm-stat header file to the common include section, and make the
definitions in the header file under the conditional inclusion
`#ifdef HAVE_KVM_STAT_SUPPORT`.
This helps to define other perf kvm related function prototypes in
kvm-stat header file, which may not need kvm-stat support.
Signed-off-by: Anju T Sudhakar <anju@linux.vnet.ibm.com>
---
tools/perf/builtin-kvm.c | 2 +-
tools/perf/util/kvm-stat.h | 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/tools/perf/builtin-kvm.c b/tools/perf/builtin-kvm.c
index b33c83489120..5d2b34d290a3 100644
--- a/tools/perf/builtin-kvm.c
+++ b/tools/perf/builtin-kvm.c
@@ -19,6 +19,7 @@
#include "util/top.h"
#include "util/data.h"
#include "util/ordered-events.h"
+#include "util/kvm-stat.h"
#include <sys/prctl.h>
#ifdef HAVE_TIMERFD_SUPPORT
@@ -55,7 +56,6 @@ static const char *get_filename_for_perf_kvm(void)
}
#ifdef HAVE_KVM_STAT_SUPPORT
-#include "util/kvm-stat.h"
void exit_event_get_key(struct perf_evsel *evsel,
struct perf_sample *sample,
diff --git a/tools/perf/util/kvm-stat.h b/tools/perf/util/kvm-stat.h
index 1403dec189b4..b3b2670e1a2b 100644
--- a/tools/perf/util/kvm-stat.h
+++ b/tools/perf/util/kvm-stat.h
@@ -2,6 +2,8 @@
#ifndef __PERF_KVM_STAT_H
#define __PERF_KVM_STAT_H
+#ifdef HAVE_KVM_STAT_SUPPORT
+
#include "../perf.h"
#include "tool.h"
#include "stat.h"
@@ -144,5 +146,6 @@ extern const int decode_str_len;
extern const char *kvm_exit_reason;
extern const char *kvm_entry_trace;
extern const char *kvm_exit_trace;
+#endif /* HAVE_KVM_STAT_SUPPORT */
#endif /* __PERF_KVM_STAT_H */
--
2.20.1
next reply other threads:[~2019-07-18 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 18:17 Anju T Sudhakar [this message]
2019-07-18 18:17 ` [PATCH v2 2/3] tools/perf: Add arch neutral function to choose event for perf kvm record Anju T Sudhakar
2019-09-20 16:20 ` [tip: perf/urgent] perf kvm: " tip-bot2 for Anju T Sudhakar
2019-07-18 18:17 ` [PATCH v2 3/3] tools/perf: Set 'trace_cycles' as defaultevent for perf kvm record in powerpc Anju T Sudhakar
2019-09-20 16:20 ` [tip: perf/urgent] perf kvm stat: Set 'trace_cycles' as default event for 'perf kvm record' " tip-bot2 for Anju T Sudhakar
2019-07-19 5:28 ` [PATCH v2 1/3] tools/perf: Move kvm-stat header file from conditional inclusion to common include section Ravi Bangoria
2019-09-19 0:05 ` Arnaldo Carvalho de Melo
2019-09-20 16:20 ` [tip: perf/urgent] perf kvm: " tip-bot2 for Anju T Sudhakar
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=20190718181749.30612-1-anju@linux.vnet.ibm.com \
--to=anju@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.ibm.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 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).