From: Zhenyu Wang Subject: Re: [PATCH] drm/i915: Disable semaphore on vGPU for now Date: Thu, 28 Mar 2019 10:26:26 +0800 Message-ID: <20190328022626.GC20332@zhen-hp.sh.intel.com> References: <20190327090636.3547-1-zhenyuw@linux.intel.com> <155367813647.24691.10538359395237455801@skylake-alporthouse-com> Reply-To: Zhenyu Wang Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1871760658==" Return-path: In-Reply-To: <155367813647.24691.10538359395237455801@skylake-alporthouse-com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Chris Wilson Cc: intel-gfx@lists.freedesktop.org, intel-gvt-dev@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org --===============1871760658== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="w7PDEPdKQumQfZlR" Content-Disposition: inline --w7PDEPdKQumQfZlR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2019.03.27 09:15:36 +0000, Chris Wilson wrote: > Quoting Zhenyu Wang (2019-03-27 09:06:36) > > This is to disable semaphore usage when on vGPU for now. Unfortunately > > GVT-g hasn't fully enabled semaphore usage yet, so current guest with > > semaphore use would cause vGPU failure. > >=20 > > Although current semaphore failure with vGPU can be simply resolved by > > allowing cmd parser to accept MI_SEMAPHORE_WAIT command with address > > audit, we're checking general usage of semaphore and how we should > > handle it properly for virtualization in consider of function and > > security concern. So we decide to request to disable it for now in > > guest driver. Once GVT could support it, we would add new compat bit > > to turn it on. >=20 > MI_WAIT_SEMAPHORE are used by Vulkan (anvil) as well for VkEvents. For batch buffer usage, current GVT won't scan on non-privileged buffer so that's still accepted. We need to consider all use case of semaphore any= way. thanks --=20 Open Source Technology Center, Intel ltd. $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827 --w7PDEPdKQumQfZlR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTXuabgHDW6LPt9CICxBBozTXgYJwUCXJww0gAKCRCxBBozTXgY J+0lAJ96WqtjvpoI9Bd6Z2d6KhYSNgzduQCfZFOd7N4Li6LSoPgyYS6Ljx5XOdI= =xqLg -----END PGP SIGNATURE----- --w7PDEPdKQumQfZlR-- --===============1871760658== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KSW50ZWwtZ2Z4 IG1haWxpbmcgbGlzdApJbnRlbC1nZnhAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vaW50ZWwtZ2Z4 --===============1871760658==--