On Wed, Jun 27, 2018 at 12:51:43PM +0900, Masahiro Yamada wrote:
> Hi Olof,
>
> 2018-06-27 2:42 GMT+09:00 Olof Johansson :
> > Hi,
> >
> > On Mon, Jun 25, 2018 at 11:13:04PM +0900, Masahiro Yamada wrote:
> >> Hi Arnd, Olof,
> >>
> >> Please pull some fixes of ARM UniPhier platform.
> >>
> >>
> >>
From: Chintan Pandya
The following kernel panic was observed on ARM64 platform due to a stale
TLB entry.
1. ioremap with 4K size, a valid pte page table is set.
2. iounmap it, its pte entry is set to 0.
3. ioremap the same address with 2M size, update its pmd entry with
a new value.
4.
On Tue, Jun 26, 2018 at 07:54:06PM +0800, GaoMing wrote:
> for example, 1708 inodes every group,3 block groups, bitmap bytes are
> 1708/8=213.5 when the inode bitmap has some errors, e2fsprogs cannot fix it
>
> Signed-off-by: GaoMing
File systems like this should not exist. Can you please
On Tue, Jun 26, 2018 at 07:54:06PM +0800, GaoMing wrote:
> for example, 1708 inodes every group,3 block groups, bitmap bytes are
> 1708/8=213.5 when the inode bitmap has some errors, e2fsprogs cannot fix it
>
> Signed-off-by: GaoMing
File systems like this should not exist. Can you please
It is just a preparation step. The patch does not change
the existing behavior.
Signed-off-by: Petr Mladek
---
kernel/printk/printk.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index
It is just a preparation step. The patch does not change
the existing behavior.
Signed-off-by: Petr Mladek
---
kernel/printk/printk.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index
The commit 719f6a7040f1bdaf96 ("printk: Use the main logbuf in NMI
when logbuf_lock is available") brought back the possible deadlocks
in printk() and NMI.
This is rework of the proposed fix, see
https://lkml.kernel.org/r/20180606111557.xzs6l3lkvg7lq...@pathway.suse.cz
I realized that we could
It is just a preparation step. The patch does not change
the existing behavior.
Signed-off-by: Petr Mladek
---
kernel/printk/printk.c | 43 ++-
1 file changed, 26 insertions(+), 17 deletions(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
The commit 719f6a7040f1bdaf96 ("printk: Use the main logbuf in NMI
when logbuf_lock is available") brought back the possible deadlocks
in printk() and NMI.
This is rework of the proposed fix, see
https://lkml.kernel.org/r/20180606111557.xzs6l3lkvg7lq...@pathway.suse.cz
I realized that we could
It is just a preparation step. The patch does not change
the existing behavior.
Signed-off-by: Petr Mladek
---
kernel/printk/printk.c | 43 ++-
1 file changed, 26 insertions(+), 17 deletions(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
On Tue, Jun 26, 2018 at 9:33 PM, Jason Gunthorpe wrote:
> On Tue, Jun 26, 2018 at 05:05:40PM +0200, Miguel Ojeda wrote:
>> Hi,
>>
>> On Tue, Jun 26, 2018 at 12:44 AM, Jason Gunthorpe wrote:
>> > The true option causes this indenting for functions:
>> >
>> > static struct something_very_very_long
On Tue, Jun 26, 2018 at 9:33 PM, Jason Gunthorpe wrote:
> On Tue, Jun 26, 2018 at 05:05:40PM +0200, Miguel Ojeda wrote:
>> Hi,
>>
>> On Tue, Jun 26, 2018 at 12:44 AM, Jason Gunthorpe wrote:
>> > The true option causes this indenting for functions:
>> >
>> > static struct something_very_very_long
Hi Paul,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pinctrl/devel]
[also build test ERROR on v4.18-rc2 next-20180627]
[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
Hi Paul,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pinctrl/devel]
[also build test ERROR on v4.18-rc2 next-20180627]
[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
On 2018-06-27 00:15, Sebastian Andrzej Siewior wrote:
On 2018-06-26 14:28:26 [-0700], Isaac J. Manjarres wrote:
Remove CPU ID swapping in stop_two_cpus() so that the
source CPU's stopper thread is added to the wake queue last,
so that the source CPU's stopper thread is woken up last,
ensuring
On 2018-06-27 00:15, Sebastian Andrzej Siewior wrote:
On 2018-06-26 14:28:26 [-0700], Isaac J. Manjarres wrote:
Remove CPU ID swapping in stop_two_cpus() so that the
source CPU's stopper thread is added to the wake queue last,
so that the source CPU's stopper thread is woken up last,
ensuring
Errata i870 is applicable in both EP and RC mode. Therefore rename
function dra7xx_pcie_ep_unaligned_memaccess(), that implements errata
workaround, to dra7xx_pcie_unaligned_memaccess() and call it from a
common place. So, that errata workaround is applied for both modes of
operation.
Errata i870 is applicable in both EP and RC mode. Therefore rename
function dra7xx_pcie_ep_unaligned_memaccess(), that implements errata
workaround, to dra7xx_pcie_unaligned_memaccess() and call it from a
common place. So, that errata workaround is applied for both modes of
operation.
On Wed, Jun 27, 2018 at 4:11 AM Mike Rapoport wrote:
>
> On Mon, Jun 25, 2018 at 10:09:41AM -0600, Rob Herring wrote:
> > On Mon, Jun 25, 2018 at 8:08 AM Michal Hocko wrote:
> > >
> > > Hi,
> > > I am wondering why do we still keep mm/bootmem.c when most architectures
> > > already moved to
On Wed, Jun 27, 2018 at 4:11 AM Mike Rapoport wrote:
>
> On Mon, Jun 25, 2018 at 10:09:41AM -0600, Rob Herring wrote:
> > On Mon, Jun 25, 2018 at 8:08 AM Michal Hocko wrote:
> > >
> > > Hi,
> > > I am wondering why do we still keep mm/bootmem.c when most architectures
> > > already moved to
On 06/25/2018 09:39 PM, Wolfram Sang wrote:
On Wed, Jun 13, 2018 at 02:36:12PM -0500, Eddie James wrote:
This series adds an algorithm for an I2C master physically located on an FSI
slave device. The I2C master has multiple ports, each of which may be connected
to an I2C slave. Access to the
On 06/25/2018 09:39 PM, Wolfram Sang wrote:
On Wed, Jun 13, 2018 at 02:36:12PM -0500, Eddie James wrote:
This series adds an algorithm for an I2C master physically located on an FSI
slave device. The I2C master has multiple ports, each of which may be connected
to an I2C slave. Access to the
On 06/25/2018 09:38 PM, Wolfram Sang wrote:
On Wed, Jun 13, 2018 at 02:36:16PM -0500, Eddie James wrote:
Add abort procedure for failed transfers. Add engine and bus reset
procedures to recover from as many faults as possible.
I think this is a way too aggressive recovery. Your are doing
On 06/25/2018 09:38 PM, Wolfram Sang wrote:
On Wed, Jun 13, 2018 at 02:36:16PM -0500, Eddie James wrote:
Add abort procedure for failed transfers. Add engine and bus reset
procedures to recover from as many faults as possible.
I think this is a way too aggressive recovery. Your are doing
On Wed, Jun 27, 2018 at 09:14:21AM -0400, Pavel Tatashin wrote:
> It does look similar to what Naoya was seeing. Herton, have you tried
> applying:
>
> http://ozlabs.org/~akpm/mmots/broken-out/x86-e820-put-e820_type_ram-regions-into-memblockreserved.patch
Thanks, I'll try it. It'll probably
On Wed, Jun 27, 2018 at 09:14:21AM -0400, Pavel Tatashin wrote:
> It does look similar to what Naoya was seeing. Herton, have you tried
> applying:
>
> http://ozlabs.org/~akpm/mmots/broken-out/x86-e820-put-e820_type_ram-regions-into-memblockreserved.patch
Thanks, I'll try it. It'll probably
On Wed, Jun 27, 2018 at 5:27 AM Mike Rapoport wrote:
>
> Hi,
>
> On Mon, Jun 25, 2018 at 10:09:41AM -0600, Rob Herring wrote:
> > On Mon, Jun 25, 2018 at 8:08 AM Michal Hocko wrote:
> > >
> > > Hi,
> > > I am wondering why do we still keep mm/bootmem.c when most architectures
> > > already moved
On Wed, Jun 27, 2018 at 5:27 AM Mike Rapoport wrote:
>
> Hi,
>
> On Mon, Jun 25, 2018 at 10:09:41AM -0600, Rob Herring wrote:
> > On Mon, Jun 25, 2018 at 8:08 AM Michal Hocko wrote:
> > >
> > > Hi,
> > > I am wondering why do we still keep mm/bootmem.c when most architectures
> > > already moved
Hi Will,
On 2018/6/27 14:28, Will Deacon wrote:
> On Wed, Jun 27, 2018 at 02:22:03PM +0100, Wei Xu wrote:
>> On 2018/6/26 18:47, Will Deacon wrote:
>>> If you look at the __idmap_kpti_put_pgtable_ent_ng asm macro, can you try
>>> replacing:
>>>
>>> dc civac, cur_\()\type\()p
>>>
>>>
Hi Will,
On 2018/6/27 14:28, Will Deacon wrote:
> On Wed, Jun 27, 2018 at 02:22:03PM +0100, Wei Xu wrote:
>> On 2018/6/26 18:47, Will Deacon wrote:
>>> If you look at the __idmap_kpti_put_pgtable_ent_ng asm macro, can you try
>>> replacing:
>>>
>>> dc civac, cur_\()\type\()p
>>>
>>>
On 06/25/2018 09:38 PM, Wolfram Sang wrote:
On Wed, Jun 13, 2018 at 02:36:19PM -0500, Eddie James wrote:
Bus recovery should reset the engine and force clock the bus 9 times
to recover most situations.
Signed-off-by: Eddie James
---
drivers/i2c/busses/i2c-fsi.c | 19 +++
On 06/25/2018 09:38 PM, Wolfram Sang wrote:
On Wed, Jun 13, 2018 at 02:36:19PM -0500, Eddie James wrote:
Bus recovery should reset the engine and force clock the bus 9 times
to recover most situations.
Signed-off-by: Eddie James
---
drivers/i2c/busses/i2c-fsi.c | 19 +++
On Wed, Jun 27, 2018 at 02:22:03PM +0100, Wei Xu wrote:
> On 2018/6/26 18:47, Will Deacon wrote:
> > If you look at the __idmap_kpti_put_pgtable_ent_ng asm macro, can you try
> > replacing:
> >
> > dc civac, cur_\()\type\()p
> >
> > with:
> >
> > dc ivac, cur_\()\type\()p
> >
On Wed, Jun 27, 2018 at 02:22:03PM +0100, Wei Xu wrote:
> On 2018/6/26 18:47, Will Deacon wrote:
> > If you look at the __idmap_kpti_put_pgtable_ent_ng asm macro, can you try
> > replacing:
> >
> > dc civac, cur_\()\type\()p
> >
> > with:
> >
> > dc ivac, cur_\()\type\()p
> >
On Mon 2018-06-25 23:16:04, Tony Lindgren wrote:
> * Pavel Machek [180625 09:52]:
> > Hi!
> >
> > > > > V4.18 is slower than it should be.
> > > > >
> > > > > user@devuan:~$ time cat /dev/urandom | head -c 1000 | bzip2 -9 -
> > > > > | wc -c
> > > > > 10044291
> > > > > 52.73user
On Mon 2018-06-25 23:16:04, Tony Lindgren wrote:
> * Pavel Machek [180625 09:52]:
> > Hi!
> >
> > > > > V4.18 is slower than it should be.
> > > > >
> > > > > user@devuan:~$ time cat /dev/urandom | head -c 1000 | bzip2 -9 -
> > > > > | wc -c
> > > > > 10044291
> > > > > 52.73user
Hi James,
On 2018/6/27 9:39, James Morse wrote:
> Hi Wei,
>
> On 26/06/18 18:47, Will Deacon wrote:
>> On Wed, Jun 27, 2018 at 01:16:44AM +0800, Wei Xu wrote:
>>> [0.00] Booting Linux on physical CPU 0x00 [0x480fd010]
>>> [0.00] Linux version
Hi James,
On 2018/6/27 9:39, James Morse wrote:
> Hi Wei,
>
> On 26/06/18 18:47, Will Deacon wrote:
>> On Wed, Jun 27, 2018 at 01:16:44AM +0800, Wei Xu wrote:
>>> [0.00] Booting Linux on physical CPU 0x00 [0x480fd010]
>>> [0.00] Linux version
Hi Will,
On 2018/6/26 18:47, Will Deacon wrote:
> Hi Wei,
>
> On Wed, Jun 27, 2018 at 01:16:44AM +0800, Wei Xu wrote:
>> Today I tried the kernel 4.18-rc2(defconfig, no change on top) with qemu
>> 2.12.0.
>> The guest sometimes still failed to boot. But the crash reason is different.
>> Could
Hi Will,
On 2018/6/26 18:47, Will Deacon wrote:
> Hi Wei,
>
> On Wed, Jun 27, 2018 at 01:16:44AM +0800, Wei Xu wrote:
>> Today I tried the kernel 4.18-rc2(defconfig, no change on top) with qemu
>> 2.12.0.
>> The guest sometimes still failed to boot. But the crash reason is different.
>> Could
On 06/25/2018 09:38 PM, Wolfram Sang wrote:
On Wed, Jun 13, 2018 at 02:36:17PM -0500, Eddie James wrote:
Execute I2C transfers from the FSI-attached I2C master. Use polling
instead of interrupts as we have no hardware IRQ over FSI.
Signed-off-by: Eddie James
---
On 06/25/2018 09:38 PM, Wolfram Sang wrote:
On Wed, Jun 13, 2018 at 02:36:17PM -0500, Eddie James wrote:
Execute I2C transfers from the FSI-attached I2C master. Use polling
instead of interrupts as we have no hardware IRQ over FSI.
Signed-off-by: Eddie James
---
Commit-ID: d79d0d8ad0cb3d782b41631dfeac8eb05e414bcd
Gitweb: https://git.kernel.org/tip/d79d0d8ad0cb3d782b41631dfeac8eb05e414bcd
Author: Dmitry Vyukov
AuthorDate: Wed, 27 Jun 2018 11:07:15 +0200
Committer: Ingo Molnar
CommitDate: Wed, 27 Jun 2018 14:08:11 +0200
x86/mm: Clean up the
Commit-ID: d79d0d8ad0cb3d782b41631dfeac8eb05e414bcd
Gitweb: https://git.kernel.org/tip/d79d0d8ad0cb3d782b41631dfeac8eb05e414bcd
Author: Dmitry Vyukov
AuthorDate: Wed, 27 Jun 2018 11:07:15 +0200
Committer: Ingo Molnar
CommitDate: Wed, 27 Jun 2018 14:08:11 +0200
x86/mm: Clean up the
Am Mittwoch, 27. Juni 2018, 15:12:48 CEST schrieb Michal Hocko:
> On Wed 27-06-18 13:29:05, Richard Weinberger wrote:
> > On Wed, Jun 27, 2018 at 11:34 AM, Jefferson Carpenter
> > wrote:
> > > Is there a way for a user process to mark memory as 'sensitive' or
> > > 'non-sensitive' when it is
Am Mittwoch, 27. Juni 2018, 15:12:48 CEST schrieb Michal Hocko:
> On Wed 27-06-18 13:29:05, Richard Weinberger wrote:
> > On Wed, Jun 27, 2018 at 11:34 AM, Jefferson Carpenter
> > wrote:
> > > Is there a way for a user process to mark memory as 'sensitive' or
> > > 'non-sensitive' when it is
Just minor typo fix. Fixed in preparation of new driver.
Signed-off: Piotr Bugalski
---
drivers/mtd/spi-nor/atmel-quadspi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/mtd/spi-nor/atmel-quadspi.c
b/drivers/mtd/spi-nor/atmel-quadspi.c
index
Just minor typo fix. Fixed in preparation of new driver.
Signed-off: Piotr Bugalski
---
drivers/mtd/spi-nor/atmel-quadspi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/mtd/spi-nor/atmel-quadspi.c
b/drivers/mtd/spi-nor/atmel-quadspi.c
index
Previously added spi-mem interface is now used instead of older approach.
Suggested-by: Boris Brezillon
Signed-off-by: Piotr Bugalski
---
drivers/mtd/spi-nor/atmel-quadspi.c | 91 -
1 file changed, 18 insertions(+), 73 deletions(-)
diff --git
Previously added spi-mem interface is now used instead of older approach.
Suggested-by: Boris Brezillon
Signed-off-by: Piotr Bugalski
---
drivers/mtd/spi-nor/atmel-quadspi.c | 91 -
1 file changed, 18 insertions(+), 73 deletions(-)
diff --git
Atmel SAMA5D2 QuadSPI driver was moved from mtd to spi subsystem,
this change is just moving DT-binding documentation.
Suggested-by: Boris Brezillon
Signed-off-by: Piotr Bugalski
---
Documentation/devicetree/bindings/{mtd => spi}/atmel-quadspi.txt | 0
1 file changed, 0 insertions(+), 0
This patch adds new interface to existing driver. New code is not used yet,
it will be enabled later.
Changes are prepared in small steps to keep patches readable.
Suggested-by: Boris Brezillon
Signed-off-by: Piotr Bugalski
---
drivers/mtd/spi-nor/atmel-quadspi.c | 205
Atmel SAMA5D2 QuadSPI driver was moved from mtd to spi subsystem,
this change is just moving DT-binding documentation.
Suggested-by: Boris Brezillon
Signed-off-by: Piotr Bugalski
---
Documentation/devicetree/bindings/{mtd => spi}/atmel-quadspi.txt | 0
1 file changed, 0 insertions(+), 0
This patch adds new interface to existing driver. New code is not used yet,
it will be enabled later.
Changes are prepared in small steps to keep patches readable.
Suggested-by: Boris Brezillon
Signed-off-by: Piotr Bugalski
---
drivers/mtd/spi-nor/atmel-quadspi.c | 205
Code used for previous interface is no longer needed.
This change just removes obsolete code.
Suggested-by: Boris Brezillon
Signed-off-by: Piotr Bugalski
---
drivers/mtd/spi-nor/atmel-quadspi.c | 389
1 file changed, 389 deletions(-)
diff --git
Kernel contains QSPI driver strongly tied to MTD and nor-flash memory.
New spi-mem interface allows usage also other memory types, especially
much larger NAND with SPI interface. This driver works as SPI controller
and is not related to MTD, however can work with NAND-flash or other
peripherals
Code used for previous interface is no longer needed.
This change just removes obsolete code.
Suggested-by: Boris Brezillon
Signed-off-by: Piotr Bugalski
---
drivers/mtd/spi-nor/atmel-quadspi.c | 389
1 file changed, 389 deletions(-)
diff --git
Kernel contains QSPI driver strongly tied to MTD and nor-flash memory.
New spi-mem interface allows usage also other memory types, especially
much larger NAND with SPI interface. This driver works as SPI controller
and is not related to MTD, however can work with NAND-flash or other
peripherals
Hello,
Atmel SAMA5D2 is equipped with two QSPI interfaces. These interfaces can
work as in SPI-compatible mode or use two / four lines to improve
communication speed. At the moment there is QSPI driver strongly tied to
NOR-flash memory and MTD subsystem.
Intention of this change is to provide new
Hello,
Atmel SAMA5D2 is equipped with two QSPI interfaces. These interfaces can
work as in SPI-compatible mode or use two / four lines to improve
communication speed. At the moment there is QSPI driver strongly tied to
NOR-flash memory and MTD subsystem.
Intention of this change is to provide new
It does look similar to what Naoya was seeing. Herton, have you tried applying:
http://ozlabs.org/~akpm/mmots/broken-out/x86-e820-put-e820_type_ram-regions-into-memblockreserved.patch
Thank you,
Pavel
On Wed, Jun 27, 2018 at 3:35 AM Michal Hocko wrote:
>
> This smells like an issue Naoya was
It does look similar to what Naoya was seeing. Herton, have you tried applying:
http://ozlabs.org/~akpm/mmots/broken-out/x86-e820-put-e820_type_ram-regions-into-memblockreserved.patch
Thank you,
Pavel
On Wed, Jun 27, 2018 at 3:35 AM Michal Hocko wrote:
>
> This smells like an issue Naoya was
On Wed 27-06-18 13:29:05, Richard Weinberger wrote:
> On Wed, Jun 27, 2018 at 11:34 AM, Jefferson Carpenter
> wrote:
> > Is there a way for a user process to mark memory as 'sensitive' or
> > 'non-sensitive' when it is allocated? That could allow it not to have to be
> > zeroed before being
On Wed 27-06-18 13:29:05, Richard Weinberger wrote:
> On Wed, Jun 27, 2018 at 11:34 AM, Jefferson Carpenter
> wrote:
> > Is there a way for a user process to mark memory as 'sensitive' or
> > 'non-sensitive' when it is allocated? That could allow it not to have to be
> > zeroed before being
On Wednesday 27 June 2018 03:56 PM, Lorenzo Pieralisi wrote:
> On Tue, Jun 26, 2018 at 04:15:01PM -0500, Bjorn Helgaas wrote:
>> On Tue, Jun 26, 2018 at 09:10:07AM +0800, kernel test robot wrote:
>>>
>>> Greetings,
>>>
>>> 0day kernel testing robot got the below dmesg and the first bad commit
On Wed, Jun 27, 2018 at 02:56:00PM +0200, Michael Straube wrote:
> Should I add a thanks line to the commit message:
>
> Thanks to Dan Carpenter, Joe Perches and Andy Shevchenko.
>
> Or would that be considered as too much?
You can write whatever the heck you want... :P No one cares.
On Wed, Jun 27, 2018 at 02:56:00PM +0200, Michael Straube wrote:
> Should I add a thanks line to the commit message:
>
> Thanks to Dan Carpenter, Joe Perches and Andy Shevchenko.
>
> Or would that be considered as too much?
You can write whatever the heck you want... :P No one cares.
On Wednesday 27 June 2018 03:56 PM, Lorenzo Pieralisi wrote:
> On Tue, Jun 26, 2018 at 04:15:01PM -0500, Bjorn Helgaas wrote:
>> On Tue, Jun 26, 2018 at 09:10:07AM +0800, kernel test robot wrote:
>>>
>>> Greetings,
>>>
>>> 0day kernel testing robot got the below dmesg and the first bad commit
2018-06-26 20:59+0800, LiuYang:
> GCC 5.4.0 enables raw strings by default and they have higher priority
> than macros, thus R is interpreted incorrectly.
> Fix it by putting a space between macro R and a string literal.
>
> Signed-off-by: LiuYang
> ---
This got fixed in 2012 by b188c81f2e1a
2018-06-26 20:59+0800, LiuYang:
> GCC 5.4.0 enables raw strings by default and they have higher priority
> than macros, thus R is interpreted incorrectly.
> Fix it by putting a space between macro R and a string literal.
>
> Signed-off-by: LiuYang
> ---
This got fixed in 2012 by b188c81f2e1a
On 27.06.2018 13:05, Tvrtko Ursulin wrote:
>
> On 27/06/18 10:47, Alexey Budankov wrote:
>>
>>
>> On 27.06.2018 12:15, Tvrtko Ursulin wrote:
>>>
>>> On 26/06/18 18:25, Alexey Budankov wrote:
Hi,
On 26.06.2018 18:36, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
>
On 27.06.2018 13:05, Tvrtko Ursulin wrote:
>
> On 27/06/18 10:47, Alexey Budankov wrote:
>>
>>
>> On 27.06.2018 12:15, Tvrtko Ursulin wrote:
>>>
>>> On 26/06/18 18:25, Alexey Budankov wrote:
Hi,
On 26.06.2018 18:36, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
>
Am 27.06.2018 um 10:33 schrieb Dan Carpenter:
On Tue, Jun 26, 2018 at 10:32:09PM +0200, Michael Straube wrote:
On 06/26/18 22:17, Joe Perches wrote:
On Tue, 2018-06-26 at 21:44 +0200, Michael Straube wrote:
On 06/26/18 19:32, Andy Shevchenko wrote:
On Tue, Jun 26, 2018 at 11:14 AM, Michael
Am 27.06.2018 um 10:33 schrieb Dan Carpenter:
On Tue, Jun 26, 2018 at 10:32:09PM +0200, Michael Straube wrote:
On 06/26/18 22:17, Joe Perches wrote:
On Tue, 2018-06-26 at 21:44 +0200, Michael Straube wrote:
On 06/26/18 19:32, Andy Shevchenko wrote:
On Tue, Jun 26, 2018 at 11:14 AM, Michael
Add disk name to tracepoints so we can better distinguish between
individual disks in the trace output and admin commands which
are represented without a disk name.
Signed-off-by: Johannes Thumshirn
---
drivers/nvme/host/core.c | 4 ++--
drivers/nvme/host/trace.h | 39
Add disk name to tracepoints so we can better distinguish between
individual disks in the trace output and admin commands which
are represented without a disk name.
Signed-off-by: Johannes Thumshirn
---
drivers/nvme/host/core.c | 4 ++--
drivers/nvme/host/trace.h | 39
From: Sagi Grimberg
We will need to reference the controller in the setup and completion
time for tracing and future traffic based keep alive support.
Signed-off-by: Sagi Grimberg
---
Changes to v4:
- Move caching from nvme_setup_cmd to .init_request (Keith)
---
drivers/nvme/host/core.c |
Patch one is a preparation patch from Sagi and caches the nvme_ctrl in
the nvme_request. This is not only useful for the tracepoints but for
further development as well.
The second patch adds the controller IDs and if applicable the disk
name to the tracepoints so we can distinguish between the
Patch one is a preparation patch from Sagi and caches the nvme_ctrl in
the nvme_request. This is not only useful for the tracepoints but for
further development as well.
The second patch adds the controller IDs and if applicable the disk
name to the tracepoints so we can distinguish between the
From: Sagi Grimberg
We will need to reference the controller in the setup and completion
time for tracing and future traffic based keep alive support.
Signed-off-by: Sagi Grimberg
---
Changes to v4:
- Move caching from nvme_setup_cmd to .init_request (Keith)
---
drivers/nvme/host/core.c |
On 2018-06-27 08:36:57 [-0400], Steven Rostedt wrote:
> On Wed, Apr 11, 2018 at 09:07:30PM +0200, Sebastian Andrzej Siewior wrote:
> >
> > This already happens:
> > - vmstat_shepherd() does get_online_cpus() and within this block it does
> > queue_delayed_work_on(). So this has to wait until
On 2018-06-27 08:36:57 [-0400], Steven Rostedt wrote:
> On Wed, Apr 11, 2018 at 09:07:30PM +0200, Sebastian Andrzej Siewior wrote:
> >
> > This already happens:
> > - vmstat_shepherd() does get_online_cpus() and within this block it does
> > queue_delayed_work_on(). So this has to wait until
Make workaround for errata i870 applicable in Host mode as
well(previously it was enabled only for EP mode) as per errata
documentation: http://www.ti.com/lit/er/sprz450/sprz450.pdf
Tested on DRA72 EVM
Changes since v1:
Drop IRQ handling rework (will be sent out separately)
v1:
Make workaround for errata i870 applicable in Host mode as
well(previously it was enabled only for EP mode) as per errata
documentation: http://www.ti.com/lit/er/sprz450/sprz450.pdf
Tested on DRA72 EVM
Changes since v1:
Drop IRQ handling rework (will be sent out separately)
v1:
On Wed 27-06-18 13:59:27, Michal Hocko wrote:
> On Wed 27-06-18 13:53:49, Jan Kara wrote:
> > On Wed 27-06-18 13:32:21, Michal Hocko wrote:
> [...]
> > > Appart from that, do we really care about 32b here? Big DIO, IB users
> > > seem to be 64b only AFAIU.
> >
> > IMO it is a bad habit to leave
On Wed 27-06-18 13:59:27, Michal Hocko wrote:
> On Wed 27-06-18 13:53:49, Jan Kara wrote:
> > On Wed 27-06-18 13:32:21, Michal Hocko wrote:
> [...]
> > > Appart from that, do we really care about 32b here? Big DIO, IB users
> > > seem to be 64b only AFAIU.
> >
> > IMO it is a bad habit to leave
Signed-off-by: Axel Lin
---
drivers/regulator/bd71837-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/bd71837-regulator.c
b/drivers/regulator/bd71837-regulator.c
index 6eae4d0432a2..403b45de1262 100644
--- a/drivers/regulator/bd71837-regulator.c
Signed-off-by: Axel Lin
---
drivers/regulator/bd71837-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/bd71837-regulator.c
b/drivers/regulator/bd71837-regulator.c
index 6eae4d0432a2..403b45de1262 100644
--- a/drivers/regulator/bd71837-regulator.c
Signed-off-by: Axel Lin
---
drivers/regulator/bd71837-regulator.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/regulator/bd71837-regulator.c
b/drivers/regulator/bd71837-regulator.c
index 403b45de1262..f57f42ed7160 100644
---
Signed-off-by: Axel Lin
---
drivers/regulator/bd71837-regulator.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/regulator/bd71837-regulator.c
b/drivers/regulator/bd71837-regulator.c
index 403b45de1262..f57f42ed7160 100644
---
On Wed, Apr 11, 2018 at 09:07:30PM +0200, Sebastian Andrzej Siewior wrote:
>
> This already happens:
> - vmstat_shepherd() does get_online_cpus() and within this block it does
> queue_delayed_work_on(). So this has to wait until cpuhotplug
> completed before it can schedule something and then
On Wed, Apr 11, 2018 at 09:07:30PM +0200, Sebastian Andrzej Siewior wrote:
>
> This already happens:
> - vmstat_shepherd() does get_online_cpus() and within this block it does
> queue_delayed_work_on(). So this has to wait until cpuhotplug
> completed before it can schedule something and then
On 6/26/18 11:49 PM, Peter Zijlstra wrote:
> On Tue, Jun 26, 2018 at 08:19:49PM +0800, Xunlei Pang wrote:
>> On 6/22/18 3:15 PM, Xunlei Pang wrote:
>>> We use per-cgroup cpu usage statistics similar to "cgroup rstat",
>>> and encountered a problem that user and sys usages are wrongly
>>> split
On 6/26/18 11:49 PM, Peter Zijlstra wrote:
> On Tue, Jun 26, 2018 at 08:19:49PM +0800, Xunlei Pang wrote:
>> On 6/22/18 3:15 PM, Xunlei Pang wrote:
>>> We use per-cgroup cpu usage statistics similar to "cgroup rstat",
>>> and encountered a problem that user and sys usages are wrongly
>>> split
On Mon, 25 Jun 2018 09:21:02 -0700
Joel Fernandes wrote:
>
> From: "Joel Fernandes (Google)"
> Subject: [PATCH v9.1 7/7] kselftests: Add tests for the preemptoff and irqsoff
> tracers
>
> Here we add unit tests for the preemptoff and irqsoff tracer by using a
> kernel module introduced
On Mon, 25 Jun 2018 09:21:02 -0700
Joel Fernandes wrote:
>
> From: "Joel Fernandes (Google)"
> Subject: [PATCH v9.1 7/7] kselftests: Add tests for the preemptoff and irqsoff
> tracers
>
> Here we add unit tests for the preemptoff and irqsoff tracer by using a
> kernel module introduced
(adding proper linux-c6x-dev list, sorry about the noise)
On Wed, Jun 27, 2018 at 03:09:20PM +0300, Mike Rapoport wrote:
> The c6x is already using memblock and does most of early memory
> reservations with it, so it was only a matter of removing the bootmem
> initialization and handover of the
(adding proper linux-c6x-dev list, sorry about the noise)
On Wed, Jun 27, 2018 at 03:09:20PM +0300, Mike Rapoport wrote:
> The c6x is already using memblock and does most of early memory
> reservations with it, so it was only a matter of removing the bootmem
> initialization and handover of the
On Friday 01 June 2018 01:55 AM, David Lechner wrote:
> This adds nodes for describing the Bluetooth chip and connections on
> LEGO MINDSTORMS EV3 to da850-lego-ev3.dts.
>
> Signed-off-by: David Lechner
Applied for v4.19.
Thanks,
Sekhar
On Friday 01 June 2018 01:55 AM, David Lechner wrote:
> This adds nodes for describing the Bluetooth chip and connections on
> LEGO MINDSTORMS EV3 to da850-lego-ev3.dts.
>
> Signed-off-by: David Lechner
Applied for v4.19.
Thanks,
Sekhar
601 - 700 of 1028 matches
Mail list logo
