[rcu:rcu/next 34/34] include/linux/rcupdate.h:426:6: error: 'rcu_scheduler_active' undeclared

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next head: ccc0666e2049e5818c236e647cf20c552a7b053b commit: ccc0666e2049e5818c236e647cf20c552a7b053b [34/34] rcu: Allow boot-time use of cond_resched_rcu_qs() config: i386-randconfig-x008-201648 (attached as

[rcu:rcu/next 34/34] include/linux/rcupdate.h:426:6: error: 'rcu_scheduler_active' undeclared

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next head: ccc0666e2049e5818c236e647cf20c552a7b053b commit: ccc0666e2049e5818c236e647cf20c552a7b053b [34/34] rcu: Allow boot-time use of cond_resched_rcu_qs() config: i386-randconfig-x008-201648 (attached as

RE: [char-msic 1/3] mei: me: disable driver on SPT SPS firmware

> > On Tue, Nov 29, 2016 at 02:44:44PM +0200, Tomas Winkler wrote: > > commit 8c57cac1457f3125a5d13dc03635c0708c61bff0 upstream > > > > Sunrise Point PCH with SPS Firmware doesn't expose working MEI > > interface, we need to quirk it out. > > The SPS Firmware is identifiable only on the first PCI

RE: [char-msic 1/3] mei: me: disable driver on SPT SPS firmware

> > On Tue, Nov 29, 2016 at 02:44:44PM +0200, Tomas Winkler wrote: > > commit 8c57cac1457f3125a5d13dc03635c0708c61bff0 upstream > > > > Sunrise Point PCH with SPS Firmware doesn't expose working MEI > > interface, we need to quirk it out. > > The SPS Firmware is identifiable only on the first PCI

Re: [PATCH v2 4/6] perf sched timehist: Add option to specify time window of interest

Em Tue, Nov 29, 2016 at 11:58:03AM -0700, David Ahern escreveu: > On 11/29/16 11:56 AM, Arnaldo Carvalho de Melo wrote: > > Em Tue, Nov 29, 2016 at 10:15:44AM -0700, David Ahern escreveu: > >> Add option to allow user to control analysis window. e.g., collect data > >> for time window and analyze

Re: [PATCH v2 4/6] perf sched timehist: Add option to specify time window of interest

Em Tue, Nov 29, 2016 at 11:58:03AM -0700, David Ahern escreveu: > On 11/29/16 11:56 AM, Arnaldo Carvalho de Melo wrote: > > Em Tue, Nov 29, 2016 at 10:15:44AM -0700, David Ahern escreveu: > >> Add option to allow user to control analysis window. e.g., collect data > >> for time window and analyze

Re: [PATCH][V2] scsi: megaraid-sas: fix spelling mistake of "outstanding"

On 11/29/2016 11:13 AM, Colin King wrote: Trivial fix to spelling mistake "oustanding" to "outstanding" in dev_info and scmd_printk messages. Also join wrapped literal string in the scmd_printk. Reviewed-by: Bart Van Assche

Re: [PATCH][V2] scsi: megaraid-sas: fix spelling mistake of "outstanding"

On 11/29/2016 11:13 AM, Colin King wrote: Trivial fix to spelling mistake "oustanding" to "outstanding" in dev_info and scmd_printk messages. Also join wrapped literal string in the scmd_printk. Reviewed-by: Bart Van Assche

Re: [PATCH v2, variant B] tty: nozomi: avoid sprintf buffer overflow

On Tue, Nov 29, 2016 at 12:51:04PM +0100, Arnd Bergmann wrote: > Testing with a gcc-7 snapshot produced an internal compiler error > for this file: > > drivers/tty/nozomi.c: In function 'receive_flow_control': > drivers/tty/nozomi.c:919:12: internal compiler error: in >

Re: [PATCH v2, variant B] tty: nozomi: avoid sprintf buffer overflow

On Tue, Nov 29, 2016 at 12:51:04PM +0100, Arnd Bergmann wrote: > Testing with a gcc-7 snapshot produced an internal compiler error > for this file: > > drivers/tty/nozomi.c: In function 'receive_flow_control': > drivers/tty/nozomi.c:919:12: internal compiler error: in >

Re: [PATCH 2/4] ARM64: dts: meson-gx: Add Graphic Controller nodes

Hi Neil, On Tuesday 29 Nov 2016 21:16:17 Laurent Pinchart wrote: > On Tuesday 29 Nov 2016 11:47:47 Neil Armstrong wrote: > > Add Video Processing Unit and CVBS Output nodes, and enable CVBS on > > selected boards. > > > > Signed-off-by: Neil Armstrong > > --- > > > >

Re: [PATCH 2/4] ARM64: dts: meson-gx: Add Graphic Controller nodes

Hi Neil, On Tuesday 29 Nov 2016 21:16:17 Laurent Pinchart wrote: > On Tuesday 29 Nov 2016 11:47:47 Neil Armstrong wrote: > > Add Video Processing Unit and CVBS Output nodes, and enable CVBS on > > selected boards. > > > > Signed-off-by: Neil Armstrong > > --- > > > >

Re: [PATCH 2/4] ARM64: dts: meson-gx: Add Graphic Controller nodes

Hi Neil, Thank you for the patch. On Tuesday 29 Nov 2016 11:47:47 Neil Armstrong wrote: > Add Video Processing Unit and CVBS Output nodes, and enable CVBS on selected > boards. > > Signed-off-by: Neil Armstrong > --- > arch/arm64/boot/dts/amlogic/meson-gx.dtsi

Re: [PATCH 2/4] ARM64: dts: meson-gx: Add Graphic Controller nodes

Hi Neil, Thank you for the patch. On Tuesday 29 Nov 2016 11:47:47 Neil Armstrong wrote: > Add Video Processing Unit and CVBS Output nodes, and enable CVBS on selected > boards. > > Signed-off-by: Neil Armstrong > --- > arch/arm64/boot/dts/amlogic/meson-gx.dtsi | 46

Re: [char-msic 3/3] mei: fix return value on disconnection

On Tue, Nov 29, 2016 at 02:44:46PM +0200, Tomas Winkler wrote: > commit 2d4d5481e2d6f93b25fcfb13a9f20bbfbf54266a upstream. > > Correct errno on client disconnection is -ENODEV not -EBUSY > > Cc: #4.4 > Signed-off-by: Tomas Winkler >

Re: [PATCH v2 0/6] perf: Add option to specify time window of interest

Em Tue, Nov 29, 2016 at 10:15:40AM -0700, David Ahern escreveu: > This series allows users to collect data and analyze a time window of > interest within the file. > > v2 > - renamed perf_time to perf_time_interval > - changed ../perf.h to perf.h in patch 1 Thanks, applied and pushed out to

Re: [PATCH v3] i2c: i2c-mux-gpio: update mux with gpiod_set_array_value_cansleep

On Thu, Nov 24, 2016 at 07:19:28PM +0100, Peter Rosin wrote: > If the gpio controller supports it and the gpio lines are concentrated > to one gpio chip, the mux controller pins will get updated simultaneously. > > Signed-off-by: Peter Rosin Applied to for-next, thanks!

Re: [char-misc-next 4/4 V2] mei: bus: enable non-blocking RX

On Mon, Nov 28, 2016 at 11:03:20PM +, Winkler, Tomas wrote: > > > > > > > > > > On Sat, Nov 19, 2016 at 02:16:11PM +0200, Tomas Winkler wrote: > > > > From: Alexander Usyskin > > > > > > > > Enable non-blocking receive for drivers on mei bus, this allows > > > >

Re: [char-msic 3/3] mei: fix return value on disconnection

On Tue, Nov 29, 2016 at 02:44:46PM +0200, Tomas Winkler wrote: > commit 2d4d5481e2d6f93b25fcfb13a9f20bbfbf54266a upstream. > > Correct errno on client disconnection is -ENODEV not -EBUSY > > Cc: #4.4 > Signed-off-by: Tomas Winkler > Signed-off-by: Alexander Usyskin > Signed-off-by: Greg

Re: [PATCH v2 0/6] perf: Add option to specify time window of interest

Em Tue, Nov 29, 2016 at 10:15:40AM -0700, David Ahern escreveu: > This series allows users to collect data and analyze a time window of > interest within the file. > > v2 > - renamed perf_time to perf_time_interval > - changed ../perf.h to perf.h in patch 1 Thanks, applied and pushed out to

Re: [PATCH v3] i2c: i2c-mux-gpio: update mux with gpiod_set_array_value_cansleep

On Thu, Nov 24, 2016 at 07:19:28PM +0100, Peter Rosin wrote: > If the gpio controller supports it and the gpio lines are concentrated > to one gpio chip, the mux controller pins will get updated simultaneously. > > Signed-off-by: Peter Rosin Applied to for-next, thanks! signature.asc

Re: [char-misc-next 4/4 V2] mei: bus: enable non-blocking RX

On Mon, Nov 28, 2016 at 11:03:20PM +, Winkler, Tomas wrote: > > > > > > > > > > On Sat, Nov 19, 2016 at 02:16:11PM +0200, Tomas Winkler wrote: > > > > From: Alexander Usyskin > > > > > > > > Enable non-blocking receive for drivers on mei bus, this allows > > > > checking for data

Re: [char-msic 2/3] mei: me: fix place for kaby point device ids.

On Tue, Nov 29, 2016 at 02:44:45PM +0200, Tomas Winkler wrote: > This is fix of the backported patch only, it places > KBL DIDs on correct place to easy on backporting of > further DIDs. > > Fixes: 5c99f32c461c ('mei: me: add kaby point device ids') > Cc: #4.4 >

Re: [char-msic 2/3] mei: me: fix place for kaby point device ids.

On Tue, Nov 29, 2016 at 02:44:45PM +0200, Tomas Winkler wrote: > This is fix of the backported patch only, it places > KBL DIDs on correct place to easy on backporting of > further DIDs. > > Fixes: 5c99f32c461c ('mei: me: add kaby point device ids') > Cc: #4.4 > Signed-off-by: Tomas Winkler >

Re: [lkp] [mm] e7c1db75fe: BUG:sleeping_function_called_from_invalid_context_at_mm/page_alloc.c

On Tue, Nov 29, 2016 at 05:21:19PM +, Sudeep Holla wrote: > On Sun, Nov 27, 2016 at 6:16 PM, kernel test robot > wrote: > > > > FYI, we noticed the following commit: > > > > commit e7c1db75fed821a961ce1ca2b602b08e75de0cd8 ("mm: Prevent > > __alloc_pages_nodemask() RCU

Re: [lkp] [mm] e7c1db75fe: BUG:sleeping_function_called_from_invalid_context_at_mm/page_alloc.c

On Tue, Nov 29, 2016 at 05:21:19PM +, Sudeep Holla wrote: > On Sun, Nov 27, 2016 at 6:16 PM, kernel test robot > wrote: > > > > FYI, we noticed the following commit: > > > > commit e7c1db75fed821a961ce1ca2b602b08e75de0cd8 ("mm: Prevent > > __alloc_pages_nodemask() RCU CPU stall warnings") >

Re: [char-msic 1/3] mei: me: disable driver on SPT SPS firmware

On Tue, Nov 29, 2016 at 02:44:44PM +0200, Tomas Winkler wrote: > commit 8c57cac1457f3125a5d13dc03635c0708c61bff0 upstream > > Sunrise Point PCH with SPS Firmware doesn't expose working > MEI interface, we need to quirk it out. > The SPS Firmware is identifiable only on the first PCI function > of

Re: [char-msic 1/3] mei: me: disable driver on SPT SPS firmware

On Tue, Nov 29, 2016 at 02:44:44PM +0200, Tomas Winkler wrote: > commit 8c57cac1457f3125a5d13dc03635c0708c61bff0 upstream > > Sunrise Point PCH with SPS Firmware doesn't expose working > MEI interface, we need to quirk it out. > The SPS Firmware is identifiable only on the first PCI function > of

[PATCH][V2] scsi: megaraid-sas: fix spelling mistake of "outstanding"

From: Colin Ian King Trivial fix to spelling mistake "oustanding" to "outstanding" in dev_info and scmd_printk messages. Also join wrapped literal string in the scmd_printk. Signed-off-by: Colin Ian King ---

[PATCH][V2] scsi: megaraid-sas: fix spelling mistake of "outstanding"

From: Colin Ian King Trivial fix to spelling mistake "oustanding" to "outstanding" in dev_info and scmd_printk messages. Also join wrapped literal string in the scmd_printk. Signed-off-by: Colin Ian King --- drivers/scsi/megaraid/megaraid_sas_base.c | 2 +-

Re: [PATCHv2] mfd: cpcap: Add minimal support

* Tony Lindgren [161129 08:48]: > --- /dev/null > +++ b/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt > @@ -0,0 +1,31 @@ > +Motorola CPCAP PMIC device tree binding > + > +Required properties: > +- compatible : One or both of "motorola,cpcap" or "ste,6556002" >

Re: [PATCHv2] mfd: cpcap: Add minimal support

* Tony Lindgren [161129 08:48]: > --- /dev/null > +++ b/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt > @@ -0,0 +1,31 @@ > +Motorola CPCAP PMIC device tree binding > + > +Required properties: > +- compatible : One or both of "motorola,cpcap" or "ste,6556002" > +- reg

Re: 4.9-rc7: (forcedeth?) BUG: sleeping function called from invalid context at kernel/irq/manage.c:110

On Tue, Nov 29, 2016 at 12:26 PM, Meelis Roos wrote: > This is 4.9-rc7 on Sun Ultra 20 (Opteron 175 on NVidia chipset PC with > NVidia ethernet). > > BUG: sleeping function called from invalid context at kernel/irq/manage.c:110 Hmm. No changes in either forcedeth or in the

Re: 4.9-rc7: (forcedeth?) BUG: sleeping function called from invalid context at kernel/irq/manage.c:110

On Tue, Nov 29, 2016 at 12:26 PM, Meelis Roos wrote: > This is 4.9-rc7 on Sun Ultra 20 (Opteron 175 on NVidia chipset PC with > NVidia ethernet). > > BUG: sleeping function called from invalid context at kernel/irq/manage.c:110 Hmm. No changes in either forcedeth or in the synchronize_irq()

Re: [PATCH 1/1] scripts: Fixing NULL pointer dereference when pos->file is NULL

On 11/29/16 02:34, Maninder Singh wrote: > This patch fixes NULL pointer dereference when pos->file is NULL. > > caught with static analysis tool. > Signed-off-by: Maninder Singh > Signed-off-by: Vaneet Narang > --- > scripts/dtc/srcpos.c | 3 +--

RE: [PATCH] perf/x86: fix event counter update issue

On Tuesday, November 29, 2016 6:20 PM Stephane Eranian wrote: >> On Tue, Nov 29, 2016 at 1:25 AM, Peter Zijlstra wrote: >> How can this happen? IIRC the thing increments, we program a negative >> value, and when it passes 0 we generate a PMI. >> > Yeah, that's the

RE: [PATCH] perf/x86: fix event counter update issue

On Tuesday, November 29, 2016 6:20 PM Stephane Eranian wrote: >> On Tue, Nov 29, 2016 at 1:25 AM, Peter Zijlstra wrote: >> How can this happen? IIRC the thing increments, we program a negative >> value, and when it passes 0 we generate a PMI. >> > Yeah, that's the part I don't quite

Re: [PATCH 1/1] scripts: Fixing NULL pointer dereference when pos->file is NULL

On 11/29/16 02:34, Maninder Singh wrote: > This patch fixes NULL pointer dereference when pos->file is NULL. > > caught with static analysis tool. > Signed-off-by: Maninder Singh > Signed-off-by: Vaneet Narang > --- > scripts/dtc/srcpos.c | 3 +-- > 1 file changed, 1 insertion(+), 2

Re: [PATCH V5] i2c: mux: pca954x: Add ACPI support for pca954x

On Tue, Nov 29, 2016 at 05:12:43PM +0700, Tin Huynh wrote: > This patch enables ACPI support for mux-pca954x driver. > > Signed-off-by: Tin Huynh Applied to for-next, thanks! signature.asc Description: PGP signature

Re: [PATCH V5] i2c: mux: pca954x: Add ACPI support for pca954x

On Tue, Nov 29, 2016 at 05:12:43PM +0700, Tin Huynh wrote: > This patch enables ACPI support for mux-pca954x driver. > > Signed-off-by: Tin Huynh Applied to for-next, thanks! signature.asc Description: PGP signature

RE: [PATCH] perf/x86: fix event counter update issue

> On Tue, Nov 29, 2016 at 09:20:10AM -0800, Stephane Eranian wrote: > > Max period is limited by the number of bits the kernel can write to an > MSR. > > Used to be 31, now it is 47 for core PMU as per patch pointed to by Kan. > > No, I think it sets it to 48 now, which is the problem. It

RE: [PATCH] perf/x86: fix event counter update issue

> On Tue, Nov 29, 2016 at 09:20:10AM -0800, Stephane Eranian wrote: > > Max period is limited by the number of bits the kernel can write to an > MSR. > > Used to be 31, now it is 47 for core PMU as per patch pointed to by Kan. > > No, I think it sets it to 48 now, which is the problem. It

[PATCH] staging: unisys: ix spelling mistake of "outstanding"

From: Colin Ian King Trivial fix to spelling mistake "oustanding" to "outstanding". Signed-off-by: Colin Ian King --- drivers/staging/unisys/visornic/visornic_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] staging: unisys: ix spelling mistake of "outstanding"

From: Colin Ian King Trivial fix to spelling mistake "oustanding" to "outstanding". Signed-off-by: Colin Ian King --- drivers/staging/unisys/visornic/visornic_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/unisys/visornic/visornic_main.c

Re: [PATCH 0/9] coresight: next v4.9-rc7

On Tue, Nov 29, 2016 at 09:47:10AM -0700, Mathieu Poirier wrote: > Hi Greg, > > These are the patches I'd like you to consider for inclusion in the > 4.10 cycle. They were sent earlier this month [1] but I haven't received > the usual automated acknowledgment, hence sending again. Everything >

Re: [PATCH 0/9] coresight: next v4.9-rc7

On Tue, Nov 29, 2016 at 09:47:10AM -0700, Mathieu Poirier wrote: > Hi Greg, > > These are the patches I'd like you to consider for inclusion in the > 4.10 cycle. They were sent earlier this month [1] but I haven't received > the usual automated acknowledgment, hence sending again. Everything >

[PATCH] scsi: megaraid-sas: fix spelling mistake of "outstanding"

From: Colin Ian King Trivial fix to spelling mistake "oustanding" to "outstanding" in dev_info and scmd_printk messages Signed-off-by: Colin Ian King --- drivers/scsi/megaraid/megaraid_sas_base.c | 2 +-

[PATCH] scsi: megaraid-sas: fix spelling mistake of "outstanding"

From: Colin Ian King Trivial fix to spelling mistake "oustanding" to "outstanding" in dev_info and scmd_printk messages Signed-off-by: Colin Ian King --- drivers/scsi/megaraid/megaraid_sas_base.c | 2 +- drivers/scsi/megaraid/megaraid_sas_fusion.c | 2 +- 2 files changed, 2 insertions(+), 2

[PATCHv4 07/10] kexec: Switch to __pa_symbol

__pa_symbol is the correct api to get the physical address of kernel symbols. Switch to it to allow for better debug checking. Signed-off-by: Laura Abbott --- Found during review of the kernel. Untested. --- kernel/kexec_core.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCHv4 07/10] kexec: Switch to __pa_symbol

__pa_symbol is the correct api to get the physical address of kernel symbols. Switch to it to allow for better debug checking. Signed-off-by: Laura Abbott --- Found during review of the kernel. Untested. --- kernel/kexec_core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCHv4 08/10] mm/kasan: Switch to using __pa_symbol and lm_alias

__pa_symbol is the correct API to find the physical address of symbols. Switch to it to allow for debugging APIs to work correctly. Other functions such as p*d_populate may call __pa internally. Ensure that the address passed is in the linear region by calling lm_alias. Signed-off-by: Laura

[PATCHv4 02/10] mm/cma: Cleanup highmem check

6b101e2a3ce4 ("mm/CMA: fix boot regression due to physical address of high_memory") added checks to use __pa_nodebug on x86 since CONFIG_DEBUG_VIRTUAL complains about high_memory not being linearlly mapped. arm64 is now getting support for CONFIG_DEBUG_VIRTUAL as well. Rather than add an

[PATCHv4 05/10] arm64: Use __pa_symbol for kernel symbols

__pa_symbol is technically the marco that should be used for kernel symbols. Switch to this as a pre-requisite for DEBUG_VIRTUAL which will do bounds checking. As part of this, introduce lm_alias, a macro which wraps the __va(__pa(...)) idiom used a few places to get the alias. Signed-off-by:

Re: [PATCH v2 4/6] perf sched timehist: Add option to specify time window of interest

Em Tue, Nov 29, 2016 at 10:15:44AM -0700, David Ahern escreveu: > Add option to allow user to control analysis window. e.g., collect data > for time window and analyze a segment of interest within that window. Trying to test this I got: [root@jouet ~]# perf sched timehist No trace sample to

[PATCHv4 06/10] xen: Switch to using __pa_symbol

__pa_symbol is the correct macro to use on kernel symbols. Switch to this from __pa. Signed-off-by: Laura Abbott --- Found during a sweep of the kernel. Untested. --- drivers/xen/xenbus/xenbus_dev_backend.c | 2 +- drivers/xen/xenfs/xenstored.c | 2 +- 2 files

[PATCHv4 08/10] mm/kasan: Switch to using __pa_symbol and lm_alias

__pa_symbol is the correct API to find the physical address of symbols. Switch to it to allow for debugging APIs to work correctly. Other functions such as p*d_populate may call __pa internally. Ensure that the address passed is in the linear region by calling lm_alias. Signed-off-by: Laura

[PATCHv4 02/10] mm/cma: Cleanup highmem check

6b101e2a3ce4 ("mm/CMA: fix boot regression due to physical address of high_memory") added checks to use __pa_nodebug on x86 since CONFIG_DEBUG_VIRTUAL complains about high_memory not being linearlly mapped. arm64 is now getting support for CONFIG_DEBUG_VIRTUAL as well. Rather than add an

[PATCHv4 05/10] arm64: Use __pa_symbol for kernel symbols

__pa_symbol is technically the marco that should be used for kernel symbols. Switch to this as a pre-requisite for DEBUG_VIRTUAL which will do bounds checking. As part of this, introduce lm_alias, a macro which wraps the __va(__pa(...)) idiom used a few places to get the alias. Signed-off-by:

Re: [PATCH v2 4/6] perf sched timehist: Add option to specify time window of interest

Em Tue, Nov 29, 2016 at 10:15:44AM -0700, David Ahern escreveu: > Add option to allow user to control analysis window. e.g., collect data > for time window and analyze a segment of interest within that window. Trying to test this I got: [root@jouet ~]# perf sched timehist No trace sample to

[PATCHv4 06/10] xen: Switch to using __pa_symbol

__pa_symbol is the correct macro to use on kernel symbols. Switch to this from __pa. Signed-off-by: Laura Abbott --- Found during a sweep of the kernel. Untested. --- drivers/xen/xenbus/xenbus_dev_backend.c | 2 +- drivers/xen/xenfs/xenstored.c | 2 +- 2 files changed, 2

Re: [PATCH v2 4/6] perf sched timehist: Add option to specify time window of interest

On 11/29/16 11:56 AM, Arnaldo Carvalho de Melo wrote: > Em Tue, Nov 29, 2016 at 10:15:44AM -0700, David Ahern escreveu: >> Add option to allow user to control analysis window. e.g., collect data >> for time window and analyze a segment of interest within that window. > Trying to test this I got: >

Re: [PATCH v2 4/6] perf sched timehist: Add option to specify time window of interest

On 11/29/16 11:56 AM, Arnaldo Carvalho de Melo wrote: > Em Tue, Nov 29, 2016 at 10:15:44AM -0700, David Ahern escreveu: >> Add option to allow user to control analysis window. e.g., collect data >> for time window and analyze a segment of interest within that window. > Trying to test this I got: >

[PATCHv4 10/10] arm64: Add support for CONFIG_DEBUG_VIRTUAL

x86 has an option CONFIG_DEBUG_VIRTUAL to do additional checks on virt_to_phys calls. The goal is to catch users who are calling virt_to_phys on non-linear addresses immediately. This inclues callers using virt_to_phys on image addresses instead of __pa_symbol. As features such as

[PATCHv4 09/10] mm/usercopy: Switch to using lm_alias

The usercopy checking code currently calls __va(__pa(...)) to check for aliases on symbols. Switch to using lm_alias instead. Signed-off-by: Laura Abbott --- Found when reviewing the kernel. Tested. --- mm/usercopy.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

[PATCHv4 10/10] arm64: Add support for CONFIG_DEBUG_VIRTUAL

x86 has an option CONFIG_DEBUG_VIRTUAL to do additional checks on virt_to_phys calls. The goal is to catch users who are calling virt_to_phys on non-linear addresses immediately. This inclues callers using virt_to_phys on image addresses instead of __pa_symbol. As features such as

[PATCHv4 09/10] mm/usercopy: Switch to using lm_alias

The usercopy checking code currently calls __va(__pa(...)) to check for aliases on symbols. Switch to using lm_alias instead. Signed-off-by: Laura Abbott --- Found when reviewing the kernel. Tested. --- mm/usercopy.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCHv4 03/10] arm64: Move some macros under #ifndef __ASSEMBLY__

Several macros for various x_to_y exist outside the bounds of an __ASSEMBLY__ guard. Move them in preparation for support for CONFIG_DEBUG_VIRTUAL. Reviewed-by: Mark Rutland Tested-by: Mark Rutland Signed-off-by: Laura Abbott ---

[PATCHv4 03/10] arm64: Move some macros under #ifndef __ASSEMBLY__

Several macros for various x_to_y exist outside the bounds of an __ASSEMBLY__ guard. Move them in preparation for support for CONFIG_DEBUG_VIRTUAL. Reviewed-by: Mark Rutland Tested-by: Mark Rutland Signed-off-by: Laura Abbott --- v4: No changes --- arch/arm64/include/asm/memory.h | 38

[PATCHv4 04/10] arm64: Add cast for virt_to_pfn

virt_to_pfn lacks a cast at the top level. Don't rely on __virt_to_phys and explicitly cast to unsigned long. Reviewed-by: Mark Rutland Tested-by: Mark Rutland Signed-off-by: Laura Abbott --- v4: No changes ---

[PATCHv4 04/10] arm64: Add cast for virt_to_pfn

virt_to_pfn lacks a cast at the top level. Don't rely on __virt_to_phys and explicitly cast to unsigned long. Reviewed-by: Mark Rutland Tested-by: Mark Rutland Signed-off-by: Laura Abbott --- v4: No changes --- arch/arm64/include/asm/memory.h | 2 +- 1 file changed, 1 insertion(+), 1

Re: [RFC PATCH v3 19/20] x86: Add support to make use of Secure Memory Encryption

On 11/24/2016 6:50 AM, Borislav Petkov wrote: > On Wed, Nov 09, 2016 at 06:38:26PM -0600, Tom Lendacky wrote: >> This patch adds the support to check if SME has been enabled and if the >> mem_encrypt=on command line option is set. If both of these conditions >> are true, then the encryption mask

Re: [RFC PATCH v3 19/20] x86: Add support to make use of Secure Memory Encryption

On 11/24/2016 6:50 AM, Borislav Petkov wrote: > On Wed, Nov 09, 2016 at 06:38:26PM -0600, Tom Lendacky wrote: >> This patch adds the support to check if SME has been enabled and if the >> mem_encrypt=on command line option is set. If both of these conditions >> are true, then the encryption mask

[PATCHv4 00/10] CONFIG_DEBUG_VIRTUAL for arm64

Hi, This is v4 of the series to add CONFIG_DEBUG_VIRTUAL for arm64. This mostly expanded on __pa_symbol conversion with a few new sites found. There's also some reworking done to avoid calling __va too early. __va relies on having memstart_addr set so very early code in early_fixmap_init and

[PATCHv4 00/10] CONFIG_DEBUG_VIRTUAL for arm64

Hi, This is v4 of the series to add CONFIG_DEBUG_VIRTUAL for arm64. This mostly expanded on __pa_symbol conversion with a few new sites found. There's also some reworking done to avoid calling __va too early. __va relies on having memstart_addr set so very early code in early_fixmap_init and

[PATCHv4 01/10] lib/Kconfig.debug: Add ARCH_HAS_DEBUG_VIRTUAL

DEBUG_VIRTUAL currently depends on DEBUG_KERNEL && X86. arm64 is getting the same support. Rather than add a list of architectures, switch this to ARCH_HAS_DEBUG_VIRTUAL and let architectures select it as appropriate. Acked-by: Ingo Molnar Reviewed-by: Mark Rutland

[GIT PULL] SCSI fixes for 4.9-rc7

Four small fixes. The be2iscsi is a potential device overrun in consistent memory, which could have nasty consequences if the consistent allocations are packed. The hpsa one fixes a regression where older controllers can now get a numbering clash between the first internal disk and the

[PATCHv4 01/10] lib/Kconfig.debug: Add ARCH_HAS_DEBUG_VIRTUAL

DEBUG_VIRTUAL currently depends on DEBUG_KERNEL && X86. arm64 is getting the same support. Rather than add a list of architectures, switch this to ARCH_HAS_DEBUG_VIRTUAL and let architectures select it as appropriate. Acked-by: Ingo Molnar Reviewed-by: Mark Rutland Tested-by: Mark Rutland

[GIT PULL] SCSI fixes for 4.9-rc7

Four small fixes. The be2iscsi is a potential device overrun in consistent memory, which could have nasty consequences if the consistent allocations are packed. The hpsa one fixes a regression where older controllers can now get a numbering clash between the first internal disk and the

4.9-rc7: (forcedeth?) BUG: sleeping function called from invalid context at kernel/irq/manage.c:110

This is 4.9-rc7 on Sun Ultra 20 (Opteron 175 on NVidia chipset PC with NVidia ethernet). BUG: sleeping function called from invalid context at kernel/irq/manage.c:110 appears twice during bootup - once during usb init when nvidia ethernet irq(?) comes in, and orher time during amd64_edac init

4.9-rc7: (forcedeth?) BUG: sleeping function called from invalid context at kernel/irq/manage.c:110

This is 4.9-rc7 on Sun Ultra 20 (Opteron 175 on NVidia chipset PC with NVidia ethernet). BUG: sleeping function called from invalid context at kernel/irq/manage.c:110 appears twice during bootup - once during usb init when nvidia ethernet irq(?) comes in, and orher time during amd64_edac init

Re: [PATCH] drm/vmwgfx: Fix handling of errors returned by 'vmw_cotable_alloc()'

Good catch. Reviewed-by: Sinclair Yeh On Tue, Nov 29, 2016 at 07:49:19AM +0100, Christophe JAILLET wrote: > 'vmw_cotable_alloc()' returns an error pointer on error, not NULL. > Propagate the error code, instead of returning -ENOMEM unconditionally > > Signed-off-by: Christophe

Re: [PATCH] drm/vmwgfx: Fix handling of errors returned by 'vmw_cotable_alloc()'

Good catch. Reviewed-by: Sinclair Yeh On Tue, Nov 29, 2016 at 07:49:19AM +0100, Christophe JAILLET wrote: > 'vmw_cotable_alloc()' returns an error pointer on error, not NULL. > Propagate the error code, instead of returning -ENOMEM unconditionally > > Signed-off-by: Christophe JAILLET > --- >

Re: [RFC PATCH v3 20/20] x86: Add support to make use of Secure Memory Encryption

On 11/26/2016 2:47 PM, Borislav Petkov wrote: > On Wed, Nov 09, 2016 at 06:38:38PM -0600, Tom Lendacky wrote: >> This patch adds the support to check if SME has been enabled and if the >> mem_encrypt=on command line option is set. If both of these conditions >> are true, then the encryption mask

Re: [RFC PATCH v3 20/20] x86: Add support to make use of Secure Memory Encryption

On 11/26/2016 2:47 PM, Borislav Petkov wrote: > On Wed, Nov 09, 2016 at 06:38:38PM -0600, Tom Lendacky wrote: >> This patch adds the support to check if SME has been enabled and if the >> mem_encrypt=on command line option is set. If both of these conditions >> are true, then the encryption mask

Re: [tip:x86/core] x86: Enable Intel Turbo Boost Max Technology 3.0

On Tue, 2016-11-29 at 08:11 +0100, Ingo Molnar wrote: > * Tim Chen wrote: > > > > > > > > > + If unsure say Y here. > > > > > > If/when other architectures make use of this the Kconfig entry can be > > > moved into  > > > the scheduler Kconfig - but for the time

Re: [tip:x86/core] x86: Enable Intel Turbo Boost Max Technology 3.0

On Tue, 2016-11-29 at 08:11 +0100, Ingo Molnar wrote: > * Tim Chen wrote: > > > > > > > > > + If unsure say Y here. > > > > > > If/when other architectures make use of this the Kconfig entry can be > > > moved into  > > > the scheduler Kconfig - but for the time being it can stay in

[PATCH 0/6] drm/vc4: VEC (SDTV) output support

Here's a series from Boris for enabling SDTV output on VC4. There are two other patches to the clk subsystem necessary to get it working, which I'm in the process of reviewing. I've tested it on composite input of a monitor I had laying around, and it's basically working. Booting with the

[PATCH 1/2] ACPI: Combine acpi_dev_resource_address_space() and acpi_dev_resource_ext_address_space()

Previously acpi_dev_resource_address_space() and acpi_dev_resource_ext_address_space() were wrappers that called acpi_decode_space(). We need to distinguish between Word/DWord/QWord address descriptors and Extended address descriptors, which was impossible in acpi_decode_space(). Fold the

[PATCH 0/2] ACPI: Ignore Consumer/Producer for QWord/DWord/Word Address Space

Per spec, the Consumer/Producer bit is defined only for Extended Address Space descriptors and should be ignored for QWord/DWord/Word Address Space descriptors. My understanding is that this is because x86 BIOSes didn't use the bit consistently, so it couldn't be relied upon. The Extended

[PATCH] sched/x86: Change CONFIG_SCHED_ITMT to CONFIG_SCHED_MC_PRIO

Update CONFIG_SCHED_ITMT for Intel Turbo Boost Max Technology 3.0 to CONFIG_SCHED_MC_PRIO. This makes the configuration extensible in future to other architectures that wish to similarly establish CPU core priorities support in the scheduler. The description in Kconfig is updated to reflect this

[PATCH 0/6] drm/vc4: VEC (SDTV) output support

Here's a series from Boris for enabling SDTV output on VC4. There are two other patches to the clk subsystem necessary to get it working, which I'm in the process of reviewing. I've tested it on composite input of a monitor I had laying around, and it's basically working. Booting with the

[PATCH 1/2] ACPI: Combine acpi_dev_resource_address_space() and acpi_dev_resource_ext_address_space()

Previously acpi_dev_resource_address_space() and acpi_dev_resource_ext_address_space() were wrappers that called acpi_decode_space(). We need to distinguish between Word/DWord/QWord address descriptors and Extended address descriptors, which was impossible in acpi_decode_space(). Fold the

[PATCH 0/2] ACPI: Ignore Consumer/Producer for QWord/DWord/Word Address Space

Per spec, the Consumer/Producer bit is defined only for Extended Address Space descriptors and should be ignored for QWord/DWord/Word Address Space descriptors. My understanding is that this is because x86 BIOSes didn't use the bit consistently, so it couldn't be relied upon. The Extended

[PATCH] sched/x86: Change CONFIG_SCHED_ITMT to CONFIG_SCHED_MC_PRIO

Update CONFIG_SCHED_ITMT for Intel Turbo Boost Max Technology 3.0 to CONFIG_SCHED_MC_PRIO. This makes the configuration extensible in future to other architectures that wish to similarly establish CPU core priorities support in the scheduler. The description in Kconfig is updated to reflect this

[PATCH 6/6] ARM: bcm/dt: Enable the VEC IP on all RaspberryPi boards

From: Boris Brezillon Enable the VEC IP on all RaspberryPi boards. Signed-off-by: Boris Brezillon Signed-off-by: Eric Anholt --- arch/arm/boot/dts/bcm2835-rpi.dtsi | 5 + 1 file changed, 5

[PATCH 1/6] drm/vc4: Fix ->clock_select setting for the VEC encoder

From: Boris Brezillon PV_CONTROL_CLK_SELECT_VEC is actually 2 and not 0. Fix the definition and rework the vc4_set_crtc_possible_masks() to cover the full range of the PV_CONTROL_CLK_SELECT field. Signed-off-by: Boris Brezillon

[PATCH 2/2] ACPI: Ignore Consumer/Producer for QWord/DWord/Word Address Space

Per ACPI spec r6.0, sec 6.4.3.5.1, 2, 3, Bit [0] of General Flags (the Consumer/Producer bit) should be ignored for QWord/DWord/Word Address Space descriptors. The Consumer/Producer bit is defined only for the Extended Address Space descriptor. Ignore Consumer/Producer except for Extended

[PATCH] ACPI / APEI: Fix NMI notification handling

When removing and adding cpu 0 on a system with GHES NMI the following stack trace is seen when re-adding the cpu: WARNING: CPU: 0 PID: 0 at arch/x86/kernel/apic/apic.c:1349 setup_local_APIC+ Modules linked in: nfsv3 rpcsec_gss_krb5 nfsv4 nfs fscache coretemp intel_ra CPU: 0 PID: 0 Comm:

[PATCH 6/6] ARM: bcm/dt: Enable the VEC IP on all RaspberryPi boards

From: Boris Brezillon Enable the VEC IP on all RaspberryPi boards. Signed-off-by: Boris Brezillon Signed-off-by: Eric Anholt --- arch/arm/boot/dts/bcm2835-rpi.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/bcm2835-rpi.dtsi

[PATCH 1/6] drm/vc4: Fix ->clock_select setting for the VEC encoder

From: Boris Brezillon PV_CONTROL_CLK_SELECT_VEC is actually 2 and not 0. Fix the definition and rework the vc4_set_crtc_possible_masks() to cover the full range of the PV_CONTROL_CLK_SELECT field. Signed-off-by: Boris Brezillon Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_crtc.c |

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