From: Peter Zijlstra <peterz@infradead.org>
To: Sami Farin <hvtaifwkbgefbaei@gmail.com>,
Linux kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 4.19.21: perf does not work on Ryzen, OK with 4.19.20
Date: Wed, 13 Feb 2019 14:09:23 +0100 [thread overview]
Message-ID: <20190213130923.GR32494@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190213110803.xbnganrtvgmfgh3b@m.mifar.in>
On Wed, Feb 13, 2019 at 12:08:03PM +0100, Sami Farin wrote:
> The same .config, BIOS, and kernel boot parameters in both kernels.
>
> # perf top -v
> ┌─Error:────────────────────────────────────────┐
> │Failed to mmap with 12 (Cannot allocate memory)│
I think you got bit by this one:
http://lkml.kernel.org/r/tip-528871b456026e6127d95b1b2bd8e3a003dc1614@git.kernel.org
prev parent reply other threads:[~2019-02-13 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 11:08 4.19.21: perf does not work on Ryzen, OK with 4.19.20 Sami Farin
2019-02-13 13:09 ` Peter Zijlstra [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=20190213130923.GR32494@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=hvtaifwkbgefbaei@gmail.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).