From: Philipp Rumpf <Philipp.H.Rumpf@mathe.stud.uni-erlangen.de>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Matthew Wilcox <Matthew.Wilcox@genedata.com>,
parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] pgtable.h:acc_rights()
Date: Sun, 7 Nov 1999 14:02:28 +0100 [thread overview]
Message-ID: <19991107140228.F14009@mathe.stud.uni-erlangen.de> (raw)
In-Reply-To: <19991106214859.A1743@alpha.franken.de>
> the real problem is, that we don't have a working copy on write at the
> moment. So whenever the first access to COW page is a read access, every
> write access afterwards will lead to an unhandled page fault (which causes
> a panic at the moment).
Actually, there is some code there to explain this. I never realized we did
differentiate between read/write accesses and thought we were still hardcoding
a write access. This shouldn't be too difficult to work around.
Philipp Rumpf
prev parent reply other threads:[~1999-11-07 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-06 16:20 [parisc-linux] pgtable.h:acc_rights() Matthew Wilcox
1999-11-06 19:51 ` Philipp Rumpf
1999-11-06 20:48 ` Thomas Bogendoerfer
1999-11-07 13:02 ` Philipp Rumpf [this message]
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=19991107140228.F14009@mathe.stud.uni-erlangen.de \
--to=philipp.h.rumpf@mathe.stud.uni-erlangen.de \
--cc=Matthew.Wilcox@genedata.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=tsbogend@alpha.franken.de \
/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