[PATCH net-next 08/24] rxrpc: Check that the client conns cache is empty before module removal

Check that the client conns cache is empty before module removal and bug if not, listing any offending connections that are still present. Unfortunately, if there are connections still around, then the transport socket is still unexpectedly open and active, so we can't just unallocate the

[PATCH net-next 18/24] rxrpc: Maintain an extra ref on a conn for the cache list

Overhaul the usage count accounting for the rxrpc_connection struct to make it easier to implement RCU access from the data_ready handler. The problem is that currently we're using a lock to prevent the garbage collector from trying to clean up a connection that we're contemplating unidling. We

[PATCH net-next 08/24] rxrpc: Check that the client conns cache is empty before module removal

Check that the client conns cache is empty before module removal and bug if not, listing any offending connections that are still present. Unfortunately, if there are connections still around, then the transport socket is still unexpectedly open and active, so we can't just unallocate the

[PATCH net-next 11/24] rxrpc: Release a call's connection ref on call disconnection

When a call is disconnected, clear the call's pointer to the connection and release the associated ref on that connection. This means that the call no longer pins the connection and the connection can be discarded even before the call is. As the code currently stands, the call struct is

[PATCH net-next 23/24] rxrpc: Use RCU to access a peer's service connection tree

Move to using RCU access to a peer's service connection tree when routing an incoming packet. This is done using a seqlock to trigger retrying of the tree walk if a change happened. Further, we no longer get a ref on the connection looked up in the data_ready handler unless we queue the

Re: [PATCHv4 wl-drv-next 2/2] mt7601u: use linux/bitfield.h

Jakub Kicinski writes: > Use the newly added linux/bitfield.h. > > Signed-off-by: Jakub Kicinski [...] > +#define MT76_SET FIELD_PUT > +#define MT76_GET FIELD_GET This define is useless now, I would just remove it entirely.

[PATCH net-next 23/24] rxrpc: Use RCU to access a peer's service connection tree

Move to using RCU access to a peer's service connection tree when routing an incoming packet. This is done using a seqlock to trigger retrying of the tree walk if a change happened. Further, we no longer get a ref on the connection looked up in the data_ready handler unless we queue the

Re: [PATCHv4 wl-drv-next 2/2] mt7601u: use linux/bitfield.h

Jakub Kicinski writes: > Use the newly added linux/bitfield.h. > > Signed-off-by: Jakub Kicinski [...] > +#define MT76_SET FIELD_PUT > +#define MT76_GET FIELD_GET This define is useless now, I would just remove it entirely. But you can do that in a follow up patch. -- Kalle Valo

[PATCH net-next 22/24] rcu: Suppress sparse warnings for rcu_dereference_raw()

From: Paul E. McKenney Data structures that are used both with and without RCU protection are difficult to write in a sparse-clean manner. If you mark the relevant pointers with __rcu, sparse will complain about all non-RCU uses, but if you don't mark those pointers,

[PATCH net-next 22/24] rcu: Suppress sparse warnings for rcu_dereference_raw()

From: Paul E. McKenney Data structures that are used both with and without RCU protection are difficult to write in a sparse-clean manner. If you mark the relevant pointers with __rcu, sparse will complain about all non-RCU uses, but if you don't mark those pointers, sparse will complain about

[PATCH net-next 24/24] rxrpc: Kill off the call hash table

The call hash table is now no longer used as calls are looked up directly by channel slot on the connection, so kill it off. Signed-off-by: David Howells --- net/rxrpc/ar-internal.h | 13 +--- net/rxrpc/call_object.c | 173 ---

[PATCH net-next 24/24] rxrpc: Kill off the call hash table

The call hash table is now no longer used as calls are looked up directly by channel slot on the connection, so kill it off. Signed-off-by: David Howells --- net/rxrpc/ar-internal.h | 13 +--- net/rxrpc/call_object.c | 173 --- 2 files changed, 2

[PATCH net-next 21/24] Introduce rb_replace_node_rcu()

Implement an RCU-safe variant of rb_replace_node() and rearrange rb_replace_node() to do things in the same order. Signed-off-by: David Howells Acked-by: Peter Zijlstra (Intel) --- include/linux/rbtree.h |2 ++

[PATCH net-next 21/24] Introduce rb_replace_node_rcu()

Implement an RCU-safe variant of rb_replace_node() and rearrange rb_replace_node() to do things in the same order. Signed-off-by: David Howells Acked-by: Peter Zijlstra (Intel) --- include/linux/rbtree.h |2 ++ include/linux/rbtree_augmented.h | 13 + lib/rbtree.c

[PATCH net-next 03/24] rxrpc: Check the source of a packet to a client conn

When looking up a client connection to which to route a packet, we need to check that the packet came from the correct source so that a peer can't try to muck around with another peer's connection. Signed-off-by: David Howells --- net/rxrpc/conn_object.c |4 +++- 1

[PATCH net-next 04/24] rxrpc: Avoid using stack memory in SG lists in rxkad

From: Herbert Xu rxkad uses stack memory in SG lists which would not work if stacks were allocated from vmalloc memory. In fact, in most cases this isn't even necessary as the stack memory ends up getting copied over to kmalloc memory. This patch eliminates all the

[PATCH net-next 20/24] rxrpc: Move data_ready peer lookup into rxrpc_find_connection()

Move the peer lookup done in input.c by data_ready into rxrpc_find_connection(). Signed-off-by: David Howells --- net/rxrpc/ar-internal.h |3 -- net/rxrpc/conn_object.c | 73 --- net/rxrpc/input.c | 30

[PATCH net-next 07/24] rxrpc: Turn connection #defines into enums and put outside struct def

Turn the connection event and state #define lists into enums and move outside of the struct definition. Whilst we're at it, change _SERVER to _SERVICE in those identifiers and add EV_ into the event name to distinguish them from flags and states. Also add a symbol indicating the number of states

[PATCH net-next 02/24] rxrpc: Fix some sparse errors

Fix the following sparse errors: ../net/rxrpc/conn_object.c:77:17: warning: incorrect type in assignment (different base types) ../net/rxrpc/conn_object.c:77:17:expected restricted __be32 [usertype] call_id ../net/rxrpc/conn_object.c:77:17:got unsigned int [unsigned] [usertype] call_id

[PATCH net-next 03/24] rxrpc: Check the source of a packet to a client conn

When looking up a client connection to which to route a packet, we need to check that the packet came from the correct source so that a peer can't try to muck around with another peer's connection. Signed-off-by: David Howells --- net/rxrpc/conn_object.c |4 +++- 1 file changed, 3

[PATCH net-next 04/24] rxrpc: Avoid using stack memory in SG lists in rxkad

From: Herbert Xu rxkad uses stack memory in SG lists which would not work if stacks were allocated from vmalloc memory. In fact, in most cases this isn't even necessary as the stack memory ends up getting copied over to kmalloc memory. This patch eliminates all the unnecessary stack memory

[PATCH net-next 20/24] rxrpc: Move data_ready peer lookup into rxrpc_find_connection()

Move the peer lookup done in input.c by data_ready into rxrpc_find_connection(). Signed-off-by: David Howells --- net/rxrpc/ar-internal.h |3 -- net/rxrpc/conn_object.c | 73 --- net/rxrpc/input.c | 30 ++-

[PATCH net-next 07/24] rxrpc: Turn connection #defines into enums and put outside struct def

Turn the connection event and state #define lists into enums and move outside of the struct definition. Whilst we're at it, change _SERVER to _SERVICE in those identifiers and add EV_ into the event name to distinguish them from flags and states. Also add a symbol indicating the number of states

[PATCH net-next 02/24] rxrpc: Fix some sparse errors

Fix the following sparse errors: ../net/rxrpc/conn_object.c:77:17: warning: incorrect type in assignment (different base types) ../net/rxrpc/conn_object.c:77:17:expected restricted __be32 [usertype] call_id ../net/rxrpc/conn_object.c:77:17:got unsigned int [unsigned] [usertype] call_id

[PATCH net-next 19/24] rxrpc: Prune the contents of the rxrpc_conn_proto struct

Prune the contents of the rxrpc_conn_proto struct. Most of the fields aren't used anymore. Signed-off-by: David Howells --- net/rxrpc/ar-internal.h | 20 +++- net/rxrpc/call_object.c |2 +- net/rxrpc/conn_client.c | 11 ---

[PATCH net-next 19/24] rxrpc: Prune the contents of the rxrpc_conn_proto struct

Prune the contents of the rxrpc_conn_proto struct. Most of the fields aren't used anymore. Signed-off-by: David Howells --- net/rxrpc/ar-internal.h | 20 +++- net/rxrpc/call_object.c |2 +- net/rxrpc/conn_client.c | 11 --- net/rxrpc/conn_service.c |2 --

Re: [PATCH v3 0/4] sched,time: fix irq time accounting with nohz_idle

On Tue, 2016-07-05 at 16:02 +0300, Nikolay Borisov wrote: > > On 06/30/2016 10:35 PM, r...@redhat.com wrote: > > Currently irq time accounting only works in these cases: > > 1) purely ticke based accounting > > 2) nohz_full accounting, but only on housekeeping & nohz_full CPUs > > 3)

Re: [PATCH] mwifiex: fix unconditional error return in .add_virtual_intf callback

Javier Martinez Canillas writes: > The commit 7311ea850079 ("mwifiex: fix AP start problem for newly added > interface") attempted to fix an issue when a new AP interface is added. > > But the patch didn't check the return value of the functions doing the > firmware calls

Re: [PATCH v3 0/4] sched,time: fix irq time accounting with nohz_idle

On Tue, 2016-07-05 at 16:02 +0300, Nikolay Borisov wrote: > > On 06/30/2016 10:35 PM, r...@redhat.com wrote: > > Currently irq time accounting only works in these cases: > > 1) purely ticke based accounting > > 2) nohz_full accounting, but only on housekeeping & nohz_full CPUs > > 3)

Re: [PATCH] mwifiex: fix unconditional error return in .add_virtual_intf callback

Javier Martinez Canillas writes: > The commit 7311ea850079 ("mwifiex: fix AP start problem for newly added > interface") attempted to fix an issue when a new AP interface is added. > > But the patch didn't check the return value of the functions doing the > firmware calls and returned an error

Re: [PATCH] gpio: of: Allow overriding the device node

On Tue, Jul 5, 2016 at 9:11 PM, Thierry Reding wrote: > From: Thierry Reding > > When registering a GPIO chip, drivers can override the device tree node > associated with the chip by setting the chip's ->of_node field. If set, > this field is

Re: [PATCH 1/4] sched,time: count actually elapsed irq & softirq time

On Tue, 2016-07-05 at 14:40 +0200, Frederic Weisbecker wrote: > On Thu, Jun 30, 2016 at 03:35:47PM -0400, r...@redhat.com wrote: > > diff --git a/kernel/sched/cputime.c b/kernel/sched/cputime.c > > index 3d60e5d76fdb..018bae2ada36 100644 > > --- a/kernel/sched/cputime.c > > +++

Re: [PATCH] gpio: of: Allow overriding the device node

On Tue, Jul 5, 2016 at 9:11 PM, Thierry Reding wrote: > From: Thierry Reding > > When registering a GPIO chip, drivers can override the device tree node > associated with the chip by setting the chip's ->of_node field. If set, > this field is supposed to take precedence over the

Re: [PATCH 1/4] sched,time: count actually elapsed irq & softirq time

On Tue, 2016-07-05 at 14:40 +0200, Frederic Weisbecker wrote: > On Thu, Jun 30, 2016 at 03:35:47PM -0400, r...@redhat.com wrote: > > diff --git a/kernel/sched/cputime.c b/kernel/sched/cputime.c > > index 3d60e5d76fdb..018bae2ada36 100644 > > --- a/kernel/sched/cputime.c > > +++

PCI bus error on startup while booting

Please cc me on any communication I am not subscribed to the list [1.] One line summary of the problem: PCI bus error on startup while booting into login screen (Kubuntu 16.04) [2.] Full description of the problem/report: With a HP Pavilion Notebook - 15-ab549tx, and Kubuntu 16.04, the problem

PCI bus error on startup while booting

Please cc me on any communication I am not subscribed to the list [1.] One line summary of the problem: PCI bus error on startup while booting into login screen (Kubuntu 16.04) [2.] Full description of the problem/report: With a HP Pavilion Notebook - 15-ab549tx, and Kubuntu 16.04, the problem

Re: [PATCH] arm64: dts: Fix rtc by providing rtc_src clock

Hello Alim, On 07/05/2016 06:05 AM, Alim Akhtar wrote: > Add rtc source clock as exynos7 needs source (32.768KHz) clock > for rtc block. Without this currently rtc driver probe is broken > on this SoC, thats because rtc-s3c driver expect rtc_src clock to > be provided for _s3c6410-rtc_ type rtc

Re: [PATCH v3 0/4] sched,time: fix irq time accounting with nohz_idle

On 06/30/2016 10:35 PM, r...@redhat.com wrote: > Currently irq time accounting only works in these cases: > 1) purely ticke based accounting > 2) nohz_full accounting, but only on housekeeping & nohz_full CPUs > 3) architectures with native vtime accounting > > On nohz_idle CPUs, which are

Re: [PATCH] arm64: dts: Fix rtc by providing rtc_src clock

Hello Alim, On 07/05/2016 06:05 AM, Alim Akhtar wrote: > Add rtc source clock as exynos7 needs source (32.768KHz) clock > for rtc block. Without this currently rtc driver probe is broken > on this SoC, thats because rtc-s3c driver expect rtc_src clock to > be provided for _s3c6410-rtc_ type rtc

Re: [PATCH v3 0/4] sched,time: fix irq time accounting with nohz_idle

On 06/30/2016 10:35 PM, r...@redhat.com wrote: > Currently irq time accounting only works in these cases: > 1) purely ticke based accounting > 2) nohz_full accounting, but only on housekeeping & nohz_full CPUs > 3) architectures with native vtime accounting > > On nohz_idle CPUs, which are

Re: [PATCH 3/3] reset: socfpga: use readl/writel_relaxed

On Tuesday, July 5, 2016 1:40:16 PM CEST Philipp Zabel wrote: > Am Dienstag, den 05.07.2016, 13:20 +0200 schrieb Arnd Bergmann: > > On Tuesday, July 5, 2016 12:17:52 PM CEST Philipp Zabel wrote: > > > This just removes the rmb()/wmb() pair between register read and > > > write. Since no relevant

Re: [PATCH 3/3] reset: socfpga: use readl/writel_relaxed

On Tuesday, July 5, 2016 1:40:16 PM CEST Philipp Zabel wrote: > Am Dienstag, den 05.07.2016, 13:20 +0200 schrieb Arnd Bergmann: > > On Tuesday, July 5, 2016 12:17:52 PM CEST Philipp Zabel wrote: > > > This just removes the rmb()/wmb() pair between register read and > > > write. Since no relevant

Re: [PATCH] perf: fix pmu::filter_match for SW-led groups

On Tue, Jul 05, 2016 at 02:04:26PM +0200, Peter Zijlstra wrote: > On Tue, Jul 05, 2016 at 10:44:48AM +0100, Mark Rutland wrote: > > My bad; I assumed that for both PMUs we'd start at the root, and thus > > would need to re-sort in order to get the current CPU's PMU ordered > > first, much like

Re: [PATCH] perf: fix pmu::filter_match for SW-led groups

On Tue, Jul 05, 2016 at 02:04:26PM +0200, Peter Zijlstra wrote: > On Tue, Jul 05, 2016 at 10:44:48AM +0100, Mark Rutland wrote: > > My bad; I assumed that for both PMUs we'd start at the root, and thus > > would need to re-sort in order to get the current CPU's PMU ordered > > first, much like

Re: [PATCH] sched/core: really pretend early bootup to be a normal task

On 05.07.2016 15:41, Peter Zijlstra wrote: On Tue, Jul 05, 2016 at 02:23:23PM +0300, Konstantin Khlebnikov wrote: Commit 1b537c7d1e58 ("sched/core: Remove check of p->sched_class") placed "current->sched_class = _sched_class" before call of init_idle() which immediately set sched_class back to

Re: [PATCH] sched/core: really pretend early bootup to be a normal task

On 05.07.2016 15:41, Peter Zijlstra wrote: On Tue, Jul 05, 2016 at 02:23:23PM +0300, Konstantin Khlebnikov wrote: Commit 1b537c7d1e58 ("sched/core: Remove check of p->sched_class") placed "current->sched_class = _sched_class" before call of init_idle() which immediately set sched_class back to

Re: [linux-sunxi] [PATCH 2/4] power: add axp20x-battery driver

On Tue, 5 Jul 2016 11:25:10 +0200 Maxime Ripard wrote: > On Tue, Jul 05, 2016 at 04:33:31PM +0800, Icenowy Zheng wrote: > > > > > > 05.07.2016, 13:26, "Michael Haas" : > > > Hi, > > > > > > nice work! Is this in any way related to Bruno Prémonts driver for the > > >

Re: [linux-sunxi] [PATCH 2/4] power: add axp20x-battery driver

On Tue, 5 Jul 2016 11:25:10 +0200 Maxime Ripard wrote: > On Tue, Jul 05, 2016 at 04:33:31PM +0800, Icenowy Zheng wrote: > > > > > > 05.07.2016, 13:26, "Michael Haas" : > > > Hi, > > > > > > nice work! Is this in any way related to Bruno Prémonts driver for the > > > axp20x? > > > > > > I've

Re: [linux-sunxi] [PATCH 2/4] power: add axp20x-battery driver

On Tue, 05 Jul 2016 16:47:38 +0800 Icenowy Zheng wrote: > I read the datasheet of axp20x, and then found that this driver does > not support backup RTC battery. > (But maybe backup battery do not need a driver -- at least on IBM PC > it has no driver) A driver is needed to enable/disable the RTC

Re: [linux-sunxi] [PATCH 2/4] power: add axp20x-battery driver

On Tue, 05 Jul 2016 16:47:38 +0800 Icenowy Zheng wrote: > I read the datasheet of axp20x, and then found that this driver does > not support backup RTC battery. > (But maybe backup battery do not need a driver -- at least on IBM PC > it has no driver) A driver is needed to enable/disable the RTC

Email

Hello, My name is Mr. Richard Sun from Hong Kong. I want you to be my partner in a business project. Contact me back via my private e-mail address for more details; ricadt...@ymail.com Thank you. Mr. Richard Sun.

Email

Hello, My name is Mr. Richard Sun from Hong Kong. I want you to be my partner in a business project. Contact me back via my private e-mail address for more details; ricadt...@ymail.com Thank you. Mr. Richard Sun.

Re: [PATCH v2 0/6] Intel Integrated Sensor Hub Support (ISH)

On 22/06/16 06:40, Srinivas Pandruvada wrote: Change log v2: - Overview in documentation show analogy with usbhid implementation - sparse errors for statics. Also pointed by Jiri - Clearly marking exported function header file. Clean up all exports unused inteface functions - Changed to

Re: [PATCH v2 0/6] Intel Integrated Sensor Hub Support (ISH)

On 22/06/16 06:40, Srinivas Pandruvada wrote: Change log v2: - Overview in documentation show analogy with usbhid implementation - sparse errors for statics. Also pointed by Jiri - Clearly marking exported function header file. Clean up all exports unused inteface functions - Changed to

Re: [PATCH] sched/core: really pretend early bootup to be a normal task

On Tue, Jul 05, 2016 at 02:23:23PM +0300, Konstantin Khlebnikov wrote: > Commit 1b537c7d1e58 ("sched/core: Remove check of p->sched_class") placed > "current->sched_class = _sched_class" before call of init_idle() which > immediately set sched_class back to idle_sched_class. > > This patch

Re: [PATCH] sched/core: really pretend early bootup to be a normal task

On Tue, Jul 05, 2016 at 02:23:23PM +0300, Konstantin Khlebnikov wrote: > Commit 1b537c7d1e58 ("sched/core: Remove check of p->sched_class") placed > "current->sched_class = _sched_class" before call of init_idle() which > immediately set sched_class back to idle_sched_class. > > This patch

Re: [PATCH 1/4] sched,time: count actually elapsed irq & softirq time

On Thu, Jun 30, 2016 at 03:35:47PM -0400, r...@redhat.com wrote: > diff --git a/kernel/sched/cputime.c b/kernel/sched/cputime.c > index 3d60e5d76fdb..018bae2ada36 100644 > --- a/kernel/sched/cputime.c > +++ b/kernel/sched/cputime.c > @@ -79,40 +79,50 @@ void irqtime_account_irq(struct task_struct

Re: [PATCH 1/4] sched,time: count actually elapsed irq & softirq time

On Thu, Jun 30, 2016 at 03:35:47PM -0400, r...@redhat.com wrote: > diff --git a/kernel/sched/cputime.c b/kernel/sched/cputime.c > index 3d60e5d76fdb..018bae2ada36 100644 > --- a/kernel/sched/cputime.c > +++ b/kernel/sched/cputime.c > @@ -79,40 +79,50 @@ void irqtime_account_irq(struct task_struct

Re: [PATCH] lpfc: Fix possible NULL pointer dereference

On Tue, Jun 28, 2016 at 01:28:19PM -0700, Tyrel Datwyler wrote: > On 06/15/2016 06:00 AM, Johannes Thumshirn wrote: > > Check for the existance of pciob->vport before accessing it. > > piocb mispelled. Oops > > > > > Signed-off-by: Johannes Thumshirn > > --- > >

Re: [PATCH] lpfc: Fix possible NULL pointer dereference

On Tue, Jun 28, 2016 at 01:28:19PM -0700, Tyrel Datwyler wrote: > On 06/15/2016 06:00 AM, Johannes Thumshirn wrote: > > Check for the existance of pciob->vport before accessing it. > > piocb mispelled. Oops > > > > > Signed-off-by: Johannes Thumshirn > > --- > > drivers/scsi/lpfc/lpfc_sli.c

Re: More parallel atomic_open/d_splice_alias fun with NFS and possibly more FSes.

On Tue, Jul 05, 2016 at 02:22:48AM -0400, Oleg Drokin wrote: > > + if (!(open_flags & O_CREAT) && !d_unhashed(dentry)) { s/d_unhashed/d_in_lookup/ in that. > So we come racing here from multiple threads (say 3 or more - we have seen > this > in the older crash reports, so totally possible) >

Re: More parallel atomic_open/d_splice_alias fun with NFS and possibly more FSes.

On Tue, Jul 05, 2016 at 02:22:48AM -0400, Oleg Drokin wrote: > > + if (!(open_flags & O_CREAT) && !d_unhashed(dentry)) { s/d_unhashed/d_in_lookup/ in that. > So we come racing here from multiple threads (say 3 or more - we have seen > this > in the older crash reports, so totally possible) >

Re: [RFC PATCH v1] irqchip: add support for SMP irq router

On 07/04/2016 02:11 PM, Mason wrote: > > In the patch subject, do you mean SMP as in Symmetric Multi Processor? As in Sigma Multimedia Processor :-) The prefix for Sigma's chips is SMP. I can change that to "Tango" if it is confusing. > > Is that the address you intend to submit with? Yes.

Re: [RFC PATCH v1] irqchip: add support for SMP irq router

On 07/04/2016 02:11 PM, Mason wrote: > > In the patch subject, do you mean SMP as in Symmetric Multi Processor? As in Sigma Multimedia Processor :-) The prefix for Sigma's chips is SMP. I can change that to "Tango" if it is confusing. > > Is that the address you intend to submit with? Yes.

[PATCH] PM / hibernate: Image data protection during restoration

From: Rafael J. Wysocki Make it possible to protect all pages holding image data during hibernate image restoration by marking them read-only (so as to catch attempts to write to those pages after image data have been stored in them). This adds overhead to image

[PATCH] PM / hibernate: Image data protection during restoration

From: Rafael J. Wysocki Make it possible to protect all pages holding image data during hibernate image restoration by marking them read-only (so as to catch attempts to write to those pages after image data have been stored in them). This adds overhead to image restoration code (it may cause

[PATCH] perf: use right filename to test

When trying to read buildid from file in function tools/perf/util/symbol.c:dso_load(), perf used wrong filename to test. The variable 'name' has just allocated and uninitialized before this sentence.Obviously, the test 'is_regular_file()' is for the latter 'filename__read_build_id()', so the right

[PATCH] perf: use right filename to test

When trying to read buildid from file in function tools/perf/util/symbol.c:dso_load(), perf used wrong filename to test. The variable 'name' has just allocated and uninitialized before this sentence.Obviously, the test 'is_regular_file()' is for the latter 'filename__read_build_id()', so the right

Re: Tool for sampling /proc/net/softnet_stat statistics

On Tue, 8 Mar 2016 10:50:56 +0100 Jesper Dangaard Brouer wrote: > On Mon, 7 Mar 2016 12:54:13 -0500 > Willem de Bruijn wrote: > > > On Mon, Mar 7, 2016 at 10:36 AM, Jesper Dangaard Brouer > > wrote: > > > Hi Google, >

Re: Tool for sampling /proc/net/softnet_stat statistics

On Tue, 8 Mar 2016 10:50:56 +0100 Jesper Dangaard Brouer wrote: > On Mon, 7 Mar 2016 12:54:13 -0500 > Willem de Bruijn wrote: > > > On Mon, Mar 7, 2016 at 10:36 AM, Jesper Dangaard Brouer > > wrote: > > > Hi Google, > > > > > > While playing with RPS, I needed to read stats from > > >

Re: [PATCH 0/2] KVM: MMU: support VMAs that got remap_pfn_range-ed

On 05/07/2016 07:41, Neo Jia wrote: > On Thu, Jun 30, 2016 at 03:01:49PM +0200, Paolo Bonzini wrote: >> The vGPU folks would like to trap the first access to a BAR by setting >> vm_ops on the VMAs produced by mmap-ing a VFIO device. The fault handler >> then can use remap_pfn_range to place

Re: [PATCH 0/2] KVM: MMU: support VMAs that got remap_pfn_range-ed

On 05/07/2016 07:41, Neo Jia wrote: > On Thu, Jun 30, 2016 at 03:01:49PM +0200, Paolo Bonzini wrote: >> The vGPU folks would like to trap the first access to a BAR by setting >> vm_ops on the VMAs produced by mmap-ing a VFIO device. The fault handler >> then can use remap_pfn_range to place

[V3 PATCH 1/2] x86/panic: Replace smp_send_stop() with kdump friendly version

This patch fixes one of the problems reported by Daniel Walker (https://lkml.org/lkml/2015/6/24/44). If crash_kexec_post_notifiers boot option is specified, other CPUs are stopped by smp_send_stop() instead of machine_crash_shutdown() in crash_kexec() path. This behavior change leads two

[V3 PATCH 1/2] x86/panic: Replace smp_send_stop() with kdump friendly version

This patch fixes one of the problems reported by Daniel Walker (https://lkml.org/lkml/2015/6/24/44). If crash_kexec_post_notifiers boot option is specified, other CPUs are stopped by smp_send_stop() instead of machine_crash_shutdown() in crash_kexec() path. This behavior change leads two

usb: memory allocation WARNING in hcd_buffer_alloc

Hello, The following program trigger the following WARNING: [ cut here ] WARNING: CPU: 0 PID: 6263 at mm/page_alloc.c:3584[< inline >] __alloc_pages_slowpath mm/page_alloc.c:3584 WARNING: CPU: 0 PID: 6263 at mm/page_alloc.c:3584[< none >]

usb: memory allocation WARNING in hcd_buffer_alloc

Hello, The following program trigger the following WARNING: [ cut here ] WARNING: CPU: 0 PID: 6263 at mm/page_alloc.c:3584[< inline >] __alloc_pages_slowpath mm/page_alloc.c:3584 WARNING: CPU: 0 PID: 6263 at mm/page_alloc.c:3584[< none >]

[V3 PATCH 2/2] kexec: Use core_param for crash_kexec_post_notifiers boot option

crash_kexec_post_notifiers ia a boot option which controls whether the 1st kernel calls panic notifiers or not before booting the 2nd kernel. However, there is no need to limit it to being modifiable only at boot time. So, use core_param instead of early_param. Signed-off-by: Hidehiro Kawai

[V3 PATCH 2/2] kexec: Use core_param for crash_kexec_post_notifiers boot option

crash_kexec_post_notifiers ia a boot option which controls whether the 1st kernel calls panic notifiers or not before booting the 2nd kernel. However, there is no need to limit it to being modifiable only at boot time. So, use core_param instead of early_param. Signed-off-by: Hidehiro Kawai

[V3 PATCH 0/2] kexec: crash_kexec_post_notifiers boot option related fixes

This is the update version of the patch which I posted one year ago (https://lkml.org/lkml/2015/7/23/864). Because I couldn't received positive opinions against the previous version, I had changed the approach to another one which utilizes kexec purgatory. Then I'm back here. PATCH 1/2 is a

[V3 PATCH 0/2] kexec: crash_kexec_post_notifiers boot option related fixes

This is the update version of the patch which I posted one year ago (https://lkml.org/lkml/2015/7/23/864). Because I couldn't received positive opinions against the previous version, I had changed the approach to another one which utilizes kexec purgatory. Then I'm back here. PATCH 1/2 is a

[PATCH] gpio: of: Allow overriding the device node

From: Thierry Reding When registering a GPIO chip, drivers can override the device tree node associated with the chip by setting the chip's ->of_node field. If set, this field is supposed to take precedence over the ->parent->of_node field, but the code doesn't actually do

[PATCH] gpio: of: Allow overriding the device node

From: Thierry Reding When registering a GPIO chip, drivers can override the device tree node associated with the chip by setting the chip's ->of_node field. If set, this field is supposed to take precedence over the ->parent->of_node field, but the code doesn't actually do that. Commit

Re: [PATCH 2/3] ARM: dts: imx6sx: Add UDOO Neo support

On Tue, Jul 5, 2016 at 1:04 AM, Andreas Färber wrote: > +/dts-v1/; > + > +#include "imx6sx-udoo-neo.dtsi" > + > +/ { > + model = "UDOO Neo Basic"; This should be something like: model = "Udoo i.MX6 SoloX UDOO Neo Basic"; > + compatible = "fsl,imx6sx"; compatible

Re: [PATCH 2/3] ARM: dts: imx6sx: Add UDOO Neo support

On Tue, Jul 5, 2016 at 1:04 AM, Andreas Färber wrote: > +/dts-v1/; > + > +#include "imx6sx-udoo-neo.dtsi" > + > +/ { > + model = "UDOO Neo Basic"; This should be something like: model = "Udoo i.MX6 SoloX UDOO Neo Basic"; > + compatible = "fsl,imx6sx"; compatible =

Re: [PATCH] perf: fix pmu::filter_match for SW-led groups

On Tue, Jul 05, 2016 at 10:44:48AM +0100, Mark Rutland wrote: > My bad; I assumed that for both PMUs we'd start at the root, and thus > would need to re-sort in order to get the current CPU's PMU ordered > first, much like currently with rotation. > > I guess I'm having difficulty figuring out

Re: [PATCH] perf: fix pmu::filter_match for SW-led groups

On Tue, Jul 05, 2016 at 10:44:48AM +0100, Mark Rutland wrote: > My bad; I assumed that for both PMUs we'd start at the root, and thus > would need to re-sort in order to get the current CPU's PMU ordered > first, much like currently with rotation. > > I guess I'm having difficulty figuring out

dccp: potential deadlock in dccp_v4_ctl_send_reset

Hello, While running syzkaller fuzzer I've got the following deadlock report: = [ INFO: inconsistent lock state ] 4.7.0-rc5+ #28 Not tainted - inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage. syz-executor/354

dccp: potential deadlock in dccp_v4_ctl_send_reset

Hello, While running syzkaller fuzzer I've got the following deadlock report: = [ INFO: inconsistent lock state ] 4.7.0-rc5+ #28 Not tainted - inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage. syz-executor/354

[PATCH] [linux-next] workqueue: Fix a typo in workqueue.txt

This patch fix a spelling typo in workqueue.txt Signed-off-by: Masanari Iida --- Documentation/workqueue.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/workqueue.txt b/Documentation/workqueue.txt index 5e0e05c5183e..c49e3178178d

[PATCH] [linux-next] workqueue: Fix a typo in workqueue.txt

This patch fix a spelling typo in workqueue.txt Signed-off-by: Masanari Iida --- Documentation/workqueue.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/workqueue.txt b/Documentation/workqueue.txt index 5e0e05c5183e..c49e3178178d 100644 ---

[PATCHv4 wl-drv-next 1/2] add basic register-field manipulation macros

Common approach to accessing register fields is to define structures or sets of macros containing mask and shift pair. Operations on the register are then performed as follows: field = (reg >> shift) & mask; reg &= ~(mask << shift); reg |= (field & mask) << shift; Defining shift and mask

[PATCHv4 wl-drv-next 1/2] add basic register-field manipulation macros

Common approach to accessing register fields is to define structures or sets of macros containing mask and shift pair. Operations on the register are then performed as follows: field = (reg >> shift) & mask; reg &= ~(mask << shift); reg |= (field & mask) << shift; Defining shift and mask

[PATCHv4 wl-drv-next 0/2] register-field manipulation macros

Hi! This set moves to a global header file macros which I find very useful and worth popularising. The basic problem is that since C bitfields are not very dependable accessing subfields of registers becomes slightly inconvenient. It is nice to have the necessary mask and shift operations

[PATCHv4 wl-drv-next 2/2] mt7601u: use linux/bitfield.h

Use the newly added linux/bitfield.h. Signed-off-by: Jakub Kicinski --- drivers/net/wireless/mediatek/mt7601u/dma.h | 2 - drivers/net/wireless/mediatek/mt7601u/mt7601u.h | 5 +- drivers/net/wireless/mediatek/mt7601u/util.h| 77 -

[PATCHv4 wl-drv-next 0/2] register-field manipulation macros

Hi! This set moves to a global header file macros which I find very useful and worth popularising. The basic problem is that since C bitfields are not very dependable accessing subfields of registers becomes slightly inconvenient. It is nice to have the necessary mask and shift operations

[PATCHv4 wl-drv-next 2/2] mt7601u: use linux/bitfield.h

Use the newly added linux/bitfield.h. Signed-off-by: Jakub Kicinski --- drivers/net/wireless/mediatek/mt7601u/dma.h | 2 - drivers/net/wireless/mediatek/mt7601u/mt7601u.h | 5 +- drivers/net/wireless/mediatek/mt7601u/util.h| 77 - 3 files changed, 4

[PATCH] kernel/watchdog: use nmi registers snapshot in hardlockup handler

NMI handler doesn't call set_irq_regs(), so get_irq_regs() returns NULL or stale snapshot from beginning of IRQ interrupted by NMI. Registers from argument are always here and points to interrupted instruction and state. Signed-off-by: Konstantin Khlebnikov Cc: Jiri

[PATCH] memory: samsung: exynos-srom: fix wrong count of registers

This patch fixes wrong count of array for srom registers from probe function. Signed-off-by: Seung-Woo Kim --- drivers/memory/samsung/exynos-srom.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/memory/samsung/exynos-srom.c

[PATCH] kernel/watchdog: use nmi registers snapshot in hardlockup handler

NMI handler doesn't call set_irq_regs(), so get_irq_regs() returns NULL or stale snapshot from beginning of IRQ interrupted by NMI. Registers from argument are always here and points to interrupted instruction and state. Signed-off-by: Konstantin Khlebnikov Cc: Jiri Kosina ---

[PATCH] memory: samsung: exynos-srom: fix wrong count of registers

This patch fixes wrong count of array for srom registers from probe function. Signed-off-by: Seung-Woo Kim --- drivers/memory/samsung/exynos-srom.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/memory/samsung/exynos-srom.c b/drivers/memory/samsung/exynos-srom.c

<    5   6   7   8   9   10   11   12   13   14   >