This fix rounds the clock rate properly by using quotient and not
remainder in the calculation. This issue was found while testing HDMI
in the Juno platform.
Fixes: 6d6a1d82eaef7 ("clk: add support for clocks provided by SCMI")
Acked-by: Sudeep Holla
Signed-off-by: Amit Daniel Kachhap
---
This fix rounds the clock rate properly by using quotient and not
remainder in the calculation. This issue was found while testing HDMI
in the Juno platform.
Fixes: 6d6a1d82eaef7 ("clk: add support for clocks provided by SCMI")
Acked-by: Sudeep Holla
Signed-off-by: Amit Daniel Kachhap
---
On Tue, 31 Jul 2018 11:29:24 +0800
Jisheng Zhang wrote:
> Hi Robin,
>
> On Mon, 30 Jul 2018 12:06:08 +0100 Robin Murphy wrote:
>
> > Hi Jisheng,
> >
> > On 26/07/18 08:14, Jisheng Zhang wrote:
> > > When using DMA, if the DMA addr spans 128MB boundary, we have to split
> > > the DMA
On Tue, 31 Jul 2018 11:29:24 +0800
Jisheng Zhang wrote:
> Hi Robin,
>
> On Mon, 30 Jul 2018 12:06:08 +0100 Robin Murphy wrote:
>
> > Hi Jisheng,
> >
> > On 26/07/18 08:14, Jisheng Zhang wrote:
> > > When using DMA, if the DMA addr spans 128MB boundary, we have to split
> > > the DMA
Byungchul Park writes:
> On Tue, Jul 31, 2018 at 09:37:50AM +0800, Huang, Ying wrote:
>> Byungchul Park writes:
>>
>> > Hello folks,
>> >
>> > I'm careful in saying.. and curious about..
>> >
>> > In restrictive cases like only addtions happen but never deletion, can't
>> > we safely traverse
Byungchul Park writes:
> On Tue, Jul 31, 2018 at 09:37:50AM +0800, Huang, Ying wrote:
>> Byungchul Park writes:
>>
>> > Hello folks,
>> >
>> > I'm careful in saying.. and curious about..
>> >
>> > In restrictive cases like only addtions happen but never deletion, can't
>> > we safely traverse
Hi all,
Today's linux-next merge of the pinctrl tree got a conflict in:
Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.txt
between commit:
791d3ef2e111 ("dt-bindings: remove 'interrupt-parent' from bindings")
from the devicetree tree and commit:
de1d08b22974 ("dt-bindings:
Hi all,
Today's linux-next merge of the pinctrl tree got a conflict in:
Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.txt
between commit:
791d3ef2e111 ("dt-bindings: remove 'interrupt-parent' from bindings")
from the devicetree tree and commit:
de1d08b22974 ("dt-bindings:
From: Ben Ho
Add basic chip support for Mediatek 8183
Signed-off-by: Ben Ho
Signed-off-by: Erin Lo
---
arch/arm64/boot/dts/mediatek/Makefile | 1 +
arch/arm64/boot/dts/mediatek/mt8183-evb.dts | 23 +
arch/arm64/boot/dts/mediatek/mt8183.dtsi| 146
From: Ben Ho
Add basic chip support for Mediatek 8183
Signed-off-by: Ben Ho
Signed-off-by: Erin Lo
---
arch/arm64/boot/dts/mediatek/Makefile | 1 +
arch/arm64/boot/dts/mediatek/mt8183-evb.dts | 23 +
arch/arm64/boot/dts/mediatek/mt8183.dtsi| 146
This adds dt-binding documentation of uart for Mediatek MT8183 SoC
Platform.
Signed-off-by: Erin Lo
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/serial/mtk-uart.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/serial/mtk-uart.txt
From: Weiyi Lu
Add MT8183 clock dt-bindings, include topckgen, apmixedsys,
infracfg and subsystem clocks.
Signed-off-by: Weiyi Lu
Signed-off-by: Erin Lo
---
include/dt-bindings/clock/mt8183-clk.h | 413 +
1 file changed, 413 insertions(+)
create mode 100644
From: Weiyi Lu
Add clock controller nodes for MT8183, include topckgen, infracfg,
apmixedsys and subsystem.
Signed-off-by: Weiyi Lu
Signed-off-by: Erin Lo
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 92
1 file changed, 92 insertions(+)
diff --git
From: Weiyi Lu
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
Signed-off-by: Erin Lo
---
drivers/clk/mediatek/clk-gate.c |
This adds dt-binding documentation of uart for Mediatek MT8183 SoC
Platform.
Signed-off-by: Erin Lo
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/serial/mtk-uart.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/serial/mtk-uart.txt
From: Weiyi Lu
Add MT8183 clock dt-bindings, include topckgen, apmixedsys,
infracfg and subsystem clocks.
Signed-off-by: Weiyi Lu
Signed-off-by: Erin Lo
---
include/dt-bindings/clock/mt8183-clk.h | 413 +
1 file changed, 413 insertions(+)
create mode 100644
From: Weiyi Lu
Add clock controller nodes for MT8183, include topckgen, infracfg,
apmixedsys and subsystem.
Signed-off-by: Weiyi Lu
Signed-off-by: Erin Lo
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 92
1 file changed, 92 insertions(+)
diff --git
From: Weiyi Lu
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
Signed-off-by: Erin Lo
---
drivers/clk/mediatek/clk-gate.c |
This adds dt-binding documentation of SYSIRQ for Mediatek MT8183 SoC
Platform.
Signed-off-by: Erin Lo
Acked-by: Rob Herring
---
.../devicetree/bindings/interrupt-controller/mediatek,sysirq.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Weiyi Lu
Add MT8183 clock support, include topckgen, apmixedsys,
infracfg and subsystem clocks.
Signed-off-by: Weiyi Lu
Signed-off-by: Erin Lo
---
drivers/clk/mediatek/Kconfig | 74 ++
drivers/clk/mediatek/Makefile | 12 +
From: Weiyi Lu
Add uart node with correct uart clocks.
Signed-off-by: Erin Lo
Signed-off-by: Weiyi Lu
---
arch/arm64/boot/dts/mediatek/mt8183-evb.dts | 8
arch/arm64/boot/dts/mediatek/mt8183.dtsi| 30 +
2 files changed, 38 insertions(+)
diff --git
MT8183 is a SoC based on 64bit ARMv8 architecture.
It contains 4 CA53 and 4 CA73 cores.
MT8183 share many HW IP with MT65xx series.
This patchset was tested on MT8183 evaluation board and use correct clock to
shell.
This series contains document bindings, device tree including interrupt, uart,
From: Weiyi Lu
This patch adds the binding documentation for apmixedsys, audiosys,
camsys, imgsys, infracfg, mfgcfg, mmsys, topckgen, vdecsys, vencsys
and ipu for Mediatek MT8183.
Signed-off-by: Weiyi Lu
Signed-off-by: Erin Lo
---
.../bindings/arm/mediatek/mediatek,apmixedsys.txt | 1 +
This adds dt-binding documentation of cpu for Mediatek MT8183.
Signed-off-by: Erin Lo
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/arm/mediatek.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/mediatek.txt
From: Weiyi Lu
This patch adds the binding documentation for apmixedsys, audiosys,
camsys, imgsys, infracfg, mfgcfg, mmsys, topckgen, vdecsys, vencsys
and ipu for Mediatek MT8183.
Signed-off-by: Weiyi Lu
Signed-off-by: Erin Lo
---
.../bindings/arm/mediatek/mediatek,apmixedsys.txt | 1 +
This adds dt-binding documentation of SYSIRQ for Mediatek MT8183 SoC
Platform.
Signed-off-by: Erin Lo
Acked-by: Rob Herring
---
.../devicetree/bindings/interrupt-controller/mediatek,sysirq.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Weiyi Lu
Add MT8183 clock support, include topckgen, apmixedsys,
infracfg and subsystem clocks.
Signed-off-by: Weiyi Lu
Signed-off-by: Erin Lo
---
drivers/clk/mediatek/Kconfig | 74 ++
drivers/clk/mediatek/Makefile | 12 +
From: Weiyi Lu
Add uart node with correct uart clocks.
Signed-off-by: Erin Lo
Signed-off-by: Weiyi Lu
---
arch/arm64/boot/dts/mediatek/mt8183-evb.dts | 8
arch/arm64/boot/dts/mediatek/mt8183.dtsi| 30 +
2 files changed, 38 insertions(+)
diff --git
MT8183 is a SoC based on 64bit ARMv8 architecture.
It contains 4 CA53 and 4 CA73 cores.
MT8183 share many HW IP with MT65xx series.
This patchset was tested on MT8183 evaluation board and use correct clock to
shell.
This series contains document bindings, device tree including interrupt, uart,
This adds dt-binding documentation of cpu for Mediatek MT8183.
Signed-off-by: Erin Lo
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/arm/mediatek.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/mediatek.txt
Dear Friend,
Good day, this is Mr. Henri Zongo, I'm happy to inform you about my success in
getting the fund $29.6Million transferred under the co-operation of a new
partner from Dubai, Presently I'm in Dubai for investment projects with my own
share of the total sum. Meanwhile,I didn't
Dear Friend,
Good day, this is Mr. Henri Zongo, I'm happy to inform you about my success in
getting the fund $29.6Million transferred under the co-operation of a new
partner from Dubai, Presently I'm in Dubai for investment projects with my own
share of the total sum. Meanwhile,I didn't
On Tue, 31 Jul 2018 03:25:06 +0200,
Agrawal, Akshu wrote:
>
>
>
> On 7/30/2018 9:20 PM, Mark Brown wrote:
> > On Mon, Jul 30, 2018 at 05:32:21PM +0200, Takashi Iwai wrote:
> >
> >> That said, if delay callback of CPU dai provides the additional delay,
> >> the patch does correct thing. OTOH,
On Tue, 31 Jul 2018 03:25:06 +0200,
Agrawal, Akshu wrote:
>
>
>
> On 7/30/2018 9:20 PM, Mark Brown wrote:
> > On Mon, Jul 30, 2018 at 05:32:21PM +0200, Takashi Iwai wrote:
> >
> >> That said, if delay callback of CPU dai provides the additional delay,
> >> the patch does correct thing. OTOH,
On Tue, Jul 31, 2018 at 09:37:50AM +0800, Huang, Ying wrote:
> Byungchul Park writes:
>
> > Hello folks,
> >
> > I'm careful in saying.. and curious about..
> >
> > In restrictive cases like only addtions happen but never deletion, can't
> > we safely traverse a llist? I believe llist can be
On Tue, Jul 31, 2018 at 09:37:50AM +0800, Huang, Ying wrote:
> Byungchul Park writes:
>
> > Hello folks,
> >
> > I'm careful in saying.. and curious about..
> >
> > In restrictive cases like only addtions happen but never deletion, can't
> > we safely traverse a llist? I believe llist can be
On Mon, Jul 30, 2018 at 5:10 PM, Sudeep Holla wrote:
> On Mon, Jul 30, 2018 at 11:03:51AM +0530, Amit Daniel Kachhap wrote:
>> Hi,
>>
>> On Fri, Jul 27, 2018 at 10:07 PM, Stephen Boyd wrote:
>> > Quoting Amit Daniel Kachhap (2018-07-27 07:01:52)
>> >> This fix rounds the clock rate properly by
On Mon, Jul 30, 2018 at 5:10 PM, Sudeep Holla wrote:
> On Mon, Jul 30, 2018 at 11:03:51AM +0530, Amit Daniel Kachhap wrote:
>> Hi,
>>
>> On Fri, Jul 27, 2018 at 10:07 PM, Stephen Boyd wrote:
>> > Quoting Amit Daniel Kachhap (2018-07-27 07:01:52)
>> >> This fix rounds the clock rate properly by
Hi all,
Today's linux-next merge of the mux tree got a conflict in:
MAINTAINERS
between commit:
fe8e81b7e899 ("adp5061: New driver for ADP5061 I2C battery charger")
from the battery tree and commit:
703160ff3e50 ("dt-bindings: mux: add adi,adgs1408")
from the mux tree.
I fixed it up
Hi all,
Today's linux-next merge of the mux tree got a conflict in:
MAINTAINERS
between commit:
fe8e81b7e899 ("adp5061: New driver for ADP5061 I2C battery charger")
from the battery tree and commit:
703160ff3e50 ("dt-bindings: mux: add adi,adgs1408")
from the mux tree.
I fixed it up
Commit-ID: 99811294b063eb44185df9a58923928fccdbe122
Gitweb: https://git.kernel.org/tip/99811294b063eb44185df9a58923928fccdbe122
Author: Kan Liang
AuthorDate: Mon, 30 Jul 2018 08:28:08 -0400
Committer: Ingo Molnar
CommitDate: Mon, 30 Jul 2018 20:13:58 +0200
perf/x86/intel/uncore: Fix
Hi Ming
On 07/31/2018 12:58 PM, Ming Lei wrote:
> On Tue, Jul 31, 2018 at 12:02:15PM +0800, Jianchao Wang wrote:
>> Currently, we will always set SCHED_RESTART whenever there are
>> requests in hctx->dispatch, then when request is completed and
>> freed the hctx queues will be restarted to avoid
Commit-ID: 99811294b063eb44185df9a58923928fccdbe122
Gitweb: https://git.kernel.org/tip/99811294b063eb44185df9a58923928fccdbe122
Author: Kan Liang
AuthorDate: Mon, 30 Jul 2018 08:28:08 -0400
Committer: Ingo Molnar
CommitDate: Mon, 30 Jul 2018 20:13:58 +0200
perf/x86/intel/uncore: Fix
Hi Ming
On 07/31/2018 12:58 PM, Ming Lei wrote:
> On Tue, Jul 31, 2018 at 12:02:15PM +0800, Jianchao Wang wrote:
>> Currently, we will always set SCHED_RESTART whenever there are
>> requests in hctx->dispatch, then when request is completed and
>> freed the hctx queues will be restarted to avoid
On Tue 31-07-18 06:01:48, Tetsuo Handa wrote:
> On 2018/07/31 4:10, Michal Hocko wrote:
> > Since should_reclaim_retry() should be a natural reschedule point,
> > let's do the short sleep for PF_WQ_WORKER threads unconditionally in
> > order to guarantee that other pending work items are started.
On Tue 31-07-18 06:01:48, Tetsuo Handa wrote:
> On 2018/07/31 4:10, Michal Hocko wrote:
> > Since should_reclaim_retry() should be a natural reschedule point,
> > let's do the short sleep for PF_WQ_WORKER threads unconditionally in
> > order to guarantee that other pending work items are started.
On 05-07-18, 10:39, Viresh Kumar wrote:
> Hi,
>
> This is an attempt to fix the broken or partially defined DT bindings
> for cooling-maps. We should list every device that participates in
> cooling down at a certain trip point, instead of just the first in the
> list as that depends on certain
On 05-07-18, 10:39, Viresh Kumar wrote:
> Hi,
>
> This is an attempt to fix the broken or partially defined DT bindings
> for cooling-maps. We should list every device that participates in
> cooling down at a certain trip point, instead of just the first in the
> list as that depends on certain
On Mon 02 Jul 05:08 PDT 2018, Sekhar Nori wrote:
> Hi Bjorn,
>
> On Thursday 21 June 2018 05:11 PM, Bartosz Golaszewski wrote:
> > 2018-06-21 12:52 GMT+02:00 Sekhar Nori :
> >> Hi Bartosz,
> >>
> >> On Thursday 21 June 2018 01:07 PM, Bartosz Golaszewski wrote:
> >>> From: Bartosz Golaszewski
>
On Mon 02 Jul 05:08 PDT 2018, Sekhar Nori wrote:
> Hi Bjorn,
>
> On Thursday 21 June 2018 05:11 PM, Bartosz Golaszewski wrote:
> > 2018-06-21 12:52 GMT+02:00 Sekhar Nori :
> >> Hi Bartosz,
> >>
> >> On Thursday 21 June 2018 01:07 PM, Bartosz Golaszewski wrote:
> >>> From: Bartosz Golaszewski
>
On Tue, Jul 31, 2018 at 09:58:36AM +0900, Byungchul Park wrote:
> Hello folks,
>
> I'm careful in saying.. and curious about..
>
> In restrictive cases like only addtions happen but never deletion, can't
> we safely traverse a llist? I believe llist can be more useful if we can
> release the
On Tue, Jul 31, 2018 at 09:58:36AM +0900, Byungchul Park wrote:
> Hello folks,
>
> I'm careful in saying.. and curious about..
>
> In restrictive cases like only addtions happen but never deletion, can't
> we safely traverse a llist? I believe llist can be more useful if we can
> release the
On 30-07-18, 12:46, Peter Ujfalusi wrote:
> Vinod,
>
> On 2018-07-24 14:14, Vinod wrote:
> Clients must not mix the two way of handling the metadata.
> The set_len() is intended to tell the DMA driver the client provided
> metadata size (in MEM_TO_DEV case mostly).
>
>
Hi John, Thomas,
Can you please review below patch and update your comments:
Regards
Gaurav
On 7/26/2018 2:12 PM, Gaurav Kohli wrote:
While migrating timer to new base, there is a need
to update base clk by calling forward_timer_base to
avoid stale clock , but at the same time if run_timer
is
On 30-07-18, 12:46, Peter Ujfalusi wrote:
> Vinod,
>
> On 2018-07-24 14:14, Vinod wrote:
> Clients must not mix the two way of handling the metadata.
> The set_len() is intended to tell the DMA driver the client provided
> metadata size (in MEM_TO_DEV case mostly).
>
>
Hi John, Thomas,
Can you please review below patch and update your comments:
Regards
Gaurav
On 7/26/2018 2:12 PM, Gaurav Kohli wrote:
While migrating timer to new base, there is a need
to update base clk by calling forward_timer_base to
avoid stale clock , but at the same time if run_timer
is
On Thu 21 Jun 00:37 PDT 2018, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Switch to using the reset framework instead of handcoded reset routines
> we used so far.
>
> Signed-off-by: Bartosz Golaszewski
> Reviewed-by: Sekhar Nori
> Reviewed-by: Philipp Zabel
Acked-by: Bjorn
On Thu 21 Jun 00:37 PDT 2018, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Switch to using the reset framework instead of handcoded reset routines
> we used so far.
>
> Signed-off-by: Bartosz Golaszewski
> Reviewed-by: Sekhar Nori
> Reviewed-by: Philipp Zabel
Acked-by: Bjorn
On Mon, Jul 30, 2018 at 8:26 PM, Hugh Dickins wrote:
> On Mon, 30 Jul 2018, Linus Torvalds wrote:
>> On Mon, Jul 30, 2018 at 2:53 PM Hugh Dickins wrote:
>> >
>> > I have no problem with reverting -rc7's vma_is_anonymous() series.
>>
>> I don't think we need to revert the whole series: I think
On Mon, Jul 30, 2018 at 8:26 PM, Hugh Dickins wrote:
> On Mon, 30 Jul 2018, Linus Torvalds wrote:
>> On Mon, Jul 30, 2018 at 2:53 PM Hugh Dickins wrote:
>> >
>> > I have no problem with reverting -rc7's vma_is_anonymous() series.
>>
>> I don't think we need to revert the whole series: I think
Hi all,
Today's linux-next merge of the kvms390 tree got a conflict in:
include/uapi/linux/kvm.h
between commit:
be26b3a73413 ("arm64: KVM: export the capability to set guest SError
syndrome")
from the kvm-arm tree and commit:
a449938297e5 ("KVM: s390: Add huge page enablement
Hi all,
Today's linux-next merge of the kvms390 tree got a conflict in:
include/uapi/linux/kvm.h
between commit:
be26b3a73413 ("arm64: KVM: export the capability to set guest SError
syndrome")
from the kvm-arm tree and commit:
a449938297e5 ("KVM: s390: Add huge page enablement
On Mon, Jul 30, 2018 at 02:38:01PM -0700, vnkgu...@codeaurora.org wrote:
> Do you mean the Signed-off-by lines above? That's because
> Channagoud is the one who is the original author of this driver,
> and I'm the one who did the incremental changes (changes in llcc)
> and uploading it upstream.
>
On Mon, Jul 30, 2018 at 02:38:01PM -0700, vnkgu...@codeaurora.org wrote:
> Do you mean the Signed-off-by lines above? That's because
> Channagoud is the one who is the original author of this driver,
> and I'm the one who did the incremental changes (changes in llcc)
> and uploading it upstream.
>
On Wed 18 Jul 04:16 PDT 2018, Arnd Bergmann wrote:
> A new driver got added that depends on QCOM_SMD and fails to link
> as built-in with CONFIG_QCOM_SMD=m:
>
> drivers/remoteproc/qcom_common.o: In function `smd_subdev_stop':
> qcom_common.c:(.text+0x674): undefined reference to
On Wed 18 Jul 04:16 PDT 2018, Arnd Bergmann wrote:
> A new driver got added that depends on QCOM_SMD and fails to link
> as built-in with CONFIG_QCOM_SMD=m:
>
> drivers/remoteproc/qcom_common.o: In function `smd_subdev_stop':
> qcom_common.c:(.text+0x674): undefined reference to
Matthew Wilcox wrote on Mon, Jul 30, 2018:
> On Mon, Jul 30, 2018 at 11:34:23AM +0200, Dominique Martinet wrote:
> > -static int p9_fcall_alloc(struct p9_fcall *fc, int alloc_msize)
> > +static int p9_fcall_alloc(struct p9_client *c, struct p9_fcall *fc,
> > + int alloc_msize)
Matthew Wilcox wrote on Mon, Jul 30, 2018:
> On Mon, Jul 30, 2018 at 11:34:23AM +0200, Dominique Martinet wrote:
> > -static int p9_fcall_alloc(struct p9_fcall *fc, int alloc_msize)
> > +static int p9_fcall_alloc(struct p9_client *c, struct p9_fcall *fc,
> > + int alloc_msize)
On Fri, Jul 27, 2018 at 06:35:10PM +0100, David Howells wrote:
> params->request indicates the attribute/attributes to be queried. This can
> be one of:
>
> fsinfo_attr_statfs - statfs-style info
> fsinfo_attr_fsinfo - Information about fsinfo()
>
On Fri, Jul 27, 2018 at 06:35:10PM +0100, David Howells wrote:
> params->request indicates the attribute/attributes to be queried. This can
> be one of:
>
> fsinfo_attr_statfs - statfs-style info
> fsinfo_attr_fsinfo - Information about fsinfo()
>
On Thu 26 Jul 18:15 PDT 2018, Suman Anna wrote:
> Unwind the modified table_ptr and restore it to the local copy
> upon any subsequent failures in the rproc_start() function. This
> keeps the function to remain balanced on failures without the need
> to balance any modified variables elsewhere.
>
On Thu 26 Jul 18:15 PDT 2018, Suman Anna wrote:
> Unwind the modified table_ptr and restore it to the local copy
> upon any subsequent failures in the rproc_start() function. This
> keeps the function to remain balanced on failures without the need
> to balance any modified variables elsewhere.
>
Dear
Manager,
Are
you interested in clean car through below way?
1. Clean
one car just using 2 liters water,
2. Just
using water for car cleaning, no chemical,
3. Killing
car bacteria and bad smelling in the car,
4. 360o comprehensive
cleaning car, include car interior and
Dear
Manager,
Are
you interested in clean car through below way?
1. Clean
one car just using 2 liters water,
2. Just
using water for car cleaning, no chemical,
3. Killing
car bacteria and bad smelling in the car,
4. 360o comprehensive
cleaning car, include car interior and
> There is no reason not to use indentation and quotation marks in a changelog.
> Squeezing it into square brackets does not really improve readability.
>
> From the specification [1]:
>
> "With enhanced IBRS, the predicted targets of indirect branches executed
>cannot be controlled by
> There is no reason not to use indentation and quotation marks in a changelog.
> Squeezing it into square brackets does not really improve readability.
>
> From the specification [1]:
>
> "With enhanced IBRS, the predicted targets of indirect branches executed
>cannot be controlled by
Dear，
Do you know what is a HHO Carbon Cleaner ?
We combine HHO carbon machine with HHO carbon cleaning.
Thus achieving：
1. Reduce clean time, only 20 minutes.
2. Thoroughly clean the clean parts.
3. Cleaning effect increased by more than 30%.
4. Achieve the dual purpose of cleaning
Dear，
Do you know what is a HHO Carbon Cleaner ?
We combine HHO carbon machine with HHO carbon cleaning.
Thus achieving：
1. Reduce clean time, only 20 minutes.
2. Thoroughly clean the clean parts.
3. Cleaning effect increased by more than 30%.
4. Achieve the dual purpose of cleaning
On Mon, Jul 30, 2018 at 01:53:50PM -0400, Prarit Bhargava wrote:
> I think this has to be
>
> boot_cpu_data.microcode = mc_amd->hdr.patch_id;
Yes, it does.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
On Mon, Jul 30, 2018 at 01:53:50PM -0400, Prarit Bhargava wrote:
> I think this has to be
>
> boot_cpu_data.microcode = mc_amd->hdr.patch_id;
Yes, it does.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
On Mon 30 Jul 04:34 PDT 2018, Baolin Wang wrote:
> Hi Bjorn,
>
> On 28 June 2018 at 10:32, Baolin Wang wrote:
> > The commit 4f1acd758b08 ("hwspinlock: Add devm_xxx() APIs to request/free
> > hwlock") introduces one bug, that will return one error pointer if failed
> > to request one hwlock,
On Mon 30 Jul 04:34 PDT 2018, Baolin Wang wrote:
> Hi Bjorn,
>
> On 28 June 2018 at 10:32, Baolin Wang wrote:
> > The commit 4f1acd758b08 ("hwspinlock: Add devm_xxx() APIs to request/free
> > hwlock") introduces one bug, that will return one error pointer if failed
> > to request one hwlock,
Add addition argument 'arch_uprobe' to uprobe_write_opcode().
We need this in later set of patches.
Signed-off-by: Ravi Bangoria
---
arch/arm/probes/uprobes/core.c | 2 +-
arch/mips/kernel/uprobes.c | 2 +-
include/linux/uprobes.h| 2 +-
kernel/events/uprobes.c| 9 +
v7 changes:
- Don't allow both zero and non-zero reference counter offset at
the same time. It's painful and error prone.
- Don't call delayed_uprobe_install() if vma->vm_mm does not have
any breakpoint installed.
v6: https://lkml.org/lkml/2018/7/16/353
Description:
Userspace Statically
We assume to have only one reference counter for one uprobe.
Don't allow user to add multiple trace_uprobe entries having
same inode+offset but different reference counter.
Ex,
# echo "p:sdt_tick/loop2 /home/ravi/tick:0x6e4(0x10036)" > uprobe_events
# echo "p:sdt_tick/loop2_1
Simplify uprobe_register() function body and let __uprobe_register()
handle everything. Also move dependency functions around to fix build
failures.
Signed-off-by: Ravi Bangoria
---
kernel/events/uprobes.c | 69 ++---
1 file changed, 36 insertions(+),
Add addition argument 'arch_uprobe' to uprobe_write_opcode().
We need this in later set of patches.
Signed-off-by: Ravi Bangoria
---
arch/arm/probes/uprobes/core.c | 2 +-
arch/mips/kernel/uprobes.c | 2 +-
include/linux/uprobes.h| 2 +-
kernel/events/uprobes.c| 9 +
v7 changes:
- Don't allow both zero and non-zero reference counter offset at
the same time. It's painful and error prone.
- Don't call delayed_uprobe_install() if vma->vm_mm does not have
any breakpoint installed.
v6: https://lkml.org/lkml/2018/7/16/353
Description:
Userspace Statically
We assume to have only one reference counter for one uprobe.
Don't allow user to add multiple trace_uprobe entries having
same inode+offset but different reference counter.
Ex,
# echo "p:sdt_tick/loop2 /home/ravi/tick:0x6e4(0x10036)" > uprobe_events
# echo "p:sdt_tick/loop2_1
Simplify uprobe_register() function body and let __uprobe_register()
handle everything. Also move dependency functions around to fix build
failures.
Signed-off-by: Ravi Bangoria
---
kernel/events/uprobes.c | 69 ++---
1 file changed, 36 insertions(+),
Userspace Statically Defined Tracepoints[1] are dtrace style markers
inside userspace applications. Applications like PostgreSQL, MySQL,
Pthread, Perl, Python, Java, Ruby, Node.js, libvirt, QEMU, glib etc
have these markers embedded in them. These markers are added by developer
at important places
We assume to have only one reference counter for one uprobe.
Don't allow user to register multiple uprobes having same
inode+offset but different reference counter.
Signed-off-by: Ravi Bangoria
---
kernel/events/uprobes.c | 9 +
1 file changed, 9 insertions(+)
diff --git
With this, perf buildid-cache will save SDT markers with reference
counter in probe cache. Perf probe will be able to probe markers
having reference counter. Ex,
# readelf -n /tmp/tick | grep -A1 loop2
Name: loop2
... Semaphore: 0x10020036
# ./perf buildid-cache --add
We assume to have only one reference counter for one uprobe.
Don't allow user to register multiple uprobes having same
inode+offset but different reference counter.
Signed-off-by: Ravi Bangoria
---
kernel/events/uprobes.c | 9 +
1 file changed, 9 insertions(+)
diff --git
With this, perf buildid-cache will save SDT markers with reference
counter in probe cache. Perf probe will be able to probe markers
having reference counter. Ex,
# readelf -n /tmp/tick | grep -A1 loop2
Name: loop2
... Semaphore: 0x10020036
# ./perf buildid-cache --add
Userspace Statically Defined Tracepoints[1] are dtrace style markers
inside userspace applications. Applications like PostgreSQL, MySQL,
Pthread, Perl, Python, Java, Ruby, Node.js, libvirt, QEMU, glib etc
have these markers embedded in them. These markers are added by developer
at important places
On Mon 30 Jul 05:29 PDT 2018, Baolin Wang wrote:
> Some LED controllers have support for autonomously controlling
> brightness over time, according to some preprogrammed pattern or
> function.
>
> This patch adds pattern trigger that LED device can configure the
> pattern and trigger it.
>
>
On Mon 30 Jul 05:29 PDT 2018, Baolin Wang wrote:
> Some LED controllers have support for autonomously controlling
> brightness over time, according to some preprogrammed pattern or
> function.
>
> This patch adds pattern trigger that LED device can configure the
> pattern and trigger it.
>
>
On Tue, 31 Jul 2018 at 00:43, Vincent Guittot
wrote:
>
> Hi Wanpeng,
>
> On Thu, 26 Jul 2018 at 05:09, Wanpeng Li wrote:
> >
> > Hi Vincent,
> > On Fri, 29 Jun 2018 at 03:07, Vincent Guittot
> > wrote:
> > >
> > > interrupt and steal time are the only remaining activities tracked by
> > >
On Tue, 31 Jul 2018 at 00:43, Vincent Guittot
wrote:
>
> Hi Wanpeng,
>
> On Thu, 26 Jul 2018 at 05:09, Wanpeng Li wrote:
> >
> > Hi Vincent,
> > On Fri, 29 Jun 2018 at 03:07, Vincent Guittot
> > wrote:
> > >
> > > interrupt and steal time are the only remaining activities tracked by
> > >
1 - 100 of 1406 matches
Mail list logo
