From: Ramalingam C <ramalingam.c@intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
Hellstrom Thomas <thomas.hellstrom@intel.com>,
Chris Wilson <chris.p.wilson@intel.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 1/5] drm/i915/dg2: Add Wa_22011450934
Date: Fri, 11 Feb 2022 19:04:00 +0530 [thread overview]
Message-ID: <20220211133400.GC25847@intel.com> (raw)
In-Reply-To: <79cefb8f-3f71-a59e-28de-6b9a59c28c30@intel.com>
On 2022-02-07 at 11:52:48 +0000, Matthew Auld wrote:
> On 07/02/2022 11:48, Matthew Auld wrote:
> > On Fri, 28 Jan 2022 at 18:52, Ramalingam C <ramalingam.c@intel.com> wrote:
> > >
> > > An indirect ctx wabb is implemented as per Wa_22011450934 to avoid rcs
> > > restore hang during context restore of a preempted context in GPGPU mode
> > >
> > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> > > cc: Chris Wilson <chris.p.wilson@intel.com>
> > Acked-by: Matthew Auld <matthew.auld@intel.com>
>
> Also, feel free to upgrade to r-b for this and patches 2-4.
Thank you Matt. I have pushed these changes to the tree.
Ram.
WARNING: multiple messages have this Message-ID (diff)
From: Ramalingam C <ramalingam.c@intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
Hellstrom Thomas <thomas.hellstrom@intel.com>,
Matthew Auld <matthew.william.auld@gmail.com>,
Chris Wilson <chris.p.wilson@intel.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 1/5] drm/i915/dg2: Add Wa_22011450934
Date: Fri, 11 Feb 2022 19:04:00 +0530 [thread overview]
Message-ID: <20220211133400.GC25847@intel.com> (raw)
In-Reply-To: <79cefb8f-3f71-a59e-28de-6b9a59c28c30@intel.com>
On 2022-02-07 at 11:52:48 +0000, Matthew Auld wrote:
> On 07/02/2022 11:48, Matthew Auld wrote:
> > On Fri, 28 Jan 2022 at 18:52, Ramalingam C <ramalingam.c@intel.com> wrote:
> > >
> > > An indirect ctx wabb is implemented as per Wa_22011450934 to avoid rcs
> > > restore hang during context restore of a preempted context in GPGPU mode
> > >
> > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> > > cc: Chris Wilson <chris.p.wilson@intel.com>
> > Acked-by: Matthew Auld <matthew.auld@intel.com>
>
> Also, feel free to upgrade to r-b for this and patches 2-4.
Thank you Matt. I have pushed these changes to the tree.
Ram.
next prev parent reply other threads:[~2022-02-11 13:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 18:52 [Intel-gfx] [PATCH 0/5] Misc DG2 enabling patches Ramalingam C
2022-01-28 18:52 ` Ramalingam C
2022-01-28 18:52 ` [Intel-gfx] [PATCH 1/5] drm/i915/dg2: Add Wa_22011450934 Ramalingam C
2022-01-28 18:52 ` Ramalingam C
2022-02-07 11:48 ` [Intel-gfx] " Matthew Auld
2022-02-07 11:52 ` Matthew Auld
2022-02-11 13:34 ` Ramalingam C [this message]
2022-02-11 13:34 ` Ramalingam C
2022-01-28 18:52 ` [Intel-gfx] [PATCH 2/5] drm/i915: align the plane_vma to min_page_size of stolen mem Ramalingam C
2022-01-28 18:52 ` Ramalingam C
2022-01-31 10:18 ` [Intel-gfx] " Matthew Auld
2022-01-31 10:18 ` Matthew Auld
2022-01-31 10:26 ` [Intel-gfx] " Matthew Auld
2022-01-28 18:52 ` [Intel-gfx] [PATCH 3/5] drm/i915: More gt idling time with guc submission Ramalingam C
2022-01-28 18:52 ` Ramalingam C
2022-01-31 10:19 ` [Intel-gfx] " Matthew Auld
2022-01-31 10:19 ` Matthew Auld
2022-01-28 18:52 ` [Intel-gfx] [PATCH 4/5] drm/i915/dg2: Add Wa_22011100796 Ramalingam C
2022-01-28 18:52 ` Ramalingam C
2022-01-31 11:06 ` [Intel-gfx] " Matthew Auld
2022-01-28 18:52 ` [Intel-gfx] [PATCH 5/5] drm/i915/guc: Allow user to override driver load failure without GuC Ramalingam C
2022-01-28 18:52 ` Ramalingam C
2022-02-07 16:55 ` [Intel-gfx] " Daniele Ceraolo Spurio
2022-02-07 16:55 ` Daniele Ceraolo Spurio
2022-02-11 13:32 ` Ramalingam C
2022-02-11 13:32 ` Ramalingam C
2022-01-28 19:21 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Misc DG2 enabling patches Patchwork
2022-01-28 19:49 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-01-29 1:53 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20220211133400.GC25847@intel.com \
--to=ramalingam.c@intel.com \
--cc=chris.p.wilson@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=thomas.hellstrom@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.