All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/gt: Split intel_ring_submission
Date: Thu, 24 Oct 2019 08:15:57 +0100	[thread overview]
Message-ID: <157190135762.18724.12145404951111756532@skylake-alporthouse-com> (raw)
In-Reply-To: <20191024071139.31917-1-chris@chris-wilson.co.uk>

Quoting Chris Wilson (2019-10-24 08:11:39)
> Split the legacy submission backend from the common ring buffer.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

Wouldn't this be a good opportunity to add some mock testing of ring
wraparound? Because that hasn't been broken for long periods of time in
the past. Shut up, shut up, shut up!
-Chris
_______________________________________________
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: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: Split intel_ring_submission
Date: Thu, 24 Oct 2019 08:15:57 +0100	[thread overview]
Message-ID: <157190135762.18724.12145404951111756532@skylake-alporthouse-com> (raw)
Message-ID: <20191024071557.MPmGmzPUqxQkaNPEbS06_H1_ARP2Ybb4VJJylTlsZhc@z> (raw)
In-Reply-To: <20191024071139.31917-1-chris@chris-wilson.co.uk>

Quoting Chris Wilson (2019-10-24 08:11:39)
> Split the legacy submission backend from the common ring buffer.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

Wouldn't this be a good opportunity to add some mock testing of ring
wraparound? Because that hasn't been broken for long periods of time in
the past. Shut up, shut up, shut up!
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-10-24  7:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24  7:11 [PATCH] drm/i915/gt: Split intel_ring_submission Chris Wilson
2019-10-24  7:11 ` [Intel-gfx] " Chris Wilson
2019-10-24  7:15 ` Chris Wilson [this message]
2019-10-24  7:15   ` Chris Wilson
2019-10-24  7:32 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2019-10-24  7:32   ` [Intel-gfx] " Patchwork
2019-10-24  7:33 ` [PATCH] " Mika Kuoppala
2019-10-24  7:33   ` [Intel-gfx] " Mika Kuoppala
2019-10-24  8:01 ` Chris Wilson
2019-10-24  8:01   ` [Intel-gfx] " Chris Wilson
2019-10-24 10:03   ` Chris Wilson
2019-10-24 10:03     ` [Intel-gfx] " Chris Wilson
2019-10-24 10:43 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gt: Split intel_ring_submission (rev3) Patchwork
2019-10-24 10:43   ` [Intel-gfx] " Patchwork
2019-10-24 11:04 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-10-24 11:04   ` [Intel-gfx] " 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=157190135762.18724.12145404951111756532@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.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.