Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Michael S.Zick <mszick@pflash.com>
To: parisc-linux@lists.parisc-linux.org
Cc: Albert Strasheim <fullung@ilink.nis.za>
Subject: Re: [parisc-linux] 720 - some progress
Date: Sat, 29 Sep 2001 13:36:16 -0500	[thread overview]
Message-ID: <01092913361601.00620@localhost.localdomain> (raw)
In-Reply-To: <20010929080006.A25136@dogbert.localdomain>

On Saturday 29 September 2001 01:00 am, Albert Strasheim wrote:
> regs->iaoq[0] = regs->iaoq[1];
> regs->iaoq[1] = regs->iaoq[0] + 4;
>
> Is this right, or should I leave Jurij's code?
>
Hello Albert,

An observation:
regs->iaoq[1] is the "following instruction" - where "following" means "in 
execution order".  So replacing the emulated instruction with this seems the 
obvious thing to do.

BUT...
Without examining the instruction (which was at iaoq[1] and is now at 
iaog[0]) I don't think it is safe to assume that the instruction following 
that one in execution order is at iaoq[1]+4 !!  (Branches, nullified 
instructions, conditional instructions, etc).

Perhaps...
Instead of trying to compute (determine) what is the next instruction in 
execution order following iaoq[1] ; iaoq[1] could be set to a value that 
would cause the hardware pipeline to fetch the correct following instruction.

Or perhaps...
A way could be found to use whatever "single step" controls are available to 
get the return made to iaoq[1] instead of iaoq[0] and leave the queues along.

Also...
What about the space register queue?  Might these instructions be in a 
different address space?

Mike

  parent reply	other threads:[~2001-09-29 18:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-27 14:42 [parisc-linux] 720 - some progress Jurij Smakov
2001-09-28  8:49 ` Jochen Friedrich
2001-09-28  9:19   ` Matthew Wilcox
2001-09-28  8:54 ` Matthew Wilcox
2001-09-29  6:00   ` Albert Strasheim
2001-09-29  8:30     ` Albert Strasheim
2001-09-29 10:01       ` Albert Strasheim
2001-09-29 11:17     ` Jochen Friedrich
2001-09-29 11:45       ` Albert Strasheim
2001-09-29 13:23         ` Jochen Friedrich
2001-09-29 18:36     ` Michael S.Zick [this message]
2001-09-29 22:19       ` Michael S.Zick
  -- strict thread matches above, loose matches on Subject: below --
2001-10-01 16:06 Michael S. Zick
2001-09-30  7:12 John Marvin
     [not found] <200109280925.FAA18777@mail.lokmail.net>
2001-09-28 16:24 ` Albert Strasheim
2001-09-28 18:48   ` Jochen Friedrich
2001-09-29 17:48     ` Carlos O'Donell Jr.
2001-09-27 16:32 Jurij Smakov
2001-09-27 19:18 ` Albert Strasheim
2001-09-27 12:23 Jurij Smakov
2001-09-27 13:04 ` Albert Strasheim
2001-09-27 13:45 ` Matthew Wilcox
2001-09-27 10:03 Jurij Smakov
2001-09-27 11:15 ` Jochen Friedrich
2001-09-27  9:09 Jurij Smakov
2001-09-27 11:11 ` Jochen Friedrich
2001-09-26 22:26 Jochen Friedrich
2001-09-27  0:07 ` Albert Strasheim

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=01092913361601.00620@localhost.localdomain \
    --to=mszick@pflash.com \
    --cc=fullung@ilink.nis.za \
    --cc=parisc-linux@lists.parisc-linux.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