From: Mark Rutland <mark.rutland@arm.com>
To: Jeremy Linton <jeremy.linton@arm.com>
Cc: Will Deacon <will.deacon@arm.com>,
linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org,
punit.agrawal@arm.com, steve.capper@arm.com, msalter@redhat.com,
mlangsdorf@redhat.com, linux@armlinux.org.uk
Subject: Re: [PATCH v11 7/7] arm: pmu: Add PMU definitions for cores not initially online
Date: Wed, 7 Dec 2016 11:08:23 +0000 [thread overview]
Message-ID: <20161207110823.GA7054@leverpostej> (raw)
In-Reply-To: <457894f4-67f8-9d32-ee8b-5a34e9a21488@arm.com>
On Tue, Dec 06, 2016 at 11:56:56AM -0600, Jeremy Linton wrote:
> Hi,
> Which might not be the right choice because
> even without these ACPI specific bits, simply running a few cpus
> online/offline while simultaneously doing something like `perf stat
> -e cache-misses ls &` in a loop causes deadlocks/crashes.
>
> That problem doesn't appear to be specific to the ACPI/PMU so I've
> stayed away from it in this patch set, although potentially a larger
> fix might cover this as well.
Urrgh; I can reproduce lockups on Seattle with v4.9-rc8.
I'll look into that.
If you see any more issues in this area, please report them in a new
thread.
Thanks,
Mark.
WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v11 7/7] arm: pmu: Add PMU definitions for cores not initially online
Date: Wed, 7 Dec 2016 11:08:23 +0000 [thread overview]
Message-ID: <20161207110823.GA7054@leverpostej> (raw)
In-Reply-To: <457894f4-67f8-9d32-ee8b-5a34e9a21488@arm.com>
On Tue, Dec 06, 2016 at 11:56:56AM -0600, Jeremy Linton wrote:
> Hi,
> Which might not be the right choice because
> even without these ACPI specific bits, simply running a few cpus
> online/offline while simultaneously doing something like `perf stat
> -e cache-misses ls &` in a loop causes deadlocks/crashes.
>
> That problem doesn't appear to be specific to the ACPI/PMU so I've
> stayed away from it in this patch set, although potentially a larger
> fix might cover this as well.
Urrgh; I can reproduce lockups on Seattle with v4.9-rc8.
I'll look into that.
If you see any more issues in this area, please report them in a new
thread.
Thanks,
Mark.
next prev parent reply other threads:[~2016-12-07 11:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 18:55 [PATCH v11 0/7] Enable PMUs in ACPI systems Jeremy Linton
2016-12-02 18:55 ` Jeremy Linton
2016-12-02 18:55 ` [PATCH v11 1/7] arm64: Rename the common MADT parse routine Jeremy Linton
2016-12-02 18:55 ` Jeremy Linton
2016-12-02 18:55 ` [PATCH v11 2/7] arm: arm64: Add routine to determine cpuid of other cpus Jeremy Linton
2016-12-02 18:55 ` Jeremy Linton
2016-12-02 18:55 ` [PATCH v11 3/7] arm64: pmu: Cache PMU interrupt numbers from MADT parse Jeremy Linton
2016-12-02 18:55 ` Jeremy Linton
2016-12-02 18:55 ` [PATCH v11 4/7] arm: arm64: pmu: Assign platform PMU CPU affinity Jeremy Linton
2016-12-02 18:55 ` Jeremy Linton
2016-12-02 18:55 ` [PATCH v11 5/7] arm64: pmu: Detect multiple generic PMUs and append counter Jeremy Linton
2016-12-02 18:55 ` Jeremy Linton
2016-12-02 18:56 ` [PATCH v11 6/7] arm64: pmu: Detect and enable multiple PMUs in an ACPI system Jeremy Linton
2016-12-02 18:56 ` Jeremy Linton
2016-12-02 18:56 ` [PATCH v11 7/7] arm: pmu: Add PMU definitions for cores not initially online Jeremy Linton
2016-12-02 18:56 ` Jeremy Linton
2016-12-06 15:21 ` Will Deacon
2016-12-06 15:21 ` Will Deacon
2016-12-06 17:56 ` Jeremy Linton
2016-12-06 17:56 ` Jeremy Linton
2016-12-07 11:08 ` Mark Rutland [this message]
2016-12-07 11:08 ` Mark Rutland
2016-12-15 17:08 ` Will Deacon
2016-12-15 17:08 ` Will Deacon
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=20161207110823.GA7054@leverpostej \
--to=mark.rutland@arm.com \
--cc=jeremy.linton@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mlangsdorf@redhat.com \
--cc=msalter@redhat.com \
--cc=punit.agrawal@arm.com \
--cc=steve.capper@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 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.