public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] p4080ds starts OS with MSR[EE]=1 and DEC armed?
Date: Tue, 15 Mar 2011 15:24:43 -0500	[thread overview]
Message-ID: <20110315152443.61f52f57@schlenkerla> (raw)
In-Reply-To: <AANLkTinksEf07RLD3OoQuk+f+Hght7nDZP=cc8VpqMNy@mail.gmail.com>

On Tue, 15 Mar 2011 14:21:03 -0500
Timur Tabi <timur@freescale.com> wrote:

> On Sun, Mar 13, 2011 at 10:46 AM, Jimi Xenidis <jimix@watson.ibm.com> wrote:
> 
> > Turns out that TSR[DIS] was on when my program took over, and this is ePAPR legal.
> > I need to reset the DEC in my code.
> 
> I wonder if it should be legal.  What value does it have to leave a
> pending decrementer interrupt when booting the OS?  That just forces
> every OS to program the decrementer and clear DIS before enabling
> interrupts.

The OS should ensure that timer interrupts are functioning the way it wants
before it enables interrupts -- but in any case, once it enables interrupts
it should be able to handle any interrupt that is enabled.  There's no
general need to clear DIS.

There's actually no good way for boot software to ensure that TSR[DIS] is
clear, other than stopping the timebase (not allowed, or at least shouldn't
be), or assuming that the OS will take control of the decrementer within a
reasonable amount of time.  We could require that TCR[DIE] be clear, but
that just imposes an extra requirement on boot software for no good reason
-- and in general, we want to minimize the extent to which we trust boot
software to do something specific.  Especially if it's something that won't
show up as a problem with most client software, until someone decides to
rely on it.

-Scot

  reply	other threads:[~2011-03-15 20:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-03 14:59 [U-Boot] p4080ds starts OS with MSR[EE]=1 and DEC armed? Jimi Xenidis
2011-03-12 22:56 ` Kumar Gala
2011-03-13 15:46   ` Jimi Xenidis
2011-03-15 19:21     ` Timur Tabi
2011-03-15 20:24       ` Scott Wood [this message]
2011-03-15 21:16         ` Jimi Xenidis
2011-03-15 21:21           ` Timur Tabi
2011-03-15 21:22             ` Jimi Xenidis
2011-03-15 21:22           ` Scott Wood
2011-03-15 21:24             ` Scott Wood
2011-03-14 18:09   ` Scott Wood
2011-03-14 19:39     ` Jimi Xenidis
2011-03-15  5:46       ` Kumar Gala
2011-03-14 21:25     ` Kumar Gala
2011-03-14 21:37       ` Scott Wood
2011-03-15  5:39         ` Kumar Gala
2011-03-15 16:11           ` Scott Wood

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=20110315152443.61f52f57@schlenkerla \
    --to=scottwood@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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