Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Helen Koike <koike@igalia.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Rob Clark <robdclark@gmail.com>,
	Abhinav Kumar <quic_abhinavk@quicinc.com>,
	Dmitry Baryshkov <lumag@kernel.org>, Sean Paul <sean@poorly.run>,
	Marijn Suijten <marijn.suijten@somainline.org>,
	Helen Koike <helen.fornazier@gmail.com>,
	Vignesh Raman <vignesh.raman@collabora.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: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: ci: skip msm_mapping@shadow on SM8350
Date: Fri, 16 May 2025 10:48:09 -0300	[thread overview]
Message-ID: <80673b87-792b-49f9-a68e-657c16a9b04a@igalia.com> (raw)
In-Reply-To: <20250513-msm-ci-fixes-v1-1-baba185529a2@oss.qualcomm.com>



On 5/13/25 15:49, Dmitry Baryshkov wrote:
> The msm_mapping@shadow test fails on SM8350, which means that the write
> might get through (hopefully not though). Disable the test completely
> for now until we can fix the issue.
> 
> Link: https://gitlab.freedesktop.org/drm/msm/-/issues/77
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>

Acked-by: Helen Koike <koike@igalia.com>

Thanks
Helen

> ---
>   drivers/gpu/drm/ci/xfails/msm-sm8350-hdk-skips.txt | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/drivers/gpu/drm/ci/xfails/msm-sm8350-hdk-skips.txt b/drivers/gpu/drm/ci/xfails/msm-sm8350-hdk-skips.txt
> index 9450f2a002fd7e68f0f674ac6ac84aeebf28347f..a8b535abc8ef0d996d0c73ece1c7a9622250928e 100644
> --- a/drivers/gpu/drm/ci/xfails/msm-sm8350-hdk-skips.txt
> +++ b/drivers/gpu/drm/ci/xfails/msm-sm8350-hdk-skips.txt
> @@ -210,3 +210,8 @@ msm/msm_mapping@ring
>   # [  229.752499] CPU features: 0x18,00000017,00200928,4200720b
>   # [  229.758095] Memory Limit: none
>   # [  229.761291] ---[ end Kernel panic - not syncing: softlockup: hung tasks ]---
> +
> +# Protection doesn't seem to be enforced, don't perform write which might get through
> +# https://gitlab.freedesktop.org/drm/msm/-/issues/77
> +msm/msm_mapping@shadow
> +
> 
> ---
> base-commit: 8f5264d302e803e7ef82a61f9632a0d2ef67413f
> change-id: 20250513-msm-ci-fixes-3e7ce259d1d9
> 
> Best regards,


      reply	other threads:[~2025-05-16 13:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 18:49 [PATCH] drm: ci: skip msm_mapping@shadow on SM8350 Dmitry Baryshkov
2025-05-16 13:48 ` Helen Koike [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=80673b87-792b-49f9-a68e-657c16a9b04a@igalia.com \
    --to=koike@igalia.com \
    --cc=airlied@gmail.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=helen.fornazier@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=marijn.suijten@somainline.org \
    --cc=mripard@kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=sean@poorly.run \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    --cc=vignesh.raman@collabora.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