Re: [RFC PATCH 1/5] mm/page_alloc: always add freeing page at the tail of the buddy list

On Wed, Oct 26, 2016 at 01:50:37PM +0800, Xishi Qiu wrote: > On 2016/10/26 12:37, Joonsoo Kim wrote: > > > On Mon, Oct 17, 2016 at 05:21:54PM +0800, Xishi Qiu wrote: > >> On 2016/10/13 16:08, js1...@gmail.com wrote: > >> > >>> From: Joonsoo Kim > >>> > >>> Currently,

Re: [RFC PATCH 1/5] mm/page_alloc: always add freeing page at the tail of the buddy list

On Wed, Oct 26, 2016 at 01:50:37PM +0800, Xishi Qiu wrote: > On 2016/10/26 12:37, Joonsoo Kim wrote: > > > On Mon, Oct 17, 2016 at 05:21:54PM +0800, Xishi Qiu wrote: > >> On 2016/10/13 16:08, js1...@gmail.com wrote: > >> > >>> From: Joonsoo Kim > >>> > >>> Currently, freeing page can stay longer

Re: [RFC PATCH 1/5] mm/page_alloc: always add freeing page at the tail of the buddy list

On 2016/10/26 12:37, Joonsoo Kim wrote: > On Mon, Oct 17, 2016 at 05:21:54PM +0800, Xishi Qiu wrote: >> On 2016/10/13 16:08, js1...@gmail.com wrote: >> >>> From: Joonsoo Kim >>> >>> Currently, freeing page can stay longer in the buddy list if next higher >>> order page is

Re: [RFC PATCH 1/5] mm/page_alloc: always add freeing page at the tail of the buddy list

On 2016/10/26 12:37, Joonsoo Kim wrote: > On Mon, Oct 17, 2016 at 05:21:54PM +0800, Xishi Qiu wrote: >> On 2016/10/13 16:08, js1...@gmail.com wrote: >> >>> From: Joonsoo Kim >>> >>> Currently, freeing page can stay longer in the buddy list if next higher >>> order page is in the buddy list in

Re: [PATCH 1/2] x86/io: add interface to reserve io memtype for a resource range. (v1.1)

On Tue, Oct 25, 2016 at 07:31:29PM +0200, Luis R. Rodriguez wrote: > On Mon, Oct 24, 2016 at 04:31:45PM +1000, Dave Airlie wrote: > > A recent change to the mm code in: > > 87744ab3832b83ba71b931f86f9cfdb000d07da5 > > mm: fix cache mode tracking in vm_insert_mixed() > > > > started enforcing

Re: [PATCH 1/2] x86/io: add interface to reserve io memtype for a resource range. (v1.1)

On Tue, Oct 25, 2016 at 07:31:29PM +0200, Luis R. Rodriguez wrote: > On Mon, Oct 24, 2016 at 04:31:45PM +1000, Dave Airlie wrote: > > A recent change to the mm code in: > > 87744ab3832b83ba71b931f86f9cfdb000d07da5 > > mm: fix cache mode tracking in vm_insert_mixed() > > > > started enforcing

[tip:x86/asm] mm/page_alloc: Remove kernel address exposure in free_reserved_area()

Commit-ID: adb1fe9ae2ee6ef6bc10f3d5a588020e7664dfa7 Gitweb: http://git.kernel.org/tip/adb1fe9ae2ee6ef6bc10f3d5a588020e7664dfa7 Author: Josh Poimboeuf AuthorDate: Tue, 25 Oct 2016 09:51:14 -0500 Committer: Ingo Molnar CommitDate: Tue, 25 Oct 2016

[tip:x86/asm] mm/page_alloc: Remove kernel address exposure in free_reserved_area()

Commit-ID: adb1fe9ae2ee6ef6bc10f3d5a588020e7664dfa7 Gitweb: http://git.kernel.org/tip/adb1fe9ae2ee6ef6bc10f3d5a588020e7664dfa7 Author: Josh Poimboeuf AuthorDate: Tue, 25 Oct 2016 09:51:14 -0500 Committer: Ingo Molnar CommitDate: Tue, 25 Oct 2016 18:40:37 +0200 mm/page_alloc: Remove

[tip:x86/asm] x86/dumpstack: Remove raw stack dump

Commit-ID: 0ee1dd9f5e7eae4e55f95935b72d4beecb03de9c Gitweb: http://git.kernel.org/tip/0ee1dd9f5e7eae4e55f95935b72d4beecb03de9c Author: Josh Poimboeuf AuthorDate: Tue, 25 Oct 2016 09:51:13 -0500 Committer: Ingo Molnar CommitDate: Tue, 25 Oct 2016

[tip:x86/asm] x86/dumpstack: Remove raw stack dump

Commit-ID: 0ee1dd9f5e7eae4e55f95935b72d4beecb03de9c Gitweb: http://git.kernel.org/tip/0ee1dd9f5e7eae4e55f95935b72d4beecb03de9c Author: Josh Poimboeuf AuthorDate: Tue, 25 Oct 2016 09:51:13 -0500 Committer: Ingo Molnar CommitDate: Tue, 25 Oct 2016 18:40:37 +0200 x86/dumpstack: Remove

[tip:x86/asm] x86/dumpstack: Remove kernel text addresses from stack dump

Commit-ID: bb5e5ce545f2031c96f7901cd8d1698ea3ca4c9c Gitweb: http://git.kernel.org/tip/bb5e5ce545f2031c96f7901cd8d1698ea3ca4c9c Author: Josh Poimboeuf AuthorDate: Tue, 25 Oct 2016 09:51:12 -0500 Committer: Ingo Molnar CommitDate: Tue, 25 Oct 2016

[tip:x86/asm] x86/dumpstack: Remove kernel text addresses from stack dump

Commit-ID: bb5e5ce545f2031c96f7901cd8d1698ea3ca4c9c Gitweb: http://git.kernel.org/tip/bb5e5ce545f2031c96f7901cd8d1698ea3ca4c9c Author: Josh Poimboeuf AuthorDate: Tue, 25 Oct 2016 09:51:12 -0500 Committer: Ingo Molnar CommitDate: Tue, 25 Oct 2016 18:40:37 +0200 x86/dumpstack: Remove

[tip:x86/asm] scripts/faddr2line: Fix "size mismatch" error

Commit-ID: efdb4167e676aaba7505bec739785b76e206cb45 Gitweb: http://git.kernel.org/tip/efdb4167e676aaba7505bec739785b76e206cb45 Author: Josh Poimboeuf AuthorDate: Tue, 25 Oct 2016 09:51:11 -0500 Committer: Ingo Molnar CommitDate: Tue, 25 Oct 2016

[tip:x86/asm] scripts/faddr2line: Fix "size mismatch" error

Commit-ID: efdb4167e676aaba7505bec739785b76e206cb45 Gitweb: http://git.kernel.org/tip/efdb4167e676aaba7505bec739785b76e206cb45 Author: Josh Poimboeuf AuthorDate: Tue, 25 Oct 2016 09:51:11 -0500 Committer: Ingo Molnar CommitDate: Tue, 25 Oct 2016 18:40:37 +0200 scripts/faddr2line: Fix

[PATCH v2 3/3] kernel/smp: Tell the user we're bringing up secondary CPUs

Currently we don't print anything before starting to bring up secondary CPUs. This can be confusing if it takes a long time to bring up the secondaries, or if the kernel crashes while doing so and produces no further output. On x86 they work around this by detecting when the first secondary CPU

[PATCH v2 3/3] kernel/smp: Tell the user we're bringing up secondary CPUs

Currently we don't print anything before starting to bring up secondary CPUs. This can be confusing if it takes a long time to bring up the secondaries, or if the kernel crashes while doing so and produces no further output. On x86 they work around this by detecting when the first secondary CPU

[PATCH v2 2/3] kernel/smp: Make the SMP boot message common on all arches

Currently after bringing up secondary CPUs all arches print "Brought up %d CPUs". On x86 they also print the number of nodes that were brought online. It would be nice to also print the number of nodes on other arches. Although we could override smp_announce() on the other ~10 NUMA aware arches,

[PATCH v2 2/3] kernel/smp: Make the SMP boot message common on all arches

Currently after bringing up secondary CPUs all arches print "Brought up %d CPUs". On x86 they also print the number of nodes that were brought online. It would be nice to also print the number of nodes on other arches. Although we could override smp_announce() on the other ~10 NUMA aware arches,

[PATCH v2 1/3] kernel/smp: Define pr_fmt() for smp.c

This makes all our pr_xxx()'s start with "smp: ", which helps pin down where they come from and generally looks nice. There is actually only one pr_xxx() use in smp.c at the moment, but we will add some more in the next commit. Suggested-by: Borislav Petkov Signed-off-by: Michael

[PATCH v2 1/3] kernel/smp: Define pr_fmt() for smp.c

This makes all our pr_xxx()'s start with "smp: ", which helps pin down where they come from and generally looks nice. There is actually only one pr_xxx() use in smp.c at the moment, but we will add some more in the next commit. Suggested-by: Borislav Petkov Signed-off-by: Michael Ellerman ---

Re: [PATCH 1/2] kernel/smp: Make the SMP boot message common on all arches

Ingo Molnar writes: > * Michael Ellerman wrote: >> @@ -564,8 +560,11 @@ void __init smp_init(void) >> cpu_up(cpu); >> } >> >> +num_nodes = num_online_nodes(); >> +pr_info("smp: Brought up %d node%s, %d CPUs\n", >> +

Re: [PATCH 1/2] kernel/smp: Make the SMP boot message common on all arches

Ingo Molnar writes: > * Michael Ellerman wrote: >> @@ -564,8 +560,11 @@ void __init smp_init(void) >> cpu_up(cpu); >> } >> >> +num_nodes = num_online_nodes(); >> +pr_info("smp: Brought up %d node%s, %d CPUs\n", >> +num_nodes, (num_nodes > 1 ? "s" :

Re: [PATCH 1/2] kernel/smp: Make the SMP boot message common on all arches

Borislav Petkov writes: > On Thu, Oct 13, 2016 at 07:55:19PM +1100, Michael Ellerman wrote: >> @@ -564,8 +560,11 @@ void __init smp_init(void) >> cpu_up(cpu); >> } >> >> +num_nodes = num_online_nodes(); >> +pr_info("smp: Brought up %d node%s, %d

Re: [PATCH 1/2] kernel/smp: Make the SMP boot message common on all arches

Borislav Petkov writes: > On Thu, Oct 13, 2016 at 07:55:19PM +1100, Michael Ellerman wrote: >> @@ -564,8 +560,11 @@ void __init smp_init(void) >> cpu_up(cpu); >> } >> >> +num_nodes = num_online_nodes(); >> +pr_info("smp: Brought up %d node%s, %d CPUs\n", >> +

[PATCH] arm64: defconfig: Enable DRM DU and V4L2 FCP + VSP modules

From: Magnus Damm Extend the ARM64 defconfig to enable the DU DRM device as module together with required dependencies of V4L2 FCP and VSP modules. This enables VGA output on the r8a7795 Salvator-X board. Signed-off-by: Magnus Damm ---

[PATCH] arm64: defconfig: Enable DRM DU and V4L2 FCP + VSP modules

From: Magnus Damm Extend the ARM64 defconfig to enable the DU DRM device as module together with required dependencies of V4L2 FCP and VSP modules. This enables VGA output on the r8a7795 Salvator-X board. Signed-off-by: Magnus Damm --- Written against next-20161026

[PATCH 3/3] x86/vmware: Add paravirt sched clock

Set pv_time_ops.sched_clock to vmware_sched_clock(). It is simplified version of native_sched_clock() without ring buffer of mult/shift/offset triplets and preempt toggling. Since VMware hypervisor provides constant tsc we can use constant mult/shift/offset triplet calculated at boot time.

[PATCH 3/3] x86/vmware: Add paravirt sched clock

Set pv_time_ops.sched_clock to vmware_sched_clock(). It is simplified version of native_sched_clock() without ring buffer of mult/shift/offset triplets and preempt toggling. Since VMware hypervisor provides constant tsc we can use constant mult/shift/offset triplet calculated at boot time.

[PATCH 2/3] x86/vmware: Add basic paravirt ops support

Add basic paravirt support: 1. set pv_info.name to "VMware" to have proper boot log message Booting paravirtualized kernel on VMware instead of "... on bare hardware" 2. set pv_cpu_ops.io_delay() to empty function - paravirt_nop() to avoid vm-exits on IO delays. Signed-off-by:

[PATCH 2/3] x86/vmware: Add basic paravirt ops support

Add basic paravirt support: 1. set pv_info.name to "VMware" to have proper boot log message Booting paravirtualized kernel on VMware instead of "... on bare hardware" 2. set pv_cpu_ops.io_delay() to empty function - paravirt_nop() to avoid vm-exits on IO delays. Signed-off-by:

lening bieden 3%

Goede dag, Dit is Lloyd's TSB Bank plc leningen aan te bieden. Lloyds TSB biedt flexibele en betaalbare leningen voor welk doel u te helpen uw doelen te bereiken. we lening tegen lage rente van 3%. Hier zijn een aantal belangrijke kenmerken van de persoonlijke lening aangeboden door

lening bieden 3%

Goede dag, Dit is Lloyd's TSB Bank plc leningen aan te bieden. Lloyds TSB biedt flexibele en betaalbare leningen voor welk doel u te helpen uw doelen te bereiken. we lening tegen lage rente van 3%. Hier zijn een aantal belangrijke kenmerken van de persoonlijke lening aangeboden door

[PATCH 0/3] x86/vmware guest improvements

This patchset includes several VMware guest improvements: Alexey Makhalov (3): x86/vmware: Use tsc_khz value for calibrate_cpu() x86/vmware: Add basic paravirt ops support x86/vmware: Add paravirt sched clock Documentation/kernel-parameters.txt | 4 +++ arch/x86/kernel/cpu/vmware.c

[PATCH 0/3] x86/vmware guest improvements

This patchset includes several VMware guest improvements: Alexey Makhalov (3): x86/vmware: Use tsc_khz value for calibrate_cpu() x86/vmware: Add basic paravirt ops support x86/vmware: Add paravirt sched clock Documentation/kernel-parameters.txt | 4 +++ arch/x86/kernel/cpu/vmware.c

[PATCH 1/3] x86/vmware: Use tsc_khz value for calibrate_cpu()

After aa297292d708, there are separate native calibrations for cpu_khz and tsc_khz. The code sets x86_platform.calibrate_cpu to native_calibrate_cpu() which looks in cpuid leaf 0x16 or msrs for the cpu frequency. Since we keep the tsc_khz constant (even after vmotion), the cpu_khz and tsc_khz may

[PATCH 1/3] x86/vmware: Use tsc_khz value for calibrate_cpu()

After aa297292d708, there are separate native calibrations for cpu_khz and tsc_khz. The code sets x86_platform.calibrate_cpu to native_calibrate_cpu() which looks in cpuid leaf 0x16 or msrs for the cpu frequency. Since we keep the tsc_khz constant (even after vmotion), the cpu_khz and tsc_khz may

RE: [PATCH 0/9] staging: fsl-mc: move bus driver out of staging, add dpio

> -Original Message- > From: Alexander Graf [mailto:ag...@suse.de] > Sent: Monday, October 24, 2016 9:34 AM > To: Stuart Yoder ; gre...@linuxfoundation.org > Cc: German Rivera ; de...@driverdev.osuosl.org; > linux-kernel@vger.kernel.org; >

RE: [PATCH 0/9] staging: fsl-mc: move bus driver out of staging, add dpio

> -Original Message- > From: Alexander Graf [mailto:ag...@suse.de] > Sent: Monday, October 24, 2016 9:34 AM > To: Stuart Yoder ; gre...@linuxfoundation.org > Cc: German Rivera ; de...@driverdev.osuosl.org; > linux-kernel@vger.kernel.org; > a...@arndb.de; Leo Li > Subject: Re: [PATCH

Re: [RFC 8/8] mm: Add N_COHERENT_DEVICE node type into node_states[]

On 10/25/2016 12:52 PM, Balbir Singh wrote: > > > On 24/10/16 15:31, Anshuman Khandual wrote: >> Add a new member N_COHERENT_DEVICE into node_states[] nodemask array to >> enlist all those nodes which contain only coherent device memory. Also >> creates a new sysfs interface

Re: [RFC 8/8] mm: Add N_COHERENT_DEVICE node type into node_states[]

On 10/25/2016 12:52 PM, Balbir Singh wrote: > > > On 24/10/16 15:31, Anshuman Khandual wrote: >> Add a new member N_COHERENT_DEVICE into node_states[] nodemask array to >> enlist all those nodes which contain only coherent device memory. Also >> creates a new sysfs interface

Re: [RFC PATCH 2/5] mm/page_alloc: use smallest fallback page first in movable allocation

On Fri, Oct 14, 2016 at 12:52:26PM +0200, Vlastimil Babka wrote: > On 10/14/2016 03:26 AM, Joonsoo Kim wrote: > >On Thu, Oct 13, 2016 at 11:12:10AM +0200, Vlastimil Babka wrote: > >>On 10/13/2016 10:08 AM, js1...@gmail.com wrote: > >>>From: Joonsoo Kim > >>> > >>>When we

Re: [RFC PATCH 2/5] mm/page_alloc: use smallest fallback page first in movable allocation

On Fri, Oct 14, 2016 at 12:52:26PM +0200, Vlastimil Babka wrote: > On 10/14/2016 03:26 AM, Joonsoo Kim wrote: > >On Thu, Oct 13, 2016 at 11:12:10AM +0200, Vlastimil Babka wrote: > >>On 10/13/2016 10:08 AM, js1...@gmail.com wrote: > >>>From: Joonsoo Kim > >>> > >>>When we try to find freepage in

Re: [RFC PATCH 1/5] mm/page_alloc: always add freeing page at the tail of the buddy list

On Mon, Oct 17, 2016 at 05:21:54PM +0800, Xishi Qiu wrote: > On 2016/10/13 16:08, js1...@gmail.com wrote: > > > From: Joonsoo Kim > > > > Currently, freeing page can stay longer in the buddy list if next higher > > order page is in the buddy list in order to help

Re: [RFC PATCH 1/5] mm/page_alloc: always add freeing page at the tail of the buddy list

On Mon, Oct 17, 2016 at 05:21:54PM +0800, Xishi Qiu wrote: > On 2016/10/13 16:08, js1...@gmail.com wrote: > > > From: Joonsoo Kim > > > > Currently, freeing page can stay longer in the buddy list if next higher > > order page is in the buddy list in order to help coalescence. However, > > it

Re: [kernel-hardening] [PATCH] module: extend 'rodata=off' boot cmdline parameter to module mappings

Rusty, Jessica On Wed, Oct 26, 2016 at 10:43:32AM +1030, Rusty Russell wrote: > AKASHI Takahiro writes: > > On Thu, Oct 20, 2016 at 01:48:15PM -0700, Kees Cook wrote: > >> On Wed, Oct 19, 2016 at 11:24 PM, AKASHI Takahiro > >> wrote: > >>

Re: [kernel-hardening] [PATCH] module: extend 'rodata=off' boot cmdline parameter to module mappings

Rusty, Jessica On Wed, Oct 26, 2016 at 10:43:32AM +1030, Rusty Russell wrote: > AKASHI Takahiro writes: > > On Thu, Oct 20, 2016 at 01:48:15PM -0700, Kees Cook wrote: > >> On Wed, Oct 19, 2016 at 11:24 PM, AKASHI Takahiro > >> wrote: > >> > The current "rodata=off" parameter disables read-only

Re: [PATCH v6 3/6] mm/cma: populate ZONE_CMA

On Tue, Oct 18, 2016 at 05:27:30PM +0900, Joonsoo Kim wrote: > On Tue, Oct 18, 2016 at 09:42:57AM +0200, Vlastimil Babka wrote: > > On 10/14/2016 05:03 AM, js1...@gmail.com wrote: > > >@@ -145,6 +145,35 @@ static int __init cma_activate_area(struct cma *cma) > > > static int __init

Re: [PATCH v6 3/6] mm/cma: populate ZONE_CMA

On Tue, Oct 18, 2016 at 05:27:30PM +0900, Joonsoo Kim wrote: > On Tue, Oct 18, 2016 at 09:42:57AM +0200, Vlastimil Babka wrote: > > On 10/14/2016 05:03 AM, js1...@gmail.com wrote: > > >@@ -145,6 +145,35 @@ static int __init cma_activate_area(struct cma *cma) > > > static int __init

Re: [PATCH v3] x86/msr: Add write msr notrace to avoid the debug codes splash

2016-10-25 19:15 GMT+08:00 Paolo Bonzini : > > > On 25/10/2016 04:58, Wanpeng Li wrote: >> @@ -319,7 +319,7 @@ static void kvm_guest_apic_eoi_write(u32 reg, u32 val) > > This needs to be notrace too. Ok, I just sent out a new version for this. Regards, Wanpeng Li

Re: [PATCH v3] x86/msr: Add write msr notrace to avoid the debug codes splash

2016-10-25 19:15 GMT+08:00 Paolo Bonzini : > > > On 25/10/2016 04:58, Wanpeng Li wrote: >> @@ -319,7 +319,7 @@ static void kvm_guest_apic_eoi_write(u32 reg, u32 val) > > This needs to be notrace too. Ok, I just sent out a new version for this. Regards, Wanpeng Li

Re: [RFC PATCH] xhci: do not halt the secondary HCD

On Tue, Sep 20, 2016 at 5:56 PM, Mathias Nyman wrote: > Quick Googling shows that that TI TUSB 73x0 USB3.0 xHCI host has an issue > with halting. > > Errata says host needs 125us to 1ms between the last control transfer and > clearing the run/stop bit. (halting the

Re: [RFC PATCH] xhci: do not halt the secondary HCD

On Tue, Sep 20, 2016 at 5:56 PM, Mathias Nyman wrote: > Quick Googling shows that that TI TUSB 73x0 USB3.0 xHCI host has an issue > with halting. > > Errata says host needs 125us to 1ms between the last control transfer and > clearing the run/stop bit. (halting the host) > > Suggested workaround

[PATCH v4] x86/msr: Add write msr notrace to avoid the debug codes splash

From: Wanpeng Li As Peterz pointed out: | The thing is, many many smp_reschedule_interrupt() invocations don't | actually execute anything much at all and are only send to tickle the | return to user path (which does the actual preemption). This patch add write msr

[PATCH v4] x86/msr: Add write msr notrace to avoid the debug codes splash

From: Wanpeng Li As Peterz pointed out: | The thing is, many many smp_reschedule_interrupt() invocations don't | actually execute anything much at all and are only send to tickle the | return to user path (which does the actual preemption). This patch add write msr notrace to avoid the debug

Re: [PATCHv4 18/43] block: define BIO_MAX_PAGES to HPAGE_PMD_NR if huge page cache enabled

On Oct 25, 2016, at 6:54 AM, Kirill A. Shutemov wrote: > > On Tue, Oct 25, 2016 at 12:21:22AM -0700, Christoph Hellwig wrote: >> On Tue, Oct 25, 2016 at 03:13:17AM +0300, Kirill A. Shutemov wrote: >>> We are going to do IO a huge page a time. So we need BIO_MAX_PAGES to be

Re: [PATCHv4 18/43] block: define BIO_MAX_PAGES to HPAGE_PMD_NR if huge page cache enabled

On Oct 25, 2016, at 6:54 AM, Kirill A. Shutemov wrote: > > On Tue, Oct 25, 2016 at 12:21:22AM -0700, Christoph Hellwig wrote: >> On Tue, Oct 25, 2016 at 03:13:17AM +0300, Kirill A. Shutemov wrote: >>> We are going to do IO a huge page a time. So we need BIO_MAX_PAGES to be >>> at least

RE: [PATCH 1/3] clk: qcom: gdsc: Add support for gdscs with HW control

Hi Stan, >Hi Sricharan, > >On 10/24/2016 01:18 PM, Sricharan R wrote: >> From: Rajendra Nayak >> >> Some GDSCs might support a HW control mode, where in the power >> domain (gdsc) is brought in and out of low power state (while >> unsued) without any SW assistance, saving

RE: [PATCH 1/3] clk: qcom: gdsc: Add support for gdscs with HW control

Hi Stan, >Hi Sricharan, > >On 10/24/2016 01:18 PM, Sricharan R wrote: >> From: Rajendra Nayak >> >> Some GDSCs might support a HW control mode, where in the power >> domain (gdsc) is brought in and out of low power state (while >> unsued) without any SW assistance, saving power. >> Such GDSCs

[PATCH] drm: rcar-du: Fix R-Car Gen3 crash when VSP is disabled

From: Magnus Damm For the DU to operate on R-Car Gen3 hardware a combination of DU and VSP devices are required. Since the DU driver also supports earlier generations hardware the VSP portion is enabled via Kconfig. The arm64 defconfig is as of v4.9-rc1 having the DU

[PATCH] drm: rcar-du: Fix R-Car Gen3 crash when VSP is disabled

From: Magnus Damm For the DU to operate on R-Car Gen3 hardware a combination of DU and VSP devices are required. Since the DU driver also supports earlier generations hardware the VSP portion is enabled via Kconfig. The arm64 defconfig is as of v4.9-rc1 having the DU driver enabled as a module,

Re: [PATCH V2 4/8] PM / OPP: Pass struct dev_pm_opp_supply to _set_opp_voltage()

On 25-10-16, 13:26, Stephen Boyd wrote: > For things like AVS we'll probably want to do that, although it's > sort of funny because replacing RCU with rw-locks is the opposite > direction most people go. Yes, that would be very funny :) > With AVS we would be updating the > voltage(s) in use for

Re: [PATCH V2 4/8] PM / OPP: Pass struct dev_pm_opp_supply to _set_opp_voltage()

On 25-10-16, 13:26, Stephen Boyd wrote: > For things like AVS we'll probably want to do that, although it's > sort of funny because replacing RCU with rw-locks is the opposite > direction most people go. Yes, that would be very funny :) > With AVS we would be updating the > voltage(s) in use for

Re: [PATCH 1/3] usb: dwc3: host: inherit dma configuration from parent dev

On Tue, Oct 25, 2016 at 04:26:26PM +0530, Sriram Dash wrote: > For xhci-hcd platform device, all the DMA parameters are not configured > properly, notably dma ops for dwc3 devices. > > The idea here is that you pass in the parent of_node along with the child > device pointer, so it would behave

Re: [PATCH 1/3] usb: dwc3: host: inherit dma configuration from parent dev

On Tue, Oct 25, 2016 at 04:26:26PM +0530, Sriram Dash wrote: > For xhci-hcd platform device, all the DMA parameters are not configured > properly, notably dma ops for dwc3 devices. > > The idea here is that you pass in the parent of_node along with the child > device pointer, so it would behave

Re: [PATCH V2 0/8] PM / OPP: Multiple regulator support

On 25-10-16, 16:13, Dave Gerlach wrote: > I think what you have shared below is a good safety check but if I rename > the regulator properties in the DT for the cpu (to vdd and vbb, meaning > cpufreq detects no regulator) and do *not* call dev_pm_opp_set_regulators > before cpufreq-dt probes we

Re: [PATCH V2 0/8] PM / OPP: Multiple regulator support

On 25-10-16, 16:13, Dave Gerlach wrote: > I think what you have shared below is a good safety check but if I rename > the regulator properties in the DT for the cpu (to vdd and vbb, meaning > cpufreq detects no regulator) and do *not* call dev_pm_opp_set_regulators > before cpufreq-dt probes we

Re: [PATCH V2 0/6] ARM64: Uprobe support added

Hi Catalin, Please let me know if everything else other than is_trap_insn() looks fine to you. May be I can work well in time. It would be great if we can make it into v4.9. ~Pratyush On Tue, Sep 27, 2016 at 1:17 PM, Pratyush Anand wrote: > Changes since v1: > * Exposed

Re: [PATCH V2 0/6] ARM64: Uprobe support added

Hi Catalin, Please let me know if everything else other than is_trap_insn() looks fine to you. May be I can work well in time. It would be great if we can make it into v4.9. ~Pratyush On Tue, Sep 27, 2016 at 1:17 PM, Pratyush Anand wrote: > Changes since v1: > * Exposed sync_icache_aliases()

Re: [PATCH 1/2] mm/memblock: prepare a capability to support memblock near alloc

On 2016/10/25 21:23, Michal Hocko wrote: > On Tue 25-10-16 10:59:17, Zhen Lei wrote: >> If HAVE_MEMORYLESS_NODES is selected, and some memoryless numa nodes are >> actually exist. The percpu variable areas and numa control blocks of that >> memoryless numa nodes need to be allocated from the

Re: [PATCH 1/2] mm/memblock: prepare a capability to support memblock near alloc

On 2016/10/25 21:23, Michal Hocko wrote: > On Tue 25-10-16 10:59:17, Zhen Lei wrote: >> If HAVE_MEMORYLESS_NODES is selected, and some memoryless numa nodes are >> actually exist. The percpu variable areas and numa control blocks of that >> memoryless numa nodes need to be allocated from the

[PATCH v6 4/5] ARM: DTS: da850: Add cfgchip syscon node

Add a syscon node for the SoC CFGCHIPn registers. This is needed for the new usb phy driver. Signed-off-by: David Lechner --- arch/arm/boot/dts/da850.dtsi | 4 1 file changed, 4 insertions(+) diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi

[PATCH v6 0/5] da8xx USB PHY platform devices and clocks

It has been almost 6 months since the v5 submission, so here is a recap: * There were a number of phy and usb dependencies that were submitted separately. * The last of the usb dependencies has finally made its way into linux-next today. * This series was recently included in "[PATCH/RFT v2

[PATCH v6 1/5] ARM: davinci: da8xx: add usb phy clocks

Up to this point, the USB phy clock configuration was handled manually in the board files and in the usb drivers. This adds proper clocks so that the usb drivers can use clk_get and clk_enable and not have to worry about the details. Also, the related code is removed from the board files and

[PATCH v6 3/5] ARM: davinci: da8xx: Add USB PHY platform declaration

There is now a proper phy driver for the DA8xx SoC USB PHY. This adds the platform device declarations needed to use it. Signed-off-by: David Lechner --- da8xx-usb-phy device id is changed to -1 since there is only one da8xx-usb-phy device.

[PATCH v6 4/5] ARM: DTS: da850: Add cfgchip syscon node

Add a syscon node for the SoC CFGCHIPn registers. This is needed for the new usb phy driver. Signed-off-by: David Lechner --- arch/arm/boot/dts/da850.dtsi | 4 1 file changed, 4 insertions(+) diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi index f79e1b9..6bbf20d

[PATCH v6 0/5] da8xx USB PHY platform devices and clocks

It has been almost 6 months since the v5 submission, so here is a recap: * There were a number of phy and usb dependencies that were submitted separately. * The last of the usb dependencies has finally made its way into linux-next today. * This series was recently included in "[PATCH/RFT v2

[PATCH v6 1/5] ARM: davinci: da8xx: add usb phy clocks

Up to this point, the USB phy clock configuration was handled manually in the board files and in the usb drivers. This adds proper clocks so that the usb drivers can use clk_get and clk_enable and not have to worry about the details. Also, the related code is removed from the board files and

[PATCH v6 3/5] ARM: davinci: da8xx: Add USB PHY platform declaration

There is now a proper phy driver for the DA8xx SoC USB PHY. This adds the platform device declarations needed to use it. Signed-off-by: David Lechner --- da8xx-usb-phy device id is changed to -1 since there is only one da8xx-usb-phy device. arch/arm/mach-davinci/board-da830-evm.c | 28

[PATCH v6 2/5] ARM: davinci: da8xx: Add CFGCHIP syscon platform declaration.

The CFGCHIP registers are used by a number of devices, so using a syscon device to share them. The first consumer of this will by the phy-da8xx-usb driver. Signed-off-by: David Lechner --- syscon device id is changed to -1 since there is only one syscon device.

[PATCH v6 5/5] ARM: DTS: da850: Add usb phy node

Add a node for the new usb phy driver. Signed-off-by: David Lechner --- arch/arm/boot/dts/da850.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi index 6bbf20d..33fcdce 100644 ---

[PATCH v6 2/5] ARM: davinci: da8xx: Add CFGCHIP syscon platform declaration.

The CFGCHIP registers are used by a number of devices, so using a syscon device to share them. The first consumer of this will by the phy-da8xx-usb driver. Signed-off-by: David Lechner --- syscon device id is changed to -1 since there is only one syscon device.

[PATCH v6 5/5] ARM: DTS: da850: Add usb phy node

Add a node for the new usb phy driver. Signed-off-by: David Lechner --- arch/arm/boot/dts/da850.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi index 6bbf20d..33fcdce 100644 --- a/arch/arm/boot/dts/da850.dtsi +++

linux-next: no releases next week

Hi all, There will probably be no linux-next releases next week while I am attending Kernel Summit. -- Cheers, Stephen Rothwell

linux-next: no releases next week

Hi all, There will probably be no linux-next releases next week while I am attending Kernel Summit. -- Cheers, Stephen Rothwell

linux-next: Tree for Oct 26

Hi all, There will probably be no linux-next releases next week while I attend the Kernel Summit. Changes since 20161025: The sunxi tree lost its build failure. The akpm-current tree still had its build failures for which I applied 2 patches. Non-merge commits (relative to Linus' tree): 2628

linux-next: Tree for Oct 26

Hi all, There will probably be no linux-next releases next week while I attend the Kernel Summit. Changes since 20161025: The sunxi tree lost its build failure. The akpm-current tree still had its build failures for which I applied 2 patches. Non-merge commits (relative to Linus' tree): 2628

Re: [RFC PATCH 0/6] UART slave devices using serio

Hi, On Tue, Oct 25, 2016 at 05:02:23PM -0500, Rob Herring wrote: > On Tue, Oct 25, 2016 at 4:55 PM, Sebastian Reichel wrote: > > On Wed, Aug 24, 2016 at 06:24:30PM -0500, Rob Herring wrote: > >> [...] > > I had a more detailed look at the series during the last two weeks. > > For me the approach

Re: [RFC PATCH 0/6] UART slave devices using serio

Hi, On Tue, Oct 25, 2016 at 05:02:23PM -0500, Rob Herring wrote: > On Tue, Oct 25, 2016 at 4:55 PM, Sebastian Reichel wrote: > > On Wed, Aug 24, 2016 at 06:24:30PM -0500, Rob Herring wrote: > >> [...] > > I had a more detailed look at the series during the last two weeks. > > For me the approach

[PATCH v2 5/5] posix-timers: make it configurable

Some embedded systems have no use for them. This removes about 22KB from the kernel binary size when configured out. Corresponding syscalls are routed to a stub logging the attempt to use those syscalls which should be enough of a clue if they were disabled without proper consideration. They

[PATCH v2 3/5] kconfig: regenerate *.c_shipped files after previous changes

Signed-off-by: Nicolas Pitre --- scripts/kconfig/zconf.hash.c_shipped | 228 ++--- scripts/kconfig/zconf.tab.c_shipped | 1631 -- 2 files changed, 888 insertions(+), 971 deletions(-) diff --git a/scripts/kconfig/zconf.hash.c_shipped

[PATCH v2 5/5] posix-timers: make it configurable

Some embedded systems have no use for them. This removes about 22KB from the kernel binary size when configured out. Corresponding syscalls are routed to a stub logging the attempt to use those syscalls which should be enough of a clue if they were disabled without proper consideration. They

[PATCH v2 3/5] kconfig: regenerate *.c_shipped files after previous changes

Signed-off-by: Nicolas Pitre --- scripts/kconfig/zconf.hash.c_shipped | 228 ++--- scripts/kconfig/zconf.tab.c_shipped | 1631 -- 2 files changed, 888 insertions(+), 971 deletions(-) diff --git a/scripts/kconfig/zconf.hash.c_shipped

[PATCH v2 1/5] kconfig: introduce the "imply" keyword

The "imply" keyword is a weak version of "select" where the target config symbol can still be turned off, avoiding those pitfalls that come with the "select" keyword. This is useful e.g. with multiple drivers that want to indicate their ability to hook into a given subsystem while still being

[PATCH v2 1/5] kconfig: introduce the "imply" keyword

The "imply" keyword is a weak version of "select" where the target config symbol can still be turned off, avoiding those pitfalls that come with the "select" keyword. This is useful e.g. with multiple drivers that want to indicate their ability to hook into a given subsystem while still being

Re: [PATCH -next 1/2] Input: synaptics-rmi4 - add support for F55 sensor tuning

On 10/25/2016 11:26 AM, Andrew Duggan wrote: On 10/24/2016 08:13 PM, Guenter Roeck wrote: Hi Andrew, On 10/24/2016 05:59 PM, Andrew Duggan wrote: Hi Guenter, I have a couple of comments below. Thanks a lot for the feedback. On 09/30/2016 08:22 PM, Guenter Roeck wrote: Sensor tuning

Re: [PATCH -next 1/2] Input: synaptics-rmi4 - add support for F55 sensor tuning

On 10/25/2016 11:26 AM, Andrew Duggan wrote: On 10/24/2016 08:13 PM, Guenter Roeck wrote: Hi Andrew, On 10/24/2016 05:59 PM, Andrew Duggan wrote: Hi Guenter, I have a couple of comments below. Thanks a lot for the feedback. On 09/30/2016 08:22 PM, Guenter Roeck wrote: Sensor tuning

[PATCH] Change the document about iowait

The iowait is not reliable by reading from /proc/stat, so this method to get iowait is not suggested. And we mark it in the document. Signed-off-by: Cao Jin Signed-off-by: Chao Fan --- Documentation/filesystems/proc.txt | 11 ++- 1

[PATCH] Change the document about iowait

The iowait is not reliable by reading from /proc/stat, so this method to get iowait is not suggested. And we mark it in the document. Signed-off-by: Cao Jin Signed-off-by: Chao Fan --- Documentation/filesystems/proc.txt | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff

Re: [PATCH] ARM: imx6: Fix GPC probe error path

On 10/25/2016 10:34 AM, Guenter Roeck wrote: GPC may fail to instantiate with imx-gpc: probe of 20dc000.gpc failed with error -22 which is returned from of_genpd_add_provider_onecell(). The error path does not call pm_genpd_remove(). This results in the following crash later on. Unhandled

Re: [PATCH] ARM: imx6: Fix GPC probe error path

On 10/25/2016 10:34 AM, Guenter Roeck wrote: GPC may fail to instantiate with imx-gpc: probe of 20dc000.gpc failed with error -22 which is returned from of_genpd_add_provider_onecell(). The error path does not call pm_genpd_remove(). This results in the following crash later on. Unhandled

  1   2   3   4   5   6   7   8   9   10   >