From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:34666) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gye7x-0008Ju-9a for qemu-devel@nongnu.org; Tue, 26 Feb 2019 09:54:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gye7u-0005n6-Ft for qemu-devel@nongnu.org; Tue, 26 Feb 2019 09:54:37 -0500 References: <20190218122710.23639-1-david@redhat.com> <20190218122710.23639-9-david@redhat.com> From: David Hildenbrand Message-ID: Date: Tue, 26 Feb 2019 15:54:21 +0100 MIME-Version: 1.0 In-Reply-To: <20190218122710.23639-9-david@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3 08/15] s390x/tcg: Handle SET FPC AND LOAD FPC 3-bit BFP rounding modes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: qemu-s390x@nongnu.org, Thomas Huth , Halil Pasic , Christian Borntraeger , Janosch Frank , Cornelia Huck , Richard Henderson On 18.02.19 13:27, David Hildenbrand wrote: > We already forward the 3 bits correctly in the translation functions. We > also have to handle them properly and check for specification > exceptions. > > Setting an invalid rounding mode (BFP only, all DFP rounding modes) > results in a specification exception. Setting unassigned bits in the > fpc, results in a specification exception. > > This fixes LOAD FPC (AND SIGNAL), SET FPC (AND SIGNAL). Also for, > SET BFP ROUNDING MODE, 3-bit rounding mode is now explicitly checked. > > Note: TCG_CALL_NO_WG is required for sfpc handler, as we now inject > exceptions. > > We won't be modeling abscence of the "floating-point extension facility" > for now, not necessary as most take the facility for granted without > checking. > > z14 PoP, 9-23, "LOAD FPC" > When the floating-point extension facility is > installed, bits 29-31 of the second operand must > specify a valid BFP rounding mode and bits 6-7, > 14-15, 24, and 28 must be zero; otherwise, a > specification exception is recognized. > > Signed-off-by: David Hildenbrand Here as well, Reviewed-by: Richard Henderson -- Thanks, David / dhildenb