Hello,
On Mon, Nov 23, 2015, at 18:42, Dave Watson wrote:
> An approach for a kernel TLS socket.
>
> Only the symmetric encryption / decryption is done in-kernel, as well
> as minimal framing handling. The handshake is kept in userspace, and
> the negotiated cipher / keys / IVs are then set on
On Sun, Nov 22, 2015 at 09:57:42AM -0800, Christoph Hellwig wrote:
> Thanks, this looks good. I should have add the const from the start.
>
> Reviewed-by: Christoph Hellwig
Thanks, applying for 4.5.--b.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Mon, Nov 23, 2015 at 03:48:58PM +0100, Pali Rohár wrote:
> On Saturday 21 November 2015 15:16:15 Gabriele Mazzotta wrote:
> > Some BIOSes unconditionally send an ACPI notification to RBTN when the
> > system is resuming from suspend. This makes dell-rbtn send an input
> > event to userspace as
Hello Guenter,
On Sun, Nov 22, 2015 at 07:20:59PM -0800, Guenter Roeck wrote:
> diff --git a/include/linux/watchdog.h b/include/linux/watchdog.h
> index b535b02b1d7f..f0292d56caf0 100644
> --- a/include/linux/watchdog.h
> +++ b/include/linux/watchdog.h
> @@ -108,6 +108,7 @@ struct watchdog_device
On (11/23/15 09:43), Dave Watson wrote:
> Currently gcm(aes) represents ~80% of our SSL connections.
>
> Userspace interface:
>
> 1) A transform and op socket are created using the userspace crypto interface
> 2) Setsockopt ALG_SET_AUTHSIZE is called
> 3) Setsockopt ALG_SET_KEY is called twice,
On Monday 23 November 2015 09:25:38 Dan Williams wrote:
>
> If we had an "static inline ahci_irq_vector(int port)" helper to
> compile out the struct msix_entry de-reference would that be
> sufficient?
Yes, that is probably a nicer way to do it. We should then also do
something like this:
@@
On 11/18/2015 07:25 AM, Petr Mladek wrote:
> Kthreads are currently implemented as an infinite loop. Each
> has its own variant of checks for terminating, freezing,
> awakening. In many cases it is unclear to say in which state
> it is and sometimes it is done a wrong way.
>
> The plan is to
From: Markus Elfring
Date: Mon, 23 Nov 2015 20:33:59 +0100
Another update suggestion was taken into account after a patch was applied
from static source code analysis.
Markus Elfring (2):
Delete an unnecessary check before the function call "rbd_dev_destroy"
From: Markus Elfring
Date: Mon, 23 Nov 2015 20:16:45 +0100
The rbd_dev_destroy() function tests whether its argument is NULL
and then returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
From: Markus Elfring
Date: Mon, 23 Nov 2015 20:22:41 +0100
The rbd_dev_destroy() function was called in two cases by the
rbd_dev_probe_parent() function during error handling even if
the passed variable contained a null pointer.
* This implementation detail could
On Fri 20 Nov 17:49 PST 2015, Stephen Boyd wrote:
> Add the generic compatible strings for the PMIC gpio and MPP
> modules found on qcom based PMICs.
>
> Cc:
> Cc: "Ivan T. Ivanov"
> Cc: Bjorn Andersson
> Cc: Rob
Add documentation and usage examples for 'hist' triggers.
Signed-off-by: Tom Zanussi
Tested-by: Masami Hiramatsu
---
Documentation/trace/events.txt | 1155
1 file changed, 1155 insertions(+)
Enable the on-chip audio codec
Signed-off-by: Stefan Monnier
---
arch/arm/boot/dts/sun7i-a20-orangepi-mini.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/sun7i-a20-orangepi-mini.dts
b/arch/arm/boot/dts/sun7i-a20-orangepi-mini.dts
index
On Sat, Nov 21, 2015 at 01:49:06PM +0200, Vassilis Virvilis wrote:
> On 11/20/2015 02:23 PM, Juergen Gross wrote:
> >On 20/11/15 11:04, vas...@iit.demokritos.gr wrote:
> >>>I've just found a potential issue: In case MTRR is disabled by the BIOS
> >>>the PAT register of the boot processor won't be
On 11/23/2015 01:00 PM, Mark Brown wrote:
On Mon, Nov 23, 2015 at 11:40:55AM -0600, Andrew F. Davis wrote:
But which of_node?
regulator_config->of_node
regulator_config->dev->of_node
The second is the only one I see getting used, the first is only
used when drivers provide their own
On Monday 23 November 2015 11:09:50 Andrew F. Davis wrote:
> On 11/23/2015 10:57 AM, Arnd Bergmann wrote:
> > On Monday 23 November 2015 10:53:51 Andrew F. Davis wrote:
> >> Separate out I2C functionality into a module. This fixes several small
> >> issues and simplifies the driver initialization.
On Monday 23 November 2015 17:22:03 Russell King - ARM Linux wrote:
> On Mon, Nov 23, 2015 at 05:52:38PM +0100, Arnd Bergmann wrote:
> > On Monday 23 November 2015 16:37:50 Russell King - ARM Linux wrote:
> > > Does that not depend on the architectures BUG() implementation? If an
> > >
On Mon, Nov 23, 2015 at 01:00:59PM +0300, Vladimir Davydov wrote:
> I've another question regarding this socket_work: its reclaim target
> always equals CHARGE_BATCH. Can't it result in a workload exceeding
> memory.high in case there are a lot of allocations coming from different
> cpus? In this
Hi folks,
Any more comments on this patch (store immediate only)?
I need more time to add XADD (I'm supposed everyone agrees it is
equivalent to atomic_add). However, this one is irrelevant to XADD, so
we may be able to apply it first?
Thanks,
Yang
On 11/12/2015 7:45 PM, Z Lim wrote:
On
From: Gustavo Padovan
- remove sw_sync, it is used only for testing/debugging and should not
be upstreamed.
- port sw_sync testcases to use debugfs somehow
- clean up and ABI check for security issues
- move the sync framework to drivers/base/dma-buf
Cc:
This is v12 of the 'hist triggers' patchset, incorporating suggestions
and fixing problems pointed out by Namhyung.
Changes from v11:
- Added tracing_map_lookup().
- Changed tracing_map_insert() to incorporate the hits/drops counter
updating. The changes allow clients to continue
Make is_string_field() and is_function_field() accessible outside of
trace_event_filters.c for other users of ftrace_event_fields.
Signed-off-by: Tom Zanussi
Reviewed-by: Masami Hiramatsu
Tested-by: Masami Hiramatsu
Named triggers are sets of triggers that share a common set of trigger
data. An example of functionality that could benefit from this type
of capability would be a set of inlined probes that would each
contribute event counts, for example, to a shared counter data
structure.
The first named
On Mon, Nov 23, 2015 at 01:50:17PM -0500, Stefan Monnier wrote:
> Enable the on-chip audio codec
>
> Signed-off-by: Stefan Monnier
Applied both, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
Similar to enable_event/disable_event triggers, these triggers enable
and disable the aggregation of events into maps rather than enabling
and disabling their writing into the trace buffer.
They can be used to automatically start and stop hist triggers based
on a matching filter condition.
If
From: Namhyung Kim
Allow users to have numeric fields displayed as log2 values in case
value range is very wide by appending '.log2' to field names.
For example,
# echo 'hist:key=bytes_req' > kmalloc/trigger
# cat kmalloc/hist
{ bytes_req:504 } hitcount:
Allow users to have syscall id fields displayed as syscall names in
the output by appending '.syscall' to field names:
# echo hist:keys=aaa.syscall ... \
[ if filter] > event/trigger
Signed-off-by: Tom Zanussi
Tested-by: Masami Hiramatsu
From: Namhyung Kim
The string in a trace event is usually recorded as dynamic array which
is variable length. But current hist code only support fixed length
array so it cannot support most strings.
This patch fixes it by checking filter_type of the field and get
proper
If we assume the maximum size for a string field, we don't have to
worry about its position. Since we only allow two keys in a compound
key and having more than one string key in a given compound key
doesn't make much sense anyway, trading a bit of extra space instead
of introducing an arbitrary
Almost all callers of the set_cpu_* functions pass an explicit true
or false. Making them static inline thus replaces the function calls
with a simple set_bit/clear_bit, saving some .text.
Acked-by: Rusty Russell
Signed-off-by: Rasmus Villemoes
Allow users to append 'pause' or 'continue' to an existing trigger in
order to have it paused or to have a paused trace continue.
This expands the hist trigger syntax from this:
# echo hist:keys=xxx:vals=yyy:sort=zzz.descending \
[ if filter] >> event/trigger
to this:
# echo
Allow users to have address fields displayed as symbols in the output
by appending '.sym' or 'sym-offset' to field names:
# echo hist:keys=aaa.sym,bbb.sym-offset ... \
[ if filter] > event/trigger
Signed-off-by: Tom Zanussi
Tested-by: Masami
Allow users to define any number of hist triggers per trace event.
Any number of hist triggers may be added for a given event, which may
differ by key, value, or filter.
Reading the event's 'hist' file will display the output of all the
hist triggers defined on an event concatenated in the order
On Mon, Nov 23, 2015 at 05:56:44PM +, Javi Merino wrote:
> I've tested this series on Juno (2xCortex-A57 4xCortex-A53). If you
> idle inject for 50% of the time, when I run 6 busy loops the scheduler
> sometimes keeps two of them in the same cpu while the another cpu is
> completely idle.
On Mon 23 Nov 01:29 PST 2015, Stanimir Varbanov wrote:
> From: Stanimir Varbanov
>
> Document Qualcomm PCIe driver devicetree bindings.
>
> Signed-off-by: Stanimir Varbanov
> Signed-off-by: Stanimir Varbanov
> ---
>
On 11/23/2015 8:54 AM, Murali Karicheri wrote:
Currently kernel crash randomly when K2L EVM is booted without
clk_ignore_unused in the bootargs. This workaround is not needed
on other K2 devices such as K2HK and K2E and with this fix, we can
remove the workaround altogether. netcp driver on K2L
On Wed 18 Nov 11:33 PST 2015, Stephen Boyd wrote:
> The number of interrupts is always equal to the number of pins
> provided by the PMIC gpio and MPP hardware blocks. Count the
> number of irqs to figure out the number of pins instead of adding
> more compatible strings or doing math on the reg
On 22/11/15 14:17, Simon Arlott wrote:
> The BCM63268 has a NAND interrupt register with combined status and enable
> registers. It also has a clock for the NAND controller that needs to be
> enabled.
>
> Set up the device by enabling the clock, disabling and acking all
> interrupts, then handle
Hello Guenter,
On Mon, Nov 23, 2015 at 08:14:56AM -0800, Guenter Roeck wrote:
> On 11/22/2015 11:53 PM, Uwe Kleine-König wrote:
> >On Sun, Nov 22, 2015 at 07:20:58PM -0800, Guenter Roeck wrote:
> >>@@ -160,7 +176,11 @@ they are supported. These optional routines/operations
> >>are:
> >>and
On Tue 17 Nov 16:35 PST 2015, Stephen Boyd wrote:
> From: Joonwoo Park
>
> Add initial pinctrl driver to support pin configuration with
> pinctrl framework for msm8996.
>
> Cc:
> Cc: Bjorn Andersson
>
On 23/11/15 07:02, Jonas Gorski wrote:
> Hi,
>
> On Sun, Nov 22, 2015 at 3:07 PM, Simon Arlott wrote:
>> Instead of using a fixed clock HZ in the driver, obtain it from the
>> "periph" clk that the watchdog timer uses.
>>
>> Signed-off-by: Simon Arlott
>>
Hi Linus,
Could you please pull the following update for 4.4-rc3.
thanks,
-- Shuah
--
The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
are available in
Adding a source operation to build a tracer's configuration from
a perf_event. That way possibly complex parsing of the information
conveyed by the event doesn't have to be carried out every time
the configuration is needed.
Since event configuration can change between concurrent sessions,
the
I haven't received much in terms of comments from this iteration.
Even if all comments from previous posts have been addressed it would
feel better to have a few "Reviewed-by:" before adding this to my
tree.
This patchset aims to integrate configuration and control of
the Coresight tracers with
Moving PM runtime operations in Coresight devices enable() and
disable() API to the framework core when a path is setup. That
way the runtime core doesn't have to be involved everytime a
path is enabled. It also avoids calling runtime PM operations
in IRQ context.
Signed-off-by: Mathieu Poirier
Changing default configuration to include the entire address
range rather than just the kernel. That way traces are more
inclusive and it is easier to narrow down if needed.
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/coresight-etm.h | 2 ++
For memory allocation purposes, code located in other places
then util/cpumap.c may want to know how many CPUs the system has.
This patch is making function set_max_cpu_num() available to
other parts of the perf tool so that global variable
@max_cpu_num gets the right value when referenced by
Adding a new section giving information on how coresight has been
integrated with the perf subsystem along with a general idea of how
to control tracing from the perf tool cmd line.
Signed-off-by: Mathieu Poirier
---
Documentation/trace/coresight.txt | 138
Adding the required mechanic allowing 'perf list pmu' to
discover coresight ETM/PTM tracers.
Signed-off-by: Mathieu Poirier
---
MAINTAINERS| 1 +
tools/perf/arch/arm/util/Build | 2 ++
tools/perf/arch/arm/util/pmu.c | 34
Adding new mode to limit tracing to kernel or user space.
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/coresight-etm.h| 7 ++-
.../hwtracing/coresight/coresight-etm3x-sysfs.c| 4 ++
drivers/hwtracing/coresight/coresight-etm3x.c |
There is really no point in having two functions to take care
of doing the initials tracer configuration. As such moving
everything to 'etm_set_default()'.
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/coresight-etm3x.c | 37
On 19/11/15 21:05, Kevin Hilman wrote:
On Fri, Nov 13, 2015 at 7:59 AM, Kevin Hilman wrote:
Eddie Huang writes:
If enable Mediatek 8173 SoC, it should also enable power domain
driver. Otherwise access clk subsystem register will fail.
On 11/23/2015 05:40 PM, Sudip Mukherjee wrote:
On Mon, Nov 23, 2015 at 04:13:39PM +0100, Matias Bjørling wrote:
On 11/23/2015 11:35 AM, Sudip Mukherjee wrote:
If copy_to_user() fails we returned error but we missed releasing
devices.
Signed-off-by: Sudip Mukherjee
---
When using the Coresight framework from the sysFS interface a
tracer is always handling a single session and as such, a path
can be associated with a tracer. But when supporting multiple
session per tracer there is no guarantee that sessions will always
have the same path from source to sink.
On 23/11/15 17:45, Jitendra Kumar Khasdev wrote:
This patch is to comedilib.h file that fixes up following warnings
reported by checkpatch.pl :
I) Block comments use * on subsequent lines
Signed-off-by: Jitendra Kumar Khasdev
---
drivers/staging/comedi/comedilib.h | 32
Adding a new mode to source API enable() in order to
distinguish where the request comes from. That way it is
possible to perform different operations based on where
the request was issued from.
The ETM4x driver is also modified to keep in sync with the
new interface.
Signed-off-by: Mathieu
On 11/23/2015 12:29 AM, Peter Chen wrote:
> On Fri, Nov 20, 2015 at 03:47:20PM -0800, Tim Bird wrote:
>> Register the chipidea driver with the phy, so that the phy
>> driver can kick the gadget driver when it resumes from low power.
>> The phy-msm-usb (Qualcomm) driver requires this in order to
On Mon, Nov 23, 2015 at 4:28 AM, Sinan Kaya wrote:
> The Qualcomm Technologies HIDMA device has been designed
> to support virtualization technology. The driver has been
> divided into two to follow the hardware design.
>
> 1. HIDMA Management driver
> 2. HIDMA Channel
Hi Saurab,
On Mon, Nov 23, 2015 at 5:15 PM, Saurabh Sengar wrote:
> use of_property_read_u8() for u8 values
Why are you making this change?
Have you tested this?
drivers/of/base.c says
* dts entry of array should be like:
* property = /bits/ 8 <0x50
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly.
Signed-off-by: Nizam Haider
---
drivers/staging/iio/frequency/ad9832.c | 2 +-
drivers/staging/iio/frequency/ad9834.c | 2 +-
2 files changed, 2 insertions(+), 2
On Mon, Nov 23, 2015 at 12:36:46PM +0300, Vladimir Davydov wrote:
> On Fri, Nov 20, 2015 at 01:56:48PM -0500, Johannes Weiner wrote:
> > I actually had all this at first, but then wondered if it makes more
> > sense to keep the legacy code in isolation. Don't you think it would
> > be easier to
On Tue 17 Nov 17:00 PST 2015, Stephen Boyd wrote:
> The drivers don't really need to know which PMIC they're for, so
> make a generic binding for them. This alleviates us from updating
> the drivers every time a new PMIC comes out. It's still
> recommended that we update the binding with new PMIC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/21/2015 01:36 PM, Vladimir Zapolskiy wrote:
> On 21.11.2015 06:40, Cory Tusar wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 11/19/2015 12:50 AM, Vladimir Zapolskiy wrote:
>>> Hi Cory,
>>>
>>> On 19.11.2015 05:29, Cory Tusar
On Tue 17 Nov 16:52 PST 2015, Stephen Boyd wrote:
> Update the driver and binding for pm8994-mpp devices.
>
> Cc:
> Cc: "Ivan T. Ivanov"
> Cc: Bjorn Andersson
> Signed-off-by: Stephen Boyd
>
On Tue 17 Nov 16:52 PST 2015, Stephen Boyd wrote:
> Update the binding and driver for pm8994-gpio devices.
>
> Cc:
> Cc: "Ivan T. Ivanov"
> Cc: Bjorn Andersson
> Signed-off-by: Stephen Boyd
Coresight ETMs are IP blocks used to perform HW assisted tracing
on a CPU core. This patch introduce the required auxiliary API
functions allowing the perf core to interact with a tracer.
Signed-off-by: Mathieu Poirier
---
MAINTAINERS | 3 +
Perf is a well known and used tool for performance monitoring
and much more. A such it is an ideal candidate for integration
with coresight based HW tracing.
This patch introduces a PMU that represent a coresight tracer to
the Perf core.
Signed-off-by: Mathieu Poirier
On some architecture the size of the private header may
be dependent on the number of tracers used in the session. As
such adding a "struct perf_session" parameter, which should
contain all the required information.
Also adjusting the existing client of the interface to take
the new parameter
TraceID values have to be unique for all tracers and
consistent between drivers and user space. As such
introducing a central function to be used whenever a
traceID value is required.
The patch also account for data traceIDs, which are usually
I(N) + 1.
Signed-off-by: Mathieu Poirier
For Coresight ETMv3/4 tracers the event carries information
about trace modes such as user or kernel space tracing and
whether tracing is allowed when operating in secure mode.
Since this information is to be embedded in the private
structure returned by setup_aux(), changing the first
parameter
Adding an ETB10 specific AUX area operations to be used
by the perf framework when events are initialised.
Part of this operation involves modeling the mmap'ed area
based on the specific ways a sink buffer gathers information.
Signed-off-by: Mathieu Poirier
---
Adding an operation mode to sink->enable() API in order
to prevent simultaneous access from different callers.
TPIU and TMC won't be supplemented with the AUX area
API immediately and as such ignore the new mode.
Signed-off-by: Mathieu Poirier
---
That way traces can be enabled and disabled automatically
from the Perf subystem using the PMU abstraction.
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/coresight-etm3x.c | 47 ---
1 file changed, 43 insertions(+), 4
Moving to use local atomic operations to take advantage of the
lockless implementation, something that will come handy when
the ETB is accessed from the Perf subsystem. Also changing the
name of the variable to something more meaningful.
Signed-off-by: Mathieu Poirier
Thanks, queued for next release.
-corey
On 11/19/2015 06:24 PM, Dave Jones wrote:
> We call cleanup_one_si from ipmi_pci_remove, which calls
> ->addr_source_cleanup,
> which gets set to point to ipmi_pci_cleanup, which does a pci_disable_device.
>
> On return from this, we do a second
There is no need to use the event enable's "always false" event to
stop trace collection. For that purpose setting the programming bit
(ETMCR:10) is enough.
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/coresight-etm3x.c | 3 ---
1 file changed, 3
On 23/11/15 15:42, Jonas Gorski wrote:
> On Sun, Nov 22, 2015 at 11:17 PM, Simon Arlott wrote:
>> + priv->clk = of_clk_get(dev->of_node, 0);
>
>
> Why not use a named clock here? That way you can make use of
> devm_clk_get and don't need to care about putting it.
Ok.
Add an API allowing external code to quickly get a handle on the
sink within a path. The sink is always last, but adding an API allows
to keep the path's node structure private and remove redundant checks.
Signed-off-by: Mathieu Poirier
---
Calling function 'smp_call_function_single()' to unlock a
tracer and calling it again right after to perform the
default initialisation doesn't make sense.
Moving 'etm_os_unlock()' just before making the default
initialisation results in the same outcome while saving
one call to
Other than plainly parsing the device tree there is no way to
know which CPU a tracer is affined to. As such adding an
interface to lookup the CPU field enclosed in the etm_drvdata
structure that was initialised at boot time.
Signed-off-by: Mathieu Poirier
---
SysFS entries are big enough to justify their own file.
As such moving all sysFS related declarations to a dedicated
location.
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/Makefile |3 +-
drivers/hwtracing/coresight/coresight-etm.h
Structure "etm_drvdata" carries the tracer's static configuration
(as laid out in hardware) and the session specific configuration
determined by users. This doesn't work when tracers are to support
multiple, simultaneous, tracing session.
As such splitting "etm_drvdata" in two sections, one for
Moving functions etm_readl/writel to file "coresight-etm.h"
so that the main ETM3x driver can be split in more than one
file.
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/coresight-etm.h | 29 +++
Allow users to define 'named' hist triggers. All triggers created
with the same 'name=xxx' option will update the same shared histogram
data.
This expands the hist trigger syntax from this:
# echo hist:keys=xxx ... [ if filter] > event/trigger
to this:
# echo hist:name=xxx:keys=xxx
Allow users to have numeric fields displayed as hex values in the
output by appending '.hex' to field names:
# echo hist:keys=aaa,bbb.hex:vals=ccc.hex ... \
[ if filter] > event/trigger
Signed-off-by: Tom Zanussi
Tested-by: Masami Hiramatsu
It's often useful to be able to use a stacktrace as a hash key, for
keeping a count of the number of times a particular call path resulted
in a trace event, for instance. Add a special key named 'stacktrace'
which can be used as key in a 'keys=' param for this purpose:
# echo
A css_set represents the relationship between a set of tasks and
css's. css_set never pinned the associated css's. This was okay
because tasks used to always disassociate immediately (in RCU sense) -
either a task is moved to a different css_set or exits and never
accesses css_set again.
From: Masami Hiramatsu
Add the hist trigger testcases for ftracetest.
This checks the basic histogram trigger behaviors like as;
- Histogram trigger itself
- Histogram with string key
- Histogram with compound keys
- Histogram with sort key
- Histogram
Allow users to specify keys and/or values to sort on. With this
addition, keys and values specified using the 'keys=' and 'vals='
keywords can be used to sort the hist trigger output via a new 'sort='
keyword. If multiple sort keys are specified, the output will be
sorted using the second key as
From: Masami Hiramatsu
This adds simple event trigger testcases for ftracetest,
which covers following triggers.
- traceon-traceoff trigger
- enable/disable_event trigger
- snapshot trigger
- stacktrace trigger
- trigger filters
Here is the test result.
Allow users to specify multiple trace event fields to use in keys by
allowing multiple fields in the 'keys=' keyword. With this addition,
any unique combination of any of the fields named in the 'keys'
keyword will result in a new entry being added to the hash table.
Signed-off-by: Tom Zanussi
Allow users to have common_pid field values displayed as program names
in the output by appending '.execname' to a common_pid field name:
# echo hist:keys=common_pid.execname ... \
[ if filter] > event/trigger
Signed-off-by: Tom Zanussi
Tested-by:
Hello,
On Mon, Nov 23, 2015 at 10:53:46AM -0500, Tejun Heo wrote:
> > [ 11.594536] [ cut here ]
> > [ 11.595274] WARNING: CPU: 1 PID: 1 at kernel/cgroup_pids.c:97
> > pids_cancel.constprop.6+0x31/0x40()
> > [ 11.595958] Modules linked in:
> > [ 11.596199] CPU: 1
Allow users to append 'clear' to an existing trigger in order to have
the hash table cleared.
This expands the hist trigger syntax from this:
# echo hist:keys=xxx:vals=yyy:sort=zzz.descending:pause/cont \
[ if filter] >> event/trigger
to this:
# echo
Add a new needs_rec flag for triggers that require unconditional
access to trace records in order to function.
Normally a trigger requires access to the contents of a trace record
only if it has a filter associated with it (since filters need the
contents of a record in order to make a filtering
Some triggers may need access to the trace event, so pass it in. Also
fix up the existing trigger funcs and their callers.
Signed-off-by: Tom Zanussi
Tested-by: Masami Hiramatsu
---
include/linux/trace_events.h| 7 ---
Allow users to specify trace event fields to use in aggregated sums
via a new 'vals=' keyword. Before this addition, the only aggregated
sum supported was the implied value 'hitcount'. With this addition,
'hitcount' is also supported as an explicit value field, as is any
numeric trace event
Exporting the cpumasks __cpu_possible_mask and friends will allow us
to remove the extra indirection through the cpu_*_mask variables. It
will also allow the set_cpu_* functions to become static inlines,
which will give a .text reduction.
Acked-by: Rusty Russell
'hist' triggers allow users to continually aggregate trace events,
which can then be viewed afterwards by simply reading a 'hist' file
containing the aggregation in a human-readable format.
The basic idea is very simple and boils down to a mechanism whereby
trace events, rather than being
Hi Michal,
On 11/23/2015 02:05 AM, Michal Simek wrote:
> All these tests looks very interesting. Do you have any any
> work-in-progress repo with other tests? It will be good to run all of
> them to validate our drivers.
I haven't upstreamed these yet, but I plan to do so soon, along with
tty
1 - 100 of 2144 matches
Mail list logo