[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200129193616.GT14914@hirez.programming.kicks-ass.net>
Date: Wed, 29 Jan 2020 20:36:16 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: SeongJae Park <sj38.park@...il.com>
Cc: sjpark@...zon.com, akpm@...ux-foundation.org,
SeongJae Park <sjpark@...zon.de>, acme@...nel.org,
amit@...nel.org, brendan.d.gregg@...il.com, corbet@....net,
dwmw@...zon.com, mgorman@...e.de, rostedt@...dmis.org,
kirill@...temov.name, brendanhiggins@...gle.com,
colin.king@...onical.com, minchan@...nel.org,
vdavydov.dev@...il.com, vdavydov@...allels.com, linux-mm@...ck.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
Ingo Molnar <mingo@...hat.com>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>
Subject: Re: Re: Re: Re: [PATCH v2 0/9] Introduce Data Access MONitor (DAMON)
On Wed, Jan 29, 2020 at 08:06:45PM +0100, SeongJae Park wrote:
> > Perf can do address based sampling of memops, I suspect you can create
> > something using that.
>
> If you're saying implementing DAMON in 'perf mem', I think it would conflict
> with abovely explained DAMON's goal.
>
> Else, if you're saying it would be the right place to handle the DAMON
> generated data, I agree, thank you for pointing me that. Will keep it in mind
> while shaping the interface of DAMON.
I'm saying it might be able to provide the data you need; without damon.
Might; because I'm not entirely sure what you're looking for, nor
exactly what events we have that provide address information.
Powered by blists - more mailing lists