From: Adrian Hunter
When the number of queues grows beyond 32, the array of queues is
resized but not all members were being copied. Fix by also copying
'tid', 'cpu' and 'set'.
Signed-off-by: Adrian Hunter
Cc: Jiri Olsa
Cc: sta...@vger.kernel.org
Fixes: e502789302a6e ("perf auxtrace: Add
From: Adrian Hunter
The logic in update_iter_mod() is overcomplicated and gets worse every
time another get_ksymbol_* function is added.
In preparation for adding another get_ksymbol_* function, simplify logic
in update_iter_mod().
Signed-off-by: Adrian Hunter
Tested-by: (ftrace changes only)
From: Benno Evers
The argument to nsinfo__copy() was assumed to be valid, but some code paths
exist that will lead to NULL being passed.
In particular, running 'perf script -D' on a perf.data file containing an
PERF_RECORD_MMAP event associating the '[vdso]' dso with pid 0 earlier in
the event
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
static variables and functions in event-parse.c:
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_buffer_init, pevent_read_token,
From: Benno Evers
The argument to nsinfo__copy() was assumed to be valid, but some code paths
exist that will lead to NULL being passed.
In particular, running 'perf script -D' on a perf.data file containing an
PERF_RECORD_MMAP event associating the '[vdso]' dso with pid 0 earlier in
the event
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
static variables and functions in event-parse.c:
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_buffer_init, pevent_read_token,
From: Alexander Kapshuk
The '||' path of execution in the 'test' block of the check_2() function
may also be taken if file2 does not exist, in which case the warning
message about the ABI headers being different would still be printed
where it should not be. See below.
% file1=file1;
From: Alexander Kapshuk
The '||' path of execution in the 'test' block of the check_2() function
may also be taken if file2 does not exist, in which case the warning
message about the ABI headers being different would still be printed
where it should not be. See below.
% file1=file1;
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_reset_function_resolver,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_reset_function_resolver,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "traceevent_". This changes
APIs: traceevent_plugin_list_options,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_find_function,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_data_lat_fmt, pevent_data_type,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_function_handler,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "traceevent_". This changes
APIs: traceevent_plugin_list_options,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_find_function,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_data_lat_fmt, pevent_data_type,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_function_handler,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_register_print_function,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
'enum pevent_errno' to 'enum tep_errno'.
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: PEVENT_FILTER_ERROR_BUFSZ,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_pid_is_registered, pevent_get_cpus,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
pevent_get_page_size API and enum pevent_flag to
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_free_format,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_pid_is_registered, pevent_get_cpus,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
pevent_get_page_size API and enum pevent_flag to
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_free_format,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_register_print_function,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
'enum pevent_errno' to 'enum tep_errno'.
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: PEVENT_FILTER_ERROR_BUFSZ,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_read_number,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_register_comm,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_read_number,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_register_comm,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "traceevent_". This
changes APIs: traceevent_host_bigendian,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_set_file_bigendian, pevent_set_flag,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "traceevent_". This
changes APIs: traceevent_host_bigendian,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_set_file_bigendian, pevent_set_flag,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_print_field, pevent_print_fields,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_parse_event, pevent_parse_format,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_print_field, pevent_print_fields,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_parse_event, pevent_parse_format,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_find_any_field,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_find_any_field,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
the 'struct pevent_record' to 'struct
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
the pevent plugin related API.
Signed-off-by:
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
the 'struct pevent_record' to 'struct
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
the pevent plugin related API.
Signed-off-by:
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_alloc, pevent_free,
From: "Tzvetomir Stoyanov (VMware)"
In order to make libtraceevent into a proper library, variables, data
structures and functions require a unique prefix to prevent name space
conflicts. That prefix will be "tep_" and not "pevent_". This changes
APIs: pevent_alloc, pevent_free,
6a9405b56c274024564f9014bba97b92c91b34d6:
perf map: Optimize maps__fixup_overlappings() (2018-08-08 15:56:00 -0300)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-core-for-mingo-4.19-20180815
for you to fetch changes up to 6855dc41b24619c3d1de3dbd27dd0546b0e45272
6a9405b56c274024564f9014bba97b92c91b34d6:
perf map: Optimize maps__fixup_overlappings() (2018-08-08 15:56:00 -0300)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-core-for-mingo-4.19-20180815
for you to fetch changes up to 6855dc41b24619c3d1de3dbd27dd0546b0e45272
From: Sandipan Das
In some cases, a symbol may have multiple aliases. Attempting to add an
entry probe for such symbols results in a probe being added at an
incorrect location while it fails altogether for return probes. This is
only applicable for binaries with debug information.
During the
Replace the whole switch statement with a for loop.
This makes the code much clear and easy to read.
This also addresses the following Coverity warnings:
Addresses-Coverity-ID: 115090 ("Missing break in switch")
Addresses-Coverity-ID: 115091 ("Missing break in switch")
Addresses-Coverity-ID:
From: Sandipan Das
In some cases, a symbol may have multiple aliases. Attempting to add an
entry probe for such symbols results in a probe being added at an
incorrect location while it fails altogether for return probes. This is
only applicable for binaries with debug information.
During the
Replace the whole switch statement with a for loop.
This makes the code much clear and easy to read.
This also addresses the following Coverity warnings:
Addresses-Coverity-ID: 115090 ("Missing break in switch")
Addresses-Coverity-ID: 115091 ("Missing break in switch")
Addresses-Coverity-ID:
On 08/06/2018 06:39 PM, Patrick Bellasi wrote:
[...]
+/**
+ * uclamp_task_active: check if a task is currently clamping a CPU
+ * @p: the task to check
+ *
+ * A task actively affects the utilization clamp of a CPU if:
+ * - it's currently enqueued or running on that CPU
+ * - it's refcounted
On 08/06/2018 06:39 PM, Patrick Bellasi wrote:
[...]
+/**
+ * uclamp_task_active: check if a task is currently clamping a CPU
+ * @p: the task to check
+ *
+ * A task actively affects the utilization clamp of a CPU if:
+ * - it's currently enqueued or running on that CPU
+ * - it's refcounted
> From: Greg Kroah-Hartman
> Date: 2018年8月15日周三 上午8:15
> Subject: Re: [PATCH 4.14 000/104] 4.14.63-stable review
> To:
> Cc: , ,
> , , ,
> , ,
>
>
>
> On Tue, Aug 14, 2018 at 07:16:14PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.63 release.
>
> From: Greg Kroah-Hartman
> Date: 2018年8月15日周三 上午8:15
> Subject: Re: [PATCH 4.14 000/104] 4.14.63-stable review
> To:
> Cc: , ,
> , , ,
> , ,
>
>
>
> On Tue, Aug 14, 2018 at 07:16:14PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.63 release.
>
Em Wed, Aug 15, 2018 at 08:02:48PM +1000, Michael Ellerman escreveu:
> Jiri Olsa writes:
> > On Tue, Aug 14, 2018 at 03:06:44PM -0300, Arnaldo Carvalho de Melo wrote:
> >> Em Tue, Aug 14, 2018 at 09:27:26AM +0200, Jiri Olsa escreveu:
> >> > sry.. Arnaldo, would you change it for simple cd
Em Wed, Aug 15, 2018 at 08:02:48PM +1000, Michael Ellerman escreveu:
> Jiri Olsa writes:
> > On Tue, Aug 14, 2018 at 03:06:44PM -0300, Arnaldo Carvalho de Melo wrote:
> >> Em Tue, Aug 14, 2018 at 09:27:26AM +0200, Jiri Olsa escreveu:
> >> > sry.. Arnaldo, would you change it for simple cd
Em Wed, Aug 15, 2018 at 09:54:13AM -0400, Steven Rostedt escreveu:
> On Wed, 15 Aug 2018 09:04:59 +0200
> Jiri Olsa wrote:
>
> > On Tue, Aug 14, 2018 at 10:54:35PM -0400, Steven Rostedt wrote:
> > > On Fri, 10 Aug 2018 13:57:06 -0300
> > > Arnaldo Carvalho de Melo wrote:
> > >
> > > > >
Em Wed, Aug 15, 2018 at 09:54:13AM -0400, Steven Rostedt escreveu:
> On Wed, 15 Aug 2018 09:04:59 +0200
> Jiri Olsa wrote:
>
> > On Tue, Aug 14, 2018 at 10:54:35PM -0400, Steven Rostedt wrote:
> > > On Fri, 10 Aug 2018 13:57:06 -0300
> > > Arnaldo Carvalho de Melo wrote:
> > >
> > > > >
From: Oscar Salvador
We are getting the nid from the pages that are not yet removed,
but a node can only be offline when its memory/cpu's have been removed.
Therefore, we know that the node is still online.
Signed-off-by: Oscar Salvador
---
drivers/base/node.c | 2 --
1 file changed, 2
From: Oscar Salvador
unregister_mem_sect_under_nodes() tries to allocate a nodemask_t
in order to check whithin the loop which nodes have already been unlinked,
so we do not repeat the operation on them.
NODEMASK_ALLOC calls kmalloc() if NODES_SHIFT > 8, otherwise
it just declares a nodemask_t
From: Oscar Salvador
We are getting the nid from the pages that are not yet removed,
but a node can only be offline when its memory/cpu's have been removed.
Therefore, we know that the node is still online.
Signed-off-by: Oscar Salvador
---
drivers/base/node.c | 2 --
1 file changed, 2
From: Oscar Salvador
unregister_mem_sect_under_nodes() tries to allocate a nodemask_t
in order to check whithin the loop which nodes have already been unlinked,
so we do not repeat the operation on them.
NODEMASK_ALLOC calls kmalloc() if NODES_SHIFT > 8, otherwise
it just declares a nodemask_t
From: Oscar Salvador
v2 -> v3:
- NODEMASK_FREE can deal with NULL pointers, so do not
make it conditional (by David).
- Split up node_online's check patch (David's suggestion)
- Added Reviewed-by from Andrew and David
- Fix checkpath.pl warnings
This
From: Oscar Salvador
Before calling to unregister_mem_sect_under_nodes(),
remove_memory_section() already checks if we got a valid memory_block.
No need to check that again in unregister_mem_sect_under_nodes().
If more functions start using unregister_mem_sect_under_nodes() in the
future, we
From: Oscar Salvador
v2 -> v3:
- NODEMASK_FREE can deal with NULL pointers, so do not
make it conditional (by David).
- Split up node_online's check patch (David's suggestion)
- Added Reviewed-by from Andrew and David
- Fix checkpath.pl warnings
This
From: Oscar Salvador
Before calling to unregister_mem_sect_under_nodes(),
remove_memory_section() already checks if we got a valid memory_block.
No need to check that again in unregister_mem_sect_under_nodes().
If more functions start using unregister_mem_sect_under_nodes() in the
future, we
From: Oscar Salvador
unregister_memory_section() calls remove_memory_section()
with three arguments:
* node_id
* section
* phys_device
Neither node_id nor phys_device are used.
Let us drop them from the function.
Signed-off-by: Oscar Salvador
Reviewed-by: David Hildenbrand
Reviewed-by:
From: Oscar Salvador
unregister_memory_section() calls remove_memory_section()
with three arguments:
* node_id
* section
* phys_device
Neither node_id nor phys_device are used.
Let us drop them from the function.
Signed-off-by: Oscar Salvador
Reviewed-by: David Hildenbrand
Reviewed-by:
On Wed, Aug 15, 2018 at 05:28:56PM +0300, Kirill Kapranov wrote:
> On 08/14/2018 05:18 PM, Mark Brown wrote:
> > Is this something that's actually happened for you?
> Yes, I observed it.
OK, that's useful to know - it differentiates between a nice to have fix
and something that should be sent to
On Wed, Aug 15, 2018 at 05:28:56PM +0300, Kirill Kapranov wrote:
> On 08/14/2018 05:18 PM, Mark Brown wrote:
> > Is this something that's actually happened for you?
> Yes, I observed it.
OK, that's useful to know - it differentiates between a nice to have fix
and something that should be sent to
On Wed, Aug 15, 2018 at 02:05:35PM +, Pavel Tatashin wrote:
> > This tries to fix [1], which was reported by David Hildenbrand, and also
> > does some cleanups/refactoring.
>
> Hi Oscar,
>
> I would like to review this work. Are you in process of sending a new
> version? If so, I will wait
On Wed, Aug 15, 2018 at 02:05:35PM +, Pavel Tatashin wrote:
> > This tries to fix [1], which was reported by David Hildenbrand, and also
> > does some cleanups/refactoring.
>
> Hi Oscar,
>
> I would like to review this work. Are you in process of sending a new
> version? If so, I will wait
On 08/14/2018 05:18 PM, Mark Brown wrote:
> Is this something that's actually happened for you?
Yes, I observed it.
Background:
The platform: fitlet2 [1] , CPU Intel(R) Celeron(R) CPU J3455 @ 1.50GHz.
On an extension board there are three SPI master controllers "Intel
Corporation
On 08/14/2018 05:18 PM, Mark Brown wrote:
> Is this something that's actually happened for you?
Yes, I observed it.
Background:
The platform: fitlet2 [1] , CPU Intel(R) Celeron(R) CPU J3455 @ 1.50GHz.
On an extension board there are three SPI master controllers "Intel
Corporation
As preparation for teaching an old dog a few new tricks.
Signed-off-by: Rasmus Villemoes
---
scripts/basic/fixdep.c | 21 ++---
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/scripts/basic/fixdep.c b/scripts/basic/fixdep.c
index 850966f3d602..666041841200 100644
Instead of having to spawn an 'rm' instance to remove the depfile after
processing, let the fixdep program itself do that. For debugging, it's
nice to not do it unconditionally.
Note that the fixdep calls from Makefiles are done under 'set -e', so
this also preserves the behaviour of keeping the
Avoid spawning one more process per TU by having fixdep open the tmpfile
and rename to its final name.
The only change in behaviour is that if fixdep fails, the tmpfile we
leave behind is $(dot-target).cmd.tmp rather than $(dot-target).tmp .
Signed-off-by: Rasmus Villemoes
---
Instead of having to spawn an 'rm' instance to remove the depfile after
processing, let the fixdep program itself do that. For debugging, it's
nice to not do it unconditionally.
Note that the fixdep calls from Makefiles are done under 'set -e', so
this also preserves the behaviour of keeping the
Avoid spawning one more process per TU by having fixdep open the tmpfile
and rename to its final name.
The only change in behaviour is that if fixdep fails, the tmpfile we
leave behind is $(dot-target).cmd.tmp rather than $(dot-target).tmp .
Signed-off-by: Rasmus Villemoes
---
As preparation for teaching an old dog a few new tricks.
Signed-off-by: Rasmus Villemoes
---
scripts/basic/fixdep.c | 21 ++---
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/scripts/basic/fixdep.c b/scripts/basic/fixdep.c
index 850966f3d602..666041841200 100644
These patches eliminate two (albeit tiny and shortlived) processes
from the cmd_and_fixdep rule, i.e. from every TU being
compiled. Whether the diffstat below is worth it I'll leave to Kbuild
maintainers to decide.
Rasmus Villemoes (3):
Kbuild: refactor fixdep to use getopt()
Kbuild: teach
These patches eliminate two (albeit tiny and shortlived) processes
from the cmd_and_fixdep rule, i.e. from every TU being
compiled. Whether the diffstat below is worth it I'll leave to Kbuild
maintainers to decide.
Rasmus Villemoes (3):
Kbuild: refactor fixdep to use getopt()
Kbuild: teach
On Wed, 2018-08-15 at 14:28 +0200, Krzysztof Kozlowski wrote:
> Hi,
>
> Bisect pointed commit ce3147990450a68b3f549088b30f087742a08b5d
> ("fs/locks: allow a lock request to block other requests.") to failure
> boot of NFSv4 with root on several boards.
>
> Log is here:
>
On Wed, 2018-08-15 at 14:28 +0200, Krzysztof Kozlowski wrote:
> Hi,
>
> Bisect pointed commit ce3147990450a68b3f549088b30f087742a08b5d
> ("fs/locks: allow a lock request to block other requests.") to failure
> boot of NFSv4 with root on several boards.
>
> Log is here:
>
On 30/07/18 05:45, Jisheng Zhang wrote:
> Add this hook so that it can be overridden with driver specific
> implementations. We also rename the original sdhci_adma_write_desc()
> to _sdhci_adma_write_desc() and export it, so that it could be reused
> by driver's specific implementations.
>
>
On 30/07/18 05:45, Jisheng Zhang wrote:
> Add this hook so that it can be overridden with driver specific
> implementations. We also rename the original sdhci_adma_write_desc()
> to _sdhci_adma_write_desc() and export it, so that it could be reused
> by driver's specific implementations.
>
>
> This tries to fix [1], which was reported by David Hildenbrand, and also
> does some cleanups/refactoring.
Hi Oscar,
I would like to review this work. Are you in process of sending a new version?
If so, I will wait for it.
Thank you,
Pavel
>
> I am sending this as RFC to see if the
> This tries to fix [1], which was reported by David Hildenbrand, and also
> does some cleanups/refactoring.
Hi Oscar,
I would like to review this work. Are you in process of sending a new version?
If so, I will wait for it.
Thank you,
Pavel
>
> I am sending this as RFC to see if the
On Wed, 15 Aug 2018 09:04:59 +0200
Jiri Olsa wrote:
> On Tue, Aug 14, 2018 at 10:54:35PM -0400, Steven Rostedt wrote:
> > On Fri, 10 Aug 2018 13:57:06 -0300
> > Arnaldo Carvalho de Melo wrote:
> >
> > > > Arnaldo takes care of that, but I guess pulling from branch is the
> > > > prefered
On Wed, 15 Aug 2018 09:04:59 +0200
Jiri Olsa wrote:
> On Tue, Aug 14, 2018 at 10:54:35PM -0400, Steven Rostedt wrote:
> > On Fri, 10 Aug 2018 13:57:06 -0300
> > Arnaldo Carvalho de Melo wrote:
> >
> > > > Arnaldo takes care of that, but I guess pulling from branch is the
> > > > prefered
[working on V2 with your feedback]
On Tue, Aug 14, 2018 at 12:04:33PM -0400, Steven Rostedt wrote:
> On Tue, 14 Aug 2018 09:33:52 +0100
> Julien Thierry wrote:
> > >> Shouldn't this be an error? The option -fpatchable-function-entry has
> > >> been added to the CC_FLAGS_FTRACE, so any call to
[working on V2 with your feedback]
On Tue, Aug 14, 2018 at 12:04:33PM -0400, Steven Rostedt wrote:
> On Tue, 14 Aug 2018 09:33:52 +0100
> Julien Thierry wrote:
> > >> Shouldn't this be an error? The option -fpatchable-function-entry has
> > >> been added to the CC_FLAGS_FTRACE, so any call to
601 - 700 of 890 matches
Mail list logo
