[PATCH 0/2] arm64: fix handling of DMA masks wider than bus supports

> I reckon the easiest way forward would be to pass in some flag to > arch_setup_dma_ops to indicate whether it's an explicitly-configured > range or not - then simply initialising parent_dma_mask to ~0 for the > default case *should* keep things working as before. Tried to do that. --- Nikita

[PATCH 0/2] arm64: fix handling of DMA masks wider than bus supports

> I reckon the easiest way forward would be to pass in some flag to > arch_setup_dma_ops to indicate whether it's an explicitly-configured > range or not - then simply initialising parent_dma_mask to ~0 for the > default case *should* keep things working as before. Tried to do that. --- Nikita

[PATCH 2/2] arm64: avoid increasing DMA masks above what hardware supports

There are cases when device supports wide DMA addresses wider than device's connection supports. In this case driver sets DMA mask based on knowledge of device capabilities. That must succeed to allow drivers to initialize. However, swiotlb or iommu still need knowledge about actual device

[PATCH 2/2] arm64: avoid increasing DMA masks above what hardware supports

There are cases when device supports wide DMA addresses wider than device's connection supports. In this case driver sets DMA mask based on knowledge of device capabilities. That must succeed to allow drivers to initialize. However, swiotlb or iommu still need knowledge about actual device

Re: [PATCH 1/5] pinctrl: core: Use delayed work for hogs

* Tony Lindgren [170111 08:29]: > * Linus Walleij [170111 07:34]: > > On Tue, Jan 10, 2017 at 8:19 PM, Tony Lindgren wrote: > > > > > Below is an experimental fix to intorduce pinctrl_start() that I've > > > tested with

Re: [PATCH 1/5] pinctrl: core: Use delayed work for hogs

* Tony Lindgren [170111 08:29]: > * Linus Walleij [170111 07:34]: > > On Tue, Jan 10, 2017 at 8:19 PM, Tony Lindgren wrote: > > > > > Below is an experimental fix to intorduce pinctrl_start() that I've > > > tested with pinctrl-single. Then we should probably make all pin > > > controller > >

Re: [PATCH] PCI: mvebu: Handle changes to the bridge windows while enabled

On Mon, Dec 12, 2016 at 11:30:20AM -0700, Jason Gunthorpe wrote: > The PCI core will write to the bridge window config multiple times > while they are enabled. This can lead to mbus failures like: > > mvebu_mbus: cannot add window '4:e8', conflicts with another window > mvebu-pcie

Re: [PATCH] PCI: mvebu: Handle changes to the bridge windows while enabled

On Mon, Dec 12, 2016 at 11:30:20AM -0700, Jason Gunthorpe wrote: > The PCI core will write to the bridge window config multiple times > while they are enabled. This can lead to mbus failures like: > > mvebu_mbus: cannot add window '4:e8', conflicts with another window > mvebu-pcie

Re: [PATCH v2] arm64: do not set dma masks that device connection can't handle

On 11/01/17 12:37, Nikita Yushchenko wrote: >> I actually have a third variation of this problem involving a PCI root >> complex which *could* drive full-width (40-bit) addresses, but won't, >> due to the way its PCI<->AXI interface is programmed. That would require >> even more complicated

Re: [PATCH v2] arm64: do not set dma masks that device connection can't handle

On 11/01/17 12:37, Nikita Yushchenko wrote: >> I actually have a third variation of this problem involving a PCI root >> complex which *could* drive full-width (40-bit) addresses, but won't, >> due to the way its PCI<->AXI interface is programmed. That would require >> even more complicated

Re: [PATCH 1/5] perf, tools: Add probing for xed

On Mon, Jan 09, 2017 at 05:02:21PM -0800, Andi Kleen wrote: SNIP > $(OUTPUT)test-all.bin: > - $(BUILD) -fstack-protector-all -O2 -D_FORTIFY_SOURCE=2 -ldw -lelf > -lnuma -lelf -laudit -I/usr/include/slang -lslang $(shell $(PKG_CONFIG) > --libs --cflags gtk+-2.0 2>/dev/null)

Re: [PATCH 1/5] perf, tools: Add probing for xed

On Mon, Jan 09, 2017 at 05:02:21PM -0800, Andi Kleen wrote: SNIP > $(OUTPUT)test-all.bin: > - $(BUILD) -fstack-protector-all -O2 -D_FORTIFY_SOURCE=2 -ldw -lelf > -lnuma -lelf -laudit -I/usr/include/slang -lslang $(shell $(PKG_CONFIG) > --libs --cflags gtk+-2.0 2>/dev/null)

Re: [tpmdd-devel] [PATCH RFC 0/4] RFC: in-kernel resource manager

On 01/11/2017 01:03 PM, Jason Gunthorpe wrote: On Wed, Jan 11, 2017 at 11:00:43AM +0100, Andreas Fuchs wrote: could we please get an ioctl, that switches the "mode" of the fd entirely. I'd like to see the write()/read() support still intact. All my current code uses main-loop based poll on the

Re: [RFC 09/10] kmod: add helpers for getting kmod count and limit

On Fri, Dec 16, 2016 at 08:57:26AM +0100, Luis R. Rodriguez wrote: > On Thu, Dec 15, 2016 at 05:56:19PM +0100, Petr Mladek wrote: > > On Thu 2016-12-08 11:49:20, Luis R. Rodriguez wrote: > > > This adds helpers for getting access to the kmod count and limit from > > > userspace. While at it, this

Re: [tpmdd-devel] [PATCH RFC 0/4] RFC: in-kernel resource manager

On 01/11/2017 01:03 PM, Jason Gunthorpe wrote: On Wed, Jan 11, 2017 at 11:00:43AM +0100, Andreas Fuchs wrote: could we please get an ioctl, that switches the "mode" of the fd entirely. I'd like to see the write()/read() support still intact. All my current code uses main-loop based poll on the

Re: [RFC 09/10] kmod: add helpers for getting kmod count and limit

On Fri, Dec 16, 2016 at 08:57:26AM +0100, Luis R. Rodriguez wrote: > On Thu, Dec 15, 2016 at 05:56:19PM +0100, Petr Mladek wrote: > > On Thu 2016-12-08 11:49:20, Luis R. Rodriguez wrote: > > > This adds helpers for getting access to the kmod count and limit from > > > userspace. While at it, this

Re: [tpmdd-devel] [PATCH RFC 0/4] RFC: in-kernel resource manager

On Wed, 2017-01-11 at 10:56 -0700, Jason Gunthorpe wrote: > On Wed, Jan 11, 2017 at 07:39:53AM -0800, James Bottomley wrote: > > > RAW access means the ability to DoS the TPM simply by exhausting > > handles. Therefore, I think most applications only get RM access. > > Re-read what Jarkko is

Re: [tpmdd-devel] [PATCH RFC 0/4] RFC: in-kernel resource manager

On Wed, 2017-01-11 at 10:56 -0700, Jason Gunthorpe wrote: > On Wed, Jan 11, 2017 at 07:39:53AM -0800, James Bottomley wrote: > > > RAW access means the ability to DoS the TPM simply by exhausting > > handles. Therefore, I think most applications only get RM access. > > Re-read what Jarkko is

Re: [RFC, PATCHv2 29/29] mm, x86: introduce RLIMIT_VADDR

On 01/11/2017 06:29 AM, Kirill A. Shutemov wrote: > +#define mmap_max_addr() \ > +({ \ > + unsigned long max_addr = min(TASK_SIZE, rlimit(RLIMIT_VADDR)); \ > + /* At the moment, MPX cannot handle addresses above 47-bits */

Re: [RFC, PATCHv2 29/29] mm, x86: introduce RLIMIT_VADDR

On 01/11/2017 06:29 AM, Kirill A. Shutemov wrote: > +#define mmap_max_addr() \ > +({ \ > + unsigned long max_addr = min(TASK_SIZE, rlimit(RLIMIT_VADDR)); \ > + /* At the moment, MPX cannot handle addresses above 47-bits */

Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003

On 11/01/17 18:06, Catalin Marinas wrote: > Some minor comments below, nothing fundamental (as long as you say the > new sequence doesn't have the speculative TLB load problem I mentioned > on a previous version). > > On Wed, Jan 11, 2017 at 09:41:15AM -0500, Christopher Covington wrote: >> diff

Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003

On 11/01/17 18:06, Catalin Marinas wrote: > Some minor comments below, nothing fundamental (as long as you say the > new sequence doesn't have the speculative TLB load problem I mentioned > on a previous version). > > On Wed, Jan 11, 2017 at 09:41:15AM -0500, Christopher Covington wrote: >> diff

Re: x86-64: Maintain 16-byte stack alignment

On Wed, Jan 11, 2017 at 12:09 AM, Herbert Xu wrote: > On Wed, Jan 11, 2017 at 08:06:54AM +, Ard Biesheuvel wrote: >> >> Couldn't we update the __aligned(x) macro to emit 32 if arch == x86 >> and x == 16? All other cases should work just fine afaict > > Not

Re: x86-64: Maintain 16-byte stack alignment

On Wed, Jan 11, 2017 at 12:09 AM, Herbert Xu wrote: > On Wed, Jan 11, 2017 at 08:06:54AM +, Ard Biesheuvel wrote: >> >> Couldn't we update the __aligned(x) macro to emit 32 if arch == x86 >> and x == 16? All other cases should work just fine afaict > > Not everyone uses that macro. You'd

[PATCH 1/2] x86/mm: don't mmap() over 4GB with compat syscall

During fixing CRIU bugs on ZDTM tests for 32-bit C/R, I found that compatible ia32/x32 syscalls mmap() and mmap2() can return address over 4Gb in x86_64 applications, which results in returning lower 4 bytes of address while dropping the higher bytes. It happens because mmap() upper limit doesn't

[PATCH 0/2] Fix compatible mmap() return pointer over 4Gb

A fix for bug in mmap() that I referenced in [1]. Also selftest for it. I would like to mark the fix as for stable v4.9 kernel if it'll be accepted, as I try to support compatible 32-bit C/R after v4.9 and working compatible mmap() is really wanted there. [1]:

[PATCH 1/2] x86/mm: don't mmap() over 4GB with compat syscall

During fixing CRIU bugs on ZDTM tests for 32-bit C/R, I found that compatible ia32/x32 syscalls mmap() and mmap2() can return address over 4Gb in x86_64 applications, which results in returning lower 4 bytes of address while dropping the higher bytes. It happens because mmap() upper limit doesn't

[PATCH 0/2] Fix compatible mmap() return pointer over 4Gb

A fix for bug in mmap() that I referenced in [1]. Also selftest for it. I would like to mark the fix as for stable v4.9 kernel if it'll be accepted, as I try to support compatible 32-bit C/R after v4.9 and working compatible mmap() is really wanted there. [1]:

[PATCH 2/2] selftests/x86: add test to check compat mmap() return addr

We can't just add segfault handler and use addr, returned by compat mmap() syscall, because the lower 4 bytes can be the same as already existed VMA. So, the test parses /proc/self/maps file, founds new VMAs those appeared after compatible sys_mmap() and checks if mmaped VMA is in that list. On

[PATCH 2/2] selftests/x86: add test to check compat mmap() return addr

We can't just add segfault handler and use addr, returned by compat mmap() syscall, because the lower 4 bytes can be the same as already existed VMA. So, the test parses /proc/self/maps file, founds new VMAs those appeared after compatible sys_mmap() and checks if mmaped VMA is in that list. On

Re: [PATCH v2 7/8] net: Rename TCA*BPF_DIGEST to ..._SHA256

On Wed, Jan 11, 2017 at 1:09 AM, Daniel Borkmann wrote: > Hi Andy, > > On 01/11/2017 04:11 AM, Andy Lutomirski wrote: >> >> On Tue, Jan 10, 2017 at 4:50 PM, Daniel Borkmann >> wrote: >>> >>> On 01/11/2017 12:24 AM, Andy Lutomirski wrote:

Re: [PATCH v2 7/8] net: Rename TCA*BPF_DIGEST to ..._SHA256

On Wed, Jan 11, 2017 at 1:09 AM, Daniel Borkmann wrote: > Hi Andy, > > On 01/11/2017 04:11 AM, Andy Lutomirski wrote: >> >> On Tue, Jan 10, 2017 at 4:50 PM, Daniel Borkmann >> wrote: >>> >>> On 01/11/2017 12:24 AM, Andy Lutomirski wrote: This makes it easier to add another digest

Re: [Linux-c6x-dev] [PATCH v2 7/7] uapi: export all headers under uapi directories

On Fri, 2017-01-06 at 10:43 +0100, Nicolas Dichtel wrote: > Regularly, when a new header is created in include/uapi/, the developer > forgets to add it in the corresponding Kbuild file. This error is usually > detected after the release is out. > > In fact, all headers under uapi directories

Re: [Linux-c6x-dev] [PATCH v2 7/7] uapi: export all headers under uapi directories

On Fri, 2017-01-06 at 10:43 +0100, Nicolas Dichtel wrote: > Regularly, when a new header is created in include/uapi/, the developer > forgets to add it in the corresponding Kbuild file. This error is usually > detected after the release is out. > > In fact, all headers under uapi directories

[GIT PULL] MD update for 4.10-rc3

Hi, Please pull MD update for 4.10-rc3. Basically one fix for raid5 cache which is merged in this cycle, others are trival fixes. Thanks, Shaohua The following changes since commit 0c744ea4f77d72b3dcebb7a8f2684633ec79be88: Linux 4.10-rc2 (2017-01-01 14:31:53 -0800) are available in the git

[GIT PULL] MD update for 4.10-rc3

Hi, Please pull MD update for 4.10-rc3. Basically one fix for raid5 cache which is merged in this cycle, others are trival fixes. Thanks, Shaohua The following changes since commit 0c744ea4f77d72b3dcebb7a8f2684633ec79be88: Linux 4.10-rc2 (2017-01-01 14:31:53 -0800) are available in the git

Re: [PATCH v4 0/4] Application Data Integrity feature introduced by SPARC M7

On 01/11/2017 08:56 AM, Khalid Aziz wrote: > On 01/11/2017 09:33 AM, Dave Hansen wrote: >> On 01/11/2017 08:12 AM, Khalid Aziz wrote: >>> A userspace task enables ADI through mprotect(). This patch series adds >>> a page protection bit PROT_ADI and a corresponding VMA flag >>> VM_SPARC_ADI.

[PATCH linux v2 3/6] hwmon: occ: Add I2C transport implementation for SCOM operations

From: "Edward A. James" Add functions to send SCOM operations over I2C bus. The BMC can communicate with the Power8 host processor over I2C, but needs to use SCOM operations in order to access the OCC register space. Signed-off-by: Edward A. James

Re: [PATCH v4 0/4] Application Data Integrity feature introduced by SPARC M7

On 01/11/2017 08:56 AM, Khalid Aziz wrote: > On 01/11/2017 09:33 AM, Dave Hansen wrote: >> On 01/11/2017 08:12 AM, Khalid Aziz wrote: >>> A userspace task enables ADI through mprotect(). This patch series adds >>> a page protection bit PROT_ADI and a corresponding VMA flag >>> VM_SPARC_ADI.

[PATCH linux v2 3/6] hwmon: occ: Add I2C transport implementation for SCOM operations

From: "Edward A. James" Add functions to send SCOM operations over I2C bus. The BMC can communicate with the Power8 host processor over I2C, but needs to use SCOM operations in order to access the OCC register space. Signed-off-by: Edward A. James Signed-off-by: Andrew Jeffery ---

[PATCH linux v2 4/6] hwmon: occ: Add callbacks for parsing P8 OCC datastructures

From: "Edward A. James" Add functions to parse the data structures that are specific to the OCC on the POWER8 processor. These are the sensor data structures, including temperature, frequency, power, and "caps." Signed-off-by: Edward A. James

[PATCH linux v2 4/6] hwmon: occ: Add callbacks for parsing P8 OCC datastructures

From: "Edward A. James" Add functions to parse the data structures that are specific to the OCC on the POWER8 processor. These are the sensor data structures, including temperature, frequency, power, and "caps." Signed-off-by: Edward A. James Signed-off-by: Andrew Jeffery ---

Re: [PATCH v2 8/8] crypto/testmgr: Allocate only the required output size for hash tests

On Wed, Jan 11, 2017 at 7:13 AM, David Laight wrote: > From: Andy Lutomirski >> Sent: 10 January 2017 23:25 >> There are some hashes (e.g. sha224) that have some internal trickery >> to make sure that only the correct number of output bytes are >> generated. If something

[PATCH linux v2 1/6] hwmon: Add core On-Chip Controller support for POWER CPUs

From: "Edward A. James" Add core support for polling the OCC for it's sensor data and parsing that data into sensor-specific information. Signed-off-by: Edward A. James Signed-off-by: Andrew Jeffery --- Documentation/hwmon/occ| 40

Re: [PATCH v2 8/8] crypto/testmgr: Allocate only the required output size for hash tests

On Wed, Jan 11, 2017 at 7:13 AM, David Laight wrote: > From: Andy Lutomirski >> Sent: 10 January 2017 23:25 >> There are some hashes (e.g. sha224) that have some internal trickery >> to make sure that only the correct number of output bytes are >> generated. If something goes wrong, they could

[PATCH linux v2 1/6] hwmon: Add core On-Chip Controller support for POWER CPUs

From: "Edward A. James" Add core support for polling the OCC for it's sensor data and parsing that data into sensor-specific information. Signed-off-by: Edward A. James Signed-off-by: Andrew Jeffery --- Documentation/hwmon/occ| 40 drivers/hwmon/Kconfig | 2 +

[PATCH linux v2 5/6] hwmon: occ: Add hwmon implementation for the P8 OCC

From: "Edward A. James" Add code to tie the hwmon sysfs code and the POWER8 OCC code together, as well as probe the entire driver from the I2C bus. I2C is the communication method between the BMC and the P8 OCC. Signed-off-by: Edward A. James

[PATCH linux v2 5/6] hwmon: occ: Add hwmon implementation for the P8 OCC

From: "Edward A. James" Add code to tie the hwmon sysfs code and the POWER8 OCC code together, as well as probe the entire driver from the I2C bus. I2C is the communication method between the BMC and the P8 OCC. Signed-off-by: Edward A. James Signed-off-by: Andrew Jeffery ---

[PATCH linux v2 6/6] hwmon: occ: Add callbacks for parsing P9 OCC datastructures

From: "Edward A. James" Add functions to parse the data structures that are specific to the OCC on the POWER9 processor. These are the sensor data structures, including temperature, frequency, power, and "caps." Signed-off-by: Edward A. James

[PATCH linux v2 6/6] hwmon: occ: Add callbacks for parsing P9 OCC datastructures

From: "Edward A. James" Add functions to parse the data structures that are specific to the OCC on the POWER9 processor. These are the sensor data structures, including temperature, frequency, power, and "caps." Signed-off-by: Edward A. James Signed-off-by: Andrew Jeffery ---

[PATCH linux v2 2/6] hwmon: occ: Add sysfs interface

From: "Edward A. James" Add a generic mechanism to expose the sensors provided by the OCC in sysfs. Signed-off-by: Edward A. James Signed-off-by: Andrew Jeffery --- Documentation/hwmon/occ | 62 ++

[PATCH linux v2 2/6] hwmon: occ: Add sysfs interface

From: "Edward A. James" Add a generic mechanism to expose the sensors provided by the OCC in sysfs. Signed-off-by: Edward A. James Signed-off-by: Andrew Jeffery --- Documentation/hwmon/occ | 62 ++ drivers/hwmon/occ/Makefile| 2 +- drivers/hwmon/occ/occ_sysfs.c | 274

[PATCH linux v2 0/6] drivers: hwmon: Add On-Chip Controller driver

From: "Edward A. James" This patchset adds a hwmon driver to support the OCC (On-Chip Controller) on the IBM POWER8 and POWER9 processors, from a BMC (Baseboard Management Controller). The OCC is an embedded processor that provides real time power and thermal monitoring. The

[PATCH linux v2 0/6] drivers: hwmon: Add On-Chip Controller driver

From: "Edward A. James" This patchset adds a hwmon driver to support the OCC (On-Chip Controller) on the IBM POWER8 and POWER9 processors, from a BMC (Baseboard Management Controller). The OCC is an embedded processor that provides real time power and thermal monitoring. The driver provides an

Re: [RFC, PATCHv2 29/29] mm, x86: introduce RLIMIT_VADDR

On Wed, Jan 11, 2017 at 6:29 AM, Kirill A. Shutemov wrote: > On Thu, Jan 05, 2017 at 12:49:44PM -0800, Dave Hansen wrote: >> On 01/05/2017 12:14 PM, Andy Lutomirski wrote: >> >> I'm not sure I'm comfortable with this. Do other rlimit changes cause >> >> silent data

Re: [RFC, PATCHv2 29/29] mm, x86: introduce RLIMIT_VADDR

On Wed, Jan 11, 2017 at 6:29 AM, Kirill A. Shutemov wrote: > On Thu, Jan 05, 2017 at 12:49:44PM -0800, Dave Hansen wrote: >> On 01/05/2017 12:14 PM, Andy Lutomirski wrote: >> >> I'm not sure I'm comfortable with this. Do other rlimit changes cause >> >> silent data corruption? I'm pretty sure

Re: [PATCH] ASoC: rt5651: use msleep for large delays

On Wed, Jan 11, 2017 at 03:06:45PM +, Nicholas Mc Guire wrote: > On Wed, Jan 11, 2017 at 02:59:26PM +, Mark Brown wrote: > > If you're doing conversions like this I'd expect us to be picking the > > lower number rather than the higher number - people are saying "wait for > > at least X

Re: [PATCH] ASoC: rt5651: use msleep for large delays

On Wed, Jan 11, 2017 at 03:06:45PM +, Nicholas Mc Guire wrote: > On Wed, Jan 11, 2017 at 02:59:26PM +, Mark Brown wrote: > > If you're doing conversions like this I'd expect us to be picking the > > lower number rather than the higher number - people are saying "wait for > > at least X

Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003

Some minor comments below, nothing fundamental (as long as you say the new sequence doesn't have the speculative TLB load problem I mentioned on a previous version). On Wed, Jan 11, 2017 at 09:41:15AM -0500, Christopher Covington wrote: > diff --git a/Documentation/arm64/silicon-errata.txt >

Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003

Some minor comments below, nothing fundamental (as long as you say the new sequence doesn't have the speculative TLB load problem I mentioned on a previous version). On Wed, Jan 11, 2017 at 09:41:15AM -0500, Christopher Covington wrote: > diff --git a/Documentation/arm64/silicon-errata.txt >

Re: [tpmdd-devel] [PATCH RFC 0/4] RFC: in-kernel resource manager

On Wed, Jan 11, 2017 at 11:00:43AM +0100, Andreas Fuchs wrote: > could we please get an ioctl, that switches the "mode" of the fd entirely. > I'd like to see the write()/read() support still intact. > All my current code uses main-loop based poll on the fd and I don't want > to be force to start

Re: [tpmdd-devel] [PATCH RFC 0/4] RFC: in-kernel resource manager

On Wed, Jan 11, 2017 at 11:00:43AM +0100, Andreas Fuchs wrote: > could we please get an ioctl, that switches the "mode" of the fd entirely. > I'd like to see the write()/read() support still intact. > All my current code uses main-loop based poll on the fd and I don't want > to be force to start

Re: [PATCH/RESEND v2 5/5] z3fold: add kref refcounting

On Wed, Jan 11, 2017 at 12:51 PM, Vitaly Wool wrote: > On Wed, Jan 11, 2017 at 6:39 PM, Dan Streetman wrote: >> On Wed, Jan 11, 2017 at 12:27 PM, Vitaly Wool wrote: >>> On Wed, Jan 11, 2017 at 6:08 PM, Dan Streetman

Re: [PATCH/RESEND v2 5/5] z3fold: add kref refcounting

On Wed, Jan 11, 2017 at 12:51 PM, Vitaly Wool wrote: > On Wed, Jan 11, 2017 at 6:39 PM, Dan Streetman wrote: >> On Wed, Jan 11, 2017 at 12:27 PM, Vitaly Wool wrote: >>> On Wed, Jan 11, 2017 at 6:08 PM, Dan Streetman wrote: On Wed, Jan 11, 2017 at 10:06 AM, Vitaly Wool wrote: > With

[PATCH v5 3/9] mm/swap: Split swap cache into 64MB trunks

From: "Huang, Ying" The patch is to improve the scalability of the swap out/in via using fine grained locks for the swap cache. In current kernel, one address space will be used for each swap device. And in the common configuration, the number of the swap device is very

Re: [PATCH] PCI: designware: fix asynchronous external abort in keystone PCIe h/w

On 01/10/2017 06:06 PM, Bjorn Helgaas wrote: > On Tue, Jan 10, 2017 at 12:18:29PM -0500, Murali Karicheri wrote: >> On 01/10/2017 10:12 AM, Bjorn Helgaas wrote: >>> Hi Murali, >>> >>> On Wed, Jan 04, 2017 at 02:32:30PM -0500, Murali Karicheri wrote: Recent fixes for iATU unroll support

[PATCH v5 1/9] mm/swap: Fix kernel message in swap_info_get()

From: "Huang, Ying" swap_info_get() is used not only in swap free code path but also in page_swapcount(), etc. So the original kernel message in swap_info_get() is not correct now. Fix it via replacing "swap_free" to "swap_info_get" in the message. Signed-off-by: "Huang,

Re: [PATCH v6] x86: fix kaslr and memmap collision

On 01/11/2017 05:00 AM, Thomas Gleixner wrote: > On Tue, 10 Jan 2017, Dave Jiang wrote: >> +unsigned long simple_strtoul(const char *cp, char **endp, unsigned int >> base); >> +long simple_strtol(const char *cp, char **endp, unsigned int base); > > What are those functions for? They are not

[PATCH v5 3/9] mm/swap: Split swap cache into 64MB trunks

From: "Huang, Ying" The patch is to improve the scalability of the swap out/in via using fine grained locks for the swap cache. In current kernel, one address space will be used for each swap device. And in the common configuration, the number of the swap device is very small (one is typical).

Re: [PATCH] PCI: designware: fix asynchronous external abort in keystone PCIe h/w

On 01/10/2017 06:06 PM, Bjorn Helgaas wrote: > On Tue, Jan 10, 2017 at 12:18:29PM -0500, Murali Karicheri wrote: >> On 01/10/2017 10:12 AM, Bjorn Helgaas wrote: >>> Hi Murali, >>> >>> On Wed, Jan 04, 2017 at 02:32:30PM -0500, Murali Karicheri wrote: Recent fixes for iATU unroll support

[PATCH v5 1/9] mm/swap: Fix kernel message in swap_info_get()

From: "Huang, Ying" swap_info_get() is used not only in swap free code path but also in page_swapcount(), etc. So the original kernel message in swap_info_get() is not correct now. Fix it via replacing "swap_free" to "swap_info_get" in the message. Signed-off-by: "Huang, Ying" Signed-off-by:

Re: [PATCH v6] x86: fix kaslr and memmap collision

On 01/11/2017 05:00 AM, Thomas Gleixner wrote: > On Tue, 10 Jan 2017, Dave Jiang wrote: >> +unsigned long simple_strtoul(const char *cp, char **endp, unsigned int >> base); >> +long simple_strtol(const char *cp, char **endp, unsigned int base); > > What are those functions for? They are not

Re: [tpmdd-devel] [PATCH RFC 0/4] RFC: in-kernel resource manager

On Wed, Jan 11, 2017 at 07:39:53AM -0800, James Bottomley wrote: > RAW access means the ability to DoS the TPM simply by exhausting > handles. Therefore, I think most applications only get RM access. Re-read what Jarkko is proposing. He is not making a complete safe & secure RM in the kernel.

Re: [tpmdd-devel] [PATCH RFC 0/4] RFC: in-kernel resource manager

On Wed, Jan 11, 2017 at 07:39:53AM -0800, James Bottomley wrote: > RAW access means the ability to DoS the TPM simply by exhausting > handles. Therefore, I think most applications only get RM access. Re-read what Jarkko is proposing. He is not making a complete safe & secure RM in the kernel.

[PATCH v5 6/9] mm/swap: Free swap slots in batch

Add new functions that free unused swap slots in batches without the need to reacquire swap info lock. This improves scalability and reduce lock contention. Signed-off-by: Tim Chen Co-developed-by: "Huang, Ying" --- include/linux/swap.h | 1

[PATCH v5 5/9] mm/swap: Allocate swap slots in batches

Currently, the swap slots are allocated one page at a time, causing contention to the swap_info lock protecting the swap partition on every page being swapped. This patch adds new functions get_swap_pages and scan_swap_map_slots to request multiple swap slots at once. This will reduces the lock

[PATCH v5 6/9] mm/swap: Free swap slots in batch

Add new functions that free unused swap slots in batches without the need to reacquire swap info lock. This improves scalability and reduce lock contention. Signed-off-by: Tim Chen Co-developed-by: "Huang, Ying" --- include/linux/swap.h | 1 + mm/swapfile.c| 155

[PATCH v5 5/9] mm/swap: Allocate swap slots in batches

Currently, the swap slots are allocated one page at a time, causing contention to the swap_info lock protecting the swap partition on every page being swapped. This patch adds new functions get_swap_pages and scan_swap_map_slots to request multiple swap slots at once. This will reduces the lock

Re: [PATCH 2/3] gpio: davinci: Redesign driver to accommodate ngpios in one gpio chip

On 01/10/2017 11:00 PM, Keerthy wrote: > The Davinci GPIO driver is implemented to work with one monolithic > Davinci GPIO platform device which may have up to Y(144) gpios. > The Davinci GPIO driver instantiates number of GPIO chips with > max 32 gpio pins per each during initialization and one

Re: [PATCH 2/3] gpio: davinci: Redesign driver to accommodate ngpios in one gpio chip

On 01/10/2017 11:00 PM, Keerthy wrote: > The Davinci GPIO driver is implemented to work with one monolithic > Davinci GPIO platform device which may have up to Y(144) gpios. > The Davinci GPIO driver instantiates number of GPIO chips with > max 32 gpio pins per each during initialization and one

[PATCH v5 2/9] mm/swap: Add cluster lock

From: "Huang, Ying" This patch is to reduce the lock contention of swap_info_struct->lock via using a more fine grained lock in swap_cluster_info for some swap operations. swap_info_struct->lock is heavily contended if multiple processes reclaim pages simultaneously.

[PATCH v5 2/9] mm/swap: Add cluster lock

From: "Huang, Ying" This patch is to reduce the lock contention of swap_info_struct->lock via using a more fine grained lock in swap_cluster_info for some swap operations. swap_info_struct->lock is heavily contended if multiple processes reclaim pages simultaneously. Because there is only one

Re: [GIT] Networking

Thanks. Pulled, going through my usual allmodconfig test-build before being pushed out, Linus On Wed, Jan 11, 2017 at 7:22 AM, David Miller wrote: > > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git

Re: [GIT] Networking

Thanks. Pulled, going through my usual allmodconfig test-build before being pushed out, Linus On Wed, Jan 11, 2017 at 7:22 AM, David Miller wrote: > > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git

[PATCH 2/3] iio: adc: ti-ads7950: Drop "ti-" prefix from module name

This drops the "ti-" prefix from the module name. It makes the module name consistent with other iio ti-ads* drivers and it makes the driver work with device tree (the spi subsystem drops the "ti," prefix when matching compatible strings from device tree). Tested working on LEGO MINDSTORMS EV3

[PATCH v5 9/9] mm/swap: Skip readahead only when swap slot cache is enabled

From: Huang Ying Because during swap off, a swap entry may have swap_map[] == SWAP_HAS_CACHE (for example, just allocated). If we return NULL in __read_swap_cache_async(), the swap off will abort. So when swap slot cache is disabled, (for swap off), we will wait for page

[PATCH v5 0/9] mm/swap: Regular page swap optimizations

Change Log: v5: 1. Rebase patch series on 4.10-rc3 kernel. Update patch series to remove usage of obsoleted hot plug functions: cpu_notifier_register_begin(), cpu_notifier_register_done(), and __register_hotcpu_notifier() 2. Fix a bug returning uninitialized swap slot when we run out of swap

[PATCH v5 4/9] mm/swap: skip read ahead for unreferenced swap slots

We can avoid needlessly allocating page for swap slots that are not used by anyone. No pages have to be read in for these slots. Signed-off-by: Tim Chen Co-developed-by: "Huang, Ying" --- include/linux/swap.h | 6 ++ mm/swap_state.c |

[PATCH v5 7/9] mm/swap: Add cache for swap slots allocation

We add per cpu caches for swap slots that can be allocated and freed quickly without the need to touch the swap info lock. Two separate caches are maintained for swap slots allocated and swap slots returned. This is to allow the swap slots to be returned to the global pool in a batch so they

[PATCH v5 8/9] mm/swap: Enable swap slots cache usage

Initialize swap slots cache and enable it on swap on. Drain all swap slots on swap off. Signed-off-by: Tim Chen --- mm/swapfile.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/mm/swapfile.c b/mm/swapfile.c index e6c30ed..14d9ea2 100644 ---

[PATCH 2/3] iio: adc: ti-ads7950: Drop "ti-" prefix from module name

This drops the "ti-" prefix from the module name. It makes the module name consistent with other iio ti-ads* drivers and it makes the driver work with device tree (the spi subsystem drops the "ti," prefix when matching compatible strings from device tree). Tested working on LEGO MINDSTORMS EV3

[PATCH v5 9/9] mm/swap: Skip readahead only when swap slot cache is enabled

From: Huang Ying Because during swap off, a swap entry may have swap_map[] == SWAP_HAS_CACHE (for example, just allocated). If we return NULL in __read_swap_cache_async(), the swap off will abort. So when swap slot cache is disabled, (for swap off), we will wait for page to be put into swap

[PATCH v5 0/9] mm/swap: Regular page swap optimizations

Change Log: v5: 1. Rebase patch series on 4.10-rc3 kernel. Update patch series to remove usage of obsoleted hot plug functions: cpu_notifier_register_begin(), cpu_notifier_register_done(), and __register_hotcpu_notifier() 2. Fix a bug returning uninitialized swap slot when we run out of swap

[PATCH v5 4/9] mm/swap: skip read ahead for unreferenced swap slots

We can avoid needlessly allocating page for swap slots that are not used by anyone. No pages have to be read in for these slots. Signed-off-by: Tim Chen Co-developed-by: "Huang, Ying" --- include/linux/swap.h | 6 ++ mm/swap_state.c | 4 mm/swapfile.c| 47

[PATCH v5 7/9] mm/swap: Add cache for swap slots allocation

We add per cpu caches for swap slots that can be allocated and freed quickly without the need to touch the swap info lock. Two separate caches are maintained for swap slots allocated and swap slots returned. This is to allow the swap slots to be returned to the global pool in a batch so they

[PATCH v5 8/9] mm/swap: Enable swap slots cache usage

Initialize swap slots cache and enable it on swap on. Drain all swap slots on swap off. Signed-off-by: Tim Chen --- mm/swapfile.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/mm/swapfile.c b/mm/swapfile.c index e6c30ed..14d9ea2 100644 --- a/mm/swapfile.c +++ b/mm/swapfile.c @@

[PATCH 3/3] iio: adc: ti-ads7950: Change regulator matching string to "vref"

This changes the reference voltage regulator matching string from "refin" to "vref". This is to be consistent with other A/DC chips that also use "vref-supply" in their device tree bindings. Signed-off-by: David Lechner --- drivers/iio/adc/ti-ads7950.c | 6 +++--- 1 file

[PATCH 3/3] iio: adc: ti-ads7950: Change regulator matching string to "vref"

This changes the reference voltage regulator matching string from "refin" to "vref". This is to be consistent with other A/DC chips that also use "vref-supply" in their device tree bindings. Signed-off-by: David Lechner --- drivers/iio/adc/ti-ads7950.c | 6 +++--- 1 file changed, 3

[PATCH 0/3] ti,ads7950 device tree bindings

This series adds device tree bindings for the TI ADS7950 family of A/DC chips. The series includes the bindings documentation and some fixes to the iio driver to make it work with the device tree bindings. FYI, the ads7950 driver has not made it into mainline yet, so no worries about breaking

[PATCH 0/3] ti,ads7950 device tree bindings

This series adds device tree bindings for the TI ADS7950 family of A/DC chips. The series includes the bindings documentation and some fixes to the iio driver to make it work with the device tree bindings. FYI, the ads7950 driver has not made it into mainline yet, so no worries about breaking

<    3   4   5   6   7   8   9   10   11   12   >