From: Peter Zijlstra <peterz@infradead.org>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [Intel-gfx] [RFC 0/6] CPU + GPU synchronised priority scheduling
Date: Thu, 30 Sep 2021 20:34:40 +0200 [thread overview]
Message-ID: <20210930183440.GD4323@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20210930171552.501553-1-tvrtko.ursulin@linux.intel.com>
On Thu, Sep 30, 2021 at 06:15:46PM +0100, Tvrtko Ursulin wrote:
> (Note I did not copy
> everyone on all patches but just the cover letter for context and the rest
> should be available from the mailing list.)
In general, if you can't be arsed to send it to me, I can't be arsed to
dig it out. I've got plenty other email I can read without having to go
looking for more.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [RFC 0/6] CPU + GPU synchronised priority scheduling
Date: Thu, 30 Sep 2021 20:34:40 +0200 [thread overview]
Message-ID: <20210930183440.GD4323@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20210930171552.501553-1-tvrtko.ursulin@linux.intel.com>
On Thu, Sep 30, 2021 at 06:15:46PM +0100, Tvrtko Ursulin wrote:
> (Note I did not copy
> everyone on all patches but just the cover letter for context and the rest
> should be available from the mailing list.)
In general, if you can't be arsed to send it to me, I can't be arsed to
dig it out. I've got plenty other email I can read without having to go
looking for more.
next prev parent reply other threads:[~2021-09-30 18:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 17:15 [Intel-gfx] [RFC 0/6] CPU + GPU synchronised priority scheduling Tvrtko Ursulin
2021-09-30 17:15 ` Tvrtko Ursulin
2021-09-30 17:15 ` [Intel-gfx] [RFC 1/6] sched: Add nice value change notifier Tvrtko Ursulin
2021-09-30 17:15 ` Tvrtko Ursulin
2021-09-30 18:33 ` [Intel-gfx] " Peter Zijlstra
2021-09-30 18:33 ` Peter Zijlstra
2021-10-01 9:04 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-01 9:04 ` Tvrtko Ursulin
2021-10-01 10:32 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-01 10:32 ` Tvrtko Ursulin
2021-10-01 15:48 ` [Intel-gfx] " Peter Zijlstra
2021-10-01 15:48 ` Peter Zijlstra
2021-10-04 8:12 ` [Intel-gfx] " Tvrtko Ursulin
2021-10-04 8:12 ` Tvrtko Ursulin
2021-10-04 8:39 ` [Intel-gfx] " Peter Zijlstra
2021-10-04 8:39 ` Peter Zijlstra
2021-09-30 17:15 ` [Intel-gfx] [RFC 2/6] drm/i915: Explicitly track DRM clients Tvrtko Ursulin
2021-09-30 17:15 ` Tvrtko Ursulin
2021-09-30 17:15 ` [Intel-gfx] [RFC 3/6] drm/i915: Make GEM contexts " Tvrtko Ursulin
2021-09-30 17:15 ` Tvrtko Ursulin
2021-09-30 17:15 ` [Intel-gfx] [RFC 4/6] drm/i915: Track all user contexts per client Tvrtko Ursulin
2021-09-30 17:15 ` Tvrtko Ursulin
2021-09-30 17:15 ` [Intel-gfx] [RFC 5/6] drm/i915: Keep track of registered clients indexed by task struct Tvrtko Ursulin
2021-09-30 17:15 ` Tvrtko Ursulin
2021-09-30 17:15 ` [Intel-gfx] [RFC 6/6] drm/i915: Connect task and GPU scheduling priorities Tvrtko Ursulin
2021-09-30 17:15 ` Tvrtko Ursulin
2021-09-30 17:23 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for CPU + GPU synchronised priority scheduling Patchwork
2021-09-30 18:34 ` Peter Zijlstra [this message]
2021-09-30 18:34 ` [RFC 0/6] " Peter Zijlstra
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=20210930183440.GD4323@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tvrtko.ursulin@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=vincent.guittot@linaro.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.