[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <641cba052d0f8_1b98bb294ab@dwillia2-xfh.jf.intel.com.notmuch>
Date: Thu, 23 Mar 2023 13:43:49 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: "Liang, Kan" <kan.liang@...ux.intel.com>,
Ian Rogers <irogers@...gle.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>,
Dan Williams <dan.j.williams@...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
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.
Powered by blists - more mailing lists