[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1506331944.5593.10.camel@linux.intel.com>
Date: Mon, 25 Sep 2017 12:32:24 +0300
From: Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>
To: "Wang, Zhi A" <zhi.a.wang@...el.com>,
Zhenyu Wang <zhenyuw@...ux.intel.com>,
Joe Perches <joe@...ches.com>
Cc: "Gao, Fred" <fred.gao@...el.com>, David Airlie <airlied@...ux.ie>,
"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jani Nikula <jani.nikula@...ux.intel.com>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"Vivi, Rodrigo" <rodrigo.vivi@...el.com>,
Colin King <colin.king@...onical.com>,
"intel-gvt-dev@...ts.freedesktop.org"
<intel-gvt-dev@...ts.freedesktop.org>
Subject: Re: [PATCH][drm-next] drm/i915/gvt: ensure -ve return value is
handled correctly
On Fri, 2017-09-22 at 17:50 +0000, Wang, Zhi A wrote:
> Thanks for the reply. Learned a lot. :)
>
> GEM_BUG_ON is new to me since it wasn't there at the beginning of
> GVT-g upstream. It showed up later. So I left a lot of WARN_ON in the
> code and some of them should be GEM_BUG_ON now.
>
> Now I can figure out those differences. We can discuss with our QA to
> see if they would like to enable I915_GEM_DEBUG and then we can move
> to GEM_BUG_ON also, or maybe we can have a dedicated GVT_BUG_ON. :)
> Thank you so much. Have a great weekend.
GVT_BUG_ON is probably the way to go :)
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
Powered by blists - more mailing lists