Re: [PATCH] KVM: x86: do not save guest-unsupported XSAVE state

On 01/02/2017 05:19, Radim Krčmář wrote: > Saving unsupported state prevents migration when the new host does not > support a XSAVE feature of the original host, even if the feature is not > exposed to the guest. > > We've masked host features with guest-visible features before, with >

Re: [PATCH] KVM: x86: do not save guest-unsupported XSAVE state

On 01/02/2017 05:19, Radim Krčmář wrote: > Saving unsupported state prevents migration when the new host does not > support a XSAVE feature of the original host, even if the feature is not > exposed to the guest. > > We've masked host features with guest-visible features before, with >

Re: [PATCH 0/3] PM / docs: linux/pm.h kerneldocs update and conversion of two docs to reST

On Monday, January 09, 2017 02:34:39 AM Lukas Wunner wrote: > On Fri, Jan 06, 2017 at 02:38:13AM +0100, Rafael J. Wysocki wrote: > > I sent patches [1-2/3] previosly a couple of weeks ago and there have not > > been any comments since then, so either they are fine by everybody or the > > timing

Re: [PATCH 0/3] PM / docs: linux/pm.h kerneldocs update and conversion of two docs to reST

On Monday, January 09, 2017 02:34:39 AM Lukas Wunner wrote: > On Fri, Jan 06, 2017 at 02:38:13AM +0100, Rafael J. Wysocki wrote: > > I sent patches [1-2/3] previosly a couple of weeks ago and there have not > > been any comments since then, so either they are fine by everybody or the > > timing

Re: [PATCH v3 21/24] media: imx: Add MIPI CSI-2 Receiver subdev driver

On 02/01/2017 03:44 PM, Russell King - ARM Linux wrote: On Fri, Jan 06, 2017 at 06:11:39PM -0800, Steve Longerbeam wrote: +static int imxcsi2_get_fmt(struct v4l2_subdev *sd, + struct v4l2_subdev_pad_config *cfg, + struct v4l2_subdev_format

Re: [PATCH v3 21/24] media: imx: Add MIPI CSI-2 Receiver subdev driver

On 02/01/2017 03:44 PM, Russell King - ARM Linux wrote: On Fri, Jan 06, 2017 at 06:11:39PM -0800, Steve Longerbeam wrote: +static int imxcsi2_get_fmt(struct v4l2_subdev *sd, + struct v4l2_subdev_pad_config *cfg, + struct v4l2_subdev_format

Re: [PATCH] xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend()

On Wed, 2017-02-01 at 18:29 -0500, Boris Ostrovsky wrote: > > I could not convince myself that napi_synchronize() is sufficient here > (mostly because I am not familiar with napi flow). At the same time I > would rather not make changes in anticipation of possible disappearance > of

Re: [PATCH] xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend()

On Wed, 2017-02-01 at 18:29 -0500, Boris Ostrovsky wrote: > > I could not convince myself that napi_synchronize() is sufficient here > (mostly because I am not familiar with napi flow). At the same time I > would rather not make changes in anticipation of possible disappearance > of

Re: net: suspicious RCU usage in nf_hook

On Wed, 2017-02-01 at 15:48 -0800, Eric Dumazet wrote: > On Wed, Feb 1, 2017 at 3:29 PM, Cong Wang wrote: > > > Not sure if it is better. The difference is caught up in > > net_enable_timestamp(), > > which is called setsockopt() path and sk_clone() path, so we could

Re: net: suspicious RCU usage in nf_hook

On Wed, 2017-02-01 at 15:48 -0800, Eric Dumazet wrote: > On Wed, Feb 1, 2017 at 3:29 PM, Cong Wang wrote: > > > Not sure if it is better. The difference is caught up in > > net_enable_timestamp(), > > which is called setsockopt() path and sk_clone() path, so we could be > > in netstamp_needed

RE: [PATCH v2 0/4] Use build registers for getting numbers of interrupts

Hi Vineet, I have checked reworked patches. I think it is fine. > -Original Message- > From: Vineet Gupta [mailto:vgu...@synopsys.com] > Sent: Wednesday, February 01, 2017 11:58 PM > To: Yuriy Kolerov ; linux-snps- > a...@lists.infradead.org > Cc:

RE: [PATCH v2 0/4] Use build registers for getting numbers of interrupts

Hi Vineet, I have checked reworked patches. I think it is fine. > -Original Message- > From: Vineet Gupta [mailto:vgu...@synopsys.com] > Sent: Wednesday, February 01, 2017 11:58 PM > To: Yuriy Kolerov ; linux-snps- > a...@lists.infradead.org > Cc: alexey.brod...@synopsys.com;

Re: [PATCH 2/2] cpufreq: brcmstb-avs-cpufreq: properly retrieve P-state upon suspend

On 1 February 2017 at 15:44, Rafael J. Wysocki wrote: > On Tuesday, January 31, 2017 10:53:01 AM Markus Mayer wrote: >> On 5 January 2017 at 20:11, Viresh Kumar wrote: >> > On 19-12-16, 12:10, Markus Mayer wrote: >> >> From: Markus Mayer

Re: [PATCH 2/2] cpufreq: brcmstb-avs-cpufreq: properly retrieve P-state upon suspend

On 1 February 2017 at 15:44, Rafael J. Wysocki wrote: > On Tuesday, January 31, 2017 10:53:01 AM Markus Mayer wrote: >> On 5 January 2017 at 20:11, Viresh Kumar wrote: >> > On 19-12-16, 12:10, Markus Mayer wrote: >> >> From: Markus Mayer >> >> >> >> The AVS GET_PMAP command does return a

[PATCH 4/4] score: remove asm/current.h

... it's already using the generic version anyways, so just drop the file as do the other archs that do not implement their own version of the current macro. Cc: lennox...@gmail.com Cc: liqin.li...@gmail.com Signed-off-by: Davidlohr Bueso --- arch/score/include/asm/Kbuild| 1

[PATCH 4/4] score: remove asm/current.h

... it's already using the generic version anyways, so just drop the file as do the other archs that do not implement their own version of the current macro. Cc: lennox...@gmail.com Cc: liqin.li...@gmail.com Signed-off-by: Davidlohr Bueso --- arch/score/include/asm/Kbuild| 1 +

[PATCH 0/4] archs: use generic current.h

Hi Andrew, This is a resend of straightforward arch patches that I had no response from the maintainers but are trivial enough that I hope you can pick them up, like you did the m32r one. Thanks! Davidlohr Bueso (4): alpha: use generic current.h cris: use generic current.h parisc: use

[PATCH 2/4] cris: use generic current.h

Given that the arch does not add its own implementations, simply use the asm-generic/current.h (generic-y) header instead of duplicating code. Cc: star...@axis.com Cc: linux-cris-ker...@axis.com Signed-off-by: Davidlohr Bueso --- arch/cris/include/asm/Kbuild| 1 +

[PATCH 0/4] archs: use generic current.h

Hi Andrew, This is a resend of straightforward arch patches that I had no response from the maintainers but are trivial enough that I hope you can pick them up, like you did the m32r one. Thanks! Davidlohr Bueso (4): alpha: use generic current.h cris: use generic current.h parisc: use

[PATCH 2/4] cris: use generic current.h

Given that the arch does not add its own implementations, simply use the asm-generic/current.h (generic-y) header instead of duplicating code. Cc: star...@axis.com Cc: linux-cris-ker...@axis.com Signed-off-by: Davidlohr Bueso --- arch/cris/include/asm/Kbuild| 1 +

[PATCH 3/4] parisc: use generic current.h

Given that the arch does not add its own implementations, simply use the asm-generic/current.h (generic-y) header instead of duplicating code. Cc: j...@parisc-linux.org Cc: linux-par...@vger.kernel.org Signed-off-by: Davidlohr Bueso --- arch/parisc/include/asm/Kbuild| 1 +

[PATCH 3/4] parisc: use generic current.h

Given that the arch does not add its own implementations, simply use the asm-generic/current.h (generic-y) header instead of duplicating code. Cc: j...@parisc-linux.org Cc: linux-par...@vger.kernel.org Signed-off-by: Davidlohr Bueso --- arch/parisc/include/asm/Kbuild| 1 +

[PATCH 1/4] alpha: use generic current.h

Given that the arch does not add its own implementations, simply use the asm-generic/current.h (generic-y) header instead of duplicating code. Cc: linux-al...@vger.kernel.org Cc: r...@twiddle.net Signed-off-by: Davidlohr Bueso --- arch/alpha/include/asm/Kbuild| 1 +

[PATCH 1/4] alpha: use generic current.h

Given that the arch does not add its own implementations, simply use the asm-generic/current.h (generic-y) header instead of duplicating code. Cc: linux-al...@vger.kernel.org Cc: r...@twiddle.net Signed-off-by: Davidlohr Bueso --- arch/alpha/include/asm/Kbuild| 1 +

Re: [PATCH 2/2] cpufreq: brcmstb-avs-cpufreq: properly retrieve P-state upon suspend

On Tuesday, January 31, 2017 10:53:01 AM Markus Mayer wrote: > On 5 January 2017 at 20:11, Viresh Kumar wrote: > > On 19-12-16, 12:10, Markus Mayer wrote: > >> From: Markus Mayer > >> > >> The AVS GET_PMAP command does return a P-state along with the

Re: [PATCH 2/2] cpufreq: brcmstb-avs-cpufreq: properly retrieve P-state upon suspend

On Tuesday, January 31, 2017 10:53:01 AM Markus Mayer wrote: > On 5 January 2017 at 20:11, Viresh Kumar wrote: > > On 19-12-16, 12:10, Markus Mayer wrote: > >> From: Markus Mayer > >> > >> The AVS GET_PMAP command does return a P-state along with the P-map > >> information. However, that P-state

Re: net: suspicious RCU usage in nf_hook

On Wed, Feb 1, 2017 at 3:29 PM, Cong Wang wrote: > Not sure if it is better. The difference is caught up in > net_enable_timestamp(), > which is called setsockopt() path and sk_clone() path, so we could be > in netstamp_needed state for a long time too until user-space

Re: net: suspicious RCU usage in nf_hook

On Wed, Feb 1, 2017 at 3:29 PM, Cong Wang wrote: > Not sure if it is better. The difference is caught up in > net_enable_timestamp(), > which is called setsockopt() path and sk_clone() path, so we could be > in netstamp_needed state for a long time too until user-space exercises > these paths.

Re: [PATCH v2] EDAC: mpc85xx: Add T2080 l2-cache support

On 02/02/17 12:28, Borislav Petkov wrote: > On Thu, Feb 02, 2017 at 12:16:24PM +1300, Chris Packham wrote: >> The l2-cache controller on the T2080 SoC has similar capabilities to the >> others already supported by the mpc85xx_edac driver. Add it to the list >> of compatible devices. >> >>

Re: [PATCH v2] EDAC: mpc85xx: Add T2080 l2-cache support

On 02/02/17 12:28, Borislav Petkov wrote: > On Thu, Feb 02, 2017 at 12:16:24PM +1300, Chris Packham wrote: >> The l2-cache controller on the T2080 SoC has similar capabilities to the >> others already supported by the mpc85xx_edac driver. Add it to the list >> of compatible devices. >> >>

Re: [PATCH v3 21/24] media: imx: Add MIPI CSI-2 Receiver subdev driver

On Fri, Jan 06, 2017 at 06:11:39PM -0800, Steve Longerbeam wrote: > +static int imxcsi2_get_fmt(struct v4l2_subdev *sd, > +struct v4l2_subdev_pad_config *cfg, > +struct v4l2_subdev_format *sdformat) > +{ > + struct imxcsi2_dev *csi2 =

Re: [PATCH v3 21/24] media: imx: Add MIPI CSI-2 Receiver subdev driver

On Fri, Jan 06, 2017 at 06:11:39PM -0800, Steve Longerbeam wrote: > +static int imxcsi2_get_fmt(struct v4l2_subdev *sd, > +struct v4l2_subdev_pad_config *cfg, > +struct v4l2_subdev_format *sdformat) > +{ > + struct imxcsi2_dev *csi2 =

Re: [PATCH 1/2] net: ethernet: bgmac: init sequence bug

On 02/01/2017 11:39 PM, Jon Mason wrote: From: Zac Schroff Fix a bug in the 'bgmac' driver init sequence that blind writes for init sequence where it should preserve most bits other than the ones it is deliberately manipulating. Signed-off-by: Zac Schroff

Re: [PATCH 1/2] net: ethernet: bgmac: init sequence bug

On 02/01/2017 11:39 PM, Jon Mason wrote: From: Zac Schroff Fix a bug in the 'bgmac' driver init sequence that blind writes for init sequence where it should preserve most bits other than the ones it is deliberately manipulating. Signed-off-by: Zac Schroff Signed-off-by: Jon Mason Fixes:

Re: [PATCH] initity: try to improve __nocapture annotations

On Wed, Feb 1, 2017 at 11:44 PM, Kees Cook wrote: > On Wed, Feb 1, 2017 at 1:05 PM, Rafael J. Wysocki wrote: >> On Wed, Feb 1, 2017 at 5:11 PM, Arnd Bergmann wrote: >>> There are some additional declarations that got missed in the

[PATCH 4/4] mm: Fix checkpatch warning, extraneous braces

From: Tobin C Harding Patch fixes checkpatch warning on use of braces around a single statement. Signed-off-by: Tobin C Harding --- mm/memory.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/mm/memory.c b/mm/memory.c index 35fb8b2..654e6f4

[PATCH 4/4] mm: Fix checkpatch warning, extraneous braces

From: Tobin C Harding Patch fixes checkpatch warning on use of braces around a single statement. Signed-off-by: Tobin C Harding --- mm/memory.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/mm/memory.c b/mm/memory.c index 35fb8b2..654e6f4 100644 --- a/mm/memory.c +++

Re: [PATCH] initity: try to improve __nocapture annotations

On Wed, Feb 1, 2017 at 11:44 PM, Kees Cook wrote: > On Wed, Feb 1, 2017 at 1:05 PM, Rafael J. Wysocki wrote: >> On Wed, Feb 1, 2017 at 5:11 PM, Arnd Bergmann wrote: >>> There are some additional declarations that got missed in the original >>> patch, >>> and some annotated functions that use

[PATCH 3/4] mm: Fix checkpatch errors, whitespace errors

From: Tobin C Harding Patch fixes whitespace checkpatch errors. Signed-off-by: Tobin C Harding --- mm/memory.c | 42 +- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/mm/memory.c b/mm/memory.c index

[PATCH 0/4] mm: trivial sparse and checkpatch fixes

From: Tobin C Harding This patchset fixes trivial sparse and checkpatch errors/warnings. The majority of the changes are whitespace only. The only code changes are replace 0 with NULL, and remove extraneous braces around single statement. Patchset aims to only make changes when

[PATCH 3/4] mm: Fix checkpatch errors, whitespace errors

From: Tobin C Harding Patch fixes whitespace checkpatch errors. Signed-off-by: Tobin C Harding --- mm/memory.c | 42 +- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/mm/memory.c b/mm/memory.c index 3562314..35fb8b2 100644 ---

[PATCH 0/4] mm: trivial sparse and checkpatch fixes

From: Tobin C Harding This patchset fixes trivial sparse and checkpatch errors/warnings. The majority of the changes are whitespace only. The only code changes are replace 0 with NULL, and remove extraneous braces around single statement. Patchset aims to only make changes when they objectively

[PATCH 1/4] mm: Fix sparse, use plain integer as NULL pointer

From: Tobin C Harding Patch fixes sparse warning: Using plain integer as NULL pointer. Replaces assignment of 0 to pointer with NULL assignment. Signed-off-by: Tobin C Harding --- mm/memory.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH 2/4] mm: Fix checkpatch warnings, whitespace

From: Tobin C Harding Patch fixes whitespace checkpatch warnings. Signed-off-by: Tobin C Harding --- mm/memory.c | 15 +++ 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/mm/memory.c b/mm/memory.c index cc5fa12..3562314 100644 ---

[PATCH 1/4] mm: Fix sparse, use plain integer as NULL pointer

From: Tobin C Harding Patch fixes sparse warning: Using plain integer as NULL pointer. Replaces assignment of 0 to pointer with NULL assignment. Signed-off-by: Tobin C Harding --- mm/memory.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/mm/memory.c b/mm/memory.c

[PATCH 2/4] mm: Fix checkpatch warnings, whitespace

From: Tobin C Harding Patch fixes whitespace checkpatch warnings. Signed-off-by: Tobin C Harding --- mm/memory.c | 15 +++ 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/mm/memory.c b/mm/memory.c index cc5fa12..3562314 100644 --- a/mm/memory.c +++ b/mm/memory.c @@

mmotm 2017-02-01-15-35 uploaded

The mm-of-the-moment snapshot 2017-02-01-15-35 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

mmotm 2017-02-01-15-35 uploaded

The mm-of-the-moment snapshot 2017-02-01-15-35 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

Re: [PATCH v3 3/4] driver property: constify property arrays values

On Wed, 2017-02-01 at 09:31 -0800, Dmitry Torokhov wrote: > Data that is fed into property arrays should not be modified, so let's mark > relevant pointers as const. This will allow us making source arrays as > const/__initconst. trivia: > diff --git a/drivers/base/property.c

Re: [PATCH v3 3/4] driver property: constify property arrays values

On Wed, 2017-02-01 at 09:31 -0800, Dmitry Torokhov wrote: > Data that is fed into property arrays should not be modified, so let's mark > relevant pointers as const. This will allow us making source arrays as > const/__initconst. trivia: > diff --git a/drivers/base/property.c

Re: net: suspicious RCU usage in nf_hook

On Wed, Feb 1, 2017 at 1:16 PM, Eric Dumazet wrote: > On Wed, 2017-02-01 at 12:51 -0800, Cong Wang wrote: >> On Tue, Jan 31, 2017 at 7:44 AM, Eric Dumazet wrote: >> > On Mon, 2017-01-30 at 22:19 -0800, Cong Wang wrote: >> > >> >> >> >> The context

Re: net: suspicious RCU usage in nf_hook

On Wed, Feb 1, 2017 at 1:16 PM, Eric Dumazet wrote: > On Wed, 2017-02-01 at 12:51 -0800, Cong Wang wrote: >> On Tue, Jan 31, 2017 at 7:44 AM, Eric Dumazet wrote: >> > On Mon, 2017-01-30 at 22:19 -0800, Cong Wang wrote: >> > >> >> >> >> The context is process context (TX path before hitting

Re: [PATCH] xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend()

On 01/31/2017 12:47 PM, Boris Ostrovsky wrote: > On 01/30/2017 02:31 PM, Boris Ostrovsky wrote: >> On 01/30/2017 02:06 PM, Eric Dumazet wrote: >>> On Mon, 2017-01-30 at 13:23 -0500, Boris Ostrovsky wrote: >>> We do netif_carrier_off() first thing in xennet_disconnect_backend() and the

Re: [PATCH] xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend()

On 01/31/2017 12:47 PM, Boris Ostrovsky wrote: > On 01/30/2017 02:31 PM, Boris Ostrovsky wrote: >> On 01/30/2017 02:06 PM, Eric Dumazet wrote: >>> On Mon, 2017-01-30 at 13:23 -0500, Boris Ostrovsky wrote: >>> We do netif_carrier_off() first thing in xennet_disconnect_backend() and the

Re: [PATCH v2] EDAC: mpc85xx: Add T2080 l2-cache support

On Thu, Feb 02, 2017 at 12:16:24PM +1300, Chris Packham wrote: > The l2-cache controller on the T2080 SoC has similar capabilities to the > others already supported by the mpc85xx_edac driver. Add it to the list > of compatible devices. > > Signed-off-by: Chris Packham

Re: [PATCH v2] EDAC: mpc85xx: Add T2080 l2-cache support

On Thu, Feb 02, 2017 at 12:16:24PM +1300, Chris Packham wrote: > The l2-cache controller on the T2080 SoC has similar capabilities to the > others already supported by the mpc85xx_edac driver. Add it to the list > of compatible devices. > > Signed-off-by: Chris Packham > Acked-by: Johannes

[PATCH v6 2/2] cpufreq: brcmstb-cpufreq: CPUfreq driver for older Broadcom STB SoCs

From: Markus Mayer This CPUfreq driver provides basic frequency scaling for older Broadcom STB SoCs that do not use AVS firmware with DVFS support. There is no support for voltage scaling. Signed-off-by: Markus Mayer Acked-by: Viresh Kumar

[PATCH v6 2/2] cpufreq: brcmstb-cpufreq: CPUfreq driver for older Broadcom STB SoCs

From: Markus Mayer This CPUfreq driver provides basic frequency scaling for older Broadcom STB SoCs that do not use AVS firmware with DVFS support. There is no support for voltage scaling. Signed-off-by: Markus Mayer Acked-by: Viresh Kumar --- drivers/cpufreq/Kconfig.arm | 12 ++

[PATCH v6 1/2] dt-bindings: brcm: clocks: add binding for brcmstb-cpu-clk-div

From: Markus Mayer Add binding document for brcm,brcmstb-cpu-clk-div. Signed-off-by: Markus Mayer --- .../bindings/clock/brcm,brcmstb-cpu-clk-div.txt| 22 ++ MAINTAINERS| 1 + 2 files

[PATCH v6 1/2] dt-bindings: brcm: clocks: add binding for brcmstb-cpu-clk-div

From: Markus Mayer Add binding document for brcm,brcmstb-cpu-clk-div. Signed-off-by: Markus Mayer --- .../bindings/clock/brcm,brcmstb-cpu-clk-div.txt| 22 ++ MAINTAINERS| 1 + 2 files changed, 23 insertions(+) create mode

[PATCH v6 0/2] cpufreq: brcmstb-cpufreq: CPUfreq driver for older Broadcom STB SoCs

From: Markus Mayer This CPUfreq driver provides basic frequency scaling for older Broadcom STB SoCs that do not use AVS firmware with DVFS support. There is no support for voltage scaling. v5 of this patch can be found at: https://lkml.org/lkml/2017/1/18/1093 Changes since

[PATCH v6 0/2] cpufreq: brcmstb-cpufreq: CPUfreq driver for older Broadcom STB SoCs

From: Markus Mayer This CPUfreq driver provides basic frequency scaling for older Broadcom STB SoCs that do not use AVS firmware with DVFS support. There is no support for voltage scaling. v5 of this patch can be found at: https://lkml.org/lkml/2017/1/18/1093 Changes since v5: - Removed DT

[PATCH] wcn36xx: Implement cancel_hw_scan

In the even that the wcn36xx interface is brought down while a hw_scan is active we must abort and wait for the ongoing scan to signal completion to mac80211. Reported-by: Mart Raudsepp Fixes: 886039036c20 ("wcn36xx: Implement firmware assisted scan") Signed-off-by: Bjorn

[PATCH] wcn36xx: Implement cancel_hw_scan

In the even that the wcn36xx interface is brought down while a hw_scan is active we must abort and wait for the ongoing scan to signal completion to mac80211. Reported-by: Mart Raudsepp Fixes: 886039036c20 ("wcn36xx: Implement firmware assisted scan") Signed-off-by: Bjorn Andersson ---

[RFC][PATCH 3/7] x86, mpx: extend MPX prctl() to pass in size of bounds directory

The MPX bounds tables are indexed by virtual address. A larger virtual address space means that we need larger tables. But, we need to ensure that userspace and the kernel agree about the size of these tables. To do this, we require that userspace passes in the size of the tables if they want

[RFC][PATCH 3/7] x86, mpx: extend MPX prctl() to pass in size of bounds directory

The MPX bounds tables are indexed by virtual address. A larger virtual address space means that we need larger tables. But, we need to ensure that userspace and the kernel agree about the size of these tables. To do this, we require that userspace passes in the size of the tables if they want

[RFC][PATCH 0/7] x86, mpx: Support larger address space (MAWA) (v2)

Changes from v1: * Added selftests support for this feature * Removed "mawa" nomenclature from all variables and functions * Added patch to cram new "mawa" value into existing MPX space in mmu_context_t * Optimize the switch_mpx_bd() code with a likely(). We will need to do a bit more

[RFC][PATCH 0/7] x86, mpx: Support larger address space (MAWA) (v2)

Changes from v1: * Added selftests support for this feature * Removed "mawa" nomenclature from all variables and functions * Added patch to cram new "mawa" value into existing MPX space in mmu_context_t * Optimize the switch_mpx_bd() code with a likely(). We will need to do a bit more

[RFC][PATCH 1/7] x86, mpx: introduce per-mm MPX table size tracking

Larger address spaces mean larger MPX bounds table sizes. This tracks which size tables we are using. "MAWA" is what the hardware documentation calls this feature: MPX Address-Width Adjust. --- b/arch/x86/include/asm/mmu.h |1 + b/arch/x86/include/asm/mpx.h |6 ++ 2 files

[RFC][PATCH 1/7] x86, mpx: introduce per-mm MPX table size tracking

Larger address spaces mean larger MPX bounds table sizes. This tracks which size tables we are using. "MAWA" is what the hardware documentation calls this feature: MPX Address-Width Adjust. --- b/arch/x86/include/asm/mmu.h |1 + b/arch/x86/include/asm/mpx.h |6 ++ 2 files

[RFC][PATCH 6/7] x86, mpx, selftests: Use prctl header instead of magic numbers

I got away with just hard-coding the prctl() numbers in the MPX selftests. Include the kernel header so we can just use the symbolic names. --- b/tools/testing/selftests/x86/mpx-mini-test.c |6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff -puN

[RFC][PATCH 6/7] x86, mpx, selftests: Use prctl header instead of magic numbers

I got away with just hard-coding the prctl() numbers in the MPX selftests. Include the kernel header so we can just use the symbolic names. --- b/tools/testing/selftests/x86/mpx-mini-test.c |6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff -puN

Re: [PATCH 5/5] soc/qcom: Move qcom_mdt_loader from remoteproc

On Mon, Jan 30, 2017 at 08:55:47AM -0800, Bjorn Andersson wrote: > With the remoteproc parts cleaned out of the MDT loader we can move it > to drivers/soc/qcom. > diff --git a/drivers/soc/qcom/Kconfig b/drivers/soc/qcom/Kconfig > index 461b387d03cc..78b1bb7bcf20 100644 > ---

[RFC][PATCH 5/7] x86, mpx: shrink per-mm MPX data

We have three pieces of data that we need to store about MPX's operation: 1. Is kernel management on/off? 2. If it's on, where is the bounds directory located? 3. If it's on, how big is the bounds directory? We keep all this data in the mm_context_t. Currently, #1 and #2 are stored in 'bd_addr'

Re: [PATCH 5/5] soc/qcom: Move qcom_mdt_loader from remoteproc

On Mon, Jan 30, 2017 at 08:55:47AM -0800, Bjorn Andersson wrote: > With the remoteproc parts cleaned out of the MDT loader we can move it > to drivers/soc/qcom. > diff --git a/drivers/soc/qcom/Kconfig b/drivers/soc/qcom/Kconfig > index 461b387d03cc..78b1bb7bcf20 100644 > ---

[RFC][PATCH 5/7] x86, mpx: shrink per-mm MPX data

We have three pieces of data that we need to store about MPX's operation: 1. Is kernel management on/off? 2. If it's on, where is the bounds directory located? 3. If it's on, how big is the bounds directory? We keep all this data in the mm_context_t. Currently, #1 and #2 are stored in 'bd_addr'

[RFC][PATCH 4/7] x86, mpx: context-switch new MPX address size MSR

As mentioned in previous patches, larger address spaces mean larger MPX tables. But, the entire system is either entirely using 5-level paging, or not. We do not mix pagetable formats. If the size of the MPX tables depended soley on the paging mode, old binaries would break because the format

[RFC][PATCH 2/7] x86, mpx: update MPX to grok larger bounds tables

The MPX code in the kernel needs to walk these tables in order to populate them on demand as well as unmap them when memory is freed. A larger virtual address space means larger MPX bounds tables. Update the bounds table walking code to understand how to walk the larger table size. We use the

[RFC][PATCH 4/7] x86, mpx: context-switch new MPX address size MSR

As mentioned in previous patches, larger address spaces mean larger MPX tables. But, the entire system is either entirely using 5-level paging, or not. We do not mix pagetable formats. If the size of the MPX tables depended soley on the paging mode, old binaries would break because the format

[RFC][PATCH 2/7] x86, mpx: update MPX to grok larger bounds tables

The MPX code in the kernel needs to walk these tables in order to populate them on demand as well as unmap them when memory is freed. A larger virtual address space means larger MPX bounds tables. Update the bounds table walking code to understand how to walk the larger table size. We use the

[RFC][PATCH 7/7] x86, mpx: update MPX selftest to test larger bounds dir

Since the bounds directory is changing its size, we also need to update userspace to allocate a larger one. This adds support to the MPX selftests to detect hardware where we need a larger bounds directory and attempts to enable MPX support for the larger directory. The messiest thing here is

[RFC][PATCH 7/7] x86, mpx: update MPX selftest to test larger bounds dir

Since the bounds directory is changing its size, we also need to update userspace to allocate a larger one. This adds support to the MPX selftests to detect hardware where we need a larger bounds directory and attempts to enable MPX support for the larger directory. The messiest thing here is

Re: [PATCH V8 08/10] ras: acpi / apei: generate trace event for unrecognized CPER section

Hi Tyler, [auto build test ERROR on pm/linux-next] [also build test ERROR on v4.10-rc6 next-20170201] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Tyler-Baicar/Add-UEFI-2-6-and-ACPI-6-1

Re: [PATCH V8 08/10] ras: acpi / apei: generate trace event for unrecognized CPER section

Hi Tyler, [auto build test ERROR on pm/linux-next] [also build test ERROR on v4.10-rc6 next-20170201] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Tyler-Baicar/Add-UEFI-2-6-and-ACPI-6-1

[PATCH] tty: serial: cpm_uart: make use of for_each_node_by_type()

Instead of open-coding loop with of_find_node_by_type(), let's use canned macro. Signed-off-by: Dmitry Torokhov --- drivers/tty/serial/cpm_uart/cpm_uart_core.c | 18 ++ 1 file changed, 10 insertions(+), 8 deletions(-) diff --git

[PATCH] tty: serial: cpm_uart: make use of for_each_node_by_type()

Instead of open-coding loop with of_find_node_by_type(), let's use canned macro. Signed-off-by: Dmitry Torokhov --- drivers/tty/serial/cpm_uart/cpm_uart_core.c | 18 ++ 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/drivers/tty/serial/cpm_uart/cpm_uart_core.c

[PATCH v2] EDAC: mpc85xx: Add T2080 l2-cache support

The l2-cache controller on the T2080 SoC has similar capabilities to the others already supported by the mpc85xx_edac driver. Add it to the list of compatible devices. Signed-off-by: Chris Packham Acked-by: Johannes Thumshirn --- This is a

[PATCH v2] EDAC: mpc85xx: Add T2080 l2-cache support

The l2-cache controller on the T2080 SoC has similar capabilities to the others already supported by the mpc85xx_edac driver. Add it to the list of compatible devices. Signed-off-by: Chris Packham Acked-by: Johannes Thumshirn --- This is a resend of a patch that got an ack[1] but didn't seem to

Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes

On Wed, Feb 1, 2017 at 12:08 PM Luck, Tony wrote: > > > I was asking for requirements, not a design proposal. In order to make a > > design you need a requirements specification. > > Here's what I came up with ... not a fully baked list, but should allow for > some useful >

Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes

On Wed, Feb 1, 2017 at 12:08 PM Luck, Tony wrote: > > > I was asking for requirements, not a design proposal. In order to make a > > design you need a requirements specification. > > Here's what I came up with ... not a fully baked list, but should allow for > some useful > discussion on whether

Re: [PATCH] prctl: implement PR_GET_ENDIAN for all architectures

On Tue, 2017-01-31 at 16:26 -0800, Andrew Morton wrote: > On Sat, 28 Jan 2017 12:13:10 +0100 Helge Deller > wrote: > > > The prctl(PR_GET_ENDIAN) syscall was added to Kernel 2.6.18, but > > implemented for PowerPC only. This trivial patch adds support for > > this syscall for all

Re: [PATCH] prctl: implement PR_GET_ENDIAN for all architectures

On Tue, 2017-01-31 at 16:26 -0800, Andrew Morton wrote: > On Sat, 28 Jan 2017 12:13:10 +0100 Helge Deller > wrote: > > > The prctl(PR_GET_ENDIAN) syscall was added to Kernel 2.6.18, but > > implemented for PowerPC only. This trivial patch adds support for > > this syscall for all other

[PATCH] sh: make use of for_each_node_by_type()

Instead of open-coding the loop, let's use canned macro. Also make sure we are not leaking last OF node reference. Signed-off-by: Dmitry Torokhov --- arch/sh/boards/of-generic.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git

[PATCH] sh: make use of for_each_node_by_type()

Instead of open-coding the loop, let's use canned macro. Also make sure we are not leaking last OF node reference. Signed-off-by: Dmitry Torokhov --- arch/sh/boards/of-generic.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/arch/sh/boards/of-generic.c

[PATCH] Kbuild: support designated_init attribute

If a structure is marked with __attribute__((designated_init)) from GCC or Sparse, it needs to have all static initializers using designated initialization. Fail the build for any missing cases. This attribute will be used by the randstruct plugin to make sure randomized structures are being

[PATCH] Kbuild: support designated_init attribute

If a structure is marked with __attribute__((designated_init)) from GCC or Sparse, it needs to have all static initializers using designated initialization. Fail the build for any missing cases. This attribute will be used by the randstruct plugin to make sure randomized structures are being

[PATCH] arm64: make use of for_each_node_by_type()

Instead of open-coding the loop, let's use canned macro. Signed-off-by: Dmitry Torokhov --- This will also be needed if I manage to make of_find_node_by_type() stop dropping reference to starting node as it is quite unexpected thing to do. arch/arm64/kernel/smp.c |

[PATCH] arm64: make use of for_each_node_by_type()

Instead of open-coding the loop, let's use canned macro. Signed-off-by: Dmitry Torokhov --- This will also be needed if I manage to make of_find_node_by_type() stop dropping reference to starting node as it is quite unexpected thing to do. arch/arm64/kernel/smp.c | 4 ++-- 1 file changed, 2

Re: [PATCH] efi: fdt: avoid FDT manipulation after ExitBootServices()

On 2/1/2017 2:08 PM, Jeffrey Hugo wrote: On 2/1/2017 10:45 AM, Ard Biesheuvel wrote: Some AArch64 UEFI implementations disable the MMU in ExitBootServices(), after which unaligned accesses to RAM are no longer supported. Commit abfb7b686a3e ("efi/libstub/arm*: Pass latest memory map to the

Re: [PATCH] efi: fdt: avoid FDT manipulation after ExitBootServices()

On 2/1/2017 2:08 PM, Jeffrey Hugo wrote: On 2/1/2017 10:45 AM, Ard Biesheuvel wrote: Some AArch64 UEFI implementations disable the MMU in ExitBootServices(), after which unaligned accesses to RAM are no longer supported. Commit abfb7b686a3e ("efi/libstub/arm*: Pass latest memory map to the

<    1   2   3   4   5   6   7   8   9   10   >