From: Philip Yang <Philip.Yang@amd.com>
To: <amd-gfx@lists.freedesktop.org>
Cc: <Felix.Kuehling@amd.com>, <jamesz@amd.com>,
Philip Yang <Philip.Yang@amd.com>
Subject: [PATCH v3 0/4] Improve SVM migrate event report
Date: Tue, 27 Aug 2024 13:10:21 -0400 [thread overview]
Message-ID: <20240827171027.12910-1-Philip.Yang@amd.com> (raw)
1. Document how to use SMI system management interface to receive SVM
events, define string format macro for user mode.
2. Increase the event kfifo size, so less chance to drop event.
3. Output migrate end event with error code if migration failed.
4. Report dropped event count if fifo is full.
v3:
Simplify event drop count handling (James Zhu)
Philip Yang (4):
drm/amdkfd: Document and define SVM events message macro
drm/amdkfd: Output migrate end event if migrate failed
drm/amdkfd: Increase SMI event fifo size
drm/amdkfd: SMI report dropped event count
drivers/gpu/drm/amd/amdkfd/kfd_migrate.c | 14 ++-
drivers/gpu/drm/amd/amdkfd/kfd_smi_events.c | 79 +++++++++------
drivers/gpu/drm/amd/amdkfd/kfd_smi_events.h | 3 +-
include/uapi/linux/kfd_ioctl.h | 107 +++++++++++++++++---
4 files changed, 150 insertions(+), 53 deletions(-)
--
2.43.2
next reply other threads:[~2024-08-27 17:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 17:10 Philip Yang [this message]
2024-08-27 17:10 ` [PATCH v3 1/4] drm/amdkfd: Document and define SVM events message macro Philip Yang
2024-08-27 17:10 ` [PATCH v3 2/4] drm/amdkfd: Output migrate end event if migrate failed Philip Yang
2024-08-27 17:10 ` [PATCH v3 3/4] drm/amdkfd: Increase SMI event fifo size Philip Yang
2024-08-27 17:10 ` [PATCH v3 4/4] drm/amdkfd: SMI report dropped event count Philip Yang
2024-08-27 17:10 ` [PATCH] " Philip Yang
2024-08-27 20:55 ` [PATCH v3 0/4] Improve SVM migrate event report James Zhu
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=20240827171027.12910-1-Philip.Yang@amd.com \
--to=philip.yang@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=jamesz@amd.com \
/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