From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
airlied@linux.ie, intel-gfx@lists.freedesktop.org,
Abaci Robot <abaci@linux.alibaba.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
sumit.semwal@linaro.org, linaro-mm-sig@lists.linaro.org,
christian.koenig@amd.com, linux-media@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: fix unsigned integer to signed assignment
Date: Wed, 16 Feb 2022 12:33:30 +0200 [thread overview]
Message-ID: <87leyb3xtx.fsf@intel.com> (raw)
In-Reply-To: <9a7b0e48-b00f-be11-7fc7-bc26719cbc1e@linux.intel.com>
On Wed, 16 Feb 2022, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote:
> On 16/02/2022 09:19, Ville Syrjälä wrote:
>> On Wed, Feb 16, 2022 at 11:02:06AM +0200, Jani Nikula wrote:
>>> On Wed, 16 Feb 2022, Jiapeng Chong <jiapeng.chong@linux.alibaba.com> wrote:
>>>> Eliminate the follow smatch warning:
>>>>
>>>> drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c:4640
>>>> guc_create_virtual() warn: assigning (-2) to unsigned variable
>>>> 've->base.instance'.
>>>>
>>>> drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c:4641
>>>> guc_create_virtual() warn: assigning (-2) to unsigned variable
>>>> 've->base.uabi_instance'.
>>>>
>>>> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
>>>> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
>>>
>>> The report seems to be valid, but I don't think this is the fix.
>>>
>>> Where do we even check for invalid instance/uabi_instance in code?
>>
>> The whole thing seems rather poorly documented as there's a matching
>> uabi struct with __u16's and the negative values are defined right
>> there in the uapi header as well.
>
> Negative ones are exception values to be used in conjunction with the virtual engine uapi (see "DOC: Virtual Engine uAPI" and also comment next to I915_CONTEXT_PARAM_ENGINES).
>
> AFAIK assigning negative int to unsigned int is defined and fine.
>
> Compiler does warn on comparisons which is why we have:
>
> ./gem/i915_gem_busy.c: if (id == (u16)I915_ENGINE_CLASS_INVALID)
> ./gem/i915_gem_busy.c: if (id == (u16)I915_ENGINE_CLASS_INVALID)
> ./gem/i915_gem_context.c: if (ci.engine_class == (u16)I915_ENGINE_CLASS_INVALID &&
> ./gem/i915_gem_context.c: ci.engine_instance == (u16)I915_ENGINE_CLASS_INVALID_NONE)
>
> So I think no action needed here.
We never check instance or uabi_instance members against
I915_ENGINE_CLASS_INVALID_VIRTUAL anywhere.
BR,
Jani.
>
> Regards,
>
> Tvrtko
>
>>>
>>> BR,
>>> Jani.
>>>
>>>
>>>> ---
>>>> drivers/gpu/drm/i915/gt/intel_engine_types.h | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_types.h b/drivers/gpu/drm/i915/gt/intel_engine_types.h
>>>> index 36365bdbe1ee..dc7cc06c68e7 100644
>>>> --- a/drivers/gpu/drm/i915/gt/intel_engine_types.h
>>>> +++ b/drivers/gpu/drm/i915/gt/intel_engine_types.h
>>>> @@ -328,10 +328,10 @@ struct intel_engine_cs {
>>>> intel_engine_mask_t logical_mask;
>>>>
>>>> u8 class;
>>>> - u8 instance;
>>>> + s8 instance;
>>>>
>>>> u16 uabi_class;
>>>> - u16 uabi_instance;
>>>> + s16 uabi_instance;
>>>>
>>>> u32 uabi_capabilities;
>>>> u32 context_size;
>>>
>>> --
>>> Jani Nikula, Intel Open Source Graphics Center
>>
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
airlied@linux.ie, intel-gfx@lists.freedesktop.org,
Abaci Robot <abaci@linux.alibaba.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
sumit.semwal@linaro.org, linaro-mm-sig@lists.linaro.org,
rodrigo.vivi@intel.com, christian.koenig@amd.com,
linux-media@vger.kernel.org
Subject: Re: [PATCH] drm/i915/gt: fix unsigned integer to signed assignment
Date: Wed, 16 Feb 2022 12:33:30 +0200 [thread overview]
Message-ID: <87leyb3xtx.fsf@intel.com> (raw)
In-Reply-To: <9a7b0e48-b00f-be11-7fc7-bc26719cbc1e@linux.intel.com>
On Wed, 16 Feb 2022, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote:
> On 16/02/2022 09:19, Ville Syrjälä wrote:
>> On Wed, Feb 16, 2022 at 11:02:06AM +0200, Jani Nikula wrote:
>>> On Wed, 16 Feb 2022, Jiapeng Chong <jiapeng.chong@linux.alibaba.com> wrote:
>>>> Eliminate the follow smatch warning:
>>>>
>>>> drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c:4640
>>>> guc_create_virtual() warn: assigning (-2) to unsigned variable
>>>> 've->base.instance'.
>>>>
>>>> drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c:4641
>>>> guc_create_virtual() warn: assigning (-2) to unsigned variable
>>>> 've->base.uabi_instance'.
>>>>
>>>> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
>>>> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
>>>
>>> The report seems to be valid, but I don't think this is the fix.
>>>
>>> Where do we even check for invalid instance/uabi_instance in code?
>>
>> The whole thing seems rather poorly documented as there's a matching
>> uabi struct with __u16's and the negative values are defined right
>> there in the uapi header as well.
>
> Negative ones are exception values to be used in conjunction with the virtual engine uapi (see "DOC: Virtual Engine uAPI" and also comment next to I915_CONTEXT_PARAM_ENGINES).
>
> AFAIK assigning negative int to unsigned int is defined and fine.
>
> Compiler does warn on comparisons which is why we have:
>
> ./gem/i915_gem_busy.c: if (id == (u16)I915_ENGINE_CLASS_INVALID)
> ./gem/i915_gem_busy.c: if (id == (u16)I915_ENGINE_CLASS_INVALID)
> ./gem/i915_gem_context.c: if (ci.engine_class == (u16)I915_ENGINE_CLASS_INVALID &&
> ./gem/i915_gem_context.c: ci.engine_instance == (u16)I915_ENGINE_CLASS_INVALID_NONE)
>
> So I think no action needed here.
We never check instance or uabi_instance members against
I915_ENGINE_CLASS_INVALID_VIRTUAL anywhere.
BR,
Jani.
>
> Regards,
>
> Tvrtko
>
>>>
>>> BR,
>>> Jani.
>>>
>>>
>>>> ---
>>>> drivers/gpu/drm/i915/gt/intel_engine_types.h | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_types.h b/drivers/gpu/drm/i915/gt/intel_engine_types.h
>>>> index 36365bdbe1ee..dc7cc06c68e7 100644
>>>> --- a/drivers/gpu/drm/i915/gt/intel_engine_types.h
>>>> +++ b/drivers/gpu/drm/i915/gt/intel_engine_types.h
>>>> @@ -328,10 +328,10 @@ struct intel_engine_cs {
>>>> intel_engine_mask_t logical_mask;
>>>>
>>>> u8 class;
>>>> - u8 instance;
>>>> + s8 instance;
>>>>
>>>> u16 uabi_class;
>>>> - u16 uabi_instance;
>>>> + s16 uabi_instance;
>>>>
>>>> u32 uabi_capabilities;
>>>> u32 context_size;
>>>
>>> --
>>> Jani Nikula, Intel Open Source Graphics Center
>>
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
airlied@linux.ie, intel-gfx@lists.freedesktop.org,
Abaci Robot <abaci@linux.alibaba.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
christian.koenig@amd.com, linaro-mm-sig@lists.linaro.org,
rodrigo.vivi@intel.com, sumit.semwal@linaro.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH] drm/i915/gt: fix unsigned integer to signed assignment
Date: Wed, 16 Feb 2022 12:33:30 +0200 [thread overview]
Message-ID: <87leyb3xtx.fsf@intel.com> (raw)
In-Reply-To: <9a7b0e48-b00f-be11-7fc7-bc26719cbc1e@linux.intel.com>
On Wed, 16 Feb 2022, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote:
> On 16/02/2022 09:19, Ville Syrjälä wrote:
>> On Wed, Feb 16, 2022 at 11:02:06AM +0200, Jani Nikula wrote:
>>> On Wed, 16 Feb 2022, Jiapeng Chong <jiapeng.chong@linux.alibaba.com> wrote:
>>>> Eliminate the follow smatch warning:
>>>>
>>>> drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c:4640
>>>> guc_create_virtual() warn: assigning (-2) to unsigned variable
>>>> 've->base.instance'.
>>>>
>>>> drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c:4641
>>>> guc_create_virtual() warn: assigning (-2) to unsigned variable
>>>> 've->base.uabi_instance'.
>>>>
>>>> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
>>>> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
>>>
>>> The report seems to be valid, but I don't think this is the fix.
>>>
>>> Where do we even check for invalid instance/uabi_instance in code?
>>
>> The whole thing seems rather poorly documented as there's a matching
>> uabi struct with __u16's and the negative values are defined right
>> there in the uapi header as well.
>
> Negative ones are exception values to be used in conjunction with the virtual engine uapi (see "DOC: Virtual Engine uAPI" and also comment next to I915_CONTEXT_PARAM_ENGINES).
>
> AFAIK assigning negative int to unsigned int is defined and fine.
>
> Compiler does warn on comparisons which is why we have:
>
> ./gem/i915_gem_busy.c: if (id == (u16)I915_ENGINE_CLASS_INVALID)
> ./gem/i915_gem_busy.c: if (id == (u16)I915_ENGINE_CLASS_INVALID)
> ./gem/i915_gem_context.c: if (ci.engine_class == (u16)I915_ENGINE_CLASS_INVALID &&
> ./gem/i915_gem_context.c: ci.engine_instance == (u16)I915_ENGINE_CLASS_INVALID_NONE)
>
> So I think no action needed here.
We never check instance or uabi_instance members against
I915_ENGINE_CLASS_INVALID_VIRTUAL anywhere.
BR,
Jani.
>
> Regards,
>
> Tvrtko
>
>>>
>>> BR,
>>> Jani.
>>>
>>>
>>>> ---
>>>> drivers/gpu/drm/i915/gt/intel_engine_types.h | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_types.h b/drivers/gpu/drm/i915/gt/intel_engine_types.h
>>>> index 36365bdbe1ee..dc7cc06c68e7 100644
>>>> --- a/drivers/gpu/drm/i915/gt/intel_engine_types.h
>>>> +++ b/drivers/gpu/drm/i915/gt/intel_engine_types.h
>>>> @@ -328,10 +328,10 @@ struct intel_engine_cs {
>>>> intel_engine_mask_t logical_mask;
>>>>
>>>> u8 class;
>>>> - u8 instance;
>>>> + s8 instance;
>>>>
>>>> u16 uabi_class;
>>>> - u16 uabi_instance;
>>>> + s16 uabi_instance;
>>>>
>>>> u32 uabi_capabilities;
>>>> u32 context_size;
>>>
>>> --
>>> Jani Nikula, Intel Open Source Graphics Center
>>
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-02-16 10:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 8:38 [Intel-gfx] [PATCH] drm/i915/gt: fix unsigned integer to signed assignment Jiapeng Chong
2022-02-16 8:38 ` Jiapeng Chong
2022-02-16 8:38 ` Jiapeng Chong
2022-02-16 9:02 ` [Intel-gfx] " Jani Nikula
2022-02-16 9:02 ` Jani Nikula
2022-02-16 9:02 ` Jani Nikula
2022-02-16 9:19 ` [Intel-gfx] " Ville Syrjälä
2022-02-16 9:19 ` Ville Syrjälä
2022-02-16 9:19 ` Ville Syrjälä
2022-02-16 9:57 ` [Intel-gfx] " Tvrtko Ursulin
2022-02-16 9:57 ` Tvrtko Ursulin
2022-02-16 9:57 ` Tvrtko Ursulin
2022-02-16 10:33 ` Jani Nikula [this message]
2022-02-16 10:33 ` Jani Nikula
2022-02-16 10:33 ` Jani Nikula
2022-02-17 5:10 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-02-17 5:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-17 14:14 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=87leyb3xtx.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=abaci@linux.alibaba.com \
--cc=airlied@linux.ie \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=ville.syrjala@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.