From: tip-bot for David Miller <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: tglx@linutronix.de, acme@redhat.com, hpa@zytor.com,
davem@davemloft.net, mingo@kernel.org, jolsa@kernel.org,
kan.liang@intel.com, linux-kernel@vger.kernel.org
Subject: [tip:perf/urgent] perf cpu_map: Align cpu map synthesized events properly.
Date: Wed, 17 Oct 2018 23:19:39 -0700 [thread overview]
Message-ID: <tip-0ed149cf5239cc6e7e65bf00f769e8f1e91076c0@git.kernel.org> (raw)
In-Reply-To: <20181011.224655.716771175766946817.davem@davemloft.net>
Commit-ID: 0ed149cf5239cc6e7e65bf00f769e8f1e91076c0
Gitweb: https://git.kernel.org/tip/0ed149cf5239cc6e7e65bf00f769e8f1e91076c0
Author: David Miller <davem@davemloft.net>
AuthorDate: Thu, 11 Oct 2018 22:46:55 -0700
Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Tue, 16 Oct 2018 12:30:03 -0300
perf cpu_map: Align cpu map synthesized events properly.
The size of the resulting cpu map can be smaller than a multiple of
sizeof(u64), resulting in SIGBUS on cpus like Sparc as the next event
will not be aligned properly.
Signed-off-by: David S. Miller <davem@davemloft.net>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Kan Liang <kan.liang@intel.com>
Fixes: 6c872901af07 ("perf cpu_map: Add cpu_map event synthesize function")
Link: http://lkml.kernel.org/r/20181011.224655.716771175766946817.davem@davemloft.net
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/perf/util/event.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/perf/util/event.c b/tools/perf/util/event.c
index 0cd42150f712..0988eb3b844b 100644
--- a/tools/perf/util/event.c
+++ b/tools/perf/util/event.c
@@ -1081,6 +1081,7 @@ void *cpu_map_data__alloc(struct cpu_map *map, size_t *size, u16 *type, int *max
}
*size += sizeof(struct cpu_map_data);
+ *size = PERF_ALIGN(*size, sizeof(u64));
return zalloc(*size);
}
prev parent reply other threads:[~2018-10-18 6:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 5:46 [PATCH] perf: Align cpu map events properly David Miller
2018-10-16 15:29 ` Arnaldo Carvalho de Melo
2018-10-18 6:19 ` tip-bot for David Miller [this message]
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=tip-0ed149cf5239cc6e7e65bf00f769e8f1e91076c0@git.kernel.org \
--to=tipbot@zytor.com \
--cc=acme@redhat.com \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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