Paul, Dave, All,
On Tue, Apr 30, 2013 at 12:25:41PM -0700, Paul E. McKenney wrote:
> On Tue, Apr 30, 2013 at 02:46:12PM -0400, Dave Jones wrote:
> > On Tue, Apr 30, 2013 at 03:21:26PM +, Linux Kernel wrote:
> >
> > > +choice
> > > +prompt "Build-forced no-CBs CPUs"
> > > +
On Tue, Apr 30, 2013 at 05:20:07PM -0400, Dave Jones wrote:
> I have a machine that crashes instantly on boot up on Linus'
> post-3.9 tree. (8c55f1463c1fd318d5e785f02b80bcc32176d342)
>
> By booting with boot_delay=100, I was able to take a photo
> and capture the top of the trace. (For some
On Mon, Apr 29, 2013 at 3:17 PM, Yinghai Lu wrote:
> On Mon, Apr 29, 2013 at 11:15 AM, Bjorn Helgaas wrote:
>>
>> I think the 1a:01.0 pci_dev should retain its reference to the pci_bus
>> for as long as the pci_dev exists, so the pci_bus_put() should go in
>> pci_release_dev() instead.
>
> Good
Rework to implement RapidIO enumeration/discovery method selection
combined with ability to use enumeration/discovery as a kernel module.
This patch adds ability to introduce new RapidIO enumeration/discovery methods
using kernel configuration options. Configuration option mechanism allows to
Add RapidIO enumeration/discovery start from user space.
User space start allows to defer RapidIO fabric scan until the moment when all
participating endpoints are initialized avoiding mandatory synchronized start
of all endpoints (which may be challenging in systems with large number of
RapidIO
Systems that use RapidIO fabric may need to implement their own enumeration
and discovery methods which are better suitable for needs of a target
application.
The following set of patches is intended to simplify process of introduction of
new RapidIO fabric enumeration/discovery methods.
The
Update RapidIO documentation to reflect changes made to enumeration/discovery
build configuration and user space triggering mechanism.
Signed-off-by: Alexandre Bounine
Cc: Matt Porter
Cc: Li Yang
Cc: Kumar Gala
Cc: Andre van Herk
Cc: Micha Nelissen
---
Documentation/rapidio/rapidio.txt |
> > After the 'restore_registers' it returns and we end up called
> > restore_processor_state() - where we reload the GDT. The reload of
> > the GDT is not needed as bootup kernel has already loaded the GDT which
> > is at the same physical location as the the restored kernel.
>
> I'm not sure if
I have a machine that crashes instantly on boot up on Linus'
post-3.9 tree. (8c55f1463c1fd318d5e785f02b80bcc32176d342)
By booting with boot_delay=100, I was able to take a photo
and capture the top of the trace. (For some reason, larger boot
delay parameters seem to make it take forever before
On Tue, 30 Apr 2013, Greg Kroah-Hartman wrote:
> > From: Jonathan Corbet
> > Subject: [PATCH] dummy-irq: require the user to specify an IRQ number
> >
> > Make sure that we let the user know that without specifying IRQ#,
> > dummy-irq driver is useless.
> >
> > Reported-by: Dave Jones
> >
On Tue, 30 Apr 2013, Joe Perches wrote:
> > On Thu, 13 Dec 2012, Hirokazu Takata wrote:
> > > Acked-by: Hirokazu Takata
>
> Hi Jiri.
>
> It's really not useful to cherry-pick a few patches
> from this series.
>
> You must first apply patch 1 of 26 before applying any
> of the others as a new
I merged a slightly better fix, you all were on cc. It's going into
3.10 and it's tagged stable, so it will show up in stable kernels
soon.
Thanks for the fix!
But where did you post it - on LKML?
(I didn't see it because I'm not subscribed to LKML?)
--
To unsubscribe from this list: send the
On Tue, 5 Mar 2013 20:47:34 +0900 Kyungsik Lee wrote:
> This patch integrates the LZ4 decompression code to the arm pre-boot code.
> And it depends on two patchs below
>
> lib: Add support for LZ4-compressed kernel
> decompressor: Add LZ4 decompressor module
>
> ...
>
> - Apply CFLAGS, -Os to
From: Eric Dumazet
commit b6c39bfcf1d7d63 ("net/mlx4_en: Add a service task")
added a build error on 32bit arches.
ERROR: "__udivdi3" [drivers/net/ethernet/mellanox/mlx4/mlx4_en.ko]
undefined!
Fix this problem by using do_div()
Reported-by: Randy Dunlap
Signed-off-by: Eric Dumazet
Acked-by:
On Tue, 30 Apr 2013, Tim Chen wrote:
> Will it be acceptable if I make the per cpu counter list under
> CONFIG_CPU_HOTPLUG default? I will need the list to go through all
> counters to update the batch value sizes. The alternative will be to
> make the configurable batch option only available
On Tue, Apr 30, 2013 at 10:42:33PM +0200, Jiri Kosina wrote:
> From: Jonathan Corbet
> Subject: [PATCH] dummy-irq: require the user to specify an IRQ number
>
> Make sure that we let the user know that without specifying IRQ#,
> dummy-irq driver is useless.
>
> Reported-by: Dave Jones
>
On Tue, 2013-04-30 at 13:39 -0700, Randy Dunlap wrote:
> Yes, that fixes it. Thanks.
>
> Acked-by: Randy Dunlap
>
Thanks, I'll send the official patch in a couple of minutes.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Tuesday 30 April 2013, Lee Jones wrote:
> @@ -6,6 +6,8 @@ Required properties:
> - reg-names: Names of the above areas to use during resource look-up
> - interrupt: Should contain the DMAC interrupt number
> - #dma-cells: must be <3>
> +- memcpy-channels: Channels to be used for memcpy
> +-
On Tuesday 30 April 2013, Lee Jones wrote:
> The DMA platform data is now empty due to some recent refactoring,
> so there is no longer a requirement to pass it though.
>
> Signed-off-by: Lee Jones
Acked-by: Arnd Bergmann
--
To unsubscribe from this list: send the line "unsubscribe
From: Jonathan Corbet
Subject: [PATCH] dummy-irq: require the user to specify an IRQ number
Make sure that we let the user know that without specifying IRQ#,
dummy-irq driver is useless.
Reported-by: Dave Jones
Signed-off-by: Jonathan Corbet
Signed-off-by: Jiri Kosina
diff --git
On Tue, 30 Apr 2013, Jiri Kosina wrote:
> please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial.git for-linus
>
> to receive 3.10 merge window updates from trivial queue.
Unfortunately I made a mistake when merging into for-linus branch, and
omitted one
On 04/30/13 12:36, Eric Dumazet wrote:
> On Tue, 2013-04-30 at 11:58 -0700, Randy Dunlap wrote:
>> On 04/29/13 23:57, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Please do not add any v3.11 destined work to your linux-next included
>>> branches until after v3.10-rc1 is released.
>>>
>>> Changes
Injects EDEADLK conditions at pseudo-random interval, with exponential
backoff up to UINT_MAX (to ensure that every lock operation still
completes in a reasonable time).
This way we can test the wound slowpath even for ww mutex users where
contention is never expected, and the ww deadlock
Hi Chris,
Can we push this change to kernel-3.10?
Thanks,
Maya
> The write packing statistics are used for debug purposes, in order
> to get the amount of packing in different scenarios.
> The statistics also include the reason for stopping the creation of
> the packed request.
>
>
The sanitize support is added as a user-app ioctl call, and
was removed from the block-device request, since its purpose is
to be invoked not via File-System but by a user.
This feature deletes the unmap memory region of the eMMC card,
by writing to a specific register in the EXT_CSD.
unmap region
On Tue, Apr 30, 2013 at 12:25:41PM -0700, Paul E. McKenney wrote:
> On Tue, Apr 30, 2013 at 02:46:12PM -0400, Dave Jones wrote:
> > Additionally, nowhere in any of this text does it say what a "no-CB CPU"
> > is,
> > or why I would care, or even what the downsides are for each option.
>
>
Hi Ulf,
You are right, the caps2 flag for Sanitize can be removed.
I will send a fix for that.
Thanks,
Maya
> On 17 April 2013 13:38, Maya Erez wrote:
>> The sanitize support is added as a user-app ioctl call, and
>> was removed from the block-device request, since its purpose is
>> to be
From: Philip J Kelleher
Verifies the card is not formatting before DMAs are
transferred.
Signed-off-by: Philip J Kelleher
---
diff -uprN -X linux-block-vanilla/Documentation/dontdiff
From: Philip J Kelleher
This changes how the driver schedules the work to the
workqueue threads.
Note: This patch is primarily for the Red Hat 6 Kernels.
Signed-off-by: Philip J Kelleher
---
diff -uprN -X
From: Philip J Kelleher
Unfortunaly, our CPU register path does not do any kind of
EEH error checking. So to fix this issue, an ioread32 was
added to the CPU register timeout code. This way, the
driver can check to see if the timeout was caused by an EEH
error or not.
Signed-off-by: Philip J
On Tuesday, April 30, 2013 08:27:53 AM Greg Kroah-Hartman wrote:
> On Tue, Apr 30, 2013 at 02:01:10PM +0200, Rafael J. Wysocki wrote:
> > On Monday, April 29, 2013 04:11:06 PM Greg Kroah-Hartman wrote:
> > > On Mon, Apr 29, 2013 at 02:28:02PM +0200, Rafael J. Wysocki wrote:
> > > > From: Rafael J.
From: Philip J Kelleher
The previous DMA cancellation mechanism was a little buggy.
It has now been reworked with this patch.
Signed-off-by: Philip J Kelleher
---
diff -uprN -X
On Tuesday, April 30, 2013 08:32:28 AM Greg Kroah-Hartman wrote:
> On Tue, Apr 30, 2013 at 01:59:55PM +0200, Rafael J. Wysocki wrote:
> > On Monday, April 29, 2013 04:10:19 PM Greg Kroah-Hartman wrote:
> > > On Mon, Apr 29, 2013 at 02:26:56PM +0200, Rafael J. Wysocki wrote:
> > > > +static inline
From: Philip J Kelleher
Adding a module parameter called 'sync_start' to wait for
the card to fully up and running before driver load is
complete.
Signed-off-by: Philip J Kelleher
---
diff -uprN -X
From: Philip J Kelleher
Changing the Discard support version number to the correct
value.
Signed-off-by: Philip J Kelleher
---
diff -uprN -X linux-block-vanilla/Documentation/dontdiff
Hey Jens, this is everything I've got ready for 3.10 - there's _still_
one more bug I'm trying to track down.
Andrew - I've got patches that rip out the pkey() and pbtree() macros,
but they're somewhat tied up with some other nontrivial refactorings so
I think I'm going to wait a bit on those.
From: Philip J Kelleher
Fixing incorrect stats calculation during read retries.
Signed-off-by: Philip J Kelleher
---
diff -uprN -X linux-block-vanilla/Documentation/dontdiff
From: Philip J Kelleher
Giving all interrupt based events their own workqueue to complete
tasks on.
Signed-off-by: Philip J Kelleher
---
diff -uprN -X linux-block-vanilla/Documentation/dontdiff
From: Philip J Kelleher
Adding in some sysfs entries to help with debugging and
testing code.
Signed-off-by: Philip J Kelleher
---
diff -uprN -X linux-block-vanilla/Documentation/dontdiff
On Mon, 29 Apr 2013 14:40:05 +0900 Chanho Min wrote:
> Some architectures need __clzsi2() or __clzdi2() for __builtin_clz and
> It causes build failure. They can be implemented using the fls() and
> overridden by linking arch-specific versions may not be implemented yet.
>
> Reference:
On Tue, 2013-04-30 at 11:58 -0700, Randy Dunlap wrote:
> On 04/29/13 23:57, Stephen Rothwell wrote:
> > Hi all,
> >
> > Please do not add any v3.11 destined work to your linux-next included
> > branches until after v3.10-rc1 is released.
> >
> > Changes since 20130429:
> >
>
> on i386:
>
>
On Tue, 2013-04-30 at 20:45 +0200, Daniel Vetter wrote:
> /**
> diff --git a/kernel/mutex.c b/kernel/mutex.c
> index 66807c7..1cc3487 100644
> --- a/kernel/mutex.c
> +++ b/kernel/mutex.c
> @@ -827,6 +827,35 @@ int __sched mutex_trylock(struct mutex *lock)
> EXPORT_SYMBOL(mutex_trylock);
>
>
On Tue, Apr 30, 2013 at 02:46:12PM -0400, Dave Jones wrote:
> On Tue, Apr 30, 2013 at 03:21:26PM +, Linux Kernel wrote:
>
> > +choice
> > + prompt "Build-forced no-CBs CPUs"
> > + default RCU_NOCB_CPU_NONE
> > + help
> > +This option allows no-CBs CPUs to be specified at build
On Tue, 30 Apr 2013 19:09:48 +0200
Sebastian Andrzej Siewior wrote:
> * Clark Williams | 2013-04-29 16:19:25 [-0500]:
>
> >On Mon, 29 Apr 2013 22:12:02 +0200
> >Sebastian Andrzej Siewior wrote:
> >> - suspend / resume seems to program program the timer wrong and wait
> >> ages until
On Sun, Apr 28, 2013 at 07:04:07PM +0200, Maarten Lankhorst wrote:
> Changes since RFC patch v1:
> - Updated to use atomic_long instead of atomic, since the reservation_id was
> a long.
> - added mutex_reserve_lock_slow and mutex_reserve_lock_intr_slow
> - removed
On Tue, Apr 30, 2013 at 06:34:52PM +0100, Stefano Stabellini wrote:
> Konrad, are you going to take care of this patch (assuming that you are
> OK with it)?
Yes. Will push it around rc1.
>
> On Tue, 30 Apr 2013, Julien Grall wrote:
> > Reset the IRQ_NOAUTOEN and IRQ_NOREQUEST flags that are
The context entries field of the slot context must be set to one more
than the highest endpoint index currently active. The previous logic
only included the set of endpoints currently being added, meaning that
if an endpoint where dropped then the field would be reset to 1,
deactivating all
Hello,
On Tue, Apr 30, 2013 at 12:00:57PM -0700, Tim Chen wrote:
> Will it be acceptable if I make the per cpu counter list under
> CONFIG_CPU_HOTPLUG default? I will need the list to go through all
> counters to update the batch value sizes. The alternative will be to
> make the configurable
Lockdep is an awesome piece of code which detects locking issues
which are relevant both to userspace and kernelspace. We can
easily make lockdep work in userspace since there is really no
kernel spacific magic going on in the code.
All we need is to wrap two functions which are used by lockdep
A simple test to make sure we handle rwlocks correctly.
Signed-off-by: Sasha Levin
---
tools/lib/lockdep/tests/WW.c | 13 +
1 file changed, 13 insertions(+)
create mode 100644 tools/lib/lockdep/tests/WW.c
diff --git a/tools/lib/lockdep/tests/WW.c b/tools/lib/lockdep/tests/WW.c
new
kernel/lockdep.c deals with validating locking scenarios for
various architectures supported by the kernel. There isn't
anything kernel specific going on in lockdep, and when we
compare userspace to other architectures that don't have to deal
with irqs such as s390, they become all too similar.
On Tue, 2013-04-30 at 18:27 +, Christoph Lameter wrote:
> On Tue, 30 Apr 2013, Tim Chen wrote:
>
> > > But you will have to dereference the pointer whenever you want the batch
> > > size from the hot path. Looks like it would be better to put the value
> > > there directly. You have a list of
This allows lockdep to be used without being compiled in the
original program.
Usage is quite simple:
LD_PRELOAD=/path/to/liblockdep.so /path/to/my/program
And magically, you'll have lockdep checking in your program!
Signed-off-by: Sasha Levin
---
tools/lib/lockdep/preload.c | 386
On Tue, Apr 30, 2013 at 02:44:18PM +0100, Ian Campbell wrote:
> On Tue, 2013-04-30 at 13:59 +0100, Daniel Kiper wrote:
> > On Mon, Apr 29, 2013 at 03:44:09PM +0100, Ian Campbell wrote:
> > > On Mon, 2013-04-29 at 12:37 +0100, Daniel Kiper wrote:
> > >
> > > > This patch enforces on target limit
This is a rather simple and basic test suite to test common
locking issues.
Beyond tests, it also shows how to use the library.
Signed-off-by: Sasha Levin
---
tools/lib/lockdep/run_tests.sh | 27 +++
tools/lib/lockdep/tests/AA.c | 13 +
These headers provide the same API as their pthread mutex
counterparts.
The design here is to allow to easily switch to liblockdep lock
validation just by adding a "liblockdep_" to pthread_mutex_*()
calls, which means that it's easy to integrate liblockdep into
existing codebases.
Signed-off-by:
On 04/29/13 23:57, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v3.11 destined work to your linux-next included
> branches until after v3.10-rc1 is released.
>
> Changes since 20130429:
>
on i386:
ERROR: "__udivdi3" [drivers/net/ethernet/mellanox/mlx4/mlx4_en.ko] undefined!
Both pthreads and lockdep support dealing with rwlocks, so
here's the liblockdep implementation for those.
Signed-off-by: Sasha Levin
---
tools/lib/lockdep/include/liblockdep/rwlock.h | 91 +++
1 file changed, 91 insertions(+)
create mode 100644
Because it is not used.
Signed-off-by: Oleg Nesterov
---
arch/x86/include/asm/thread_info.h |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/arch/x86/include/asm/thread_info.h
b/arch/x86/include/asm/thread_info.h
index 2cd056e..af71d98 100644
---
This is a simple wrapper to make using liblockdep on existing
applications much easier.
After running 'make && make install', it becomes quite simple to
test things with liblockdep. For example, to try it on perf:
lockdep perf
No other integration required.
Signed-off-by: Sasha Levin
flush_ptrace_hw_breakpoint() destroys the counters set by ptrace, but
"leaks" ->debugreg6 and ->ptrace_dr7.
The problem is minor, but still it doesn't look right and flush_thread()
did this until 66cb5917. Now that PTRACE_DETACH does flush_ too this makes
even more sense.
Signed-off-by: Oleg
On 04/30, Oleg Nesterov wrote:
>
> On 04/30, Frederic Weisbecker wrote:
> >
> > > Btw. perhaps flush_ptrace_hw_breakpoint() should also clear the
> > > virtual registers like thread.debugreg7 ? Even without this patch,
> > > flush_ is also called exec.
> >
> > Yeah makes sense.
>
> OK, and
liblockdep is a tiny wrapper built around kernel/lockdep.c. The aim is to
provide the same functionality the kernel gets from lockdep to userspace.
The bulk of the code here is the LD_PRELOAD support which provides users
an easy way to test their code without having to integrate liblockdep into
Signed-off-by: Sasha Levin
---
MAINTAINERS | 5 +
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8bdd7a7..e39345e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4784,6 +4784,11 @@ F: drivers/lguest/
F: include/linux/lguest*.h
F: tools/lguest/
On Fri, Apr 26, 2013 at 6:01 PM, Dave Airlie wrote:
> On Sat, Apr 27, 2013 at 11:00 AM, Dave Airlie wrote:
>> On Sat, Apr 27, 2013 at 10:37 AM, Andy Lutomirski
>> wrote:
>>> On Wed, Apr 24, 2013 at 12:33 PM, Andy Lutomirski
>>> wrote:
For an upcoming (and, sadly, NDA'd [1]) project, I
On Tue, Apr 30, 2013 at 11:35 AM, Josh Boyer wrote:
> On Tue, Apr 30, 2013 at 10:25:41AM -0700, Kees Cook wrote:
>> To fix /dev/kmsg, let's compare the existing interfaces and what they allow:
>>
>> - /proc/kmsg allows:
>> - open (SYSLOG_ACTION_OPEN) if CAP_SYSLOG since it uses a destructive
>>
> On Tue, Apr 30, 2013 at 01:11:45PM -0500, Naoya Horiguchi wrote:
> >
> > /proc//smaps should not be looking at VM_PFNMAP areas.
> >
> > Certain tests in show_smap() (especially for huge pages) assume that the
> > mapped PFN's are backed with page structures. And this is not usually true
> >
On Tue, Apr 30, 2013 at 03:21:26PM +, Linux Kernel wrote:
> +choice
> +prompt "Build-forced no-CBs CPUs"
> +default RCU_NOCB_CPU_NONE
> +help
> + This option allows no-CBs CPUs to be specified at build time.
> + Additional no-CBs CPUs may be specified by the
From: Davidlohr Bueso
Use the already defined macro to pass the function return address.
Signed-off-by: Davidlohr Bueso
---
kernel/softirq.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/kernel/softirq.c b/kernel/softirq.c
index 14d7758..8cd0d58 100644
---
On Fri, Apr 26, 2013 at 02:38:11PM +0200, Marek Belisko wrote:
> When McASP is bit clock and frame clock master enable pin output for rx
> clocks.
Applied, thanks.
signature.asc
Description: Digital signature
On Thu, Apr 25, 2013 at 03:13:11PM +0200, Marek Belisko wrote:
> changes from v1 (for patch 2 and 3):
> - add prefix linux for compatible property (for both tx and rx)
> - rename spdif_transceiver.c to spdif_transmitter.c
> - add bindings documentation
Applied all, thanks.
signature.asc
Injects EDEADLK conditions at pseudo-random interval, with exponential
backoff up to UINT_MAX (to ensure that every lock operation still
completes in a reasonable time).
This way we can test the wound slowpath even for ww mutex users where
contention is never expected, and the ww deadlock
On 04/29/13 23:57, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v3.11 destined work to your linux-next included
> branches until after v3.10-rc1 is released.
>
> Changes since 20130429:
>
when CONFIG_PROC_FS is not enabled:
sound/core/memalloc.c: In function 'snd_mem_exit':
On Tue, Apr 30, 2013 at 12:07:18PM +0200, Marek Belisko wrote:
> Add new property tx-rx-clk-separate which we can distinquish between common
> and separate clock for tx and rx blocks.
So, this is a sensible thing to have and in fact the core already has
the symmetric_rates flag for this. This
Rev A2 SoCs have an unorthodox memory re-mapping and this needs
to be reflected in the cache operations.
This patch adds new outer cache functions for the l2x0 driver
to support this SoC revision. It also adds a new compatible
value for the cache to enable this functionality.
Signed-off-by:
Hey Stephen and Dave,
On Mon, Apr 29, 2013 at 11:40:02AM +1000, Dave Chinner wrote:
> On Mon, Apr 29, 2013 at 11:29:43AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the xfs tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > ERROR:
On Tue, Apr 30, 2013 at 10:25:41AM -0700, Kees Cook wrote:
> To fix /dev/kmsg, let's compare the existing interfaces and what they allow:
>
> - /proc/kmsg allows:
> - open (SYSLOG_ACTION_OPEN) if CAP_SYSLOG since it uses a destructive
>single-reader interface (SYSLOG_ACTION_READ).
> -
On Tue, Apr 30, 2013 at 04:09:54PM +0200, Fabio Baltieri wrote:
> Update mop500_ab8500_machine_init to register mop500_ab8500_ctrls as
> card control instead of codec control, as it only contains
> SOC_DAPM_PIN_SWITCH definitions.
Applied, thanks.
signature.asc
Description: Digital signature
On Tue, Apr 30, 2013 at 04:09:52PM +0200, Fabio Baltieri wrote:
> Update dapm_clock_event to use clk_prepare_enable and
> clk_disable_unprepare.
Applied, thanks.
signature.asc
Description: Digital signature
On Tue, Apr 30, 2013 at 04:09:53PM +0200, Fabio Baltieri wrote:
> Move ab8500 clock control definitions to the ab8500 codec driver,
> leaving only card specific setting in mop500_ab8500_ctrls.
So, if this is some generic thing and not some weird stuff for the card
this really reopens the question
On Tue, 2013-04-30 at 11:10 -0700, Eric Dumazet wrote:
> On Tue, 2013-04-30 at 09:23 -0700, Tim Chen wrote:
> > On Tue, 2013-04-30 at 13:32 +, Christoph Lameter wrote:
> > > On Mon, 29 Apr 2013, Tim Chen wrote:
> > >
> > > > diff --git a/include/linux/percpu_counter.h
> > > >
On Tue, 30 Apr 2013, Tim Chen wrote:
> > But you will have to dereference the pointer whenever you want the batch
> > size from the hot path. Looks like it would be better to put the value
> > there directly. You have a list of percpu counters that can be traversed
> > to change the batch size.
>
On Tue, 2013-04-30 at 09:23 -0700, Tim Chen wrote:
> On Tue, 2013-04-30 at 13:32 +, Christoph Lameter wrote:
> > On Mon, 29 Apr 2013, Tim Chen wrote:
> >
> > > diff --git a/include/linux/percpu_counter.h
> > > b/include/linux/percpu_counter.h
> > > index d5dd465..5ca7df5 100644
> > > ---
The userspace audit tools didn't like the existing formatting of the
AUDIT_ANOM_LINK event. It needed to be expanded to emit an AUDIT_PATH
event as well, so this implements the change. The bulk of the patch is
moving code out of auditsc.c into audit.c and audit.h for general use.
It expands
[8.910064] [ cut here ]
[8.911030] kernel BUG at net/rfkill/core.c:244!
[8.911030] invalid opcode: [#1] SMP
[8.911030] Modules linked in: hp_wmi(+) psmouse sparse_keymap rfkill
yenta_socket(+) pcmcia_rsrc pcmcia_core snd_hda_intel(+) snd_hda_codec
On Tue, 2013-04-30 at 19:09 +0200, Sebastian Andrzej Siewior wrote:
> The next thing that happens is that RCU assumes nobody is doing any
> progress (for almost 28secs) and triggers NMIs & printks to get some
> attention. I have a trace where
> - CPU0: arch_trigger_all_cpu_backtrace_handler() =>
This is the first round, consisting mostly of drivers and patches
submitted 3 weeks ago. Since I've been travelling quite a bit, there
will be a second round just before the merge window closes for all the
patches three weeks or newer, or which got flagged for my attention
after 10 April.
The
On Tue, 30 Apr 2013, Tim Chen wrote:
> > And why is it a pointer?
>
> A pointer because the default percpu_counter_batch value could change
> later when cpus come online after we initialize per cpu counter and
> percpu_counter_batch will get computed again in percpu_counter_startup.
> Making it a
On Tue, 2013-04-30 at 17:53 +, Christoph Lameter wrote:
> On Tue, 30 Apr 2013, Tim Chen wrote:
>
> > > And why is it a pointer?
> >
> > A pointer because the default percpu_counter_batch value could change
> > later when cpus come online after we initialize per cpu counter and
> >
On 04/30, Frederic Weisbecker wrote:
>
> On Mon, Apr 29, 2013 at 06:40:38PM +0200, Oleg Nesterov wrote:
>
> > No, I think this (minor) problem is very old... At least, when I look
> > at 2.6.26 code I do not see anything which coould clear db regs on
> > detach.
>
> Ok, if so then the conversion
>
> > Maybe the condition around the posix_cpu_timer_schedule() block inside
> > cpu_timer_fire() could even be a good candidate for 'unlikely'
> > qualifier.
>
> Well, cpu_timer_fire() is probably not a fast path. So helping branch
> prediction there probably won't have much measurable effect
On Tue, 2013-04-30 at 17:28 +, Christoph Lameter wrote:
> On Tue, 30 Apr 2013, Tim Chen wrote:
>
> > On Tue, 2013-04-30 at 13:32 +, Christoph Lameter wrote:
> > > On Mon, 29 Apr 2013, Tim Chen wrote:
> > >
> > > > diff --git a/include/linux/percpu_counter.h
> > > >
On 04/30/13 09:36, David Rientjes wrote:
> On Mon, 29 Apr 2013, Randy Dunlap wrote:
>
>> From: Randy Dunlap
>>
>> Fix build error when CONFIG_PROC_FS is not enabled:
>> (remove duplicated line)
>>
>> include/linux/proc_fs.h:58:20: error: redefinition of 'proc_set_size'
>>
On Mon, Apr 29, 2013 at 05:22:52PM -0700, David Rientjes wrote:
> This exports the amount of anonymous transparent hugepages for each memcg
> via the new "rss_huge" stat in memory.stat. The units are in bytes.
>
> This is helpful to determine the hugepage utilization for individual jobs
> on the
> > What is this for and why does it have that alignmend?
>
> I was assuming that if batch is frequently referenced, it probably
> should not share a cache line with the counters field.
As long as they are both read-mostly it should be fine to share
(cache line will just be SHARED)
Padding
Konrad, are you going to take care of this patch (assuming that you are
OK with it)?
On Tue, 30 Apr 2013, Julien Grall wrote:
> Reset the IRQ_NOAUTOEN and IRQ_NOREQUEST flags that are enabled by
> default on ARM. If IRQ_NOAUTOEN is set, __setup_irq doesn't call
> irq_startup, that is responsible
On Tue, 30 Apr 2013, Tim Chen wrote:
> On Tue, 2013-04-30 at 13:32 +, Christoph Lameter wrote:
> > On Mon, 29 Apr 2013, Tim Chen wrote:
> >
> > > diff --git a/include/linux/percpu_counter.h
> > > b/include/linux/percpu_counter.h
> > > index d5dd465..5ca7df5 100644
> > > ---
On Tue, Apr 30, 2013 at 1:21 AM, Bin Gao wrote:
> x86/pci/mrst: force all pci config access toward 0:0:0, 0:2:0 and 0:3:0 to
> type 1
>
> For real pci devices 0:0:0, 0:2:0 and 0:3:0, there is either no pci shim, or
> no guarantee of data correctness of offset 256-4k. So for whatever reason,
>
On Tue, 2013-04-30 at 16:52 +0900, Jonghwan Choi wrote:
> This patch looks like it should be in the 3.8-stable tree, should we apply
> it?
>
I don't see this as a candidate for stable. Its just an optimization and
doesn't address any existing issue.
Thanks,
Davidlohr
--
To unsubscribe from
Ladies and Gentlemen,
I'm glad to announce the 5th release of the checkpoint-restore tool!
This release is mostly about the tool itself. The v3.9 kernel, with which the
new CRIU tool should be used, only contains a couple of bug fixes related to
the C/R project and no new related features. As
101 - 200 of 926 matches
Mail list logo
