Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP

On Wed, Aug 23, 2017 at 9:22 PM, Sinan Kaya wrote: > Hi Oza, > >> In working Enumuration case I get following: >> [9.125976] pci :00:00.0: bridge configuration invalid ([bus >> 00-00]), re-configuring >> [9.134267] where=0x0 val=0x0001 >> [9.146946]

Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP

On Wed, Aug 23, 2017 at 9:22 PM, Sinan Kaya wrote: > Hi Oza, > >> In working Enumuration case I get following: >> [9.125976] pci :00:00.0: bridge configuration invalid ([bus >> 00-00]), re-configuring >> [9.134267] where=0x0 val=0x0001 >> [9.146946] where=0x0 val=0x0001 >>

Re: gcc-8 objtool warnings

On Wed, Aug 23, 2017 at 03:38:02PM +0200, Arnd Bergmann wrote: > On Wed, Aug 23, 2017 at 2:48 PM, Josh Poimboeuf wrote: > > On Wed, Aug 23, 2017 at 02:22:34PM +0200, Arnd Bergmann wrote: > >> ... > >> > >> : > >>0: e8 00 00 00 00 callq 5

Re: gcc-8 objtool warnings

On Wed, Aug 23, 2017 at 03:38:02PM +0200, Arnd Bergmann wrote: > On Wed, Aug 23, 2017 at 2:48 PM, Josh Poimboeuf wrote: > > On Wed, Aug 23, 2017 at 02:22:34PM +0200, Arnd Bergmann wrote: > >> ... > >> > >> : > >>0: e8 00 00 00 00 callq 5 > >>

Re: [PATCH 1/2] sched/wait: Break up long wake list walk

On 08/23/2017 07:49 AM, Liang, Kan wrote: >> On Tue, Aug 22, 2017 at 12:55 PM, Liang, Kan wrote: >>> So I propose testing the attached trivial patch. >>> >>> It doesn’t work. >>> The call stack is the same. >> >> So I would have expected the stack trace to be the same,

Re: [PATCH 1/2] sched/wait: Break up long wake list walk

On 08/23/2017 07:49 AM, Liang, Kan wrote: >> On Tue, Aug 22, 2017 at 12:55 PM, Liang, Kan wrote: >>> So I propose testing the attached trivial patch. >>> >>> It doesn’t work. >>> The call stack is the same. >> >> So I would have expected the stack trace to be the same, and I would even >>

Re: [PATCH v5 3/4] perf, tools: Add support for printing new mem_info encodings

> so if I find HITM with this flag set I should count it > as remote HITM then? something like attached.. untested You mean for c2c? Yes looks reasonable. -Andi > > thanks, > jirka > > --- > diff --git a/tools/perf/util/mem-events.c b/tools/perf/util/mem-events.c > index

Re: [PATCH v5 3/4] perf, tools: Add support for printing new mem_info encodings

> so if I find HITM with this flag set I should count it > as remote HITM then? something like attached.. untested You mean for c2c? Yes looks reasonable. -Andi > > thanks, > jirka > > --- > diff --git a/tools/perf/util/mem-events.c b/tools/perf/util/mem-events.c > index

Re: [PATCH v3] fbcon: add fbcon=margin: command line option

On 08/23/2017 10:56 AM, Bartlomiej Zolnierkiewicz wrote: Given the standard console palette contains 16 colors, why limit this to the first 8 colors, and not 0 to 15? Good question. I think in some of my previous attempts there was a 0x7 mask involved somewhere and this is a carryover

Re: [PATCH v3] fbcon: add fbcon=margin: command line option

On 08/23/2017 10:56 AM, Bartlomiej Zolnierkiewicz wrote: Given the standard console palette contains 16 colors, why limit this to the first 8 colors, and not 0 to 15? Good question. I think in some of my previous attempts there was a 0x7 mask involved somewhere and this is a carryover

Re: [PATCH V9 2/2] powerpc/nodes: Ensure enough nodes avail for operations

Hi Michael, [auto build test ERROR on powerpc/next] [also build test ERROR on v4.13-rc6 next-20170823] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Michael-Bringmann/powerpc-numa-Update-CPU

Re: [PATCH V9 2/2] powerpc/nodes: Ensure enough nodes avail for operations

Hi Michael, [auto build test ERROR on powerpc/next] [also build test ERROR on v4.13-rc6 next-20170823] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Michael-Bringmann/powerpc-numa-Update-CPU

[PATCH v2 0/5] android: binder: move allocator metadata and add shrinker

This patch set moves internal kernel data in the binder driver out of mmap regions that is readable by user space. A shrinker is added to the driver to dynamically manage the memory used by binder transactions and only free pages when the system is under memory pressure. This patch set also adds

[PATCH v2 0/5] android: binder: move allocator metadata and add shrinker

This patch set moves internal kernel data in the binder driver out of mmap regions that is readable by user space. A shrinker is added to the driver to dynamically manage the memory used by binder transactions and only free pages when the system is under memory pressure. This patch set also adds

Re: [PATCH v3 2/4] dmaengine: Add STM32 MDMA driver

On Tue, Aug 22, 2017 at 05:59:26PM +0200, Pierre Yves MORDRET wrote: > > > On 08/16/2017 06:47 PM, Vinod Koul wrote: > > On Wed, Jul 26, 2017 at 11:48:20AM +0200, Pierre-Yves MORDRET wrote: > > > >> +/* MDMA Channel x transfer configuration register */ > >> +#define STM32_MDMA_CTCR(x)

Re: [PATCH v3 2/4] dmaengine: Add STM32 MDMA driver

On Tue, Aug 22, 2017 at 05:59:26PM +0200, Pierre Yves MORDRET wrote: > > > On 08/16/2017 06:47 PM, Vinod Koul wrote: > > On Wed, Jul 26, 2017 at 11:48:20AM +0200, Pierre-Yves MORDRET wrote: > > > >> +/* MDMA Channel x transfer configuration register */ > >> +#define STM32_MDMA_CTCR(x)

Re: [PATCH] usb: reducing an usb-port auto-resume latency.

On 23.08.2017 17:30, Alan Stern wrote: On Wed, 23 Aug 2017, Mathias Nyman wrote: On 23.08.2017 09:18, anshuman.gu...@intel.com wrote: From: Anshuman Gupta This patch will improve the variable auto-resume latency of an usb-port. When xhci gets a port status change

Re: [PATCH] usb: reducing an usb-port auto-resume latency.

On 23.08.2017 17:30, Alan Stern wrote: On Wed, 23 Aug 2017, Mathias Nyman wrote: On 23.08.2017 09:18, anshuman.gu...@intel.com wrote: From: Anshuman Gupta This patch will improve the variable auto-resume latency of an usb-port. When xhci gets a port status change event interrupt due to

Re: [PATCH v3] fbcon: add fbcon=margin: command line option

Hi, On Friday, August 18, 2017 02:19:28 PM David Lechner wrote: > On 08/18/2017 01:21 PM, Geert Uytterhoeven wrote: > > Hi David, > > > > On Tue, Aug 1, 2017 at 6:35 PM, David Lechner wrote: > >> This adds a new command line option to select the fbcon margin color. > >> >

Re: [PATCH v3] fbcon: add fbcon=margin: command line option

Hi, On Friday, August 18, 2017 02:19:28 PM David Lechner wrote: > On 08/18/2017 01:21 PM, Geert Uytterhoeven wrote: > > Hi David, > > > > On Tue, Aug 1, 2017 at 6:35 PM, David Lechner wrote: > >> This adds a new command line option to select the fbcon margin color. > >> > >> The motivation for

Re: [PATCH v3 2/5] intel_pstate: convert to use acpi_match_platform_list()

On Wed, 2017-08-23 at 17:46 +0200, Borislav Petkov wrote: > On Fri, Aug 18, 2017 at 01:46:41PM -0600, Toshi Kani wrote: > > Convert to use acpi_match_platform_list() for the platform check. > > There is no change in functionality. > > : > > Btw, why is that ACPI_SIG_FADT's description not

Re: [PATCH v3 2/5] intel_pstate: convert to use acpi_match_platform_list()

On Wed, 2017-08-23 at 17:46 +0200, Borislav Petkov wrote: > On Fri, Aug 18, 2017 at 01:46:41PM -0600, Toshi Kani wrote: > > Convert to use acpi_match_platform_list() for the platform check. > > There is no change in functionality. > > : > > Btw, why is that ACPI_SIG_FADT's description not

Applied "spi: imx: fix little-endian build" to the spi tree

The patch spi: imx: fix little-endian build has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during

Applied "spi: imx: fix little-endian build" to the spi tree

The patch spi: imx: fix little-endian build has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during

Applied "ASoC: rt5645: make rt5645_platform_data const" to the asoc tree

The patch ASoC: rt5645: make rt5645_platform_data const has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "ASoC: rt5645: make rt5645_platform_data const" to the asoc tree

The patch ASoC: rt5645: make rt5645_platform_data const has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP

Hi Oza, > In working Enumuration case I get following: > [9.125976] pci :00:00.0: bridge configuration invalid ([bus > 00-00]), re-configuring > [9.134267] where=0x0 val=0x0001 > [9.146946] where=0x0 val=0x0001 > [9.158943] where=0x0 val=0x0001 > [9.170945]

Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP

Hi Oza, > In working Enumuration case I get following: > [9.125976] pci :00:00.0: bridge configuration invalid ([bus > 00-00]), re-configuring > [9.134267] where=0x0 val=0x0001 > [9.146946] where=0x0 val=0x0001 > [9.158943] where=0x0 val=0x0001 > [9.170945]

[PATCH v2 0/5] android: binder: move allocator metadata and add shrinker

This patch set moves internal kernel data in the binder driver out of mmap regions that is readable by user space. A shrinker is added to the driver to dynamically manage the memory used by binder transactions and only free pages when the system is under memory pressure. This patch set also adds

[PATCH v2 0/5] android: binder: move allocator metadata and add shrinker

This patch set moves internal kernel data in the binder driver out of mmap regions that is readable by user space. A shrinker is added to the driver to dynamically manage the memory used by binder transactions and only free pages when the system is under memory pressure. This patch set also adds

[PATCH v2 3/5] android: binder: Move buffer out of area shared with user space

Binder driver allocates buffer meta data in a region that is mapped in user space. These meta data contain pointers in the kernel. This patch allocates buffer meta data on the kernel heap that is not mapped in user space, and uses a pointer to refer to the data mapped. Signed-off-by: Sherry Yang

[PATCH v2 3/5] android: binder: Move buffer out of area shared with user space

Binder driver allocates buffer meta data in a region that is mapped in user space. These meta data contain pointers in the kernel. This patch allocates buffer meta data on the kernel heap that is not mapped in user space, and uses a pointer to refer to the data mapped. Signed-off-by: Sherry Yang

[PATCH v2 5/5] android: binder: Add shrinker tracepoints

Add tracepoints in binder transaction allocator to record lru hits and alloc/free page. Signed-off-by: Sherry Yang --- drivers/android/binder_alloc.c | 27 +++-- drivers/android/binder_trace.h | 55 ++ 2 files changed,

[PATCH v2 5/5] android: binder: Add shrinker tracepoints

Add tracepoints in binder transaction allocator to record lru hits and alloc/free page. Signed-off-by: Sherry Yang --- drivers/android/binder_alloc.c | 27 +++-- drivers/android/binder_trace.h | 55 ++ 2 files changed, 80 insertions(+), 2

[PATCH v2 4/5] android: binder: Add global lru shrinker to binder

Hold on to the pages allocated and mapped for transaction buffers until the system is under memory pressure. When that happens, use linux shrinker to free pages. Without using shrinker, patch "android: binder: Move buffer out of area shared with user space" will cause a significant slow down for

[PATCH v2 4/5] android: binder: Add global lru shrinker to binder

Hold on to the pages allocated and mapped for transaction buffers until the system is under memory pressure. When that happens, use linux shrinker to free pages. Without using shrinker, patch "android: binder: Move buffer out of area shared with user space" will cause a significant slow down for

[PATCH v2 1/5] android: binder: Refactor prev and next buffer into a helper function

Use helper functions buffer_next and buffer_prev instead of list_entry to get the next and previous buffers. Signed-off-by: Sherry Yang --- drivers/android/binder_alloc.c | 24 +++- 1 file changed, 15 insertions(+), 9 deletions(-) diff --git

[PATCH v2 1/5] android: binder: Refactor prev and next buffer into a helper function

Use helper functions buffer_next and buffer_prev instead of list_entry to get the next and previous buffers. Signed-off-by: Sherry Yang --- drivers/android/binder_alloc.c | 24 +++- 1 file changed, 15 insertions(+), 9 deletions(-) diff --git a/drivers/android/binder_alloc.c

[PATCH v2 2/5] android: binder: Add allocator selftest

binder_alloc_selftest tests that alloc_new_buf handles page allocation and deallocation properly when allocate and free buffers. The test allocates 5 buffers of various sizes to cover all possible page alignment cases, and frees the buffers using a list of exhaustive freeing order. Test: boot the

[PATCH v2 2/5] android: binder: Add allocator selftest

binder_alloc_selftest tests that alloc_new_buf handles page allocation and deallocation properly when allocate and free buffers. The test allocates 5 buffers of various sizes to cover all possible page alignment cases, and frees the buffers using a list of exhaustive freeing order. Test: boot the

Re: [PATCH v3 2/5] intel_pstate: convert to use acpi_match_platform_list()

On Fri, Aug 18, 2017 at 01:46:41PM -0600, Toshi Kani wrote: > Convert to use acpi_match_platform_list() for the platform check. > There is no change in functionality. > > Signed-off-by: Toshi Kani > Cc: "Rafael J. Wysocki" > Cc: Srinivas Pandruvada

Re: [PATCH v3 2/5] intel_pstate: convert to use acpi_match_platform_list()

On Fri, Aug 18, 2017 at 01:46:41PM -0600, Toshi Kani wrote: > Convert to use acpi_match_platform_list() for the platform check. > There is no change in functionality. > > Signed-off-by: Toshi Kani > Cc: "Rafael J. Wysocki" > Cc: Srinivas Pandruvada > Cc: Len Brown > Cc: Borislav Petkov > ---

Re: [PATCH v6] irqchip: Add support for tango interrupt router

On 23/08/2017 12:58, Marc Zyngier wrote: > On 20/08/17 18:22, Mason wrote: > >> On 07/08/2017 14:47, Marc Zyngier wrote: >> >>> On 01/08/17 17:56, Mason wrote: >>> +static int tango_alloc(struct irq_domain *dom, uint virq, uint n, void *arg) +{ + int spi; + struct

Re: [PATCH v6] irqchip: Add support for tango interrupt router

On 23/08/2017 12:58, Marc Zyngier wrote: > On 20/08/17 18:22, Mason wrote: > >> On 07/08/2017 14:47, Marc Zyngier wrote: >> >>> On 01/08/17 17:56, Mason wrote: >>> +static int tango_alloc(struct irq_domain *dom, uint virq, uint n, void *arg) +{ + int spi; + struct

Re: [GIT PULL] SCSI fixes for 4.13-rc6

On Wed, 2017-08-23 at 11:27 -0400, Martin K. Petersen wrote: > However, what's more important is that we still need a good version of > your patch for 4.13. I took Brian's workaround for ipr but I still think > Christoph's concerns need to be addressed for me to put your change back > in. Hello

Re: [GIT PULL] SCSI fixes for 4.13-rc6

On Wed, 2017-08-23 at 11:27 -0400, Martin K. Petersen wrote: > However, what's more important is that we still need a good version of > your patch for 4.13. I took Brian's workaround for ipr but I still think > Christoph's concerns need to be addressed for me to put your change back > in. Hello

Re: [PATCH 2/3] staging: rtlwifi: add MAC80211 dependency

On 08/23/2017 06:22 AM, Arnd Bergmann wrote: > Like the version in drivers/net/wireless, this driver requires the > MAC80211 framework, otherwise we run into a link error: > > ERROR: "ieee80211_rx_irqsafe" [drivers/staging/rtlwifi/r8822be.ko] undefined! > ERROR: "cfg80211_unlink_bss"

Re: [PATCH 2/3] staging: rtlwifi: add MAC80211 dependency

On 08/23/2017 06:22 AM, Arnd Bergmann wrote: > Like the version in drivers/net/wireless, this driver requires the > MAC80211 framework, otherwise we run into a link error: > > ERROR: "ieee80211_rx_irqsafe" [drivers/staging/rtlwifi/r8822be.ko] undefined! > ERROR: "cfg80211_unlink_bss"

Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP

On Wed, Aug 23, 2017 at 7:21 PM, Bjorn Helgaas wrote: > On Wed, Aug 23, 2017 at 03:57:02PM +0530, Oza Oza wrote: >> On Wed, Aug 23, 2017 at 2:03 AM, Bjorn Helgaas wrote: >> > [+cc Sinan, Timur, Alex] >> > >> > Hi Oza, >> > >> > On Mon, Aug 21, 2017 at

Re: [PATCH v7 1/2] PCI: iproc: Retry request when CRS returned from EP

On Wed, Aug 23, 2017 at 7:21 PM, Bjorn Helgaas wrote: > On Wed, Aug 23, 2017 at 03:57:02PM +0530, Oza Oza wrote: >> On Wed, Aug 23, 2017 at 2:03 AM, Bjorn Helgaas wrote: >> > [+cc Sinan, Timur, Alex] >> > >> > Hi Oza, >> > >> > On Mon, Aug 21, 2017 at 09:28:43PM +0530, Oza Pawandeep wrote: >> >>

[PATCH][next] net: hinic: fix comparison of a uint16_t type with -1

From: Colin Ian King The comparison of hw_ioctxt.rx_buf_sz_idx == -1 is always false because rx_buf_sz_idx is a uint16_t. Fix this by explicitly casting -1 to uint16_t. Detected by CoverityScan, CID#1454559 ("Operands don't affect result") Signed-off-by: Colin Ian

[PATCH][next] net: hinic: fix comparison of a uint16_t type with -1

From: Colin Ian King The comparison of hw_ioctxt.rx_buf_sz_idx == -1 is always false because rx_buf_sz_idx is a uint16_t. Fix this by explicitly casting -1 to uint16_t. Detected by CoverityScan, CID#1454559 ("Operands don't affect result") Signed-off-by: Colin Ian King ---

Re: [PATCH v2 1/2] KVM: SVM: Add Virtual GIF feature definition

On Wed, Aug 23, 2017 at 09:57:18AM -0500, Janakarajan Natarajan wrote: > Add a new cpufeature definition for Virtual GIF. > > Signed-off-by: Janakarajan Natarajan > --- > arch/x86/include/asm/cpufeatures.h | 1 + > 1 file changed, 1 insertion(+) > > diff --git

Re: [PATCH v2 1/2] KVM: SVM: Add Virtual GIF feature definition

On Wed, Aug 23, 2017 at 09:57:18AM -0500, Janakarajan Natarajan wrote: > Add a new cpufeature definition for Virtual GIF. > > Signed-off-by: Janakarajan Natarajan > --- > arch/x86/include/asm/cpufeatures.h | 1 + > 1 file changed, 1 insertion(+) > > diff --git

Re: [PATCH] media: omap3isp: fix uninitialized variable use

Hi, On Wed, Aug 23, 2017 at 04:58:27PM +0300, Sakari Ailus wrote: > On Wed, Aug 23, 2017 at 03:30:19PM +0200, Arnd Bergmann wrote: > > A debug printk statement was copied incorrectly into the new > > csi1 parser code and causes a warning there: > > > > drivers/media/platform/omap3isp/isp.c: In

Re: [PATCH] media: omap3isp: fix uninitialized variable use

Hi, On Wed, Aug 23, 2017 at 04:58:27PM +0300, Sakari Ailus wrote: > On Wed, Aug 23, 2017 at 03:30:19PM +0200, Arnd Bergmann wrote: > > A debug printk statement was copied incorrectly into the new > > csi1 parser code and causes a warning there: > > > > drivers/media/platform/omap3isp/isp.c: In

Re: [PATCH] ARM: at91: don't select CONFIG_ARM_CPU_SUSPEND for old platforms

On Wed, Aug 23, 2017 at 5:19 PM, Alexandre Belloni wrote: > On 23/08/2017 at 16:46:15 +0200, Arnd Bergmann wrote: >> My previous patch fixed a link error for all at91 platforms when >> CONFIG_ARM_CPU_SUSPEND was not set, however this caused another >> problem

Re: [PATCH] ARM: at91: don't select CONFIG_ARM_CPU_SUSPEND for old platforms

On Wed, Aug 23, 2017 at 5:19 PM, Alexandre Belloni wrote: > On 23/08/2017 at 16:46:15 +0200, Arnd Bergmann wrote: >> My previous patch fixed a link error for all at91 platforms when >> CONFIG_ARM_CPU_SUSPEND was not set, however this caused another >> problem on a configuration that enabled

Re: [PATCH 0/2] completion: Reduce stack usage caused by COMPLETION_INITIALIZER_ONSTACK()

On Wed, Aug 23, 2017 at 5:25 PM, Boqun Feng wrote: > With LOCKDEP_CROSSRELEASE and LOCKDEP_COMPLETIONS introduced, the growth > in kernel stack usage of several functions were reported: > > https://marc.info/?l=linux-kernel=150270063231284=2 > > The root cause of

Re: [PATCH 0/2] completion: Reduce stack usage caused by COMPLETION_INITIALIZER_ONSTACK()

On Wed, Aug 23, 2017 at 5:25 PM, Boqun Feng wrote: > With LOCKDEP_CROSSRELEASE and LOCKDEP_COMPLETIONS introduced, the growth > in kernel stack usage of several functions were reported: > > https://marc.info/?l=linux-kernel=150270063231284=2 > > The root cause of this is in

Re: [PATCH 0/1] devpts: use dynamic_dname() to generate proc name

Christian Brauner writes: > On Wed, Aug 16, 2017 at 11:45 PM, Linus Torvalds > wrote: >> On Wed, Aug 16, 2017 at 2:37 PM, Christian Brauner >> wrote: And Christian, if you can beat on this,

Re: [PATCH 0/1] devpts: use dynamic_dname() to generate proc name

Christian Brauner writes: > On Wed, Aug 16, 2017 at 11:45 PM, Linus Torvalds > wrote: >> On Wed, Aug 16, 2017 at 2:37 PM, Christian Brauner >> wrote: And Christian, if you can beat on this, that would be good. >>> >>> Yes, I can pound on this nicely with liblxc. We have patch >>> (

Re: [RFC Part1 PATCH v3 14/17] x86/boot: Add early boot support when running with SEV active

On Mon, Jul 24, 2017 at 02:07:54PM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > Early in the boot process, add checks to determine if the kernel is > running with Secure Encrypted Virtualization (SEV) active. > > Checking for SEV requires checking that the

Re: [RFC Part1 PATCH v3 14/17] x86/boot: Add early boot support when running with SEV active

On Mon, Jul 24, 2017 at 02:07:54PM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > Early in the boot process, add checks to determine if the kernel is > running with Secure Encrypted Virtualization (SEV) active. > > Checking for SEV requires checking that the kernel is running under a >

Re: [PATCH v2 1/2] dax: fix deadlock due to misaligned PMD faults

On Wed, Aug 23, 2017 at 11:57:33AM +0200, Jan Kara wrote: > On Tue 22-08-17 16:24:35, Ross Zwisler wrote: > > In DAX there are two separate places where the 2MiB range of a PMD is > > defined. > > > > The first is in the page tables, where a PMD mapping inserted for a given > > address spans from

Re: [PATCH v2 1/2] dax: fix deadlock due to misaligned PMD faults

On Wed, Aug 23, 2017 at 11:57:33AM +0200, Jan Kara wrote: > On Tue 22-08-17 16:24:35, Ross Zwisler wrote: > > In DAX there are two separate places where the 2MiB range of a PMD is > > defined. > > > > The first is in the page tables, where a PMD mapping inserted for a given > > address spans from

Re: [GIT PULL] SCSI fixes for 4.13-rc6

Hi Bart, > Had you noticed that Damien had asked not to send the "sd_zbc: Write > unlock zone from sd_uninit_cmnd()" patch to Linus without my "scsi-mq: > Always unprepare before requeuing a request" patch? He did change his mind later in that thread, though. However, what's more important is

Re: [GIT PULL] SCSI fixes for 4.13-rc6

Hi Bart, > Had you noticed that Damien had asked not to send the "sd_zbc: Write > unlock zone from sd_uninit_cmnd()" patch to Linus without my "scsi-mq: > Always unprepare before requeuing a request" patch? He did change his mind later in that thread, though. However, what's more important is

[PATCH 2/2] completion: Avoid unnecessary stack allocation for COMPLETION_INITIALIZER_ONSTACK()

In theory, COMPLETION_INITIALIZER_ONSTACK() should never affect the stack allocation of the caller. However, on some compilers, a temporary structure was allocated for the return value of COMPLETION_INITIALIZER_ONSTACK(), for example in write_journal() with LOCKDEP_COMPLETIONS=y(gcc is 7.1.1):

[PATCH 2/2] completion: Avoid unnecessary stack allocation for COMPLETION_INITIALIZER_ONSTACK()

In theory, COMPLETION_INITIALIZER_ONSTACK() should never affect the stack allocation of the caller. However, on some compilers, a temporary structure was allocated for the return value of COMPLETION_INITIALIZER_ONSTACK(), for example in write_journal() with LOCKDEP_COMPLETIONS=y(gcc is 7.1.1):

[PATCH 1/2] nfit: Use init_completion() in acpi_nfit_flush_probe()

There is no need to use COMPLETION_INITIALIZER_ONSTACK() in acpi_nfit_flush_probe(), replace it with init_completion(). Signed-off-by: Boqun Feng --- drivers/acpi/nfit/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/acpi/nfit/core.c

[PATCH 1/2] nfit: Use init_completion() in acpi_nfit_flush_probe()

There is no need to use COMPLETION_INITIALIZER_ONSTACK() in acpi_nfit_flush_probe(), replace it with init_completion(). Signed-off-by: Boqun Feng --- drivers/acpi/nfit/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/acpi/nfit/core.c b/drivers/acpi/nfit/core.c

[no subject]

306027330035843.doc Description: MS-Word document

[no subject]

306027330035843.doc Description: MS-Word document

[PATCH 0/2] completion: Reduce stack usage caused by COMPLETION_INITIALIZER_ONSTACK()

With LOCKDEP_CROSSRELEASE and LOCKDEP_COMPLETIONS introduced, the growth in kernel stack usage of several functions were reported: https://marc.info/?l=linux-kernel=150270063231284=2 The root cause of this is in COMPLETION_INITIALIZER_ONSTACK(), we use ({init_completion();

[PATCH 0/2] completion: Reduce stack usage caused by COMPLETION_INITIALIZER_ONSTACK()

With LOCKDEP_CROSSRELEASE and LOCKDEP_COMPLETIONS introduced, the growth in kernel stack usage of several functions were reported: https://marc.info/?l=linux-kernel=150270063231284=2 The root cause of this is in COMPLETION_INITIALIZER_ONSTACK(), we use ({init_completion();

[no subject]

306027330035843.doc Description: MS-Word document

[no subject]

306027330035843.doc Description: MS-Word document

Re: [PATCH] storvsc: do not assume SG list is continuous when doing bounce buffers (for 4.1 stable only)

Christoph, > Ok. If the stable maintainers are ok with your small fix > I'm not going to complain too loudly. But I'm always worried about > stable trees divering too much from mainline. The seemingly innocuous transition from SG_GAPS to virt boundary has caused several data corruption

Re: [PATCH] storvsc: do not assume SG list is continuous when doing bounce buffers (for 4.1 stable only)

Christoph, > Ok. If the stable maintainers are ok with your small fix > I'm not going to complain too loudly. But I'm always worried about > stable trees divering too much from mainline. The seemingly innocuous transition from SG_GAPS to virt boundary has caused several data corruption

Re: [PATCH] x86/nmi/64: avoid passing user space rsp of pt_regs to nmi handler

On Wed, Aug 23, 2017 at 10:19:02PM +0800, oliver yang wrote: > 2017-08-23 1:51 GMT+08:00 Josh Poimboeuf : > > On Tue, Aug 22, 2017 at 05:09:19PM +, yang oliver wrote: > >> From: Yong Yang > >> > >> While NMI interrupts the very beginning of SYSCALL,

Re: [PATCH] x86/nmi/64: avoid passing user space rsp of pt_regs to nmi handler

On Wed, Aug 23, 2017 at 10:19:02PM +0800, oliver yang wrote: > 2017-08-23 1:51 GMT+08:00 Josh Poimboeuf : > > On Tue, Aug 22, 2017 at 05:09:19PM +, yang oliver wrote: > >> From: Yong Yang > >> > >> While NMI interrupts the very beginning of SYSCALL, the rsp could > >> be still user space

Re: [PATCH] ARM: at91: don't select CONFIG_ARM_CPU_SUSPEND for old platforms

On 23/08/2017 at 16:46:15 +0200, Arnd Bergmann wrote: > My previous patch fixed a link error for all at91 platforms when > CONFIG_ARM_CPU_SUSPEND was not set, however this caused another > problem on a configuration that enabled CONFIG_ARCH_AT91 but none > of the individual SoCs, and that also

Re: [PATCH] ARM: at91: don't select CONFIG_ARM_CPU_SUSPEND for old platforms

On 23/08/2017 at 16:46:15 +0200, Arnd Bergmann wrote: > My previous patch fixed a link error for all at91 platforms when > CONFIG_ARM_CPU_SUSPEND was not set, however this caused another > problem on a configuration that enabled CONFIG_ARCH_AT91 but none > of the individual SoCs, and that also

Re: [PATCH v2] venus: fix copy/paste error in return_buf_error

On 08/23/2017 03:59 PM, Stanimir Varbanov wrote: > Gustavo, > > could you resend the patch with the Acked-by and Cc stable kernel. No need to resend, sorry for the noise. -- regards, Stan

Re: [PATCH v2] venus: fix copy/paste error in return_buf_error

On 08/23/2017 03:59 PM, Stanimir Varbanov wrote: > Gustavo, > > could you resend the patch with the Acked-by and Cc stable kernel. No need to resend, sorry for the noise. -- regards, Stan

Re: [PATCH 1/3] ARM: dts: sun8i: Add basic dtsi file for Allwinner R40

在 2017-08-23 22:35，Maxime Ripard 写道： On Wed, Aug 23, 2017 at 07:56:29PM +0800, icen...@aosc.io wrote: > > + reg = <0x01c0f000 0x1000>; > > + clocks = < CLK_BUS_MMC0>, < CLK_MMC0>; > > + clock-names = "ahb", "mmc"; > > +

Re: [PATCH 1/3] ARM: dts: sun8i: Add basic dtsi file for Allwinner R40

在 2017-08-23 22:35，Maxime Ripard 写道： On Wed, Aug 23, 2017 at 07:56:29PM +0800, icen...@aosc.io wrote: > > + reg = <0x01c0f000 0x1000>; > > + clocks = < CLK_BUS_MMC0>, < CLK_MMC0>; > > + clock-names = "ahb", "mmc"; > > +

Re: [PATCH] rtc: ds1307: add basic support for ds1341 chip

On 23/08/17 07:38, Nikita Yushchenko wrote: > This adds support for reading and writing date/time from/to ds1314 chip. > > Other functionality (alarms, inout clock, output clock) is not added > yet, because availability of that depends on chip connections. > > Signed-off-by: Nikita Yushchenko

Re: [PATCH] rtc: ds1307: add basic support for ds1341 chip

On 23/08/17 07:38, Nikita Yushchenko wrote: > This adds support for reading and writing date/time from/to ds1314 chip. > > Other functionality (alarms, inout clock, output clock) is not added > yet, because availability of that depends on chip connections. > > Signed-off-by: Nikita Yushchenko

[PATCH] staging: r8822be: fix null pointer dereference with a null driver_adapter

From: Colin Ian King The call to _rtl_dbg_trace via macro HALMAC_RT_TRACE will trigger a null pointer deference on the null driver_adapter. Fix this by assigning driver_adapter earlier to halmac_adapter->driver_adapter before the tracing call so that a non-null

[PATCH] staging: r8822be: fix null pointer dereference with a null driver_adapter

From: Colin Ian King The call to _rtl_dbg_trace via macro HALMAC_RT_TRACE will trigger a null pointer deference on the null driver_adapter. Fix this by assigning driver_adapter earlier to halmac_adapter->driver_adapter before the tracing call so that a non-null driver_adapter is passed instead.

Re: [GIT PULL] SCSI fixes for 4.13-rc6

On Wed, 2017-08-23 at 07:42 +0100, James Bottomley wrote: > Six minor and error leg fixes, plus one major change: the reversion of > scsi-mq as the default. We're doing the latter temporarily (with a > backport to stable) to give us time to fix all the issues that turned > up with this default

Re: [GIT PULL] SCSI fixes for 4.13-rc6

On Wed, 2017-08-23 at 07:42 +0100, James Bottomley wrote: > Six minor and error leg fixes, plus one major change: the reversion of > scsi-mq as the default. We're doing the latter temporarily (with a > backport to stable) to give us time to fix all the issues that turned > up with this default

[PATCH] scsi: lpfc: avoid false-positive gcc-8 warning

This is an interesting regression with gcc-8, showing a harmless warning for correct code: In file included from include/linux/kernel.h:13:0, ... from drivers/scsi/lpfc/lpfc_debugfs.c:23: include/linux/printk.h:301:2: error: 'eq' may be used uninitialized in this

[PATCH] scsi: lpfc: avoid false-positive gcc-8 warning

This is an interesting regression with gcc-8, showing a harmless warning for correct code: In file included from include/linux/kernel.h:13:0, ... from drivers/scsi/lpfc/lpfc_debugfs.c:23: include/linux/printk.h:301:2: error: 'eq' may be used uninitialized in this

[PATCH v2 1/2] KVM: SVM: Add Virtual GIF feature definition

Add a new cpufeature definition for Virtual GIF. Signed-off-by: Janakarajan Natarajan --- arch/x86/include/asm/cpufeatures.h | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/x86/include/asm/cpufeatures.h b/arch/x86/include/asm/cpufeatures.h index

[PATCH v2 1/2] KVM: SVM: Add Virtual GIF feature definition

Add a new cpufeature definition for Virtual GIF. Signed-off-by: Janakarajan Natarajan --- arch/x86/include/asm/cpufeatures.h | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/x86/include/asm/cpufeatures.h b/arch/x86/include/asm/cpufeatures.h index ca3c48c..0e25e7a 100644 ---

[PATCH v2 2/2] KVM: SVM: Enable Virtual GIF feature

Enable the Virtual GIF feature. This is done by setting bit 25 at position 60h in the vmcb. With this feature enabled, the processor uses bit 9 at position 60h as the virtual GIF when executing STGI/CLGI instructions. Since the execution of STGI by the L1 hypervisor does not cause a return to

[PATCH v2 2/2] KVM: SVM: Enable Virtual GIF feature

Enable the Virtual GIF feature. This is done by setting bit 25 at position 60h in the vmcb. With this feature enabled, the processor uses bit 9 at position 60h as the virtual GIF when executing STGI/CLGI instructions. Since the execution of STGI by the L1 hypervisor does not cause a return to

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