From: Nicolas Pitre <nico@cam.org>
To: Jared Hulbert <jaredeh@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Josh Boyer <jwboyer@gmail.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Advanced XIP File System
Date: Wed, 03 May 2006 11:57:26 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0605031151120.28543@localhost.localdomain> (raw)
In-Reply-To: <6934efce0605030845o6d313681x6b89bef71c28b3a9@mail.gmail.com>
On Wed, 3 May 2006, Jared Hulbert wrote:
> > We
> > only need to mark those pages as absent in the page tables if we ever
> > schedule to userspace while the flash is in a mode other than read mode.
> > Then handle the page fault by switching the flash back or waiting for
> > it.
>
> Where would we do this? In each MTD driver? A new generic aops function?
First, is it worth it?
IOW, are there real setups out there wishing to have user space XIP
while the kernel itself isn't XIP?
Because right now you only need to turn on CONFIG_MTD_XIP for XIP user
space to just work, regardless of whether the kernel itself is XIP or
not. And of course CONFIG_MTD_XIP is mandatory if you want to write to
flash with a XIP kernel.
Nicolas
next prev parent reply other threads:[~2006-05-03 15:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 21:53 Jared Hulbert
2006-05-03 0:00 ` Arnd Bergmann
2006-05-03 1:59 ` Jared Hulbert
2006-05-03 2:27 ` Josh Boyer
2006-05-03 5:04 ` Jared Hulbert
2006-05-03 8:31 ` David Woodhouse
2006-05-03 19:14 ` Pavel Machek
2006-05-04 16:32 ` Jared Hulbert
2006-05-03 0:56 ` Josh Boyer
2006-05-03 3:17 ` Nicolas Pitre
2006-05-03 10:41 ` Josh Boyer
2006-05-03 12:11 ` David Woodhouse
2006-05-03 15:45 ` Jared Hulbert
2006-05-03 15:52 ` David Woodhouse
2006-05-03 15:57 ` Nicolas Pitre [this message]
2006-05-03 16:01 ` David Woodhouse
2006-05-03 16:10 ` Nicolas Pitre
2006-05-03 5:11 ` Jared Hulbert
2006-05-03 12:50 ` Mark Lord
2006-05-03 15:33 ` Jared Hulbert
2006-05-03 13:05 ` Jörn Engel
2006-05-03 15:31 ` Jared Hulbert
2006-05-03 15:47 ` Jörn Engel
2006-05-03 15:58 ` Jared Hulbert
2006-05-03 17:03 ` Jörn Engel
2006-05-03 18:58 ` Jared Hulbert
2006-05-03 16:38 ` Jan Engelhardt
2006-05-03 18:54 ` Jared Hulbert
2006-05-03 23:17 ` Josh Boyer
2006-05-03 23:48 ` Jared Hulbert
2006-05-04 0:21 ` Josh Boyer
2006-05-03 22:49 ` David Woodhouse
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=Pine.LNX.4.64.0605031151120.28543@localhost.localdomain \
--to=nico@cam.org \
--cc=dwmw2@infradead.org \
--cc=jaredeh@gmail.com \
--cc=jwboyer@gmail.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®