Now that all media documentation was converted to Sphinx, we
should get rid of the old DocBook one, as we don't want people
to submit patches against the old stuff.
Signed-off-by: Mauro Carvalho Chehab
---
Jon,
This patch should be applied after Linus handle my media documentation
pull request.
On 07/27/2016 11:32 AM, Mauro Carvalho Chehab wrote:
> Now that all media documentation was converted to Sphinx, we
> should get rid of the old DocBook one, as we don't want people
> to submit patches against the old stuff.
>
> Signed-off-by: Mauro Carvalho Chehab
Acked-by: Hans Verkuil
I'd
On Mon, 25 Jul 2016, Christoph Lameter wrote:
> Guess so. I will have a look at this when I get some time again.
Ok so the problem is the clocksource_watchdog() function in
kernel/time/clocksource.c. This function is active if
CONFIG_CLOCKSOURCE_WATCHDOG is defined. It will check the timesources
We tested this with 4.7-rc7 and aside from the issue with
clocksource_watchdog() this is working fine.
Tested-by: Christoph Lameter
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.k
When kernel.perf_event_paranoid is set to 3 (or greater), disallow
all access to performance events by users without CAP_SYS_ADMIN.
This new level of restriction is intended to reduce the attack
surface of the kernel. Perf is a valuable tool for developers but
is generally unnecessary and unused o
When CONFIG_SECURITY_PERF_EVENTS_RESTRICT=y kernel.perf_event_paranoid
sysctl will be set to 3 by default, and no unprivileged use of the
perf_event_open syscall will be permitted unless it is changed.
This new level of restriction is intended to reduce the attack
surface of the kernel. It allows
On Wed, 27 Jul 2016, Chris Metcalf wrote:
> > Should we just cycle through the cpus that are not isolated? Otherwise we
> > need to have some means to check the clocksources for accuracy remotely
> > (probably impossible for TSC etc).
>
> That sounds like the right idea - use the housekeeping cpu
Ok here is a possible patch that explicitly checks for housekeeping cpus:
Subject: clocksource: Do not schedule watchdog on isolated or NOHZ cpus
watchdog checks can only run on housekeeping capable cpus. Otherwise
we will be generating noise that we would like to avoid on the isolated
processors
On 7/27/2016 11:31 AM, Christoph Lameter wrote:
Ok here is a possible patch that explicitly checks for housekeeping cpus:
Subject: clocksource: Do not schedule watchdog on isolated or NOHZ cpus
watchdog checks can only run on housekeeping capable cpus. Otherwise
we will be generating noise that
On Thu, Jul 14, 2016 at 11:06:43AM -0500, ttha...@opensource.altera.com wrote:
> From: Thor Thayer
>
> Add Altera Arria10 NAND FIFO memory EDAC support.
>
> Signed-off-by: Thor Thayer
> ---
> drivers/edac/Kconfig |7 +++
> drivers/edac/altera_edac.c | 34 +++
On 07/27/2016 12:10 PM, Borislav Petkov wrote:
On Thu, Jul 14, 2016 at 11:06:43AM -0500, ttha...@opensource.altera.com wrote:
From: Thor Thayer
Add Altera Arria10 NAND FIFO memory EDAC support.
Signed-off-by: Thor Thayer
---
drivers/edac/Kconfig |7 +++
drivers/edac/altera
On Wed, 27 Jul 2016, Chris Metcalf wrote:
> How about using cpumask_next_and(raw_smp_processor_id(), cpu_online_mask,
> housekeeping_cpumask()), likewise cpumask_first_and()? Does that work?
Ok here is V2:
Subject: clocksource: Do not schedule watchdog on isolated or NOHZ cpus V2
watchdog che
On Wed, 27 Jul 2016, Chris Metcalf wrote:
> Looks good. Did you omit the equivalent fix in clocksource_start_watchdog()
> on purpose? For now I just took your change, but tweaked it to add the
> equivalent diff with cpumask_first_and() there.
Can the watchdog be started on an isolated cpu at al
On 7/27/2016 2:56 PM, Christoph Lameter wrote:
On Wed, 27 Jul 2016, Chris Metcalf wrote:
How about using cpumask_next_and(raw_smp_processor_id(), cpu_online_mask,
housekeeping_cpumask()), likewise cpumask_first_and()? Does that work?
Ok here is V2:
Subject: clocksource: Do not schedule watc
On Wed, Jul 27, 2016 at 01:43:04PM -0500, Thor Thayer wrote:
> Yes, that's better. I was trying to stay within the 80 character limit but
> missed the if/else if improvement. Thanks, Boris!
>
> Should I re-submit?
Nah, no need.
I'd only ask you to test the final result once I've pushed it out af
On Wed, Jul 27, 2016 at 7:45 AM, Jeff Vander Stoep wrote:
> When kernel.perf_event_paranoid is set to 3 (or greater), disallow
> all access to performance events by users without CAP_SYS_ADMIN.
>
> This new level of restriction is intended to reduce the attack
> surface of the kernel. Perf is a va
On Wed, Jul 27, 2016 at 7:46 AM, Jeff Vander Stoep wrote:
> When CONFIG_SECURITY_PERF_EVENTS_RESTRICT=y kernel.perf_event_paranoid
> sysctl will be set to 3 by default, and no unprivileged use of the
> perf_event_open syscall will be permitted unless it is changed.
>
> This new level of restrictio
On 7/27/2016 3:53 PM, Christoph Lameter wrote:
On Wed, 27 Jul 2016, Chris Metcalf wrote:
Looks good. Did you omit the equivalent fix in clocksource_start_watchdog()
on purpose? For now I just took your change, but tweaked it to add the
equivalent diff with cpumask_first_and() there.
Can the
On Wed, 27 Jul 2016 06:32:31 -0300
Mauro Carvalho Chehab wrote:
> This patch should be applied after Linus handle my media documentation
> pull request. Do you prefer to send the patch yourself, or if I do it?
If you want it to go up for 4.8, just go ahead and send it in, no need for
a middleman
This patch adds the DMA_ATTR_PRIVILEGED attribute to the DMA-mapping
subsystem.
Some advanced peripherals such as remote processors and GPUs perform
accesses to DMA buffers in both privileged "supervisor" and unprivileged
"user" modes. This attribute is used to indicate to the DMA-mapping
subsyst
20 matches
Mail list logo
