Displaying 20 results from an estimated 1984 matches for "perfs".
Did you mean:
perf
2014 May 05
2
[GIT PULL 01/12] perf/core improvements and fixes
hi Ingo,
please consider pulling
thanks,
jirka
The following changes since commit 3617660e4e1618a888a2e3a4067224534302cb33:
Merge tag 'perf-core-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf into perf/core (2014-05-01 08:24:59 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
2014 May 05
2
[GIT PULL 01/12] perf/core improvements and fixes
hi Ingo,
please consider pulling
thanks,
jirka
The following changes since commit 3617660e4e1618a888a2e3a4067224534302cb33:
Merge tag 'perf-core-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf into perf/core (2014-05-01 08:24:59 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
2014 May 05
0
[GIT PULL 01/12] perf/core improvements and fixes
* Jiri Olsa <jolsa at kernel.org> wrote:
>
> hi Ingo,
> please consider pulling
>
> thanks,
> jirka
>
>
> The following changes since commit 3617660e4e1618a888a2e3a4067224534302cb33:
>
> Merge tag 'perf-core-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf into perf/core (2014-05-01 08:24:59 +0200)
>
> are
2014 Apr 13
1
[PATCH] tools: Consolidate types.h
And while we're at it, let's do another consolidation:
---
From: Borislav Petkov <bp at suse.de>
Date: Sat, 12 Apr 2014 20:10:49 +0200
Subject: [PATCH] tools: Consolidate types.h
Combine all definitions into a common tools/include/linux/types.h and
kill the wild growth elsewhere. While at it, move u64_swap to its only
user, evsel.h.
Signed-off-by: Borislav Petkov <bp at
2014 Apr 13
1
[PATCH] tools: Consolidate types.h
And while we're at it, let's do another consolidation:
---
From: Borislav Petkov <bp at suse.de>
Date: Sat, 12 Apr 2014 20:10:49 +0200
Subject: [PATCH] tools: Consolidate types.h
Combine all definitions into a common tools/include/linux/types.h and
kill the wild growth elsewhere. While at it, move u64_swap to its only
user, evsel.h.
Signed-off-by: Borislav Petkov <bp at
2014 Apr 11
2
[PATCH] tools: Unify export.h
On Thu, Apr 10, 2014 at 07:38:05PM +0200, Borislav Petkov wrote:
> Rebased onto current acme/perf/core:
>
> --
> From: Borislav Petkov <bp at suse.de>
> Date: Sun, 23 Feb 2014 12:04:53 +0100
> Subject: [PATCH] tools: Unify export.h
>
> So tools/ has been growing three, at a different stage of their
> development export.h headers and so we should unite into one.
2014 Apr 11
2
[PATCH] tools: Unify export.h
On Thu, Apr 10, 2014 at 07:38:05PM +0200, Borislav Petkov wrote:
> Rebased onto current acme/perf/core:
>
> --
> From: Borislav Petkov <bp at suse.de>
> Date: Sun, 23 Feb 2014 12:04:53 +0100
> Subject: [PATCH] tools: Unify export.h
>
> So tools/ has been growing three, at a different stage of their
> development export.h headers and so we should unite into one.
2012 Jun 20
2
[LLVMdev] Exception handling slowdown?
Did something change with exception handling recently? A bunch of lit bots are
showing slower compile times for many tests.
Ciao, Duncan.
On 20/06/12 07:53, llvm-testresults at cs.uiuc.edu wrote:
>
> lab-mini-03__O0-g__clang_DEV__x86_64 test results
> <http://llvm.org/perf/db_default/v4/nts/1283?compare_to=1278&baseline=999>
>
> Run Order Start Time Duration
>
2012 Jun 25
0
[LLVMdev] Exception handling slowdown?
Nothing that I'm aware of has changed with EH. Is it possible to bisect the problem?
-bw
On Jun 20, 2012, at 12:38 AM, Duncan Sands <baldrick at free.fr> wrote:
> Did something change with exception handling recently? A bunch of lit bots are
> showing slower compile times for many tests.
>
> Ciao, Duncan.
>
> On 20/06/12 07:53, llvm-testresults at cs.uiuc.edu
2012 Jul 05
2
[LLVMdev] Exception handling slowdown?
Hi Bill,
> Nothing that I'm aware of has changed with EH. Is it possible to bisect the problem?
I don't see any relevant LLVM changes, so I guess clang C++ compilation slowed
down due to some clang changes. I'm not going to investigate this.
Ciao, Duncan.
>
> -bw
>
> On Jun 20, 2012, at 12:38 AM, Duncan Sands <baldrick at free.fr> wrote:
>
>> Did
2011 Dec 01
1
[LLVMdev] [llvm-testresults] bwilson__llvm-gcc_PROD__i386 nightly tester results
Are these 225 compile time regressions real? It sure looks bad!
Ciao, Duncan.
On 01/12/11 09:39, llvm-testresults at cs.uiuc.edu wrote:
>
> bwilson__llvm-gcc_PROD__i386 nightly tester results
>
> URL http://llvm.org/perf/db_default/simple/nts/380/
> Nickname bwilson__llvm-gcc_PROD__i386:4
> Name curlew.apple.com
>
> Run ID Order Start Time End Time
> Current 380
2016 May 11
0
Questions about CMT event statistic
Hi
I'm testing cmt event of libvirt, and I have two questions. I will be very grateful if someone can give me some help.
Q1:"virsh domstats --perf" and linux perf tool has different result.
I have a guest with cmt event enabled, start guest and get perf statistic every 1s:
# while true; do virsh domstats rhel7.2-1030 --perf; sleep 1; done
In the meanwhile, I use perf tool to get
2012 Jul 06
0
[LLVMdev] Exception handling slowdown?
On Jul 5, 2012, at 1:33 AM, Duncan Sands wrote:
> Hi Bill,
>
>> Nothing that I'm aware of has changed with EH. Is it possible to bisect the problem?
>
> I don't see any relevant LLVM changes, so I guess clang C++ compilation slowed
> down due to some clang changes. I'm not going to investigate this.
>
Crumbs.
John, Do you know of anything that went into
2014 Feb 25
2
[PATCH] tools: Unify export.h
Em Tue, Feb 25, 2014 at 10:52:02PM +1030, Rusty Russell escreveu:
> Borislav Petkov <bp at suse.de> writes:
> > On Tue, Feb 25, 2014 at 12:09:23PM +1030, Rusty Russell wrote:
> >> Should we get more ambitious and start a fake-kernel/ directory where
> >> we can put userspace equivs/stubs of kernel functionality?
> >
> > Dunno - people like to do that
2014 Feb 25
2
[PATCH] tools: Unify export.h
Em Tue, Feb 25, 2014 at 10:52:02PM +1030, Rusty Russell escreveu:
> Borislav Petkov <bp at suse.de> writes:
> > On Tue, Feb 25, 2014 at 12:09:23PM +1030, Rusty Russell wrote:
> >> Should we get more ambitious and start a fake-kernel/ directory where
> >> we can put userspace equivs/stubs of kernel functionality?
> >
> > Dunno - people like to do that
2020 Apr 18
2
PerfJITEventListener needs perf-<pid>.map?
I'm trying to use PerfJITEventListener with llvm::orc::LLJITBuilder:
1. perf record -o /tmp/perf.data -- <my_binary_with_event_listener>
2. perf inject -j -v -i /tmp/perf.data -o /tmp/perf.data.jit
*jit marker found: ~.debug/jit/llvm-IR-jit-20200417-3c2242/jit-149849.dump*
*injecting: ~/.debug/jit/llvm-IR-jit-20200417-3c2242/jit-149849.dump*
*write ELF image
2015 May 10
2
[LLVMdev] http://llvm.org/perf/ instability: some clues
Daniel, Tobias, Renato and myself have been looking a little bit at the
potential underlying reason
for why http://llvm.org/perf/ is instable, and have found some clues. I want
to share them here
to give people with more experience in the frameworks used by LNT (flask,
sqlalchemy, wsgi, .)
a chance to check if our reasoning below seems plausible.
Daniel noticed the following backtrace in the
2020 Mar 16
2
ORC JIT Weekly #7 -- JITEventListener support and Swift Immediate Mode Migration
Hi,
On 2020-03-09 21:20:44 +0100, Frank Tetzel via llvm-dev wrote:
> I think, debugging and profiling support is very important for a JIT
> engine. I could never get it to work with older LLVM versions. Is there
> example code somewhere available?
Since I added the perf listener I probably can help you with that. What
exactly was the problem you were hitting?
I don't have isolated
2017 Jul 31
2
Internal server error when submitting LNT to lnt.llvm.org
Dear all,
I recently started to see internal server errors when submitting perf
results to lnt.llvm.org
http://lab.llvm.org:8011/builders/perf-x86_64-penryn-O3-polly-before-vectorizer/builds/1154/steps/lnt.nightly-test/logs/stdio
nt
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-before-vectorizer/tests/nt/build/sample-0/report.simple.csv
2014 Apr 14
1
[PATCH 1/3] tools: Unify export.h
From: Borislav Petkov <bp at suse.de>
So tools/ has been growing three, at a different stage of their
development export.h headers and so we should unite into one. Add
tools/include/ to the include path of virtio and liblockdep to pick the
shared header now.
Cc: Sasha Levin <sasha.levin at oracle.com>
Cc: Peter Zijlstra <a.p.zijlstra at chello.nl>
Cc: Paul Mackerras <paulus