linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jolsa@redhat.com
Cc: acme@kernel.org, linux-kernel@vger.kernel.org,
	namhyung@kernel.org, jolsa@kernel.org
Subject: Re: [PATCH RFC] hist lookups
Date: Mon, 05 Nov 2018 20:03:21 -0800 (PST)	[thread overview]
Message-ID: <20181105.200321.1569039579935458312.davem@davemloft.net> (raw)
In-Reply-To: <20181105.194542.476367332910923203.davem@davemloft.net>

From: David Miller <davem@davemloft.net>
Date: Mon, 05 Nov 2018 19:45:42 -0800 (PST)

> Build fix for sparc below, I'm playing with this now.

I get various assertion failures and crashes during make -j128 kernel
builds on my sparc64 box:

====================
perf: Segmentation fault
-------- backtrace --------
/lib/sparc-linux-gnu/libc.so.6(+0x38918)[0xf7264918]
./perf(thread__set_namespaces+0x30)[0x10b2f0]
./perf(machine__process_namespaces_event+0x134)[0xfad54]
./perf[0x517b8]
./perf(queued_events__flush+0xc8)[0x109288]
./perf[0x5133c]
/lib/sparc-linux-gnu/libpthread.so.0(+0x6714)[0xf7c7e714]
/lib/sparc-linux-gnu/libc.so.6(+0xf70b4)[0xf73230b4]
/lib/sparc-linux-gnu/libpthread.so.0(+0x6a84)[0xf7c7ea84]
davem@patience:~/src/GIT/sparc/tools/perf$ 
====================

and:

====================
perf: /home/davem/src/GIT/sparc/tools/include/linux/refcount.h:131: refcount_sub_and_test: Assertion `!(new > val)' failed.
====================

I don't have a lot of time to try and debug this, but let me know if you
want any fixes tested.

I did look at the changes and I like what you're trying to do.

  reply	other threads:[~2018-11-06  4:06 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31  5:03 [PATCH RFC] hist lookups David Miller
2018-10-31 12:43 ` Arnaldo Carvalho de Melo
2018-10-31 15:39   ` Jiri Olsa
2018-10-31 16:08     ` David Miller
2018-11-03  6:30       ` David Miller
2018-11-04 20:18         ` Jiri Olsa
2018-11-05  0:50           ` David Miller
2018-11-05 20:34             ` Jiri Olsa
2018-11-05 22:52               ` David Miller
2018-11-06  3:45               ` David Miller
2018-11-06  4:03                 ` David Miller [this message]
2018-11-06  4:53                   ` David Miller
2018-11-06 11:54                     ` Jiri Olsa
2018-11-19  5:26                       ` Namhyung Kim
2018-11-19  9:12                         ` Jiri Olsa
2018-11-20  1:13                           ` Namhyung Kim
2018-11-06 20:42                     ` Jiri Olsa
2018-11-07  6:13                       ` David Miller
2018-11-07  8:32                         ` Jiri Olsa
2018-11-07 19:43                           ` Jiri Olsa
2018-11-07 20:01                             ` David Miller
2018-11-07 20:28                               ` Arnaldo Carvalho de Melo
2018-11-08  6:04                                 ` David Miller
2018-11-08  7:13                               ` Jiri Olsa
2018-11-09  1:07                                 ` David Miller
2018-11-11 19:41                                   ` Jiri Olsa
2018-11-11 19:41                                     ` Jiri Olsa
2018-11-11 22:32                                     ` David Miller
2018-11-11 22:43                                       ` Jiri Olsa
2018-11-11 22:58                                         ` David Miller
2018-11-11 23:08                                     ` David Miller
2018-11-11 23:26                                       ` Jiri Olsa
2018-11-11 23:32                                         ` David Miller
2018-11-13 10:40                                           ` Jiri Olsa
2018-11-19  4:52                                             ` David Miller
2018-11-19  6:28                                               ` Namhyung Kim
2018-11-19  6:33                                                 ` David Miller
2018-11-19  7:16                                                   ` Namhyung Kim
2018-11-19  9:14                                               ` Jiri Olsa
2018-11-06 11:51                 ` Jiri Olsa

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=20181105.200321.1569039579935458312.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=acme@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@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).