From: kernel test robot <lkp@intel.com>
To: Lukas Zapolskas <lukas.zapolskas@arm.com>,
Boris Brezillon <bbrezillon@kernel.org>,
Liviu Dudau <liviu.dudau@arm.com>,
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>
Cc: oe-kbuild-all@lists.linux.dev, nd@arm.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Lukas Zapolskas <lukas.zapolskas@arm.com>,
Ketil Johnsen <ketil.johnsen@arm.com>
Subject: Re: [PATCH v1 5/5] drm/panthor: Use GROUP_GET_STATE to provide group and queue errors
Date: Tue, 16 Dec 2025 17:29:54 +0800 [thread overview]
Message-ID: <202512161757.nqIBsB07-lkp@intel.com> (raw)
In-Reply-To: <20251215115457.2137485-6-lukas.zapolskas@arm.com>
Hi Lukas,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on next-20251216]
[cannot apply to linus/master v6.19-rc1]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Lukas-Zapolskas/drm-panthor-Implement-CS_FAULT-propagation-to-userspace/20251215-195920
base: https://gitlab.freedesktop.org/drm/misc/kernel.git drm-misc-next
patch link: https://lore.kernel.org/r/20251215115457.2137485-6-lukas.zapolskas%40arm.com
patch subject: [PATCH v1 5/5] drm/panthor: Use GROUP_GET_STATE to provide group and queue errors
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20251216/202512161757.nqIBsB07-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251216/202512161757.nqIBsB07-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202512161757.nqIBsB07-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/panthor/panthor_sched.c: In function 'panthor_group_get_state':
>> drivers/gpu/drm/panthor/panthor_sched.c:3968:42: error: 'struct panthor_group' has no member named 'fault'
3968 | get_state->exception_type = group->fault.exception_type;
| ^~
drivers/gpu/drm/panthor/panthor_sched.c:3969:39: error: 'struct panthor_group' has no member named 'fault'
3969 | get_state->access_type = group->fault.access_type;
| ^~
drivers/gpu/drm/panthor/panthor_sched.c:3970:37: error: 'struct panthor_group' has no member named 'fault'
3970 | get_state->source_id = group->fault.source_id;
| ^~
drivers/gpu/drm/panthor/panthor_sched.c:3971:41: error: 'struct panthor_group' has no member named 'fault'
3971 | get_state->valid_address = group->fault.valid_address;
| ^~
drivers/gpu/drm/panthor/panthor_sched.c:3972:35: error: 'struct panthor_group' has no member named 'fault'
3972 | get_state->address = group->fault.address;
| ^~
vim +3968 drivers/gpu/drm/panthor/panthor_sched.c
3938
3939 int panthor_group_get_state(struct panthor_file *pfile,
3940 struct drm_panthor_group_get_state *get_state,
3941 struct drm_panthor_queue_event *events, u32 count)
3942 {
3943 struct panthor_group_pool *gpool = pfile->groups;
3944 struct panthor_device *ptdev = pfile->ptdev;
3945 struct panthor_scheduler *sched = ptdev->scheduler;
3946 struct panthor_group *group = NULL;
3947 u32 fault_count;
3948
3949 group = group_from_handle(gpool, get_state->group_handle);
3950 if (!group)
3951 return -EINVAL;
3952
3953 guard(mutex)(&sched->lock);
3954
3955 if (group->timedout)
3956 get_state->state |= DRM_PANTHOR_GROUP_STATE_TIMEDOUT;
3957 if (group->fatal_queues) {
3958 get_state->state |= DRM_PANTHOR_GROUP_STATE_FATAL_FAULT;
3959 get_state->fatal_queues = group->fatal_queues;
3960 }
3961 if (group->innocent)
3962 get_state->state |= DRM_PANTHOR_GROUP_STATE_INNOCENT;
3963 if (group->fault_queues) {
3964 get_state->state |= DRM_PANTHOR_GROUP_STATE_QUEUE_FAULT;
3965 get_state->fault_queues = group->fault_queues;
3966 }
3967
> 3968 get_state->exception_type = group->fault.exception_type;
3969 get_state->access_type = group->fault.access_type;
3970 get_state->source_id = group->fault.source_id;
3971 get_state->valid_address = group->fault.valid_address;
3972 get_state->address = group->fault.address;
3973
3974 fault_count = panthor_group_count_faults(sched, group);
3975
3976 if (!count && !events) {
3977 get_state->faults.count = fault_count;
3978 get_state->faults.stride = sizeof(struct drm_panthor_queue_event);
3979 goto exit;
3980 }
3981
3982 panthor_group_get_faults(sched, group, events, min(get_state->faults.count, count));
3983
3984 exit:
3985 group_put(group);
3986 return 0;
3987 }
3988
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-12-16 9:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 11:54 [PATCH v1 0/5] drm/panthor: Implement fault information propagation Lukas Zapolskas
2025-12-15 11:54 ` [PATCH v1 1/5] drm/panthor: Implement CS_FAULT propagation to userspace Lukas Zapolskas
2025-12-15 12:03 ` Boris Brezillon
2025-12-15 11:54 ` [PATCH v1 2/5] drm/panthor: Store queue fault and fatal information Lukas Zapolskas
2025-12-15 12:11 ` Boris Brezillon
2025-12-17 11:37 ` Steven Price
2025-12-15 11:54 ` [PATCH v1 3/5] drm/panthor: Track VM faults Lukas Zapolskas
2025-12-15 12:37 ` Boris Brezillon
2025-12-15 11:54 ` [PATCH v1 4/5] drm/panthor: Propagate VM-level faults to groups Lukas Zapolskas
2025-12-15 12:41 ` Boris Brezillon
2025-12-15 12:46 ` Boris Brezillon
2025-12-15 11:54 ` [PATCH v1 5/5] drm/panthor: Use GROUP_GET_STATE to provide group and queue errors Lukas Zapolskas
2025-12-15 17:31 ` Boris Brezillon
2025-12-16 5:45 ` kernel test robot
2025-12-16 7:52 ` Marcin Ślusarz
2025-12-16 9:29 ` kernel test robot [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=202512161757.nqIBsB07-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=bbrezillon@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ketil.johnsen@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lukas.zapolskas@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nd@arm.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).