[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1708031355400.26654@macbook-air>
Date: Thu, 3 Aug 2017 13:57:33 -0400 (EDT)
From: Vince Weaver <vincent.weaver@...ne.edu>
To: "Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>
cc: Peter Zijlstra <peterz@...radead.org>,
Jiri Olsa <jolsa@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Ingo Molnar <mingo@...nel.org>,
Vince Weaver <vincent.weaver@...ne.edu>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] kernel/events: Add option to notify through
signals on wakeup
On Tue, 1 Aug 2017, Naveen N. Rao wrote:
> Add a new option 'signal_on_wakeup' to request for a signal to be
> delivered on ring buffer wakeup controlled through watermark and
> {wakeup_events, wakeup_watermark}. HUP is signaled on exit.
>
> Setting signal_on_wakeup disables use of IOC_REFRESH to control signal
> delivery, instead relying on IOC_ENABLE/DISABLE.
so I probably missed the original thread on this new interface, but why is
IOC_REFRESH not being used?
For new interfaces like this it's also nice to have some text that can be
added to the perf_event_open() manpage, especially if there's weird
conditions like this.
Vince
Powered by blists - more mailing lists