Rename pmap_is_write() to pmap_l3_writable().

[markj]

Summary

This is consistent with pmap_l3_valid(), for instance. Fix style bugs
along the way. No functional change intended.

Test Plan

Booted under QEMU and spike.

[jhb]

sys/riscv/riscv/pmap.c

360

If we support superpages eventually then we might not want l3 in this name? That might be true for pmap_l3_valid as well? (Or will we only use this function on leaf PTEs?)

[markj]

sys/riscv/riscv/pmap.c

360

I was wondering about that too, as I'm starting to work on superpage support. We'll probably eventually have a use for an is_writable predicate for superpage mappings (ditto for the other predicates below). One wrinkle, though, is that we use distinct types (pd_entry_t vs. pt_entry_t). I'm not sure if that indicates that we should instead use a macro or just test bits inline. I lean somewhat towards the latter, since the flag names are pretty clear.

[jhb]

sys/riscv/riscv/pmap.c

360

I think it is also probably readable to just test bits inline. What does amd64 do? That's probably the best pmap to be copying from.

[markj]

sys/riscv/riscv/pmap.c

360

amd64 is hamstrung by the fact that the bit definitions vary depending on the pmap type, so it's more or less forced to look up the definition once and then use inline tests.

I'll think about it a bit more, but I'm inclined to just get rid of these predicates and inline everything. I'll upload the diff here once that's done.

[markj]

• Get rid of the (inconsistently used) predicates and just use inline tests.

sys/riscv/riscv/pmap.c

 .Op Fl t Ar trstr
 .Ar command
 .Sh DESCRIPTION
 The
 .Nm
 utility enables kernel trace logging for the specified processes.
 Kernel trace data is logged to the file
 .Pa ktrace.out .
-The kernel operations that are traced include system calls,
+The kernel operations that are traced include system calls
+.Pq see Xr intro 2 ,
 .Xr namei 9
-translations, signal processing, and
+translations, signal processing
+.Pq Xr sigaction 2 ,
+and
 .Tn I/O .
 .Pp
 Once tracing is enabled on a process, trace data will be logged until
 either the process exits or the trace point is cleared.
 A traced process can generate enormous amounts of log data quickly;
 It is strongly suggested that users memorize how to disable tracing before
 attempting to trace a process.
 The following command is sufficient to disable tracing on all user-owned

 .Dl $ ktrace -c -f tracedata
 .Pp
 Disable tracing of all user-owned processes:
 .Dl $ ktrace -C
 .Sh SEE ALSO
 .Xr dtrace 1 ,
 .Xr kdump 1 ,
 .Xr truss 1 ,
+.Xr intro 2 ,
 .Xr ktrace 2 ,
+.Xr sigaction 2 ,
 .Xr utrace 2 ,
 .Xr capsicum 4 ,
 .Xr namei 9
 .Sh HISTORY
 The
 .Nm
 command appeared in
 .Bx 4.4 .
 .Sh BUGS
 Only works if
 .Ar trfile
 is a regular file.