, November 27, 2017 1:59 PM
To: zhen...@linux.intel.com; Wang, Zhi A <zhi.a.w...@intel.com>;
jani.nik...@linux.intel.com; joonas.lahti...@linux.intel.com; Vivi, Rodrigo
<rodrigo.v...@intel.com>; airl...@linux.ie;
intel-gvt-...@lists.freedesktop.org; intel-...@lists.freedesktop.
, November 27, 2017 1:59 PM
To: zhen...@linux.intel.com; Wang, Zhi A ;
jani.nik...@linux.intel.com; joonas.lahti...@linux.intel.com; Vivi, Rodrigo
; airl...@linux.ie;
intel-gvt-...@lists.freedesktop.org; intel-...@lists.freedesktop.org;
dri-de...@lists.freedesktop.org; linux-kernel@vger.kernel.org
.@intel.com>;
Zhenyu Wang <zhen...@linux.intel.com>; Wang, Zhi A <zhi.a.w...@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>; kernel-janit...@vger.kernel.org
Subject: [PATCH] drm/i915/gvt: Use common error handling code in
shadow_workload_ring_buffer()
From: Markus Elfring
, 2017 3:26 PM
To: dri-de...@lists.freedesktop.org; intel-...@lists.freedesktop.org;
intel-gvt-...@lists.freedesktop.org; David Airlie ; Jani
Nikula ; Joonas Lahtinen
; Vivi, Rodrigo ;
Zhenyu Wang ; Wang, Zhi A
Cc: LKML ; kernel-janit...@vger.kernel.org
Subject: [PATCH] drm/i915/gvt: Use common
AM
To: Gao, Fred <fred@intel.com>; Zhenyu Wang <zhen...@linux.intel.com>;
Wang, Zhi A <zhi.a.w...@intel.com>; Jani Nikula <jani.nik...@linux.intel.com>;
Joonas Lahtinen <joonas.lahti...@linux.intel.com>; Vivi, Rodrigo
<rodrigo.v...@intel.com>; David A
AM
To: Gao, Fred ; Zhenyu Wang ;
Wang, Zhi A ; Jani Nikula ;
Joonas Lahtinen ; Vivi, Rodrigo
; David Airlie ;
intel-gvt-...@lists.freedesktop.org; intel-...@lists.freedesktop.org;
dri-de...@lists.freedesktop.org; linux-kernel@vger.kernel.org
Cc: Christos Gkekas
Subject: [PATCH] drm/i915/gvt
, September 22, 2017 2:11 PM
To: Wang, Zhi A <zhi.a.w...@intel.com>; Zhenyu Wang <zhen...@linux.intel.com>;
Joe Perches <j...@perches.com>
Cc: Gao, Fred <fred@intel.com>; David Airlie <airl...@linux.ie>;
intel-...@lists.freedesktop.org; kernel-janit...@
, September 22, 2017 2:11 PM
To: Wang, Zhi A ; Zhenyu Wang ;
Joe Perches
Cc: Gao, Fred ; David Airlie ;
intel-...@lists.freedesktop.org; kernel-janit...@vger.kernel.org;
linux-kernel@vger.kernel.org; Jani Nikula ;
dri-de...@lists.freedesktop.org; Vivi, Rodrigo ; Colin
King ; intel-gvt
..@lists.freedesktop.org; Vivi, Rodrigo <rodrigo.v...@intel.com>; Colin
King <colin.k...@canonical.com>; intel-gvt-...@lists.freedesktop.org; Wang, Zhi
A <zhi.a.w...@intel.com>
Subject: Re: [PATCH][drm-next] drm/i915/gvt: ensure -ve return value is handled
correctly
On T
Cc: Gao, Fred ; David Airlie ;
intel-...@lists.freedesktop.org; kernel-janit...@vger.kernel.org;
linux-kernel@vger.kernel.org; Jani Nikula ;
dri-de...@lists.freedesktop.org; Vivi, Rodrigo ; Colin
King ; intel-gvt-...@lists.freedesktop.org; Wang, Zhi
A
Subject: Re: [PATCH][drm-next] drm/i915
This patch factors out mempool_refill() from mempool_resize(). It's reasonable
that the mempool user wants to refill the pool immdiately when it has chance
e.g. inside a sleepible context, so that next time in the IRQ context the pool
would have much more available elements to allocate.
After the
This patch factors out mempool_refill() from mempool_resize(). It's reasonable
that the mempool user wants to refill the pool immdiately when it has chance
e.g. inside a sleepible context, so that next time in the IRQ context the pool
would have much more available elements to allocate.
After the
This patch factors out mempool_refill() from mempool_resize(). It's reasonable
that the mempool user wants to refill the pool immdiately when it has chance
e.g. inside a sleepible context, so that next time in the IRQ context the pool
would have much more available elements to allocate.
After the
This patch factors out mempool_refill() from mempool_resize(). It's reasonable
that the mempool user wants to refill the pool immdiately when it has chance
e.g. inside a sleepible context, so that next time in the IRQ context the pool
would have much more available elements to allocate.
After the
Hi Gurus:
Currently we met some allocation failed in mempool_resize() ->
/* Grow the pool */
new_elements = kmalloc_array(new_min_nr, sizeof(*new_elements), //
< Here
GFP_KERNEL);
if (!new_elements)
return
Hi Gurus:
Currently we met some allocation failed in mempool_resize() ->
/* Grow the pool */
new_elements = kmalloc_array(new_min_nr, sizeof(*new_elements), //
< Here
GFP_KERNEL);
if (!new_elements)
return
16 matches
Mail list logo