From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: Mark up potential allocation paths within i915_sw_fence as might_sleep
Date: Wed, 13 Dec 2017 13:08:39 +0200 [thread overview]
Message-ID: <1513163319.5228.29.camel@linux.intel.com> (raw)
In-Reply-To: <20171212180652.22061-1-chris@chris-wilson.co.uk>
On Tue, 2017-12-12 at 18:06 +0000, Chris Wilson wrote:
> As kmalloc is allowed to block (if given the right flags), mark up the
> two i915_sw_fence routines that may call kmalloc as potential sleeping
> routines.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-12-13 11:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 18:06 [PATCH 1/3] drm/i915: Mark up potential allocation paths within i915_sw_fence as might_sleep Chris Wilson
2017-12-12 18:06 ` [PATCH 2/3] drm/i915: Allow fence allocations to fail Chris Wilson
2017-12-13 11:15 ` Joonas Lahtinen
2017-12-13 11:25 ` Chris Wilson
2017-12-12 18:06 ` [PATCH 3/3] drm/i915: Ratelimit request allocation under oom Chris Wilson
2017-12-13 11:18 ` Joonas Lahtinen
2017-12-13 11:25 ` Chris Wilson
2017-12-12 18:30 ` ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915: Mark up potential allocation paths within i915_sw_fence as might_sleep Patchwork
2017-12-12 19:20 ` ✓ Fi.CI.IGT: " Patchwork
2017-12-13 13:29 ` Chris Wilson
2017-12-13 11:08 ` Joonas Lahtinen [this message]
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=1513163319.5228.29.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox