Re: microblaze fails to to compile with allmodconfig

Hi Michal, 2017-09-15 21:17 GMT+09:00 Michal Simek : > Hi Michal and Geert, +Nicolas and Masahiro > > On 14.9.2017 11:19, Geert Uytterhoeven wrote: >> Hi Michal, >> >> On Thu, Sep 14, 2017 at 11:07 AM, Michal Hocko wrote: >>> I've started seeing the

Re: microblaze fails to to compile with allmodconfig

Hi Michal, 2017-09-15 21:17 GMT+09:00 Michal Simek : > Hi Michal and Geert, +Nicolas and Masahiro > > On 14.9.2017 11:19, Geert Uytterhoeven wrote: >> Hi Michal, >> >> On Thu, Sep 14, 2017 at 11:07 AM, Michal Hocko wrote: >>> I've started seeing the following compilation failures with

Re: [Xen-devel] [PATCH 4/4] xen: select grant interface version

On 13/09/17 11:23, Juergen Gross wrote: > On 12/09/17 20:54, Andrew Cooper wrote: >> On 08/09/17 15:48, Juergen Gross wrote: >>> static void gnttab_request_version(void) >>> { >>> - int rc; >>> + long rc; >>> struct gnttab_set_version gsv; >>> >>> - gsv.version = 1; >>> + rc =

Re: [Xen-devel] [PATCH 4/4] xen: select grant interface version

On 13/09/17 11:23, Juergen Gross wrote: > On 12/09/17 20:54, Andrew Cooper wrote: >> On 08/09/17 15:48, Juergen Gross wrote: >>> static void gnttab_request_version(void) >>> { >>> - int rc; >>> + long rc; >>> struct gnttab_set_version gsv; >>> >>> - gsv.version = 1; >>> + rc =

imx6: CSI for ADCs (fpga)

Hi folks, did anyone already use the imx6's csi port for anything other than cameras ? I'm thinking about using it for an ADC (in fpga). Theoretically it should be possible to transfer non-video data, but the question here is whether the ipu might interfer here (eg. trying colorspace

imx6: CSI for ADCs (fpga)

Hi folks, did anyone already use the imx6's csi port for anything other than cameras ? I'm thinking about using it for an ADC (in fpga). Theoretically it should be possible to transfer non-video data, but the question here is whether the ipu might interfer here (eg. trying colorspace

[PATCH v3] PCI: quirks: update Cavium ThunderX ACS quirk implementation

This commit makes Cavium PCI ACS quirk applicable only to Cavium ThunderX (CN81/83/88XX) PCIE Root Ports which has limited PCI capabilities in terms of no ACS support advertisement. However, the RTL internally implements similar protection as if ACS had completion redirection, blocking and

[PATCH v3] PCI: quirks: update Cavium ThunderX ACS quirk implementation

This commit makes Cavium PCI ACS quirk applicable only to Cavium ThunderX (CN81/83/88XX) PCIE Root Ports which has limited PCI capabilities in terms of no ACS support advertisement. However, the RTL internally implements similar protection as if ACS had completion redirection, blocking and

Re: d57108d4f6 ("watchdog/core: Get rid of the thread .."): BUG: unable to handle kernel NULL pointer dereference at 0000000000000208

On Fri, 15 Sep 2017, Thomas Gleixner wrote: > On Fri, 15 Sep 2017, kernel test robot wrote: > > [0.035023] CPU: Intel Common KVM processor (family: 0xf, model: 0x6, > > stepping: 0x1) > > [0.042302] Performance Events: unsupported Netburst CPU model 6 no PMU > > driver, software events

Re: d57108d4f6 ("watchdog/core: Get rid of the thread .."): BUG: unable to handle kernel NULL pointer dereference at 0000000000000208

On Fri, 15 Sep 2017, Thomas Gleixner wrote: > On Fri, 15 Sep 2017, kernel test robot wrote: > > [0.035023] CPU: Intel Common KVM processor (family: 0xf, model: 0x6, > > stepping: 0x1) > > [0.042302] Performance Events: unsupported Netburst CPU model 6 no PMU > > driver, software events

Re: [mainline][DLPAR][Oops] OF: ERROR: Bad of_node_put() on /cpus

On Fri, Sep 15, 2017 at 6:04 AM, abdul wrote: > Hi, > > Mainline kernel panics during DLPAR CPU add/remove operation. > > Machine Type: Power8 PowerVM LPAR > kernel 4.13.0 Did 4.12 work or when was it last working? I'm not seeing anything recent in the DT code that

Re: [mainline][DLPAR][Oops] OF: ERROR: Bad of_node_put() on /cpus

On Fri, Sep 15, 2017 at 6:04 AM, abdul wrote: > Hi, > > Mainline kernel panics during DLPAR CPU add/remove operation. > > Machine Type: Power8 PowerVM LPAR > kernel 4.13.0 Did 4.12 work or when was it last working? I'm not seeing anything recent in the DT code that looks suspicious. Rob

[PATCH bisected regression in 4.14] PCI: fix race while enabling upstream bridges concurrently

In pci_enable_bridge() pci_enable_device() is called before calling pci_set_master(), thus check pci_is_enabled() becomes true in the middle of this sequence. As a result in pci_enable_device_flags() concurrent enable of device on same bridge could think that this bridge is completely enabled, but

[PATCH bisected regression in 4.14] PCI: fix race while enabling upstream bridges concurrently

In pci_enable_bridge() pci_enable_device() is called before calling pci_set_master(), thus check pci_is_enabled() becomes true in the middle of this sequence. As a result in pci_enable_device_flags() concurrent enable of device on same bridge could think that this bridge is completely enabled, but

[PULL REQUEST] i2c for 4.14

Linus, I2C has two more, new drivers: Altera FPGA and STM32F7. Please pull. Thanks, Wolfram The following changes since commit 46c1e79fee417f151547aa46fae04ab06cb666f4: Merge branch 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2017-09-13 12:24:20

[PULL REQUEST] i2c for 4.14

Linus, I2C has two more, new drivers: Altera FPGA and STM32F7. Please pull. Thanks, Wolfram The following changes since commit 46c1e79fee417f151547aa46fae04ab06cb666f4: Merge branch 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2017-09-13 12:24:20

Re: [PATCH v2 3/4] tpm: reduce tpm_msleep() time in get_burstcount()

On 09/13/2017 06:30 AM, Jarkko Sakkinen wrote: On Wed, Sep 06, 2017 at 08:56:38AM -0400, Nayna Jain wrote: Currently, get_burstcount() function sleeps for 5msec in a loop before retrying for next query to burstcount. However, if it takes lesser time for TPM to return, this 5 msec delay is

Re: [PATCH v2 3/4] tpm: reduce tpm_msleep() time in get_burstcount()

On 09/13/2017 06:30 AM, Jarkko Sakkinen wrote: On Wed, Sep 06, 2017 at 08:56:38AM -0400, Nayna Jain wrote: Currently, get_burstcount() function sleeps for 5msec in a loop before retrying for next query to burstcount. However, if it takes lesser time for TPM to return, this 5 msec delay is

Re: [PATCH v3 04/20] mm: VMA sequence count

Hi, On 14/09/2017 11:40, Sergey Senozhatsky wrote: > On (09/14/17 11:15), Laurent Dufour wrote: >> On 14/09/2017 11:11, Sergey Senozhatsky wrote: >>> On (09/14/17 10:58), Laurent Dufour wrote: >>> [..] That's right, but here this is the sequence counter mm->mm_seq, not the vm_seq one.

Re: [PATCH v3 04/20] mm: VMA sequence count

Hi, On 14/09/2017 11:40, Sergey Senozhatsky wrote: > On (09/14/17 11:15), Laurent Dufour wrote: >> On 14/09/2017 11:11, Sergey Senozhatsky wrote: >>> On (09/14/17 10:58), Laurent Dufour wrote: >>> [..] That's right, but here this is the sequence counter mm->mm_seq, not the vm_seq one.

Re: [PATCH v2 2/4] tpm: define __wait_for_tpm_stat to specify variable polling sleep time

On 09/13/2017 06:28 AM, Jarkko Sakkinen wrote: On Wed, Sep 06, 2017 at 08:56:37AM -0400, Nayna Jain wrote: The existing wait_for_tpm_stat() checks the chip status before sleeping for 5 msec in a polling loop. For some functions although the status isn't ready immediately, the status returns

Re: [PATCH v2 2/4] tpm: define __wait_for_tpm_stat to specify variable polling sleep time

On 09/13/2017 06:28 AM, Jarkko Sakkinen wrote: On Wed, Sep 06, 2017 at 08:56:37AM -0400, Nayna Jain wrote: The existing wait_for_tpm_stat() checks the chip status before sleeping for 5 msec in a polling loop. For some functions although the status isn't ready immediately, the status returns

[PATCH] lightnvm: pblk: remove I/O dependency on write path

pblk schedules user I/O, metadata I/O and erases on the write path in order to minimize collisions at the media level. Until now, there has been a dependency between user and metadata I/Os that could lead to a deadlock as both take the per-LUN semaphore to schedule submission. This path removes

[PATCH] lightnvm: pblk: remove redundant check on read path

A partial read I/O in pblk is an I/O where some sectors reside in the write buffer in main memory and some are persisted on the device. Such an I/O must at least contain 2 lbas, therefore checking for the case where a single lba is mapped is not necessary. Signed-off-by: Javier González

[PATCH] lightnvm: pblk: remove I/O dependency on write path

pblk schedules user I/O, metadata I/O and erases on the write path in order to minimize collisions at the media level. Until now, there has been a dependency between user and metadata I/Os that could lead to a deadlock as both take the per-LUN semaphore to schedule submission. This path removes

[PATCH] lightnvm: pblk: remove redundant check on read path

A partial read I/O in pblk is an I/O where some sectors reside in the write buffer in main memory and some are persisted on the device. Such an I/O must at least contain 2 lbas, therefore checking for the case where a single lba is mapped is not necessary. Signed-off-by: Javier González ---

[PATCH] staging: rtlwifi: delete double assignment

Remove two adjacent assignments to the same location. In practice, many such occurences are intentional but this case don't seem to fall into that category. Done using following coccinelle semantic patch @@ expression e1,e2,e3; @@ ( (<+...e1++...+>)=e2; | (<+...e1--...+>)=e2; |

[PATCH] staging: rtlwifi: delete double assignment

Remove two adjacent assignments to the same location. In practice, many such occurences are intentional but this case don't seem to fall into that category. Done using following coccinelle semantic patch @@ expression e1,e2,e3; @@ ( (<+...e1++...+>)=e2; | (<+...e1--...+>)=e2; |

[PATCH] lightnvm: pblk: check lba sanity on read path

As part of pblk's recovery scheme, we store the lba mapped to each physical sector on the device's out-of-bound (OOB) area. On the read path, we can use this information to validate that the data being delivered to the upper layers corresponds to the lba being requested. The cost of this check is

[PATCH] lightnvm: pblk: check lba sanity on read path

As part of pblk's recovery scheme, we store the lba mapped to each physical sector on the device's out-of-bound (OOB) area. On the read path, we can use this information to validate that the data being delivered to the upper layers corresponds to the lba being requested. The cost of this check is

[PATCH] lightnvm: pblk: ensure right bad block calculation

Make sure that the variable controlling block threshold for allocating extra metadata sectors in case of a line with bad blocks does not get a negative value. Otherwise, the line will be marked as corrupted and wasted. Signed-off-by: Javier González ---

[PATCH] lightnvm: pblk: ensure right bad block calculation

Make sure that the variable controlling block threshold for allocating extra metadata sectors in case of a line with bad blocks does not get a negative value. Otherwise, the line will be marked as corrupted and wasted. Signed-off-by: Javier González --- drivers/lightnvm/pblk-init.c | 2 +- 1

[PATCH] lightnvm: pblk: guarantee line integrity on reads

When a line is recycled during garbage collection, reads can still be issued to the line. If the line is freed in the middle of this process, data corruption might occur. This patch guarantees that lines are not freed in the middle of reads that target them (lines). Specifically, we use the

[PATCH] lightnvm: pblk: guarantee line integrity on reads

When a line is recycled during garbage collection, reads can still be issued to the line. If the line is freed in the middle of this process, data corruption might occur. This patch guarantees that lines are not freed in the middle of reads that target them (lines). Specifically, we use the

[PATCH] lightnvm: pblk: enable 1 LUN configuration

Metadata I/Os are scheduled to minimize their impact on user data I/Os. When there are enough LUNs instantiated (i.e., enought bandwidth), it is easy to interleave metadata and data one after the other so that metadata I/Os are the ones being blocked and not viceversa. We do this by calculating

[PATCH] lightnvm: pblk: enable 1 LUN configuration

Metadata I/Os are scheduled to minimize their impact on user data I/Os. When there are enough LUNs instantiated (i.e., enought bandwidth), it is easy to interleave metadata and data one after the other so that metadata I/Os are the ones being blocked and not viceversa. We do this by calculating

Re: [PATCH v2 1/4] tpm: ignore burstcount to improve tpm_tis send() performance.

On 09/14/2017 04:40 AM, Jarkko Sakkinen wrote: On Wed, Sep 13, 2017 at 11:39:03AM -0700, Peter Huewe wrote: Am 12. September 2017 17:45:08 GMT-07:00 schrieb Jarkko Sakkinen : On Wed, Sep 06, 2017 at 08:56:36AM -0400, Nayna Jain wrote: The TPM burstcount

Re: [PATCH v2 1/4] tpm: ignore burstcount to improve tpm_tis send() performance.

On 09/14/2017 04:40 AM, Jarkko Sakkinen wrote: On Wed, Sep 13, 2017 at 11:39:03AM -0700, Peter Huewe wrote: Am 12. September 2017 17:45:08 GMT-07:00 schrieb Jarkko Sakkinen : On Wed, Sep 06, 2017 at 08:56:36AM -0400, Nayna Jain wrote: The TPM burstcount status indicates the number of

[PATCH 02/11] lightnvm: pblk: normalize ppa namings

Normalize the way we name ppa variables to improve code readability. Signed-off-by: Javier González --- drivers/lightnvm/pblk-core.c | 48 +++- 1 file changed, 25 insertions(+), 23 deletions(-) diff --git

[PATCH 02/11] lightnvm: pblk: normalize ppa namings

Normalize the way we name ppa variables to improve code readability. Signed-off-by: Javier González --- drivers/lightnvm/pblk-core.c | 48 +++- 1 file changed, 25 insertions(+), 23 deletions(-) diff --git a/drivers/lightnvm/pblk-core.c

[PATCH 03/11] lightnvm: pblk: refactor read lba sanity check

Refactor lba sanity check on read path to avoid code duplication. Signed-off-by: Javier González --- drivers/lightnvm/pblk-read.c | 29 ++--- 1 file changed, 10 insertions(+), 19 deletions(-) diff --git a/drivers/lightnvm/pblk-read.c

[PATCH 03/11] lightnvm: pblk: refactor read lba sanity check

Refactor lba sanity check on read path to avoid code duplication. Signed-off-by: Javier González --- drivers/lightnvm/pblk-read.c | 29 ++--- 1 file changed, 10 insertions(+), 19 deletions(-) diff --git a/drivers/lightnvm/pblk-read.c b/drivers/lightnvm/pblk-read.c index

[PATCH 04/11] lightnvm: pblk: simplify data validity check on GC

When a line is selected for recycling by the garbage collector (GC), the line state changes and the invalid bitmap is frozen, preventing invalidations from happening. Throughout the GC, the L2P map is checked to verify that not data being recycled has been updated. The last check is done before

[PATCH 04/11] lightnvm: pblk: simplify data validity check on GC

When a line is selected for recycling by the garbage collector (GC), the line state changes and the invalid bitmap is frozen, preventing invalidations from happening. Throughout the GC, the L2P map is checked to verify that not data being recycled has been updated. The last check is done before

[PATCH 05/11] lightnvm: pblk: refactor read path on GC

Simplify the part of the garbage collector where data is read from the line being recycled and moved into an internal queue before being copied to the memory buffer. This allows to get rid of a dedicated function, which introduces an unnecessary dependency on the code. Signed-off-by: Javier

[PATCH 05/11] lightnvm: pblk: refactor read path on GC

Simplify the part of the garbage collector where data is read from the line being recycled and moved into an internal queue before being copied to the memory buffer. This allows to get rid of a dedicated function, which introduces an unnecessary dependency on the code. Signed-off-by: Javier

[PATCH 06/11] lightnvm: pblk: put bio on bio completion

Simplify put bio by doing it on bio end_io instead of manually putting it on the completion path. Signed-off-by: Javier González --- drivers/lightnvm/pblk-core.c | 10 +++--- drivers/lightnvm/pblk-read.c | 1 - drivers/lightnvm/pblk-recovery.c | 1 -

[PATCH 00/11] lightnvm: pblk: cleanup

This patchset is a general cleanup to improve code readability. Javier González (11): lightnvm: pblk: use constant for GC max inflight lightnvm: pblk: normalize ppa namings lightnvm: pblk: refactor read lba sanity check lightnvm: pblk: simplify data validity check on GC lightnvm: pblk:

[PATCH 06/11] lightnvm: pblk: put bio on bio completion

Simplify put bio by doing it on bio end_io instead of manually putting it on the completion path. Signed-off-by: Javier González --- drivers/lightnvm/pblk-core.c | 10 +++--- drivers/lightnvm/pblk-read.c | 1 - drivers/lightnvm/pblk-recovery.c | 1 - drivers/lightnvm/pblk-write.c

[PATCH 00/11] lightnvm: pblk: cleanup

This patchset is a general cleanup to improve code readability. Javier González (11): lightnvm: pblk: use constant for GC max inflight lightnvm: pblk: normalize ppa namings lightnvm: pblk: refactor read lba sanity check lightnvm: pblk: simplify data validity check on GC lightnvm: pblk:

[PATCH 09/11] lightnvm: pblk: improve naming for internal req.

Each request type sent to the LightNVM subsystem requires different metadata. Until now, we have tailored this metadata based on write, read and erase commands. However, pblk uses different metadata for internal writes that do not hit the write buffer. Instead of abusing the metadata for reads,

[PATCH 09/11] lightnvm: pblk: improve naming for internal req.

Each request type sent to the LightNVM subsystem requires different metadata. Until now, we have tailored this metadata based on write, read and erase commands. However, pblk uses different metadata for internal writes that do not hit the write buffer. Instead of abusing the metadata for reads,

[PATCH 01/11] lightnvm: pblk: use constant for GC max inflight

Use a constant to set the maximum number of inflight GC requests allowed. Signed-off-by: Javier González --- drivers/lightnvm/pblk-gc.c | 4 ++-- drivers/lightnvm/pblk.h| 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/lightnvm/pblk-gc.c

[PATCH 01/11] lightnvm: pblk: use constant for GC max inflight

Use a constant to set the maximum number of inflight GC requests allowed. Signed-off-by: Javier González --- drivers/lightnvm/pblk-gc.c | 4 ++-- drivers/lightnvm/pblk.h| 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/lightnvm/pblk-gc.c

Re: [RFC] KVM: arm/arm64: Introduce KVM_DEV_ARM_ITS_CTRL_RESET

Hi, On 14/09/2017 19:06, Marc Zyngier wrote: > On Thu, Sep 14 2017 at 10:57:28 am BST, Eric Auger > wrote: >> At the moment, the in-kernel emulated ITS is not properly reset. >> On guest restart/reset some registers keep their old values and >> internal structures like

[PATCH 10/11] lightnvm: pblk: refactor rqd alloc/free

Refactor the rqd allocation and free functions so that all I/O types can use these helper functions. Signed-off-by: Javier González --- drivers/lightnvm/pblk-core.c | 40 ++-- drivers/lightnvm/pblk-read.c | 2 --

Re: [RFC] KVM: arm/arm64: Introduce KVM_DEV_ARM_ITS_CTRL_RESET

Hi, On 14/09/2017 19:06, Marc Zyngier wrote: > On Thu, Sep 14 2017 at 10:57:28 am BST, Eric Auger > wrote: >> At the moment, the in-kernel emulated ITS is not properly reset. >> On guest restart/reset some registers keep their old values and >> internal structures like device, ITE, collection

[PATCH 10/11] lightnvm: pblk: refactor rqd alloc/free

Refactor the rqd allocation and free functions so that all I/O types can use these helper functions. Signed-off-by: Javier González --- drivers/lightnvm/pblk-core.c | 40 ++-- drivers/lightnvm/pblk-read.c | 2 -- drivers/lightnvm/pblk-recovery.c | 2

[PATCH 07/11] lightnvm: pblk: simplify path on REQ_PREFLUSH

On REQ_PREFLUSH, directly tag the I/O context flags to signal a flush in the write to cache path, instead of finding the correct entry context and imposing a memory barrier. This simplifies the code and might potentially prevent race conditions when adding functionality to the write path.

[PATCH 07/11] lightnvm: pblk: simplify path on REQ_PREFLUSH

On REQ_PREFLUSH, directly tag the I/O context flags to signal a flush in the write to cache path, instead of finding the correct entry context and imposing a memory barrier. This simplifies the code and might potentially prevent race conditions when adding functionality to the write path.

[PATCH 11/11] lightnvm: pblk: use rqd->end_io for completion

For consistency with the rest of pblk, use rqd->end_io to point to the function taking care of ending the request on the completion path. Signed-off-by: Javier González --- drivers/lightnvm/pblk-core.c | 7 --- drivers/lightnvm/pblk-read.c | 5 ++--- 2 files changed, 2

[PATCH 11/11] lightnvm: pblk: use rqd->end_io for completion

For consistency with the rest of pblk, use rqd->end_io to point to the function taking care of ending the request on the completion path. Signed-off-by: Javier González --- drivers/lightnvm/pblk-core.c | 7 --- drivers/lightnvm/pblk-read.c | 5 ++--- 2 files changed, 2 insertions(+), 10

[PATCH 08/11] lightnvm: pblk: allocate bio size more accurately

Wait until we know the exact number of ppas to be sent to the device, before allocating the bio. Signed-off-by: Javier González --- drivers/lightnvm/pblk-rb.c| 5 +++-- drivers/lightnvm/pblk-write.c | 20 ++-- drivers/lightnvm/pblk.h | 4 ++-- 3

[PATCH 08/11] lightnvm: pblk: allocate bio size more accurately

Wait until we know the exact number of ppas to be sent to the device, before allocating the bio. Signed-off-by: Javier González --- drivers/lightnvm/pblk-rb.c| 5 +++-- drivers/lightnvm/pblk-write.c | 20 ++-- drivers/lightnvm/pblk.h | 4 ++-- 3 files changed, 15

Re: [RFC Part1 PATCH v3 13/17] x86/io: Unroll string I/O when SEV is active

On Tue, Aug 22, 2017 at 06:52:48PM +0200, Borislav Petkov wrote: > As always, the devil is in the detail. Ok, actually we can make this much simpler by using a static key. A conceptual patch below - I only need to fix that crazy include hell I'm stepping into with this. In any case, we were

Re: [RFC Part1 PATCH v3 13/17] x86/io: Unroll string I/O when SEV is active

On Tue, Aug 22, 2017 at 06:52:48PM +0200, Borislav Petkov wrote: > As always, the devil is in the detail. Ok, actually we can make this much simpler by using a static key. A conceptual patch below - I only need to fix that crazy include hell I'm stepping into with this. In any case, we were

Re: microblaze fails to to compile with allmodconfig

Hi Michal and Geert, +Nicolas and Masahiro On 14.9.2017 11:19, Geert Uytterhoeven wrote: > Hi Michal, > > On Thu, Sep 14, 2017 at 11:07 AM, Michal Hocko wrote: >> I've started seeing the following compilation failures with microblaze >> with the current linux-next

Re: microblaze fails to to compile with allmodconfig

Hi Michal and Geert, +Nicolas and Masahiro On 14.9.2017 11:19, Geert Uytterhoeven wrote: > Hi Michal, > > On Thu, Sep 14, 2017 at 11:07 AM, Michal Hocko wrote: >> I've started seeing the following compilation failures with microblaze >> with the current linux-next (next-20170913). I have no

frv-linux-ld: Warning: size of symbol `sys_add_key' changed from 8 in kernel/sys_ni.o to 500 in security/keys/keyctl.o

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 711aab1dbb324d321e3d84368a435a78908c7bce commit: 799c43415442414b1032580c47684cb709dfed6d kbuild: thin archives make default for all archs date: 3 months ago config: frv-defconfig (attached as .config)

frv-linux-ld: Warning: size of symbol `sys_add_key' changed from 8 in kernel/sys_ni.o to 500 in security/keys/keyctl.o

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 711aab1dbb324d321e3d84368a435a78908c7bce commit: 799c43415442414b1032580c47684cb709dfed6d kbuild: thin archives make default for all archs date: 3 months ago config: frv-defconfig (attached as .config)

Re: [PATCH 3/3] mm: oom: show unreclaimable slab info when kernel panic

On 2017/09/15 2:14, Yang Shi wrote: > @@ -1274,6 +1276,29 @@ static int slab_show(struct seq_file *m, void *p) > return 0; > } > > +void show_unreclaimable_slab() > +{ > + struct kmem_cache *s = NULL; > + struct slabinfo sinfo; > + > + memset(, 0, sizeof(sinfo)); > + > +

Re: [PATCH 3/3] mm: oom: show unreclaimable slab info when kernel panic

On 2017/09/15 2:14, Yang Shi wrote: > @@ -1274,6 +1276,29 @@ static int slab_show(struct seq_file *m, void *p) > return 0; > } > > +void show_unreclaimable_slab() > +{ > + struct kmem_cache *s = NULL; > + struct slabinfo sinfo; > + > + memset(, 0, sizeof(sinfo)); > + > +

Re: Detecting page cache trashing state

Dne 15.9.2017 v 02:16 Taras Kondratiuk napsal(a): Hi In our devices under low memory conditions we often get into a trashing state when system spends most of the time re-reading pages of .text sections from a file system (squashfs in our case). Working set doesn't fit into available page cache,

Re: Detecting page cache trashing state

Dne 15.9.2017 v 02:16 Taras Kondratiuk napsal(a): Hi In our devices under low memory conditions we often get into a trashing state when system spends most of the time re-reading pages of .text sections from a file system (squashfs in our case). Working set doesn't fit into available page cache,

Re: [PATCH v2 0/7] swait: Introduce and use swq_has_sleeper()

On 13/09/2017 22:08, Davidlohr Bueso wrote: > The following patches fix and/or justify (in baby steps) some of the > callers. The main exception is s390, which I didn't follow how ->valid_wakeup > can get hoisted as kvm_vcpu_block does not use that in the wait loop. valid_wakeup is just an

Re: [PATCH v2 0/7] swait: Introduce and use swq_has_sleeper()

On 13/09/2017 22:08, Davidlohr Bueso wrote: > The following patches fix and/or justify (in baby steps) some of the > callers. The main exception is s390, which I didn't follow how ->valid_wakeup > can get hoisted as kvm_vcpu_block does not use that in the wait loop. valid_wakeup is just an

Re: [PATCH 2/3] mm: Handle numa statistics distinctively based-on different VM stats modes

On Fri 15-09-17 17:23:25, Kemi Wang wrote: [...] > @@ -2743,6 +2745,17 @@ static inline void zone_statistics(struct zone > *preferred_zone, struct zone *z) > #ifdef CONFIG_NUMA > enum numa_stat_item local_stat = NUMA_LOCAL; > > + /* > + * skip zone_statistics() if vmstat is a

Re: [PATCH 2/3] mm: Handle numa statistics distinctively based-on different VM stats modes

On Fri 15-09-17 17:23:25, Kemi Wang wrote: [...] > @@ -2743,6 +2745,17 @@ static inline void zone_statistics(struct zone > *preferred_zone, struct zone *z) > #ifdef CONFIG_NUMA > enum numa_stat_item local_stat = NUMA_LOCAL; > > + /* > + * skip zone_statistics() if vmstat is a

Re: [PATCH 1/3] mm, sysctl: make VM stats configurable

On Fri 15-09-17 17:23:24, Kemi Wang wrote: > This patch adds a tunable interface that allows VM stats configurable, as > suggested by Dave Hansen and Ying Huang. > > When performance becomes a bottleneck and you can tolerate some possible > tool breakage and some decreased counter precision (e.g.

Re: [PATCH 1/3] mm, sysctl: make VM stats configurable

On Fri 15-09-17 17:23:24, Kemi Wang wrote: > This patch adds a tunable interface that allows VM stats configurable, as > suggested by Dave Hansen and Ying Huang. > > When performance becomes a bottleneck and you can tolerate some possible > tool breakage and some decreased counter precision (e.g.

Re: [PATCH 3/7] kvm,lapic: Justify use of swait_activate()

On 13/09/2017 22:08, Davidlohr Bueso wrote: > A comment might serve future readers. > > Signed-off-by: Davidlohr Bueso > --- > arch/x86/kvm/lapic.c | 4 > 1 file changed, 4 insertions(+) > > diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c > index

Re: [PATCH 3/7] kvm,lapic: Justify use of swait_activate()

On 13/09/2017 22:08, Davidlohr Bueso wrote: > A comment might serve future readers. > > Signed-off-by: Davidlohr Bueso > --- > arch/x86/kvm/lapic.c | 4 > 1 file changed, 4 insertions(+) > > diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c > index aaf10b6f5380..69c5612be786 100644

did you receive the email i send to you?

did you receive the email i send to you?

Re: [PATCH 7/7] kvm,mips: Fix potential swait_active() races

On 14/09/2017 00:22, Davidlohr Bueso wrote: > On Wed, 13 Sep 2017, Paolo Bonzini wrote: >> has_sleeper*s*. Can fix when committing. > > So for regular waitqueues we have it singular, which is why I kept > that name -- albeit sleepers() being better suited, yes. I don't think > we want to rename

Re: [PATCH 7/7] kvm,mips: Fix potential swait_active() races

On 14/09/2017 00:22, Davidlohr Bueso wrote: > On Wed, 13 Sep 2017, Paolo Bonzini wrote: >> has_sleeper*s*. Can fix when committing. > > So for regular waitqueues we have it singular, which is why I kept > that name -- albeit sleepers() being better suited, yes. I don't think > we want to rename

Re: [PATCH v8 00/20] ILP32 for ARM64

Hi all, Linaro has announced the support for ILP32-enabled cross-toolchain: https://lists.linaro.org/pipermail/linaro-toolchain/2017-September/006247.html Files: http://snapshots.linaro.org/components/toolchain/binaries/7.1-2017.08-rc1/aarch64-linux-gnu_ilp32/ Yury On Mon, Jun 19, 2017 at

Re: [PATCH v8 00/20] ILP32 for ARM64

Hi all, Linaro has announced the support for ILP32-enabled cross-toolchain: https://lists.linaro.org/pipermail/linaro-toolchain/2017-September/006247.html Files: http://snapshots.linaro.org/components/toolchain/binaries/7.1-2017.08-rc1/aarch64-linux-gnu_ilp32/ Yury On Mon, Jun 19, 2017 at

Re: [PATCH v2] [DVB][FRONTEND] Added a new ioctl for optimizing frontend property set operation

Em Fri, 15 Sep 2017 06:18:20 -0400 Satendra Singh Thakur escreveu: > Hello Mr Chehab, > Thanks for the comments. > I have modified dtv_property_process_set and > also added documentation. > Please let me know if any further modifications required. That's a way better.

Re: [PATCH v2] [DVB][FRONTEND] Added a new ioctl for optimizing frontend property set operation

Em Fri, 15 Sep 2017 06:18:20 -0400 Satendra Singh Thakur escreveu: > Hello Mr Chehab, > Thanks for the comments. > I have modified dtv_property_process_set and > also added documentation. > Please let me know if any further modifications required. That's a way better. Just a few minor things

Re: [PATCH 1/2] KVM: nVMX: Fix nested #PF intends to break L1's vmlauch/vmresume

On 15/09/2017 13:26, Paolo Bonzini wrote: > On 15/09/2017 05:48, Wanpeng Li wrote: >> 2017-09-14 5:45 GMT+08:00 Paolo Bonzini : >>> On 13/09/2017 13:03, Wanpeng Li wrote: From: Wanpeng Li [ cut here ]

Re: [PATCH 1/2] KVM: nVMX: Fix nested #PF intends to break L1's vmlauch/vmresume

On 15/09/2017 13:26, Paolo Bonzini wrote: > On 15/09/2017 05:48, Wanpeng Li wrote: >> 2017-09-14 5:45 GMT+08:00 Paolo Bonzini : >>> On 13/09/2017 13:03, Wanpeng Li wrote: From: Wanpeng Li [ cut here ] WARNING: CPU: 4 PID: 5280 at

Re: [PATCH 1/2] KVM: nVMX: Fix nested #PF intends to break L1's vmlauch/vmresume

On 15/09/2017 05:48, Wanpeng Li wrote: > 2017-09-14 5:45 GMT+08:00 Paolo Bonzini : >> On 13/09/2017 13:03, Wanpeng Li wrote: >>> From: Wanpeng Li >>> >>> [ cut here ] >>> WARNING: CPU: 4 PID: 5280 at

Re: [PATCH 1/2] KVM: nVMX: Fix nested #PF intends to break L1's vmlauch/vmresume

On 15/09/2017 05:48, Wanpeng Li wrote: > 2017-09-14 5:45 GMT+08:00 Paolo Bonzini : >> On 13/09/2017 13:03, Wanpeng Li wrote: >>> From: Wanpeng Li >>> >>> [ cut here ] >>> WARNING: CPU: 4 PID: 5280 at /home/kernel/linux/arch/x86/kvm//vmx.c:11394 >>>

Re: [GIT PULL] x86/mm changes for v4.14: PCID support, 5-level paging support, Secure Memory Encryption support

On Thu 2017-09-07 10:07:09, Ingo Molnar wrote: > > * Linus Torvalds wrote: > > > On Tue, Sep 5, 2017 at 2:40 PM, Ingo Molnar wrote: > > > > > > Hm, just as background, there are no regression reports I'm aware of > > > against any of these

Re: [GIT PULL] x86/mm changes for v4.14: PCID support, 5-level paging support, Secure Memory Encryption support

On Thu 2017-09-07 10:07:09, Ingo Molnar wrote: > > * Linus Torvalds wrote: > > > On Tue, Sep 5, 2017 at 2:40 PM, Ingo Molnar wrote: > > > > > > Hm, just as background, there are no regression reports I'm aware of > > > against any of these trees, plus most of the dangerous commits have > > >

[PATCH] perf ftrace: Add -O option to set trace option

From: Changbin Du There are some trace options to control what gets printed in the trace output or manipulate the tracers. This patch add a commandline option to set it. Example: perf ftrace -t function -O noprint-parent --trace-funcs "__kmalloc" -a Xorg-1874

[PATCH] perf ftrace: Add -O option to set trace option

From: Changbin Du There are some trace options to control what gets printed in the trace output or manipulate the tracers. This patch add a commandline option to set it. Example: perf ftrace -t function -O noprint-parent --trace-funcs "__kmalloc" -a Xorg-1874 [002]

Re: [PATCH for 4.9 39/59] arm: dts: mt2701: Add subsystem clock controller device nodes

On 09/14/2017 05:51 PM, Levin, Alexander (Sasha Levin) wrote: From: James Liao [ Upstream commit f235c7e7a75325f28a33559a71f25a0eca6112db ] Add MT2701 subsystem clock controllers, inlcude mmsys, imgsys, vdecsys, hifsys, ethsys and bdpsys. Signed-off-by: James

Re: [PATCH for 4.9 39/59] arm: dts: mt2701: Add subsystem clock controller device nodes

On 09/14/2017 05:51 PM, Levin, Alexander (Sasha Levin) wrote: From: James Liao [ Upstream commit f235c7e7a75325f28a33559a71f25a0eca6112db ] Add MT2701 subsystem clock controllers, inlcude mmsys, imgsys, vdecsys, hifsys, ethsys and bdpsys. Signed-off-by: James Liao Signed-off-by: Matthias

<    3   4   5   6   7   8   9   10   11   >