Re: [PATCH] CodingStyle: Expand IS_ENABLED() documentation

2016-09-27 Thread Bjorn Helgaas
On Tue, Sep 27, 2016 at 09:32:08PM +0200, Paul Bolle wrote: > On Tue, 2016-09-27 at 14:08 -0500, Bjorn Helgaas wrote: > > > --- a/Documentation/CodingStyle > > +++ b/Documentation/CodingStyle > > > +Because the compiler processes the block, you have to use an #ifdef instead > > +of IS_ENABLED()

Re: [PATCH] CodingStyle: Expand IS_ENABLED() documentation

2016-09-27 Thread Paul Bolle
On Tue, 2016-09-27 at 14:08 -0500, Bjorn Helgaas wrote: > --- a/Documentation/CodingStyle > +++ b/Documentation/CodingStyle > +Because the compiler processes the block, you have to use an #ifdef instead > +of IS_ENABLED() when code inside the block references symbols that will not > +exist if

[PATCH] CodingStyle: Expand IS_ENABLED() documentation

2016-09-27 Thread Bjorn Helgaas
CodingStyle recommends IS_ENABLED(CONFIG_FOO) over #ifdef. Add an example of the #ifdef, since it's not completely obvious that in many cases the #ifdef needs to test both CONFIG_FOO and CONFIG_FOO_MODULE. Signed-off-by: Bjorn Helgaas --- Documentation/CodingStyle | 15

[PATCH v2 -tip] locking/rtmutex: Reduce top-waiter blocking on a lock

2016-09-27 Thread Davidlohr Bueso
By applying well known spin-on-lock-owner techniques, we can avoid the blocking overhead during the process of when the task is trying to take the rtmutex. The idea is that as long as the owner is running, there is a fair chance it'll release the lock soon, and thus a task trying to acquire the

Re: [PATCH] dax : Fix documentation with respect to struct pages

2016-09-27 Thread Ross Zwisler
On Sun, Sep 25, 2016 at 07:18:37PM -0600, Stephen Bates wrote: > The documentation for dax is not up to date with respect to the struct > page support available in some of the device drivers that utilize > it. > > Signed-off-by: Stephen Bates Great, thanks for updating

Re: [PATCH v15 04/13] task_isolation: add initial support

2016-09-27 Thread Frederic Weisbecker
On Tue, Sep 27, 2016 at 04:39:26PM +0200, Peter Zijlstra wrote: > On Tue, Sep 27, 2016 at 04:22:20PM +0200, Frederic Weisbecker wrote: > > > The RCU context tracking doesn't take care of callbacks. It's only there > > to tell the RCU core whether the CPU runs code that may or may not run > > RCU

Re: Ping: [PATCH v15 00/13] support "task_isolation" mode

2016-09-27 Thread Frederic Weisbecker
On Mon, Sep 12, 2016 at 08:20:16PM -0400, Francis Giraldeau wrote: > > The args are valid, but the system has an unstable clock, therefore the > operation is not supported. In the user point of view, maybe ENOTSUPP > would be more appropriate? But then, we need to check the reason and >

Re: [PATCH v15 04/13] task_isolation: add initial support

2016-09-27 Thread Paul E. McKenney
On Tue, Sep 27, 2016 at 04:22:20PM +0200, Frederic Weisbecker wrote: > On Fri, Sep 02, 2016 at 10:28:00AM -0700, Andy Lutomirski wrote: > > > > Unless I'm missing something (which is reasonably likely), couldn't > > the isolation code just force or require rcu_nocbs on the isolated > > CPUs to

Re: [PATCH v15 04/13] task_isolation: add initial support

2016-09-27 Thread Peter Zijlstra
On Tue, Sep 27, 2016 at 04:22:20PM +0200, Frederic Weisbecker wrote: > The RCU context tracking doesn't take care of callbacks. It's only there > to tell the RCU core whether the CPU runs code that may or may not run > RCU read side critical sections. This is assumed by "kernel may use RCU, >

Re: Ping: [PATCH v15 00/13] support "task_isolation" mode

2016-09-27 Thread Frederic Weisbecker
On Mon, Aug 29, 2016 at 12:27:06PM -0400, Chris Metcalf wrote: > On 8/16/2016 5:19 PM, Chris Metcalf wrote: > >Here is a respin of the task-isolation patch set. > > > >Again, I have been getting email asking me when and where this patch > >will be upstreamed so folks can start using it. I had

Re: [PATCH v15 04/13] task_isolation: add initial support

2016-09-27 Thread Frederic Weisbecker
On Fri, Sep 02, 2016 at 10:28:00AM -0700, Andy Lutomirski wrote: > > Unless I'm missing something (which is reasonably likely), couldn't > the isolation code just force or require rcu_nocbs on the isolated > CPUs to avoid this problem entirely. rcu_nocb is already implied by nohz_full. Which

Re: [PATCH v7 5/8] thunderbolt: Networking state machine

2016-09-27 Thread Greg KH
On Tue, Sep 27, 2016 at 04:43:38PM +0300, Amir Levy wrote: > This patch builds the peer to peer communication path. > Communication is established by a negotiation process whereby messages are > sent back and forth between the peers until a connection is established. > This includes the

Re: [PATCH v7 4/8] thunderbolt: Communication with the ICM (firmware)

2016-09-27 Thread Greg KH
On Tue, Sep 27, 2016 at 04:43:37PM +0300, Amir Levy wrote: > This patch provides the communication protocol between the > Intel Connection Manager(ICM) firmware that is operational in the > Thunderbolt controller in non-Apple hardware. > The ICM firmware-based controller is used for establishing

Re: [PATCH v7 3/8] thunderbolt: Kconfig for Thunderbolt Networking

2016-09-27 Thread Greg KH
On Tue, Sep 27, 2016 at 04:43:36PM +0300, Amir Levy wrote: > Update to the Kconfig Thunderbolt description to add > Thunderbolt networking as an option. > The menu item "Thunderbolt support" now offers: > "Apple Hardware Support" (existing) > and/or > "Thunderbolt Networking" (new) > >

[PATCH v7 3/8] thunderbolt: Kconfig for Thunderbolt Networking

2016-09-27 Thread Amir Levy
Update to the Kconfig Thunderbolt description to add Thunderbolt networking as an option. The menu item "Thunderbolt support" now offers: "Apple Hardware Support" (existing) and/or "Thunderbolt Networking" (new) You can choose the driver for your platform or build both drivers - each

[PATCH v7 2/8] thunderbolt: Updating the register definitions

2016-09-27 Thread Amir Levy
Adding more Thunderbolt(TM) register definitions and some helper macros. Signed-off-by: Amir Levy --- drivers/thunderbolt/nhi_regs.h | 109 + 1 file changed, 109 insertions(+) diff --git a/drivers/thunderbolt/nhi_regs.h

[PATCH v7 4/8] thunderbolt: Communication with the ICM (firmware)

2016-09-27 Thread Amir Levy
This patch provides the communication protocol between the Intel Connection Manager(ICM) firmware that is operational in the Thunderbolt controller in non-Apple hardware. The ICM firmware-based controller is used for establishing and maintaining the Thunderbolt Networking connection - we need to

[PATCH v7 1/8] thunderbolt: Macro rename

2016-09-27 Thread Amir Levy
This first patch updates the NHI Thunderbolt controller registers file to reflect that it is not only for Cactus Ridge. No functional change intended. Signed-off-by: Amir Levy Signed-off-by: Andreas Noever --- drivers/thunderbolt/nhi_regs.h |

[PATCH v7 8/8] thunderbolt: Adding maintainer entry

2016-09-27 Thread Amir Levy
Add Amir Levy as maintainer for Thunderbolt(TM) ICM driver Signed-off-by: Amir Levy --- MAINTAINERS | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 01bff8e..a4a4614 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@

[PATCH v7 6/8] thunderbolt: Networking transmit and receive

2016-09-27 Thread Amir Levy
This patch provides the handling interface for sending and receiving network packets between the hosts over the full communication route (using the communication path established in the previous patch). The Thunderbolt Network driver interfaces the Linux network stack and the hardware controller

[PATCH v7 5/8] thunderbolt: Networking state machine

2016-09-27 Thread Amir Levy
This patch builds the peer to peer communication path. Communication is established by a negotiation process whereby messages are sent back and forth between the peers until a connection is established. This includes the Thunderbolt Network driver communication with the second peer via Intel

[PATCH v7 7/8] thunderbolt: Networking doc

2016-09-27 Thread Amir Levy
Adding Thunderbolt(TM) networking documentation. Signed-off-by: Amir Levy --- Documentation/00-INDEX | 2 + Documentation/thunderbolt/networking.txt | 132 +++ 2 files changed, 134 insertions(+) create mode 100644

[PATCH v2 0/1] mm/mempolicy.c: forbid static or relative flags for local NUMA mode

2016-09-27 Thread Piotr Kwapulinski
The MPOL_F_STATIC_NODES and MPOL_F_RELATIVE_NODES flags are irrelevant when setting them for MPOL_LOCAL NUMA memory policy via set_mempolicy or mbind. Return the "invalid argument" from set_mempolicy and mbind whenever any of these flags is passed along with MPOL_LOCAL. It is consistent with

[PATCH 1/1] mm/mempolicy.c: add MPOL_LOCAL NUMA memory policy documentation

2016-09-27 Thread Piotr Kwapulinski
The MPOL_LOCAL mode has been implemented by Peter Zijlstra (commit: 479e2802d09f1e18a97262c4c6f8f17ae5884bd8). Add the documentation for this mode. Signed-off-by: Piotr Kwapulinski --- Documentation/vm/numa_memory_policy.txt | 8

[PATCH 0/1] man/set_mempolicy.2,mbind.2: add MPOL_LOCAL NUMA memory policy documentation

2016-09-27 Thread Piotr Kwapulinski
The MPOL_LOCAL mode has been implemented by Peter Zijlstra (commit: 479e2802d09f1e18a97262c4c6f8f17ae5884bd8). Add the documentation for this mode. Signed-off-by: Piotr Kwapulinski --- man2/mbind.2 | 16

Re: [RFC PATCH 08/11] pci: controller: dra7xx: Add EP mode support

2016-09-27 Thread Kishon Vijay Abraham I
Hi, On Friday 23 September 2016 08:22 PM, Rob Herring wrote: > On Wed, Sep 14, 2016 at 10:42:04AM +0530, Kishon Vijay Abraham I wrote: >> The PCIe controller integrated in dra7xx SoCs is capable of operating >> in endpoint mode. Add support for dra7xx SoCs to operate in endpoint >> mode. >> >>

Re: [RFC PATCH 07/11] pci: controller: designware: Add EP mode support

2016-09-27 Thread Kishon Vijay Abraham I
Hi, On Friday 23 September 2016 08:11 PM, Rob Herring wrote: > On Wed, Sep 14, 2016 at 10:42:03AM +0530, Kishon Vijay Abraham I wrote: >> Add endpoint mode support to designware driver. This uses the >> EP Core layer introduced recently to add endpoint mode support. >> *Any* function driver can