Re: [RFC PATCH 1/1] mm/percpu.c: fix memory leakage issue when allocate a odd alignment area

On 10/12/2016 02:53 PM, Michal Hocko wrote: > On Wed 12-10-16 08:28:17, zijun_hu wrote: >> On 2016/10/12 1:22, Michal Hocko wrote: >>> On Tue 11-10-16 21:24:50, zijun_hu wrote: From: zijun_hu the LSB of a chunk->map element is used for free/in-use flag of a area

Re: [RFC PATCH 1/1] mm/percpu.c: fix memory leakage issue when allocate a odd alignment area

On 10/12/2016 02:53 PM, Michal Hocko wrote: > On Wed 12-10-16 08:28:17, zijun_hu wrote: >> On 2016/10/12 1:22, Michal Hocko wrote: >>> On Tue 11-10-16 21:24:50, zijun_hu wrote: From: zijun_hu the LSB of a chunk->map element is used for free/in-use flag of a area and the other

Re: [PATCH v2 4/4] mm: make unreserve highatomic functions reliable

On 10/12/2016 07:33 AM, Minchan Kim wrote: Currently, unreserve_highatomic_pageblock bails out if it found highatomic pageblock regardless of really moving free pages from the one so that it could mitigate unreserve logic's goal which saves OOM of a process. This patch makes unreserve functions

Re: [PATCH v2 4/4] mm: make unreserve highatomic functions reliable

On 10/12/2016 07:33 AM, Minchan Kim wrote: Currently, unreserve_highatomic_pageblock bails out if it found highatomic pageblock regardless of really moving free pages from the one so that it could mitigate unreserve logic's goal which saves OOM of a process. This patch makes unreserve functions

Re: [PATCH v2 3/4] mm: try to exhaust highatomic reserve before the OOM

On 10/12/2016 07:33 AM, Minchan Kim wrote: It's weird to show that zone has enough free memory above min watermark but OOMed with 4K GFP_KERNEL allocation due to reserved highatomic pages. As last resort, try to unreserve highatomic pages again and if it has moved pages to non-highatmoc free

Re: [PATCH v2 3/4] mm: try to exhaust highatomic reserve before the OOM

On 10/12/2016 07:33 AM, Minchan Kim wrote: It's weird to show that zone has enough free memory above min watermark but OOMed with 4K GFP_KERNEL allocation due to reserved highatomic pages. As last resort, try to unreserve highatomic pages again and if it has moved pages to non-highatmoc free

Re: [mm] c4344e8035: WARNING: CPU: 0 PID: 101 at mm/memory.c:303 __tlb_remove_page_size+0x25/0x99

On 10/12, Aneesh Kumar K.V wrote: >kernel test robot <xiaolong...@intel.com> writes: > >> FYI, we noticed the following commit: >> >> https://github.com/0day-ci/linux >> Aneesh-Kumar-K-V/mm-Use-the-correct-page-size-when-removin

Re: [mm] c4344e8035: WARNING: CPU: 0 PID: 101 at mm/memory.c:303 __tlb_remove_page_size+0x25/0x99

On 10/12, Aneesh Kumar K.V wrote: >kernel test robot writes: > >> FYI, we noticed the following commit: >> >> https://github.com/0day-ci/linux >> Aneesh-Kumar-K-V/mm-Use-the-correct-page-size-when-removing-the-page/20161012-013446 >> commit c4344e80359420d75

Re: [PATCH 1/2] driver core: skip removal test for non-removable drivers

Hi Rob, On 10/11/16 20:41, Rob Herring wrote: > Some drivers do not support removal/unbinding. These drivers should have > drv->suppress_bind_attrs set to true, so use that to skip the removal > test. > > This doesn't fix anything reported so far, but should prevent some other > cases. Some

Re: [PATCH 1/2] driver core: skip removal test for non-removable drivers

Hi Rob, On 10/11/16 20:41, Rob Herring wrote: > Some drivers do not support removal/unbinding. These drivers should have > drv->suppress_bind_attrs set to true, so use that to skip the removal > test. > > This doesn't fix anything reported so far, but should prevent some other > cases. Some

Re: [PATCH v3 07/11] arm64/tracing: fix compat syscall handling

Hi Will, On 11.10.2016 15:36, Will Deacon wrote: On Tue, Oct 11, 2016 at 12:42:52PM +0200, Marcin Nowakowski wrote: Add arch_syscall_addr for arm64 and define NR_compat_syscalls, as the number of compat syscalls for arm64 exceeds the number defined by NR_syscalls. Signed-off-by: Marcin

Re: [PATCH v3 07/11] arm64/tracing: fix compat syscall handling

Hi Will, On 11.10.2016 15:36, Will Deacon wrote: On Tue, Oct 11, 2016 at 12:42:52PM +0200, Marcin Nowakowski wrote: Add arch_syscall_addr for arm64 and define NR_compat_syscalls, as the number of compat syscalls for arm64 exceeds the number defined by NR_syscalls. Signed-off-by: Marcin

Re: [PATCH 00/44] Convert FibreChannel bsg code to use bsg-lib

On Tue, Oct 11, 2016 at 09:49:38AM -0700, Christoph Hellwig wrote: > Hi Johannes, > > this looks great to me. But is there a chance to consolidate it into > a more manageable set of patches? E.g. all the patches to call > export fc_bsg_jobdone, use it directly and remove the function pointer >

Re: [PATCH 00/44] Convert FibreChannel bsg code to use bsg-lib

On Tue, Oct 11, 2016 at 09:49:38AM -0700, Christoph Hellwig wrote: > Hi Johannes, > > this looks great to me. But is there a chance to consolidate it into > a more manageable set of patches? E.g. all the patches to call > export fc_bsg_jobdone, use it directly and remove the function pointer >

Re: [PATCH] gpio: pca953x: add a comment explaining the need for a lockdep subclass

On Mon, Sep 26, 2016 at 11:54:15AM +0200, Bartosz Golaszewski wrote: > This is a follow-up to commit 559b46990e76 ("gpio: pca953x: fix an > incorrect lockdep warning"). The reason for calling > lockdep_set_subclass() in pca953x_probe() is not explained in > the code. > > Add a comment describing

Re: [PATCH] gpio: pca953x: add a comment explaining the need for a lockdep subclass

On Mon, Sep 26, 2016 at 11:54:15AM +0200, Bartosz Golaszewski wrote: > This is a follow-up to commit 559b46990e76 ("gpio: pca953x: fix an > incorrect lockdep warning"). The reason for calling > lockdep_set_subclass() in pca953x_probe() is not explained in > the code. > > Add a comment describing

Re: [PATCH] iwlwifi: pcie: reduce "unsupported splx" to a warning

Hi Chris, On Tue, 2016-10-11 at 09:09 -0500, Chris Rorvick wrote: > On Tue, Oct 11, 2016 at 5:11 AM, Paul Bolle wrote: > > > This is not coming from the NIC itself, but from the platform's ACPI > > > tables. Can you tell us which platform you are using? > > > Interesting.

Re: [PATCH] iwlwifi: pcie: reduce "unsupported splx" to a warning

Hi Chris, On Tue, 2016-10-11 at 09:09 -0500, Chris Rorvick wrote: > On Tue, Oct 11, 2016 at 5:11 AM, Paul Bolle wrote: > > > This is not coming from the NIC itself, but from the platform's ACPI > > > tables. Can you tell us which platform you are using? > > > Interesting. I'm running a Dell

Re: [RFC PATCH 00/11] Introduce writeback connectors

On Tue, Oct 11, 2016 at 10:24:23PM +0100, Brian Starkey wrote: > On Tue, Oct 11, 2016 at 10:02:43PM +0200, Daniel Vetter wrote: > > The problem with just that is that there's lots of different things > > that can feed into the overall needs_modeset variable. That's why we > > split it up into

Re: [RFC PATCH 00/11] Introduce writeback connectors

On Tue, Oct 11, 2016 at 10:24:23PM +0100, Brian Starkey wrote: > On Tue, Oct 11, 2016 at 10:02:43PM +0200, Daniel Vetter wrote: > > The problem with just that is that there's lots of different things > > that can feed into the overall needs_modeset variable. That's why we > > split it up into

[PATCH v8 5/6] mfd: lpc_ich: Add Device IDs for Intel Apollo Lake PCH

Adding Intel codename Apollo Lake platform device IDs for PCH. Signed-off-by: Tan Jui Nee --- Changes in V8: - No change drivers/mfd/lpc_ich_core.c | 6 ++ include/linux/mfd/lpc_ich.h | 1 + 2 files changed, 7 insertions(+) diff --git

[PATCH v8 5/6] mfd: lpc_ich: Add Device IDs for Intel Apollo Lake PCH

Adding Intel codename Apollo Lake platform device IDs for PCH. Signed-off-by: Tan Jui Nee --- Changes in V8: - No change drivers/mfd/lpc_ich_core.c | 6 ++ include/linux/mfd/lpc_ich.h | 1 + 2 files changed, 7 insertions(+) diff --git a/drivers/mfd/lpc_ich_core.c

[PATCH v8 3/6] x86/intel-ivi: Add Intel In-Vehicle Infotainment (IVI) systems used in cars support

Add support for non ACPI system, such as system that uses Advanced Boot Loader (ABL) whereby a platform device has to be created in order to bind with PINCTRL/GPIO. At the moment, Intel Apollo Lake SoC requires P2SB driver to hide and unhide P2SB to lookup P2SB BAR and pass the PCI BAR address to

[PATCH v8 4/6] mfd: move enum lpc_chipsets into lpc_ich.h

Move the enum's definition into a standalone header file which can be used wherever its definition is needed. Signed-off-by: Tan Jui Nee --- Changes in V8: - No change drivers/mfd/lpc_ich_core.c | 71 -

Re: igb driver can cause cache invalidation of non-owned memory?

>>> The main reason why this isn't a concern for the igb driver is because >>> we currently pass the page up as read-only. We don't allow the stack >>> to write into the page by keeping the page count greater than 1 which >>> means that the page is shared. It isn't until we unmap the page that

Re: [PATCH v6] net: ip, diag -- Add diag interface for raw sockets

On Wed, Oct 12, 2016 at 01:50:22AM -0400, David Miller wrote: > > Macros that look like function calls and are also lvalues tend to be > troublesome. > > I know what you're trying to achieve, you want a named way to access > this so that the intent and semantics are clear. > > But I'd rather

Re: [PATCH 2/4] mm: prevent double decrease of nr_reserved_highatomic

On Fri, Oct 07, 2016 at 02:45:34PM +0900, Minchan Kim wrote: > There is race between page freeing and unreserved highatomic. > > CPU 0CPU 1 > > free_hot_cold_page > mt = get_pfnblock_migratetype > set_pcppage_migratetype(page, mt) >

[PATCH v8 6/6] mfd: lpc_ich: Add support for Intel Apollo Lake GPIO pinctrl in non-ACPI system

This driver uses the P2SB hide/unhide mechanism cooperatively to pass the PCI BAR address to the gpio platform driver. Signed-off-by: Tan Jui Nee --- Changes in V8: - Rename source file lpc_ich-apl.c to lpc_ich_apl.c (suggested by Mika). Changes in V7: -

[PATCH v8 3/6] x86/intel-ivi: Add Intel In-Vehicle Infotainment (IVI) systems used in cars support

Add support for non ACPI system, such as system that uses Advanced Boot Loader (ABL) whereby a platform device has to be created in order to bind with PINCTRL/GPIO. At the moment, Intel Apollo Lake SoC requires P2SB driver to hide and unhide P2SB to lookup P2SB BAR and pass the PCI BAR address to

[PATCH v8 4/6] mfd: move enum lpc_chipsets into lpc_ich.h

Move the enum's definition into a standalone header file which can be used wherever its definition is needed. Signed-off-by: Tan Jui Nee --- Changes in V8: - No change drivers/mfd/lpc_ich_core.c | 71 - include/linux/mfd/lpc_ich.h | 71

Re: igb driver can cause cache invalidation of non-owned memory?

>>> The main reason why this isn't a concern for the igb driver is because >>> we currently pass the page up as read-only. We don't allow the stack >>> to write into the page by keeping the page count greater than 1 which >>> means that the page is shared. It isn't until we unmap the page that

Re: [PATCH v6] net: ip, diag -- Add diag interface for raw sockets

On Wed, Oct 12, 2016 at 01:50:22AM -0400, David Miller wrote: > > Macros that look like function calls and are also lvalues tend to be > troublesome. > > I know what you're trying to achieve, you want a named way to access > this so that the intent and semantics are clear. > > But I'd rather

Re: [PATCH 2/4] mm: prevent double decrease of nr_reserved_highatomic

On Fri, Oct 07, 2016 at 02:45:34PM +0900, Minchan Kim wrote: > There is race between page freeing and unreserved highatomic. > > CPU 0CPU 1 > > free_hot_cold_page > mt = get_pfnblock_migratetype > set_pcppage_migratetype(page, mt) >

[PATCH v8 6/6] mfd: lpc_ich: Add support for Intel Apollo Lake GPIO pinctrl in non-ACPI system

This driver uses the P2SB hide/unhide mechanism cooperatively to pass the PCI BAR address to the gpio platform driver. Signed-off-by: Tan Jui Nee --- Changes in V8: - Rename source file lpc_ich-apl.c to lpc_ich_apl.c (suggested by Mika). Changes in V7: - Add author information

[PATCH RFC V2 2/2] KVM: x86: Support using the VMX preemption timer for APIC Timer periodic/oneshot mode

From: Wanpeng Li Most windows guests still utilize APIC Timer periodic/oneshot mode instead of tsc-deadline mode, and the APIC Timer periodic/oneshot mode are still emulated by high overhead hrtimer on host. This patch converts the expected expire time of the

[PATCH RFC V2 1/2] KVM: lapic: introduce start_sw_period() to handle oneshot/periodic mode

From: Wanpeng Li Extract start_sw_period() to handle periodic/oneshot mode, it will be used by later patch. Cc: Paolo Bonzini Cc: Radim Krčmář Cc: Yunhong Jiang Signed-off-by: Wanpeng Li

Re: [RFC PATCH 1/1] mm/percpu.c: fix memory leakage issue when allocate a odd alignment area

On Wed 12-10-16 08:28:17, zijun_hu wrote: > On 2016/10/12 1:22, Michal Hocko wrote: > > On Tue 11-10-16 21:24:50, zijun_hu wrote: > >> From: zijun_hu > >> > >> the LSB of a chunk->map element is used for free/in-use flag of a area > >> and the other bits for offset, the

[PATCH RFC V2 2/2] KVM: x86: Support using the VMX preemption timer for APIC Timer periodic/oneshot mode

From: Wanpeng Li Most windows guests still utilize APIC Timer periodic/oneshot mode instead of tsc-deadline mode, and the APIC Timer periodic/oneshot mode are still emulated by high overhead hrtimer on host. This patch converts the expected expire time of the periodic/oneshot mode to guest

[PATCH RFC V2 1/2] KVM: lapic: introduce start_sw_period() to handle oneshot/periodic mode

From: Wanpeng Li Extract start_sw_period() to handle periodic/oneshot mode, it will be used by later patch. Cc: Paolo Bonzini Cc: Radim Krčmář Cc: Yunhong Jiang Signed-off-by: Wanpeng Li --- arch/x86/kvm/lapic.c | 89 +++- 1 file changed, 47

Re: [RFC PATCH 1/1] mm/percpu.c: fix memory leakage issue when allocate a odd alignment area

On Wed 12-10-16 08:28:17, zijun_hu wrote: > On 2016/10/12 1:22, Michal Hocko wrote: > > On Tue 11-10-16 21:24:50, zijun_hu wrote: > >> From: zijun_hu > >> > >> the LSB of a chunk->map element is used for free/in-use flag of a area > >> and the other bits for offset, the sufficient and necessary

[PATCH v8 0/6] inctrl/broxton: enable platform device in the absent of ACPI enumeration

Hi, The patches are to cater the need for non-ACPI system whereby a platform device has to be created in order to bind with Apollo Lake Pinctrl GPIO platform driver. The MMIO BAR is accessed over the Primary to Sideband bridge (P2SB). Since the BIOS prevents the P2SB device from being enumerated

[PATCH RFC V2 0/2] KVM: x86: Support using the VMX preemption timer for APIC Timer periodic/oneshot mode

Most windows guests which I have on hand currently still utilize APIC Timer periodic/oneshot mode instead of APIC Timer tsc-deadline mode: - windows 2008 server r2 - windows 2012 server r2 - windows 7 - windows 10 This patchset adds the support using the VMX preemption timer for APIC Timer

[PATCH v8 0/6] inctrl/broxton: enable platform device in the absent of ACPI enumeration

Hi, The patches are to cater the need for non-ACPI system whereby a platform device has to be created in order to bind with Apollo Lake Pinctrl GPIO platform driver. The MMIO BAR is accessed over the Primary to Sideband bridge (P2SB). Since the BIOS prevents the P2SB device from being enumerated

[PATCH RFC V2 0/2] KVM: x86: Support using the VMX preemption timer for APIC Timer periodic/oneshot mode

Most windows guests which I have on hand currently still utilize APIC Timer periodic/oneshot mode instead of APIC Timer tsc-deadline mode: - windows 2008 server r2 - windows 2012 server r2 - windows 7 - windows 10 This patchset adds the support using the VMX preemption timer for APIC Timer

Re: [PATCH] iwlwifi: pcie: reduce "unsupported splx" to a warning

Luca, On Wed, 2016-10-12 at 09:11 +0300, Luca Coelho wrote: > By "platform" I meant the PC you are using.  The ACPI table is created > by the OEM, so different PCs have different tables. Like Chris I use a Dell XPS 13 (9350), but mine came with an AC 8260 out of it's assembly plant:     Detected

Re: [PATCH] iwlwifi: pcie: reduce "unsupported splx" to a warning

Luca, On Wed, 2016-10-12 at 09:11 +0300, Luca Coelho wrote: > By "platform" I meant the PC you are using.  The ACPI table is created > by the OEM, so different PCs have different tables. Like Chris I use a Dell XPS 13 (9350), but mine came with an AC 8260 out of it's assembly plant:     Detected

[PATCH v8 1/6] x86/platform/p2sb: New Primary to Sideband bridge support driver for Intel SOC's

From: Andy Shevchenko There is already one and at least one more user coming which require an access to Primary to Sideband bridge (P2SB) in order to get IO or MMIO bar hidden by BIOS. Create a driver to access P2SB for x86 devices. Signed-off-by: Yong,

[PATCH v8 2/6] mfd: lpc_ich: Rename lpc-ich driver

This patch follows the example of mfd/wm831x to rename the driver from "lpc_ich" to "lpc_ich_core". Signed-off-by: Tan Jui Nee --- Changes in V8: - Update new file name with lpc_ich_core.c at description of source file. - Rework Makefile with new source

[PATCH v8 1/6] x86/platform/p2sb: New Primary to Sideband bridge support driver for Intel SOC's

From: Andy Shevchenko There is already one and at least one more user coming which require an access to Primary to Sideband bridge (P2SB) in order to get IO or MMIO bar hidden by BIOS. Create a driver to access P2SB for x86 devices. Signed-off-by: Yong, Jonathan Signed-off-by: Andy Shevchenko

[PATCH v8 2/6] mfd: lpc_ich: Rename lpc-ich driver

This patch follows the example of mfd/wm831x to rename the driver from "lpc_ich" to "lpc_ich_core". Signed-off-by: Tan Jui Nee --- Changes in V8: - Update new file name with lpc_ich_core.c at description of source file. - Rework Makefile with new source file name lpc_ich_apl.c.

Re: [PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate".

On Wed, Oct 12, 2016 at 03:08:24AM +, Sun, Jing A wrote: > Interestingly, I am able to reload i915 and drm. Our CI has tests for > i915 unload/reload, but does not check drm. In any case the config > problem should not impact the reloadability of i915. > == > Sorry that I didn't make

Re: [PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate".

On Wed, Oct 12, 2016 at 03:08:24AM +, Sun, Jing A wrote: > Interestingly, I am able to reload i915 and drm. Our CI has tests for > i915 unload/reload, but does not check drm. In any case the config > problem should not impact the reloadability of i915. > == > Sorry that I didn't make

Re: [PATCH v1 00/10] *** imx-sdma: misc fix ***

Hello Are there any comments for this patch set? Thanks, Jiada On 05/17/2016 12:48 PM, Jiada Wang wrote: this patch set contains the following changes 1. fix issues in cyclic dma 2. add support to SYNC DMA termination 3. avoid system hang, when SDMA channel 0 timeouts 4. add lock to prevent

Re: [PATCH v1 00/10] *** imx-sdma: misc fix ***

Hello Are there any comments for this patch set? Thanks, Jiada On 05/17/2016 12:48 PM, Jiada Wang wrote: this patch set contains the following changes 1. fix issues in cyclic dma 2. add support to SYNC DMA termination 3. avoid system hang, when SDMA channel 0 timeouts 4. add lock to prevent

Re: [PATCHv3 13/41] truncate: make sure invalidate_mapping_pages() can discard huge pages

On Wed 12-10-16 00:53:49, Kirill A. Shutemov wrote: > On Tue, Oct 11, 2016 at 05:58:15PM +0200, Jan Kara wrote: > > On Thu 15-09-16 14:54:55, Kirill A. Shutemov wrote: > > > invalidate_inode_page() has expectation about page_count() of the page > > > -- if it's not 2 (one to caller, one to

Re: [PATCHv3 13/41] truncate: make sure invalidate_mapping_pages() can discard huge pages

On Wed 12-10-16 00:53:49, Kirill A. Shutemov wrote: > On Tue, Oct 11, 2016 at 05:58:15PM +0200, Jan Kara wrote: > > On Thu 15-09-16 14:54:55, Kirill A. Shutemov wrote: > > > invalidate_inode_page() has expectation about page_count() of the page > > > -- if it's not 2 (one to caller, one to

Re: [PATCH 6/6] cpufreq: pxa: convert to clock API

On 12-10-16, 08:22, Robert Jarzmik wrote: > Viresh Kumar writes: > > > On 10-10-16, 22:09, Robert Jarzmik wrote: > >> As the clock settings have been introduced into the clock pxa drivers, > >> which are now available to change the CPU clock by themselves, remove > >>

Re: [PATCH 6/6] cpufreq: pxa: convert to clock API

On 12-10-16, 08:22, Robert Jarzmik wrote: > Viresh Kumar writes: > > > On 10-10-16, 22:09, Robert Jarzmik wrote: > >> As the clock settings have been introduced into the clock pxa drivers, > >> which are now available to change the CPU clock by themselves, remove > >> the clock handling from

Re: [PATCH 6/6] cpufreq: pxa: convert to clock API

Viresh Kumar writes: > On 10-10-16, 22:09, Robert Jarzmik wrote: >> As the clock settings have been introduced into the clock pxa drivers, >> which are now available to change the CPU clock by themselves, remove >> the clock handling from this driver, and rely on pxa

Re: [PATCH 6/6] cpufreq: pxa: convert to clock API

Viresh Kumar writes: > On 10-10-16, 22:09, Robert Jarzmik wrote: >> As the clock settings have been introduced into the clock pxa drivers, >> which are now available to change the CPU clock by themselves, remove >> the clock handling from this driver, and rely on pxa clock drivers. >> >>

[patch] drm/amdgpu: potential NULL dereference in debugfs code

debugfs_create_file() returns NULL on error, it only returns error pointers if debugfs isn't enabled in the config and we checked for that earlier so it can't happen. Fixes: 4f4824b55650 ('drm/amd/amdgpu: Convert ring debugfs entries to binary') Signed-off-by: Dan Carpenter

[patch] drm/amdgpu: potential NULL dereference in debugfs code

debugfs_create_file() returns NULL on error, it only returns error pointers if debugfs isn't enabled in the config and we checked for that earlier so it can't happen. Fixes: 4f4824b55650 ('drm/amd/amdgpu: Convert ring debugfs entries to binary') Signed-off-by: Dan Carpenter diff --git

Re: [PATCH] iwlwifi: pcie: reduce "unsupported splx" to a warning

Hi Paul, On Tue, 2016-10-11 at 12:11 +0200, Paul Bolle wrote: > On Mon, 2016-10-10 at 17:02 +0300, Luca Coelho wrote: > > On Mon, 2016-10-10 at 02:19 -0500, Chris Rorvick wrote: > > This is not coming from the NIC itself, but from the platform's ACPI > > tables.  Can you tell us which platform you

Re: [PATCH] iwlwifi: pcie: reduce "unsupported splx" to a warning

Hi Paul, On Tue, 2016-10-11 at 12:11 +0200, Paul Bolle wrote: > On Mon, 2016-10-10 at 17:02 +0300, Luca Coelho wrote: > > On Mon, 2016-10-10 at 02:19 -0500, Chris Rorvick wrote: > > This is not coming from the NIC itself, but from the platform's ACPI > > tables.  Can you tell us which platform you

Re: [PATCH 32/41] staging: lustre: llite: restart short read/write for normal IO

On Wed, Oct 12, 2016 at 12:22:35AM +0100, James Simmons wrote: > > > On Sun, Oct 02, 2016 at 10:28:28PM -0400, James Simmons wrote: > > > From: Bobi Jam > > > > > > If normal IO got short read/write, we'd restart the IO from where > > > we've accomplished until we meet EOF

Re: [PATCH 32/41] staging: lustre: llite: restart short read/write for normal IO

On Wed, Oct 12, 2016 at 12:22:35AM +0100, James Simmons wrote: > > > On Sun, Oct 02, 2016 at 10:28:28PM -0400, James Simmons wrote: > > > From: Bobi Jam > > > > > > If normal IO got short read/write, we'd restart the IO from where > > > we've accomplished until we meet EOF or error happens. > >

Re: [PATCH] drivers: staging: greybus: audio_topology.c: Fixed CHECKS for brace issues

On Wed, Oct 12, 2016 at 5:19 AM, Chase Metzger wrote: > Added braces for else and else if statements where checkpatch complained. > > Signed-off-by: Chase Metzger > --- > drivers/staging/greybus/audio_topology.c | 7 +-- > 1 file changed,

Re: [PATCH] drivers: staging: greybus: audio_topology.c: Fixed CHECKS for brace issues

On Wed, Oct 12, 2016 at 5:19 AM, Chase Metzger wrote: > Added braces for else and else if statements where checkpatch complained. > > Signed-off-by: Chase Metzger > --- > drivers/staging/greybus/audio_topology.c | 7 +-- > 1 file changed, 5 insertions(+), 2 deletions(-) > > diff --git

[PATCH 0/4] ARM64: More flexible HW watchpoint

Currently, we do not support all the byte select option provided by ARM64 specs for a HW watchpoint. This patch set will help user to instrument a watchpoint with all possible byte select options. Pratyush Anand (4): hw_breakpoint: Allow watchpoint of length 3,5,6 and 7 arm64: Allow hw

[PATCH 0/4] ARM64: More flexible HW watchpoint

Currently, we do not support all the byte select option provided by ARM64 specs for a HW watchpoint. This patch set will help user to instrument a watchpoint with all possible byte select options. Pratyush Anand (4): hw_breakpoint: Allow watchpoint of length 3,5,6 and 7 arm64: Allow hw

Re: [PATCH] strparser: Propagate correct error code in strp_recv()

From: Geert Uytterhoeven Date: Thu, 6 Oct 2016 15:41:49 +0200 > With m68k-linux-gnu-gcc-4.1: > > net/strparser/strparser.c: In function ‘strp_recv’: > net/strparser/strparser.c:98: warning: ‘err’ may be used uninitialized in > this function > > Pass "len" (which

Re: [PATCH] strparser: Propagate correct error code in strp_recv()

From: Geert Uytterhoeven Date: Thu, 6 Oct 2016 15:41:49 +0200 > With m68k-linux-gnu-gcc-4.1: > > net/strparser/strparser.c: In function ‘strp_recv’: > net/strparser/strparser.c:98: warning: ‘err’ may be used uninitialized in > this function > > Pass "len" (which is an error code when

[PATCH 1/4] hw_breakpoint: Allow watchpoint of length 3,5,6 and 7

We only support breakpoint/watchpoint of length 1, 2, 4 and 8. If we can support other length as well, then user may watch more data with less number of watchpoints (provided hardware supports it). For example: if we have to watch only 4th, 5th and 6th byte from a 64 bit aligned address, we will

Re: [PATCH] drivers: staging: greybus: audio_manager_sysfs.c: Fixed CHECK for brace issue

On Wed, Oct 12, 2016 at 4:52 AM, Chase Metzger wrote: > Added braces to else and else if statements where checkpatch complained. > > Signed-off-by: Chase Metzger > --- > drivers/staging/greybus/audio_manager_sysfs.c | 5 +++-- > 1 file

[PATCH 1/4] hw_breakpoint: Allow watchpoint of length 3,5,6 and 7

We only support breakpoint/watchpoint of length 1, 2, 4 and 8. If we can support other length as well, then user may watch more data with less number of watchpoints (provided hardware supports it). For example: if we have to watch only 4th, 5th and 6th byte from a 64 bit aligned address, we will

Re: [PATCH] drivers: staging: greybus: audio_manager_sysfs.c: Fixed CHECK for brace issue

On Wed, Oct 12, 2016 at 4:52 AM, Chase Metzger wrote: > Added braces to else and else if statements where checkpatch complained. > > Signed-off-by: Chase Metzger > --- > drivers/staging/greybus/audio_manager_sysfs.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git

[PATCH 4/4] selftests: arm64: add test for unaligned watchpoint address handling

ARM64 hardware expects 64bit aligned address for watchpoint invocation. However, it provides byte selection method to select any number of consecutive byte set within the range of 1-8. This patch adds support to test all such byte selection option for different memory write sizes. Signed-off-by:

[PATCH 2/4] arm64: Allow hw watchpoint at varied offset from base address

ARM64 hardware supports watchpoint at any double word aligned address. However, it can select any consecutive bytes from offset 0 to 7 from that base address. For example, if base address is programmed as 0x420030 and byte select is 0x1C, then access of 0x420032,0x420033 and 0x420034 will generate

[PATCH 4/4] selftests: arm64: add test for unaligned watchpoint address handling

ARM64 hardware expects 64bit aligned address for watchpoint invocation. However, it provides byte selection method to select any number of consecutive byte set within the range of 1-8. This patch adds support to test all such byte selection option for different memory write sizes. Signed-off-by:

[PATCH 2/4] arm64: Allow hw watchpoint at varied offset from base address

ARM64 hardware supports watchpoint at any double word aligned address. However, it can select any consecutive bytes from offset 0 to 7 from that base address. For example, if base address is programmed as 0x420030 and byte select is 0x1C, then access of 0x420032,0x420033 and 0x420034 will generate

[PATCH 3/4] arm64: Allow hw watchpoint of length 3,5,6 and 7

Since, arm64 can support all offset within a double word limit. Therefore, now support other lengths within that range as well. Signed-off-by: Pratyush Anand --- arch/arm64/include/asm/hw_breakpoint.h | 4 arch/arm64/kernel/hw_breakpoint.c | 36

[PATCH 3/4] arm64: Allow hw watchpoint of length 3,5,6 and 7

Since, arm64 can support all offset within a double word limit. Therefore, now support other lengths within that range as well. Signed-off-by: Pratyush Anand --- arch/arm64/include/asm/hw_breakpoint.h | 4 arch/arm64/kernel/hw_breakpoint.c | 36 ++ 2

<    9   10   11   12   13   14