From: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
To: <John.C.Harrison@Intel.com>, <Intel-GFX@Lists.FreeDesktop.Org>
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/guc: Fix flag query helper function to not modify state
Date: Mon, 28 Feb 2022 16:38:16 -0800 [thread overview]
Message-ID: <94d2176c-4606-2f1a-9df9-4df04de5e96a@intel.com> (raw)
In-Reply-To: <20220217212942.629922-1-John.C.Harrison@Intel.com>
On 2/17/2022 1:29 PM, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> A flag query helper was actually writing to the flags word rather than
> just reading. Fix that. Also update the function's comment as it was
> out of date.
>
> NB: No need for a 'Fixes' tag. The test was only ever used inside a
> BUG_ON during context registration. Rather than asserting that the
> condition was true, it was making the condition true. So, in theory,
> there was no consequence because we should never have hit a BUG_ON
> anyway. Which means the write should always have been a no-op.
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
I seem to have confused patchwork by doing a cut & paste of my r-b from
a different review, so here it is again:
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Daniele
> ---
> drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> index b3a429a92c0d..d9f4218f5ef4 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> @@ -174,11 +174,8 @@ static inline void init_sched_state(struct intel_context *ce)
> __maybe_unused
> static bool sched_state_is_init(struct intel_context *ce)
> {
> - /*
> - * XXX: Kernel contexts can have SCHED_STATE_NO_LOCK_REGISTERED after
> - * suspend.
> - */
> - return !(ce->guc_state.sched_state &=
> + /* Kernel contexts can have SCHED_STATE_REGISTERED after suspend. */
> + return !(ce->guc_state.sched_state &
> ~(SCHED_STATE_BLOCKED_MASK | SCHED_STATE_REGISTERED));
> }
>
prev parent reply other threads:[~2022-03-01 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 21:29 [Intel-gfx] [PATCH] drm/i915/guc: Fix flag query helper function to not modify state John.C.Harrison
2022-02-18 4:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-02-18 15:19 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-02-28 22:45 ` [Intel-gfx] [PATCH] " Ceraolo Spurio, Daniele
2022-03-01 0:38 ` Ceraolo Spurio, Daniele [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=94d2176c-4606-2f1a-9df9-4df04de5e96a@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=DRI-Devel@Lists.FreeDesktop.Org \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
--cc=John.C.Harrison@Intel.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