From: Sebastian Reichel <sre@debian.org>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
freemangordon@abv.bg
Subject: Re: [PATCH] ARM: OMAP2+: Add support for thumb mode on DT booted N900
Date: Thu, 6 Feb 2014 01:25:12 +0100 [thread overview]
Message-ID: <20140206002512.GA654@earth.universe> (raw)
In-Reply-To: <CAHYPw2FRbcR_anv9f2igcFV6XnCfpjJMHaeZmcNs8KpXuG96cQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
On Wed, Feb 05, 2014 at 09:42:30PM +0100, Pali Rohár wrote:
> 2014-02-05 Sebastian Reichel <sre@debian.org>:
> > Hi,
> >
> > On Wed, Feb 05, 2014 at 05:38:54PM +0100, Pali Rohár wrote:
> >> > I assumed, that the workaround is not needed for this device type.
> >>
> >> That rx51 secure call must not be called on non secure devices (e.g.
> >> qemu), because it cause kernel crash. So I thought that kernel should
> >> write something like secure call is disabled on that device types.
> >> Kernel code for errata 430973 will update ibe bit for non secure
> >> devices.
> >
> > Do you see any advantage in having that message?
> >
>
> Consistency. Print message 1) only if secure rx51 smc instruction is
> called or 2) print message always (also if smc is not called). With
> that patch message is printed (enabled/disabled) only if device is
> rx51 and device type is HS.
>
> For information it is also good to know that in qemu that special
> secure smc instruction was not called.
Assuming I do not know about this errata/workaround and have some
problems with crashing binaries I may have a look at the kernel
warnings. Without the additional message I won't get any hint about
the errata/workaround at all.
On the other hand there is no such information gain on qemu. It just
tells the user, that some workaround, which is not needed, has not
been activated.
-- Sebastian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-02-06 0:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 12:33 [PATCH] ARM: OMAP2+: Add support for thumb mode on DT booted N900 Sebastian Reichel
2014-02-05 13:12 ` Pali Rohár
2014-02-05 16:31 ` Sebastian Reichel
2014-02-05 16:38 ` Pali Rohár
2014-02-05 17:17 ` Sebastian Reichel
2014-02-05 20:30 ` Ivaylo Dimitrov
2014-02-06 0:39 ` Sebastian Reichel
2014-02-05 20:42 ` Pali Rohár
2014-02-06 0:25 ` Sebastian Reichel [this message]
2014-02-16 23:04 ` Pavel Machek
2014-02-17 21:30 ` [PATCHv2] " Sebastian Reichel
2014-02-21 23:08 ` Tony Lindgren
2014-03-01 21:32 ` Pali Rohár
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=20140206002512.GA654@earth.universe \
--to=sre@debian.org \
--cc=freemangordon@abv.bg \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox