On 07/19/2014 02:10 AM, Paul E. McKenney wrote:
>> diff --git a/kernel/rcu/tree_plugin.h b/kernel/rcu/tree_plugin.h
>> index ce8c331..8f987c1 100644
>> --- a/kernel/rcu/tree_plugin.h
>> +++ b/kernel/rcu/tree_plugin.h
>> @@ -2053,9 +2053,10 @@ static void rcu_init_one_nocb(struct rcu_node *rnp)
>>
On Sa, 2014-07-19 at 01:42 -0400, Theodore Ts'o wrote:
> On Sat, Jul 19, 2014 at 01:35:48AM +0200, Hannes Frederic Sowa wrote:
> > > + nfrac = ibytes << (ENTROPY_SHIFT + 3);
> > > + if (entropy_count < 0) {
> >
> > Minor nit: maybe also add an unlikely() here?
>
> Yep, done.
>
> > > + if ((unsig
On Thu, Jul 17, 2014 at 08:11:01PM -0400, Pranith Kumar wrote:
> On 07/17/2014 07:49 PM, Paul E. McKenney wrote:
> > On Thu, Jul 17, 2014 at 05:30:11PM -0400, Pranith Kumar wrote:
> >> Hi Paul,
> >>
> >> This is something similar to what you found yesterday with tick_nohz_full
> >> mask.
> >>
> >>
The following changes since commit 1795cd9b3a91d4b5473c97f491d63892442212ab:
Linux 3.16-rc5 (2014-07-13 14:04:33 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random.git
tags/random_for_linus_stable
for you to fetch changes up to 79a8468
On Sat, Jul 19, 2014 at 01:35:48AM +0200, Hannes Frederic Sowa wrote:
> > + nfrac = ibytes << (ENTROPY_SHIFT + 3);
> > + if (entropy_count < 0) {
>
> Minor nit: maybe also add an unlikely() here?
Yep, done.
> > + if ((unsigned) entropy_count > nfrac)
>
> (unsigned) -> (size_t)
>
> size_t
Hi Linus,
The following changes since commit cacadb4ff969a82628d47db87b5a531be466b134:
Merge tag 'samsung-fixes-3' of
git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung into fixes
(2014-07-12 21:19:21 -0700)
are available in the git repository at:
git://git.kernel.org/pub/s
在 2014年7月19日，上午2:21，Rajesh Borundia 写道：
>> -Original Message-
>> From: Ethan Zhao [mailto:ethan.z...@oracle.com]
>> Sent: Friday, July 18, 2014 9:13 AM
>> To: Manish Chopra; Sony Chacko; Rajesh Borundia; netdev
>> Cc: linux-kernel; ethan.ker...@gmail.com; Ethan Zhao
>> Subject: [PATCH V
On Sat, Jul 19, 2014 at 1:20 AM, James Bottomley
wrote:
> On Fri, 2014-07-18 at 22:25 -0400, Nick Krause wrote:
>> On Fri, Jul 18, 2014 at 5:03 PM, James Bottomley
>> wrote:
>> > On Fri, 2014-07-18 at 16:37 -0400, Nicholas Krause wrote:
>> >> The comment for size of frame not being needed is inco
On Fri, 2014-07-18 at 22:25 -0400, Nick Krause wrote:
> On Fri, Jul 18, 2014 at 5:03 PM, James Bottomley
> wrote:
> > On Fri, 2014-07-18 at 16:37 -0400, Nicholas Krause wrote:
> >> The comment for size of frame not being needed is incorrect , the
> >> function called needs this parameter.
> >
> >
This patch removes a unneeded line from this file as stated by the
fix me in this file.
Signed-off-by: Nicholas Krause
---
arch/mips/kernel/smp-cmp.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/mips/kernel/smp-cmp.c b/arch/mips/kernel/smp-cmp.c
index fc8a515..61bfa20 100644
--- a/a
Since upgrading from 3.12.24 kernel to 3.14.10, and today, .12 kernel
log and dmesg are flooded with constant messages
option1 ttyUSB0: option_instat_callback: error -2
The device still works, it sends and receives SMS's as well,
I tried setting verbose usb debug to see if it offers any more
e
On Fri, Jul 18, 2014 at 06:43:39PM +0100, Pawel Moll wrote:
>
> This code definitely needs more work and testing (I'm not 100%
> sure if the Kp and Ki I've picked for the proportional and
> integral terms are universal),
I wouldn't bet on it.
> but for now wanted to see
> if this approach makes
> Hi Steve
>
> Why not share your quilt skills, say by adding a file in the Document
> directory?
>
> Hillf
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majord
On Sat, Jul 19, 2014 at 9:31 AM, Steven Rostedt wrote:
> On Fri, Jul 18, 2014 at 06:22:15PM -0400, Theodore Ts'o wrote:
>>
>> And then think very hard about which patches people need to see in
>> order to be able to evaluate a patch. For example, if you have patch
>> 1 out of a series which adds
On Fri, 18 Jul 2014 22:55:12 -0400 (EDT)
Nicolas Pitre wrote:
> Any comments / ACKs on the other patches? I'd like to see 1/4 to 3/4
> (and your patch) merged upstream during the next window. 4/4 is up for
> debate.
You can add my Acked-by for patches 1,2 and 3, after the clean up of
the #if
Hi friend, hope you are fine, My name is Benita Sayyed, I am lonely, tender,
caring, faithful and honest girl, I am ready to give all my care,
love, attention and devotion.I promise to send my recent pictures and
tell you more about myself.
Regards.
Benita Sayyed
--
To unsubscribe from this list: s
Hi Paul,
I looked at why my previous change removing checks for
rcu_scheduler_fully_active failed to boot.
The reason is that rcu_init() is called earlier than rest_init() from within
which the early_init() is being called. rcu_init() calls rcu_cpu_notify() which
in turn calls rcu_spawn_all_nocb_
On Fri, 18 Jul 2014, Steven Rostedt wrote:
> On Fri, 18 Jul 2014 16:55:42 -0400 (EDT)
> Nicolas Pitre wrote:
>
> >
> > Here's the patch I have at the head of the series now, with the above
> > ugliness changed to an unconditional __tracepoint_string attribute.
> >
>
> I was thinking of someth
On Fri, Jul 18, 2014 at 10:45 PM, Nick Krause wrote:
> Sorry didn't run spell check. I will resend this patch with the
> correct information
> as needed. Thanks for the advice, Sasha.
>
> Cheers Nick
>
> On Fri, Jul 18, 2014 at 10:36 PM, Sasha Levin wrote:
>> On 07/18/2014 01:34 PM, Nicholas Krau
Sorry didn't run spell check. I will resend this patch with the
correct information
as needed. Thanks for the advice, Sasha.
Cheers Nick
On Fri, Jul 18, 2014 at 10:36 PM, Sasha Levin wrote:
> On 07/18/2014 01:34 PM, Nicholas Krause wrote:
>> I am removing two fix mes in this file as after dicuss
At Fri, 18 Jul 2014 06:47:32 -0700,
Guenter Roeck wrote:
>
> On 07/18/2014 05:16 AM, Jiri Slaby wrote:
> > On 07/18/2014 02:12 PM, Jiri Slaby wrote:
> >> This is the start of the stable review cycle for the 3.12.25 release.
> >> There are 170 patches in this series, all will be posted as a respons
On 07/18/2014 01:34 PM, Nicholas Krause wrote:
> I am removing two fix mes in this file as after dicussing then it seems
> there is no reason to check against Null for usb_device as it can never
> be NULL and this is check is therefore not needed.
>
> Signed-off-by: Nicholas Krause
Please expla
On Fri, Jul 18, 2014 at 5:03 PM, James Bottomley
wrote:
> On Fri, 2014-07-18 at 16:37 -0400, Nicholas Krause wrote:
>> The comment for size of frame not being needed is incorrect , the
>> function called needs this parameter.
>
> Actually, that's not correct. The point of the FIXME is that fram_s
On Fri, Jul 18, 2014 at 7:29 PM, Randy Dunlap wrote:
> On 07/18/2014 12:59 PM, Nick Krause wrote:
>> On Fri, Jul 18, 2014 at 2:10 PM, Randy Dunlap wrote:
>>> On 07/18/2014 10:45 AM, Nick Krause wrote:
Hey Greg and others,
When I built the usb directory today to check a patch I am also
>
Allows kbuild to generate LLVM bitcode files with the .ll extension when
building with Clang.
# c code
CC=clang make kernel/pid.ll
# asm code
CC=clang make arch/arm/kernel/calls.ll
Signed-off-by: Vinícius Tinti
Signed-off-by: Behan Webster
---
Makefile | 7 +++
scri
On Fri, Jul 18, 2014 at 06:22:15PM -0400, Theodore Ts'o wrote:
>
> And then think very hard about which patches people need to see in
> order to be able to evaluate a patch. For example, if you have patch
> 1 out of a series which adds a new function, and then patches 2
> through 1000 modify a th
Commit 6079d38 ("dmaengine: pl330: Remove useless xfer_cb indirection")
removed the __callback() function which created an unnecessary level of
indirection to execute the tranfer callback .xfer_cb
Unfortunately the commit also changed the semantics slightly since that
function used to check if the
This addresses all earlier comments. Especially perf mem report
for mem-stores now works correctly again.
The Haswell PEBS list unfortunately isn't simple anymore to report
all the mem_op flags correctly, but at least it's more correct
than before. Also fixed a bug.
Hopefully should be ready for
From: Andi Kleen
The basic idea is that it does not make sense to list all PEBS
events individually. The list is very long, sometimes outdated
and the hardware doesn't need it. If an event does not support
PEBS it will just not count, there is no security issue.
We need to only list events that
From: Andi Kleen
Haswell supports reporting the data address for a range
of PEBS events, including:
UOPS_RETIRED.ALL
MEM_UOPS_RETIRED.STLB_MISS_LOADS
MEM_UOPS_RETIRED.STLB_MISS_STORES
MEM_UOPS_RETIRED.LOCK_LOADS
MEM_UOPS_RETIRED.SPLIT_LOADS
MEM_UOPS_RETIRED.SPLIT_STORES
MEM_UOPS_RETIRED.ALL_LOAD
From: Andi Kleen
This fixes a bug introduced with
commit 722e76e60f2775c21b087ff12c5e678cf0ebcaaf
Author: Stephane Eranian
Date: Thu May 15 17:56:44 2014 +0200
fix Haswell precise store data source encoding
When returning early we need to return the complete value of the
memory hierarch
On Tue, Jul 15, 2014 at 12:49:43AM +0200, Stephane Eranian wrote:
> On Tue, Jul 15, 2014 at 12:39 AM, Andi Kleen wrote:
> >> I have a problem with this patch.
> >>
> >> It makes: perf mem -t store rec record OP_NA for the store.
> >> It was recording OP_STORE before.
> >>
> >> I think we need to k
On Fri, Jul 18, 2014 at 01:30:52PM -0400, Pranith Kumar wrote:
> Hi Paul,
>
> While running the kvm rcutorture test scripts, I encountered a build failure
> caused by
>
> Commit 918179699e4a ("rcu: Don't keep timekeeping CPU tick running for
> non-nohz_full= CPUs")
>
> This commit fixes the fa
When a CPU wakes up from idle and finds out that the timekeeper is
sleeping, we need to kick it such that it switches from dynticks to
periodic mode to maintain its timekeeping duty on behalf of the newly
awoken CPU.
However we aren't using the right API for that. rcu_kick_nohz_cpu() is
aimed at w
In full dynticks idle mode, the timekeeper should never be set to another
CPU than 0.
Lets enforce that through a dedicated mutator.
Cc: Ingo Molnar
Cc: Paul E. McKenney
Cc: Peter Zijlstra
Cc: Steven Rostedt
Cc: Thomas Gleixner
Cc: Viresh Kumar
Signed-off-by: Frederic Weisbecker
---
kerne
When we enqueue a remote irq work, we trigger the same IPI as those
raised by smp_call_function_*() family.
So when we receive such IPI, we check both irq_work and smp_call_function
queues. Thus if we trigger a remote irq work, we'll likely find the
smp_call_function queue empty unless we collide
While we enqueue a new timer on a dynticks target, we must send it an
IPI so that it reschedules the next tick accordingly.
Now all we need for that is to run irq_exit() on the target. Hence
an empty IRQ is way enough. We don't need to run tick_nohz_full_check()
and all the overhead that comes wit
Hi Linus,
A couple of key fixes and a few less critical ones. The main ones
are:
1. to add a .bss section to the PE/COFF headers when building with EFI
stub.
2. to invoke the correct paravirt magic when building the espfix page
tables.
Unfortunately both of these areas also have at lea
We fetch it unconditionally from the tick stop code whereas only
the timekeeper, or the CPU that carried that duty last, needs it.
Fetching the timekeeping max deferment should be lightweight but it
still involves a few read side barriers and a seqcount that may well
be cache cold for non-timekeep
The timekeeper gets initialized to the value of the CPU where the
first clockevent device is setup. This works well because the timekeeper
can be any online CPU in most configs.
Full dynticks has its own requirement though and needs the timekeeper
to always be 0. And this requirement seem to accom
The nohz full timekeeper is always CPU 0. Lets add it to the list of
special tick_do_timer_cpu symbols for more self explanatory code.
Cc: Ingo Molnar
Cc: Paul E. McKenney
Cc: Peter Zijlstra
Cc: Steven Rostedt
Cc: Thomas Gleixner
Cc: Viresh Kumar
Signed-off-by: Frederic Weisbecker
---
kern
When a full dynticks CPU stays for too long in the kernel, it may fail
to report quiescent states due to it missing ticks and therefore it can
delay the completion of grace periods.
A way to solve this is to send an IPI to the incriminated CPU such that
it can check rcu_needs_cpu() and reschedule
In full dynticks, the CPU 0 carries the timekeeping duty on behalf
of all other CPUs in the system. This way full dynticks are left
undisturbed on this regard.
Of course this prevents CPU 0 from entering in dynticks idle mode
because any CPU may need uptodate timekeeping at any time.
Theoreticall
Currently when nohz full is active, the CPU 0 handles timekeeping on
behalf of all other CPUs. This prevents it from ever entering in dynticks
idle mode.
This patchset uses the RCU sysidle feature to allow that. The CPU 0 can
know safely when to sleep and when to wake up, the sysidle code determin
Being able to trigger an empty IPI appears to be useless in the first
place. Yet it is expected to be very useful for callers who just need
to execute irq_enter() or irq_exit() to a remote target.
More precisely this is going to be useful for the nohz subsystem which
often needs a remote CPU to re
On 07/18/2014 04:24 PM, Stephen Boyd wrote:
> On 07/18/14 15:42, John Stultz wrote:
>> If its a regression (and needs -stable backports) it needs to go in via
>> tip/timers/urgent, and not via the regular merge window.
>>
>> Whats the additional risk -stable wise for canceling the timer during
>> s
Some devices use freq_table instead of OPP. For those devices, the
available_frequencies sysfs file shows up empty. So, add a
possible_frequencies attribute/syfs file that list all the possible
frequencies.
For devices that use OPP, the output of this file will match
available_frequencies. It may
On 07/18/2014 05:29 PM, Sam Ravnborg wrote:
On Fri, Jul 18, 2014 at 02:44:34PM -0600, Shuah Khan wrote:
Add a new devtest make target to enable developer testing. This
new target does full build (make all) and then runs selftests.
Signed-off-by: Shuah Khan
---
Makefile | 11 +++
1 f
On Friday, July 18, 2014 01:57:18 PM Joerg Roedel wrote:
> From: Joerg Roedel
>
> This patch adds the code to allocate and build the radix
> tree to store the memory bitmap. The old data structure is
> left in place until the radix tree implementation is
> finished.
>
> Signed-off-by: Joerg Roed
Hi,
On Fr, 2014-07-18 at 18:07 -0400, Theodore Ts'o wrote:
> From: Hannes Frederic Sowa
>
> The expression entropy_count -= ibytes << (ENTROPY_SHIFT + 3) could
> actually increase entropy_count if during assignment of the unsigned
> expression on the RHS (mind the -=) we reduce the value modulo
On 07/18/2014 12:59 PM, Nick Krause wrote:
> On Fri, Jul 18, 2014 at 2:10 PM, Randy Dunlap wrote:
>> On 07/18/2014 10:45 AM, Nick Krause wrote:
>>> Hey Greg and others,
>>> When I built the usb directory today to check a patch I am also
>>> sending to. I seem to hitting
>>> a few compiler errors a
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differently, please holler.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majo
On Fri, Jun 20, 2014 at 02:31:44PM -0500, Christoph Lameter wrote:
> Replace the single use of __get_cpu_var in avr32 with
> __this_cpu_write.
>
> Cc: Haavard Skinnemoen
> Acked-by: Hans-Christian Egtvedt
> Signed-off-by: Christoph Lameter
Applied to wq/for-3.17-consistent-ops. If this patch
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differently, please holler.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majo
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differently, please holler.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majo
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differently, please holler.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majo
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differently, please holler.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majo
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differently, please holler.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majo
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differently, please holler.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majo
On Fri, Jul 18, 2014 at 02:44:34PM -0600, Shuah Khan wrote:
> Add a new devtest make target to enable developer testing. This
> new target does full build (make all) and then runs selftests.
>
> Signed-off-by: Shuah Khan
> ---
> Makefile | 11 +++
> 1 file changed, 11 insertions(+)
>
>
On Fri, Jun 20, 2014 at 02:31:34PM -0500, Christoph Lameter wrote:
>
> From: David Daney
>
> The use of __this_cpu_inc() requires a fundamental integer type, so
> change the type of all the counters to unsigned long, which is the
> same width they were before, but not wrapped in local_t.
>
> Si
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differently, please holler.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majo
On Fri, Jun 20, 2014 at 02:31:33PM -0500, Christoph Lameter wrote:
> __this_cpu_ptr is being phased out. So replace with raw_cpu_ptr.
>
> Cc: Russell King
> Cc: Catalin Marinas
> CC: Will Deacon
> Signed-off-by: Christoph Lameter
Applied to wq/for-3.17-consistent-ops. If this patch should be
On Fri, Jun 20, 2014 at 02:31:32PM -0500, Christoph Lameter wrote:
> Use __this_cpu_read instead.
>
> Cc: Hedi Berriche
> Cc: Mike Travis
> Cc: Dimitri Sivanich
> Signed-off-by: Christoph Lameter
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differently, please holler
On Fri, Jun 20, 2014 at 02:31:30PM -0500, Christoph Lameter wrote:
> [ARM specific]
>
> These are generally replaced with raw_cpu_ptr. However, in
> gic_get_percpu_base() we immediately dereference the pointer. This is
> equivalent to a raw_cpu_read. So use that operation there.
>
> Cc: nicolas.p
On Fri, Jun 20, 2014 at 02:31:27PM -0500, Christoph Lameter wrote:
> __this_cpu_ptr is being phased out.
>
> Signed-off-by: Christoph Lameter
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differently, please holler.
Thanks.
--
tejun
--
To unsubscribe from this list: s
On Fri, Jun 20, 2014 at 02:31:28PM -0500, Christoph Lameter wrote:
> Replace __get_cpu_var uses for address calculation with this_cpu_ptr().
>
> Acked-by: James Hogan
> Signed-off-by: Christoph Lameter
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differently, please ho
On Fri, Jun 20, 2014 at 02:31:29PM -0500, Christoph Lameter wrote:
> Another case was merged for 3.14-rc1
>
> Signed-off-by: Christoph Lameter
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differently, please holler.
Thanks.
--
tejun
--
To unsubscribe from this list:
On Fri, Jun 20, 2014 at 02:31:26PM -0500, Christoph Lameter wrote:
> Replace uses of get_cpu_var for address calculation through this_cpu_ptr.
>
> Cc: net...@vger.kernel.org
> Cc: Eric Dumazet
> Acked-by: David S. Miller
> Signed-off-by: Christoph Lameter
Applied to wq/for-3.17-consistent-ops.
On Friday, July 18, 2014 04:16:50 PM Dmitry Torokhov wrote:
> On Saturday, July 19, 2014 12:55:09 AM Rafael J. Wysocki wrote:
> > On Saturday, July 19, 2014 12:19:39 AM Rafael J. Wysocki wrote:
> > > On Friday, July 18, 2014 02:45:40 PM Dmitry Torokhov wrote:
> > > > On Friday, July 18, 2014 11:59:
On Fri, Jun 20, 2014 at 02:31:25PM -0500, Christoph Lameter wrote:
> Most of these are the uses of &__raw_get_cpu_var for address calculation.
>
> touch_softlockup_watchdog_sync() uses __raw_get_cpu_var to write to
> per cpu variables. Use __this_cpu_write instead.
>
> Cc: Wim Van Sebroeck
> Cc:
On Fri, Jun 20, 2014 at 02:31:23PM -0500, Christoph Lameter wrote:
> Replace __get_cpu_var used for address calculation with this_cpu_ptr.
>
> Acked-by: James Hogan
> Signed-off-by: Christoph Lameter
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differently, please holl
On Fri, Jun 20, 2014 at 02:31:24PM -0500, Christoph Lameter wrote:
> Replace with this_cpu_ptr.
>
> Acked-by: Chris Metcalf
> Signed-off-by: Christoph Lameter
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differently, please holler.
Thanks.
--
tejun
--
To unsubscribe
On Fri, Jun 20, 2014 at 02:31:20PM -0500, Christoph Lameter wrote:
> A single case of using __get_cpu_var for address calculation.
>
> Cc: Arnd Bergmann
> Cc: Greg Kroah-Hartman
> Signed-off-by: Christoph Lameter
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differentl
On Fri, Jun 20, 2014 at 02:31:22PM -0500, Christoph Lameter wrote:
> Replace the uses of __get_cpu_var for address calculation with this_cpu_ptr.
>
> Cc: Robert Richter
> Cc: oprofile-l...@lists.sf.net
> Signed-off-by: Christoph Lameter
Applied to wq/for-3.17-consistent-ops. If this patch shou
On Fri, Jun 20, 2014 at 02:31:21PM -0500, Christoph Lameter wrote:
> All of these are for address calculation. Replace with
> this_cpu_ptr().
>
> Cc: Daniel Lezcano
> Cc: linux...@vger.kernel.org
> Acked-by: Rafael J. Wysocki
> [cpufreq changes]
> Signed-off-by: Christoph Lameter
Applied to wq
On Fri, Jun 20, 2014 at 02:31:19PM -0500, Christoph Lameter wrote:
> __this_cpu_ptr is being phased out use raw_cpu_ptr instead which was
> introduced in 3.15-rc1.
>
> Cc: Jens Axboe
> Signed-off-by: Christoph Lameter
Applied to wq/for-3.17-consistent-ops. If this patch should be routed
differ
On Fri, Jun 20, 2014 at 02:31:18PM -0500, Christoph Lameter wrote:
> Convert all uses of __get_cpu_var for address calculation to use
> this_cpu_ptr instead.
>
> Cc: Peter Zijlstra
> Acked-by: Ingo Molnar
> Signed-off-by: Christoph Lameter
Applied to wq/for-3.17-consistent-ops. If this patch
On Fri, Jun 20, 2014 at 02:31:16PM -0500, Christoph Lameter wrote:
> Replace uses of __get_cpu_var for address calculation with this_cpu_ptr.
>
> Cc: a...@linux-foundation.org
> Signed-off-by: Christoph Lameter
Applied to wq/for-3.17-consistent-ops.
Thanks.
--
tejun
--
To unsubscribe from thi
Hi Kukjin,
On 18.07.2014 21:38, Kukjin Kim wrote:
> On 07/16/14 09:56, Tomasz Figa wrote:
>> On 16.07.2014 02:53, Kukjin Kim wrote:
>>> Kukjin Kim wrote:
On 07/05/14 02:48, Tomasz Figa wrote:
> Move debug-macro.S from mach/include to include/debug where
> all other common debug m
Hi Felipe,
On Fri, 18 Jul 2014 10:42:32 -0500 Felipe Balbi wrote:
>
> already in my tree, should be in linux-next already. If not today,
> tomorrow.
Well, Monday (logical tomorrow :-))
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
signature.asc
Description: PGP signatu
On 07/18/14 15:42, John Stultz wrote:
> If its a regression (and needs -stable backports) it needs to go in via
> tip/timers/urgent, and not via the regular merge window.
>
> Whats the additional risk -stable wise for canceling the timer during
> suspend and starting it back up during resume?
>
I'
On Fri, Jul 18, 2014 at 10:17:54AM +0530, Sanjeev Sharma wrote:
> This patch will add an blank line after
> declaration reported by checkpatch.pl script.
>
> Signed-off-by: Sanjeev Sharma
> ---
> drivers/staging/android/sw_sync.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/driver
On Saturday, July 19, 2014 12:55:09 AM Rafael J. Wysocki wrote:
> On Saturday, July 19, 2014 12:19:39 AM Rafael J. Wysocki wrote:
> > On Friday, July 18, 2014 02:45:40 PM Dmitry Torokhov wrote:
> > > On Friday, July 18, 2014 11:59:18 PM Rafael J. Wysocki wrote:
> > > > On Friday, July 18, 2014 02:2
On Fri, Jul 18, 2014 at 09:35:13PM +0300, Igor Bezukh wrote:
> Since there is a lot of stuff that need to be changed in order to meet the
> kernel
> coding style in wcmd.c file, I've decided to fix function-per-patch.
> The following changes were made in vCommandTimerWait function:
>
> - Camel ca
On Fri, Jul 18, 2014 at 11:13:07PM +0300, Sam Asadi wrote:
> A 'quoted string split across lines' issue fixed, while a better use of
> language applied to the comment.
>
> Signed-off-by: Sam Asadi
> ---
> drivers/staging/comedi/drivers/adl_pci9118.c |3 +--
> 1 file changed, 1 insertion(+),
On Fri, Jul 18, 2014 at 05:59:16PM +0200, Samuel Iglesias Gonsálvez wrote:
> On Fri, 2014-07-18 at 17:27 +0200, Benoit Taine wrote:
> > We should prefer `struct pci_device_id` over `DEFINE_PCI_DEVICE_TABLE` to
> > meet
> > kernel coding style guidelines. This issue was reported by checkpatch.
> >
Sorry about the delay.
On Wed, Jul 16, 2014 at 09:28:55AM +0800, Lai Jiangshan wrote:
> On 07/14/2014 12:05 PM, Lai Jiangshan wrote:
> > Simply unfold the code of start_worker() into create_worker() and
> > remove the original start_worker() and create_and_start_worker().
> >
> > The only trade-o
On Fri, Jul 18, 2014 at 06:38:26PM -0400, Tejun Heo wrote:
> On Wed, Jul 16, 2014 at 06:09:59PM +0800, Lai Jiangshan wrote:
> > worker_set_flags() doesn't necessarily wake next worker and the @wakeup
> > can be removed, the caller can use the following conbination instead
> > when needed:
> >
> >
On Fri, Jul 18, 2014 at 06:05:14PM -0400, Tejun Heo wrote:
> On Wed, Jul 16, 2014 at 06:09:58PM +0800, Lai Jiangshan wrote:
> > In this code:
> > if ((worker->flags & WORKER_UNBOUND) && need_more_worker(pool))
> > wake_up_worker(pool);
> >
> > the first test is unneeded. Even the f
Don't break into kgdb when userspace executes the kernel break instructions
(KGDB_BREAKINST and KGDB_COMPILED_BREAK). The kernel will oops in
kgdb_handle_exception.
Signed-off-by: Omar Sandoval
---
The following program will immediately cause a kernel oops:
.globl _start
_start:
udf #
Hello,
On Wed, Jul 16, 2014 at 02:56:50PM +0800, Lai Jiangshan wrote:
> @@ -2300,11 +2300,6 @@ repeat:
> move_linked_works(work, scheduled, &n);
>
> process_scheduled_works(rescuer);
> - spin_unlock_irq(&pool->lock);
> -
> - wor
On Fri, 2014-07-18 at 15:47 -0700, Joe Perches wrote:
> On Fri, 2014-07-18 at 18:22 -0400, Theodore Ts'o wrote:
> > and get_maintainers.pl.
> I think checkpatch
Umm, make that get_maintainer...
> is pretty good about cc'ing mostly the
> right folk by default.
--
To unsubscribe from this list:
On Thu, Jul 17, 2014 at 10:31:37AM +0200, Jan Kara wrote:
> On Wed 16-07-14 23:34:08, Andreas Bombe wrote:
> > On Mon, Jul 14, 2014 at 10:35:27AM +0200, Jan Kara wrote:
> > > On Sun 29-06-14 00:50:50, Andreas Bombe wrote:
> > > > None of the post 3.15 kernel boot for me. They all hang at the GRUB
>
On Fri, 2014-07-18 at 18:22 -0400, Theodore Ts'o wrote:
> On Fri, Jul 18, 2014 at 05:38:30PM +0300, Andrey Utkin wrote:
> > Is there script for automated checkpatch.pl && get_maintainers.pl &&
> > git send-email for range of commits? I see none. Would it be welcome
> > to submit such one to kernel
On Wed, Jul 16, 2014 at 02:56:36PM +0800, Lai Jiangshan wrote:
> We don't need to wake up regular worker when nr_running==1,
> so need_more_worker() is sufficient here.
>
> And need_more_worker() gives us better readability due to the name of
> "keep_working()" implies the rescuer should keep work
On 07/18/2014 03:38 PM, Stephen Boyd wrote:
> On 07/18/14 15:25, John Stultz wrote:
>> On 07/18/2014 03:09 PM, Stephen Boyd wrote:
>>> During suspend we call sched_clock_poll() to update the epoch and
>>> accumulated time and reprogram the sched_clock_timer to fire
>>> before the next wrap-around t
On Fri, Jul 18, 2014 at 10:22:50PM +0200, Peter Zijlstra wrote:
> So the generic stuff seems optimized for 32bit arch, short clocks and
> seems to hard assume the clock is globally consistent.
>
> The x86 sched_clock code is optimized for 64bit, has a full 64bit clock
> and cannot ever assume the
On 07/18/14 15:25, John Stultz wrote:
> On 07/18/2014 03:09 PM, Stephen Boyd wrote:
>> During suspend we call sched_clock_poll() to update the epoch and
>> accumulated time and reprogram the sched_clock_timer to fire
>> before the next wrap-around time. Unfortunately,
>> sched_clock_poll() doesn't
On Wed, Jul 16, 2014 at 06:09:59PM +0800, Lai Jiangshan wrote:
> worker_set_flags() doesn't necessarily wake next worker and the @wakeup
> can be removed, the caller can use the following conbination instead
> when needed:
>
> worker_set_flags();
> if (need_more_worker(pool))
>
1 - 100 of 992 matches
Mail list logo
