From: "Kuehling, Felix" <Felix.Kuehling@amd.com>
To: Oded Gabbay <oded.gabbay@gmail.com>,
"Cornwall, Jay" <Jay.Cornwall@amd.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ldv@altlinux.org" <ldv@altlinux.org>
Subject: Re: [PATCH 2/2] uapi: fix more linux/kfd_ioctl.h userspace compilation errors
Date: Fri, 2 Nov 2018 23:14:13 +0000 [thread overview]
Message-ID: <653fdf2e-cecb-2016-c934-607672ec22a5@amd.com> (raw)
In-Reply-To: <20181101110328.GB20538@altlinux.org>
On 2018-11-01 7:03 a.m., Dmitry V. Levin wrote:
> Consistently use types provided by <linux/types.h> via <drm/drm.h>
> to fix struct kfd_ioctl_get_queue_wave_state_args userspace compilation errors.
>
> Fixes: 5df099e8bc83f ("drm/amdkfd: Add wavefront context save state retrieval ioctl")
> Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
Thank you for catching this, and sorry for messing it up incrementally.
Our internal branch is already fixed, but I must have missed this when I
cherry-picked older patches.
The series is Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
I also applied it to our amd-staging-drm-next branch.
Regards,
Felix
> ---
> include/uapi/linux/kfd_ioctl.h | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/include/uapi/linux/kfd_ioctl.h b/include/uapi/linux/kfd_ioctl.h
> index dae897f38e59..b01eb502d49c 100644
> --- a/include/uapi/linux/kfd_ioctl.h
> +++ b/include/uapi/linux/kfd_ioctl.h
> @@ -83,11 +83,11 @@ struct kfd_ioctl_set_cu_mask_args {
> };
>
> struct kfd_ioctl_get_queue_wave_state_args {
> - uint64_t ctl_stack_address; /* to KFD */
> - uint32_t ctl_stack_used_size; /* from KFD */
> - uint32_t save_area_used_size; /* from KFD */
> - uint32_t queue_id; /* to KFD */
> - uint32_t pad;
> + __u64 ctl_stack_address; /* to KFD */
> + __u32 ctl_stack_used_size; /* from KFD */
> + __u32 save_area_used_size; /* from KFD */
> + __u32 queue_id; /* to KFD */
> + __u32 pad;
> };
>
> /* For kfd_ioctl_set_memory_policy_args.default_policy and alternate_policy */
prev parent reply other threads:[~2018-11-02 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 11:03 [PATCH 2/2] uapi: fix more linux/kfd_ioctl.h userspace compilation errors Dmitry V. Levin
2018-11-02 23:14 ` Kuehling, Felix [this message]
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=653fdf2e-cecb-2016-c934-607672ec22a5@amd.com \
--to=felix.kuehling@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Jay.Cornwall@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oded.gabbay@gmail.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