00:21:00 <jbk> as a side note for 15091 -- has anyone tried it on recent versions of go?
00:21:31 <jbk> at least on 1.26.3, strip -x seems to work
00:23:59 <richlowe> tests/.../v4mapped might be another gitignore slip-through 
00:26:11 <richlowe> andyf: I think that's one of yours
00:26:25 <richlowe> but apparenly log -S doesn't do what I want mid-merge  
02:22:25 <gitomat> [illumos-gate] 18295 Add header tests to cover 18293 18294 -- Gordon Ross <gordon.w.ross⊙gc>
06:40:33 <andyf> richlowe - thanks, I will add a check to my RTI flow, and follow up on that.
07:18:01 <richlowe> andyf: the best I can think of is having nightly do `git status -su | awk '$1 == "?"'` when it completes
07:18:20 <richlowe> probably annoying as you're working, though.
14:19:53 <jbk> with the very obvious acknowledgement of the danger involved, is there any tool that'd let you map/peek/poke a device's registers?
14:20:00 <jbk> from userland
15:50:06 <andyf> richlowe, yes, but at least I can make my "prepare for RTI" thing do it. 
17:41:00 <alanc> jbk: pcitool? 
17:41:32 <jbk> our version seems to only deal with interrupts
17:42:04 <jbk> though maybe there's other PCI ioctls?
17:43:58 <alanc> jbk: https://github.com/illumos/illumos-gate/blob/master/usr/src/cmd/pcitool/pcitool_usage.c#L35 - your man page doesn't document them, but the source code does
17:44:32 <jbk> that's what i get for relying on the man page :)
17:46:49 <alanc> wouldn't want people using it who didn't know what they were doing 8-)
17:53:53 <jbk> fair enough :) I mean, it could cause havoc...
19:13:21 <andyf>  /usr/lib/pci/pcieadm has grown "bar write" and others recently too.
19:38:36 <richlowe> the manual page was added hastily because pcitool underpinned some interrupt remapping stuff on sun4v
19:38:42 <richlowe> before that it wasn't shipped
19:50:55 <richlowe> if I remember it wasn't even really available unless support gave it to you to work around something.  I think other than that you either worked there or asked dan mick for it 
21:43:43 <Ellenor> :o