| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
It could occasionally happen that the child process spawned less(1)
before the parent process passed the control of the terminal to the
child, and in that case, less(1) sometimes complained "Stopped (tty
output)". Issue reported by naddy@.
|
|
|
|
If you prefer "lighter" punctuation and one space between sentences,
for example:
Mr and Mrs Jones are from the UK. They arrived today.
over more liberal use of full stops and double spaces between
sentences:
Mr. and Mrs. Jones are from the U.K. They arrived today.
then toggling 'sentence-end-double-space' will make mg's
fill-paragraph function format text using one space instead of two
(the default) between sentences. However, be careful, should you have
a double spaced document and accidentally "format" it to have single
spaces, then you may have a problem. mg won't be able to revert the
formatting for you (unless you have a previous version of the text in
the "undo" history, or are using mg's backup facility and haven't
opened and saved multiple times!).
Comments from schwarze@
|
|
performance notably.
Discussed with Miod long ago
Tested by and ok jasper@
|
|
|
|
This prevents console clutter about spurious UART interrupts.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
still a bit magical, but good enough for now.
|
|
node in /dev, that services all bpf consumers (up to 1024). Also,
disallow the usage of all but the first minor device, so accidental use
of another minor device will attract attention.
Cloning bpf offers some advantages:
- Users with high bpf usage won't have to clutter their /dev with device
nodes.
- A lot of programs in base use a pattern like this to acces bpf:
int fd, n = 0;
do {
(void)snprintf(device, sizeof device, "/dev/bpf%d", n++);
fd = open(device, mode);
} while (fd < 0 && errno == EBUSY);
Those can now be replaced by a simple open(), without loop.
ok mikeb
"right time in the cycle to try" deraadt
|
|
on (at least) various HP laptops that previously had no working keyboard
after resuming from 'zzz'.
Reported by Aleksandar Lakic, who also verified several versions of the
diff during development, thanks.
discussed with miod and kettenis, tested by many others on tech@ - thanks.
|
|
architectural performance counters, instead of cpu family/model values.
Fixes a panic seen on some hypervisors when pctr(1) is used when the
hypervisor masks out the counters.
Reported by Hiltjo Posthuma, thanks.
ok mikeb@, guenther@
|
|
this should be enough to make io reliable
|
|
we run with 2 entries for the nvme controller identify, and then bump it
up to cover the maxphys divided by the page size we negotiate.
|
|
|
|
prpe is short for Physical Region Page Entry. this is where long
lists of dma regions go when they wont fit into a submission queue
entry.
|
|
nvme and the host cpu need to agree on the page size because its
the implicit size of the elements in the chips scatter gather lists.
if the min nvme size is greater than the cpus page size then we
cant guarantee that io buffers are contig for nvme pages.
nvme 1.1 provides an alternative sgl mechanism, so if this really
becomes a problem in the future we can fix it on 1.1 and later
devices.
|
|
it ends up being a use after free, which disagrees with the midlayer.
|
|
again, only called during autoconf which is a kind of process context.
|
|
nvme 1.0 does not use conventional scatter gather lists of
address+length pairs. instead, it simply expects a list of page
addresses. this should be ok if we only feed it single VA chunks
which map directly to only whole physical pages.
nvme 1.1 introduced another scather format, but still accepts the
1.0 format too. we'll stick to the 1.0 format so we can support 1.0
devs.
|
|
this means we'll notice io completions.
|
|
|
|
|
|
Requested by deraadt@
|
|
ive only tested reads, and not very big ones.
nvme 1.0 has a very stupid/naive idea about what constitutes a
scatter gather list. it assumes io is in whole pages in memory, but
i dont know if that is true in our kernel.
this could be cleaned up a bit, and it currently runs with a single
opening for the whole scsi layer and a bunch of magic values for
the size and number of the io queues.
|
|
EVP_aead_chacha20_poly1305_ietf().
|
|
plaintext for the regress test case.
|
|
|
|
this is necessary to run reads and writes against the device.
|
|
|
|
at the moment this just pretends the commands completed fine.
|
|
read cap 16 claims the devices are thin.
|
|
most values are as per the nvm to scsi mapping guide. this doesnt
do vpd at all, so no devids or serial numbers just yet.
|
|
the same name in sections with an alphabetical suffix; same logic
as in main.c rev. 1.171.
|
|
|
|
probe issues a namespace identify against the "target". if it works
it stashes a copy of the info, otherwise it tells the midlayer to
avoid it.
free gets rid of the stashed info.
|
|
|
|
|
|
|
|
the same name in sections with an alphabetical suffix (on OpenBSD,
mostly 3p), restoring behaviour of the traditional BSD man(1) that
got lost in the switch to the mandoc-based implementation.
Issue reported by jsg@, using an idea by mikeb@ for the solution,
and at least afresh1@ and jasper@ also seem in favour of the direction.
|
|
so far the only useful info is namespace identify info
|
|
the nn is used to size the scsi bus, and the controller identify is used
to build responses for various scsi commands.
|
