From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Tauro, Riana" <riana.tauro@intel.com>,
"Jadav, Raag" <raag.jadav@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Roper, Matthew D" <matthew.d.roper@intel.com>
Subject: Re: [PATCH 1/1] drm/xe/survivability: broadcast dmesg when engaging survivability
Date: Thu, 29 Oct 2026 18:57:09 +0000 [thread overview]
Message-ID: <40e6e0bc0c8a7aa97208629a41255568e7faa319.camel@intel.com> (raw)
In-Reply-To: <b5964a238b9677518cc46648a90a7c5c7034396f.camel@intel.com>
On Thu, 2026-10-29 at 11:41 -0700, Teres Alexis, Alan Previn wrote:
> > > >
While i have your time on this area of code i just realized we have a bug
with how we are using udelay within pcode_try_request where the "wait" param
increases exponentially without bounding to (MAX_UDELAY_MS*1000) - which can
cause overflow and potentially not waiting long enough. this should be a fixup
so ill post separately.
next prev parent reply other threads:[~2026-10-29 18:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 17:36 [PATCH 1/1] drm/xe/survivability: broadcast dmesg when engaging survivability Alan Previn
2026-10-23 17:46 ` ✓ CI.KUnit: success for series starting with [1/1] " Patchwork
2026-10-23 18:24 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-24 1:30 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-10-28 3:18 ` [PATCH 1/1] " Raag Jadav
2026-10-28 21:01 ` Teres Alexis, Alan Previn
2026-10-29 4:48 ` Raag Jadav
2026-10-29 9:38 ` Tauro, Riana
2026-10-29 18:41 ` Teres Alexis, Alan Previn
2026-10-29 18:57 ` Teres Alexis, Alan Previn [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-10-23 0:18 Alan Previn
2026-10-23 0:27 ` sashiko-bot
2026-10-23 16:43 ` Teres Alexis, Alan Previn
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=40e6e0bc0c8a7aa97208629a41255568e7faa319.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@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.