Re: [patch] let CONFIG_SECCOMP default to n

> > I can put in a patch into my tree for the next merge to disable the 
> > TSC disable code on i386 too like I did earlier for x86-64.
> 
> please do.

Hmm, with the new thread test as it was pointed out it can be indeed made zero 
cost for the common case. Perhaps that's not needed then.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [patch] let CONFIG_SECCOMP default to n
  - From: Ingo Molnar <[email protected]>

References:
- Re: [patch] let CONFIG_SECCOMP default to n
  - From: Andi Kleen <[email protected]>
- Re: [patch] let CONFIG_SECCOMP default to n
  - From: Ingo Molnar <[email protected]>

Prev by Date: Re: [PATCH] Use uname not sysctl to get the kernel revision
Next by Date: Re: [patch] Re: Magic Alt-SysRq change in 2.6.18-rc1
Previous by thread: Re: [patch] let CONFIG_SECCOMP default to n
Next by thread: Re: [patch] let CONFIG_SECCOMP default to n
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]