public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Alexey Budankov <alexey.budankov@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Andi Kleen <ak@linux.intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v11 1/3]: perf util: map data buffer for preserving collected data
Date: Mon, 8 Oct 2018 14:37:24 +0200	[thread overview]
Message-ID: <20181008123724.GC18757@krava> (raw)
In-Reply-To: <43747adb-4591-e0ff-f173-525a5f5d47b4@linux.intel.com>

On Mon, Oct 08, 2018 at 02:55:13PM +0300, Alexey Budankov wrote:
> Hi,
> 
> On 08.10.2018 13:50, Jiri Olsa wrote:
> > On Mon, Oct 08, 2018 at 09:14:29AM +0300, Alexey Budankov wrote:
> >>
> <SNIP>
> >> diff --git a/tools/perf/Makefile.config b/tools/perf/Makefile.config
> >> index f6d1a03c7523..2e90f4ce9214 100644
> >> --- a/tools/perf/Makefile.config
> >> +++ b/tools/perf/Makefile.config
> >> @@ -355,6 +355,11 @@ endif # NO_LIBELF
> >>  
> >>  ifeq ($(feature-glibc), 1)
> >>    CFLAGS += -DHAVE_GLIBC_SUPPORT
> >> +  ifndef NO_AIO
> > 
> > hum, do we need NO_AIO? we have the --aio option to enable that right?
> 
> Right. Enable that *in runtime*.
> 
> > I guess BIONIC does not support aio, but but will it fail when it's
> > compiled in there?
> 
> Please see updated section of the cover letter for more information 
> regarding this. Possible compilation issues is that's why we better 
> have this capability in advance:
>   
>   objdump -T tools/perf/perf | grep aio
> 
>   0000000000000000      DF *UND*	0000000000000000  GLIBC_2.2.5 aio_suspend64
>   0000000000000000      DF *UND*	0000000000000000  GLIBC_2.2.5 aio_return64
>   0000000000000000      DF *UND*	0000000000000000  GLIBC_2.2.5 aio_error64
>   0000000000000000      DF *UND*	0000000000000000  GLIBC_2.2.5 aio_write64
> 
> IMHO, it is worth implementing NO_AIO define.

ok, if there are c libs that won't compile with that,
then sure, we need it

thanks,
jirka

  reply	other threads:[~2018-10-08 12:37 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08  5:55 [PATCH v11 0/3]: perf: reduce data loss when profiling highly parallel CPU bound workloads Alexey Budankov
2018-10-08  6:14 ` [PATCH v11 1/3]: perf util: map data buffer for preserving collected data Alexey Budankov
2018-10-08 10:50   ` Jiri Olsa
2018-10-08 11:55     ` Alexey Budankov
2018-10-08 12:37       ` Jiri Olsa [this message]
2018-10-08 10:50   ` Jiri Olsa
2018-10-08 12:03     ` Alexey Budankov
2018-10-08 12:38       ` Jiri Olsa
2018-10-08 14:43         ` Alexey Budankov
2018-10-08 15:12           ` Jiri Olsa
2018-10-08 15:38             ` Alexey Budankov
2018-10-08 10:51   ` Jiri Olsa
2018-10-08 12:05     ` Alexey Budankov
2018-10-08  6:17 ` [PATCH v11 2/3]: perf record: enable asynchronous trace writing Alexey Budankov
2018-10-08 10:50   ` Jiri Olsa
2018-10-08 12:17     ` Alexey Budankov
2018-10-08 10:51   ` Jiri Olsa
2018-10-08 12:19     ` Alexey Budankov
2018-10-08 10:52   ` Jiri Olsa
2018-10-08 12:24     ` Alexey Budankov
2018-10-08 12:53       ` Jiri Olsa
2018-10-08 14:42         ` Alexey Budankov
2018-10-08 15:11           ` Jiri Olsa
2018-10-08 15:39             ` Alexey Budankov
2018-10-08 10:57   ` Jiri Olsa
2018-10-08 12:15     ` Alexey Budankov
2018-10-08 10:58   ` Jiri Olsa
2018-10-08 12:26     ` Alexey Budankov
2018-10-08  6:19 ` [PATCH v11 3/3]: perf record: extend trace writing to multi AIO Alexey Budankov
2018-10-08 10:55   ` Jiri Olsa
2018-10-08 11:47     ` Alexey Budankov
2018-10-08 12:45       ` Jiri Olsa
2018-10-08 15:21         ` Alexey Budankov

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=20181008123724.GC18757@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=alexey.budankov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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