Whitespace
Implement rumpcomp_sync_icache() hyprecall for arm and add
a barebone implementation of arm cache ops to librumpkern_sljit.
How to deal with src/external/mit/lua/src: No such file or directory
More general advice about "cvs [update aborted]... No such file
or directory".

Also invent a "Cause:" keyword for use in "Symptom:/Cause:/Fix" sections.

Also add a note near the top of the file saying that there are
several sections marked by "^^^".
No functional change:
- Add missing prototypes.
- Rename functions for consistency and clarify.
- KNF.
No functional change:
- Grouping functions.
- KNF.
In the RUMP_KERNEL_IS_LIBC case, account for WEAKASM, i.e. create a
_sys_foo strong alias, and _foo and foo weak aliases.  This actually
treats all syscalls as WEAKASM, but it's probably(?) harmless, and saves
us from manual work a la libc.  Fixes at least pthread_cancelstub.
regen
split PRU_SENDOOB and PRU_RCVOOB function out of pr_generic() usrreq
switches and put into separate functions
  xxx_sendoob(struct socket *, struct mbuf *, struct mbuf *)
  xxx_recvoob(struct socket *, struct mbuf *, int)

  - always KASSERT(solocked(so)) even if request is not implemented

  - replace calls to pr_generic() with req = PRU_{SEND,RCV}OOB with
    calls to pr_{send,recv}oob() respectively.

there is still some tweaking of m_freem(m) and m_freem(control) to come
for consistency.  not performed with this commit for clarity.

reviewed by rmind
Bind i810 dcache pages at the requested offset, not at VA start.

From John D Baker in PR xsrc/48344.

XXX pullup to 6 (by patch)
Also unbind the right offset.
For the unbind code to work the bind code must set the offset.
Tweak style, make it compile...oops.
RCS IDs do not go in header files.
Omit redundant vga_is_console test.

This was a copypasta error -- before it tested iot then memt -- but I
see no evidence that passing memt to vga_is_console is ever sensible.
Rename sljitarch.h to sljit_machdep.h.
Sync DIAGNOSTIC performance comments with historical reality.

Somehow, options(4) ended up with a bizarre claim that DIAGNOSTIC can
reduce performance by 15%.  While that might have been true at some
isolated point due to a bug, it's an outlier.  Since at least 2BSD,
DIAGNOSTIC has added asserts, resulting in at most
difficult-to-perceived performance degredation, and many people have
been running production systems (meaning systems they intend to use,
rather than debugging targets) with this option.    (The decision a
while ago to enable DIAGNOSTIC in -current's GENERIC reflects this; if
it really were a 15% hit such enabling by default would be unreasonable.)
Fix typo. Bump date for previous.