Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tursulin@ursulin.net>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
	"Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Cc: intel-xe@lists.freedesktop.org,
	Lucas De Marchi <lucas.demarchi@intel.com>,
	Anshuman Gupta <anshuman.gupta@intel.com>
Subject: Re: [PATCH 1/3] drm/xe: Introduce a simple busted state
Date: Fri, 15 Mar 2024 14:14:34 +0000	[thread overview]
Message-ID: <89074e2d-9b23-40af-87f5-61017173d33c@ursulin.net> (raw)
In-Reply-To: <ZfO8BzWmVJ98T0Eg@intel.com>


On 15/03/2024 03:09, Rodrigo Vivi wrote:
> On Thu, Mar 14, 2024 at 06:23:04PM -0700, Dixit, Ashutosh wrote:
>> On Thu, 14 Mar 2024 18:03:15 -0700, Rodrigo Vivi wrote:
>>>
>>> Introduce a very simple 'busted' state where any attempt
>>> to access the GPU is entirely blocked.
>>
>> Busted?
>>
>> busted. / (ˈbʌstəd) / adjective. informal caught out doing something wrong
>> and therefore in trouble: you are so busted.
> 
> that's why ;)
> 
> also:
> https://www.dictionary.com/browse/busted
> "broken, fractured, or seriously damaged"
> 
>>
>> Why not wedged
> 
> https://www.merriam-webster.com/dictionary/wedged : "shaped like a wedge" ? :)
> 
> or perhaps this: https://dictionary.cambridge.org/us/dictionary/english/wedged
> 
> "to make something stay in a particular position by using a wedge"
> 
> "to put something into a very small or narrow space, so that it cannot move easily"
> 
> that's the i915 terminology and meaning that I'm trying to avoid here...
> 
> i.e. wedged can be a temporary state like in i915 where we 'wedge' and 'unwedge'
> the gpu in so many cases. That flow doesn't fit well with xe scheduler and it is
> a complication that is not desired.
> 
> So I want a stronger word that makes it really clear that something went wrong
> and won't easily transition back.
> 
>>   or lost
> 
> but not that strong...
> 
> it is not entirely lost... we can still open the client, otherwise we would lose
> display and also get the guc logs.
> 
> If we really want to go lost and avoid the client connection then we could
> simply deregister the drm card device for instance...
> 
>> or down
> 
> looks like 'off' without power...
> 
>> or dead?
> 
> too strong... like lost.

Busted feels maybe not fully professional in the logs? So if wedged 
really cannot be re-used for reduced congitive load then Merriam Webster 
lists 'jammed' as a synonym which has a pretty neat definitions.

a
: to become blocked, wedged, or stuck fast
The line jammed and the boat hung useless.

b
: to become unworkable when a movable part becomes blocked or stuck
the gun jammed

Or 'off-lined' and maybe truly unregister the client as you say above. 
There is some benefit to avoiding funny words in kernel logs I think.

Regards,

Tvrtko

> 
>>
>> :-)
>>
>> Ashutosh

  reply	other threads:[~2024-03-15 14:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15  1:03 [PATCH 1/3] drm/xe: Introduce a simple busted state Rodrigo Vivi
2024-03-15  1:03 ` [PATCH 2/3] drm/xe: declare busted upon GuC load failure Rodrigo Vivi
2024-03-15 11:16   ` Ghimiray, Himal Prasad
2024-03-15 13:54     ` Rodrigo Vivi
2024-03-15 14:23   ` Ghimiray, Himal Prasad
2024-03-15  1:03 ` [PATCH 3/3] drm/xe: Force busted state and block GT reset upon any GPU hang Rodrigo Vivi
2024-03-15  4:31   ` Ghimiray, Himal Prasad
2024-03-15 13:59     ` Rodrigo Vivi
2024-03-15  1:08 ` ✓ CI.Patch_applied: success for series starting with [1/3] drm/xe: Introduce a simple busted state Patchwork
2024-03-15  1:08 ` ✓ CI.checkpatch: " Patchwork
2024-03-15  1:09 ` ✓ CI.KUnit: " Patchwork
2024-03-15  1:20 ` ✓ CI.Build: " Patchwork
2024-03-15  1:22 ` ✓ CI.Hooks: " Patchwork
2024-03-15  1:23 ` [PATCH 1/3] " Dixit, Ashutosh
2024-03-15  3:08   ` Lucas De Marchi
2024-03-15  3:09   ` Rodrigo Vivi
2024-03-15 14:14     ` Tvrtko Ursulin [this message]
2024-03-18 23:23       ` Dixit, Ashutosh
2024-03-15  1:24 ` ✓ CI.checksparse: success for series starting with [1/3] " Patchwork
2024-03-15  1:48 ` ✓ CI.BAT: " Patchwork
2024-03-15  7:13 ` [PATCH 1/3] " Aravind Iddamsetty
2024-03-15 13:50   ` Rodrigo Vivi
2024-03-15 11:52 ` Ghimiray, Himal Prasad

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=89074e2d-9b23-40af-87f5-61017173d33c@ursulin.net \
    --to=tursulin@ursulin.net \
    --cc=anshuman.gupta@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=rodrigo.vivi@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