[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1431588493-1474-1-git-send-email-milos@redhat.com>
Date: Thu, 14 May 2015 09:28:09 +0200
From: Milos Vyletel <milos@...hat.com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Namhyung Kim <namhyung@...nel.org>,
Milos Vyletel <milos@...hat.com>, Jiri Olsa <jolsa@...nel.org>,
He Kuang <hekuang@...wei.com>,
Adrian Hunter <adrian.hunter@...el.com>,
linux-kernel@...r.kernel.org (open list:PERFORMANCE EVENT...)
Subject: [PATCH 0/2] Add perf debug dir locking
Hi,
this series is follow up on my last submission where Jirka mentioned it would
be nice to have some locking around .debug dir operations.
https://lkml.org/lkml/2015/3/20/126
Following two patches add such functionality by utilizing flock. Since flock
supports both shared(read) and exclusive(write) locks both variants are being
added so that we can use multiple readers while only one writer.
Having said that any comments/suggestions on the code are welcome.
I did some basic testing. Mostly manual tool testing as well as the recreator
from above mentioned URL. I do not expect any functional change however more
testing is welcome.
Milos
Milos Vyletel (2):
perf/tools: add read/write buildid dir locks
perf/tools: put new buildid locks to use
tools/perf/builtin-buildid-cache.c | 12 +++++
tools/perf/util/build-id.c | 97 ++++++++++++++++++++++++++++++++++----
tools/perf/util/build-id.h | 5 ++
3 files changed, 106 insertions(+), 8 deletions(-)
--
2.4.0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists