From: Frank Rowand <frank_rowand@hp.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] depi?
Date: Tue, 16 Nov 1999 13:43:12 -0800 [thread overview]
Message-ID: <3831CFF0.F4B3CE3E@hp.com> (raw)
In-Reply-To: 19991116170819.B750@mathe.stud.uni-erlangen.de
Philipp Rumpf wrote:
>
> > This is just one of several recent messages dealing with the issues caused by
> > locating the kernel at virtual address 0xc0000000 instead of 0x00000000. I
> > still don't understand why the kernel can't be at zero, even though several
> > people have tried to explain it to me. Can anyone provide a clear
> > explanation?
>
> Advantages of mapping the kernel at 0xc000 0000 (or 0x8000 0000/0xe000 0000)
>
< stuff deleted >
>
> Disadvantages
>
- C code that needs to run in real mode seems to be rather fragile, given
Paul's recent experience with head.c. (I think it was Paul.)
- A single instance of code can't (easily) be coded to be able to run both
in real mode and in virtual mode.
- It's real easy to mis-code real mode assembly (eg. use the PA() macro when
it shouldn't be used or don't use it when it should be used).
- Issues with coherent I/O.
< stuff deleted >
-Frank
next prev parent reply other threads:[~1999-11-16 21:41 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-15 8:08 [parisc-linux] depi? Alex deVries
1999-11-15 7:24 ` Jeffrey A Law
1999-11-15 7:36 ` Stan Sieler
1999-11-15 8:25 ` Philipp Rumpf
1999-11-15 23:14 ` Frank Rowand
1999-11-16 0:26 ` John David Anglin
1999-11-16 12:39 ` Matthew Wilcox
1999-11-16 17:17 ` Philipp Rumpf
1999-11-16 8:26 ` Philippe Benard
1999-11-16 12:20 ` Alan Cox
1999-11-16 11:53 ` Philippe Benard
1999-11-16 12:58 ` Alan Cox
1999-11-16 15:55 ` John David Anglin
1999-11-17 13:00 ` Philipp Rumpf
1999-11-16 12:35 ` Matthew Wilcox
1999-11-16 16:08 ` Philipp Rumpf
1999-11-16 17:14 ` Alan Cox
1999-11-16 16:47 ` Philipp Rumpf
1999-11-16 17:50 ` Alan Cox
1999-11-17 0:06 ` Grant Grundler
1999-11-17 6:21 ` Philipp Rumpf
1999-11-17 18:57 ` Stan Sieler
1999-11-17 19:29 ` Philipp Rumpf
1999-11-17 20:01 ` Stan Sieler
1999-11-17 20:33 ` Philipp Rumpf
1999-11-16 21:43 ` Frank Rowand [this message]
1999-11-17 6:12 ` Philipp Rumpf
1999-11-17 18:56 ` Frank Rowand
1999-11-17 22:05 ` Philipp Rumpf
1999-11-17 22:39 ` John David Anglin
1999-11-17 22:52 ` Philipp Rumpf
1999-11-17 23:37 ` Stan Sieler
1999-11-18 0:09 ` Philipp Rumpf
1999-11-18 0:43 ` Frank Rowand
1999-11-18 1:35 ` Frank Rowand
1999-11-18 5:33 ` John David Anglin
1999-11-18 8:02 ` Philippe Benard
1999-11-18 20:37 ` John David Anglin
1999-11-18 22:38 ` Frank Rowand
1999-11-19 4:12 ` Philipp Rumpf
1999-11-19 9:08 ` Philippe Benard
1999-11-17 23:02 ` Frank Rowand
1999-11-17 23:25 ` Philipp Rumpf
1999-11-17 8:14 ` Philippe Benard
1999-11-15 8:19 ` 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=3831CFF0.F4B3CE3E@hp.com \
--to=frank_rowand@hp.com \
--cc=frowand@cup.hp.com \
--cc=parisc-linux@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