Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Philipp Rumpf <prumpf@suse.de>
To: Grant Grundler <grundler@cup.hp.com>
Cc: Ryan Bradetich <rbradetich@uswest.net>,
	Parisc Linux <parisc-linux@thepuffingroup.com>
Subject: Re: [parisc-linux] Questions understanding exec_kernel
Date: Wed, 22 Sep 1999 15:32:24 +0200	[thread overview]
Message-ID: <19990922153224.Z5481@suse.de> (raw)
In-Reply-To: <199909220426.VAA27105@milano.cup.hp.com>; from Grant Grundler on Tue, Sep 21, 1999 at 09:26:50PM -0700

> >  [Question: Page 5-149 from the PA-RISC 1.1 Architecture and Instruction
> > Set Reference Manual states: "Level 0:  If the target control register
> > is CR 8, 9, 12, 13, 17, or 20, this instructin executes as a null
> > instruction."  I am assuming we are running at level 0 since the rfi
> > command required running at level 0, so what is the difference between a
> > null instruction and a nop?]

There is none.  Null instructions (here) refer to instructions ignored since
they don't apply to the specific hardware.  Nops are usually regular forms of
arithmetic / logical instructions that happen to do nothing.

> That's an easy one:
> Nullfied instructions are simple ignored - output discarded.

Except we're not talking about nullified instructions :)

	Philipp Rumpf

  parent reply	other threads:[~1999-09-22 13:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-22  1:12 [parisc-linux] Questions understanding exec_kernel Ryan Bradetich
1999-09-22  4:26 ` Grant Grundler
1999-09-22  6:45   ` [parisc-linux] C360 boot problem Hannu Martikka
1999-09-22 13:34     ` Philipp Rumpf
1999-09-22 13:32   ` Philipp Rumpf [this message]
1999-09-22 12:46 ` [parisc-linux] Questions understanding exec_kernel Hai Vo-Ba
1999-09-22 13:36   ` Philipp Rumpf
1999-09-22 13:29 ` Philipp Rumpf

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=19990922153224.Z5481@suse.de \
    --to=prumpf@suse.de \
    --cc=grundler@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=rbradetich@uswest.net \
    /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