Re: [PATCH v5 net-next 00/12] bpf: rewrite value tracking in verifier

From: Daniel Borkmann Date: Tue, 08 Aug 2017 02:46:16 +0200 > On 08/07/2017 04:21 PM, Edward Cree wrote: >> This series simplifies alignment tracking, generalises bounds tracking >> and >> fixes some bounds-tracking bugs in the BPF verifier. Pointer >> arithmetic on >>

Re: [PATCH v5 net-next 00/12] bpf: rewrite value tracking in verifier

From: Daniel Borkmann Date: Tue, 08 Aug 2017 02:46:16 +0200 > On 08/07/2017 04:21 PM, Edward Cree wrote: >> This series simplifies alignment tracking, generalises bounds tracking >> and >> fixes some bounds-tracking bugs in the BPF verifier. Pointer >> arithmetic on >> packet pointers,

Re: Possible null pointer dereference in rcar-dmac.ko

Hi Anton # add Laurent > While searching for races in the Linux kernel I've come across > "drivers/dma/sh/rcar-dmac.ko" module. Here is a question that I came > up with while analyzing results. Lines are given using the info from > Linux v4.12. > > Consider the following case: > > Thread 1:

Re: Possible null pointer dereference in rcar-dmac.ko

Hi Anton # add Laurent > While searching for races in the Linux kernel I've come across > "drivers/dma/sh/rcar-dmac.ko" module. Here is a question that I came > up with while analyzing results. Lines are given using the info from > Linux v4.12. > > Consider the following case: > > Thread 1:

Re: [PATCH 0/6] In-kernel QMI handling

On Tue, 2017-08-08 at 15:42 -0700, Bjorn Andersson wrote: > On Tue 08 Aug 04:02 PDT 2017, Bj?rn Mork wrote: > > > Bjorn Andersson writes: > > > > > This series starts by moving the common definitions of the QMUX > > > protocol to the > > > uapi header, as they are

Re: [PATCH 0/6] In-kernel QMI handling

On Tue, 2017-08-08 at 15:42 -0700, Bjorn Andersson wrote: > On Tue 08 Aug 04:02 PDT 2017, Bj?rn Mork wrote: > > > Bjorn Andersson writes: > > > > > This series starts by moving the common definitions of the QMUX > > > protocol to the > > > uapi header, as they are shared with clients - both in

Re: [PATCH 1/3] autofs - fix AT_NO_AUTOMOUNT not being honored

On 08/08/17 21:11, Colin Walters wrote: > On Tue, Aug 8, 2017, at 12:26 AM, Ian Kent wrote: > >> --- a/include/linux/fs.h >> +++ b/include/linux/fs.h >> @@ -3022,8 +3022,7 @@ static inline int vfs_lstat(const char __user *name, >> struct kstat *stat) >> static inline int vfs_fstatat(int dfd,

Re: [PATCH 1/3] autofs - fix AT_NO_AUTOMOUNT not being honored

On 08/08/17 21:11, Colin Walters wrote: > On Tue, Aug 8, 2017, at 12:26 AM, Ian Kent wrote: > >> --- a/include/linux/fs.h >> +++ b/include/linux/fs.h >> @@ -3022,8 +3022,7 @@ static inline int vfs_lstat(const char __user *name, >> struct kstat *stat) >> static inline int vfs_fstatat(int dfd,

[PATCH v3] perf/core: Avoid context switch overheads

From: "leilei.lin" A performance issue caused by less strickly check in task sched when these tasks were once attached by per-task perf_event. A task will alloc task->perf_event_ctxp[ctxn] when it was called by perf_event_open, and task->perf_event_ctxp[ctxn] would not ever

[PATCH v3] perf/core: Avoid context switch overheads

From: "leilei.lin" A performance issue caused by less strickly check in task sched when these tasks were once attached by per-task perf_event. A task will alloc task->perf_event_ctxp[ctxn] when it was called by perf_event_open, and task->perf_event_ctxp[ctxn] would not ever be freed to NULL.

Re: [PATCH 4/4] scripts/move_maintainer_sections.bash

On Tue, 2017-08-08 at 11:33 -0700, Linus Torvalds wrote: > On Mon, Aug 7, 2017 at 10:04 AM, Joe Perches wrote: > > On Sat, 2017-08-05 at 18:45 -0700, Joe Perches wrote: > > > Move MAINTAINERS into a separate directory and reorder it. > > > Separate various blocks of MAINTAINER

Re: [PATCH 4/4] scripts/move_maintainer_sections.bash

On Tue, 2017-08-08 at 11:33 -0700, Linus Torvalds wrote: > On Mon, Aug 7, 2017 at 10:04 AM, Joe Perches wrote: > > On Sat, 2017-08-05 at 18:45 -0700, Joe Perches wrote: > > > Move MAINTAINERS into a separate directory and reorder it. > > > Separate various blocks of MAINTAINER sections into

[PATCH v3] perf/core: Avoid context switch overheads

From: "leilei.lin" A performance issue caused by less strickly check in task sched when these tasks were once attached by per-task perf_event. A task will alloc task->perf_event_ctxp[ctxn] when it was called by perf_event_open, and task->perf_event_ctxp[ctxn] would

[PATCH v3] perf/core: Avoid context switch overheads

From: "leilei.lin" A performance issue caused by less strickly check in task sched when these tasks were once attached by per-task perf_event. A task will alloc task->perf_event_ctxp[ctxn] when it was called by perf_event_open, and task->perf_event_ctxp[ctxn] would not ever be freed to NULL.

Re: [PATCH v2] perf/core: Avoid context switch overheads

2017-08-08 18:37 GMT+08:00 Peter Zijlstra : > On Tue, Aug 08, 2017 at 06:00:45PM +0800, 石祤 wrote: > >> diff --git a/kernel/events/core.c b/kernel/events/core.c >> index 426c2ff..3d86695 100644 >> --- a/kernel/events/core.c >> +++ b/kernel/events/core.c >> @@ -3180,6 +3180,13

Re: [PATCH v2] perf/core: Avoid context switch overheads

2017-08-08 18:37 GMT+08:00 Peter Zijlstra : > On Tue, Aug 08, 2017 at 06:00:45PM +0800, 石祤 wrote: > >> diff --git a/kernel/events/core.c b/kernel/events/core.c >> index 426c2ff..3d86695 100644 >> --- a/kernel/events/core.c >> +++ b/kernel/events/core.c >> @@ -3180,6 +3180,13 @@ static void

Re: [RFC PATCH] exec: Avoid recursive modprobe for binary format handlers

On Wed, Aug 02, 2017 at 02:12:00AM +0200, Luis R. Rodriguez wrote: > On Fri, Jul 21, 2017 at 03:05:20PM +0100, Matt Redfearn wrote: > > diff --git a/fs/exec.c b/fs/exec.c > > index 62175cbcc801..004bb50a01fe 100644 > > --- a/fs/exec.c > > +++ b/fs/exec.c > > @@ -1644,6 +1644,9 @@ int

Re: [RFC PATCH] exec: Avoid recursive modprobe for binary format handlers

On Wed, Aug 02, 2017 at 02:12:00AM +0200, Luis R. Rodriguez wrote: > On Fri, Jul 21, 2017 at 03:05:20PM +0100, Matt Redfearn wrote: > > diff --git a/fs/exec.c b/fs/exec.c > > index 62175cbcc801..004bb50a01fe 100644 > > --- a/fs/exec.c > > +++ b/fs/exec.c > > @@ -1644,6 +1644,9 @@ int

[PATCH RESEND] Input: xpad - fix PowerA init quirk for some gamepad models

The PowerA gamepad initialization quirk worked with the PowerA wired gamepad I had around (0x24c6:0x543a), but a user reported [0] that it didn't work for him, even though our gamepads shared the same vendor and product IDs. When I initially implemented the PowerA quirk, I wanted to avoid

[PATCH RESEND] Input: xpad - fix PowerA init quirk for some gamepad models

The PowerA gamepad initialization quirk worked with the PowerA wired gamepad I had around (0x24c6:0x543a), but a user reported [0] that it didn't work for him, even though our gamepads shared the same vendor and product IDs. When I initially implemented the PowerA quirk, I wanted to avoid

Re: [PATCH] powerpc: xive: ensure active irqd when setting affinity

Michael Ellerman [m...@ellerman.id.au] wrote: > Sukadev Bhattiprolu writes: > > > From fd0abf5c61b6041fdb75296e8580b86dc91d08d6 Mon Sep 17 00:00:00 2001 > > From: Benjamin Herrenschmidt > > Date: Tue, 1 Aug 2017 20:54:41 -0500 > > Subject:

Re: [PATCH] powerpc: xive: ensure active irqd when setting affinity

Michael Ellerman [m...@ellerman.id.au] wrote: > Sukadev Bhattiprolu writes: > > > From fd0abf5c61b6041fdb75296e8580b86dc91d08d6 Mon Sep 17 00:00:00 2001 > > From: Benjamin Herrenschmidt > > Date: Tue, 1 Aug 2017 20:54:41 -0500 > > Subject: [PATCH] powerpc: xive: ensure active irqd when setting

Re: linux-next: Signed-off-by missing for commits in the scsi tree

Hi James, On Tue, 08 Aug 2017 16:41:36 -0700 James Bottomley wrote: > >  The rule, I believe, is that only the person who transforms the email > to a git tree should be the last signoff in the commit log, even if > they're a tree pulling into another one

Re: linux-next: Signed-off-by missing for commits in the scsi tree

Hi James, On Tue, 08 Aug 2017 16:41:36 -0700 James Bottomley wrote: > >  The rule, I believe, is that only the person who transforms the email > to a git tree should be the last signoff in the commit log, even if > they're a tree pulling into another one and thereafter the signoffs go > in the

[PATCH libdrm] drm: Remove create_handle() drm_framebuffer "virtual".

Because all drivers currently use gem objects for framebuffer planes, the virtual create_handle() is not required. This change adds a struct drm_gem_object *gems[4] field to drm_framebuffer and removes create_handle() function pointer from drm_framebuffer_funcs. The corresponding

[PATCH libdrm] drm: Remove create_handle() drm_framebuffer "virtual".

Because all drivers currently use gem objects for framebuffer planes, the virtual create_handle() is not required. This change adds a struct drm_gem_object *gems[4] field to drm_framebuffer and removes create_handle() function pointer from drm_framebuffer_funcs. The corresponding

Re: linux-next: Signed-off-by missing for commits in the scsi tree

On Wed, 2017-08-09 at 09:27 +1000, Stephen Rothwell wrote: > Hi James, > > The commit series > >   94b76dcac422 ("scsi: qla2xxx: Fix system crash while triggering FW > dump") > to >   b96b8da34c40 ("scsi: aacraid: Fix out of bounds in > aac_get_name_resp") > > is missing Signed-off-bys from its

Re: linux-next: Signed-off-by missing for commits in the scsi tree

On Wed, 2017-08-09 at 09:27 +1000, Stephen Rothwell wrote: > Hi James, > > The commit series > >   94b76dcac422 ("scsi: qla2xxx: Fix system crash while triggering FW > dump") > to >   b96b8da34c40 ("scsi: aacraid: Fix out of bounds in > aac_get_name_resp") > > is missing Signed-off-bys from its

Re: [PATCH V8 1/2] PCI: handle CRS returned by device after FLR

On 8/8/2017 5:19 PM, Bjorn Helgaas wrote: > On Sun, Aug 06, 2017 at 10:09:51PM -0400, Sinan Kaya wrote: > > We should include some high-level description of the problem we're > trying to solve here. > > I *think* the problem is that we do something like this: > > - perform an FLR > - sleep

Re: [PATCH V8 1/2] PCI: handle CRS returned by device after FLR

On 8/8/2017 5:19 PM, Bjorn Helgaas wrote: > On Sun, Aug 06, 2017 at 10:09:51PM -0400, Sinan Kaya wrote: > > We should include some high-level description of the problem we're > trying to solve here. > > I *think* the problem is that we do something like this: > > - perform an FLR > - sleep

Re: [PATCH] sched/fair: Make PELT signal more accurate

Hi Peter, On Mon, Aug 7, 2017 at 6:40 AM, Peter Zijlstra wrote: > On Fri, Aug 04, 2017 at 08:40:23AM -0700, Joel Fernandes wrote: >> The PELT signal (sa->load_avg and sa->util_avg) are not updated if the >> amount accumulated during a single update doesn't cross a period >>

Re: [PATCH] sched/fair: Make PELT signal more accurate

Hi Peter, On Mon, Aug 7, 2017 at 6:40 AM, Peter Zijlstra wrote: > On Fri, Aug 04, 2017 at 08:40:23AM -0700, Joel Fernandes wrote: >> The PELT signal (sa->load_avg and sa->util_avg) are not updated if the >> amount accumulated during a single update doesn't cross a period >> boundary. > >> This

Re: [PATCH 2/2] mm, oom: fix potential data corruption when oom_reaper races with writer

Andrea Arcangeli wrote: > Overall OOM killing to me was reliable also before the oom reaper was > introduced. I don't think so. We spent a lot of time in order to remove possible locations which can lead to failing to invoke the OOM killer when out_of_memory() is called. > > I just did a

Re: [PATCH 2/2] mm, oom: fix potential data corruption when oom_reaper races with writer

Andrea Arcangeli wrote: > Overall OOM killing to me was reliable also before the oom reaper was > introduced. I don't think so. We spent a lot of time in order to remove possible locations which can lead to failing to invoke the OOM killer when out_of_memory() is called. > > I just did a

[PATCH] kmod: test_kmod: Correctly lock reg_dev_mutex

It appears that, in the preamble of register_test_dev_kmod(), mutex_lock() has been confused with mutex_unlock(). Previously, register_test_dev_kmod() never called mutex_lock() but instead, it called mutex_unlock() twice. Signed-off-by: Daniel Mentz Cc: Luis R. Rodriguez

[PATCH] kmod: test_kmod: Correctly lock reg_dev_mutex

It appears that, in the preamble of register_test_dev_kmod(), mutex_lock() has been confused with mutex_unlock(). Previously, register_test_dev_kmod() never called mutex_lock() but instead, it called mutex_unlock() twice. Signed-off-by: Daniel Mentz Cc: Luis R. Rodriguez Cc: Greg Kroah-Hartman

Re: [PATCH] netfilter: nf_nat_h323: fix logical-not-parentheses warning

bumping for review On Mon, Jul 31, 2017 at 11:39 AM, Nick Desaulniers wrote: > Clang produces the following warning: > > net/ipv4/netfilter/nf_nat_h323.c:553:6: error: > logical not is only applied to the left hand side of this comparison >

Re: [PATCH] netfilter: nf_nat_h323: fix logical-not-parentheses warning

bumping for review On Mon, Jul 31, 2017 at 11:39 AM, Nick Desaulniers wrote: > Clang produces the following warning: > > net/ipv4/netfilter/nf_nat_h323.c:553:6: error: > logical not is only applied to the left hand side of this comparison > [-Werror,-Wlogical-not-parentheses] > if

linux-next: Signed-off-by missing for commits in the scsi tree

Hi James, The commit series 94b76dcac422 ("scsi: qla2xxx: Fix system crash while triggering FW dump") to b96b8da34c40 ("scsi: aacraid: Fix out of bounds in aac_get_name_resp") is missing Signed-off-bys from its committer. It looks like you have rebased a series from Martin ... -- Cheers,

linux-next: Signed-off-by missing for commits in the scsi tree

Hi James, The commit series 94b76dcac422 ("scsi: qla2xxx: Fix system crash while triggering FW dump") to b96b8da34c40 ("scsi: aacraid: Fix out of bounds in aac_get_name_resp") is missing Signed-off-bys from its committer. It looks like you have rebased a series from Martin ... -- Cheers,

Re: [PATCH v06 35/36] uapi linux/tls.h: don't include in user space

On Sun, Aug 06, 2017 at 06:44:26PM +0200, Mikko Rapeli wrote: > It is not needed and not part of uapi headers, but causes > user space compilation error: > > fatal error: net/tcp.h: No such file or directory > #include > ^ > > Signed-off-by: Mikko Rapeli

Re: [PATCH v06 35/36] uapi linux/tls.h: don't include in user space

On Sun, Aug 06, 2017 at 06:44:26PM +0200, Mikko Rapeli wrote: > It is not needed and not part of uapi headers, but causes > user space compilation error: > > fatal error: net/tcp.h: No such file or directory > #include > ^ > > Signed-off-by: Mikko Rapeli > Cc: Dave Watson

Re: [v4 4/4] mm, oom, docs: describe the cgroup-aware OOM killer

On Wed, 26 Jul 2017, Roman Gushchin wrote: > +Cgroup-aware OOM Killer > +~~~ > + > +Cgroup v2 memory controller implements a cgroup-aware OOM killer. > +It means that it treats memory cgroups as first class OOM entities. > + > +Under OOM conditions the memory controller tries

Re: [v4 4/4] mm, oom, docs: describe the cgroup-aware OOM killer

On Wed, 26 Jul 2017, Roman Gushchin wrote: > +Cgroup-aware OOM Killer > +~~~ > + > +Cgroup v2 memory controller implements a cgroup-aware OOM killer. > +It means that it treats memory cgroups as first class OOM entities. > + > +Under OOM conditions the memory controller tries

Re: [PATCH v9 1/4] PCI: Add new PCIe Fabric End Node flag, PCI_DEV_FLAGS_NO_RELAXED_ORDERING

On Sat, Aug 05, 2017 at 03:15:10PM +0800, Ding Tianhong wrote: > From: Casey Leedom > > The patch adds a new flag PCI_DEV_FLAGS_NO_RELAXED_ORDERING to indicate that > Relaxed Ordering (RO) attribute should not be used for Transaction Layer > Packets (TLP) targetted towards

Re: [PATCH v9 1/4] PCI: Add new PCIe Fabric End Node flag, PCI_DEV_FLAGS_NO_RELAXED_ORDERING

On Sat, Aug 05, 2017 at 03:15:10PM +0800, Ding Tianhong wrote: > From: Casey Leedom > > The patch adds a new flag PCI_DEV_FLAGS_NO_RELAXED_ORDERING to indicate that > Relaxed Ordering (RO) attribute should not be used for Transaction Layer > Packets (TLP) targetted towards these affected root

Re: [PATCH net-next v2] wan: dscc4: add checks for dma mapping errors

Alexey Khoroshilov : [...] > diff --git a/drivers/net/wan/dscc4.c b/drivers/net/wan/dscc4.c > index 799830f..6a9ffac 100644 > --- a/drivers/net/wan/dscc4.c > +++ b/drivers/net/wan/dscc4.c > @@ -518,23 +518,31 @@ static void dscc4_release_ring(struct dscc4_dev_priv >

Re: [PATCH net-next v2] wan: dscc4: add checks for dma mapping errors

Alexey Khoroshilov : [...] > diff --git a/drivers/net/wan/dscc4.c b/drivers/net/wan/dscc4.c > index 799830f..6a9ffac 100644 > --- a/drivers/net/wan/dscc4.c > +++ b/drivers/net/wan/dscc4.c > @@ -518,23 +518,31 @@ static void dscc4_release_ring(struct dscc4_dev_priv > *dpriv) > static inline int

Re: [PATCH 4/7] signal/mips: Document a conflict with SI_USER with SIGFPE

On Tue, 8 Aug 2017, Eric W. Biederman wrote: > > This is an "impossible" state to reach unless your hardware is on fire. > > One or more of the FCSR Cause bits will have been set (in `fcr31') or the > > FPE exception would not have happened. > > > > Of course there could be a simulator bug,

Re: [PATCH 4/7] signal/mips: Document a conflict with SI_USER with SIGFPE

On Tue, 8 Aug 2017, Eric W. Biederman wrote: > > This is an "impossible" state to reach unless your hardware is on fire. > > One or more of the FCSR Cause bits will have been set (in `fcr31') or the > > FPE exception would not have happened. > > > > Of course there could be a simulator bug,

Re: [PATCH v06 22/36] uapi linux/reiserfs_xattr.h: use __kernel_size_t instead of size_t

On Sun, Aug 06, 2017 at 06:44:13PM +0200, Mikko Rapeli wrote: > Fixes userspace compilation error: > > error: unknown type name ‘size_t’ > size_t length; > > Signed-off-by: Mikko Rapeli > Cc: reiserfs-de...@vger.kernel.org > --- > include/uapi/linux/reiserfs_xattr.h | 2

Re: [PATCH v06 22/36] uapi linux/reiserfs_xattr.h: use __kernel_size_t instead of size_t

On Sun, Aug 06, 2017 at 06:44:13PM +0200, Mikko Rapeli wrote: > Fixes userspace compilation error: > > error: unknown type name ‘size_t’ > size_t length; > > Signed-off-by: Mikko Rapeli > Cc: reiserfs-de...@vger.kernel.org > --- > include/uapi/linux/reiserfs_xattr.h | 2 +- > 1 file changed,

Re: [RFC] Tagging of vmalloc pages for supporting the pmalloc allocator

On Tue, Aug 08, 2017 at 03:59:36PM +0300, Igor Stoppa wrote: > On 07/08/17 22:12, Jerome Glisse wrote: > > On Mon, Aug 07, 2017 at 05:13:00PM +0300, Igor Stoppa wrote: > > [...] > > >> I have an updated version of the old proposal: > >> > >> * put a magic number in the private field, during

Re: [RFC] Tagging of vmalloc pages for supporting the pmalloc allocator

On Tue, Aug 08, 2017 at 03:59:36PM +0300, Igor Stoppa wrote: > On 07/08/17 22:12, Jerome Glisse wrote: > > On Mon, Aug 07, 2017 at 05:13:00PM +0300, Igor Stoppa wrote: > > [...] > > >> I have an updated version of the old proposal: > >> > >> * put a magic number in the private field, during

Re: [PATCH v06 21/36] uapi linux/kexec.h: use __kernel_size_t instead of size_t

On Sun, Aug 06, 2017 at 06:44:12PM +0200, Mikko Rapeli wrote: > Fixes userspace compilation error: > > error: unknown type name ‘size_t’ > size_t bufsz; > > Signed-off-by: Mikko Rapeli > Cc: ke...@lists.infradead.org > Cc: Eric Biederman > --- >

Re: [PATCH v06 21/36] uapi linux/kexec.h: use __kernel_size_t instead of size_t

On Sun, Aug 06, 2017 at 06:44:12PM +0200, Mikko Rapeli wrote: > Fixes userspace compilation error: > > error: unknown type name ‘size_t’ > size_t bufsz; > > Signed-off-by: Mikko Rapeli > Cc: ke...@lists.infradead.org > Cc: Eric Biederman > --- > include/uapi/linux/kexec.h | 4 ++-- > 1 file

Re: [v4 3/4] mm, oom: introduce oom_priority for memory cgroups

On Wed, 26 Jul 2017, Roman Gushchin wrote: > Introduce a per-memory-cgroup oom_priority setting: an integer number > within the [-1, 1] range, which defines the order in which > the OOM killer selects victim memory cgroups. > > OOM killer prefers memory cgroups with larger priority if

Re: [v4 3/4] mm, oom: introduce oom_priority for memory cgroups

On Wed, 26 Jul 2017, Roman Gushchin wrote: > Introduce a per-memory-cgroup oom_priority setting: an integer number > within the [-1, 1] range, which defines the order in which > the OOM killer selects victim memory cgroups. > > OOM killer prefers memory cgroups with larger priority if

Re: [PATCH v06 30/36] uapi rdma/rdma_user_rxe.h: include in.h and in6.h

On Sun, Aug 06, 2017 at 06:44:21PM +0200, Mikko Rapeli wrote: > Fixes these userspace compilation errors when rdma_user_rxe.h is compiled > alone: > > rdma/rdma_user_rxe.h:59:20: error: field ???_sockaddr??? has incomplete type >struct sockaddr _sockaddr; > ^ >

Re: [PATCH v06 30/36] uapi rdma/rdma_user_rxe.h: include in.h and in6.h

On Sun, Aug 06, 2017 at 06:44:21PM +0200, Mikko Rapeli wrote: > Fixes these userspace compilation errors when rdma_user_rxe.h is compiled > alone: > > rdma/rdma_user_rxe.h:59:20: error: field ???_sockaddr??? has incomplete type >struct sockaddr _sockaddr; > ^ >

Re: [PATCH v06 19/36] uapi linux/omapfb.h: use __kernel_size_t instead of size_t

On Sun, Aug 06, 2017 at 06:44:10PM +0200, Mikko Rapeli wrote: > Fixes userspace compilation error: > > error: unknown type name ‘size_t’ > > Signed-off-by: Mikko Rapeli > Cc: linux-o...@vger.kernel.org > Cc: Tomi Valkeinen > Cc: Aaro Koskinen

Re: [PATCH v06 19/36] uapi linux/omapfb.h: use __kernel_size_t instead of size_t

On Sun, Aug 06, 2017 at 06:44:10PM +0200, Mikko Rapeli wrote: > Fixes userspace compilation error: > > error: unknown type name ‘size_t’ > > Signed-off-by: Mikko Rapeli > Cc: linux-o...@vger.kernel.org > Cc: Tomi Valkeinen > Cc: Aaro Koskinen > --- > include/uapi/linux/omapfb.h | 2 +- > 1

[PATCH v6 04/17] powerpc/vas: Define helpers to access MMIO regions

Define some helper functions to access the MMIO regions. We use these in follow-on patches to read/write VAS hardware registers. They are also used to later issue 'paste' instructions to submit requests to the NX hardware engines. Signed-off-by: Sukadev Bhattiprolu

[PATCH v6 04/17] powerpc/vas: Define helpers to access MMIO regions

Define some helper functions to access the MMIO regions. We use these in follow-on patches to read/write VAS hardware registers. They are also used to later issue 'paste' instructions to submit requests to the NX hardware engines. Signed-off-by: Sukadev Bhattiprolu --- Changelog [v6]: -

[PATCH v6 02/17] powerpc/vas: Move GET_FIELD/SET_FIELD to vas.h

Move the GET_FIELD and SET_FIELD macros to vas.h as VAS and other users of VAS, including NX-842 can use those macros. There is a lot of related code between the VAS/NX kernel drivers and skiboot. For consistency switch the order of parameters in SET_FIELD to match the order in skiboot.

[PATCH v6 02/17] powerpc/vas: Move GET_FIELD/SET_FIELD to vas.h

Move the GET_FIELD and SET_FIELD macros to vas.h as VAS and other users of VAS, including NX-842 can use those macros. There is a lot of related code between the VAS/NX kernel drivers and skiboot. For consistency switch the order of parameters in SET_FIELD to match the order in skiboot.

[PATCH v6 01/17] powerpc/vas: Define macros, register fields and structures

Define macros for the VAS hardware registers and bit-fields as well as couple of data structures needed by the VAS driver. Signed-off-by: Sukadev Bhattiprolu --- Changelog[v6] - Add some fields for FTW windows Changelog[v4] - [Michael Neuling] Move

Re: [PATCH] sched/fair: Make PELT signal more accurate

Hi Vincent, On Mon, Aug 7, 2017 at 6:24 AM, Vincent Guittot wrote: > Hi Joel, > > On 4 August 2017 at 17:40, Joel Fernandes wrote: >> The PELT signal (sa->load_avg and sa->util_avg) are not updated if the amount >> accumulated during a single

Re: [PATCH] sched/fair: Make PELT signal more accurate

Hi Vincent, On Mon, Aug 7, 2017 at 6:24 AM, Vincent Guittot wrote: > Hi Joel, > > On 4 August 2017 at 17:40, Joel Fernandes wrote: >> The PELT signal (sa->load_avg and sa->util_avg) are not updated if the amount >> accumulated during a single update doesn't cross a period boundary. This is >>

[PATCH v6 01/17] powerpc/vas: Define macros, register fields and structures

Define macros for the VAS hardware registers and bit-fields as well as couple of data structures needed by the VAS driver. Signed-off-by: Sukadev Bhattiprolu --- Changelog[v6] - Add some fields for FTW windows Changelog[v4] - [Michael Neuling] Move VAS code to arch/powerpc;

[PATCH v6 05/17] powerpc/vas: Define helpers to init window context

Define helpers to initialize window context registers of the VAS hardware. These will be used in follow-on patches when opening/closing VAS windows. Signed-off-by: Sukadev Bhattiprolu --- Changelog[v6] - Add support for FTW windows and drop the fault window id

[PATCH v6 05/17] powerpc/vas: Define helpers to init window context

Define helpers to initialize window context registers of the VAS hardware. These will be used in follow-on patches when opening/closing VAS windows. Signed-off-by: Sukadev Bhattiprolu --- Changelog[v6] - Add support for FTW windows and drop the fault window id code since it is

[PATCH v6 07/17] powerpc/vas: Define vas_win_paste_addr()

Define an interface that the NX drivers can use to find the physical paste address of a send window. This interface is expected to be used with the mmap() operation of the NX driver's device. i.e the user space process can use driver's mmap() operation to map the send window's paste address into

[PATCH v6 07/17] powerpc/vas: Define vas_win_paste_addr()

Define an interface that the NX drivers can use to find the physical paste address of a send window. This interface is expected to be used with the mmap() operation of the NX driver's device. i.e the user space process can use driver's mmap() operation to map the send window's paste address into

[PATCH v6 10/17] powerpc/vas: Define vas_rx_win_open() interface

Define the vas_rx_win_open() interface. This interface is intended to be used by the Nest Accelerator (NX) driver(s) to setup receive windows for one or more NX engines (which implement compression/encryption algorithms in the hardware). Follow-on patches will provide an interface to close the

[PATCH v6 06/17] powerpc/vas: Define helpers to alloc/free windows

Define helpers to allocate/free VAS window objects. These will be used in follow-on patches when opening/closing windows. Signed-off-by: Sukadev Bhattiprolu --- arch/powerpc/platforms/powernv/vas-window.c | 70 + 1 file changed, 70

[PATCH v6 03/17] powerpc/vas: Define vas_init() and vas_exit()

Implement vas_init() and vas_exit() functions for a new VAS module. This VAS module is essentially a library for other device drivers and kernel users of the NX coprocessors like NX-842 and NX-GZIP. In the future this will be extended to add support for user space to access the NX coprocessors.

[PATCH v6 10/17] powerpc/vas: Define vas_rx_win_open() interface

Define the vas_rx_win_open() interface. This interface is intended to be used by the Nest Accelerator (NX) driver(s) to setup receive windows for one or more NX engines (which implement compression/encryption algorithms in the hardware). Follow-on patches will provide an interface to close the

[PATCH v6 06/17] powerpc/vas: Define helpers to alloc/free windows

Define helpers to allocate/free VAS window objects. These will be used in follow-on patches when opening/closing windows. Signed-off-by: Sukadev Bhattiprolu --- arch/powerpc/platforms/powernv/vas-window.c | 70 + 1 file changed, 70 insertions(+) diff --git

[PATCH v6 03/17] powerpc/vas: Define vas_init() and vas_exit()

Implement vas_init() and vas_exit() functions for a new VAS module. This VAS module is essentially a library for other device drivers and kernel users of the NX coprocessors like NX-842 and NX-GZIP. In the future this will be extended to add support for user space to access the NX coprocessors.

[PATCH v6 09/17] powerpc/vas: Define vas_rx_win_open() interface

Define the vas_rx_win_open() interface. This interface is intended to be used by the Nest Accelerator (NX) driver(s) to setup receive windows for one or more NX engines (which implement compression/encryption algorithms in the hardware). Follow-on patches will provide an interface to close the

[PATCH v6 09/17] powerpc/vas: Define vas_rx_win_open() interface

Define the vas_rx_win_open() interface. This interface is intended to be used by the Nest Accelerator (NX) driver(s) to setup receive windows for one or more NX engines (which implement compression/encryption algorithms in the hardware). Follow-on patches will provide an interface to close the

[PATCH v6 12/17] powerpc/vas: Define vas_tx_win_open()

Define an interface to open a VAS send window. This interface is intended to be used the Nest Accelerator (NX) driver(s) to open a send window and use it to submit compression/encryption requests to a VAS receive window. The receive window, identified by the [vasid, cop] parameters, must already

[PATCH v6 12/17] powerpc/vas: Define vas_tx_win_open()

Define an interface to open a VAS send window. This interface is intended to be used the Nest Accelerator (NX) driver(s) to open a send window and use it to submit compression/encryption requests to a VAS receive window. The receive window, identified by the [vasid, cop] parameters, must already

[PATCH v6 14/17] powerpc: Add support for setting SPRN_TIDR

We need the SPRN_TIDR to bet set for use with fast thread-wakeup (core-to-core wakeup). Each thread in a process needs to have a unique id within the process but as explained below, for now, we assign globally unique thread ids to all threads in the system. Signed-off-by: Sukadev Bhattiprolu

[PATCH v6 14/17] powerpc: Add support for setting SPRN_TIDR

We need the SPRN_TIDR to bet set for use with fast thread-wakeup (core-to-core wakeup). Each thread in a process needs to have a unique id within the process but as explained below, for now, we assign globally unique thread ids to all threads in the system. Signed-off-by: Sukadev Bhattiprolu

Re: [PATCH v06 33/36] uapi linux/fsmap.h: use __kernel_size_t instead of size_t

On Mon, Aug 07, 2017 at 10:20:58PM +0200, Arnd Bergmann wrote: > On Mon, Aug 7, 2017 at 6:45 PM, Darrick J. Wong > wrote: > > On Mon, Aug 07, 2017 at 06:01:43PM +0200, Arnd Bergmann wrote: > >> On Mon, Aug 7, 2017 at 5:54 PM, Darrick J. Wong >

Re: [PATCH v06 33/36] uapi linux/fsmap.h: use __kernel_size_t instead of size_t

On Mon, Aug 07, 2017 at 10:20:58PM +0200, Arnd Bergmann wrote: > On Mon, Aug 7, 2017 at 6:45 PM, Darrick J. Wong > wrote: > > On Mon, Aug 07, 2017 at 06:01:43PM +0200, Arnd Bergmann wrote: > >> On Mon, Aug 7, 2017 at 5:54 PM, Darrick J. Wong > >> wrote: > >> > On Sun, Aug 06, 2017 at

[PATCH v6 15/17] powerpc/vas: Define window open ioctls API

Define the VAS_TX_WIN_OPEN and VAS_RX_WIN_OPEN ioctl interface. Each user of VAS, like the NX-FTW driver in a follow-on patch, should implement these ioctls. Signed-off-by: Sukadev Bhattiprolu --- arch/powerpc/include/uapi/asm/vas.h | 30

[PATCH v6 15/17] powerpc/vas: Define window open ioctls API

Define the VAS_TX_WIN_OPEN and VAS_RX_WIN_OPEN ioctl interface. Each user of VAS, like the NX-FTW driver in a follow-on patch, should implement these ioctls. Signed-off-by: Sukadev Bhattiprolu --- arch/powerpc/include/uapi/asm/vas.h | 30 ++ 1 file changed, 30

Re: [PATCH v4] printk: Add monotonic, boottime, and realtime timestamps

On 08/08/2017 04:28 AM, Peter Zijlstra wrote: > On Mon, Aug 07, 2017 at 01:36:39PM -0700, Paul E. McKenney wrote: >> On Mon, Aug 07, 2017 at 04:06:09PM -0400, Prarit Bhargava wrote: > >>> peterz? Want to offer a suggestion? The issue is that I'm changing a bool >>> config option to an int and

Re: [PATCH v4] printk: Add monotonic, boottime, and realtime timestamps

On 08/08/2017 04:28 AM, Peter Zijlstra wrote: > On Mon, Aug 07, 2017 at 01:36:39PM -0700, Paul E. McKenney wrote: >> On Mon, Aug 07, 2017 at 04:06:09PM -0400, Prarit Bhargava wrote: > >>> peterz? Want to offer a suggestion? The issue is that I'm changing a bool >>> config option to an int and

[PATCH v6 16/17] powerpc/vas: Implement a simple FTW driver

The Fast Thread Wake-up (FTW) driver provides user space applications an interface to the Core-to-Core functionality in POWER9. The driver provides the device node/ioctl API to applications and uses the external interfaces to the VAS driver to interact with the VAS hardware. A follow-on patch

[PATCH v6 16/17] powerpc/vas: Implement a simple FTW driver

The Fast Thread Wake-up (FTW) driver provides user space applications an interface to the Core-to-Core functionality in POWER9. The driver provides the device node/ioctl API to applications and uses the external interfaces to the VAS driver to interact with the VAS hardware. A follow-on patch

[PATCH v6 13/17] powerpc/vas: Define copy/paste interfaces

Define interfaces (wrappers) to the 'copy' and 'paste' instructions (which are new in PowerISA 3.0). These are intended to be used to by NX driver(s) to submit Coprocessor Request Blocks (CRBs) to the NX hardware engines. Signed-off-by: Sukadev Bhattiprolu ---

[PATCH v6 13/17] powerpc/vas: Define copy/paste interfaces

Define interfaces (wrappers) to the 'copy' and 'paste' instructions (which are new in PowerISA 3.0). These are intended to be used to by NX driver(s) to submit Coprocessor Request Blocks (CRBs) to the NX hardware engines. Signed-off-by: Sukadev Bhattiprolu --- Changelog[v4] - Export

[PATCH v6 17/17] powerpc/vas: Document FTW API/usage

Document the usage of the VAS Fast thread-wakeup API. Thanks for input/comments from Benjamin Herrenschmidt, Michael Neuling, Michael Ellerman, Robert Blackmore, Ian Munsie, Haren Myneni, Paul Mackerras. Cc:Ian Munsie Cc:Paul Mackerras Signed-off-by:

[PATCH v6 11/17] powerpc/vas: Define vas_win_close() interface

Define the vas_win_close() interface which should be used to close a send or receive windows. While the hardware configurations required to open send and receive windows differ, the configuration to close a window is the same for both. So we use a single interface to close the window.

[PATCH v6 17/17] powerpc/vas: Document FTW API/usage

Document the usage of the VAS Fast thread-wakeup API. Thanks for input/comments from Benjamin Herrenschmidt, Michael Neuling, Michael Ellerman, Robert Blackmore, Ian Munsie, Haren Myneni, Paul Mackerras. Cc:Ian Munsie Cc:Paul Mackerras Signed-off-by: Sukadev Bhattiprolu ---

[PATCH v6 11/17] powerpc/vas: Define vas_win_close() interface

Define the vas_win_close() interface which should be used to close a send or receive windows. While the hardware configurations required to open send and receive windows differ, the configuration to close a window is the same for both. So we use a single interface to close the window.

<    1   2   3   4   5   6   7   8   9   10   >