Re: rasops(9): revert changes in rasops32_putchar()?

2019-03-23 Thread Theo de Raadt
Mateusz Guzik wrote: > You may notice pagezero uses rep. Background page zeroing was removed > quite some time ago. I see OpenBSD still has it, but it is most likely > detrimental by now. If it is to be kept, a pagezero variant utilizing > non-temporal stores still makes sense but a different

Re: rasops(9): revert changes in rasops32_putchar()?

2019-03-23 Thread Mark Kettenis
> From: Mateusz Guzik > Date: Sat, 23 Mar 2019 15:29:39 +0100 > > On 3/18/19, Frederic Cambus wrote: > > Hi tech@, > > > > Now that efifb(4) supports remapping the framebuffer in write combining > > mode, it's on par with inteldrm regarding display performance as for as > > rasops(9) is

Re: rasops(9): revert changes in rasops32_putchar()?

2019-03-23 Thread Mateusz Guzik
On 3/18/19, Frederic Cambus wrote: > Hi tech@, > > Now that efifb(4) supports remapping the framebuffer in write combining > mode, it's on par with inteldrm regarding display performance as for as > rasops(9) is concerned. > > Therefore, I'm proposing reverting changes which were introduced in >

Re: rasops(9): revert changes in rasops32_putchar()?

2019-03-22 Thread Mark Kettenis
> Date: Mon, 18 Mar 2019 14:49:48 +0100 > From: Frederic Cambus > > Hi tech@, > > Now that efifb(4) supports remapping the framebuffer in write combining > mode, it's on par with inteldrm regarding display performance as for as > rasops(9) is concerned. > > Therefore, I'm proposing reverting

rasops(9): revert changes in rasops32_putchar()?

2019-03-18 Thread Frederic Cambus
Hi tech@, Now that efifb(4) supports remapping the framebuffer in write combining mode, it's on par with inteldrm regarding display performance as for as rasops(9) is concerned. Therefore, I'm proposing reverting changes which were introduced in rasops32_putchar() in revision 1.8 [1] as they are