file-system -> file system
make (most) lines shorter than 80 chars
use more appropriate macros
fix a few typos
add two XXX for wrong sentences I'm not sure how to fix properly
was developed as part of Google's Summer of Code 2005 program. This
change adds the kernel code, the mount_tmpfs utility, a regression test
suite and does all other related changes to integrate these.
The file-system is still *experimental*. Therefore, it is disabled by
default in all kernels. However, as typically done, a commented-out
entry is added in them to ease its setup.
Note that I haven't commited the required mountd(8) changes to be able
to export tmpfs file-systems because NFS support is still very unstable
and because, before enabling it, I'd like to do some other changes.
OK'ed by my project mentor, William Studenmund (wrstuden@).
no need to swap byteorder.
Whele here, change style of some byteswap ops from
foo = bar();
foo = ahc_htole32(foo);
to
foo = ahc_htole32(bar());
XXX: I leave ahc_htole32() usage for union ins_formats for now
XXX: though it may be better to use byte-shift ops rather than byteswap.
/*XXX this is straightforward to fix but I have no time right now */
tasks so we don't lose track of them.
Format and purpose are documented at the top of the file.
Discussed with Christos and others
per floppy for a while. (The rest of the sums are ok).
Change the 'padded' size to include all the space in the last 8k block
of the tar file.
Similarly if the image doesn't fit, report the exact amount of overflow.
instead to always trying PG_RW and falling back to PG_RO if this fails.
Use uvm_map_checkprot() in IOCTL_PRIVCMD_MMAP and IOCTL_PRIVCMD_MMAP_BATCH
to compute the appropriate vm_prot_t for pmap_remap_pages().
Thanks to Jed Davis for pointing out uvm_map_checkprot().
In pmap_remap_pages() new mappings are created (PG_RW|PG_M). When saving
a domain, the hypervisor will refuse to map the foreing pages RW.
As a temporary measure, retry the mapping read-only if PG_RW fails, so that
domain save will work. Also fix the PTP's wire_count if the MMU update
fails (prevent a kernel panic).
Since all the x_<prog> get build into crunched binaries (which does a
reachover build these days) I suspect this is entirely unnecessary.
But having deleted x_dmesg we must ensure it doesn't go there.
