On Wed, 5 Dec 2018 11:43:12 +0100
Anders Roxell wrote:
> > > + schedulable = !irqs_disabled() && !preempt_count();
> >
> > Is there a reason not to use preemptible() here?
>
> As I understand it preemptible() is defined to 0 if
> CONFIG_PREEMPT_COUNT is disabled.
> Thats no good right ?
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Yangtao Li
---
drivers/usb/host/isp1362-hcd.c | 16 +++-
1 file changed, 3 insertions(+), 13 deletions(-)
diff --git a/drivers/usb/host/isp1362-hcd.c b/drivers/usb/host/isp1362-hcd.c
index
On Wed, 5 Dec 2018 11:43:12 +0100
Anders Roxell wrote:
> > > + schedulable = !irqs_disabled() && !preempt_count();
> >
> > Is there a reason not to use preemptible() here?
>
> As I understand it preemptible() is defined to 0 if
> CONFIG_PREEMPT_COUNT is disabled.
> Thats no good right ?
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Yangtao Li
---
drivers/usb/host/isp1362-hcd.c | 16 +++-
1 file changed, 3 insertions(+), 13 deletions(-)
diff --git a/drivers/usb/host/isp1362-hcd.c b/drivers/usb/host/isp1362-hcd.c
index
On 03. 12. 18 8:50, Masahiro Yamada wrote:
> I guess
>
> || (rm -f $@ && echo false)
>
> ... should be
>
> || (rm -f $@ && false)
>
> since printing the string "false" on the console has no point.
>
> Moreover, no Makefile needs to delete a target on error explicitly
> since commit
On 03. 12. 18 8:50, Masahiro Yamada wrote:
> I guess
>
> || (rm -f $@ && echo false)
>
> ... should be
>
> || (rm -f $@ && false)
>
> since printing the string "false" on the console has no point.
>
> Moreover, no Makefile needs to delete a target on error explicitly
> since commit
On 03. 12. 18 8:50, Masahiro Yamada wrote:
> I fixed a race condition in the parallel building of ARM in commit
> 3939f3345050 ("ARM: 8418/1: add boot image dependencies to not
> generate invalid images").
>
> I see the same problem for MicroBlaze too.
>
> "make -j ARCH=microblaze all
On 03. 12. 18 8:50, Masahiro Yamada wrote:
> I fixed a race condition in the parallel building of ARM in commit
> 3939f3345050 ("ARM: 8418/1: add boot image dependencies to not
> generate invalid images").
>
> I see the same problem for MicroBlaze too.
>
> "make -j ARCH=microblaze all
Hi Greg,
On 05-12-18, 11:03, Greg Kroah-Hartman wrote:
> On Wed, Dec 05, 2018 at 04:42:56PM +0800, Long Cheng wrote:
> > In Mediatek SOCs, the uart can support DMA function.
> > Base on DMA engine formwork, we add the DMA code to support uart. And put
> > the code under drivers/dma.
> >
> >
Hi Greg,
On 05-12-18, 11:03, Greg Kroah-Hartman wrote:
> On Wed, Dec 05, 2018 at 04:42:56PM +0800, Long Cheng wrote:
> > In Mediatek SOCs, the uart can support DMA function.
> > Base on DMA engine formwork, we add the DMA code to support uart. And put
> > the code under drivers/dma.
> >
> >
* Borislav Petkov wrote:
> From: Borislav Petkov
>
> Rename the containing folder to "mce" which is the most widespread name.
> Drop the "mce[-_]" filename prefix of some compilation units (while
> others don't have it).
>
> This unifies the file naming in the MCE subsystem:
>
> mce/
> |--
* Borislav Petkov wrote:
> From: Borislav Petkov
>
> Rename the containing folder to "mce" which is the most widespread name.
> Drop the "mce[-_]" filename prefix of some compilation units (while
> others don't have it).
>
> This unifies the file naming in the MCE subsystem:
>
> mce/
> |--
On Wed, Dec 05, 2018 at 06:02:22AM -0800, Todd Kjos wrote:
> On Wed, Dec 5, 2018 at 2:57 AM Greg KH wrote:
>
> > On Mon, Dec 03, 2018 at 12:24:54PM -0800, Todd Kjos wrote:
> > > Add __acquire()/__release() annnotations to fix warnings
> > > in sparse context checking
> > >
> > > There is one
On Wed, Dec 05, 2018 at 06:02:22AM -0800, Todd Kjos wrote:
> On Wed, Dec 5, 2018 at 2:57 AM Greg KH wrote:
>
> > On Mon, Dec 03, 2018 at 12:24:54PM -0800, Todd Kjos wrote:
> > > Add __acquire()/__release() annnotations to fix warnings
> > > in sparse context checking
> > >
> > > There is one
On Wed, Dec 05, 2018 at 12:27:43PM +0100, Peter Rajnoha wrote:
> Two small patches to aid handling of synthetic uevents back in userspace:
>
> - Return error code back to userspace on /sys/.../uevent file write
> failure so userspace knows and it can act accordingly.
>
> - Add new
On Wed, Dec 05, 2018 at 12:27:43PM +0100, Peter Rajnoha wrote:
> Two small patches to aid handling of synthetic uevents back in userspace:
>
> - Return error code back to userspace on /sys/.../uevent file write
> failure so userspace knows and it can act accordingly.
>
> - Add new
* Borislav Petkov wrote:
> On Wed, Dec 05, 2018 at 10:49:06PM +0900, Masami Hiramatsu wrote:
> > I would like to put this prototype inside arch/x86/kernel/kprobes/core.c,
> > since that is locally used.
>
> Done.
Also, preferably the prototype should be eliminated via proper ordering
of
* Borislav Petkov wrote:
> On Wed, Dec 05, 2018 at 10:49:06PM +0900, Masami Hiramatsu wrote:
> > I would like to put this prototype inside arch/x86/kernel/kprobes/core.c,
> > since that is locally used.
>
> Done.
Also, preferably the prototype should be eliminated via proper ordering
of
Hi Peter,
Good news is that I got our opengl test running on your x86/mm branch.
The commit a2b4306c50b5de2ca955cd73ac57c2ac6426ee15 (current tip of
x86/mm) is good. For sanity I jumped back and found this commit
a2aa52ab16efbee40ad118ebac4a5e438f5b43ee doesn't work.
Thanks,
Tom
On
Hi Peter,
Good news is that I got our opengl test running on your x86/mm branch.
The commit a2b4306c50b5de2ca955cd73ac57c2ac6426ee15 (current tip of
x86/mm) is good. For sanity I jumped back and found this commit
a2aa52ab16efbee40ad118ebac4a5e438f5b43ee doesn't work.
Thanks,
Tom
On
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Yangtao Li
---
drivers/dma/mic_x100_dma.c | 22 +++---
1 file changed, 3 insertions(+), 19 deletions(-)
diff --git a/drivers/dma/mic_x100_dma.c b/drivers/dma/mic_x100_dma.c
index adfd316db1a8..6a91e28d537d
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Yangtao Li
---
drivers/dma/mic_x100_dma.c | 22 +++---
1 file changed, 3 insertions(+), 19 deletions(-)
diff --git a/drivers/dma/mic_x100_dma.c b/drivers/dma/mic_x100_dma.c
index adfd316db1a8..6a91e28d537d
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Yangtao Li
---
drivers/dma/amba-pl08x.c | 14 ++
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/drivers/dma/amba-pl08x.c b/drivers/dma/amba-pl08x.c
index 97483df1f82e..fc8c2bab563c 100644
---
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Yangtao Li
---
drivers/dma/amba-pl08x.c | 14 ++
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/drivers/dma/amba-pl08x.c b/drivers/dma/amba-pl08x.c
index 97483df1f82e..fc8c2bab563c 100644
---
On Wed, Dec 5, 2018 at 11:59 PM Vinod Koul wrote:
>
> On 05-12-18, 23:49, Frank Lee wrote:
> > On Wed, Dec 5, 2018 at 4:27 PM Vinod Koul wrote:
> > >
> > > On 30-11-18, 10:42, Yangtao Li wrote:
> > > > We already have the DEFINE_SHOW_ATTRIBUTE,There is no need to define
> > > > such a macro,so
On Wed, Dec 5, 2018 at 11:59 PM Vinod Koul wrote:
>
> On 05-12-18, 23:49, Frank Lee wrote:
> > On Wed, Dec 5, 2018 at 4:27 PM Vinod Koul wrote:
> > >
> > > On 30-11-18, 10:42, Yangtao Li wrote:
> > > > We already have the DEFINE_SHOW_ATTRIBUTE,There is no need to define
> > > > such a macro,so
On Wed, 5 Dec 2018 at 17:11, Anand Moon wrote:
>
> Hi Krzysztof,
>
> Thanks for your review.
> .
> On Wed, 5 Dec 2018 at 19:36, Krzysztof Kozlowski wrote:
> >
> > On Tue, 4 Dec 2018 at 20:40, Anand Moon wrote:
> > >
> > > Add suspend-to-mem node to regulator core to be enabled or disabled
> > >
On Wed, 5 Dec 2018 at 17:11, Anand Moon wrote:
>
> Hi Krzysztof,
>
> Thanks for your review.
> .
> On Wed, 5 Dec 2018 at 19:36, Krzysztof Kozlowski wrote:
> >
> > On Tue, 4 Dec 2018 at 20:40, Anand Moon wrote:
> > >
> > > Add suspend-to-mem node to regulator core to be enabled or disabled
> > >
We already have the DEFINE_SHOW_ATTRIBUTE, There is no need to define
such a macro, so remove DBGFS_FUNC_DECL.
Signed-off-by: Yangtao Li
Acked-by: Robert Jarzmik
---
drivers/dma/pxa_dma.c | 36
1 file changed, 12 insertions(+), 24 deletions(-)
diff --git
We already have the DEFINE_SHOW_ATTRIBUTE, There is no need to define
such a macro, so remove DBGFS_FUNC_DECL.
Signed-off-by: Yangtao Li
Acked-by: Robert Jarzmik
---
drivers/dma/pxa_dma.c | 36
1 file changed, 12 insertions(+), 24 deletions(-)
diff --git
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Yangtao Li
Acked-by: Sinan Kaya
---
drivers/dma/qcom/hidma_dbg.c | 33 ++---
1 file changed, 6 insertions(+), 27 deletions(-)
diff --git a/drivers/dma/qcom/hidma_dbg.c
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Yangtao Li
Acked-by: Sinan Kaya
---
drivers/dma/qcom/hidma_dbg.c | 33 ++---
1 file changed, 6 insertions(+), 27 deletions(-)
diff --git a/drivers/dma/qcom/hidma_dbg.c
On Wed, Nov 28, 2018 at 10:39:50AM +0100, Thierry Reding wrote:
> On Wed, Nov 21, 2018 at 03:54:10PM +0100, Thierry Reding wrote:
> > From: Thierry Reding
> >
> > Hi,
> >
> > This series of patches adds device-managed registration functions for
> > mailbox controllers. A number of drivers can
On Wed, Nov 28, 2018 at 10:39:50AM +0100, Thierry Reding wrote:
> On Wed, Nov 21, 2018 at 03:54:10PM +0100, Thierry Reding wrote:
> > From: Thierry Reding
> >
> > Hi,
> >
> > This series of patches adds device-managed registration functions for
> > mailbox controllers. A number of drivers can
On Wed, Dec 05, 2018 at 10:37:56AM +0100, Ondrej Mosnacek wrote:
> I just tested the Q28 branch rebased onto a recent Fedora rawhide
> kernel (4.20.0-0.rc5.git0.1) and that code seems to be working fine.
> The submount test failed with Q28 and succeeds with Q28+fix, as
> expected. Also, the
On Wed, Dec 05, 2018 at 10:37:56AM +0100, Ondrej Mosnacek wrote:
> I just tested the Q28 branch rebased onto a recent Fedora rawhide
> kernel (4.20.0-0.rc5.git0.1) and that code seems to be working fine.
> The submount test failed with Q28 and succeeds with Q28+fix, as
> expected. Also, the
On Sun, Nov 18, 2018 at 08:33:03AM +1100, NeilBrown wrote:
> On Thu, Oct 04 2018, Nishad Kamdar wrote:
>
> > This patch removes #if 0 code blocks and usages of
> > functions defined in the #if 0 blocks in sd.c.
> >
> > Signed-off-by: Nishad Kamdar
>
> Hi Nishad,
> thanks for this patch (and
On Sun, Nov 18, 2018 at 08:33:03AM +1100, NeilBrown wrote:
> On Thu, Oct 04 2018, Nishad Kamdar wrote:
>
> > This patch removes #if 0 code blocks and usages of
> > functions defined in the #if 0 blocks in sd.c.
> >
> > Signed-off-by: Nishad Kamdar
>
> Hi Nishad,
> thanks for this patch (and
On Tue, Nov 27, 2018 at 12:03 PM Georgi Djakov wrote:
>
> This patch introduces a new API to get requirements and configure the
> interconnect buses across the entire chipset to fit with the current
> demand.
>
> The API is using a consumer/provider-based model, where the providers are
> the
On Tue, Nov 27, 2018 at 12:03 PM Georgi Djakov wrote:
>
> This patch introduces a new API to get requirements and configure the
> interconnect buses across the entire chipset to fit with the current
> demand.
>
> The API is using a consumer/provider-based model, where the providers are
> the
The below patch
https://lore.kernel.org/patchwork/patch/995533/
does not completely remove an #if 0 block in sd.c.
This causes the function msdc_select_clksrc()
which was earler not compiled, to be compiled.
That causes an error - MSDC_CLKSRC_REG is not
defined.
This patch completely removes the
The below patch
https://lore.kernel.org/patchwork/patch/995533/
does not completely remove an #if 0 block in sd.c.
This causes the function msdc_select_clksrc()
which was earler not compiled, to be compiled.
That causes an error - MSDC_CLKSRC_REG is not
defined.
This patch completely removes the
Hi Krzysztof,
Krzysztof Kozlowski wrote on Wed, 5 Dec 2018 17:10:38
+0100:
> On Tue, 20 Nov 2018 at 13:15, Krzysztof Kozlowski wrote:
> >
> > On Tue, 20 Nov 2018 at 13:09, Boris Brezillon
> > wrote:
> > >
> > > On Tue, 20 Nov 2018 12:48:46 +0100
> > > Krzysztof Kozlowski wrote:
> > >
> >
Hi Krzysztof,
Krzysztof Kozlowski wrote on Wed, 5 Dec 2018 17:10:38
+0100:
> On Tue, 20 Nov 2018 at 13:15, Krzysztof Kozlowski wrote:
> >
> > On Tue, 20 Nov 2018 at 13:09, Boris Brezillon
> > wrote:
> > >
> > > On Tue, 20 Nov 2018 12:48:46 +0100
> > > Krzysztof Kozlowski wrote:
> > >
> >
On Tue, 20 Nov 2018 at 13:15, Krzysztof Kozlowski wrote:
>
> On Tue, 20 Nov 2018 at 13:09, Boris Brezillon
> wrote:
> >
> > On Tue, 20 Nov 2018 12:48:46 +0100
> > Krzysztof Kozlowski wrote:
> >
> > > On Tue, 20 Nov 2018 at 11:33, Miquel Raynal
> > > wrote:
> > > >
> > > > Hi Krzysztof,
> > >
On Tue, 20 Nov 2018 at 13:15, Krzysztof Kozlowski wrote:
>
> On Tue, 20 Nov 2018 at 13:09, Boris Brezillon
> wrote:
> >
> > On Tue, 20 Nov 2018 12:48:46 +0100
> > Krzysztof Kozlowski wrote:
> >
> > > On Tue, 20 Nov 2018 at 11:33, Miquel Raynal
> > > wrote:
> > > >
> > > > Hi Krzysztof,
> > >
Hi Krzysztof,
Thanks for your review.
.
On Wed, 5 Dec 2018 at 19:36, Krzysztof Kozlowski wrote:
>
> On Tue, 4 Dec 2018 at 20:40, Anand Moon wrote:
> >
> > Add suspend-to-mem node to regulator core to be enabled or disabled
> > during system suspend and also support changing the regulator
Hi Krzysztof,
Thanks for your review.
.
On Wed, 5 Dec 2018 at 19:36, Krzysztof Kozlowski wrote:
>
> On Tue, 4 Dec 2018 at 20:40, Anand Moon wrote:
> >
> > Add suspend-to-mem node to regulator core to be enabled or disabled
> > during system suspend and also support changing the regulator
Quoting Sylwester Nawrocki (2018-12-05 02:57:32)
> On 12/4/18 19:40, Stephen Boyd wrote:
> > Quoting Kamil Konieczny (2018-12-04 08:52:48)
> >> +
> >> +static const unsigned long imem_clk_regs[] __initconst = {
> >> + ENABLE_ACLK_IMEM,
> >> + ENABLE_ACLK_IMEM_INT_MEM,
> >> +
On Tue, Dec 04, 2018 at 03:37:16PM -0700, Yu Zhao wrote:
> The parameter is still there but it's ignored. We need to check its
> value before deciding to go into passthrough mode for AMD IOMMU.
>
> Fixes: aafd8ba0ca74 ("iommu/amd: Implement add_device and remove_device")
>
> Signed-off-by: Yu
Quoting Sylwester Nawrocki (2018-12-05 02:57:32)
> On 12/4/18 19:40, Stephen Boyd wrote:
> > Quoting Kamil Konieczny (2018-12-04 08:52:48)
> >> +
> >> +static const unsigned long imem_clk_regs[] __initconst = {
> >> + ENABLE_ACLK_IMEM,
> >> + ENABLE_ACLK_IMEM_INT_MEM,
> >> +
On Tue, Dec 04, 2018 at 03:37:16PM -0700, Yu Zhao wrote:
> The parameter is still there but it's ignored. We need to check its
> value before deciding to go into passthrough mode for AMD IOMMU.
>
> Fixes: aafd8ba0ca74 ("iommu/amd: Implement add_device and remove_device")
>
> Signed-off-by: Yu
On Wed, Dec 05, 2018 at 04:57:17PM +0530, Aneesh Kumar K.V wrote:
> On 12/5/18 12:19 AM, Jerome Glisse wrote:
>
> > Above example is for migrate. Here is an example for how the
> > topology is use today:
> >
> > Application knows that the platform is running on have 16
> > GPU split
On Wed, Dec 05, 2018 at 04:57:17PM +0530, Aneesh Kumar K.V wrote:
> On 12/5/18 12:19 AM, Jerome Glisse wrote:
>
> > Above example is for migrate. Here is an example for how the
> > topology is use today:
> >
> > Application knows that the platform is running on have 16
> > GPU split
hi,
Steven asked for possibility to block traced process
in case the tracer can't keep up and we would loose
events.
This (RFC) patchset tries to implement this by adding
'block' bool in struct perf_event_attr to be set only
for syscalls tracepoints and adding code to block the
traced
hi,
Steven asked for possibility to block traced process
in case the tracer can't keep up and we would loose
events.
This (RFC) patchset tries to implement this by adding
'block' bool in struct perf_event_attr to be set only
for syscalls tracepoints and adding code to block the
traced
On Wed, Dec 5, 2018 at 4:08 AM Rafael David Tinoco
wrote:
>
> On 12/5/18 4:58 AM, Greg Kroah-Hartman wrote:
> > On Tue, Dec 04, 2018 at 07:09:46PM -0200, Rafael David Tinoco wrote:
> >> On 12/4/18 8:48 AM, Greg Kroah-Hartman wrote:
> >>> This is the start of the stable review cycle for the 4.19.7
On Wed, Dec 5, 2018 at 4:08 AM Rafael David Tinoco
wrote:
>
> On 12/5/18 4:58 AM, Greg Kroah-Hartman wrote:
> > On Tue, Dec 04, 2018 at 07:09:46PM -0200, Rafael David Tinoco wrote:
> >> On 12/4/18 8:48 AM, Greg Kroah-Hartman wrote:
> >>> This is the start of the stable review cycle for the 4.19.7
Adding support to specify 'block' bool in struct perf_event_attr
for syscalls tracepoints, allowing the event to block the process,
if there's no space in the ring buffer.
The blocking code will poll/periodically check for the space and
continue if the event was successfully written.
It's
Adding --block option to allow trace command pass along
the --block option for record command or to set it for
trace run session, like:
# perf trace --block kill
# perf trace --block -p ...
# perf trace -e raw_syscalls:sys_enter --block -p ...
It's allowed only for syscall tracepoint
Adding support to specify 'block' bool in struct perf_event_attr
for syscalls tracepoints, allowing the event to block the process,
if there's no space in the ring buffer.
The blocking code will poll/periodically check for the space and
continue if the event was successfully written.
It's
Adding --block option to allow trace command pass along
the --block option for record command or to set it for
trace run session, like:
# perf trace --block kill
# perf trace --block -p ...
# perf trace -e raw_syscalls:sys_enter --block -p ...
It's allowed only for syscall tracepoint
Adding --block option to allow record command set block
bool in struct perf_event_attr for event, like:
# perf record -e raw_syscalls:sys_enter --block ls
# perf record -e raw_syscalls:sys_enter --block -p ...
It's allowed only for syscall tracepoint events
attached to process.
Link:
Adding OE_FLUSH__TIME flush type, to be able to flush
only certain amount of the queue based on the provided
timestamp. It will be used in following patches.
Link: http://lkml.kernel.org/n/tip-a3na77vemwr1g92lfhlrz...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/ordered-events.c
Adding --block option to allow record command set block
bool in struct perf_event_attr for event, like:
# perf record -e raw_syscalls:sys_enter --block ls
# perf record -e raw_syscalls:sys_enter --block -p ...
It's allowed only for syscall tracepoint events
attached to process.
Link:
Adding OE_FLUSH__TIME flush type, to be able to flush
only certain amount of the queue based on the provided
timestamp. It will be used in following patches.
Link: http://lkml.kernel.org/n/tip-a3na77vemwr1g92lfhlrz...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/ordered-events.c
Link: http://lkml.kernel.org/n/tip-lh4vrg3t3sjhvue16i5f3...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/include/uapi/linux/perf_event.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/include/uapi/linux/perf_event.h
b/tools/include/uapi/linux/perf_event.h
index
Link: http://lkml.kernel.org/n/tip-lh4vrg3t3sjhvue16i5f3...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/include/uapi/linux/perf_event.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/include/uapi/linux/perf_event.h
b/tools/include/uapi/linux/perf_event.h
index
Moving event delivery code to deliver_event function,
so it's easier to add conditional ordered delivery
coming in following patches.
Link: http://lkml.kernel.org/n/tip-qz9wzti2cw6q7swja0h2x...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/builtin-trace.c | 25 -
Moving event delivery code to deliver_event function,
so it's easier to add conditional ordered delivery
coming in following patches.
Link: http://lkml.kernel.org/n/tip-qz9wzti2cw6q7swja0h2x...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/builtin-trace.c | 25 -
Allow to specify 'block' term for tracepoint in the -e command
line option, like:
# perf record -e raw_syscalls:sys_enter/block/ -p ...
# perf trace -e raw_syscalls:sys_enter/block/ -p ...
to set this tracepoint as blocking (sets struct perf_event_attr::block)
It's allowed only for syscall
Allow to specify 'block' term for tracepoint in the -e command
line option, like:
# perf record -e raw_syscalls:sys_enter/block/ -p ...
# perf trace -e raw_syscalls:sys_enter/block/ -p ...
to set this tracepoint as blocking (sets struct perf_event_attr::block)
It's allowed only for syscall
Adding support to sort the trace events if --block option is set.
In this mode we don't loose events, and we are potentionally slow
by definition, because the traced process could be blocked.
In this case it makes sense to sort events and provide the precise
outcome of ordered events.
Link:
Adding support to sort the trace events if --block option is set.
In this mode we don't loose events, and we are potentionally slow
by definition, because the traced process could be blocked.
In this case it makes sense to sort events and provide the precise
outcome of ordered events.
Link:
On 18-11-22 14:14:29, Marc Zyngier wrote:
> On Wed, 21 Nov 2018 17:58:41 +,
> Pavel Tatashin wrote:
> >
> > On 18-11-21 17:47:07, Will Deacon wrote:
> > > > + /*
> > > > +* The arm64 boot protocol mandates that CNTFRQ_EL0 reflects
> > > > +* the timer frequency. To
On 18-11-22 14:14:29, Marc Zyngier wrote:
> On Wed, 21 Nov 2018 17:58:41 +,
> Pavel Tatashin wrote:
> >
> > On 18-11-21 17:47:07, Will Deacon wrote:
> > > > + /*
> > > > +* The arm64 boot protocol mandates that CNTFRQ_EL0 reflects
> > > > +* the timer frequency. To
Hi Evan,
On 12/1/18 02:39, Evan Green wrote:
> On Tue, Nov 27, 2018 at 10:04 AM Georgi Djakov
> wrote:
>>
>> From: David Dai
>>
>> Introduce Qualcomm SDM845 specific provider driver using the
>> interconnect framework.
>>
>> Signed-off-by: David Dai
>> Signed-off-by: Georgi Djakov
>> ---
>>
Hi Evan,
On 12/1/18 02:39, Evan Green wrote:
> On Tue, Nov 27, 2018 at 10:04 AM Georgi Djakov
> wrote:
>>
>> From: David Dai
>>
>> Introduce Qualcomm SDM845 specific provider driver using the
>> interconnect framework.
>>
>> Signed-off-by: David Dai
>> Signed-off-by: Georgi Djakov
>> ---
>>
Hi Evan,
On 12/1/18 02:39, Evan Green wrote:
> On Tue, Nov 27, 2018 at 10:04 AM Georgi Djakov
> wrote:
>>
>> From: David Dai
>>
>> Add RSC (Resource State Coordinator) provider
>> dictating network-on-chip interconnect bus performance
>> found on SDM845-based platforms.
>>
>> Signed-off-by:
On Wed, Nov 07, 2018 at 10:09:10AM +, Z.q. Hou wrote:
> From: Hou Zhiqiang
>
> The current type of mem_size is 'u32', so when resource_size()
> return 4G it will be truncated to zero. This patch fix it by
> changing its type to 'u64'.
>
> Signed-off-by: Hou Zhiqiang
> Acked-by: Gustavo
Hi Evan,
On 12/1/18 02:39, Evan Green wrote:
> On Tue, Nov 27, 2018 at 10:04 AM Georgi Djakov
> wrote:
>>
>> From: David Dai
>>
>> Add RSC (Resource State Coordinator) provider
>> dictating network-on-chip interconnect bus performance
>> found on SDM845-based platforms.
>>
>> Signed-off-by:
On Wed, Nov 07, 2018 at 10:09:10AM +, Z.q. Hou wrote:
> From: Hou Zhiqiang
>
> The current type of mem_size is 'u32', so when resource_size()
> return 4G it will be truncated to zero. This patch fix it by
> changing its type to 'u64'.
>
> Signed-off-by: Hou Zhiqiang
> Acked-by: Gustavo
On 12/5/18 3:23 PM, Ulf Hansson wrote:
On Tue, 20 Nov 2018 at 10:42, Ulf Hansson wrote:
On 7 November 2018 at 10:30, Ludovic Barre wrote:
From: Ludovic Barre
Refer to "4.15 set block count command" of sd specification:
Host needs to issue CMD12 if any error is detected in
the CMD18 and
On 12/5/18 3:23 PM, Ulf Hansson wrote:
On Tue, 20 Nov 2018 at 10:42, Ulf Hansson wrote:
On 7 November 2018 at 10:30, Ludovic Barre wrote:
From: Ludovic Barre
Refer to "4.15 set block count command" of sd specification:
Host needs to issue CMD12 if any error is detected in
the CMD18 and
On Wed, Dec 05, 2018 at 04:19:16PM +0100, Johan Hovold wrote:
> On Mon, Nov 19, 2018 at 07:44:14PM +0100, Andreas Kemnade wrote:
>
> > On Mon, 19 Nov 2018 09:22:59 +0100
> > "H. Nikolaus Schaller" wrote:
>
> > > > Am 18.11.2018 um 22:57 schrieb Andreas Kemnade :
> > > >
> > > > Here is another
On Wed, Dec 05, 2018 at 04:19:16PM +0100, Johan Hovold wrote:
> On Mon, Nov 19, 2018 at 07:44:14PM +0100, Andreas Kemnade wrote:
>
> > On Mon, 19 Nov 2018 09:22:59 +0100
> > "H. Nikolaus Schaller" wrote:
>
> > > > Am 18.11.2018 um 22:57 schrieb Andreas Kemnade :
> > > >
> > > > Here is another
Quoting Taniya Das (2018-12-05 00:02:00)
> The GCC lpass clocks are updated as protected, so clean up the ifdefers.
>
> Signed-off-by: Taniya Das
> ---
Ok. But this will have to wait for a few months until everything is
merged together. Was that the intention of sending this now instead of
Quoting Taniya Das (2018-12-05 00:02:00)
> The GCC lpass clocks are updated as protected, so clean up the ifdefers.
>
> Signed-off-by: Taniya Das
> ---
Ok. But this will have to wait for a few months until everything is
merged together. Was that the intention of sending this now instead of
On 05-12-18, 23:49, Frank Lee wrote:
> On Wed, Dec 5, 2018 at 4:27 PM Vinod Koul wrote:
> >
> > On 30-11-18, 10:42, Yangtao Li wrote:
> > > We already have the DEFINE_SHOW_ATTRIBUTE,There is no need to define
> > > such a macro,so remove DBGFS_FUNC_DECL.Also use macro to simplify some
> > > code.
On 05-12-18, 23:49, Frank Lee wrote:
> On Wed, Dec 5, 2018 at 4:27 PM Vinod Koul wrote:
> >
> > On 30-11-18, 10:42, Yangtao Li wrote:
> > > We already have the DEFINE_SHOW_ATTRIBUTE,There is no need to define
> > > such a macro,so remove DBGFS_FUNC_DECL.Also use macro to simplify some
> > > code.
On 03. 12. 18 8:50, Masahiro Yamada wrote:
> linux.bin, linux.bin.gz, and linux.bin.ub are phony targets to
> generate a corresponding image under arch/microblaze/boot/.
>
> simpleImage.% also works like a PHONY target, but a pattern that
> contains '%' cannot be a PHONY target. I renamed it to
On 03. 12. 18 8:50, Masahiro Yamada wrote:
> linux.bin, linux.bin.gz, and linux.bin.ub are phony targets to
> generate a corresponding image under arch/microblaze/boot/.
>
> simpleImage.% also works like a PHONY target, but a pattern that
> contains '%' cannot be a PHONY target. I renamed it to
On Thu, Nov 29, 2018 at 09:51:55AM -0500, Connor McAdams wrote:
This patch won't break anything, but it also won't fix anything
either. Not sure if that matters or not.
I'll remove it then, thank you.
--
Thanks,
Sasha
On Thu, Nov 29, 2018 at 09:51:55AM -0500, Connor McAdams wrote:
This patch won't break anything, but it also won't fix anything
either. Not sure if that matters or not.
I'll remove it then, thank you.
--
Thanks,
Sasha
On 03. 12. 18 8:50, Masahiro Yamada wrote:
> This Makefile is wrong in multiple ways.
>
> The first issue is the breakage of 'linux.bin.ub' target since commit
> ece97f3a5fb5 ("microblaze: Fix simpleImage format generation")
> because the addition of UIMAGE_{IN,OUT} obviously affected it.
>
>
On 03. 12. 18 8:50, Masahiro Yamada wrote:
> This Makefile is wrong in multiple ways.
>
> The first issue is the breakage of 'linux.bin.ub' target since commit
> ece97f3a5fb5 ("microblaze: Fix simpleImage format generation")
> because the addition of UIMAGE_{IN,OUT} obviously affected it.
>
>
Hi Evan,
On 12/1/18 02:38, Evan Green wrote:
> On Tue, Nov 27, 2018 at 10:03 AM Georgi Djakov
> wrote:
>>
>> This patch introduces a new API to get requirements and configure the
>> interconnect buses across the entire chipset to fit with the current
>> demand.
>>
>> The API is using a
Hi Evan,
On 12/1/18 02:38, Evan Green wrote:
> On Tue, Nov 27, 2018 at 10:04 AM Georgi Djakov
> wrote:
>>
>> Currently we support only platform data for specifying the interconnect
>> endpoints. As now the endpoints are hard-coded into the consumer driver
>> this may lead to complications when
Hi Evan,
On 12/1/18 02:38, Evan Green wrote:
> On Tue, Nov 27, 2018 at 10:03 AM Georgi Djakov
> wrote:
>>
>> This patch introduces a new API to get requirements and configure the
>> interconnect buses across the entire chipset to fit with the current
>> demand.
>>
>> The API is using a
Hi Evan,
On 12/1/18 02:38, Evan Green wrote:
> On Tue, Nov 27, 2018 at 10:04 AM Georgi Djakov
> wrote:
>>
>> Currently we support only platform data for specifying the interconnect
>> endpoints. As now the endpoints are hard-coded into the consumer driver
>> this may lead to complications when
1101 - 1200 of 2376 matches
Mail list logo
