search for: nv_ioctl

...gs = data; > struct nvkm_device *device = nv_device(object); > struct nvkm_pm *ppm = (void *)object->engine; > @@ -97,9 +97,9 @@ nvkm_perfctr_query(struct nvkm_object *object, void *data, u32 size) > int tmp = 0, di, si; > int ret; > > - nv_ioctl(object, "perfctr query size %d\n", size); > + nv_ioctl(object, "perfmon query signal size %d\n", size); > if (nvif_unpack(args->v0, 0, 0, false)) { > - nv_ioctl(object, "perfctr query vers %d iter %08x\n", > + nv...

Hello, This series exposes global performance counters (PCOUNTER) to the userspace through the nvif interface by reworking most of the code related to the PM engine. This interface will allow the userspace to control and monitor complex hardware events like the proprietary driver already does, for example with CUPTI and PerfKit. For now, this series only exposes performance counters on NV50,

Hi there, Resending these now that they've had some more polish and testing, and I heard that Ben's vacation is over :-) These patches work as a starting point for more explicit error mechanisms and better robustness. At the moment, when a job hangs or faults, it seems that nouveau doesn't quite know how to handle the situation and often results in a hang. Some of these situations