From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Sandipan Das <sandipan@linux.vnet.ibm.com>
Cc: mpe@ellerman.id.au, anton@samba.org, paulus@samba.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/3] powerpc/lib/sstep: Add XER bits introduced in POWER ISA v3.0
Date: Fri, 29 Sep 2017 13:01:24 +0530 [thread overview]
Message-ID: <20170929073124.zymjf7v7dr336ye3@naverao1-tp.localdomain> (raw)
In-Reply-To: <20170929054410.12600-1-sandipan@linux.vnet.ibm.com>
On 2017/09/29 05:44AM, Sandipan Das wrote:
> This adds definitions for the OV32 and CA32 bits of XER that
> were introduced in POWER ISA v3.0. There are some existing
> instructions that currently set the OV and CA bits based on
> certain conditions.
>
> The emulation behaviour of all these instructions needs to
> be updated to set these new bits accordingly.
>
> Signed-off-by: Sandipan Das <sandipan@linux.vnet.ibm.com>
For this series:
Acked-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
> ---
> arch/powerpc/lib/sstep.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/powerpc/lib/sstep.c b/arch/powerpc/lib/sstep.c
> index 5e8418c28bd8..16814bfc01da 100644
> --- a/arch/powerpc/lib/sstep.c
> +++ b/arch/powerpc/lib/sstep.c
> @@ -31,6 +31,8 @@ extern char system_call_common[];
> #define XER_SO 0x80000000U
> #define XER_OV 0x40000000U
> #define XER_CA 0x20000000U
> +#define XER_OV32 0x00080000U
> +#define XER_CA32 0x00040000U
>
> #ifdef CONFIG_PPC_FPU
> /*
> --
> 2.13.5
>
next prev parent reply other threads:[~2017-09-29 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 5:44 [PATCH 1/3] powerpc/lib/sstep: Add XER bits introduced in POWER ISA v3.0 Sandipan Das
2017-09-29 5:44 ` [PATCH 2/3] powerpc/lib/sstep: Fix fixed-point arithmetic instructions that set CA32 Sandipan Das
2017-09-29 5:44 ` [PATCH 3/3] powerpc/lib/sstep: Fix fixed-point shift " Sandipan Das
2017-09-29 7:31 ` Naveen N. Rao [this message]
2017-10-05 4:21 ` [1/3] powerpc/lib/sstep: Add XER bits introduced in POWER ISA v3.0 Michael Ellerman
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=20170929073124.zymjf7v7dr336ye3@naverao1-tp.localdomain \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=sandipan@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.