From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org, Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915/execlists: Avoid reusing the same logical CCID
Date: Fri, 01 May 2020 02:55:18 +0000 [thread overview]
Message-ID: <20200501025518.EEED32137B@mail.kernel.org> (raw)
In-Reply-To: <20200428085336.9580-1-chris@chris-wilson.co.uk>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 2935ed5339c4 ("drm/i915: Remove logical HW ID").
The bot has tested the following trees: v5.6.7.
v5.6.7: Failed to apply! Possible dependencies:
1883a0a4658e ("drm/i915: Track hw reported context runtime")
35f3fd8182ba ("drm/i915/execlists: Workaround switching back to a completed context")
489645d522df ("drm/i915/gt: Show the cumulative context runtime in engine debug")
4c8ed8b12674 ("drm/i915/selftests: Exercise timeslice rewinding")
4c977837ba29 ("drm/i915/execlists: Peek at the next submission for error interrupts")
606727842d8b ("drm/i915/gt: Include the execlists CCID of each port in the engine dump")
61f874d6e001 ("drm/i915/gt: Use scnprintf() for avoiding potential buffer overflow")
6f280b133dc2 ("drm/i915/perf: Fix OA context id overlap with idle context id")
70a76a9b8e9d ("drm/i915/gt: Hook up CS_MASTER_ERROR_INTERRUPT")
8b6d457f9532 ("drm/i915/execlists: Include priority info in trace_ports")
b4892e440432 ("drm/i915: Make define for lrc state offset")
b4d3acaa7333 ("drm/i915/gt: Pull sseu context updates under gt")
c4e8ba739034 ("drm/i915/gt: Yield the timeslice if caught waiting on a user semaphore")
ff3d4ff6c9e6 ("drm/i915/gt: Tidy repetition in declaring gen8+ interrupts")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/i915/execlists: Avoid reusing the same logical CCID
Date: Fri, 01 May 2020 02:55:18 +0000 [thread overview]
Message-ID: <20200501025518.EEED32137B@mail.kernel.org> (raw)
In-Reply-To: <20200428085336.9580-1-chris@chris-wilson.co.uk>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 2935ed5339c4 ("drm/i915: Remove logical HW ID").
The bot has tested the following trees: v5.6.7.
v5.6.7: Failed to apply! Possible dependencies:
1883a0a4658e ("drm/i915: Track hw reported context runtime")
35f3fd8182ba ("drm/i915/execlists: Workaround switching back to a completed context")
489645d522df ("drm/i915/gt: Show the cumulative context runtime in engine debug")
4c8ed8b12674 ("drm/i915/selftests: Exercise timeslice rewinding")
4c977837ba29 ("drm/i915/execlists: Peek at the next submission for error interrupts")
606727842d8b ("drm/i915/gt: Include the execlists CCID of each port in the engine dump")
61f874d6e001 ("drm/i915/gt: Use scnprintf() for avoiding potential buffer overflow")
6f280b133dc2 ("drm/i915/perf: Fix OA context id overlap with idle context id")
70a76a9b8e9d ("drm/i915/gt: Hook up CS_MASTER_ERROR_INTERRUPT")
8b6d457f9532 ("drm/i915/execlists: Include priority info in trace_ports")
b4892e440432 ("drm/i915: Make define for lrc state offset")
b4d3acaa7333 ("drm/i915/gt: Pull sseu context updates under gt")
c4e8ba739034 ("drm/i915/gt: Yield the timeslice if caught waiting on a user semaphore")
ff3d4ff6c9e6 ("drm/i915/gt: Tidy repetition in declaring gen8+ interrupts")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-05-01 2:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 8:53 [Intel-gfx] [PATCH 1/2] drm/i915/execlists: Avoid reusing the same logical CCID Chris Wilson
2020-04-28 8:53 ` Chris Wilson
2020-04-28 8:53 ` [Intel-gfx] [PATCH 2/2] drm/i915/execlists: Verify we don't submit two identical CCIDs Chris Wilson
2020-04-28 12:15 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/execlists: Avoid reusing the same logical CCID Patchwork
2020-04-28 12:42 ` Chris Wilson
2020-05-01 2:55 ` Sasha Levin [this message]
2020-05-01 2:55 ` [PATCH 1/2] " Sasha Levin
-- strict thread matches above, loose matches on Subject: below --
2020-04-27 21:10 [Intel-gfx] " Chris Wilson
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=20200501025518.EEED32137B@mail.kernel.org \
--to=sashal@kernel.org \
--cc=chris@chris-wilson.co.uk \
--cc=stable@vger.kernel.org \
/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.