On Tue, 2018-11-06 at 08:49 +0100, Rafael J. Wysocki wrote:
> On Tue, Nov 6, 2018 at 3:42 AM Bo YU wrote:
> > Fix warning form checkpatch, use pr_warn replace KERN_WARNING
> >
> > Signed-off-by: Bo YU
>
> First off, IMO, you should not change the existing code just in order
> to make
On Tue, 2018-11-06 at 08:49 +0100, Rafael J. Wysocki wrote:
> On Tue, Nov 6, 2018 at 3:42 AM Bo YU wrote:
> > Fix warning form checkpatch, use pr_warn replace KERN_WARNING
> >
> > Signed-off-by: Bo YU
>
> First off, IMO, you should not change the existing code just in order
> to make
On Tue, Nov 6, 2018 at 8:41 AM Randy Dunlap wrote:
>
> From: Randy Dunlap
>
> Correct function name and spelling/typo for device_block_probing()
> in drivers/base/dd.c.
>
> Signed-off-by: Randy Dunlap
> Cc: Greg Kroah-Hartman
> Cc: "Rafael J. Wysocki"
Reviewed-by: Rafael J. Wysocki
> ---
>
On Tue, Nov 6, 2018 at 8:41 AM Randy Dunlap wrote:
>
> From: Randy Dunlap
>
> Correct function name and spelling/typo for device_block_probing()
> in drivers/base/dd.c.
>
> Signed-off-by: Randy Dunlap
> Cc: Greg Kroah-Hartman
> Cc: "Rafael J. Wysocki"
Reviewed-by: Rafael J. Wysocki
> ---
>
On Tue, Nov 6, 2018 at 3:42 AM Bo YU wrote:
>
> Fix warning form checkpatch, use pr_warn replace KERN_WARNING
>
> Signed-off-by: Bo YU
First off, IMO, you should not change the existing code just in order
to make checkpatch happy about it. That alone is not a good enough
reason for modifying
On Tue, Nov 6, 2018 at 3:42 AM Bo YU wrote:
>
> Fix warning form checkpatch, use pr_warn replace KERN_WARNING
>
> Signed-off-by: Bo YU
First off, IMO, you should not change the existing code just in order
to make checkpatch happy about it. That alone is not a good enough
reason for modifying
Hi Jongseok,
Den fre 6 juli 2018 kl 07:11 skrev Jongseok Kim :
>
> During the processing of headless pages in z3fold_reclaim_page(),
> there was a problem that the zhdr pointed to another page
> or a page was already released in z3fold_free(). So, the wrong page
> is encoded in headless, or
Hi Jongseok,
Den fre 6 juli 2018 kl 07:11 skrev Jongseok Kim :
>
> During the processing of headless pages in z3fold_reclaim_page(),
> there was a problem that the zhdr pointed to another page
> or a page was already released in z3fold_free(). So, the wrong page
> is encoded in headless, or
Tim,
On Mon, 5 Nov 2018, Tim Chen wrote:
> > Aside of the condition being pointless in that case, that issues an IPI
> > whether the task is running or not. So this allows a task to issue tons of
> > async IPIs disturbing others by toggling the control.
>
> I'm not crazy about sending IPIs too.
Tim,
On Mon, 5 Nov 2018, Tim Chen wrote:
> > Aside of the condition being pointless in that case, that issues an IPI
> > whether the task is running or not. So this allows a task to issue tons of
> > async IPIs disturbing others by toggling the control.
>
> I'm not crazy about sending IPIs too.
Page fault handlers are supposed to return VM_FAULT codes,
but some drivers/file systems mistakenly return error
numbers. Now that all drivers/file systems have been converted
to use the vm_fault_t return type, change the type definition
to no longer be compatible with 'int'. By making it an
Page fault handlers are supposed to return VM_FAULT codes,
but some drivers/file systems mistakenly return error
numbers. Now that all drivers/file systems have been converted
to use the vm_fault_t return type, change the type definition
to no longer be compatible with 'int'. By making it an
There are two intc drivers and two clocksource drivers, also include
related dt-bindings' documentations.
Signed-off-by: Guo Ren
---
MAINTAINERS | 5 +
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index f485597..fb7286a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
There are two intc drivers and two clocksource drivers, also include
related dt-bindings' documentations.
Signed-off-by: Guo Ren
---
MAINTAINERS | 5 +
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index f485597..fb7286a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
Use the gpiod interface instead of the deprecated old non-descriptor
interface in olpc_dcon_xo_1.c.
---
Changes in v3:
- Resolve a few compilation errors.
Changes in v2:
- Resolve a few compilation errors.
- Add a level of indirection to read and write gpios.
Signed-off-by: Nishad Kamdar
---
Use the gpiod interface instead of the deprecated old non-descriptor
interface in olpc_dcon_xo_1.c.
---
Changes in v3:
- Resolve a few compilation errors.
Changes in v2:
- Resolve a few compilation errors.
- Add a level of indirection to read and write gpios.
Signed-off-by: Nishad Kamdar
---
From: Randy Dunlap
Correct function name and spelling/typo for device_block_probing()
in drivers/base/dd.c.
Signed-off-by: Randy Dunlap
Cc: Greg Kroah-Hartman
Cc: "Rafael J. Wysocki"
---
drivers/base/dd.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
---
From: Randy Dunlap
Correct function name and spelling/typo for device_block_probing()
in drivers/base/dd.c.
Signed-off-by: Randy Dunlap
Cc: Greg Kroah-Hartman
Cc: "Rafael J. Wysocki"
---
drivers/base/dd.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
---
Sasha Levin 于2018年11月1日周四 上午12:45写道：
>
> From: Shaohua Li
>
> [ Upstream commit d595567dc4f0c1d90685ec1e2e296e2cad2643ac ]
>
> If we change the number of array's device after device is removed from array,
> then add the device back to array, we can see that device is added as active
> role
Sasha Levin 于2018年11月1日周四 上午12:45写道：
>
> From: Shaohua Li
>
> [ Upstream commit d595567dc4f0c1d90685ec1e2e296e2cad2643ac ]
>
> If we change the number of array's device after device is removed from array,
> then add the device back to array, we can see that device is added as active
> role
Hi, Bartlomiej,
On 一, 2018-11-05 at 17:35 +0100, Bartlomiej Zolnierkiewicz wrote:
> On 11/05/2018 04:04 AM, Zhang Rui wrote:
> >
> > Hi, Bartlomiej,
> Hi Rui,
>
> >
> > Interesting, I'm about to bring this issue to Linux Plumber
> > Conference
> > this year for discussion, and I'm also
Hi, Bartlomiej,
On 一, 2018-11-05 at 17:35 +0100, Bartlomiej Zolnierkiewicz wrote:
> On 11/05/2018 04:04 AM, Zhang Rui wrote:
> >
> > Hi, Bartlomiej,
> Hi Rui,
>
> >
> > Interesting, I'm about to bring this issue to Linux Plumber
> > Conference
> > this year for discussion, and I'm also
Gregory Shapiro 于2018年11月5日周一 下午4:19写道：
>
> Hello, my name is Gregory Shapiro and I am a newbie on this list.
> I recently encountered data corruption as I got a kernel to
> acknowledge write ("io_getevents" system call with a correct number of
> bytes) but undergoing write to disk failed.
>
Gregory Shapiro 于2018年11月5日周一 下午4:19写道：
>
> Hello, my name is Gregory Shapiro and I am a newbie on this list.
> I recently encountered data corruption as I got a kernel to
> acknowledge write ("io_getevents" system call with a correct number of
> bytes) but undergoing write to disk failed.
>
Hi Linus,
On Tue, Nov 06, 2018 at 12:15:02PM +1100, Stephen Rothwell wrote:
> After merging the gpio tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> drivers/gpio/gpiolib.c:1514:12: warning: 'devm_gpio_chip_match' defined but
> not used [-Wunused-function]
>
Hi Linus,
On Tue, Nov 06, 2018 at 12:15:02PM +1100, Stephen Rothwell wrote:
> After merging the gpio tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> drivers/gpio/gpiolib.c:1514:12: warning: 'devm_gpio_chip_match' defined but
> not used [-Wunused-function]
>
From: Zhaoyang Huang
In some cases, the instruction of "bl foo1" will be the last one of the
foo2[1], which will cause the lr be the first instruction of the adjacent
foo3[2]. Hence, the backtrace will show the weird result as bellow[3].
The patch will fix it by miner 4 of the lr when
From: Zhaoyang Huang
In some cases, the instruction of "bl foo1" will be the last one of the
foo2[1], which will cause the lr be the first instruction of the adjacent
foo3[2]. Hence, the backtrace will show the weird result as bellow[3].
The patch will fix it by miner 4 of the lr when
Call nvme_dev_disable() function leads to the power consumption goes
up to 2.2 Watt during suspend-to-idle, and from SK hynix FE, they
suggest us to use its own APST feature to do the power management during
s2idle.
After D3 is diabled and nvme_dev_disable() is not called while
suspending, the
Call nvme_dev_disable() function leads to the power consumption goes
up to 2.2 Watt during suspend-to-idle, and from SK hynix FE, they
suggest us to use its own APST feature to do the power management during
s2idle.
After D3 is diabled and nvme_dev_disable() is not called while
suspending, the
It leads to the power consumption raises to 2.2W during s2idle, while
it consumes less than 1W during long idle if put SK hynix nvme to D3
and then enter s2idle.
>From SK hynix FE, MS Windows doesn't put nvme to D3, and uses its own
APST feature to do the power management.
To leverage its APST
It leads to the power consumption raises to 2.2W during s2idle, while
it consumes less than 1W during long idle if put SK hynix nvme to D3
and then enter s2idle.
>From SK hynix FE, MS Windows doesn't put nvme to D3, and uses its own
APST feature to do the power management.
To leverage its APST
On Tue, Nov 06, 2018 at 10:04:02AM +0800, AceLan Kao wrote:
> Call nvme_dev_disable() function leads to the power consumption goes
> up to 2.2 Watt during suspend-to-idle, and from SK hynix FE, they
> suggest us to use its own APST feature to do the power management during
> s2idle.
> After D3 is
On Tue, Nov 06, 2018 at 10:04:02AM +0800, AceLan Kao wrote:
> Call nvme_dev_disable() function leads to the power consumption goes
> up to 2.2 Watt during suspend-to-idle, and from SK hynix FE, they
> suggest us to use its own APST feature to do the power management during
> s2idle.
> After D3 is
On Tue, Nov 06, 2018 at 10:04:01AM +0800, AceLan Kao wrote:
> It leads to the power consumption raises to 2.2W during s2idle, while
> it consumes less than 1W during long idle if put SK hynix nvme to D3
> and then enter s2idle.
> >From SK hynix FE, MS Windows doesn't put nvme to D3, and uses its
On Tue, Nov 06, 2018 at 10:04:01AM +0800, AceLan Kao wrote:
> It leads to the power consumption raises to 2.2W during s2idle, while
> it consumes less than 1W during long idle if put SK hynix nvme to D3
> and then enter s2idle.
> >From SK hynix FE, MS Windows doesn't put nvme to D3, and uses its
On Mon, Nov 05, 2018 at 02:51:33PM +0100, Arnd Bergmann wrote:
> With the stricter policy you suggest, we'd loose the ability to support
> some extensions that might be common:
>
> - an extension for user space that adds new registers that must be
> saved and restored on a task switch, e.g.
On Mon, Nov 05, 2018 at 02:51:33PM +0100, Arnd Bergmann wrote:
> With the stricter policy you suggest, we'd loose the ability to support
> some extensions that might be common:
>
> - an extension for user space that adds new registers that must be
> saved and restored on a task switch, e.g.
On Mon, Nov 05, 2018 at 09:39:29PM +0200, Nick Kossifidis wrote:
> a) By directly modifying your custom CSRs, it means that we will need
> compiler support in order to compile a kernel with your code in it. This
> will break CI systems and will introduce various issues on testing and
> reviewing
On Mon, Nov 05, 2018 at 09:39:29PM +0200, Nick Kossifidis wrote:
> a) By directly modifying your custom CSRs, it means that we will need
> compiler support in order to compile a kernel with your code in it. This
> will break CI systems and will introduce various issues on testing and
> reviewing
On 05. 11. 18 21:43, Borislav Petkov wrote:
> On Mon, Nov 05, 2018 at 12:38:05PM -0800, Olof Johansson wrote:
>> Yeah, that's the way we've been trying to do for various subsystems
>> and it's been working pretty well. Of course, if there's need to
>> coordinate more closely for something in the
Hi Kishon，
-Original Message-
From: Kishon Vijay Abraham I
Sent: 2018年11月6日 14:07
To: Xiaowei Bao ; bhelg...@google.com; robh...@kernel.org;
mark.rutl...@arm.com; shawn...@kernel.org; Leo Li ;
lorenzo.pieral...@arm.com; a...@arndb.de; gre...@linuxfoundation.org; M.h. Lian
; Mingkai
On 05. 11. 18 21:43, Borislav Petkov wrote:
> On Mon, Nov 05, 2018 at 12:38:05PM -0800, Olof Johansson wrote:
>> Yeah, that's the way we've been trying to do for various subsystems
>> and it's been working pretty well. Of course, if there's need to
>> coordinate more closely for something in the
Hi Kishon，
-Original Message-
From: Kishon Vijay Abraham I
Sent: 2018年11月6日 14:07
To: Xiaowei Bao ; bhelg...@google.com; robh...@kernel.org;
mark.rutl...@arm.com; shawn...@kernel.org; Leo Li ;
lorenzo.pieral...@arm.com; a...@arndb.de; gre...@linuxfoundation.org; M.h. Lian
; Mingkai
From: Owen Chen
1. pcwibits: The integer bits of pcw for plls is extend to 8 bits,
add a variable to indicate this change and
backward-compatible.
2. fmin: The pll freqency lower-bound is vary from 1GMhz to
1.5Ghz, add a variable to indicate platform-dependent.
Signed-off-by: Owen Chen
From: Owen Chen
PLLs with tuner_en bit, such as APLL1, need to disable
tuner_en before apply new frequency settings, or the new frequency
settings (pcw) will not be applied.
The tuner_en bit will be disabled during changing PLL rate
and be restored after new settings applied.
Signed-off-by:
From: Owen Chen
1. pcwibits: The integer bits of pcw for plls is extend to 8 bits,
add a variable to indicate this change and
backward-compatible.
2. fmin: The pll freqency lower-bound is vary from 1GMhz to
1.5Ghz, add a variable to indicate platform-dependent.
Signed-off-by: Owen Chen
From: Owen Chen
PLLs with tuner_en bit, such as APLL1, need to disable
tuner_en before apply new frequency settings, or the new frequency
settings (pcw) will not be applied.
The tuner_en bit will be disabled during changing PLL rate
and be restored after new settings applied.
Signed-off-by:
On some Mediatek platforms, there are critical clocks of
clock gate type.
To register clock gate with flags CLK_IS_CRITICAL,
we need to add the flags field in mtk_gate data and register APIs.
Signed-off-by: Weiyi Lu
---
drivers/clk/mediatek/clk-gate.c | 5 +++--
drivers/clk/mediatek/clk-gate.h
On some Mediatek platforms, there are critical clocks of
clock gate type.
To register clock gate with flags CLK_IS_CRITICAL,
we need to add the flags field in mtk_gate data and register APIs.
Signed-off-by: Weiyi Lu
---
drivers/clk/mediatek/clk-gate.c | 5 +++--
drivers/clk/mediatek/clk-gate.h
From: Owen Chen
On both MT8183 & MT6765, there add "set/clr" register for
each clkmux setting, and one update register to trigger value change.
It is designed to prevent read-modify-write racing issue.
The sw design need to add a new API to handle this hw change with
a new mtk_clk_mux/mtk_mux
Add scpsys driver for MT8183
Signed-off-by: Weiyi Lu
---
drivers/soc/mediatek/mtk-scpsys.c | 226 ++
1 file changed, 226 insertions(+)
diff --git a/drivers/soc/mediatek/mtk-scpsys.c
b/drivers/soc/mediatek/mtk-scpsys.c
index 80be2e05e4e0..57b9f04a69de 100644
---
Add scpsys driver for MT8183
Signed-off-by: Weiyi Lu
---
drivers/soc/mediatek/mtk-scpsys.c | 226 ++
1 file changed, 226 insertions(+)
diff --git a/drivers/soc/mediatek/mtk-scpsys.c
b/drivers/soc/mediatek/mtk-scpsys.c
index 80be2e05e4e0..57b9f04a69de 100644
---
From: Owen Chen
On both MT8183 & MT6765, there add "set/clr" register for
each clkmux setting, and one update register to trigger value change.
It is designed to prevent read-modify-write racing issue.
The sw design need to add a new API to handle this hw change with
a new mtk_clk_mux/mtk_mux
Add MT8183 clock support, include topckgen, apmixedsys,
infracfg, mcucfg and subsystem clocks.
Signed-off-by: Weiyi Lu
---
drivers/clk/mediatek/Kconfig | 75 ++
drivers/clk/mediatek/Makefile | 12 +
drivers/clk/mediatek/clk-mt8183-audio.c| 112 ++
Add MT8183 clock support, include topckgen, apmixedsys,
infracfg, mcucfg and subsystem clocks.
Signed-off-by: Weiyi Lu
---
drivers/clk/mediatek/Kconfig | 75 ++
drivers/clk/mediatek/Makefile | 12 +
drivers/clk/mediatek/clk-mt8183-audio.c| 112 ++
fix incorrect IC name that will affect the MT8183 power dt-bindings
Signed-off-by: Weiyi Lu
---
include/dt-bindings/power/mt8173-power.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/dt-bindings/power/mt8173-power.h
b/include/dt-bindings/power/mt8173-power.h
Add MT8183 clock dt-bindings, include topckgen, apmixedsys,
infracfg, mcucfg and subsystem clocks.
Signed-off-by: Weiyi Lu
Reviewed-by: Rob Herring
---
include/dt-bindings/clock/mt8183-clk.h | 421 +
1 file changed, 421 insertions(+)
create mode 100644
This patch adds the binding documentation for apmixedsys, audiosys,
camsys, imgsys, infracfg, mcucfg, mfgcfg, mmsys, topckgen, vdecsys,
vencsys and ipu for Mediatek MT8183.
Signed-off-by: Weiyi Lu
Reviewed-by: Rob Herring
---
.../arm/mediatek/mediatek,apmixedsys.txt | 1 +
This series is based on v4.20-rc1 and most of changes are
extracted from series below
(clock/scpsys common changes for both MT8183 & MT6765)
https://patchwork.kernel.org/patch/10528495/
(clock support of MT8183)
https://patchwork.kernel.org/patch/10549891/
The whole series is composed of
clock
This series is based on v4.20-rc1 and most of changes are
extracted from series below
(clock/scpsys common changes for both MT8183 & MT6765)
https://patchwork.kernel.org/patch/10528495/
(clock support of MT8183)
https://patchwork.kernel.org/patch/10549891/
The whole series is composed of
clock
From: Owen Chen
Both MT8183 & MT6765 add more bus protect node than previous project,
therefore we add two more register for setup bus protect, which reside
at INFRA_CFG & SMI_COMMON.
With the following change
1. bus protect need not only infracfg but smi_common registers involved
to setup.
fix incorrect IC name that will affect the MT8183 power dt-bindings
Signed-off-by: Weiyi Lu
---
include/dt-bindings/power/mt8173-power.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/dt-bindings/power/mt8173-power.h
b/include/dt-bindings/power/mt8173-power.h
Add MT8183 clock dt-bindings, include topckgen, apmixedsys,
infracfg, mcucfg and subsystem clocks.
Signed-off-by: Weiyi Lu
Reviewed-by: Rob Herring
---
include/dt-bindings/clock/mt8183-clk.h | 421 +
1 file changed, 421 insertions(+)
create mode 100644
This patch adds the binding documentation for apmixedsys, audiosys,
camsys, imgsys, infracfg, mcucfg, mfgcfg, mmsys, topckgen, vdecsys,
vencsys and ipu for Mediatek MT8183.
Signed-off-by: Weiyi Lu
Reviewed-by: Rob Herring
---
.../arm/mediatek/mediatek,apmixedsys.txt | 1 +
This series is based on v4.20-rc1 and most of changes are
extracted from series below
(clock/scpsys common changes for both MT8183 & MT6765)
https://patchwork.kernel.org/patch/10528495/
(clock support of MT8183)
https://patchwork.kernel.org/patch/10549891/
The whole series is composed of
clock
This series is based on v4.20-rc1 and most of changes are
extracted from series below
(clock/scpsys common changes for both MT8183 & MT6765)
https://patchwork.kernel.org/patch/10528495/
(clock support of MT8183)
https://patchwork.kernel.org/patch/10549891/
The whole series is composed of
clock
From: Owen Chen
Both MT8183 & MT6765 add more bus protect node than previous project,
therefore we add two more register for setup bus protect, which reside
at INFRA_CFG & SMI_COMMON.
With the following change
1. bus protect need not only infracfg but smi_common registers involved
to setup.
Add power dt-bindings for MT8183.
Signed-off-by: Weiyi Lu
---
.../bindings/soc/mediatek/scpsys.txt | 14 ++
include/dt-bindings/power/mt8183-power.h | 26 +++
2 files changed, 40 insertions(+)
create mode 100644 include/dt-bindings/power/mt8183-power.h
Add power dt-bindings for MT8183.
Signed-off-by: Weiyi Lu
---
.../bindings/soc/mediatek/scpsys.txt | 14 ++
include/dt-bindings/power/mt8183-power.h | 26 +++
2 files changed, 40 insertions(+)
create mode 100644 include/dt-bindings/power/mt8183-power.h
On Mon, Nov 05, 2018 at 02:05:49PM +, Marcel Ziswiler wrote:
On Fri, 2018-11-02 at 22:02 -0400, Sasha Levin wrote:
On Fri, Nov 02, 2018 at 07:56:57PM +, Sudip Mukherjee wrote:
> Hi Greg,
>
> On Fri, Nov 2, 2018 at 6:53 PM Greg Kroah-Hartman
> wrote:
> >
> > 4.14-stable review patch.
On Mon, Nov 05, 2018 at 02:05:49PM +, Marcel Ziswiler wrote:
On Fri, 2018-11-02 at 22:02 -0400, Sasha Levin wrote:
On Fri, Nov 02, 2018 at 07:56:57PM +, Sudip Mukherjee wrote:
> Hi Greg,
>
> On Fri, Nov 2, 2018 at 6:53 PM Greg Kroah-Hartman
> wrote:
> >
> > 4.14-stable review patch.
On Tue, Nov 06, 2018 at 12:06:32AM +0200, Aaro Koskinen wrote:
> With the below change, the MMC card probe seems to with v4.19. But it
> feels a bit hackish, don't you think... Is there some obvious simple
> fix that I'm missing? Any comments?
Please just use dma_coerce_mask_and_coherent in the
On Tue, Nov 06, 2018 at 12:06:32AM +0200, Aaro Koskinen wrote:
> With the below change, the MMC card probe seems to with v4.19. But it
> feels a bit hackish, don't you think... Is there some obvious simple
> fix that I'm missing? Any comments?
Please just use dma_coerce_mask_and_coherent in the
On Tue, Nov 6, 2018 at 11:51 AM Mike Rapoport wrote:
>
> On Mon, Nov 05, 2018 at 07:23:55PM +0530, Souptick Joarder wrote:
> > On Mon, Nov 5, 2018 at 2:43 PM Mike Rapoport wrote:
> > >
> > > On Mon, Nov 05, 2018 at 11:14:17AM +0530, Souptick Joarder wrote:
> > > > Hi Matthew,
> > > >
> > > > On
On Tue, Nov 6, 2018 at 11:51 AM Mike Rapoport wrote:
>
> On Mon, Nov 05, 2018 at 07:23:55PM +0530, Souptick Joarder wrote:
> > On Mon, Nov 5, 2018 at 2:43 PM Mike Rapoport wrote:
> > >
> > > On Mon, Nov 05, 2018 at 11:14:17AM +0530, Souptick Joarder wrote:
> > > > Hi Matthew,
> > > >
> > > > On
btw I have few related questions:
1) extend_credit_for_blkdel() can return error but its return code is not
checked,
neither here nor in all other places. Could somebody clarify, is it normal?
2) there is similar function free_ext_idx(). After internal failures it calls
btw I have few related questions:
1) extend_credit_for_blkdel() can return error but its return code is not
checked,
neither here nor in all other places. Could somebody clarify, is it normal?
2) there is similar function free_ext_idx(). After internal failures it calls
On Mon, Nov 05, 2018 at 07:23:55PM +0530, Souptick Joarder wrote:
> On Mon, Nov 5, 2018 at 2:43 PM Mike Rapoport wrote:
> >
> > On Mon, Nov 05, 2018 at 11:14:17AM +0530, Souptick Joarder wrote:
> > > Hi Matthew,
> > >
> > > On Sun, Nov 4, 2018 at 2:06 PM Mike Rapoport wrote:
> > > >
> > > > On
On Mon, Nov 05, 2018 at 07:23:55PM +0530, Souptick Joarder wrote:
> On Mon, Nov 5, 2018 at 2:43 PM Mike Rapoport wrote:
> >
> > On Mon, Nov 05, 2018 at 11:14:17AM +0530, Souptick Joarder wrote:
> > > Hi Matthew,
> > >
> > > On Sun, Nov 4, 2018 at 2:06 PM Mike Rapoport wrote:
> > > >
> > > > On
free_ind_block(), free_dind_blocks() and free_tind_blocks() are replaced
by a single recursive function.
Signed-off-by: Vasily Averin
---
fs/ext4/migrate.c | 115 +-
1 file changed, 32 insertions(+), 83 deletions(-)
diff --git a/fs/ext4/migrate.c
free_ind_block(), free_dind_blocks() and free_tind_blocks() are replaced
by a single recursive function.
Signed-off-by: Vasily Averin
---
fs/ext4/migrate.c | 115 +-
1 file changed, 32 insertions(+), 83 deletions(-)
diff --git a/fs/ext4/migrate.c
On Mon, Nov 05, 2018 at 05:36:03PM -0500, Stefan Berger wrote:
> On 11/4/18 8:45 PM, Jarkko Sakkinen wrote:
> > Move tpm_validate_command() to tpm2-space.c and make it part of the
> > tpm2_prepare_space() flow. Make cc resolution as part of the TPM space
> > functionality in order to detach it
When the userspace tries to read the crashstate dump, the read side
implementation in the driver currently ascii85 encodes all the binary
buffers and it does this each time the read system call is called.
A userspace tool like cat typically does a page by page read and the
number of read calls
On Mon, Nov 05, 2018 at 05:36:03PM -0500, Stefan Berger wrote:
> On 11/4/18 8:45 PM, Jarkko Sakkinen wrote:
> > Move tpm_validate_command() to tpm2-space.c and make it part of the
> > tpm2_prepare_space() flow. Make cc resolution as part of the TPM space
> > functionality in order to detach it
When the userspace tries to read the crashstate dump, the read side
implementation in the driver currently ascii85 encodes all the binary
buffers and it does this each time the read system call is called.
A userspace tool like cat typically does a page by page read and the
number of read calls
On Mon, Nov 05, 2018 at 05:26:30PM -0500, Stefan Berger wrote:
> On 11/4/18 8:45 PM, Jarkko Sakkinen wrote:
> > Instead of accessing fields of the command header through offsets to
> > the raw buffer, it is a better idea to use the header struct pointer
> > that is already used elsewhere in the
On Mon, Nov 05, 2018 at 05:26:30PM -0500, Stefan Berger wrote:
> On 11/4/18 8:45 PM, Jarkko Sakkinen wrote:
> > Instead of accessing fields of the command header through offsets to
> > the raw buffer, it is a better idea to use the header struct pointer
> > that is already used elsewhere in the
They not only increase the code footprint, they actually make things
slower rather than faster. Remove them as contemporary hardware doesn't
need any hint.
Suggested-by: Dan Williams
Signed-off-by: Arun KS
---
mm/page_alloc.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff
They not only increase the code footprint, they actually make things
slower rather than faster. Remove them as contemporary hardware doesn't
need any hint.
Suggested-by: Dan Williams
Signed-off-by: Arun KS
---
mm/page_alloc.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff
When free pages are done with higher order, time spend on
coalescing pages by buddy allocator can be reduced. With
section size of 256MB, hot add latency of a single section
shows improvement from 50-60 ms to less than 1 ms, hence
improving the hot add latency by 60%. Modify external
providers of
When free pages are done with higher order, time spend on
coalescing pages by buddy allocator can be reduced. With
section size of 256MB, hot add latency of a single section
shows improvement from 50-60 ms to less than 1 ms, hence
improving the hot add latency by 60%. Modify external
providers of
On Mon, Nov 05, 2018 at 05:20:33PM -0500, Stefan Berger wrote:
> > +out_locality:
> > + if (has_locality)
> > + tpm_relinquish_locality(chip, flags);
>
> Safer to also put has_locality = false here ?
Not really sure why?
/Jarkko
MOVDIR64B moves 64-bytes as direct-store with 64-bytes write atomicity.
Direct store is implemented by using write combining (WC) for writing
data directly into memory without caching the data.
Availability of the MOVDIR64B instruction is indicated by the presence
of the CPUID feature flag
Direct stores instructions MOVDIRI and MOVDIR64B will be available in
Tremont and other future x86 processors,
and need to be exposed to guest VM.
The release document ref below link:
https://software.intel.com/sites/default/files/managed/c5/15/\
On Mon, Nov 05, 2018 at 05:20:33PM -0500, Stefan Berger wrote:
> > +out_locality:
> > + if (has_locality)
> > + tpm_relinquish_locality(chip, flags);
>
> Safer to also put has_locality = false here ?
Not really sure why?
/Jarkko
MOVDIR64B moves 64-bytes as direct-store with 64-bytes write atomicity.
Direct store is implemented by using write combining (WC) for writing
data directly into memory without caching the data.
Availability of the MOVDIR64B instruction is indicated by the presence
of the CPUID feature flag
Direct stores instructions MOVDIRI and MOVDIR64B will be available in
Tremont and other future x86 processors,
and need to be exposed to guest VM.
The release document ref below link:
https://software.intel.com/sites/default/files/managed/c5/15/\
MOVDIRI moves doubleword or quadword from register to memory through
direct store which is implemented by using write combining (WC) for
writing data directly into memory without caching the data.
Availability of the MOVDIRI instruction is indicated by the presence of
the CPUID feature flag
MOVDIRI moves doubleword or quadword from register to memory through
direct store which is implemented by using write combining (WC) for
writing data directly into memory without caching the data.
Availability of the MOVDIRI instruction is indicated by the presence of
the CPUID feature flag
1 - 100 of 1452 matches
Mail list logo
