AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Kuehling <felix.kuehling@amd.com>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"Huang, JinhuiEric" <jinhuieric.huang@amd.com>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/amdkfd: bump KFD version for unified ctx save/restore memory
Date: Tue, 12 Jul 2022 18:57:19 -0400	[thread overview]
Message-ID: <fbaa55f0-b6ae-6dbf-7951-bdb1239017ee@amd.com> (raw)
In-Reply-To: <BL1PR12MB5144B5BB5BA660DCE16E8B86F7869@BL1PR12MB5144.namprd12.prod.outlook.com>

Eric sent out the corresponding user mode patches to the mailing list as 
well. It looks a bit weird, because it looks like they're part of the 
same patch series. But patch 2 and 3 are actually user mode patches. The 
interesting one is patch 3.


Do we still need a link to a user mode patch in this case?


Regards,
   Felix


On 2022-07-12 09:57, Deucher, Alexander wrote:
>
> [AMD Official Use Only - General]
>
>
> Can you please include a link to the proposed userspace in the commit 
> message when you commit this?
>
> Alex
> ------------------------------------------------------------------------
> *From:* amd-gfx <amd-gfx-bounces@lists.freedesktop.org> on behalf of 
> Eric Huang <jinhuieric.huang@amd.com>
> *Sent:* Monday, July 11, 2022 2:41 PM
> *To:* amd-gfx@lists.freedesktop.org <amd-gfx@lists.freedesktop.org>
> *Cc:* Huang, JinHuiEric <JinHuiEric.Huang@amd.com>; Kuehling, Felix 
> <Felix.Kuehling@amd.com>
> *Subject:* [PATCH] drm/amdkfd: bump KFD version for unified ctx 
> save/restore memory
> To expose unified memory for ctx save/resotre area feature
> availablity to libhsakmt.
>
> Signed-off-by: Eric Huang <jinhuieric.huang@amd.com>
> ---
>  include/uapi/linux/kfd_ioctl.h | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/uapi/linux/kfd_ioctl.h 
> b/include/uapi/linux/kfd_ioctl.h
> index 7a423855a86e..afd8ff29c74f 100644
> --- a/include/uapi/linux/kfd_ioctl.h
> +++ b/include/uapi/linux/kfd_ioctl.h
> @@ -36,9 +36,10 @@
>   * - 1.8 - CRIU - Support for SDMA transfers with GTT BOs
>   * - 1.9 - Add available memory ioctl
>   * - 1.10 - Add SMI profiler event log
> + * - 1.11 - Add unified memory for ctx save/restore area
>   */
>  #define KFD_IOCTL_MAJOR_VERSION 1
> -#define KFD_IOCTL_MINOR_VERSION 10
> +#define KFD_IOCTL_MINOR_VERSION 11
>
>  struct kfd_ioctl_get_version_args {
>          __u32 major_version;    /* from KFD */
> -- 
> 2.25.1
>

  parent reply	other threads:[~2022-07-12 22:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 18:41 [PATCH] drm/amdkfd: bump KFD version for unified ctx save/restore memory Eric Huang
2022-07-11 18:41 ` [PATCH 2/3] libhsakmt: add new flag for svm Eric Huang
2022-07-11 18:41 ` [PATCH 3/3] libhsakmt: allocate unified memory for ctx save restore area Eric Huang
2022-07-11 18:50 ` [PATCH] drm/amdkfd: bump KFD version for unified ctx save/restore memory Felix Kuehling
2022-07-12 13:57 ` Deucher, Alexander
2022-07-12 14:30   ` Eric Huang
2022-07-12 22:57   ` Felix Kuehling [this message]
2022-07-13  1:47     ` Alex Deucher

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=fbaa55f0-b6ae-6dbf-7951-bdb1239017ee@amd.com \
    --to=felix.kuehling@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=jinhuieric.huang@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