linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: linux-arm-kernel@lists.infradead.org,
	Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Kim Phillips <kim.phillips@arm.com>,
	Thomas Richter <tmricht@linux.ibm.com>,
	open list <linux-kernel@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	rmk+kernel@armlinux.org.uk, Ingo Molnar <mingo@redhat.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Jiri Olsa <jolsa@redhat.com>,
	l.stach@pengutronix.de
Subject: Re: [PATCH 2/2] perf tests: Add a test for the ARM 32-bit [vectors] page
Date: Thu, 25 Oct 2018 10:19:54 -0700	[thread overview]
Message-ID: <175fd725-a97a-c282-5aa1-952014ff9023@gmail.com> (raw)
In-Reply-To: <20181025021013.GA30116@lunn.ch>

On 10/24/18 7:10 PM, Andrew Lunn wrote:
> On Wed, Oct 24, 2018 at 05:09:05PM -0700, Florian Fainelli wrote:
>> perf on ARM requires CONFIG_KUSER_HELPERS to be turned on to allow some
>> independance with respect to the ARM CPU being used. Add a test which
>> tries to locate the [vectors] page, created when CONFIG_KUSER_HELPERS is
>> turned on to help asses the system's health.
> 
> Hi Florian
> 
> I've suffered the pain from missing CONFIG_KUSER_HELPERS. The
> segfaults give little clue as to what is going wrong,and gdb is not
> much use either.

If you have a working backtrace, you can typically see the virtual
address being in 0xffff_xxxx which gives a bit of a clue, but yes, this
is not particularly helpful.

> 
> What i don't see here is any clue to CONFIG_KUSER_HELPERS. If the test
> fails, could you print a message suggesting CONFIG_KUSER_HELPERS on
> ARM?

Sure, sounds reasonable, thanks for taking a look.
-- 
Florian

  reply	other threads:[~2018-10-25 17:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25  0:09 [PATCH 0/2] perf tests: Check for ARM [vectors] page Florian Fainelli
2018-10-25  0:09 ` [PATCH 1/2] perf tools: Make find_vdso_map() more modular Florian Fainelli
2018-10-25  0:14   ` Florian Fainelli
2018-10-25  0:09 ` [PATCH 2/2] perf tests: Add a test for the ARM 32-bit [vectors] page Florian Fainelli
2018-10-25  2:10   ` Andrew Lunn
2018-10-25 17:19     ` Florian Fainelli [this message]
2018-10-25 17:32       ` Russell King - ARM Linux
2018-10-25 17:53         ` Florian Fainelli
2018-10-25 18:03           ` Russell King - ARM Linux
2018-10-31 22:21 ` [PATCH 0/2] perf tests: Check for ARM " Florian Fainelli

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=175fd725-a97a-c282-5aa1-952014ff9023@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=andrew@lunn.ch \
    --cc=gregkh@linuxfoundation.org \
    --cc=jolsa@redhat.com \
    --cc=kim.phillips@arm.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@linux.ibm.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=tglx@linutronix.de \
    --cc=tmricht@linux.ibm.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 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).