Displaying 20 results from an estimated 1000 matches similar to: "[PATCH] pmu: fix queued messages while getting no IRQ"
2015 Nov 14
0
[PATCH v3] pmu: fix queued messages while getting no IRQ
I encountered while stresstesting the reclocking code, that rarely (1 out of
20.000+ requests) we don't get any IRQ in nvkm_pmu_intr.
This means we have a queued message on the pmu, but nouveau doesn't read it and
waits infinitely in nvkm_pmu_send:
if (reply) {
wait_event(pmu->recv.wait, (pmu->recv.process == 0));
therefore let us use wait_event_timeout with a 1s timeout frame
2015 Nov 14
1
[PATCH v2] pmu: fix queued messages while getting no IRQ
I encountered while stresstesting the reclocking code, that rarely (1 out of
20.000+ requests) we don't get any IRQ in nvkm_pmu_intr.
This means we have a queued message on the pmu, but nouveau doesn't read it and
waits infinitely in nvkm_pmu_send:
if (reply) {
wait_event(pmu->recv.wait, (pmu->recv.process == 0));
therefore let us use wait_event_timeout with a 1s timeout frame
2016 Mar 01
2
[PATCH 0/2] PMU communications improvements
Both patches should make the communicating with the PMU more stable.
Karol Herbst (2):
pmu: fix queued messages while getting no IRQ
pmu: be more strict about locking
drm/nouveau/nvkm/subdev/pmu/base.c | 49 ++++++++++++++++++++++++++++++++------
1 file changed, 42 insertions(+), 7 deletions(-)
--
2.7.2
2018 Dec 19
1
[PATCH] drm/nouveau/pmu: don't print reply values if exec is false
From: Colin Ian King <colin.king at canonical.com>
Currently the uninitialized values in the array reply are printed out
when exec is false and nvkm_pmu_send has not updated the array. Avoid
confusion by only dumping out these values if they have been actually
updated.
Detected by CoverityScan, CID#1271291 ("Uninitialized scaler variable")
Fixes: ebb58dc2ef8c
2020 Jan 16
0
[PATCH AUTOSEL 4.19 203/671] drm/nouveau/pmu: don't print reply values if exec is false
From: Colin Ian King <colin.king at canonical.com>
[ Upstream commit b1d03fc36ec9834465a08c275c8d563e07f6f6bf ]
Currently the uninitialized values in the array reply are printed out
when exec is false and nvkm_pmu_send has not updated the array. Avoid
confusion by only dumping out these values if they have been actually
updated.
Detected by CoverityScan, CID#1271291 ("Uninitialized
2020 Jan 16
0
[PATCH AUTOSEL 4.14 112/371] drm/nouveau/pmu: don't print reply values if exec is false
From: Colin Ian King <colin.king at canonical.com>
[ Upstream commit b1d03fc36ec9834465a08c275c8d563e07f6f6bf ]
Currently the uninitialized values in the array reply are printed out
when exec is false and nvkm_pmu_send has not updated the array. Avoid
confusion by only dumping out these values if they have been actually
updated.
Detected by CoverityScan, CID#1271291 ("Uninitialized
2020 Jan 16
0
[PATCH AUTOSEL 4.9 081/251] drm/nouveau/pmu: don't print reply values if exec is false
From: Colin Ian King <colin.king at canonical.com>
[ Upstream commit b1d03fc36ec9834465a08c275c8d563e07f6f6bf ]
Currently the uninitialized values in the array reply are printed out
when exec is false and nvkm_pmu_send has not updated the array. Avoid
confusion by only dumping out these values if they have been actually
updated.
Detected by CoverityScan, CID#1271291 ("Uninitialized
2020 Jan 16
0
[PATCH AUTOSEL 4.4 049/174] drm/nouveau/pmu: don't print reply values if exec is false
From: Colin Ian King <colin.king at canonical.com>
[ Upstream commit b1d03fc36ec9834465a08c275c8d563e07f6f6bf ]
Currently the uninitialized values in the array reply are printed out
when exec is false and nvkm_pmu_send has not updated the array. Avoid
confusion by only dumping out these values if they have been actually
updated.
Detected by CoverityScan, CID#1271291 ("Uninitialized
2015 Nov 14
2
[PATCH v2] pmu: use nvkm_msec instead of do while
I hit this while loop in an error state of the gpu
v2: unlock mutex only if reply == true
Signed-off-by: Karol Herbst <nouveau at karolherbst.de>
---
drm/nouveau/nvkm/subdev/pmu/base.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/drm/nouveau/nvkm/subdev/pmu/base.c b/drm/nouveau/nvkm/subdev/pmu/base.c
index 81a5583..eb248fd 100644
---
2015 Oct 26
0
[PATCH 4/4] nouveau/debugfs: add interface for current load
From: Karol Herbst <git at karolherbst.de>
---
drm/nouveau/include/nvif/device.h | 1 +
drm/nouveau/include/nvkm/subdev/pmu.h | 10 ++++++++++
drm/nouveau/nouveau_debugfs.c | 23 +++++++++++++++++++++++
drm/nouveau/nvkm/subdev/pmu/base.c | 18 ++++++++++++++++++
4 files changed, 52 insertions(+)
diff --git a/drm/nouveau/include/nvif/device.h
2015 Oct 26
0
[PATCH v2 4/4] nouveau/debugfs: add interface for current load
From: Karol Herbst <git at karolherbst.de>
v2: optimize macro and fixed data array type
---
drm/nouveau/include/nvif/device.h | 1 +
drm/nouveau/include/nvkm/subdev/pmu.h | 10 ++++++++++
drm/nouveau/nouveau_debugfs.c | 23 +++++++++++++++++++++++
drm/nouveau/nvkm/subdev/pmu/base.c | 18 ++++++++++++++++++
4 files changed, 52 insertions(+)
diff --git
2015 Oct 26
0
[PATCH v3 4/4] nouveau/debugfs: add interface for current load
From: Karol Herbst <git at karolherbst.de>
v2: optimize macro and fixed data array type
v3: fix bug I added in the last version
---
drm/nouveau/include/nvif/device.h | 1 +
drm/nouveau/include/nvkm/subdev/pmu.h | 10 ++++++++++
drm/nouveau/nouveau_debugfs.c | 23 +++++++++++++++++++++++
drm/nouveau/nvkm/subdev/pmu/base.c | 18 ++++++++++++++++++
4 files changed, 52
2015 Nov 14
0
[PATCH] pmu: use nvkm_msec instead of do while
I hit this while loop in an error state of the gpu
Signed-off-by: Karol Herbst <nouveau at karolherbst.de>
---
drm/nouveau/nvkm/subdev/pmu/base.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/drm/nouveau/nvkm/subdev/pmu/base.c b/drm/nouveau/nvkm/subdev/pmu/base.c
index fafbe2a..398b6a8 100644
--- a/drm/nouveau/nvkm/subdev/pmu/base.c
+++
2015 Nov 15
0
[PATCH v2] pmu: use nvkm_msec instead of do while
> Emil Velikov <emil.l.velikov at gmail.com> hat am 14. November 2015 um 23:44
> geschrieben:
>
> On 14 November 2015 at 19:51, Karol Herbst <nouveau at karolherbst.de> wrote:
> > I hit this while loop in an error state of the gpu
> >
> > v2: unlock mutex only if reply == true
> >
> > Signed-off-by: Karol Herbst <nouveau at
2015 Oct 26
1
[PATCH 4/4] nouveau/debugfs: add interface for current load
On Mon, Oct 26, 2015 at 2:13 PM, Karol Herbst <nouveau at karolherbst.de> wrote:
> From: Karol Herbst <git at karolherbst.de>
>
> ---
> drm/nouveau/include/nvif/device.h | 1 +
> drm/nouveau/include/nvkm/subdev/pmu.h | 10 ++++++++++
> drm/nouveau/nouveau_debugfs.c | 23 +++++++++++++++++++++++
> drm/nouveau/nvkm/subdev/pmu/base.c | 18
2016 Dec 13
0
[PATCH v2 5/15] pmu: add nvkm_pmu_ctor() function
Add a PMU constructor so implementations that extend the nvkm_pmu
structure can have all base members properly initialized.
Signed-off-by: Alexandre Courbot <acourbot at nvidia.com>
---
drm/nouveau/nvkm/subdev/pmu/base.c | 21 +++++++++++++++------
drm/nouveau/nvkm/subdev/pmu/priv.h | 2 ++
2 files changed, 17 insertions(+), 6 deletions(-)
diff --git a/drm/nouveau/nvkm/subdev/pmu/base.c
2017 Jul 05
0
[PATCH] secboot/acr352: reset PMU after secboot
On 07/05/2017 03:35 AM, Karol Herbst wrote:
> This is needed for using Nouveaus PMU image after performing secboot. This will
> be helpfull for Maxwell2 reclocking on boards without externally controlled
> fans like on most laptops or fanless boards.
I get the idea in principal, but have some concerns:
- Does this screw up re-running secboot during channel recovery (ie.
page fault on
2017 Jul 04
2
[PATCH] secboot/acr352: reset PMU after secboot
This is needed for using Nouveaus PMU image after performing secboot. This will
be helpfull for Maxwell2 reclocking on boards without externally controlled
fans like on most laptops or fanless boards.
Signed-off-by: Karol Herbst <karolherbst at gmail.com>
---
drm/nouveau/nvkm/subdev/secboot/acr_r352.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git
2011 Feb 11
1
[PATCH 2/3]: Staging: hv: Use native wait primitives
In preperation for getting rid of the osd layer; change
the code to use native wait interfaces. As part of this,
fixed the buggy implementation in the osd_wait_primitive
where the condition was cleared potentially after the
condition was signalled.
Signed-off-by: K. Y. Srinivasan <kys at microsoft.com>
Signed-off-by: Hank Janssen <hjanssen at microsoft.com>
---
2011 Feb 11
1
[PATCH 2/3]: Staging: hv: Use native wait primitives
In preperation for getting rid of the osd layer; change
the code to use native wait interfaces. As part of this,
fixed the buggy implementation in the osd_wait_primitive
where the condition was cleared potentially after the
condition was signalled.
Signed-off-by: K. Y. Srinivasan <kys at microsoft.com>
Signed-off-by: Hank Janssen <hjanssen at microsoft.com>
---