On Sun, Jul 10, 2016 at 11:48:11AM -0700, Stephane Eranian wrote: > So we either redirect ref-cycles towards 0x013c > (cpu_clk_unhalted:xlck) or another event maybe
Another solution is us introducing (another) fake event, say 0x0400, which will have a constrained mask of: 0x0F | (6 << 32) and varies in actual encoding depending on which counter it lands on. That way we have more flexibility in scheduling the NMI watchdog, and its exact period isn't _that_ important; although we could obviously also fix up some of that if we wanted.
