From: Grant Grundler <grundler@cup.hp.com>
To: Matthew Wilcox <willy@thepuffingroup.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] PDC calls on the C3000
Date: Mon, 17 Jan 2000 10:02:59 -0800 [thread overview]
Message-ID: <200001171802.KAA18011@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Mon, 17 Jan 2000 10:57:34 PST." <20000117105734.L11300@thepuffingroup.com>
Matthew,
The hair on the back of my neck stood up when I read the second part...
Matthew Wilcox wrote:
...
> So the CPU was helpfully sign-extending the address of real_stack
...
> The tophys macro was clearing the `c' to leave us with
...
> which would work if PDC recognised we were being called from narrow mode
> (presumably PDC does on C360 hardware, or we wouldn't've had it working
> on that machine).
I'm thinking the inconsistency is possibly a firmware "bug" where either
the C360 or C3000 isn't behaving "right". Can anyone comment on what
the expected behavior is?
> I changed the tophys macro to:
>
> zdep gr, 31, 30, gr
>
> which takes the rightmost 30 bits from the register, zeroes the whole
> register and then stores them back into it:
> 0xffff'ffff'c0xx'xxxx
> becomes
> 0x0000'0000'00xx'xxxx
> and now PDC is happy, and so am I.
This is where the hair on the back of my neck went up.
The problem is on L-class and N-class machine we have
I/O and memory addresses which are > 4GB. And PDC will really
be confused on those platforms.
I wonder if the right answer is for the ldil instruction to NOT sign extend.
I don't know how to acheive that and I don't see us getting to L-class
without addressing that issue. I'm also hoping fixing this behavior will
make the firmware behavior differences (c360 vs C3000) irrelevant.
thanks,
grant
Grant Grundler
Unix Development Lab
+1.408.447.7253
next prev parent reply other threads:[~2000-01-17 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-17 15:57 [parisc-linux] PDC calls on the C3000 Matthew Wilcox
2000-01-17 18:02 ` Grant Grundler [this message]
2000-01-17 18:34 ` Matthew Wilcox
2000-01-17 18:48 ` Alex deVries
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=200001171802.KAA18011@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=willy@thepuffingroup.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