All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Kuehling <felix.kuehling@amd.com>
To: Philip Yang <Philip.Yang@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH v5 1/11] drm/amdkfd: Add KFD SMI event IDs and triggers
Date: Thu, 30 Jun 2022 10:46:16 -0400	[thread overview]
Message-ID: <f175e926-ac60-e1e6-3492-44b5a596ba30@amd.com> (raw)
In-Reply-To: <20220628145020.26925-2-Philip.Yang@amd.com>

Am 2022-06-28 um 10:50 schrieb Philip Yang:
> Define new system management interface event IDs for migration, GPU
> recoverable page fault, user queues eviction, restore and unmap from
> GPU events and corresponding event triggers, those will be implemented
> in the following patches.
>
> Signed-off-by: Philip Yang <Philip.Yang@amd.com>

Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>


> ---
>   include/uapi/linux/kfd_ioctl.h | 37 ++++++++++++++++++++++++++++++++++
>   1 file changed, 37 insertions(+)
>
> diff --git a/include/uapi/linux/kfd_ioctl.h b/include/uapi/linux/kfd_ioctl.h
> index c648ed7c5ff1..f239e260796b 100644
> --- a/include/uapi/linux/kfd_ioctl.h
> +++ b/include/uapi/linux/kfd_ioctl.h
> @@ -468,6 +468,43 @@ enum kfd_smi_event {
>   	KFD_SMI_EVENT_THERMAL_THROTTLE = 2,
>   	KFD_SMI_EVENT_GPU_PRE_RESET = 3,
>   	KFD_SMI_EVENT_GPU_POST_RESET = 4,
> +	KFD_SMI_EVENT_MIGRATE_START = 5,
> +	KFD_SMI_EVENT_MIGRATE_END = 6,
> +	KFD_SMI_EVENT_PAGE_FAULT_START = 7,
> +	KFD_SMI_EVENT_PAGE_FAULT_END = 8,
> +	KFD_SMI_EVENT_QUEUE_EVICTION = 9,
> +	KFD_SMI_EVENT_QUEUE_RESTORE = 10,
> +	KFD_SMI_EVENT_UNMAP_FROM_GPU = 11,
> +
> +	/*
> +	 * max event number, as a flag bit to get events from all processes,
> +	 * this requires super user permission, otherwise will not be able to
> +	 * receive event from any process. Without this flag to receive events
> +	 * from same process.
> +	 */
> +	KFD_SMI_EVENT_ALL_PROCESS = 64
> +};
> +
> +enum KFD_MIGRATE_TRIGGERS {
> +	KFD_MIGRATE_TRIGGER_PREFETCH,
> +	KFD_MIGRATE_TRIGGER_PAGEFAULT_GPU,
> +	KFD_MIGRATE_TRIGGER_PAGEFAULT_CPU,
> +	KFD_MIGRATE_TRIGGER_TTM_EVICTION
> +};
> +
> +enum KFD_QUEUE_EVICTION_TRIGGERS {
> +	KFD_QUEUE_EVICTION_TRIGGER_SVM,
> +	KFD_QUEUE_EVICTION_TRIGGER_USERPTR,
> +	KFD_QUEUE_EVICTION_TRIGGER_TTM,
> +	KFD_QUEUE_EVICTION_TRIGGER_SUSPEND,
> +	KFD_QUEUE_EVICTION_CRIU_CHECKPOINT,
> +	KFD_QUEUE_EVICTION_CRIU_RESTORE
> +};
> +
> +enum KFD_SVM_UNMAP_TRIGGERS {
> +	KFD_SVM_UNMAP_TRIGGER_MMU_NOTIFY,
> +	KFD_SVM_UNMAP_TRIGGER_MMU_NOTIFY_MIGRATE,
> +	KFD_SVM_UNMAP_TRIGGER_UNMAP_FROM_CPU
>   };
>   
>   #define KFD_SMI_EVENT_MASK_FROM_INDEX(i) (1ULL << ((i) - 1))

  reply	other threads:[~2022-06-30 14:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 14:50 [PATCH v5 0/11] HMM profiler interface Philip Yang
2022-06-28 14:50 ` [PATCH v5 1/11] drm/amdkfd: Add KFD SMI event IDs and triggers Philip Yang
2022-06-30 14:46   ` Felix Kuehling [this message]
2022-06-28 14:50 ` [PATCH v5 2/11] drm/amdkfd: Enable per process SMI event Philip Yang
2022-06-28 14:50 ` [PATCH v5 3/11] drm/amdkfd: Add GPU recoverable fault " Philip Yang
2022-06-30 14:19   ` Felix Kuehling
2022-06-30 14:53     ` philip yang
2022-06-28 14:50 ` [PATCH v5 4/11] drm/amdkfd: Add migration " Philip Yang
2022-06-30 14:29   ` Felix Kuehling
2022-06-28 14:50 ` [PATCH v5 5/11] drm/amdkfd: Add user queue eviction restore " Philip Yang
2022-06-30 14:36   ` Felix Kuehling
2022-06-28 14:50 ` [PATCH v5 6/11] drm/amdkfd: Add unmap from GPU " Philip Yang
2022-06-30 14:39   ` Felix Kuehling
2022-06-28 14:50 ` [PATCH v5 7/11] drm/amdkfd: Asynchronously free smi_client Philip Yang
2022-06-30 14:45   ` Felix Kuehling
2022-06-28 14:50 ` [PATCH v5 8/11] drm/amdkfd: Bump KFD API version for SMI profiling event Philip Yang
2022-06-30 14:45   ` Felix Kuehling
2022-06-28 14:50 ` [PATCH 9/11] libhsakmt: hsaKmtGetNodeProperties add gpu_id Philip Yang
2022-06-28 14:50 ` [PATCH 10/11] libhsakmt: add open SMI event handle Philip Yang
2022-06-28 14:50 ` [PATCH 11/11] ROCR-Runtime Basic SVM profiler Philip Yang

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=f175e926-ac60-e1e6-3492-44b5a596ba30@amd.com \
    --to=felix.kuehling@amd.com \
    --cc=Philip.Yang@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.