Re: kernel reordering and config -e

2017-11-22 Thread Paul B. Henson
On Wed, Nov 22, 2017 at 04:45:59PM +, Kevin Chadwick wrote: > I believe the second scenario would need /dev/mem access making it a > larger change than it first appears (config with a new option could > possibly save the original kernel file and compare the two kernel > files). Ah, I didn't

Re: kernel reordering and config -e

2017-11-22 Thread Kevin Chadwick
On Tue, 21 Nov 2017 12:41:41 -0800 > Or would you want > something more integrated into config where it would have a new > command that would generate a file based on the current session, and > a new option to process changes from a file rather than > interactively? It looks like it would be

RE: kernel reordering and config -e

2017-11-22 Thread leo_tck
"Ed Hynan" wrote: > No patch from OP yet, Yeah, I'm sorry, my OpenBSD machine is currently air-gapped and is still running 6.1 :( It's been hectic IRL 'round here. > so how about this: for someone needing config -e > it's probably sufficient if /usr/libexec/reorder_kernel

Re: kernel reordering and config -e

2017-11-22 Thread Ed Hynan
On Mon, 20 Nov 2017, Theo de Raadt wrote: If someone wants to solve this fully there have been some proposals for keeping track of the instruction sequence, and attempting to reapply it upon each relink in the build directory. There just hasn't been any scripting changes to do that from anyone,

Re: kernel reordering and config -e

2017-11-21 Thread Paul B. Henson
On Tue, Nov 21, 2017 at 09:49:37AM +, Dimitris Papastamos wrote: > This is what I do in rc.shutdown to handle this case: > > /usr/bin/printf "disable inteldrm*\nquit\n" | /usr/sbin/config -ef /bsd > /bin/sha256 -h /var/db/kernel.SHA256 /bsd Cool, thanks for the suggestion; that should be

Re: kernel reordering and config -e

2017-11-21 Thread Paul B. Henson
On Mon, Nov 20, 2017 at 02:01:56PM -0700, Theo de Raadt wrote: > If someone wants to solve this fully there have been some proposals > for keeping track of the instruction sequence, and attempting to > reapply it upon each relink in the build directory. There just hasn't > been any scripting

Re: kernel reordering and config -e

2017-11-21 Thread Dimitris Papastamos
On Sun, Nov 19, 2017 at 07:31:20PM -0800, Paul B. Henson wrote: > I just updated a server to 6.2; unfortunately this box has an oddball > SOL com2 on irq10 so I need to run 'config -e' on the kernel to update > it and make the serial console work. I noticed afterwards in the boot > messages it was

RE: kernel reordering and config -e

2017-11-20 Thread leo_tck
theo wrote: > Hmm... I can't seem to find a patch in there anywhere. I'll read that as 'proposal accepted', and will try and provide a patch soon. --schaafuit.

Re: RE: kernel reordering and config -e

2017-11-20 Thread Theo de Raadt
> > If someone wants to solve this fully there have been some proposals > > for keeping track of the instruction sequence, and attempting to > > reapply it upon each relink in the build directory. There just hasn't > > been any scripting changes to do that from anyone, and it isn't on my > > radar

RE: kernel reordering and config -e

2017-11-20 Thread leo_tck
theo wrote: > If someone wants to solve this fully there have been some proposals > for keeping track of the instruction sequence, and attempting to > reapply it upon each relink in the build directory. There just hasn't > been any scripting changes to do that from anyone, and it isn't on my >

Re: kernel reordering and config -e

2017-11-20 Thread Theo de Raadt
> On Mon, Nov 20, 2017 at 08:37:43AM +, Roderick wrote: > > > Commenting out the line "/usr/libexec/reorder_kernel &" at the > > end of rc? > > > > I suspect it is not forseen not to benefice of KARL. > > No, actually, if the hash of the kernel is different than expected, the >

Re: kernel reordering and config -e

2017-11-20 Thread Paul B. Henson
On Mon, Nov 20, 2017 at 08:37:43AM +, Roderick wrote: > Commenting out the line "/usr/libexec/reorder_kernel &" at the > end of rc? > > I suspect it is not forseen not to benefice of KARL. No, actually, if the hash of the kernel is different than expected, the reorder_kernel aborts and

RE: kernel reordering and config -e

2017-11-20 Thread leo_tck
Hi, "Paul B. Henson" wrote: > Or do you need to update your settings > in the config and compile a kernel from scratch? If you do, does > /usr/share/compile automatically get populated with your new kernel > objects and reordering just starts working, or do you need to do >

Re: kernel reordering and config -e

2017-11-20 Thread Roderick
On Mon, 20 Nov 2017, Sebastien Marie wrote: config -e and KARL (kernel reordering) are mutually incompatibles. [...] So currently, you have to choose between: - modifying /bsd with config(8) and don't benefice of KARL Commenting out the line "/usr/libexec/reorder_kernel &" at

Re: kernel reordering and config -e

2017-11-19 Thread Sebastien Marie
On Sun, Nov 19, 2017 at 10:19:05PM -0800, Paul B. Henson wrote: > On Mon, Nov 20, 2017 at 06:50:30AM +0100, Sebastien Marie wrote: > > > For me, there is currently no way to ask config(8) to alter the right > > file in /usr/share/relink/kernel to "ship" the modification in all > > future

Re: kernel reordering and config -e

2017-11-19 Thread Paul B. Henson
On Mon, Nov 20, 2017 at 06:50:30AM +0100, Sebastien Marie wrote: > When it did that, it uses the object (I didn't recall the exact name) > with the previous mentioned array, with *default* configuration. So the > previous modification done with config(8) is cleared. Yeah, I figured that out

Re: kernel reordering and config -e

2017-11-19 Thread Sebastien Marie
ly to get it running with a locally compiled kernel? > config -e and KARL (kernel reordering) are mutually incompatibles. By using config -e, you modify /bsd: config(8) did a binary change in a particular array in the kernel file (in short, the one which contains the list of drivers to load: it s

kernel reordering and config -e

2017-11-19 Thread Paul B. Henson
I just updated a server to 6.2; unfortunately this box has an oddball SOL com2 on irq10 so I need to run 'config -e' on the kernel to update it and make the serial console work. I noticed afterwards in the boot messages it was complaining about kernel reordering failures, and thinking I was fixing