Le 03/10/2017 à 00:09, Taylor R Campbell a écrit :
Date: Mon, 2 Oct 2017 21:42:11 +0200
From: Joerg Sonnenberger
On Mon, Oct 02, 2017 at 07:23:16PM +, Maxime Villard wrote:
Add a machdep.tsc_user_enable sysctl, to enable/disable the rdtsc
instruction in usermode. It defaults to enabled.
> Module Name:src
> Committed By: christos
> Date: Mon Oct 2 22:19:45 UTC 2017
>
> Modified Files:
> src/tools/compat: compat_defs.h configure.ac fpurge.c
>
> Log Message:
> handle __fpurge being declared in
This has broken the tools build of awk for me.
cc -O -D__EXTE
On Mon, Oct 02, 2017 at 04:25:34PM -0600, Warner Losh wrote:
> Even if you don't have the ability to change the defective hardware?
The hardware is not defective. We are not talking about variable timing
for basic arithmetic operations based on the operand value. Outside
maybe division, that could
> Date: Mon, 2 Oct 2017 16:25:34 -0600
> From: Warner Losh
>
> Why should I provide an attacker a stop watch? I want him/her to build
> their own that has the potential to be accurate enough, but is necessarily
> less accurate than the one I'm denying them access to.
There are plenty of legitima
> Date: Mon, 2 Oct 2017 21:42:11 +0200
> From: Joerg Sonnenberger
>
> On Mon, Oct 02, 2017 at 07:23:16PM +, Maxime Villard wrote:
> > Add a machdep.tsc_user_enable sysctl, to enable/disable the rdtsc
> > instruction in usermode. It defaults to enabled.
>
> Do we really need this change? I've
Le 02/10/2017 à 19:12, Manuel Bouyer a écrit :
On Mon, Oct 02, 2017 at 07:05:20PM +0200, Maxime Villard wrote:
Le 02/10/2017 à 18:51, Manuel Bouyer a écrit :
On Mon, Oct 02, 2017 at 06:11:57PM +0200, Maxime Villard wrote:
so we remove COMPAT_LINUX from all architectures that do not support ker
On Mon, Oct 02, 2017 at 07:23:16PM +, Maxime Villard wrote:
> Module Name: src
> Committed By: maxv
> Date: Mon Oct 2 19:23:16 UTC 2017
>
> Modified Files:
> src/sys/arch/x86/x86: tsc.c tsc.h x86_machdep.c
>
> Log Message:
> Add a machdep.tsc_user_enable sysctl, to enable/disa
On Mon, Oct 02, 2017 at 03:36:17PM +0200, Martin Husemann wrote:
> On Mon, Oct 02, 2017 at 03:16:14PM +0200, Maxime Villard wrote:
> > Le 02/10/2017 à 14:47, Manuel Bouyer a écrit :
> > > On Mon, Oct 02, 2017 at 02:39:47PM +0200, Maxime Villard wrote:
> > > > > Actually I did suggest to make the de
On Mon, Oct 02, 2017 at 07:05:20PM +0200, Maxime Villard wrote:
> Le 02/10/2017 à 18:51, Manuel Bouyer a écrit :
> > On Mon, Oct 02, 2017 at 06:11:57PM +0200, Maxime Villard wrote:
> > > so we remove COMPAT_LINUX from all architectures that do not support
> > > kernel
> > > modules? this doesn't m
Le 02/10/2017 à 18:51, Manuel Bouyer a écrit :
On Mon, Oct 02, 2017 at 06:11:57PM +0200, Maxime Villard wrote:
so we remove COMPAT_LINUX from all architectures that do not support kernel
modules? this doesn't make compat_linux "nearby" or "easy to use" anymore
which architecture are theses ?
On Mon, Oct 02, 2017 at 06:11:57PM +0200, Maxime Villard wrote:
> so we remove COMPAT_LINUX from all architectures that do not support kernel
> modules? this doesn't make compat_linux "nearby" or "easy to use" anymore
which architecture are theses ?
--
Manuel Bouyer
NetBSD: 26 ans d'experi
Le 02/10/2017 à 15:36, Martin Husemann a écrit :
On Mon, Oct 02, 2017 at 03:16:14PM +0200, Maxime Villard wrote:
Le 02/10/2017 à 14:47, Manuel Bouyer a écrit :
On Mon, Oct 02, 2017 at 02:39:47PM +0200, Maxime Villard wrote:
Actually I did suggest to make the default dependant on MODULAR.
wha
On 02.10.2017 15:36, Martin Husemann wrote:
> On Mon, Oct 02, 2017 at 03:16:14PM +0200, Maxime Villard wrote:
>> Le 02/10/2017 à 14:47, Manuel Bouyer a écrit :
>>> On Mon, Oct 02, 2017 at 02:39:47PM +0200, Maxime Villard wrote:
> Actually I did suggest to make the default dependant on MODULAR.
On Mon, Oct 02, 2017 at 03:16:14PM +0200, Maxime Villard wrote:
> Le 02/10/2017 à 14:47, Manuel Bouyer a écrit :
> > On Mon, Oct 02, 2017 at 02:39:47PM +0200, Maxime Villard wrote:
> > > > Actually I did suggest to make the default dependant on MODULAR.
> > >
> > > what's the point exactly?
> >
>
Le 02/10/2017 à 14:47, Manuel Bouyer a écrit :
On Mon, Oct 02, 2017 at 02:39:47PM +0200, Maxime Villard wrote:
Actually I did suggest to make the default dependant on MODULAR.
what's the point exactly?
that if I build a non-modular kernel with an emulation option explicitely
selected, it wor
On Mon, Oct 02, 2017 at 02:47:57PM +0200, Manuel Bouyer wrote:
> On Mon, Oct 02, 2017 at 02:39:47PM +0200, Maxime Villard wrote:
> > > Actually I did suggest to make the default dependant on MODULAR.
> >
> > what's the point exactly?
>
> that if I build a non-modular kernel with an emulation opti
On Mon, Oct 02, 2017 at 02:39:47PM +0200, Maxime Villard wrote:
> > Actually I did suggest to make the default dependant on MODULAR.
>
> what's the point exactly?
that if I build a non-modular kernel with an emulation option explicitely
selected, it works at boot. Even in single-user mode.
--
M
Le 01/10/2017 à 13:38, Manuel Bouyer a écrit :
On Sun, Oct 01, 2017 at 09:38:32AM +0200, Maxime Villard wrote:
No. It is clear that none of the proposals in the recent threads has brought
unanimous consensus, but this sysctl appears to be the least problematic
solution. You can speculate endles
At Mon, 2 Oct 2017 07:06:15 +,
> Committed By: nat
> Date: Mon Oct 2 07:06:15 UTC 2017
>
> Modified Files:
> src/sys/dev: auconv.c
>
> Log Message:
> Allow maxused to be an odd number of bytes. This makes single byte
> conversions work for the test described in the PR.
Please
19 matches
Mail list logo
