From: Will Deacon <will.deacon@arm.com>
To: "Wang, Yalin" <Yalin.Wang@sonymobile.com>
Cc: "'linux-arm-msm-owner@vger.kernel.org'"
<linux-arm-msm-owner@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
jonathan.austin@arm.com
Subject: Re: SDIV / UDIV Question
Date: Thu, 10 Oct 2013 10:21:46 +0100 [thread overview]
Message-ID: <20131010092146.GC3817@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <35FD53F367049845BC99AC72306C23D1014D1A0971B0@CNBJMBX05.corpusers.net>
[Adding Jonny]
On Thu, Oct 10, 2013 at 06:04:41AM +0100, Wang, Yalin wrote:
> Oh , I see ,
> Thanks for your clarification !
> So R-class cores will not run linux ?
R-class cores can run Linux, but I don't reckon we touch SCTLR.DZ. I've
added Jonny, so he can clarify the behaviour here. (I'm also not sure which
cores have these instructions either).
Will
> -----Original Message-----
> From: Will Deacon [mailto:will.deacon@arm.com]
> Sent: Wednesday, October 09, 2013 6:54 PM
> To: Wang, Yalin
> Cc: 'linux-arm-msm-owner@vger.kernel.org'; linux-kernel@vger.kernel.org
> Subject: Re: SDIV / UDIV Question
>
> On Wed, Oct 09, 2013 at 08:08:05AM +0100, Wang, Yalin wrote:
> > I have a question about sdiv/ udiv instructions :
> > In armv7 A/R TRM, it said sdiv/udiv will cause Divide by zero as
> > undefined exception or just return zero (decided by implementation) .
> >
> > So in kernel , should we need register a undef hook to Get this
> > undef exception and send SIGFPE to user space Process ?
>
> As far as I can see, this can only happen for R-class cores, based on SCTLR.DZ.
>
> Will
>
prev parent reply other threads:[~2013-10-10 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 7:08 Wang, Yalin
2013-10-09 10:53 ` Will Deacon
2013-10-10 5:04 ` Wang, Yalin
2013-10-10 9:21 ` Will Deacon [this message]
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=20131010092146.GC3817@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=Yalin.Wang@sonymobile.com \
--cc=jonathan.austin@arm.com \
--cc=linux-arm-msm-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®