From: Shuai Xue <xueshuai@linux.alibaba.com>
To: alexander.shishkin@linux.intel.com, peterz@infradead.org
Cc: mingo@redhat.com, acme@kernel.org, mark.rutland@arm.com,
jolsa@kernel.org, namhyung@kernel.org, irogers@google.com,
adrian.hunter@intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: [PATCH 0/2] Fix high-order allocations for AUX space
Date: Mon, 12 Jun 2023 13:24:50 +0800 [thread overview]
Message-ID: <20230612052452.53425-1-xueshuai@linux.alibaba.com> (raw)
When perf-record with large AUX area, it reveals WARNINGs with __alloc_pages.
Fix with correct MAX_ORDER limit to request higher order allocations so that
larger contiguous areas is allocated.
Shuai Xue (2):
perf/core: Bail out early if the request AUX area is out of bound
perf/ring_buffer: Fix high-order allocations for AUX space with
correct MAX_ORDER limit
kernel/events/core.c | 10 ++++++++++
kernel/events/ring_buffer.c | 4 ++--
tools/perf/Documentation/perf-record.txt | 3 ++-
3 files changed, 14 insertions(+), 3 deletions(-)
--
1.8.3.1
next reply other threads:[~2023-06-12 5:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 5:24 Shuai Xue [this message]
2023-06-12 5:24 ` [PATCH 1/2] perf/core: Bail out early if the request AUX area is out of bound Shuai Xue
2023-06-12 7:38 ` Leo Yan
2023-06-12 8:35 ` Shuai Xue
2023-06-12 10:05 ` Leo Yan
2023-06-12 10:25 ` Leo Yan
2023-06-13 3:00 ` Shuai Xue
2023-06-12 8:47 ` James Clark
2023-06-12 5:24 ` [PATCH 2/2] perf/ring_buffer: Fix high-order allocations for AUX space with correct MAX_ORDER limit Shuai Xue
2023-06-12 8:30 ` Leo Yan
2023-06-12 8:35 ` Shuai Xue
2023-06-12 8:45 ` James Clark
2023-06-12 9:09 ` Leo Yan
2023-06-13 6:42 ` Shuai Xue
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=20230612052452.53425-1-xueshuai@linux.alibaba.com \
--to=xueshuai@linux.alibaba.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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®