> Um, trying to clarify: S390. Also known as zSeries, big iron machine, uses
> its own weird processor design rather than x86, x86-64, arm, or mips
> processors.
Right. filemap_xip.c allows for an XIP filesystem. The only
filesystem that is supported is ext2. Even that requires a block
device driver thingy, which I don't understand, that's specific to the
s390.
> How does "struct page" enter into this?
Don't sweat it, it has to do with the way filemap_xip.c works.
> What I want to know is, are you saying execute in place doesn't work on things
> like arm and mips? (I so, I was unaware of this. I heard about somebody
> getting it to work on a Nintendo DS:
> http://forums.maxconsole.net/showthread.php?t=18668 )
XIP works fine on things like arm and mips. However there is mixed
support in the mainline kernel for it. For example, you can build an
XiP kernel image for arm since like 2.6.10 or 12. Also MTD has an XiP
aware mode that protects XiP objects in flash from get screwed up
during programs and erases. But there is no mainlined solution for
XiP of applications from the filesystem. However there have been
patches for cramfs to do this for years. They are kind of messy and
keep getting rejected. I do have a solution in the works for this
part of it - http://axfs.sf.net.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
