Since the stack is top-down, entries appear in reverse order.

* 'master' of github.com:/avikivity/osv:
  fs: directory entry cache
  bootfs: don't create root directory objects
  fs: drop bootfs::subdir()
  fs: piece-wise path lookup
  fs: reference count files

Store directory entries in a hash table for future lookup.

Eventually loader dump them into the console for debug

We need one object, so we can use it as a key in the cache.  Store it in
the filesystem object.

It interferes with the upcoming cache lookup.  Use the existing metadata
instead to look for a directory.

real filesystems (and /proc, our immediate target) look up files incrementally
by each component.  Apply that to our filesystem infrastructure.

A new object is introduced, dir, representing a directory.  Lookup operations
are deferred to this object.

avoid leakage

This takes the short cut of using sse 4.1 for the implementation,
avoiding a coplicated C implementation.  Will work on Core and higher
processors.

override with 'make V=1'

needed to set up the initial TLS block

It is not an exception condition.

This allows generic code to include arch specific code, by eliding the
arch/x64/ prefix.

We will never build a single program containing code from two architectures,
so segregating arch-specific code into a separate namespace is not solving
any problem.  However it makes using arch-specific code from generic code
impossible.

Remove the 86 namespace to fix this.

The compiler complains that the varibles are not initialized, even though the
inout guarantees that they will be.  Initialize them anyway.