From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: will.deacon@arm.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robh@kernel.org,
mathieu.poirier@linaro.org, leo.yan@linaro.org,
peterz@infradead.org, mark.rutland@arm.com,
frowand.list@gmail.com, marc.zyngier@arm.com,
jonathan.cameron@huawei.com, sudeep.holla@arm.com,
Suzuki K Poulose <suzuki.poulose@arm.com>
Subject: [PATCH v11 1/8] perf: Export perf_event_update_userpage
Date: Tue, 2 Jan 2018 11:25:26 +0000 [thread overview]
Message-ID: <20180102112533.13640-2-suzuki.poulose@arm.com> (raw)
In-Reply-To: <20180102112533.13640-1-suzuki.poulose@arm.com>
Export perf_event_update_userpage() so that PMU driver using them,
can be built as modules.
Acked-by: Peter Zilstra <peterz@infradead.org>
Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
---
kernel/events/core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index 4df5b695bf0d..64ec2c9d2c44 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -4904,6 +4904,7 @@ void perf_event_update_userpage(struct perf_event *event)
unlock:
rcu_read_unlock();
}
+EXPORT_SYMBOL_GPL(perf_event_update_userpage);
static int perf_mmap_fault(struct vm_fault *vmf)
{
--
2.13.6
next prev parent reply other threads:[~2018-01-02 11:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 11:25 [PATCH v11 0/8] perf: Support for ARM DynamIQ Shared Unit Suzuki K Poulose
2018-01-02 11:25 ` Suzuki K Poulose [this message]
2018-01-02 11:25 ` [PATCH v11 2/8] of: Add helper for mapping device node to logical CPU number Suzuki K Poulose
2018-01-02 11:25 ` [PATCH v11 3/8] coresight: of: Use of_cpu_node_to_id helper Suzuki K Poulose
2018-01-02 11:25 ` [PATCH v11 4/8] irqchip: gic-v3: " Suzuki K Poulose
2018-01-02 11:25 ` [PATCH v11 5/8] arm64: Use of_cpu_node_to_id helper for CPU topology parsing Suzuki K Poulose
2018-01-02 11:25 ` [PATCH v11 6/8] arm_pmu: Use of_cpu_node_to_id helper Suzuki K Poulose
2018-01-02 11:25 ` [PATCH v11 7/8] dt-bindings: Document devicetree binding for ARM DSU PMU Suzuki K Poulose
2018-01-02 11:25 ` [PATCH v11 8/8] perf: ARM DynamIQ Shared Unit PMU support Suzuki K Poulose
2018-02-22 2:32 ` Saravana Kannan
2018-02-22 11:33 ` Mark Rutland
2018-02-22 20:38 ` Saravana Kannan
2018-02-23 11:35 ` Mark Rutland
2018-02-23 21:46 ` Saravana Kannan
2018-02-24 0:53 ` Saravana Kannan
2018-02-25 14:36 ` Mark Rutland
2018-02-28 22:17 ` Saravana Kannan
2018-03-01 11:49 ` Mark Rutland
2018-03-01 20:35 ` Saravana Kannan
2018-03-02 10:42 ` Mark Rutland
2018-03-02 19:19 ` Saravana Kannan
2018-03-05 10:59 ` Mark Rutland
2018-03-05 22:10 ` Saravana Kannan
2018-03-07 14:59 ` Suzuki K Poulose
2018-03-07 21:36 ` Saravana Kannan
2018-03-19 9:50 ` Suzuki K Poulose
2018-03-08 11:42 ` Mark Rutland
2018-03-08 23:59 ` Saravana Kannan
2018-03-09 10:53 ` Suzuki K Poulose
2018-03-09 13:35 ` Mark Rutland
2018-03-09 22:49 ` Saravana Kannan
2018-03-10 15:45 ` Mark Rutland
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=20180102112533.13640-2-suzuki.poulose@arm.com \
--to=suzuki.poulose@arm.com \
--cc=frowand.list@gmail.com \
--cc=jonathan.cameron@huawei.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®