Re: printf.1: fix incorrect conversion of apostrophe

2019-06-01 Thread Anthony J. Bentley
Stephen Gregoratto writes: > In the escape sequences section of printf.1, the > character is represented using "\e\'". In UTF-8 mode, mandoc converts > this to an acute accent. To fix this I explicitly used "\(aq" as per the > Accents section of mandoc_char(7), although using "\e'" works as well.

printf.1: fix incorrect conversion of apostrophe

2019-06-01 Thread Stephen Gregoratto
In the escape sequences section of printf.1, the character is represented using "\e\'". In UTF-8 mode, mandoc converts this to an acute accent. To fix this I explicitly used "\(aq" as per the Accents section of mandoc_char(7), although using "\e'" works as well. Index: printf.1 =

Re: mtx_enter_try(9) & recursion

2019-06-01 Thread Visa Hankala
On Sat, Jun 01, 2019 at 07:04:23PM -0300, Martin Pieuchot wrote: > On 01/06/19(Sat) 23:22, Mark Kettenis wrote: > > > Date: Sat, 1 Jun 2019 17:32:52 -0300 > > > From: Martin Pieuchot > > > > > > Currently it isn't safe to call mtx_enter_try(9) if you're already > > > holding the mutex. That mean

Re: vmd(8) i8042 device implementation questions

2019-06-01 Thread Katherine Rohl
Couple questions: > This means no interrupt will be injected. I'm not sure if that's what you > want. > See vm.c: vcpu_exit_inout(..). It looks like you may have manually asserted > the > IRQ in this file, which is a bit different than what we do in other devices. > That > may be okay, though.

Re: mtx_enter_try(9) & recursion

2019-06-01 Thread Martin Pieuchot
On 01/06/19(Sat) 23:22, Mark Kettenis wrote: > > Date: Sat, 1 Jun 2019 17:32:52 -0300 > > From: Martin Pieuchot > > > > Currently it isn't safe to call mtx_enter_try(9) if you're already > > holding the mutex. That means it isn't safe to call that function > > in hardclock(9), like with `windup_

Pump my sched: fewer SCHED_LOCK() & kill p_priority

2019-06-01 Thread Martin Pieuchot
Diff below exists mainly for documentation and test purposes. If you're not interested about how to break the scheduler internals in pieces, don't read further and go straight to testing! - First change is to stop calling tsleep(9) at PUSER. That makes it clear that all "sleeping priorities" a

Re: mtx_enter_try(9) & recursion

2019-06-01 Thread Mark Kettenis
> Date: Sat, 1 Jun 2019 17:32:52 -0300 > From: Martin Pieuchot > > Currently it isn't safe to call mtx_enter_try(9) if you're already > holding the mutex. That means it isn't safe to call that function > in hardclock(9), like with `windup_mtx'. That's why the mutex needs > to be initialized as

Re: sysupgrade(8): Adding ability to check if new release available

2019-06-01 Thread Andrew Klaus
Please ignore my last patch, since I had mixed up the -l and -c flags from syspatch. This new patch will work for both releases and snapshots as well. When running on a snapshot, it still outputs the SHA256.sig transfer and "Signature Verified" to stdout, which isn't ideal, but it's a start.

mtx_enter_try(9) & recursion

2019-06-01 Thread Martin Pieuchot
Currently it isn't safe to call mtx_enter_try(9) if you're already holding the mutex. That means it isn't safe to call that function in hardclock(9), like with `windup_mtx'. That's why the mutex needs to be initialized as IPL_CLOCK. I'm working on removing the SCHED_LOCK() from inside hardclock(

Re: PCI interrupt functions

2019-06-01 Thread Mark Kettenis
> From: "Theo de Raadt" > Date: Fri, 31 May 2019 15:34:18 -0600 > > > On arm64, pci_intr_handle_t is a pointer to an opaque struct. > > That's a subtle trap. How would someone realize the order is wrong... > > Would it not be better if this was done like the other architectures, > where the pc

Re: Reduce the scope of SCHED_LOCK()

2019-06-01 Thread Martin Pieuchot
On 01/06/19(Sat) 15:54, Mark Kettenis wrote: > > Date: Sat, 25 May 2019 15:57:44 -0300 > > From: Martin Pieuchot > > > > On 12/05/19(Sun) 18:17, Martin Pieuchot wrote: > > > People started complaining that the SCHED_LOCK() is contended. Here's a > > > first round at reducing its scope. > > > >

Re: Reduce the scope of SCHED_LOCK()

2019-06-01 Thread Mark Kettenis
> Date: Sat, 25 May 2019 15:57:44 -0300 > From: Martin Pieuchot > > On 12/05/19(Sun) 18:17, Martin Pieuchot wrote: > > People started complaining that the SCHED_LOCK() is contended. Here's a > > first round at reducing its scope. > > > > Diff below introduces a per-process mutex to protect time

Re: ftp.html: adjust mirror minimum space

2019-06-01 Thread Reyk Floeter
On Sat, Jun 01, 2019 at 12:18:33PM +0200, Theo Buehler wrote: > On Sat, Jun 01, 2019 at 12:05:09PM +0200, Reyk Floeter wrote: > > Hi, > > > > a fresh rsync over night revealed that the minimum space for mirrors > > should be adjusted. > > > > OK? > > I don't know whether the size is correct or w

Re: ftp.html: adjust mirror minimum space

2019-06-01 Thread Theo Buehler
On Sat, Jun 01, 2019 at 12:05:09PM +0200, Reyk Floeter wrote: > Hi, > > a fresh rsync over night revealed that the minimum space for mirrors > should be adjusted. > > OK? I don't know whether the size is correct or whether it should be bumped further, but please note that ftp.html is generated.

ftp.html: adjust mirror minimum space

2019-06-01 Thread Reyk Floeter
Hi, a fresh rsync over night revealed that the minimum space for mirrors should be adjusted. OK? Reyk Index: ftp.html === RCS file: /cvs/www/ftp.html,v retrieving revision 1.794 diff -u -p -u -p -r1.794 ftp.html --- ftp.html30

sysupgrade(8): Adding ability to check if new release available

2019-06-01 Thread Andrew Klaus
This adds the ability to check if you're running the latest release, without actually upgrading. I'd like to use this functionality when writing an Ansible module for sysupgrade soon. I already have one for syspatch that's been accepted today. This follows the same usage (-l) as syspatch(8) to