Re: wscons/wsmux question

2017-06-17 Thread Paul Goyette
On Sun, 18 Jun 2017, Thor Lancelot Simon wrote: On Sun, Jun 18, 2017 at 12:14:41PM +0800, Paul Goyette wrote: Would anyone object if I were to remove all of the "#if NWSMUX > 0" conditionals, and simply require the wsmux code to be included (via files.wscons) whenever any child dev

Re: wscons/wsmux question

2017-06-17 Thread Thor Lancelot Simon
On Sun, Jun 18, 2017 at 12:14:41PM +0800, Paul Goyette wrote: > > Would anyone object if I were to remove all of the "#if NWSMUX > 0" > conditionals, and simply require the wsmux code to be included (via > files.wscons) whenever any child dev (wsdisplay, wskbd, wsmouse, or wsbell) > is

Re: wscons/wsmux question

2017-06-17 Thread Paul Goyette
On Thu, 15 Jun 2017, Paul Goyette wrote: While recently working with Nat to get the wsbell(4) device working, I've noticed that both wsdisplay(4) and wsmouse(4) (as well as the new wsbell(4)) have lots of code conditionally compiled based on "NWSMUX 0" (which is defined in wsmux.h resulting

re: ARM pmap

2017-06-17 Thread matthew green
Michael writes: > Hello, > > On Fri, 16 Jun 2017 14:30:18 +1000 > matthew green wrote: > > > > Or just tar xpzf ... - ours at least unlinks files before writing them, > > > install(1) instead of cp(1) for single files. > > > > FWIW, it's temp file + rename, not unlink. >

kpreempt_disable and lwp migration

2017-06-17 Thread coypu
Hello tech-kern, It seems that kpreempt_disable() does not prevent a lwp from migrating. The assumption that it does is in some places in NetBSD. This came up as I am using a non-MPSAFE filesystem (LFS), and had panics in x86 pmap's pmap_extract, which states it makes this assumption in a

Re: ARM pmap

2017-06-17 Thread Michael
Hello, On Fri, 16 Jun 2017 14:30:18 +1000 matthew green wrote: > > Or just tar xpzf ... - ours at least unlinks files before writing them, > > install(1) instead of cp(1) for single files. > > FWIW, it's temp file + rename, not unlink. Hmm, the man page says:

Re: kernel aslr: someone interested?

2017-06-17 Thread Kamil Rytarowski
On 17.06.2017 12:25, Maxime Villard wrote: > Le 23/03/2017 à 18:30, Maxime Villard a écrit : >> I have some plans to implement kernel aslr on amd64. Actually, a few >> months >> ago I wrote set of patches for the bootloader and the kernel, and also a >> complete kernel relocator. As far as I can

Re: kernel aslr: someone interested?

2017-06-17 Thread Maxime Villard
Le 23/03/2017 à 18:30, Maxime Villard a écrit : I have some plans to implement kernel aslr on amd64. Actually, a few months ago I wrote set of patches for the bootloader and the kernel, and also a complete kernel relocator. As far as I can test, everything works correctly and reliably; the whole