Re: [PATCH RFC UGLY] x86,mm,sched: make lazy TLB mode even lazier

On Sun, 2016-08-28 at 01:11 -0700, Andy Lutomirski wrote: > On Aug 25, 2016 9:06 PM, "Rik van Riel" wrote: > > > > Subject: x86,mm,sched: make lazy TLB mode even lazier > > > > Lazy TLB mode can result in an idle CPU being woken up for a TLB > > flush, when all it really needed

Re: [PATCH RFC UGLY] x86,mm,sched: make lazy TLB mode even lazier

On Sun, 2016-08-28 at 01:11 -0700, Andy Lutomirski wrote: > On Aug 25, 2016 9:06 PM, "Rik van Riel" wrote: > > > > Subject: x86,mm,sched: make lazy TLB mode even lazier > > > > Lazy TLB mode can result in an idle CPU being woken up for a TLB > > flush, when all it really needed to do was flush

Re: OOM detection regressions since 4.7

On Mon 29-08-16 16:52:03, Olaf Hering wrote: > On Thu, Aug 25, Olaf Hering wrote: > > > On Thu, Aug 25, Michal Hocko wrote: > > > > > Any luck with the testing of this patch? > > I ran rc3 for a few hours on Friday amd FireFox was not killed. > Now rc3 is running for a day with the usual

Re: OOM detection regressions since 4.7

On Mon 29-08-16 16:52:03, Olaf Hering wrote: > On Thu, Aug 25, Olaf Hering wrote: > > > On Thu, Aug 25, Michal Hocko wrote: > > > > > Any luck with the testing of this patch? > > I ran rc3 for a few hours on Friday amd FireFox was not killed. > Now rc3 is running for a day with the usual

[PATCH] xenbus: Use proc_create_mount_point() to create /proc/xen

Mounting proc in user namespace containers fails if the xenbus filesystem is mounted on /proc/xen because this directory fails the "permanently empty" test. proc_create_mount_point() exists specifically to create such mountpoints in proc but is currently proc-internal. Export this interface to

[PATCH] xenbus: Use proc_create_mount_point() to create /proc/xen

Mounting proc in user namespace containers fails if the xenbus filesystem is mounted on /proc/xen because this directory fails the "permanently empty" test. proc_create_mount_point() exists specifically to create such mountpoints in proc but is currently proc-internal. Export this interface to

Re: demise of gmane and lkml/kernel mailing lists archiving

On Wed, Aug 03, 2016 at 04:53:53PM -0700, Joe Perches wrote: > Instead of relying on external resources to archive the mailing > lists, would it be reasonable/feasible to have kernel.org archive > the various kernel related mailing lists? Yes, it's feasible. It's also feasible to migrate the

Re: demise of gmane and lkml/kernel mailing lists archiving

On Wed, Aug 03, 2016 at 04:53:53PM -0700, Joe Perches wrote: > Instead of relying on external resources to archive the mailing > lists, would it be reasonable/feasible to have kernel.org archive > the various kernel related mailing lists? Yes, it's feasible. It's also feasible to migrate the

Re: [f2fs-dev] [PATCH] fscrypto: fix to null-terminate encrypted filename in fname_encrypt

Hi Ted, Jaegeuk, On 2016/8/28 14:16, Chao Yu wrote: > Hi Ted, > > On 2016/8/28 13:13, Theodore Ts'o wrote: >> On Sun, Aug 28, 2016 at 09:13:28AM +0800, Chao Yu wrote: >>> From: Chao Yu >>> >>> This patch fixes to add null character at the end of encrypted filename Since

Re: [f2fs-dev] [PATCH] fscrypto: fix to null-terminate encrypted filename in fname_encrypt

Hi Ted, Jaegeuk, On 2016/8/28 14:16, Chao Yu wrote: > Hi Ted, > > On 2016/8/28 13:13, Theodore Ts'o wrote: >> On Sun, Aug 28, 2016 at 09:13:28AM +0800, Chao Yu wrote: >>> From: Chao Yu >>> >>> This patch fixes to add null character at the end of encrypted filename Since encryption

Re: OOM detection regressions since 4.7

On Mon, Aug 29, Olaf Hering wrote: > Full dmesg attached. Now.. dmesg-4.8.0-rc3-3.bug994066-default.txt.gz Description: GNU Zip compressed data signature.asc Description: PGP signature

Re: OOM detection regressions since 4.7

On Mon, Aug 29, Olaf Hering wrote: > Full dmesg attached. Now.. dmesg-4.8.0-rc3-3.bug994066-default.txt.gz Description: GNU Zip compressed data signature.asc Description: PGP signature

Re: OOM detection regressions since 4.7

On Thu, Aug 25, Olaf Hering wrote: > On Thu, Aug 25, Michal Hocko wrote: > > > Any luck with the testing of this patch? I ran rc3 for a few hours on Friday amd FireFox was not killed. Now rc3 is running for a day with the usual workload and FireFox is still running. Today I noticed the

Re: OOM detection regressions since 4.7

On Thu, Aug 25, Olaf Hering wrote: > On Thu, Aug 25, Michal Hocko wrote: > > > Any luck with the testing of this patch? I ran rc3 for a few hours on Friday amd FireFox was not killed. Now rc3 is running for a day with the usual workload and FireFox is still running. Today I noticed the

4.8-rc4 spews "BUG: sleeping function called from invalid context at fs/dcache.c:757"

Hi, I noticed that a freshly booted 4.8-rc4 kernel gives the following kernel messages a few times: BUG: sleeping function called from invalid context at fs/dcache.c:757 in_atomic(): 1, irqs_disabled(): 0, pid: 8431, name: automount 1 lock held by automount/8431: #0:

4.8-rc4 spews "BUG: sleeping function called from invalid context at fs/dcache.c:757"

Hi, I noticed that a freshly booted 4.8-rc4 kernel gives the following kernel messages a few times: BUG: sleeping function called from invalid context at fs/dcache.c:757 in_atomic(): 1, irqs_disabled(): 0, pid: 8431, name: automount 1 lock held by automount/8431: #0:

Re: [PATCH] mm: clarify COMPACTION Kconfig text

On Mon 29-08-16 10:10:45, Johannes Weiner wrote: > On Tue, Aug 23, 2016 at 10:09:17AM +0200, Michal Hocko wrote: > > From: Michal Hocko > > > > The current wording of the COMPACTION Kconfig help text doesn't > > emphasise that disabling COMPACTION might cripple the page

Re: [PATCH] mm: clarify COMPACTION Kconfig text

On Mon 29-08-16 10:10:45, Johannes Weiner wrote: > On Tue, Aug 23, 2016 at 10:09:17AM +0200, Michal Hocko wrote: > > From: Michal Hocko > > > > The current wording of the COMPACTION Kconfig help text doesn't > > emphasise that disabling COMPACTION might cripple the page allocator > > which

Re: [PATCH] ALSA: usb-audio: Add sample rate inquiry quirk for B850V3 CP2114

On Mon, 29 Aug 2016 16:45:58 +0200, Akshay Bhat wrote: > > > > On 08/29/2016 10:13 AM, Takashi Iwai wrote: > > On Mon, 29 Aug 2016 16:10:03 +0200, > > Akshay Bhat wrote: > >> > >> Hi, > >> > >> On Fri, Aug 12, 2016 at 2:08 PM, Akshay Bhat > >> wrote: > >>> From: Ken

Re: what is the purpose of SLAB and SLUB

On Mon, 29 Aug 2016, Michal Hocko wrote: > Compaction can certainly help and the more we are proactive in that > direction the better. Vlastimil has already done a first step in that > direction and we a have a dedicated kcompactd kernel thread for that > purpose. But I guess what Mel had in mind

Re: [PATCH] ALSA: usb-audio: Add sample rate inquiry quirk for B850V3 CP2114

On Mon, 29 Aug 2016 16:45:58 +0200, Akshay Bhat wrote: > > > > On 08/29/2016 10:13 AM, Takashi Iwai wrote: > > On Mon, 29 Aug 2016 16:10:03 +0200, > > Akshay Bhat wrote: > >> > >> Hi, > >> > >> On Fri, Aug 12, 2016 at 2:08 PM, Akshay Bhat > >> wrote: > >>> From: Ken Lin > >>> > >>> Avoid

Re: what is the purpose of SLAB and SLUB

On Mon, 29 Aug 2016, Michal Hocko wrote: > Compaction can certainly help and the more we are proactive in that > direction the better. Vlastimil has already done a first step in that > direction and we a have a dedicated kcompactd kernel thread for that > purpose. But I guess what Mel had in mind

Re: [PATCH 2/2] mm/usercopy: enable usercopy size checking for modern versions of gcc

On Fri, Aug 26, 2016 at 05:37:20PM -0700, Linus Torvalds wrote: > On Fri, Aug 26, 2016 at 1:56 PM, Josh Poimboeuf wrote: > > > > There's one problem with that though. It's going to annoy a lot of > > people who do allyesconfig/allmodconfig builds because > >

Re: [PATCH 2/2] mm/usercopy: enable usercopy size checking for modern versions of gcc

On Fri, Aug 26, 2016 at 05:37:20PM -0700, Linus Torvalds wrote: > On Fri, Aug 26, 2016 at 1:56 PM, Josh Poimboeuf wrote: > > > > There's one problem with that though. It's going to annoy a lot of > > people who do allyesconfig/allmodconfig builds because > > DEBUG_STRICT_USER_COPY_CHECKS adds

Re: [Patch v4 9/9] arm64: Update device tree for Layerscape SoCs

On Mon, Aug 29, 2016 at 04:33:50PM +0800, Shawn Guo wrote: > To avoid potential merge conflicts. Haven't heard of any so far. And I don't see how adding 1 or 2 DT entries more per driver is a serious merge conflict. > Unless there are hard dependencies like making it compile, avoiding >

Re: [Patch v4 9/9] arm64: Update device tree for Layerscape SoCs

On Mon, Aug 29, 2016 at 04:33:50PM +0800, Shawn Guo wrote: > To avoid potential merge conflicts. Haven't heard of any so far. And I don't see how adding 1 or 2 DT entries more per driver is a serious merge conflict. > Unless there are hard dependencies like making it compile, avoiding >

Re: [v4.7.2: Oops] When loading IT87 HARDWARE MONITORING DRIVER

On 08/29/2016 03:11 AM, Jean Delvare wrote: On Mon, 29 Aug 2016 12:06:34 +0200, Jean Delvare wrote: I'm trying to find when the bug was introduced. I have a hard time believing it went unnoticed for long. If it fixes your problem I'll send a clean patch. Broken by: commit

Re: [v4.7.2: Oops] When loading IT87 HARDWARE MONITORING DRIVER

On 08/29/2016 03:11 AM, Jean Delvare wrote: On Mon, 29 Aug 2016 12:06:34 +0200, Jean Delvare wrote: I'm trying to find when the bug was introduced. I have a hard time believing it went unnoticed for long. If it fixes your problem I'll send a clean patch. Broken by: commit

Re: [PATCH] ALSA: usb-audio: Add sample rate inquiry quirk for B850V3 CP2114

On 08/29/2016 10:13 AM, Takashi Iwai wrote: On Mon, 29 Aug 2016 16:10:03 +0200, Akshay Bhat wrote: Hi, On Fri, Aug 12, 2016 at 2:08 PM, Akshay Bhat wrote: From: Ken Lin Avoid getting sample rate on B850V3 CP2114 as it is unsupported and

Re: [PATCH] ALSA: usb-audio: Add sample rate inquiry quirk for B850V3 CP2114

On 08/29/2016 10:13 AM, Takashi Iwai wrote: On Mon, 29 Aug 2016 16:10:03 +0200, Akshay Bhat wrote: Hi, On Fri, Aug 12, 2016 at 2:08 PM, Akshay Bhat wrote: From: Ken Lin Avoid getting sample rate on B850V3 CP2114 as it is unsupported and causes noisy "current rate is different from the

[PATCH] drm/i915/skl: Don't try to update plane watermarks if they haven't changed

i915 sometimes needs to disable planes in the middle of an atomic commit, and then reenable them later in the same commit. Because of this, we can't make the assumption that the state of the plane actually changed. Since the state of the plane hasn't actually changed, neither have it's watermarks.

[PATCH] drm/i915/skl: Don't try to update plane watermarks if they haven't changed

i915 sometimes needs to disable planes in the middle of an atomic commit, and then reenable them later in the same commit. Because of this, we can't make the assumption that the state of the plane actually changed. Since the state of the plane hasn't actually changed, neither have it's watermarks.

Re: perf-4.8.0-rc3: Segmentation fault

Em Thu, Aug 25, 2016 at 01:49:41PM +0300, Alexey Dobriyan escreveu: > I profiled kernel allmodconfig build (don't ask) and perf tui reliably > segfaults when trying to enter annotation mode for any of the > individual functions. It segfaults immediately before even showing > menu with choices. >

Re: perf-4.8.0-rc3: Segmentation fault

Em Thu, Aug 25, 2016 at 01:49:41PM +0300, Alexey Dobriyan escreveu: > I profiled kernel allmodconfig build (don't ask) and perf tui reliably > segfaults when trying to enter annotation mode for any of the > individual functions. It segfaults immediately before even showing > menu with choices. >

Re: [PATCH 1/3] perf/x86/intel/bts: Fix confused ordering of PMU callbacks

Peter Zijlstra writes: > On Wed, Aug 24, 2016 at 05:15:54PM +0300, Alexander Shishkin wrote: >> @@ -221,10 +245,13 @@ static void __bts_event_start(struct perf_event *event) >> >> /* >> * local barrier to make sure that ds configuration made it >> - *

Re: [PATCH 1/3] perf/x86/intel/bts: Fix confused ordering of PMU callbacks

Peter Zijlstra writes: > On Wed, Aug 24, 2016 at 05:15:54PM +0300, Alexander Shishkin wrote: >> @@ -221,10 +245,13 @@ static void __bts_event_start(struct perf_event *event) >> >> /* >> * local barrier to make sure that ds configuration made it >> - * before we enable BTS >> +

Re: [PACTH v2 0/3] Implement /proc//totmaps

[Sorry for a late reply, I was busy with other stuff] On Mon 22-08-16 15:44:53, Sonny Rao wrote: > On Mon, Aug 22, 2016 at 12:54 AM, Michal Hocko wrote: [...] > But what about the private_clean and private_dirty? Surely > those are more generally useful for calculating a

Re: [PACTH v2 0/3] Implement /proc//totmaps

[Sorry for a late reply, I was busy with other stuff] On Mon 22-08-16 15:44:53, Sonny Rao wrote: > On Mon, Aug 22, 2016 at 12:54 AM, Michal Hocko wrote: [...] > But what about the private_clean and private_dirty? Surely > those are more generally useful for calculating a lower bound on >

Re: [PATCH][v8] PM / hibernate: Verify the consistent of e820 memory map by md5 value

On Mon, Aug 29, 2016 at 09:15:00AM +0200, Pavel Machek wrote: > Sounds about as easy as hot unplugging arbitrary memory address. IOW > "not easy". Regardless, forcibly panicking the system more is still the wrong approach IMO. Instead, I'd try to issue a big fat warning that BIOS corrupts E820

Re: [PATCH][v8] PM / hibernate: Verify the consistent of e820 memory map by md5 value

On Mon, Aug 29, 2016 at 09:15:00AM +0200, Pavel Machek wrote: > Sounds about as easy as hot unplugging arbitrary memory address. IOW > "not easy". Regardless, forcibly panicking the system more is still the wrong approach IMO. Instead, I'd try to issue a big fat warning that BIOS corrupts E820

Re: [PATCH V2] ARM: imx: add cpuidle support for i.mx6ul

On Mon, Aug 29, 2016 at 11:41:12PM +0800, Anson Huang wrote: > This patch enables cpuidle driver for i.MX6UL, it > reuses i.MX6SX's cpuidle driver, 3 levels of cpuidle > supported: > > 1. ARM WFI; > 2. SOC in WAIT mode; > 3. SOC in WAIT mode + ARM power off. > > As i.MX6UL has cortex-A7 CORE

Re: [PATCH V2] ARM: imx: add cpuidle support for i.mx6ul

On Mon, Aug 29, 2016 at 11:41:12PM +0800, Anson Huang wrote: > This patch enables cpuidle driver for i.MX6UL, it > reuses i.MX6SX's cpuidle driver, 3 levels of cpuidle > supported: > > 1. ARM WFI; > 2. SOC in WAIT mode; > 3. SOC in WAIT mode + ARM power off. > > As i.MX6UL has cortex-A7 CORE

Re: [PATCH V2] ARM: dts: imx6ul iomuxc syscon is compatible to imx6q

On Mon, Aug 29, 2016 at 10:25:43PM +0800, Anson Huang wrote: > The imx6ul iomuxc syscon is compatible to imx6q, > so let's add compatible string 'fsl,imx6q-iomuxc-gpr' > for imx6ul iomuxc syscon node. > > Signed-off-by: Anson Huang Will this patch still be needed if you

Re: [PATCH V2] ARM: dts: imx6ul iomuxc syscon is compatible to imx6q

On Mon, Aug 29, 2016 at 10:25:43PM +0800, Anson Huang wrote: > The imx6ul iomuxc syscon is compatible to imx6q, > so let's add compatible string 'fsl,imx6q-iomuxc-gpr' > for imx6ul iomuxc syscon node. > > Signed-off-by: Anson Huang Will this patch still be needed if you implement imx6ul suspend

Re: [PATCH V2 1/2] ARM: imx: rename imx6q_set_int_mem_clk_lpm() function

On Mon, Aug 29, 2016 at 09:49:56PM +0800, Anson Huang wrote: > Let's rename the function imx6q_set_int_mem_clk_lpm() > to imx6_set_int_mem_clk_lpm() since it's actually > common for all i.MX6 SoCs. > > Signed-off-by: Anson Huang Applied both, thanks.

Re: [PATCH V2 1/2] ARM: imx: rename imx6q_set_int_mem_clk_lpm() function

On Mon, Aug 29, 2016 at 09:49:56PM +0800, Anson Huang wrote: > Let's rename the function imx6q_set_int_mem_clk_lpm() > to imx6_set_int_mem_clk_lpm() since it's actually > common for all i.MX6 SoCs. > > Signed-off-by: Anson Huang Applied both, thanks.

Re: [PATCH v2] ARM: imx: use IS_ENABLED() instead of checking for built-in or module

On Mon, Aug 29, 2016 at 12:12:04PM +0200, Javier Martinez Canillas wrote: > The IS_ENABLED() macro checks if a Kconfig symbol has been enabled either > built-in or as a module, use that macro instead of open coding the same. > > Using the macro makes the code more readable by helping abstract

Re: [PATCH v2] ARM: imx: use IS_ENABLED() instead of checking for built-in or module

On Mon, Aug 29, 2016 at 12:12:04PM +0200, Javier Martinez Canillas wrote: > The IS_ENABLED() macro checks if a Kconfig symbol has been enabled either > built-in or as a module, use that macro instead of open coding the same. > > Using the macro makes the code more readable by helping abstract

Re: [PATCH v1] kdump, vmcoreinfo: report memory sections virtual addresses

Great, thanks Baoquan. On Mon, Aug 29, 2016 at 3:11 AM, Baoquan He wrote: > Hi Thomas, > > I used below code and it works. Since using VMCOREINFO_NUMBER can reuse > the existing struct number_table to import the data. It makes change > easier. But the place could be next to

Re: [PATCH v1] kdump, vmcoreinfo: report memory sections virtual addresses

Great, thanks Baoquan. On Mon, Aug 29, 2016 at 3:11 AM, Baoquan He wrote: > Hi Thomas, > > I used below code and it works. Since using VMCOREINFO_NUMBER can reuse > the existing struct number_table to import the data. It makes change > easier. But the place could be next to KERNEL_IMAGE_SIZE, or

Re: [PATCH] mmc: sdhci-msm: Add pm_runtime and system PM support

On 16 June 2016 at 14:35, Pramod Gurav wrote: > Provides runtime PM callbacks to enable and disable clock resources > when idle. Also support system PM callbacks to be called during system > suspend and resume. > > Signed-off-by: Pramod Gurav >

Re: [PATCH] mmc: sdhci-msm: Add pm_runtime and system PM support

On 16 June 2016 at 14:35, Pramod Gurav wrote: > Provides runtime PM callbacks to enable and disable clock resources > when idle. Also support system PM callbacks to be called during system > suspend and resume. > > Signed-off-by: Pramod Gurav > --- > drivers/mmc/host/sdhci-msm.c | 57 >

Re: [PATCH 1/3] ARM: dts: imx7-colibri: move SD-card to module level

On Sun, Aug 28, 2016 at 10:13:22PM -0700, Stefan Agner wrote: > Move SD-card definition to module level. While at it, also disable > write-protect since the Colibri standard does not define a pin for > SD-Card write-protection. > > Signed-off-by: Stefan Agner Applied all,

Re: [PATCH 1/3] ARM: dts: imx7-colibri: move SD-card to module level

On Sun, Aug 28, 2016 at 10:13:22PM -0700, Stefan Agner wrote: > Move SD-card definition to module level. While at it, also disable > write-protect since the Colibri standard does not define a pin for > SD-Card write-protection. > > Signed-off-by: Stefan Agner Applied all, thanks.

RE: [PATCH v3] IB/cxgb4: Mark symbols static for _free_qp

> Subject: [PATCH v3] IB/cxgb4: Mark symbols static for _free_qp > > We get 1 warning when build kernel with W=1: > drivers/infiniband/hw/cxgb4/qp.c:686:6: warning: no previous prototype for > '_free_qp' [-Wmissing-prototypes] > > In fact, this function is only used in the file in which it is

RE: [PATCH v3] IB/cxgb4: Mark symbols static for _free_qp

> Subject: [PATCH v3] IB/cxgb4: Mark symbols static for _free_qp > > We get 1 warning when build kernel with W=1: > drivers/infiniband/hw/cxgb4/qp.c:686:6: warning: no previous prototype for > '_free_qp' [-Wmissing-prototypes] > > In fact, this function is only used in the file in which it is

RE: [PATCH v2] fix:infiniband:hw:cxgb4:qp:mark symbols static where possible

> Subject: [PATCH v2] fix:infiniband:hw:cxgb4:qp:mark symbols static where possible > Is "fix:infiniband:hw:cxgb4:qp:" some standard way patches are being submitted these days? Usually it would be the module name, something like: iw_cxgb4: make _free_qp() static Steve

RE: [PATCH v2] fix:infiniband:hw:cxgb4:qp:mark symbols static where possible

> Subject: [PATCH v2] fix:infiniband:hw:cxgb4:qp:mark symbols static where possible > Is "fix:infiniband:hw:cxgb4:qp:" some standard way patches are being submitted these days? Usually it would be the module name, something like: iw_cxgb4: make _free_qp() static Steve

Re: [PATCH 3/8] media: vidc: decoder: add video decoder files

Hi Hans, +static int vdec_start_streaming(struct vb2_queue *q, unsigned int count) +{ + struct vidc_inst *inst = vb2_get_drv_priv(q); + struct hfi_core *hfi = >core->hfi; + struct device *dev = inst->core->dev; + struct hfi_buffer_requirements bufreq; +

Re: [PATCH 3/8] media: vidc: decoder: add video decoder files

Hi Hans, +static int vdec_start_streaming(struct vb2_queue *q, unsigned int count) +{ + struct vidc_inst *inst = vb2_get_drv_priv(q); + struct hfi_core *hfi = >core->hfi; + struct device *dev = inst->core->dev; + struct hfi_buffer_requirements bufreq; +

Re: [PATCH v3 1/3] firmware_class: encapsulate firmware loading status

On 08/29/2016 11:50 AM, Daniel Wagner wrote: On 08/25/2016 07:50 PM, Luis R. Rodriguez wrote: +#else /* CONFIG_FW_LOADER_USER_HELPER */ + +static int loading_timeout = 60; +#define firmware_loading_timeout() (loading_timeout * HZ) + +#define fw_status_wait_timeout(fw_st, long)0

Re: [PATCH v3 1/3] firmware_class: encapsulate firmware loading status

On 08/29/2016 11:50 AM, Daniel Wagner wrote: On 08/25/2016 07:50 PM, Luis R. Rodriguez wrote: +#else /* CONFIG_FW_LOADER_USER_HELPER */ + +static int loading_timeout = 60; +#define firmware_loading_timeout() (loading_timeout * HZ) + +#define fw_status_wait_timeout(fw_st, long)0

Re: [PATCH 1/3] perf/x86/intel/bts: Fix confused ordering of PMU callbacks

On Wed, Aug 24, 2016 at 05:15:54PM +0300, Alexander Shishkin wrote: > @@ -221,10 +245,13 @@ static void __bts_event_start(struct perf_event *event) > > /* >* local barrier to make sure that ds configuration made it > - * before we enable BTS > + * before we enable BTS and

Re: [PATCH 1/3] perf/x86/intel/bts: Fix confused ordering of PMU callbacks

On Wed, Aug 24, 2016 at 05:15:54PM +0300, Alexander Shishkin wrote: > @@ -221,10 +245,13 @@ static void __bts_event_start(struct perf_event *event) > > /* >* local barrier to make sure that ds configuration made it > - * before we enable BTS > + * before we enable BTS and

Re: [PATCH] mm: clarify COMPACTION Kconfig text

On Tue, Aug 23, 2016 at 10:09:17AM +0200, Michal Hocko wrote: > From: Michal Hocko > > The current wording of the COMPACTION Kconfig help text doesn't > emphasise that disabling COMPACTION might cripple the page allocator > which relies on the compaction quite heavily for high

Re: [PATCH] mm: clarify COMPACTION Kconfig text

On Tue, Aug 23, 2016 at 10:09:17AM +0200, Michal Hocko wrote: > From: Michal Hocko > > The current wording of the COMPACTION Kconfig help text doesn't > emphasise that disabling COMPACTION might cripple the page allocator > which relies on the compaction quite heavily for high order requests and

Re: [PATCHv6 1/3] usb: USB Type-C connector class

Hi Guenter, > > Overall this is quite vague and, especially for chargers, most of the time > > misses the point. > > > > I would really prefer if we could stay closer to the specification in this > > case, and not try to merge multiple orthogonal attributes into one. > > OK. So what would you

Re: [PATCHv6 1/3] usb: USB Type-C connector class

Hi Guenter, > > Overall this is quite vague and, especially for chargers, most of the time > > misses the point. > > > > I would really prefer if we could stay closer to the specification in this > > case, and not try to merge multiple orthogonal attributes into one. > > OK. So what would you

Re: [PATCH] ALSA: usb-audio: Add sample rate inquiry quirk for B850V3 CP2114

On Mon, 29 Aug 2016 16:10:03 +0200, Akshay Bhat wrote: > > Hi, > > On Fri, Aug 12, 2016 at 2:08 PM, Akshay Bhat wrote: > > From: Ken Lin > > > > Avoid getting sample rate on B850V3 CP2114 as it is unsupported and > > causes noisy "current rate

Re: [PATCH] ALSA: usb-audio: Add sample rate inquiry quirk for B850V3 CP2114

On Mon, 29 Aug 2016 16:10:03 +0200, Akshay Bhat wrote: > > Hi, > > On Fri, Aug 12, 2016 at 2:08 PM, Akshay Bhat wrote: > > From: Ken Lin > > > > Avoid getting sample rate on B850V3 CP2114 as it is unsupported and > > causes noisy "current rate is different from the runtime rate" messages > >

Re: [PATCH] ALSA: usb-audio: Add sample rate inquiry quirk for B850V3 CP2114

Hi, On Fri, Aug 12, 2016 at 2:08 PM, Akshay Bhat wrote: > From: Ken Lin > > Avoid getting sample rate on B850V3 CP2114 as it is unsupported and > causes noisy "current rate is different from the runtime rate" messages > when playback starts. >

Re: [PATCH] ALSA: usb-audio: Add sample rate inquiry quirk for B850V3 CP2114

Hi, On Fri, Aug 12, 2016 at 2:08 PM, Akshay Bhat wrote: > From: Ken Lin > > Avoid getting sample rate on B850V3 CP2114 as it is unsupported and > causes noisy "current rate is different from the runtime rate" messages > when playback starts. > > Signed-off-by: Ken Lin > Signed-off-by: Akshay

Re: [PATCH] thp: reduce usage of huge zero page's atomic counter

On Mon, Aug 29, 2016 at 07:17:58PM +0530, Anshuman Khandual wrote: > On 08/29/2016 02:23 PM, Aaron Lu wrote: > > On 08/29/2016 04:49 PM, Anshuman Khandual wrote: > >> > On 08/29/2016 12:01 PM, Aaron Lu wrote: > >>> >> The global zero page is used to satisfy an anonymous read fault. If > >>> >>

Re: [PATCH] thp: reduce usage of huge zero page's atomic counter

On Mon, Aug 29, 2016 at 07:17:58PM +0530, Anshuman Khandual wrote: > On 08/29/2016 02:23 PM, Aaron Lu wrote: > > On 08/29/2016 04:49 PM, Anshuman Khandual wrote: > >> > On 08/29/2016 12:01 PM, Aaron Lu wrote: > >>> >> The global zero page is used to satisfy an anonymous read fault. If > >>> >>

Re: [PATCH] Bluetooth: add WCNSS dependency for HCI driver

Hi Arnd, > The newly added bluetooth driver is based on the soc-specific support, > but lacks the obvious compile-time dependency on that: > > drivers/bluetooth/btqcomsmd.o: In function `btqcomsmd_probe': > btqcomsmd.c:(.text.btqcomsmd_probe+0x40): undefined reference to >

Re: [PATCH] Bluetooth: add WCNSS dependency for HCI driver

Hi Arnd, > The newly added bluetooth driver is based on the soc-specific support, > but lacks the obvious compile-time dependency on that: > > drivers/bluetooth/btqcomsmd.o: In function `btqcomsmd_probe': > btqcomsmd.c:(.text.btqcomsmd_probe+0x40): undefined reference to >

[RFC] spi: Prevent unexpected SPI time out due to arithmetic overflow

When reading SPI flash as MTD device, the transfer length is directly passed to the spi driver. If the requested data size exceeds 512KB, it will cause the time out calculation to overflow since transfer length is 32-bit unsigned integer. This issue is resolved by using 64-bit unsigned integer to

[RFC] spi: Prevent unexpected SPI time out due to arithmetic overflow

When reading SPI flash as MTD device, the transfer length is directly passed to the spi driver. If the requested data size exceeds 512KB, it will cause the time out calculation to overflow since transfer length is 32-bit unsigned integer. This issue is resolved by using 64-bit unsigned integer to

Re: [PATCH v2] mm: memcontrol: avoid unused function warning

On Wed, Aug 24, 2016 at 12:23:00PM +0200, Arnd Bergmann wrote: > A bugfix in v4.8-rc2 introduced a harmless warning when CONFIG_MEMCG_SWAP > is disabled but CONFIG_MEMCG is enabled: > > mm/memcontrol.c:4085:27: error: 'mem_cgroup_id_get_online' defined but not > used [-Werror=unused-function] >

Re: [PATCH v2] mm: memcontrol: avoid unused function warning

On Wed, Aug 24, 2016 at 12:23:00PM +0200, Arnd Bergmann wrote: > A bugfix in v4.8-rc2 introduced a harmless warning when CONFIG_MEMCG_SWAP > is disabled but CONFIG_MEMCG is enabled: > > mm/memcontrol.c:4085:27: error: 'mem_cgroup_id_get_online' defined but not > used [-Werror=unused-function] >

Re: [PATCH] arch: all: include: asm: bitops: Use bool instead of int for all bit test functions

On Mon, Aug 29, 2016 at 3:46 PM, Peter Zijlstra wrote: > On Mon, Aug 29, 2016 at 03:03:41PM +0200, Arnd Bergmann wrote: >> - Change the Documentation/atomic_ops.txt file accordingly > > Not sure that really matters; that document is so out of date its nearly > useless :-( >

Re: [PATCH] arch: all: include: asm: bitops: Use bool instead of int for all bit test functions

On Mon, Aug 29, 2016 at 3:46 PM, Peter Zijlstra wrote: > On Mon, Aug 29, 2016 at 03:03:41PM +0200, Arnd Bergmann wrote: >> - Change the Documentation/atomic_ops.txt file accordingly > > Not sure that really matters; that document is so out of date its nearly > useless :-( > > Rewriting it is

Re: [RESEND PATCH] ARM: tegra: fix erroneous address in dts

Hi, may I poke you again? Could you please revert this one (b5c86b7 upstream)? It was only required for 4.7.x where it got already applied. Thanks Ralf On 08/12/2016 07:26 PM, Ralf Ramsauer wrote: > On 08/10/2016 10:46 PM, Arnd Bergmann wrote: >> On Monday, July 18, 2016 11:58:02 AM CEST

Re: [RESEND PATCH] ARM: tegra: fix erroneous address in dts

Hi, may I poke you again? Could you please revert this one (b5c86b7 upstream)? It was only required for 4.7.x where it got already applied. Thanks Ralf On 08/12/2016 07:26 PM, Ralf Ramsauer wrote: > On 08/10/2016 10:46 PM, Arnd Bergmann wrote: >> On Monday, July 18, 2016 11:58:02 AM CEST

Re: [PATCH 2/2] sched/wait: avoid abort_exclusive_wait() in __wait_on_bit_lock()

On 08/29, Hillf Danton wrote: > > > > On 08/26, Oleg Nesterov wrote: > > __wait_on_bit_lock(wait_queue_head_t *wq, struct wait_bit_queue *q, > > wait_bit_action_f *action, unsigned mode) > > { > > int ret = 0; > > > > for (;;) { > >

Re: [PATCH 2/2] sched/wait: avoid abort_exclusive_wait() in __wait_on_bit_lock()

On 08/29, Hillf Danton wrote: > > > > On 08/26, Oleg Nesterov wrote: > > __wait_on_bit_lock(wait_queue_head_t *wq, struct wait_bit_queue *q, > > wait_bit_action_f *action, unsigned mode) > > { > > int ret = 0; > > > > for (;;) { > >

Re: DT connectors, thoughts

On Thu, Aug 25, 2016 at 06:38:41PM -0700, Stephen Boyd wrote: > Quoting David Gibson (2016-07-21 21:25:56) > > On Thu, Jul 21, 2016 at 02:15:57PM -0500, Rob Herring wrote: > > > On Mon, Jul 18, 2016 at 9:20 AM, David Gibson > > > wrote: > > > > > > I understand how

Re: DT connectors, thoughts

On Thu, Aug 25, 2016 at 06:38:41PM -0700, Stephen Boyd wrote: > Quoting David Gibson (2016-07-21 21:25:56) > > On Thu, Jul 21, 2016 at 02:15:57PM -0500, Rob Herring wrote: > > > On Mon, Jul 18, 2016 at 9:20 AM, David Gibson > > > wrote: > > > > > > I understand how you are using i2c alias, but

Re: [PATCHv6 0/3] USB Type-C Connector class

On Mon, Aug 29, 2016 at 06:06:39AM -0700, Guenter Roeck wrote: > On 08/29/2016 05:36 AM, Heikki Krogerus wrote: > > The USB Type-C class is meant to provide unified interface to the > > userspace to present the USB Type-C ports in a system. > > > The subject says "v6". True. I used the wrong

Re: [PATCH] thp: reduce usage of huge zero page's atomic counter

On 08/29/2016 02:23 PM, Aaron Lu wrote: > On 08/29/2016 04:49 PM, Anshuman Khandual wrote: >> > On 08/29/2016 12:01 PM, Aaron Lu wrote: >>> >> The global zero page is used to satisfy an anonymous read fault. If >>> >> THP(Transparent HugePage) is enabled then the global huge zero page is >>> >>

Re: [PATCHv6 0/3] USB Type-C Connector class

On Mon, Aug 29, 2016 at 06:06:39AM -0700, Guenter Roeck wrote: > On 08/29/2016 05:36 AM, Heikki Krogerus wrote: > > The USB Type-C class is meant to provide unified interface to the > > userspace to present the USB Type-C ports in a system. > > > The subject says "v6". True. I used the wrong

Re: [PATCH] thp: reduce usage of huge zero page's atomic counter

On 08/29/2016 02:23 PM, Aaron Lu wrote: > On 08/29/2016 04:49 PM, Anshuman Khandual wrote: >> > On 08/29/2016 12:01 PM, Aaron Lu wrote: >>> >> The global zero page is used to satisfy an anonymous read fault. If >>> >> THP(Transparent HugePage) is enabled then the global huge zero page is >>> >>

Re: [PATCH] arch: all: include: asm: bitops: Use bool instead of int for all bit test functions

On Mon, Aug 29, 2016 at 03:03:41PM +0200, Arnd Bergmann wrote: > - Change the Documentation/atomic_ops.txt file accordingly Not sure that really matters; that document is so out of date its nearly useless :-( Rewriting it is somewhere on the TODO list...

Re: [PATCH] arch: all: include: asm: bitops: Use bool instead of int for all bit test functions

On Mon, Aug 29, 2016 at 03:03:41PM +0200, Arnd Bergmann wrote: > - Change the Documentation/atomic_ops.txt file accordingly Not sure that really matters; that document is so out of date its nearly useless :-( Rewriting it is somewhere on the TODO list...

Re: what is the purpose of SLAB and SLUB

On Fri 26-08-16 13:47:47, Andi Kleen wrote: > Christoph Lameter writes: > > > >> If you want to rework the VM to use a larger fundamental unit, track > >> sub-units where required and deal with the internal fragmentation issues > >> then by all means go ahead and deal with it. > >

Re: what is the purpose of SLAB and SLUB

On Fri 26-08-16 13:47:47, Andi Kleen wrote: > Christoph Lameter writes: > > > >> If you want to rework the VM to use a larger fundamental unit, track > >> sub-units where required and deal with the internal fragmentation issues > >> then by all means go ahead and deal with it. > > > > Hmmm... The

Re: [PATCH 1/4] spinlock: Document memory barrier rules

On Mon, Aug 29, 2016 at 02:54:54PM +0200, Manfred Spraul wrote: > Hi Peter, > > On 08/29/2016 12:48 PM, Peter Zijlstra wrote: > >On Sun, Aug 28, 2016 at 01:56:13PM +0200, Manfred Spraul wrote: > >>Right now, the spinlock machinery tries to guarantee barriers even for > >>unorthodox locking cases,

Re: [PATCH 1/4] spinlock: Document memory barrier rules

On Mon, Aug 29, 2016 at 02:54:54PM +0200, Manfred Spraul wrote: > Hi Peter, > > On 08/29/2016 12:48 PM, Peter Zijlstra wrote: > >On Sun, Aug 28, 2016 at 01:56:13PM +0200, Manfred Spraul wrote: > >>Right now, the spinlock machinery tries to guarantee barriers even for > >>unorthodox locking cases,

Re: [PATCHv6 1/3] usb: USB Type-C connector class

On Mon, Aug 29, 2016 at 06:04:52AM -0700, Guenter Roeck wrote: > Heikki, > > On 08/26/2016 07:07 AM, Heikki Krogerus wrote: > > > > > > > > +What: /sys/class/typec/-partner/type > > > > > > +Date: June 2016 > > > > > > +Contact: Heikki Krogerus

Re: [PATCHv6 1/3] usb: USB Type-C connector class

On Mon, Aug 29, 2016 at 06:04:52AM -0700, Guenter Roeck wrote: > Heikki, > > On 08/26/2016 07:07 AM, Heikki Krogerus wrote: > > > > > > > > +What: /sys/class/typec/-partner/type > > > > > > +Date: June 2016 > > > > > > +Contact: Heikki Krogerus > > > > > > +Description:

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