From: Peter Zijlstra <peterz@infradead.org>
To: zhe.he@windriver.com
Cc: acme@kernel.org, ak@linux.intel.com,
alexander.shishkin@linux.intel.com, bp@alien8.de, hpa@zytor.com,
jolsa@kernel.org, jolsa@redhat.com, kan.liang@linux.intel.com,
mingo@redhat.com, namhyung@kernel.org, tglx@linutronix.de,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-rt-users@vger.kernel.org
Subject: Re: [PATCH] perf/x86/intel: Avoid unnecessary reallocations of memory allocated in cpu hotplug prepare state
Date: Tue, 18 Dec 2018 12:02:09 +0100 [thread overview]
Message-ID: <20181218110209.GD15430@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1545129033-21757-1-git-send-email-zhe.he@windriver.com>
On Tue, Dec 18, 2018 at 06:30:33PM +0800, zhe.he@windriver.com wrote:
> Besides, in preempt-rt full mode, the freeing can happen in atomic context and
> thus cause the following BUG.
Hurm, I though we fixed all those long ago..
And no, the patch is horrible; that's what we have things like
x86_pmu::cpu_dead() for.
next prev parent reply other threads:[~2018-12-18 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 10:30 [PATCH] perf/x86/intel: Avoid unnecessary reallocations of memory allocated in cpu hotplug prepare state zhe.he
2018-12-18 11:02 ` Peter Zijlstra [this message]
2018-12-18 11:16 ` Sebastian Andrzej Siewior
2018-12-18 11:31 ` Peter Zijlstra
2018-12-18 11:37 ` Peter Zijlstra
2018-12-18 11:47 ` Sebastian Andrzej Siewior
2018-12-18 12:34 ` Peter Zijlstra
2018-12-18 12:45 ` He Zhe
2018-12-18 13:59 ` Sebastian Andrzej Siewior
2018-12-19 16:53 ` [PATCH] perf/x86/intel: Delay memory deallocation until x86_pmu_dead_cpu() Sebastian Andrzej Siewior
2019-02-04 8:48 ` [tip:perf/core] " tip-bot for Peter Zijlstra
2018-12-18 11:25 ` [PATCH] perf/x86/intel: Avoid unnecessary reallocations of memory allocated in cpu hotplug prepare state Thomas Gleixner
2018-12-18 11:38 ` Peter Zijlstra
2018-12-18 11:14 ` Sebastian Andrzej Siewior
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=20181218110209.GD15430@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zhe.he@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.