From: Grant Grundler <grundler@parisc-linux.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Grant Grundler <grundler@parisc-linux.org>,
artem.alimarine@stromasys.com, linux-parisc@vger.kernel.org
Subject: Re: Wierd code in Entry.S
Date: Fri, 10 Jul 2009 09:36:20 -0600 [thread overview]
Message-ID: <20090710153620.GB28778@lackof.org> (raw)
In-Reply-To: <20090710001506.A2C43507E@hiauly1.hia.nrc.ca>
On Thu, Jul 09, 2009 at 08:15:04PM -0400, John David Anglin wrote:
...
> > > The DEPI instruction on a 64-bit machine sets bit 44=32+12,
> > > whereas we use the value as the argument to IDTLBT, which expects bit 12
> > > to be used instead.
> > >
> > > Does it mean that the U-bit is never set and the
> > > authorization id gets corrupted???
> >
> > U-bit will get set only if _PAGE_NO_CACHE_BIT+32 is also set.
...
> To me, it looks like the instruction should be a depdi. See the preceding
> deposit of PAGE_USER. According to the IDTLBT description, the U bit is
> bit 12 in r2, not bit 44.
Yes - I see it now too. Excellent catch.
But I'm still wondering what the effect of this bug will be.
The first order (not setting U-bit) should only affect ZX1 (pa8800/pa8900)
machines. Those have uncacheable IO space between 2GB-4GB physical address.
My guess is the machines should HPMC since the CPU would attempt to access
those ranges as a cacheline read/write instead of sub-cacheline transactions.
It's not clear from the arch manual what happens if bit 44 is set in R2.
I didn't look far enough to see where the auth ID gets corrupted.
thanks,
grant
>
> rp3440 boots with the depdi change. Building gcc...
>
> Dave
> --
> J. David Anglin dave.anglin@nrc-cnrc.gc.ca
> National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
next prev parent reply other threads:[~2009-07-10 15:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 13:11 Wierd code in Entry.S Artem Alimarine
2009-07-09 22:55 ` Grant Grundler
2009-07-10 0:15 ` John David Anglin
2009-07-10 15:36 ` Grant Grundler [this message]
2009-07-10 15:55 ` John David Anglin
2009-07-10 16:18 ` James Bottomley
2009-07-10 18:48 ` John David Anglin
2009-07-15 6:38 ` Grant Grundler
2009-07-15 12:41 ` James Bottomley
2009-07-15 15:00 ` Matthew Wilcox
2009-07-22 5:34 ` Grant Grundler
2009-07-10 16:11 ` Artem Alimarine
2009-07-15 6:40 ` Grant Grundler
2009-07-10 15:52 ` James Bottomley
2009-07-10 16:25 ` Artem Alimarine
2009-07-11 0:12 ` John David Anglin
2009-07-11 0:30 ` John David Anglin
2009-07-11 1:05 ` John David Anglin
2009-07-12 19:40 ` John David Anglin
2009-07-13 1:15 ` Kyle McMartin
2009-07-13 1:44 ` John David Anglin
2009-07-13 1:54 ` Kyle McMartin
2009-07-13 2:18 ` John David Anglin
2009-07-10 7:31 ` Artem Alimarine
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=20090710153620.GB28778@lackof.org \
--to=grundler@parisc-linux.org \
--cc=artem.alimarine@stromasys.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=linux-parisc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.