mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lyude@redhat.com
To: Mohamed Ahmed <mohamedahmedegypt2001@gmail.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Danilo Krummrich <dakr@kernel.org>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard	 <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie	 <airlied@gmail.com>,
	Simona Vetter <simona@ffwll.ch>,
	Mary Guillemard	 <mary@mary.zone>,
	Milos Tijanic <mtijanic@nvidia.com>,
		nouveau@lists.freedesktop.org
Subject: Re: [PATCH 3/6] drm/nouveau: add GSP hwmon support
Date: Tue, 21 Jul 2026 16:36:36 -0400	[thread overview]
Message-ID: <37f6625f23cc0c041d5d079dbca683d47fe9b4fa.camel@redhat.com> (raw)
In-Reply-To: <CAA+WOBuLgkKy_BAgEWgN7jgxDrJYchO1D+B44u6VVMPsGJ-AEA@mail.gmail.com>

On Tue, 2026-07-21 at 23:36 +0400, Mohamed Ahmed wrote:
> It can work but it's strictly worse than this. nvif_msec() does busy
> looping, which would be overkill for this as it would be doing a lot
> more reading for something that changes at most once per 500ms poll
> cycle, and it keeps the CPU fully occupied with every read. It also
> couples us to GPU timing while the main thing we are waiting here on
> is whether the GSP's buffer writes are now visible in RAM so GPU side
> time doesn't offer us anything. I actually wasn't sure at first how
> to
> properly wait and did go over all the possible timing alternatives
> and
> jiffies looked to be the best here.
> 
> That said, to address what Milos mentioned (the weirdness of files
> being -ENODATA), I am going to have to move this into nvkm/rusd,
> inside r570_rusd_supported()/r570_rusd_read() which doesn't have any
> other alternative available to do a similar style waiting loop.

Gotcha, sgtm


  reply	other threads:[~2026-07-21 20:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 21:14 [PATCH 0/6] drm/nouveau: GSP telemetry via RUSD, and fdinfo telemetry exposure Mohamed Ahmed
2026-07-14 21:14 ` [PATCH 1/6] drm/nouveau/gsp: vendor the RUSD header Mohamed Ahmed
2026-07-14 21:14 ` [PATCH 2/6] drm/nouveau/gsp: add RUSD telemetry support Mohamed Ahmed
2026-07-21 18:23   ` lyude
2026-07-14 21:14 ` [PATCH 3/6] drm/nouveau: add GSP hwmon support Mohamed Ahmed
2026-07-21 18:36   ` lyude
2026-07-21 19:36     ` Mohamed Ahmed
2026-07-21 20:36       ` lyude [this message]
2026-07-14 21:14 ` [PATCH 4/6] drm/nouveau: expose RUSD telemetry via sysfs Mohamed Ahmed
2026-07-14 21:14 ` [PATCH 5/6] drm/nouveau: expose global VRAM size and usage " Mohamed Ahmed
2026-07-14 21:14 ` [PATCH 6/6] drm/nouveau: expose per-client GPU usage via fdinfo Mohamed Ahmed
2026-07-20 22:16 ` [PATCH 0/6] drm/nouveau: GSP telemetry via RUSD, and fdinfo telemetry exposure lyude
2026-07-21 10:39 ` Milos Tijanic
2026-07-21 15:11   ` Mohamed Ahmed
2026-07-21 20:40 ` lyude
2026-07-21 20:46   ` Mohamed Ahmed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=37f6625f23cc0c041d5d079dbca683d47fe9b4fa.camel@redhat.com \
    --to=lyude@redhat.com \
    --cc=airlied@gmail.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mary@mary.zone \
    --cc=mohamedahmedegypt2001@gmail.com \
    --cc=mripard@kernel.org \
    --cc=mtijanic@nvidia.com \
    --cc=nouveau@lists.freedesktop.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®