On Fri, Aug 03, 2018 at 11:02:34AM +0800, Songjun Wu wrote:
> Support more platform.
>
> Signed-off-by: Songjun Wu
> ---
Your changelog text makes no sense, sorry.
greg k-h
On Fri, Aug 03, 2018 at 11:02:34AM +0800, Songjun Wu wrote:
> Support more platform.
>
> Signed-off-by: Songjun Wu
> ---
Your changelog text makes no sense, sorry.
greg k-h
On Fri, Aug 03, 2018 at 11:02:33AM +0800, Songjun Wu wrote:
> Previous implementation uses platform-dependent API to get the clock.
> Those functions are not available for other SoC which uses the same IP.
> The CCF (Common Clock Framework) have an abstraction based APIs for
> clock. In future,
On Fri, Aug 03, 2018 at 11:02:33AM +0800, Songjun Wu wrote:
> Previous implementation uses platform-dependent API to get the clock.
> Those functions are not available for other SoC which uses the same IP.
> The CCF (Common Clock Framework) have an abstraction based APIs for
> clock. In future,
for the soft_limit reclaim has more directivity than global reclaim, we
have current memcg be skipped to avoid potential page thrashing.
Signed-off-by: Zhaoyang Huang
---
mm/memcontrol.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/mm/memcontrol.c
for the soft_limit reclaim has more directivity than global reclaim, we
have current memcg be skipped to avoid potential page thrashing.
Signed-off-by: Zhaoyang Huang
---
mm/memcontrol.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/mm/memcontrol.c
On (08/03/18 14:23), Sergey Senozhatsky wrote:
>
> Hmm, any chance a WB device can be async on its own? We add a page
> to a new bio and submit it to another async device driver. Then we
> return back to the upper layer (swap), which can free a page before
> the device picks up a request. Can
On (08/03/18 14:23), Sergey Senozhatsky wrote:
>
> Hmm, any chance a WB device can be async on its own? We add a page
> to a new bio and submit it to another async device driver. Then we
> return back to the upper layer (swap), which can free a page before
> the device picks up a request. Can
On Fri, Aug 03, 2018 at 11:02:27AM +0800, Songjun Wu wrote:
> Get serial id from dts.
>
> "#ifdef CONFIG_LANTIQ" preprocessor is used because LTQ_EARLY_ASC
> macro is defined in lantiq_soc.h.
> lantiq_soc.h is in arch path for legacy product support.
>
>
On Fri, Aug 03, 2018 at 11:02:27AM +0800, Songjun Wu wrote:
> Get serial id from dts.
>
> "#ifdef CONFIG_LANTIQ" preprocessor is used because LTQ_EARLY_ASC
> macro is defined in lantiq_soc.h.
> lantiq_soc.h is in arch path for legacy product support.
>
>
On Thu, Aug 02, 2018 at 06:21:39PM -0700, Guenter Roeck wrote:
> On 08/02/2018 12:45 PM, Greg Kroah-Hartman wrote:
> [ ... ]
> >
> > I've pushed out -rc2 releases for all of these with that patch removed.
> >
>
> Boot tests with updated images passed for all three releases.
Wonderful, thanks
On Thu, Aug 02, 2018 at 06:21:39PM -0700, Guenter Roeck wrote:
> On 08/02/2018 12:45 PM, Greg Kroah-Hartman wrote:
> [ ... ]
> >
> > I've pushed out -rc2 releases for all of these with that patch removed.
> >
>
> Boot tests with updated images passed for all three releases.
Wonderful, thanks
On Fri, Aug 03, 2018 at 09:45:21AM +0800, Zhang Ning wrote:
> when firmware is in filesystem, request_firmware will load it,
> and copy it to vmalloc memory, that is page align memory.
>
> but when firmware is builtin, it is 8 bytes or 4 bytes alignment.
>
> make sure builtin firmware is page
On Fri, Aug 03, 2018 at 09:45:21AM +0800, Zhang Ning wrote:
> when firmware is in filesystem, request_firmware will load it,
> and copy it to vmalloc memory, that is page align memory.
>
> but when firmware is builtin, it is 8 bytes or 4 bytes alignment.
>
> make sure builtin firmware is page
On Fri, 27 Jul 2018 21:20:47 +0900
Masami Hiramatsu wrote:
> Add a testcase for max stack tracer, which checks basic
> max stack usage tracing and its filter feature.
>
Hmm, this test sometimes fails. (not always)
Let me check what happens.
Thank you,
> Signed-off-by: Masami Hiramatsu
>
On Fri, 27 Jul 2018 21:20:47 +0900
Masami Hiramatsu wrote:
> Add a testcase for max stack tracer, which checks basic
> max stack usage tracing and its filter feature.
>
Hmm, this test sometimes fails. (not always)
Let me check what happens.
Thank you,
> Signed-off-by: Masami Hiramatsu
>
On (08/03/18 13:51), Minchan Kim wrote:
>
> AFAIK, onging writeback page couldn't freed so it was not writeabck problem.
>
> What I'm tryig to fix is read part.
> If we use swapcache, it shouldn't be a problem either because swapcache
> has a reference count and we should wait PG_lock release
On (08/03/18 13:51), Minchan Kim wrote:
>
> AFAIK, onging writeback page couldn't freed so it was not writeabck problem.
>
> What I'm tryig to fix is read part.
> If we use swapcache, it shouldn't be a problem either because swapcache
> has a reference count and we should wait PG_lock release
On Fri, Aug 03, 2018 at 01:13:02PM +0900, Sergey Senozhatsky wrote:
> Hi Minchan,
>
> On (08/03/18 12:00), Minchan Kim wrote:
> > > "Device is so fast that asynchronous IO would be inefficient."
> > >
> > > Which is not the reason why BDI_CAP_SYNCHRONOUS_IO is used by ZRAM.
> > > Probably, the
On Fri, Aug 03, 2018 at 01:13:02PM +0900, Sergey Senozhatsky wrote:
> Hi Minchan,
>
> On (08/03/18 12:00), Minchan Kim wrote:
> > > "Device is so fast that asynchronous IO would be inefficient."
> > >
> > > Which is not the reason why BDI_CAP_SYNCHRONOUS_IO is used by ZRAM.
> > > Probably, the
Hi Wolfran,
Thanks for the review.
I will update the patch with a small comment section above
len --;
so that there is no confusion.
On 08/01/2018 02:35 AM, Wolfram Sang wrote:
--- a/drivers/i2c/busses/i2c-xlp9xx.c
+++ b/drivers/i2c/busses/i2c-xlp9xx.c
@@ -191,28 +191,30 @@ static void
Hi Wolfran,
Thanks for the review.
I will update the patch with a small comment section above
len --;
so that there is no confusion.
On 08/01/2018 02:35 AM, Wolfram Sang wrote:
--- a/drivers/i2c/busses/i2c-xlp9xx.c
+++ b/drivers/i2c/busses/i2c-xlp9xx.c
@@ -191,28 +191,30 @@ static void
Hi Mark,
After merging the spi tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/spi/spi-mem.c: In function 'spi_mem_probe':
drivers/spi/spi-mem.c:375:13: warning: assignment discards 'const' qualifier
from pointer target type [-Wdiscarded-qualifiers]
Refactored rtl_get_tcb_desc slightly to stay within the 80 character
line limit.
Signed-off-by: Luke Triantafyllidis
---
Changes in v2:
- Fixed the formatting of the comments
- Unwrapped some of the lines that were originally wrapped over multiple
lines to stay within the 80 character
Hi Mark,
After merging the spi tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/spi/spi-mem.c: In function 'spi_mem_probe':
drivers/spi/spi-mem.c:375:13: warning: assignment discards 'const' qualifier
from pointer target type [-Wdiscarded-qualifiers]
Refactored rtl_get_tcb_desc slightly to stay within the 80 character
line limit.
Signed-off-by: Luke Triantafyllidis
---
Changes in v2:
- Fixed the formatting of the comments
- Unwrapped some of the lines that were originally wrapped over multiple
lines to stay within the 80 character
Hi Minchan,
On (08/03/18 12:00), Minchan Kim wrote:
> > "Device is so fast that asynchronous IO would be inefficient."
> >
> > Which is not the reason why BDI_CAP_SYNCHRONOUS_IO is used by ZRAM.
> > Probably, the comment needs to be updated as well.
>
> I couldn't catch your point. Could
Hi Minchan,
On (08/03/18 12:00), Minchan Kim wrote:
> > "Device is so fast that asynchronous IO would be inefficient."
> >
> > Which is not the reason why BDI_CAP_SYNCHRONOUS_IO is used by ZRAM.
> > Probably, the comment needs to be updated as well.
>
> I couldn't catch your point. Could
On Thu, 2 Aug 2018 at 21:04, Paolo Bonzini wrote:
>
> On 23/07/2018 08:39, Wanpeng Li wrote:
> > +Returns 0 if successfully delivery the IPIs and 1 if discarded.
>
> I'm changing this to
>
> "Returns the number of CPUs to which the IPIs were delivered successfully"
>
> with an obvious change to
On Thu, 2 Aug 2018 at 21:04, Paolo Bonzini wrote:
>
> On 23/07/2018 08:39, Wanpeng Li wrote:
> > +Returns 0 if successfully delivery the IPIs and 1 if discarded.
>
> I'm changing this to
>
> "Returns the number of CPUs to which the IPIs were delivered successfully"
>
> with an obvious change to
Hi,
On 08/02/2018 04:15 AM, Michal Hocko wrote:
On Wed 01-08-18 15:04:17, Jeremy Linton wrote:
[...]
@@ -2519,6 +2519,8 @@ static void *___slab_alloc(struct kmem_cache *s, gfp_t
gfpflags, int node,
if (unlikely(!node_match(page, searchnode))) {
stat(s,
Hi,
On 08/02/2018 04:15 AM, Michal Hocko wrote:
On Wed 01-08-18 15:04:17, Jeremy Linton wrote:
[...]
@@ -2519,6 +2519,8 @@ static void *___slab_alloc(struct kmem_cache *s, gfp_t
gfpflags, int node,
if (unlikely(!node_match(page, searchnode))) {
stat(s,
Hi,
On 08/02/2018 02:31 AM, Michal Hocko wrote:
On Wed 01-08-18 15:04:18, Jeremy Linton wrote:
Its possible to crash __alloc_pages_nodemask by passing it
bogus node ids. This is caused by NODE_DATA() returning null
(hopefully) when the requested node is offline. We can
harded against the basic
Hi,
On 08/02/2018 02:31 AM, Michal Hocko wrote:
On Wed 01-08-18 15:04:18, Jeremy Linton wrote:
Its possible to crash __alloc_pages_nodemask by passing it
bogus node ids. This is caused by NODE_DATA() returning null
(hopefully) when the requested node is offline. We can
harded against the basic
Hi,
On 08/01/2018 07:14 PM, Andrew Morton wrote:
On Wed, 1 Aug 2018 17:56:46 -0500 Jeremy Linton wrote:
Hi,
On 08/01/2018 04:50 PM, Andrew Morton wrote:
On Wed, 1 Aug 2018 15:04:16 -0500 Jeremy Linton wrote:
The thread "avoid alloc memory on offline node"
Hi,
On 08/01/2018 07:14 PM, Andrew Morton wrote:
On Wed, 1 Aug 2018 17:56:46 -0500 Jeremy Linton wrote:
Hi,
On 08/01/2018 04:50 PM, Andrew Morton wrote:
On Wed, 1 Aug 2018 15:04:16 -0500 Jeremy Linton wrote:
The thread "avoid alloc memory on offline node"
On Thu, Aug 02, 2018 at 11:40:55AM +0200, Thomas Gleixner wrote:
> On Thu, 2 Aug 2018, Marc Zyngier wrote:
> > On Thu, 02 Aug 2018 07:55:49 +0100,
> > Thomas Gleixner wrote:
> > >
> > > On Thu, 2 Aug 2018, Marc Zyngier wrote:
> > > >
> > > > If we need to distinguish between the two, then we
On Thu, Aug 02, 2018 at 11:40:55AM +0200, Thomas Gleixner wrote:
> On Thu, 2 Aug 2018, Marc Zyngier wrote:
> > On Thu, 02 Aug 2018 07:55:49 +0100,
> > Thomas Gleixner wrote:
> > >
> > > On Thu, 2 Aug 2018, Marc Zyngier wrote:
> > > >
> > > > If we need to distinguish between the two, then we
Hi,
On 08/02/2018 09:23 AM, Christopher Lameter wrote:
On Wed, 1 Aug 2018, Jeremy Linton wrote:
diff --git a/mm/slub.c b/mm/slub.c
index 51258eff4178..e03719bac1e2 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -2519,6 +2519,8 @@ static void *___slab_alloc(struct kmem_cache *s, gfp_t
gfpflags,
Hi,
On 08/02/2018 09:23 AM, Christopher Lameter wrote:
On Wed, 1 Aug 2018, Jeremy Linton wrote:
diff --git a/mm/slub.c b/mm/slub.c
index 51258eff4178..e03719bac1e2 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -2519,6 +2519,8 @@ static void *___slab_alloc(struct kmem_cache *s, gfp_t
gfpflags,
Rename fpiclk to freqclk.
Signed-off-by: Songjun Wu
---
Changes in v2: None
drivers/tty/serial/lantiq.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/tty/serial/lantiq.c b/drivers/tty/serial/lantiq.c
index 2e1b35b1cf4d..28086d52e980 100644
---
Rename fpiclk to freqclk.
Signed-off-by: Songjun Wu
---
Changes in v2: None
drivers/tty/serial/lantiq.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/tty/serial/lantiq.c b/drivers/tty/serial/lantiq.c
index 2e1b35b1cf4d..28086d52e980 100644
---
init_lqasc() is only used internally, change to static declaration.
Signed-off-by: Songjun Wu
---
Changes in v2: None
drivers/tty/serial/lantiq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/serial/lantiq.c b/drivers/tty/serial/lantiq.c
index
Clocks and clock-names are updated in device tree binding.
Signed-off-by: Songjun Wu
---
Changes in v2: None
Documentation/devicetree/bindings/serial/lantiq_asc.txt | 15 +++
1 file changed, 15 insertions(+)
diff --git a/Documentation/devicetree/bindings/serial/lantiq_asc.txt
init_lqasc() is only used internally, change to static declaration.
Signed-off-by: Songjun Wu
---
Changes in v2: None
drivers/tty/serial/lantiq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/serial/lantiq.c b/drivers/tty/serial/lantiq.c
index
Clocks and clock-names are updated in device tree binding.
Signed-off-by: Songjun Wu
---
Changes in v2: None
Documentation/devicetree/bindings/serial/lantiq_asc.txt | 15 +++
1 file changed, 15 insertions(+)
diff --git a/Documentation/devicetree/bindings/serial/lantiq_asc.txt
Previous implementation uses platform-dependent API to get the clock.
Those functions are not available for other SoC which uses the same IP.
The CCF (Common Clock Framework) have an abstraction based APIs for
clock. In future, the platform specific code will be removed when the
legacy soc use CCF
Previous implementation uses a hard-coded register value to check
if the current serial entity is the console entity.
Now the lantiq serial driver uses the aliases for the index of the
serial port.
The lantiq danube serial dts are updated with aliases to support this.
Signed-off-by: Songjun Wu
ltq prefix is platform specific function, asc prefix
is more generic.
Signed-off-by: Songjun Wu
---
Changes in v2: None
drivers/tty/serial/lantiq.c | 33 -
1 file changed, 20 insertions(+), 13 deletions(-)
diff --git a/drivers/tty/serial/lantiq.c
Support more platform.
Signed-off-by: Songjun Wu
---
Changes in v2: None
drivers/tty/serial/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/serial/Kconfig b/drivers/tty/serial/Kconfig
index df8bd0c7b97d..564c71fc24bb 100644
---
Previous implementation uses platform-dependent functions
ltq_w32()/ltq_r32() to access registers. Those functions are not
available for other SoC which uses the same IP.
Change to OS provided readl()/writel() and readb()/writeb(), so
that different SoCs can use the same driver.
Signed-off-by:
Previous implementation uses platform-dependent API to get the clock.
Those functions are not available for other SoC which uses the same IP.
The CCF (Common Clock Framework) have an abstraction based APIs for
clock. In future, the platform specific code will be removed when the
legacy soc use CCF
Previous implementation uses a hard-coded register value to check
if the current serial entity is the console entity.
Now the lantiq serial driver uses the aliases for the index of the
serial port.
The lantiq danube serial dts are updated with aliases to support this.
Signed-off-by: Songjun Wu
ltq prefix is platform specific function, asc prefix
is more generic.
Signed-off-by: Songjun Wu
---
Changes in v2: None
drivers/tty/serial/lantiq.c | 33 -
1 file changed, 20 insertions(+), 13 deletions(-)
diff --git a/drivers/tty/serial/lantiq.c
Support more platform.
Signed-off-by: Songjun Wu
---
Changes in v2: None
drivers/tty/serial/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/serial/Kconfig b/drivers/tty/serial/Kconfig
index df8bd0c7b97d..564c71fc24bb 100644
---
Previous implementation uses platform-dependent functions
ltq_w32()/ltq_r32() to access registers. Those functions are not
available for other SoC which uses the same IP.
Change to OS provided readl()/writel() and readb()/writeb(), so
that different SoCs can use the same driver.
Signed-off-by:
Reorder the head files according to the coding style.
Signed-off-by: Songjun Wu
---
Changes in v2:
- New patch to reorder the head files according to the coding style.
drivers/tty/serial/lantiq.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git
All the upper case in unit-address and hex constants are
changed to lower case according to the Linux conventions.
Signed-off-by: Songjun Wu
---
Changes in v2: None
arch/mips/boot/dts/lantiq/danube.dtsi | 42 -
arch/mips/boot/dts/lantiq/easy50712.dts | 14
The clk driver has introduced new clock APIs that replace
the existing clk_enable and clk_disable.
-clk_enable() APIs is replaced with clk_prepare_enable().
-clk_disable() API is replaced with clk_disable_unprepare().
Signed-off-by: Songjun Wu
---
Changes in v2: None
SWAP_IO_SPACE macro prevents serial driver /drivers/tty/serial/lantiq.c
to use readl/writel to replace ltq_r32/w32 which are SoC or platform
specific APIs.
readl/writel are used for this serial driver to support multiple
platforms and multiple architectures. The legacy lantiq platform(Danube)
Get serial id from dts.
"#ifdef CONFIG_LANTIQ" preprocessor is used because LTQ_EARLY_ASC
macro is defined in lantiq_soc.h.
lantiq_soc.h is in arch path for legacy product support.
arch/mips/include/asm/mach-lantiq/xway/lantiq_soc.h
If "#ifdef preprocessor" is changed to
"if
Reorder the head files according to the coding style.
Signed-off-by: Songjun Wu
---
Changes in v2:
- New patch to reorder the head files according to the coding style.
drivers/tty/serial/lantiq.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git
All the upper case in unit-address and hex constants are
changed to lower case according to the Linux conventions.
Signed-off-by: Songjun Wu
---
Changes in v2: None
arch/mips/boot/dts/lantiq/danube.dtsi | 42 -
arch/mips/boot/dts/lantiq/easy50712.dts | 14
The clk driver has introduced new clock APIs that replace
the existing clk_enable and clk_disable.
-clk_enable() APIs is replaced with clk_prepare_enable().
-clk_disable() API is replaced with clk_disable_unprepare().
Signed-off-by: Songjun Wu
---
Changes in v2: None
SWAP_IO_SPACE macro prevents serial driver /drivers/tty/serial/lantiq.c
to use readl/writel to replace ltq_r32/w32 which are SoC or platform
specific APIs.
readl/writel are used for this serial driver to support multiple
platforms and multiple architectures. The legacy lantiq platform(Danube)
Get serial id from dts.
"#ifdef CONFIG_LANTIQ" preprocessor is used because LTQ_EARLY_ASC
macro is defined in lantiq_soc.h.
lantiq_soc.h is in arch path for legacy product support.
arch/mips/include/asm/mach-lantiq/xway/lantiq_soc.h
If "#ifdef preprocessor" is changed to
"if
From: Hua Ma
This patch adds binding documentation for the
compatible values of the Intel MIPS SoCs.
Signed-off-by: Hua Ma
Signed-off-by: Songjun Wu
---
Changes in v2:
- New patch split from previous patch
- Add the board and chip compatible in dt document
From: Yixin Zhu
This patch adds binding documentation for grx500 clock controller.
Signed-off-by: YiXin Zhu
Signed-off-by: Songjun Wu
---
Changes in v2:
- Rewrite clock driver's dt-binding document according to Rob Herring's
comments.
- Simplify device tree docoment, remove some clock
From: Hua Ma
Add dts files to support Intel MIPS SoCs:
- xrx500.dtsi is the chip dts
- easy350_anywan.dts is the board dts
Signed-off-by: Hua Ma
Signed-off-by: Songjun Wu
---
Changes in v2:
- New patch split from previous patch
- The memory address is changed to @2000
- Update to
From: Hua Ma
This patch adds binding documentation for the
compatible values of the Intel MIPS SoCs.
Signed-off-by: Hua Ma
Signed-off-by: Songjun Wu
---
Changes in v2:
- New patch split from previous patch
- Add the board and chip compatible in dt document
From: Yixin Zhu
This patch adds binding documentation for grx500 clock controller.
Signed-off-by: YiXin Zhu
Signed-off-by: Songjun Wu
---
Changes in v2:
- Rewrite clock driver's dt-binding document according to Rob Herring's
comments.
- Simplify device tree docoment, remove some clock
From: Hua Ma
Add dts files to support Intel MIPS SoCs:
- xrx500.dtsi is the chip dts
- easy350_anywan.dts is the board dts
Signed-off-by: Hua Ma
Signed-off-by: Songjun Wu
---
Changes in v2:
- New patch split from previous patch
- The memory address is changed to @2000
- Update to
This patch series is for adding the support for Intel MIPS
interAptiv SoC GRX500 family. It includes CCF support, serial
driver optimization and DTS modification.
This patch series is applied on top of linux v4.18-rc7.
Basic verification is performed on GRX500 board.
We propose merging this
This patch series is for adding the support for Intel MIPS
interAptiv SoC GRX500 family. It includes CCF support, serial
driver optimization and DTS modification.
This patch series is applied on top of linux v4.18-rc7.
Basic verification is performed on GRX500 board.
We propose merging this
From: Yixin Zhu
This driver provides PLL clock registration as well as various clock
branches, e.g. MUX clock, gate clock, divider clock and so on.
PLLs that provide clock to DDR, CPU and peripherals are shown below:
+-+
|--->| LCPLL3 0|--PCIe clk-->
XO
From: Hua Ma
Add initial support for Intel MIPS interAptiv SoCs made by Intel.
This series will add support for the grx500 family.
The series allows booting a minimal system using a initramfs.
Signed-off-by: Hua Ma
Signed-off-by: Songjun Wu
---
Changes in v2:
- Remove unused _END macros
-
From: Yixin Zhu
This driver provides PLL clock registration as well as various clock
branches, e.g. MUX clock, gate clock, divider clock and so on.
PLLs that provide clock to DDR, CPU and peripherals are shown below:
+-+
|--->| LCPLL3 0|--PCIe clk-->
XO
From: Hua Ma
Add initial support for Intel MIPS interAptiv SoCs made by Intel.
This series will add support for the grx500 family.
The series allows booting a minimal system using a initramfs.
Signed-off-by: Hua Ma
Signed-off-by: Songjun Wu
---
Changes in v2:
- Remove unused _END macros
-
Hi Sergey,
On Fri, Aug 03, 2018 at 11:39:29AM +0900, Sergey Senozhatsky wrote:
> On (08/02/18 14:13), Andrew Morton wrote:
> [..]
> > That changelog is rather hard to follow. Please review my edits:
> >
> > : If zram supports writeback feature, it's no longer a BD_CAP_SYNCHRONOUS_IO
>
Hi Sergey,
On Fri, Aug 03, 2018 at 11:39:29AM +0900, Sergey Senozhatsky wrote:
> On (08/02/18 14:13), Andrew Morton wrote:
> [..]
> > That changelog is rather hard to follow. Please review my edits:
> >
> > : If zram supports writeback feature, it's no longer a BD_CAP_SYNCHRONOUS_IO
>
Hi Masami,
On Thu, Aug 2, 2018 at 7:55 AM, Masami Hiramatsu wrote:
> Hi Joel,
>
> I found this caused several issues when testing ftrace.
>
> #1) ftrace boottest (FTRACE_STARTUP_TEST) fails
This sadly appears to be a real issue. The startup test for
"preemptirqsoff" tracer fails, however it
Hi Masami,
On Thu, Aug 2, 2018 at 7:55 AM, Masami Hiramatsu wrote:
> Hi Joel,
>
> I found this caused several issues when testing ftrace.
>
> #1) ftrace boottest (FTRACE_STARTUP_TEST) fails
This sadly appears to be a real issue. The startup test for
"preemptirqsoff" tracer fails, however it
On Thu, Aug 2, 2018 at 6:00 PM, Stephen Rothwell wrote:
> Hi Kees,
>
> After merging the pstore tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> fs/pstore/platform.o: In function `zbufsize_zstd':
> platform.c:(.text+0x172): undefined reference to `ZSTD_compressBound'
>
On Thu, Aug 2, 2018 at 6:00 PM, Stephen Rothwell wrote:
> Hi Kees,
>
> After merging the pstore tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> fs/pstore/platform.o: In function `zbufsize_zstd':
> platform.c:(.text+0x172): undefined reference to `ZSTD_compressBound'
>
Hi Andrew,
On Thu, Aug 02, 2018 at 02:13:04PM -0700, Andrew Morton wrote:
> On Thu, 2 Aug 2018 14:11:12 +0900 Minchan Kim wrote:
>
> > If zram supports writeback feature, it's no more syncrhonous
> > device beause zram does synchronous IO opeation for
> > incompressible page.
> >
> > Do not
On (08/03/18 11:39), Sergey Senozhatsky wrote:
> [..]
>
> > A reader looking at this would wonder "why the heck are we doing that".
> > Adding a code comment would help them.
>
> The interesting thing here is that include/linux/backing-dev.h
> BDI_CAP_SYNCHRONOUS_IO comment says
>
>
Hi Andrew,
On Thu, Aug 02, 2018 at 02:13:04PM -0700, Andrew Morton wrote:
> On Thu, 2 Aug 2018 14:11:12 +0900 Minchan Kim wrote:
>
> > If zram supports writeback feature, it's no more syncrhonous
> > device beause zram does synchronous IO opeation for
> > incompressible page.
> >
> > Do not
On (08/03/18 11:39), Sergey Senozhatsky wrote:
> [..]
>
> > A reader looking at this would wonder "why the heck are we doing that".
> > Adding a code comment would help them.
>
> The interesting thing here is that include/linux/backing-dev.h
> BDI_CAP_SYNCHRONOUS_IO comment says
>
>
On (08/02/18 14:13), Andrew Morton wrote:
[..]
> That changelog is rather hard to follow. Please review my edits:
>
> : If zram supports writeback feature, it's no longer a BD_CAP_SYNCHRONOUS_IO
^BDI_CAP_SYNCHRONOUS_IO
[..]
> A reader
On (08/02/18 14:13), Andrew Morton wrote:
[..]
> That changelog is rather hard to follow. Please review my edits:
>
> : If zram supports writeback feature, it's no longer a BD_CAP_SYNCHRONOUS_IO
^BDI_CAP_SYNCHRONOUS_IO
[..]
> A reader
Since we switched to using SRCU for tracepoints used in the idle path,
we can no longer use rcu_dereference_sched for dereferencing points in
trace-event hooks.
Since tracepoints can now use either SRCU or sched-RCU, just use
rcu_dereference_raw for traceevents just like we're doing when
Since we switched to using SRCU for tracepoints used in the idle path,
we can no longer use rcu_dereference_sched for dereferencing points in
trace-event hooks.
Since tracepoints can now use either SRCU or sched-RCU, just use
rcu_dereference_raw for traceevents just like we're doing when
ssion support")
I have used the pstore tree from next-20180802 for today.
--
Cheers,
Stephen Rothwell
pgpqkh2PNeXBK.pgp
Description: OpenPGP digital signature
ssion support")
I have used the pstore tree from next-20180802 for today.
--
Cheers,
Stephen Rothwell
pgpqkh2PNeXBK.pgp
Description: OpenPGP digital signature
On Fri, Aug 03, 2018 at 10:00:48AM +0800, Dou Liyang wrote:
>
>
>At 07/23/2018 05:29 PM, Chao Fan wrote:
>> Imitate the ACPI code to parse ACPI tables. Functions are simplified
>> cause some operations are not needed here.
>> And also, this method won't influence the initialization of ACPI.
>>
>>
On Fri, Aug 03, 2018 at 10:00:48AM +0800, Dou Liyang wrote:
>
>
>At 07/23/2018 05:29 PM, Chao Fan wrote:
>> Imitate the ACPI code to parse ACPI tables. Functions are simplified
>> cause some operations are not needed here.
>> And also, this method won't influence the initialization of ACPI.
>>
>>
Dominique Martinet wrote on Fri, Aug 03, 2018:
> (the code is currently not safe if it returns an error, I'm sending
> another mail about it right after this one as we already have a partial
> fix)
I take that one back, ksys_mount() does check for error properly so just
the null checks we have in
Dominique Martinet wrote on Fri, Aug 03, 2018:
> (the code is currently not safe if it returns an error, I'm sending
> another mail about it right after this one as we already have a partial
> fix)
I take that one back, ksys_mount() does check for error properly so just
the null checks we have in
piaojun wrote on Fri, Aug 03, 2018:
> We'd better reach an agreement about the patch fix.
The way I read Greg's comment was that he agreed to the proposed changes
and is waiting for a new version.
I'm writing a longer reply than I should because I don't like people
saying strncmp is safe just
piaojun wrote on Fri, Aug 03, 2018:
> We'd better reach an agreement about the patch fix.
The way I read Greg's comment was that he agreed to the proposed changes
and is waiting for a new version.
I'm writing a longer reply than I should because I don't like people
saying strncmp is safe just
1 - 100 of 1362 matches
Mail list logo
