Re: x86: A process doesn't stop on hw breakpoints sometimes

On Mon, May 23, 2016 at 4:05 PM, Andrei Vagin wrote: > Hi, > > We use breakpoints on CRIU to stop a processes before calling > rt_sigreturn and we found that sometimes a process runs through a > break-point without stopping on it. > > https://github.com/xemul/criu/issues/162 > >

Re: x86: A process doesn't stop on hw breakpoints sometimes

On Mon, May 23, 2016 at 4:05 PM, Andrei Vagin wrote: > Hi, > > We use breakpoints on CRIU to stop a processes before calling > rt_sigreturn and we found that sometimes a process runs through a > break-point without stopping on it. > > https://github.com/xemul/criu/issues/162 > > > A small

[RESEND PATCH v2] ASoC: rockchip: Add machine driver for MAX98357A/RT5514/DA7219

There are multi codec devices on the RK3399 platform, we can use this patch support and control these codecs. Signed-off-by: Xing Zheng --- Changes in v2: - use the FS 256 to set mclks of the max98357a and rt5514 danamically - add more sample rate for da7219

[RESEND PATCH v2] ASoC: rockchip: Add machine driver for MAX98357A/RT5514/DA7219

There are multi codec devices on the RK3399 platform, we can use this patch support and control these codecs. Signed-off-by: Xing Zheng --- Changes in v2: - use the FS 256 to set mclks of the max98357a and rt5514 danamically - add more sample rate for da7219

Re: [PATCH] autofs: don't stuck in a loop if vfs_write returns an error

On Mon, 2016-05-23 at 14:50 -0700, Andrei Vagin wrote: > Hi Ian, > > When are you going to apply this patch? We can't test linux-next without it. I though I sent this with the last series but I can't see that I have. I have the rest of that series to send over to Andrew which I was planning to

Re: [PATCH] autofs: don't stuck in a loop if vfs_write returns an error

On Mon, 2016-05-23 at 14:50 -0700, Andrei Vagin wrote: > Hi Ian, > > When are you going to apply this patch? We can't test linux-next without it. I though I sent this with the last series but I can't see that I have. I have the rest of that series to send over to Andrew which I was planning to

Re: [PATCH] regulator: mt6397: Constify struct regulator_ops

Hi Mark, On Mon, 2016-05-23 at 12:32 +0100, Mark Brown wrote: > On Mon, May 23, 2016 at 03:30:16PM +0800, Henry Chen wrote: > > Consitify the structure of regulator operations. > > Oh, actually the mode setting patch does apply but it depends on this > one (which was sent after...). It would

Re: [PATCH] regulator: mt6397: Constify struct regulator_ops

Hi Mark, On Mon, 2016-05-23 at 12:32 +0100, Mark Brown wrote: > On Mon, May 23, 2016 at 03:30:16PM +0800, Henry Chen wrote: > > Consitify the structure of regulator operations. > > Oh, actually the mode setting patch does apply but it depends on this > one (which was sent after...). It would

Re: [PATCH 2/2] pci: Add PCIe driver for Rockchip Soc

Hi Bharat, On 2016/5/23 23:15, Bharat Kumar Gogada wrote: + + irq = platform_get_irq_byname(pdev, "pcie-sys"); + if (irq < 0) { + dev_err(dev, "missing pcie_sys IRQ resource\n"); + return -EINVAL; + } + err = devm_request_irq(dev, irq,

Re: [PATCH 2/2] pci: Add PCIe driver for Rockchip Soc

Hi Bharat, On 2016/5/23 23:15, Bharat Kumar Gogada wrote: + + irq = platform_get_irq_byname(pdev, "pcie-sys"); + if (irq < 0) { + dev_err(dev, "missing pcie_sys IRQ resource\n"); + return -EINVAL; + } + err = devm_request_irq(dev, irq,

Re: x86: A process doesn't stop on hw breakpoints sometimes

On Mon, May 23, 2016 at 4:05 PM, Andrei Vagin wrote: > Hi, > > We use breakpoints on CRIU to stop a processes before calling > rt_sigreturn and we found that sometimes a process runs through a > break-point without stopping on it. > > https://github.com/xemul/criu/issues/162 > >

Re: x86: A process doesn't stop on hw breakpoints sometimes

On Mon, May 23, 2016 at 4:05 PM, Andrei Vagin wrote: > Hi, > > We use breakpoints on CRIU to stop a processes before calling > rt_sigreturn and we found that sometimes a process runs through a > break-point without stopping on it. > > https://github.com/xemul/criu/issues/162 > > > A small

Re: [PATCH v3 3/3] sched, x86: Check that we're on the right stack in schedule and __might_sleep

On Sun, Feb 28, 2016 at 9:27 PM, Andy Lutomirski wrote: > On Wed, Nov 19, 2014 at 11:44 AM, Linus Torvalds > wrote: >> On Wed, Nov 19, 2014 at 11:29 AM, Andi Kleen wrote: >>> >>> The exception handlers which use the IST

Re: [PATCH v3 3/3] sched, x86: Check that we're on the right stack in schedule and __might_sleep

On Sun, Feb 28, 2016 at 9:27 PM, Andy Lutomirski wrote: > On Wed, Nov 19, 2014 at 11:44 AM, Linus Torvalds > wrote: >> On Wed, Nov 19, 2014 at 11:29 AM, Andi Kleen wrote: >>> >>> The exception handlers which use the IST stacks don't necessarily >>> set irq count. Maybe they should. >> >> Hmm. I

Re: [PATCH] fbcon: warn on invalid cursor blink intervals

On Fri, 20 May 2016, Scot Doyle wrote: > On Fri, 20 May 2016, Jeremy Kerr wrote: > > Hi Ming, > > > > >Then looks there are two fix patches acked & tested: > > > > > > - the patch in this thread > > > - another one "[PATCH] tty: vt: Fix soft lockup in fbcon cursor > > >blink timer." > > >

Re: [PATCH] fbcon: warn on invalid cursor blink intervals

On Fri, 20 May 2016, Scot Doyle wrote: > On Fri, 20 May 2016, Jeremy Kerr wrote: > > Hi Ming, > > > > >Then looks there are two fix patches acked & tested: > > > > > > - the patch in this thread > > > - another one "[PATCH] tty: vt: Fix soft lockup in fbcon cursor > > >blink timer." > > >

Re: [PATCH v2] KVM: halt-polling: poll if emulated lapic timer will fire soon

On Mon, May 23, 2016 at 6:13 PM, Yang Zhang wrote: > On 2016/5/24 2:04, David Matlack wrote: >> >> On Sun, May 22, 2016 at 6:26 PM, Yang Zhang >> wrote: >>> >>> On 2016/5/21 2:37, David Matlack wrote: It's not obvious to me why

Re: [PATCH v2] KVM: halt-polling: poll if emulated lapic timer will fire soon

On Mon, May 23, 2016 at 6:13 PM, Yang Zhang wrote: > On 2016/5/24 2:04, David Matlack wrote: >> >> On Sun, May 22, 2016 at 6:26 PM, Yang Zhang >> wrote: >>> >>> On 2016/5/21 2:37, David Matlack wrote: It's not obvious to me why polling for a timer interrupt would improve

Re: [PATCH v2] KVM: halt-polling: poll if emulated lapic timer will fire soon

On 2016/5/24 2:04, David Matlack wrote: On Sun, May 22, 2016 at 6:26 PM, Yang Zhang wrote: On 2016/5/21 2:37, David Matlack wrote: It's not obvious to me why polling for a timer interrupt would improve context switch latency. Can you explain a bit more? We have a

Re: [PATCH v2] KVM: halt-polling: poll if emulated lapic timer will fire soon

On 2016/5/24 2:04, David Matlack wrote: On Sun, May 22, 2016 at 6:26 PM, Yang Zhang wrote: On 2016/5/21 2:37, David Matlack wrote: It's not obvious to me why polling for a timer interrupt would improve context switch latency. Can you explain a bit more? We have a workload which using high

Re: [PATCH V7 00/11] Support for generic ACPI based PCI host controller

Bjorn, Out walking so sorry about top posting. Quick reply though: 1. I checked with the Windows team. They usually avoid quirks entirely but when it has happened, it has been done via the MCFG/FADT not DSDT. 2. They would be ok if we were to key off the OEM name and revision for the IP in

Re: [PATCH V7 00/11] Support for generic ACPI based PCI host controller

Bjorn, Out walking so sorry about top posting. Quick reply though: 1. I checked with the Windows team. They usually avoid quirks entirely but when it has happened, it has been done via the MCFG/FADT not DSDT. 2. They would be ok if we were to key off the OEM name and revision for the IP in

Re: [PATCH 1/3] Documentation: dtb: xgene: Add hwmon dts binding documentation

Hi Rob, Thanks for your review ! On Mon, May 23, 2016 at 1:30 PM, Rob Herring wrote: > > On Mon, May 16, 2016 at 09:17:25AM -0700, Hoan Tran wrote: > > This patch adds the APM X-Gene hwmon device tree node documentation. > > > > Signed-off-by: Hoan Tran > > ---

Re: [PATCH 1/3] Documentation: dtb: xgene: Add hwmon dts binding documentation

Hi Rob, Thanks for your review ! On Mon, May 23, 2016 at 1:30 PM, Rob Herring wrote: > > On Mon, May 16, 2016 at 09:17:25AM -0700, Hoan Tran wrote: > > This patch adds the APM X-Gene hwmon device tree node documentation. > > > > Signed-off-by: Hoan Tran > > --- > >

[PATCH 1/3] perf pt: Mark PT return events as "return"

From: Andi Kleen With perf script --itrace=cr we can synthesize calls and returns out of a PT log. However both calls and returns are marked with the same event, called branches. This makes it difficult to read and post process, because calls and returns are somewhat

[PATCH 1/3] perf pt: Mark PT return events as "return"

From: Andi Kleen With perf script --itrace=cr we can synthesize calls and returns out of a PT log. However both calls and returns are marked with the same event, called branches. This makes it difficult to read and post process, because calls and returns are somewhat diffferent. Create a

[PATCH 2/3] perf util: Move get_main_thread to thread.c

From: Andi Kleen Move the get_main_thread function from db-export.c to thread.c so that it can be used elsewhere. Signed-off-by: Andi Kleen --- tools/perf/util/db-export.c | 13 + tools/perf/util/db-export.h | 2 ++

[PATCH 2/3] perf util: Move get_main_thread to thread.c

From: Andi Kleen Move the get_main_thread function from db-export.c to thread.c so that it can be used elsewhere. Signed-off-by: Andi Kleen --- tools/perf/util/db-export.c | 13 + tools/perf/util/db-export.h | 2 ++ tools/perf/util/thread.c| 11 +++

[PATCH 3/3] perf script: Support callindent

From: Andi Kleen When printing PT instruction traces with perf script it is rather useful to see some indentation for the call tree. This patch adds a new callindent field to perf script that prints spaces for the function call stack depth. We already have code to track

[PATCH 3/3] perf script: Support callindent

From: Andi Kleen When printing PT instruction traces with perf script it is rather useful to see some indentation for the call tree. This patch adds a new callindent field to perf script that prints spaces for the function call stack depth. We already have code to track the function call stack

Re: [PATCH 1/2] perf pt: Mark PT return events as "return"

On Mon, May 23, 2016 at 03:05:08PM +0300, Adrian Hunter wrote: > On 20/05/16 22:52, Andi Kleen wrote: > > From: Andi Kleen > > > > With perf script --itrace=cr we can synthesize calls and returns out of > > a PT log. However both calls and returns are marked with the same

Re: [PATCH 1/2] perf pt: Mark PT return events as "return"

On Mon, May 23, 2016 at 03:05:08PM +0300, Adrian Hunter wrote: > On 20/05/16 22:52, Andi Kleen wrote: > > From: Andi Kleen > > > > With perf script --itrace=cr we can synthesize calls and returns out of > > a PT log. However both calls and returns are marked with the same event, > > called

Re: [PATCH v5 3/5] mmc: core: implement enhanced strobe support

Shawn, On Sun, May 22, 2016 at 9:13 PM, Shawn Lin wrote: > Controllers use data strobe line to latch data from devices > under hs400 mode, but not for cmd line. So since emmc 5.1, JEDEC > introduces enhanced strobe mode for latching cmd response from > emmc devices to

Re: [PATCH v5 3/5] mmc: core: implement enhanced strobe support

Shawn, On Sun, May 22, 2016 at 9:13 PM, Shawn Lin wrote: > Controllers use data strobe line to latch data from devices > under hs400 mode, but not for cmd line. So since emmc 5.1, JEDEC > introduces enhanced strobe mode for latching cmd response from > emmc devices to host controllers. This new

[PATCH] staging: lustre: llite: drop acl from cache

Commit b8a7a3a6 change get_acl() for posix xattr to always cache the ACL which increases the reference count. That reference count can be reduced by have ll_get_acl() call forget_cached_acl() which it wasn't. When an inode gets deleted by Lustre the POSIX ACL reference count is tested to ensure

[PATCH] staging: lustre: llite: drop acl from cache

Commit b8a7a3a6 change get_acl() for posix xattr to always cache the ACL which increases the reference count. That reference count can be reduced by have ll_get_acl() call forget_cached_acl() which it wasn't. When an inode gets deleted by Lustre the POSIX ACL reference count is tested to ensure

[PATCH v4 2/4] gpio: Allow PC/104 devices on X86_64

With the introduction of the ISA_BUS_API Kconfig option, ISA-style drivers may be built for X86_64 architectures. This patch changes the ISA Kconfig option dependency of the PC/104 drivers to ISA_BUS_API, thus allowing them to build for X86_64 as they are expected to. Cc: Guenter Roeck

[PATCH v4 4/4] watchdog: ebc-c384_wdt: Allow build for X86_64

With the introduction of the ISA_BUS_API Kconfig option, ISA-style drivers may be built for X86_64 architectures. This patch changes the ISA Kconfig option dependency of the WinSystems EBC-C384 watchdog timer driver to ISA_BUS_API, thus allowing it to build for X86_64 as it is expected to. Cc:

[PATCH v4 2/4] gpio: Allow PC/104 devices on X86_64

With the introduction of the ISA_BUS_API Kconfig option, ISA-style drivers may be built for X86_64 architectures. This patch changes the ISA Kconfig option dependency of the PC/104 drivers to ISA_BUS_API, thus allowing them to build for X86_64 as they are expected to. Cc: Guenter Roeck Cc: Linus

[PATCH v4 4/4] watchdog: ebc-c384_wdt: Allow build for X86_64

With the introduction of the ISA_BUS_API Kconfig option, ISA-style drivers may be built for X86_64 architectures. This patch changes the ISA Kconfig option dependency of the WinSystems EBC-C384 watchdog timer driver to ISA_BUS_API, thus allowing it to build for X86_64 as it is expected to. Cc:

[PATCH v4 1/4] isa: Allow ISA-style drivers on modern systems

Several modern devices, such as PC/104 cards, are expected to run on modern systems via an ISA bus interface. Since ISA is a legacy interface for most modern architectures, ISA support should remain disabled in general. Support for ISA-style drivers should be enabled on a per driver basis. To

[PATCH v4 3/4] iio: stx104: Allow build for X86_64

With the introduction of the ISA_BUS_API Kconfig option, ISA-style drivers may be built for X86_64 architectures. This patch changes the ISA Kconfig option dependency of the Apex Embedded Systems STX104 DAC driver to ISA_BUS_API, thus allowing it to build for X86_64 as it is expected to. Cc:

[PATCH v4 1/4] isa: Allow ISA-style drivers on modern systems

Several modern devices, such as PC/104 cards, are expected to run on modern systems via an ISA bus interface. Since ISA is a legacy interface for most modern architectures, ISA support should remain disabled in general. Support for ISA-style drivers should be enabled on a per driver basis. To

[PATCH v4 3/4] iio: stx104: Allow build for X86_64

With the introduction of the ISA_BUS_API Kconfig option, ISA-style drivers may be built for X86_64 architectures. This patch changes the ISA Kconfig option dependency of the Apex Embedded Systems STX104 DAC driver to ISA_BUS_API, thus allowing it to build for X86_64 as it is expected to. Cc:

[PATCH v4 0/4] Allow ISA-style drivers on modern systems

Changes in v4: - Remove unnecessary explicit "default n" from the X86 ISA_BUS Kconfig option since Kconfig options are disabled by default Changes in v3: - Remove redundant X86 dependency from the X86 ISA_BUS Kconfig option Changes in v2: - Adjusted preprocessor compilation conditional

[PATCH v4 0/4] Allow ISA-style drivers on modern systems

Changes in v4: - Remove unnecessary explicit "default n" from the X86 ISA_BUS Kconfig option since Kconfig options are disabled by default Changes in v3: - Remove redundant X86 dependency from the X86 ISA_BUS Kconfig option Changes in v2: - Adjusted preprocessor compilation conditional

[PATCH 13/23] arm64: introduce is_a32_task and is_a32_thread (for AArch32 compat)

Based on patch of Andrew Pinski. This patch introduces is_a32_compat_task and is_a32_thread so it is easier to say this is a a32 specific thread or a generic compat thread/task. Corresponding functions are located in to avoid mess in headers. Some files include both and , and this is wrong

[PATCH 13/23] arm64: introduce is_a32_task and is_a32_thread (for AArch32 compat)

Based on patch of Andrew Pinski. This patch introduces is_a32_compat_task and is_a32_thread so it is easier to say this is a a32 specific thread or a generic compat thread/task. Corresponding functions are located in to avoid mess in headers. Some files include both and , and this is wrong

[PATCH 05/23] all: wrap needed syscalls in generic unistd

As generic unistd syscall table is written in C, syscall prototypes declaration is needed. It's added to compat header. Signed-off-by: Yury Norov --- include/linux/compat.h| 225 + include/uapi/asm-generic/unistd.h | 227

[PATCH 10/23] arm64: rename COMPAT to AARCH32_EL0 in Kconfig

From: Andrew Pinski In this patchset ILP32 ABI support is added. Additionally to AARCH32, which is binary-compatible with ARM, ILP32 is (mostly) ABI-compatible. >From now, AARCH32_EL0 (former COMPAT) config option means the support of AARCH32 userspace, ARM64_ILP32 -

[PATCH 05/23] all: wrap needed syscalls in generic unistd

As generic unistd syscall table is written in C, syscall prototypes declaration is needed. It's added to compat header. Signed-off-by: Yury Norov --- include/linux/compat.h| 225 + include/uapi/asm-generic/unistd.h | 227

[PATCH 10/23] arm64: rename COMPAT to AARCH32_EL0 in Kconfig

From: Andrew Pinski In this patchset ILP32 ABI support is added. Additionally to AARCH32, which is binary-compatible with ARM, ILP32 is (mostly) ABI-compatible. >From now, AARCH32_EL0 (former COMPAT) config option means the support of AARCH32 userspace, ARM64_ILP32 - support of ILP32 ABI (see

Re: Regression in 4.6.0-git - bisected to commit dd254f5a382c

On Mon, May 23, 2016 at 04:30:43PM -0500, Larry Finger wrote: > The mainline kernels past 4.6.0 fail hang when logging in. There are no > error messages, and the machine seems to be waiting for some event that > never happens. > > The problem has been bisected to commit dd254f5a382c ("fold checks

Re: Regression in 4.6.0-git - bisected to commit dd254f5a382c

On Mon, May 23, 2016 at 04:30:43PM -0500, Larry Finger wrote: > The mainline kernels past 4.6.0 fail hang when logging in. There are no > error messages, and the machine seems to be waiting for some event that > never happens. > > The problem has been bisected to commit dd254f5a382c ("fold checks

[PATCH v6 00/21] ILP32 for ARM64

This series enables aarch64 with ilp32 mode, and as supporting work, introduces compat wrappers based on s390 solution, and also introduces ARCH_32BIT_OFF_T configuration option that is enabled for existing 32-bit architectures but disabled for new arches (so 64-bit off_t is is used by new

[PATCH 04/23] all: s390: move compat_wrappers.c from arch/s390/kernel to kernel/

Some syscalls are declared conditionally, so corresponding wrappers are conditional accordingly. Signed-off-by: Yury Norov --- arch/s390/kernel/Makefile | 2 +- arch/s390/kernel/compat_linux.c | 4 + arch/s390/kernel/compat_wrapper.c | 129

[PATCH v6 00/21] ILP32 for ARM64

This series enables aarch64 with ilp32 mode, and as supporting work, introduces compat wrappers based on s390 solution, and also introduces ARCH_32BIT_OFF_T configuration option that is enabled for existing 32-bit architectures but disabled for new arches (so 64-bit off_t is is used by new

[PATCH 04/23] all: s390: move compat_wrappers.c from arch/s390/kernel to kernel/

Some syscalls are declared conditionally, so corresponding wrappers are conditional accordingly. Signed-off-by: Yury Norov --- arch/s390/kernel/Makefile | 2 +- arch/s390/kernel/compat_linux.c | 4 + arch/s390/kernel/compat_wrapper.c | 129

[PATCH 02/23] all: introduce COMPAT_WRAPPER option and enable it for s390

Signed-off-by: Yury Norov --- arch/Kconfig | 4 arch/s390/Kconfig | 1 + 2 files changed, 5 insertions(+) diff --git a/arch/Kconfig b/arch/Kconfig index 81869a5..92fcbd4 100644 --- a/arch/Kconfig +++ b/arch/Kconfig @@ -589,6 +589,10 @@ config

[PATCH 02/23] all: introduce COMPAT_WRAPPER option and enable it for s390

Signed-off-by: Yury Norov --- arch/Kconfig | 4 arch/s390/Kconfig | 1 + 2 files changed, 5 insertions(+) diff --git a/arch/Kconfig b/arch/Kconfig index 81869a5..92fcbd4 100644 --- a/arch/Kconfig +++ b/arch/Kconfig @@ -589,6 +589,10 @@ config HAVE_STACK_VALIDATION

[PATCH 07/23] 32-bit ABI: introduce ARCH_32BIT_OFF_T config option

All new 32-bit architectures should have 64-bit off_t type, but existing architectures has 32-bit ones. To handle it, new config option is added to arch/Kconfig that defaults ARCH_32BIT_OFF_T to be disabled for non-64 bit architectures. All existing 32-bit architectures enable it explicitly here.

[PATCH 07/23] 32-bit ABI: introduce ARCH_32BIT_OFF_T config option

All new 32-bit architectures should have 64-bit off_t type, but existing architectures has 32-bit ones. To handle it, new config option is added to arch/Kconfig that defaults ARCH_32BIT_OFF_T to be disabled for non-64 bit architectures. All existing 32-bit architectures enable it explicitly here.

[PATCH 18/23] arm64: ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it

From: Andrew Pinski Add a separate syscall-table for ILP32, which dispatches either to native LP64 system call implementation or to compat-syscalls, as appropriate. Signed-off-by: Andrew Pinski Signed-off-by: Yury Norov

[PATCH 15/23] arm64: introduce binfmt_elf32.c

As we support more than one compat formats, it looks more reasonable to not use fs/compat_binfmt.c. Custom binfmt_elf32.c allows to move aarch32 specific definitions there and make code more maintainable and readable. Signed-off-by: Yury Norov --- arch/arm64/Kconfig

[PATCH 18/23] arm64: ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it

From: Andrew Pinski Add a separate syscall-table for ILP32, which dispatches either to native LP64 system call implementation or to compat-syscalls, as appropriate. Signed-off-by: Andrew Pinski Signed-off-by: Yury Norov --- arch/arm64/include/asm/unistd.h | 11 +-

[PATCH 15/23] arm64: introduce binfmt_elf32.c

As we support more than one compat formats, it looks more reasonable to not use fs/compat_binfmt.c. Custom binfmt_elf32.c allows to move aarch32 specific definitions there and make code more maintainable and readable. Signed-off-by: Yury Norov --- arch/arm64/Kconfig | 1 -

[PATCH 17/23] arm64: ptrace: handle ptrace_request differently for aarch32 and ilp32

Here new aarch32 ptrace syscall handler is introsuced to avoid run-time detection of the task type. Signed-off-by: Yury Norov --- arch/arm64/include/asm/unistd32.h | 2 +- arch/arm64/kernel/ptrace.c| 50 ++-

[PATCH 17/23] arm64: ptrace: handle ptrace_request differently for aarch32 and ilp32

Here new aarch32 ptrace syscall handler is introsuced to avoid run-time detection of the task type. Signed-off-by: Yury Norov --- arch/arm64/include/asm/unistd32.h | 2 +- arch/arm64/kernel/ptrace.c| 50 ++- arch/arm64/kernel/sys32.c | 1 +

[PATCH 14/23] arm64: ilp32: add is_ilp32_compat_{task,thread} and TIF_32BIT_AARCH64

ILP32 tasks are needed to be distinguished from lp64 and aarch32. This patch adds helper functions is_ilp32_compat_{task,thread} and thread flag TIF_32BIT_AARCH64 to address it. This is a preparation for following patches in ilp32 patchset. For consistency, SET_PERSONALITY is changed here

[PATCH 20/23] arm64: signal32: move ilp32 and aarch32 common code to separated file

Signed-off-by: Yury Norov --- arch/arm64/include/asm/signal32_common.h | 25 +++ arch/arm64/kernel/Makefile | 1 + arch/arm64/kernel/signal32.c | 85 --- arch/arm64/kernel/signal32_common.c | 115

[PATCH 14/23] arm64: ilp32: add is_ilp32_compat_{task,thread} and TIF_32BIT_AARCH64

ILP32 tasks are needed to be distinguished from lp64 and aarch32. This patch adds helper functions is_ilp32_compat_{task,thread} and thread flag TIF_32BIT_AARCH64 to address it. This is a preparation for following patches in ilp32 patchset. For consistency, SET_PERSONALITY is changed here

[PATCH 20/23] arm64: signal32: move ilp32 and aarch32 common code to separated file

Signed-off-by: Yury Norov --- arch/arm64/include/asm/signal32_common.h | 25 +++ arch/arm64/kernel/Makefile | 1 + arch/arm64/kernel/signal32.c | 85 --- arch/arm64/kernel/signal32_common.c | 115 +++ 4 files

Re: [PATCH] xen/privcmd: use vma_pages().

On Mon, May 23, 2016 at 04:26:37PM -0400, Boris Ostrovsky wrote: > On 05/21/2016 09:09 AM, Muhammad Falak R Wani wrote: > > Replace explicit computation of vma page count by a call to > > vma_pages() > > > > Can you combine all three patches into a single one? > > Thanks. > -boris > Sure, I

Re: [PATCH] xen/privcmd: use vma_pages().

On Mon, May 23, 2016 at 04:26:37PM -0400, Boris Ostrovsky wrote: > On 05/21/2016 09:09 AM, Muhammad Falak R Wani wrote: > > Replace explicit computation of vma page count by a call to > > vma_pages() > > > > Can you combine all three patches into a single one? > > Thanks. > -boris > Sure, I

[PATCH 12/23] thread: move thread bits accessors to separated file

They may be accessed from low-level code, so isolating is a measure to avoid circular dependencies in header files. The exact reason for circular dependency is WARN_ON() macro added by Al Viro in patch [edd63a27] "set_restore_sigmask() is never called without SIGPENDING (and never should be)"

[PATCH 09/23] arm64: ensure the kernel is compiled for LP64

From: Andrew Pinski The kernel needs to be compiled as a LP64 binary for ARM64, even when using a compiler that defaults to code-generation for the ILP32 ABI. Consequently, we need to explicitly pass '-mabi=lp64' (supported on gcc-4.9 and newer). Signed-off-by: Andrew Pinski

[PATCH 12/23] thread: move thread bits accessors to separated file

They may be accessed from low-level code, so isolating is a measure to avoid circular dependencies in header files. The exact reason for circular dependency is WARN_ON() macro added by Al Viro in patch [edd63a27] "set_restore_sigmask() is never called without SIGPENDING (and never should be)"

[PATCH 09/23] arm64: ensure the kernel is compiled for LP64

From: Andrew Pinski The kernel needs to be compiled as a LP64 binary for ARM64, even when using a compiler that defaults to code-generation for the ILP32 ABI. Consequently, we need to explicitly pass '-mabi=lp64' (supported on gcc-4.9 and newer). Signed-off-by: Andrew Pinski Signed-off-by:

[PATCH 21/23] arm64: ilp32: introduce ilp32-specific handlers for sigframe and ucontext

From: Andrew Pinski ILP32 uses AARCH32 compat structures and syscall handlers for signals. But ILP32 struct rt_sigframe and ucontext differs from both LP64 and AARCH32. So some specific mechanism is needed to take care of it. Signed-off-by: Andrew Pinski

[PATCH 19/23] arm64: signal: share lp64 signal routines to ilp32

After that, it will be possible to reuse it in ilp32. Signed-off-by: Yury Norov --- arch/arm64/include/asm/signal_common.h | 33 arch/arm64/kernel/signal.c | 91 +- 2 files changed, 90 insertions(+), 34

[PATCH 23/23] arm64:ilp32: add ARM64_ILP32 to Kconfig

From: Andrew Pinski This patch adds the config option for ILP32. Signed-off-by: Andrew Pinski Signed-off-by: Philipp Tomsich Signed-off-by: Christoph Muellner

[PATCH 16/23] arm64: ilp32: introduce binfmt_ilp32.c

to handle ILP32 binaries Signed-off-by: Yury Norov --- arch/arm64/kernel/Makefile | 1 + arch/arm64/kernel/binfmt_ilp32.c | 91 2 files changed, 92 insertions(+) create mode 100644 arch/arm64/kernel/binfmt_ilp32.c diff

[PATCH 22/23] arm64:ilp32: add vdso-ilp32 and use for signal return

From: Philipp Tomsich ILP32 VDSO exports next symbols: __kernel_rt_sigreturn; __kernel_gettimeofday; __kernel_clock_gettime; __kernel_clock_getres; What shared object to use, kernel selects depending on result of is_ilp32_compat_task() in

[PATCH 11/23] arm64:uapi: set __BITS_PER_LONG correctly for ILP32 and LP64

From: Andrew Pinski Define __BITS_PER_LONG depending on the ABI used (i.e. check whether __ILP32__ or __LP64__ is defined). This is necessary for glibc to determine the appropriate type definitions for the system call interface. Signed-off-by: Andrew Pinski

[PATCH 21/23] arm64: ilp32: introduce ilp32-specific handlers for sigframe and ucontext

From: Andrew Pinski ILP32 uses AARCH32 compat structures and syscall handlers for signals. But ILP32 struct rt_sigframe and ucontext differs from both LP64 and AARCH32. So some specific mechanism is needed to take care of it. Signed-off-by: Andrew Pinski Signed-off-by: Yury Norov ---

[PATCH 19/23] arm64: signal: share lp64 signal routines to ilp32

After that, it will be possible to reuse it in ilp32. Signed-off-by: Yury Norov --- arch/arm64/include/asm/signal_common.h | 33 arch/arm64/kernel/signal.c | 91 +- 2 files changed, 90 insertions(+), 34 deletions(-) create mode 100644

[PATCH 23/23] arm64:ilp32: add ARM64_ILP32 to Kconfig

From: Andrew Pinski This patch adds the config option for ILP32. Signed-off-by: Andrew Pinski Signed-off-by: Philipp Tomsich Signed-off-by: Christoph Muellner Signed-off-by: Yury Norov Reviewed-by: David Daney --- arch/arm64/Kconfig | 12 +++- 1 file changed, 11 insertions(+), 1

[PATCH 16/23] arm64: ilp32: introduce binfmt_ilp32.c

to handle ILP32 binaries Signed-off-by: Yury Norov --- arch/arm64/kernel/Makefile | 1 + arch/arm64/kernel/binfmt_ilp32.c | 91 2 files changed, 92 insertions(+) create mode 100644 arch/arm64/kernel/binfmt_ilp32.c diff --git

[PATCH 22/23] arm64:ilp32: add vdso-ilp32 and use for signal return

From: Philipp Tomsich ILP32 VDSO exports next symbols: __kernel_rt_sigreturn; __kernel_gettimeofday; __kernel_clock_gettime; __kernel_clock_getres; What shared object to use, kernel selects depending on result of is_ilp32_compat_task() in arch/arm64/kernel/vdso.c, so it substitutes correct

[PATCH 11/23] arm64:uapi: set __BITS_PER_LONG correctly for ILP32 and LP64

From: Andrew Pinski Define __BITS_PER_LONG depending on the ABI used (i.e. check whether __ILP32__ or __LP64__ is defined). This is necessary for glibc to determine the appropriate type definitions for the system call interface. Signed-off-by: Andrew Pinski Signed-off-by: Philipp Tomsich

[PATCH 08/23] arm64: ilp32: add documentation on the ILP32 ABI for ARM64

Based on Andrew Pinski's patch-series. Signed-off-by: Yury Norov --- Documentation/arm64/ilp32.txt | 25 + 1 file changed, 25 insertions(+) create mode 100644 Documentation/arm64/ilp32.txt diff --git a/Documentation/arm64/ilp32.txt

[PATCH 08/23] arm64: ilp32: add documentation on the ILP32 ABI for ARM64

Based on Andrew Pinski's patch-series. Signed-off-by: Yury Norov --- Documentation/arm64/ilp32.txt | 25 + 1 file changed, 25 insertions(+) create mode 100644 Documentation/arm64/ilp32.txt diff --git a/Documentation/arm64/ilp32.txt b/Documentation/arm64/ilp32.txt new

[PATCH 03/23] all: s390: move wrapper infrastructure to generic headers

This patch moves required calls to generic files to let other arches use it if needed. Here also, additional code is introduced, as s390 uses asm syscall tables, while in general case, wrappers may be used in C code. __SC_COMPAT_CAST for s390 is too specific due to 31-bit pointer length, so it's

[PATCH 06/23] compat ABI: use non-compat openat and open_by_handle_at variants

The only difference is that non-compat version forces O_LARGEFILE, and it should be the default behaviour for all architectures, as we don't support 32-bit off_t. The only exception is tile32, that continues with compat version of syscalls. Signed-off-by: Yury Norov

[PATCH 01/23] all: syscall wrappers: add documentation

Signed-off-by: Yury Norov --- Documentation/adding-syscalls.txt | 32 1 file changed, 32 insertions(+) diff --git a/Documentation/adding-syscalls.txt b/Documentation/adding-syscalls.txt index cc2d4ac..d02a6bd 100644 ---

[PATCH 01/23] all: syscall wrappers: add documentation

Signed-off-by: Yury Norov --- Documentation/adding-syscalls.txt | 32 1 file changed, 32 insertions(+) diff --git a/Documentation/adding-syscalls.txt b/Documentation/adding-syscalls.txt index cc2d4ac..d02a6bd 100644 --- a/Documentation/adding-syscalls.txt +++

[PATCH 03/23] all: s390: move wrapper infrastructure to generic headers

This patch moves required calls to generic files to let other arches use it if needed. Here also, additional code is introduced, as s390 uses asm syscall tables, while in general case, wrappers may be used in C code. __SC_COMPAT_CAST for s390 is too specific due to 31-bit pointer length, so it's

[PATCH 06/23] compat ABI: use non-compat openat and open_by_handle_at variants

The only difference is that non-compat version forces O_LARGEFILE, and it should be the default behaviour for all architectures, as we don't support 32-bit off_t. The only exception is tile32, that continues with compat version of syscalls. Signed-off-by: Yury Norov Acked-by: Arnd Bergmann

[PATCH v2] xen: use vma_pages().

Replace explicit computation of vma page count by a call to vma_pages(). Signed-off-by: Muhammad Falak R Wani --- drivers/xen/gntalloc.c | 2 +- drivers/xen/gntdev.c | 2 +- drivers/xen/privcmd.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH v2] xen: use vma_pages().

Replace explicit computation of vma page count by a call to vma_pages(). Signed-off-by: Muhammad Falak R Wani --- drivers/xen/gntalloc.c | 2 +- drivers/xen/gntdev.c | 2 +- drivers/xen/privcmd.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/xen/gntalloc.c

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