From: "Ulrich Weigand" <Ulrich.Weigand@de.ibm.com>
To: John Alvord <jalvo@mbay.net>
Cc: Jeff Mahoney <jeffm@suse.com>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [SOLVED + PATCH]: documented Oops running big-endian reiserfs on parisc architecture
Date: Tue, 4 Sep 2001 19:04:37 +0200 [thread overview]
Message-ID: <OFF77409CC.FF70C78C-ONC1256ABD.005CEB95@de.ibm.com> (raw)
John Alvord wrote:
>> It is only *atomic* accesses (those implemented using the S/390
>> compare-and-swap instruction) that need to be word aligned; this
includes
>> the atomic bit operations that reiserfs appears to be using.
>
>Aren't their some other "must align" instructions like CVB? Or have they
>all been relaxed...
CVB doesn't have any alignment requirement (I'm not sure it ever had one).
Execpt for the 'atomic' operations (CS, CSG, CDS, CDSG, LPQ, STPQ, PLO)
I know only of two general-purpose instructions with operand alignment
requirement, and that's LAM and STAM. As access registers are not
normally used in Linux this shouldn't be a problem.
There *is* a whole bunch of privileged system instructions that have
various aligment requirements; but here I'd say it's fair to require the
user to provide correct aligment in these special cases.
Mit freundlichen Gruessen / Best Regards
Ulrich Weigand
--
Dr. Ulrich Weigand
Linux for S/390 Design & Development
IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032 Boeblingen
Phone: +49-7031/16-3727 --- Email: Ulrich.Weigand@de.ibm.com
next reply other threads:[~2001-09-04 17:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 17:04 Ulrich Weigand [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-04 22:55 Ulrich Weigand
2001-09-04 14:34 Ulrich Weigand
2001-09-04 15:02 ` Richard B. Johnson
2001-09-04 16:09 ` John Alvord
[not found] <20010902105538.A15344@middle.of.nowhere.suse.lists.linux.kernel>
[not found] ` <20010902150023.U5126@parcelfarce.linux.theplanet.co.uk.suse.lists.linux.kernel>
[not found] ` <20010902195717.A21209@middle.of.nowhere.suse.lists.linux.kernel>
[not found] ` <20010903003437.A385@linux-m68k.org.suse.lists.linux.kernel>
[not found] ` <20010903213835.A13887@fury.csh.rit.edu.suse.lists.linux.kernel>
2001-09-04 9:44 ` Andi Kleen
2001-09-04 12:50 ` Jeff Mahoney
2001-09-04 10:04 ` David S. Miller
2001-09-04 10:25 ` Andi Kleen
2001-09-04 10:29 ` David S. Miller
2001-09-03 12:08 Ulrich Weigand
2001-09-03 13:14 ` Ralf Baechle
2001-09-03 22:24 ` David S. Miller
2001-09-08 1:41 ` Linus Torvalds
2001-09-02 8:55 thunder7
2001-09-02 14:00 ` [parisc-linux] " Matthew Wilcox
2001-09-02 17:57 ` [SOLVED + PATCH]: " thunder7
2001-09-02 22:34 ` Richard Zidlicky
2001-09-04 1:38 ` Jeff Mahoney
2001-09-02 23:08 ` David S. Miller
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=OFF77409CC.FF70C78C-ONC1256ABD.005CEB95@de.ibm.com \
--to=ulrich.weigand@de.ibm.com \
--cc=ak@suse.de \
--cc=jalvo@mbay.net \
--cc=jeffm@suse.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®