[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAP-5=fX5KaQE+P5X+jBt9uFymkjWbUi_0dgq2w=18jX8vVQ1XQ@mail.gmail.com>
Date: Fri, 24 Mar 2023 00:15:27 -0700
From: Ian Rogers <irogers@...gle.com>
To: Dan Williams <dan.j.williams@...el.com>
Cc: "Liang, Kan" <kan.liang@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Zhengjun Xing <zhengjun.xing@...ux.intel.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
Edward Baker <edward.baker@...el.com>, perry.taylor@...el.com,
caleb.biggers@...el.com, samantha.alt@...el.com,
weilin.wang@...el.com
Subject: Re: [PATCH v2 8/9] perf metrics: Add has_optane literal
On Thu, Mar 23, 2023 at 1:44 PM Dan Williams <dan.j.williams@...el.com> wrote:
>
> Liang, Kan wrote:
> >
> >
> > On 2023-03-23 3:20 p.m., Ian Rogers wrote:
> > > Add literal so that if optane memory isn't installed we can record
> > > fewer events.
> >
> > I think we call it pmem (Persistent Memory) everywhere in the Linux
> > code. Maybe we should use #has_pmem instead?
>
> That makes sense especially because has_optane implies more precision
> than the the check is performing. In general Optane is probably the
> widest deployed NVDIMM type, but this check will succeed with battery
> backed NVDIMMs and emulated PMEM in VMs which I think is perfectly ok
> for making a default event record decision.
Thanks, I'll change this in v3.
Ian
Powered by blists - more mailing lists