[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <00000141a8a7ea27-4ab5f822-e15f-4789-a5cf-f313c402a901-000000@email.amazonses.com>
Date: Fri, 11 Oct 2013 17:54:38 +0000
From: Christoph Lameter <cl@...ux.com>
To: Tejun Heo <tj@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>
Subject: [PATCH 0/6] percpu: Implement Preemption checks for __this_cpu operations V4
This patchset introduces preemption checks for __this_cpu operations.
First we add new raw_cpu operations that perform this cpu operations
without preempt checks in the future.
Then those raw_cpu operations are used in a number of locations to avoid
false positives.
The last patch then adds the preemption checks by modifying the
__this_cpu macros in include/linux/percpu.h
V3->v4:
- Drop CONFIG_DEBUG_THIS_CPU_OPERATIONS
- Detail operation triggering the log entry.
- Use quilt 0.60/ [PATCH] prefix.
- Clean up subject lines.
- Include raw_cpu_ops conversion/fixes that were tested on
a Ubuntu 13.04 desktop.
- Traces
V2->V3:
- Subject line in the raw_cpu_ops patch had ; instead of :.
Guess I am getting old.
- Improve descriptions and variable names.
- Run tests again with kvm to verify that it still works.
A) No warnings with just the patches applied
B) Lots of warnings with CONFIG_DEBUG_THIS_CPU_OPERATIONS enabled
C) No warnings with 3 core patches applied that simply convert
__this_cpu operations to raw_cpu_ops.
V1->V2:
- Reuse preemption check logic in lib/smp_processor_id.c
- Add CONFIG_DEBUG_THIS_CPU_OPERATIONS
- Remove conversions to the use of raw_cpu_ops since
these may require some discussion first.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists