On Fri, 26 Feb 2016, Rafał Miłecki wrote:
> >> KSEG0ADDR was translating 0x1c00 into 0x9c00. With
> >> ioremap_cachable we use MIPS's __ioremap (and remap_area_pages). This
> >> results in different address (e.g. 0xc008) but it still should be
> >> cached as expected and it was success
On Fri, 2016-02-26 at 13:20 +0200, Heikki Krogerus wrote:
> Since device_add_property_set() now always takes a copy of
> the property_set, and also since the fwnode type is always
> hard coded to be FWNODE_PDATA, there is no need for the
> drivers to deliver the entire struct property_set. The
> fu
The problem that makes us use wrappers is that some compat
architectures allows user code to access top halves of registers.
This is not a problem for syscalls that are already handled by compat
code, or for that who has types of the same size in kernel and
userspace. In case of s390 and lp64/ilp32
Signed-off-by: Yury Norov
---
Documentation/adding-syscalls.txt | 32
1 file changed, 32 insertions(+)
diff --git a/Documentation/adding-syscalls.txt
b/Documentation/adding-syscalls.txt
index cc2d4ac..d02a6bd 100644
--- a/Documentation/adding-syscalls.txt
+++ b/
Signed-off-by: Yury Norov
---
arch/Kconfig | 4
arch/s390/Kconfig | 1 +
2 files changed, 5 insertions(+)
diff --git a/arch/Kconfig b/arch/Kconfig
index f6b649d..6393093 100644
--- a/arch/Kconfig
+++ b/arch/Kconfig
@@ -583,6 +583,10 @@ config HAVE_COPY_THREAD_TLS
normal C par
Hi Boris,
On 26/02/16 00:57, Boris Brezillon wrote:
The mtd_ooblayout_xxx() helper functions have been added to avoid direct
accesses to the ecclayout field, and thus ease for future reworks.
Use these helpers in all places where the oobfree[] and eccpos[] arrays
where directly accessed.
Signed
This patch moves required code to generic files to let other arches use
it if needed. Here also, additional code is introduced, as s390 uses asm
syscall tables, while in general case, wrappers may be used in C code.
__SC_COMPAT_CAST for s390 is too specific due to 31-bit pointer length, so it's
mo
S390-specific wrappers are moved to arch/s390/kernel/compat_linux.c
Some syscalls are declared conditionally, so corresponding wrappers
are conditional accordingly.
Signed-off-by: Yury Norov
---
arch/s390/kernel/Makefile | 2 +-
arch/s390/kernel/compat_linux.c | 4 +
arch/s390/ker
As generic unistd syscall table is written in C, syscall
prototypes declaration is needed. It's added to compat header.
Signed-off-by: Yury Norov
---
include/linux/compat.h| 225 +
include/uapi/asm-generic/unistd.h | 227 +++
On Fri, Feb 26, 2016 at 8:51 AM, Boris Ostrovsky
wrote:
> On 02/26/2016 05:53 AM, Roger Pau Monné wrote:
>>
>> El 25/2/16 a les 16:16, Boris Ostrovsky ha escrit:
>>>
>>> PV guests need to have their .bss zeroed out since it is not guaranteed
>>> to be cleared by Xen's domain builder
>>
>> I guess
On Tue, Jan 26, 2016 at 06:14:29PM -0500, Wan Zongshun wrote:
> Suravee Suthikulpanit (3):
> iommu/amd: Modify ivhd_header structure to support type 11h and 40h
> iommu/amd: Use the most comprehensive IVHD type that the driver can
> support
> iommu/amd: Introduces ivrs_acpihid kernel para
On 26/02/16 14:28, Stefano Stabellini wrote:
> On Thu, 25 Feb 2016, Stefano Stabellini wrote:
>> Hi all,
>>
>> this series exports xenboot on ARM and ARM64 as earlycon, and gets
>> xenboot fully working again for PV DomUs on x86 (currently the xenboot
>> output only goes to the hypervisor via hyper
On Thu, 2016-02-25 at 22:17 -0800, Hugh Dickins wrote:
> On Fri, 26 Feb 2016, Ebru Akagunduz wrote:
> > in Thu, Feb 25, 2016 at 05:35:50PM -0500, Rik van Riel wrote:
>
> > > Am I forgetting anything obvious?
> > >
> > > Is this too aggressive?
> > >
> > > Not aggressive enough?
> > >
> > > Coul
channel is already gone. Thus, the next time txstate()
is called, there is a NULL pointer exception because the buffer is
mapped but no DMA channel is allocated.
This patch adds an extra call unmap_dma_buffer() before releasing the
channel.
Signed-off-by: John Ogness
---
patch against next-20160226
This patchset adds missing input_sel settings to imx6ul-pinfunc.h.
The first patch is a cleanup patch with no functional changes
intended.
Various pads are missing the input_sel offset and value. Fix this.
Signed-off-by: Lothar Waßmann
---
arch/arm/boot/dts/imx6ul-pinfunc.h | 90 +++---
1 file changed, 45 insertions(+), 45 deletions(-)
diff --git a/arch/arm/boot/dts/imx6ul-pinfunc.h
b/arch/arm/boot
On Fri 2016-02-26 14:22:42, Kazimierz Krosman wrote:
> On 02/25/2016 10:47 PM, Tejun Heo wrote:
> >I'm not sure this is the right layer to implement generic logging
> >facility.
> In general this patches add only one feature- possibility of adding
> and deleting
> new kmsg devices, so I think that
On Fri, 26 Feb 2016 11:25:13 +0100
Sebastian Andrzej Siewior wrote:
> Steven, does this change look reasonable to you? I remember we had a
> discussion about this.
I'm still very nervous about having tracepoints in the preemptirqsoff
section. But that's not relevant to this patch.
I'm fine with
On 2/26/16 06:39, Jiri Kosina wrote:
> On Fri, 26 Feb 2016, Chen Gang wrote:
>
>> git is a tool mainly for analyzing code, but not mainly for normal
>> reading main code.
>>
>> So for me, the coding styles need not consider about git.
>
> You are mistaken here. It's very helpful when debugging;
On Sun, Feb 21, 2016 at 06:55:05PM -0800, H. Peter Anvin wrote:
> On 02/19/16 13:06, Luis R. Rodriguez wrote:
> >>
> >> I think the \n\t is unnecessary.
> >
> > Super! I wonder if we we can just use this on s390 as well without it
> > pooping?
> > I ask as this would set a precedent.
> >
>
> As
On Fri 2016-02-26 12:37:20, Sergey Senozhatsky wrote:
> When watchdog detects a hardlockup and calls nmi_panic() `printk_func'
> must be restored via printk_nmi_exit() call, so panic() will be able
> to flush nmi buf and show backtrace and panic message. We also better
> explicitly ask nmi to print
Tadeusz Struk wrote:
> + if (memcmp(sig->digest, output, sig->digest_size) ||
> + req->dst_len != sig->digest_size)
You must always do the size check first!
David
On 2/26/16 07:12, SeongJae Park wrote:
>
> On Fri, 26 Feb 2016, Chen Gang wrote:
>
>>
>> git is a tool mainly for analyzing code, but not mainly for normal
>> reading main code.
>>
>> So for me, the coding styles need not consider about git.
>
>
> It is common to see reject of trivial coding st
On 02/26/2016 09:42 AM, Brian Gerst wrote:
On Fri, Feb 26, 2016 at 8:51 AM, Boris Ostrovsky
wrote:
On 02/26/2016 05:53 AM, Roger Pau Monné wrote:
El 25/2/16 a les 16:16, Boris Ostrovsky ha escrit:
PV guests need to have their .bss zeroed out since it is not guaranteed
to be cleared by Xen's d
Hi Harvey,
On Fri, 26 Feb 2016 14:35:08 +
Harvey Hunt wrote:
> Hi Boris,
>
> On 26/02/16 00:57, Boris Brezillon wrote:
> > The mtd_ooblayout_xxx() helper functions have been added to avoid direct
> > accesses to the ecclayout field, and thus ease for future reworks.
> > Use these helpers in
On 26/02/16 15:10, Boris Ostrovsky wrote:
> On 02/26/2016 09:42 AM, Brian Gerst wrote:
>> On Fri, Feb 26, 2016 at 8:51 AM, Boris Ostrovsky
>> wrote:
>>> On 02/26/2016 05:53 AM, Roger Pau Monné wrote:
El 25/2/16 a les 16:16, Boris Ostrovsky ha escrit:
> PV guests need to have their .bss ze
On Thu 2016-02-25 13:36:41, Peter Zijlstra wrote:
> On Mon, Feb 22, 2016 at 03:56:55PM +0100, Petr Mladek wrote:
> > Also note that drain() correctly handles self-queuing works in compare
> > with flush().
>
> Nothing seems to prevent adding more work after drain() observes
> list_empty().
You mi
mkspec is copying built kernel to temporrary location
/boot/vmlinuz-$KERNELRELEASE-rpm
and runs installkernel on it. This however directly leads to grub2
menuentry for this suffixed binary being generated as well during the run
of installkernel script.
Later in the process the temporar
Hi Boris,
On 26/02/16 15:10, Boris Brezillon wrote:
Hi Harvey,
On Fri, 26 Feb 2016 14:35:08 +
Harvey Hunt wrote:
[...]
I'll look into this more later today, but wanted to run it by you in
case you have any thoughts.
Can you apply this patch [1], and let me know if you see the additiona
On Fri, Feb 26, 2016 at 03:21:35PM +0100, John Crispin wrote:
> The ESW is found in many of the old 100mbit MIPS based SoCs. it has 5
> external ports, 1 cpu port and 1 further port that the internal HW
> offloading engine connects to.
>
> This driver is very basic and only provides basic init and
On 26-02-16, 13:22, Arnd Bergmann wrote:
> The thermal subsystem can be a loadable module, so the qoriq driver has to be
> a module in that case as well in order to call of_cpufreq_cooling_register:
>
> drivers/built-in.o: In function `qoriq_cpufreq_ready':
> text+0x1f4548): undefined reference to
On Wed, Feb 24, 2016 at 05:44:57PM -0800, David Daney wrote:
> From: Andrew Pinski
>
> On ThunderX T88 pass 1.x through 2.1 parts, broadcast TLBI
> instructions may cause the icache to become corrupted if it contains
> data for a non-current ASID.
>
> This patch implements the workaround (which
El 26/2/16 a les 16:10, Boris Ostrovsky ha escrit:
> On 02/26/2016 09:42 AM, Brian Gerst wrote:
>> On Fri, Feb 26, 2016 at 8:51 AM, Boris Ostrovsky
>> wrote:
>>> On 02/26/2016 05:53 AM, Roger Pau Monné wrote:
El 25/2/16 a les 16:16, Boris Ostrovsky ha escrit:
> PV guests need to have thei
On 2/26/16 10:32, Jianyu Zhan wrote:
> On Fri, Feb 26, 2016 at 6:29 AM, Chen Gang wrote:
>> git is a tool mainly for analyzing code, but not mainly for normal
>> reading main code.
>>
>> So for me, the coding styles need not consider about git.
>
> For you, maybe yes.
>
> But for most of the dev
On Thu 2016-02-25 13:35:51, Peter Zijlstra wrote:
> On Mon, Feb 22, 2016 at 03:56:54PM +0100, Petr Mladek wrote:
> > +/**
> > + * drain_kthread_worker - drain a kthread worker
> > + * @worker: worker to be drained
> > + *
> > + * Wait until there is no work queued for the given kthread worker.
> >
On 2016-02-26 16:15, Jiri Kosina wrote:
> mkspec is copying built kernel to temporrary location
>
> /boot/vmlinuz-$KERNELRELEASE-rpm
>
> and runs installkernel on it. This however directly leads to grub2
> menuentry for this suffixed binary being generated as well during the run
> of inst
On 26/02/2016 16:18, Andrew Lunn wrote:
> On Fri, Feb 26, 2016 at 03:21:35PM +0100, John Crispin wrote:
>> The ESW is found in many of the old 100mbit MIPS based SoCs. it has 5
>> external ports, 1 cpu port and 1 further port that the internal HW
>> offloading engine connects to.
>>
>> This drive
On Tuesday 23 February 2016 09:38 PM, Andrew Lunn wrote:
> Hi Sekhar
>
> Thanks for offering to test. You can get the series here:
>
> https://github.com/lunn/linux.git branch v4.5-rc3-nvmem
Tested on DM365 by verifying MAC address read continues to work
Tested-by: Sekhar Nori
Thanks,
Sekhar
When CONFIG_MEDIA_CONTROLLER is disabled, we get a warning
about an unused function:
drivers/media/pci/saa7134/saa7134-core.c:832:13: error:
'saa7134_create_entities' defined but not used [-Werror=unused-function]
This moves the #ifdef outside of the function, as it is
never called here.
Signed
On 26/02/16 15:22, Roger Pau Monné wrote:
> El 26/2/16 a les 16:10, Boris Ostrovsky ha escrit:
>> On 02/26/2016 09:42 AM, Brian Gerst wrote:
>>> On Fri, Feb 26, 2016 at 8:51 AM, Boris Ostrovsky
>>> wrote:
On 02/26/2016 05:53 AM, Roger Pau Monné wrote:
> El 25/2/16 a les 16:16, Boris Ostro
Hi Bryan
I want to make sure I get the right message for Bjorn, so held off on
sending anything before confirming.
As far as clearing the 64-bit resource flag when it's a 32-bit address,
that seems pretty straight forward as captured in the comment.
But do we actually rely on a memory window bel
On 02/26/2016 10:22 AM, Roger Pau Monné wrote:
El 26/2/16 a les 16:10, Boris Ostrovsky ha escrit:
On 02/26/2016 09:42 AM, Brian Gerst wrote:
On Fri, Feb 26, 2016 at 8:51 AM, Boris Ostrovsky
wrote:
On 02/26/2016 05:53 AM, Roger Pau Monné wrote:
El 25/2/16 a les 16:16, Boris Ostrovsky ha escri
On Fri, 2016-02-26 at 15:03:19 +0200, Grygorii Strashko wrote:
> On 02/05/2016 01:39 AM, Sören Brinkmann wrote:
> > On Thu, 2016-02-04 at 15:14:47 -0800, Moritz Fischer wrote:
> >> Hi Soeren,
> >>
> >> On Thu, Feb 4, 2016 at 2:41 PM, Sören Brinkmann
> >> wrote:
> >>
> >>> But with this change the
On Fri, Feb 26, 2016 at 01:20:00PM +0200, Heikki Krogerus wrote:
> Since device_add_property_set() now always takes a copy of
> the property_set, and also since the fwnode type is always
> hard coded to be FWNODE_PDATA, there is no need for the
> drivers to deliver the entire struct property_set. T
On Thu 2016-02-25 13:59:32, Peter Zijlstra wrote:
> On Wed, Feb 24, 2016 at 05:18:05PM +0100, Petr Mladek wrote:
> > @@ -770,7 +782,22 @@ void delayed_kthread_work_timer_fn(unsigned long
> > __data)
> > if (WARN_ON_ONCE(!worker))
> > return;
> >
> > - spin_lock(&worker->lock);
On 02/26/2016 10:26 AM, David Vrabel wrote:
The tools support loading bzImages, not just ELF images.
We load them as ELF images though, I believe, after uncompressing. E.g.:
static int xc_dom_load_bzimage_kernel(struct xc_dom_image *dom)
{
return elf_loader.loader(dom);
}
-boris
On Thu, 25 Feb 2016, Boris Ostrovsky wrote:
> On 02/25/2016 07:10 AM, Stefano Stabellini wrote:
> > The xenboot early console has been partially broken for DomU for a long
> > time: the output would only go to the hypervisor via hypercall
> > (HYPERVISOR_console_io), while it wouldn't actually go t
This patch applies the two introduced helpers to
figure out the 1st and last bvec, and fixes the
original way after bio splitting.
Cc: sta...@vger.kernel.org
Reported-by: Sagi Grimberg
Reviewed-by: Sagi Grimberg
Reviewed-by: Christoph Hellwig
Signed-off-by: Ming Lei
---
include/linux/blkdev.h
Hi Guys,
The bio passed to bio_will_gap() may be fast cloned from upper
layer(dm, md, bcache, fs, ...), or from bio splitting in block
core. Unfortunately bio_will_gap() just figures out the last
bvec via 'bi_io_vec[prev->bi_vcnt - 1]' directly, and this way
is obviously wrong in case of fast-clon
In the following patch, the way for figuring out
the last bvec will be changed with a bit cost introduced,
so return immediately if the queue doesn't have virt
boundary limit. Actually most of devices have not
this limit.
Reviewed-by: Sagi Grimberg
Reviewed-by: Christoph Hellwig
Signed-off-by: M
The bio passed to bio_will_gap() may be fast cloned from upper
layer(dm, md, bcache, fs, ...), or from bio splitting in block
core.
Unfortunately bio_will_gap() just figures out the last bvec via
'bi_io_vec[prev->bi_vcnt - 1]' directly, and this way is obviously
wrong.
This patch introduces two h
On Thu 2016-02-25 14:01:15, Peter Zijlstra wrote:
> On Mon, Feb 22, 2016 at 03:57:00PM +0100, Petr Mladek wrote:
> > +enum {
> > + KTW_FREEZABLE = 1 << 2, /* freeze during suspend */
> > +};
>
> Weird value; what was wrong with 1 << 0 ?
Heh, the flag was inspired by
WQ_
On 2/25/16 7:08 PM, Mark Brown wrote:
On Wed, Feb 24, 2016 at 10:10:05AM -0600, Pierre-Louis Bossart wrote:
On 2/23/16 9:32 PM, Mark Brown wrote:
That said we really do need x86 to transition to use the clock API
in order to integrate with external devices, where the machine driver
does manag
Palams extcon IRQs are nested threaded and wired to the Palmas
inerrupt controller. So, this flag is not required for nested irqs
anymore, since commit 3c646f2c6aa9 ("genirq: Don't suspend
nested_thread irqs over system suspend") was merged.
Cc: MyungJoo Ham
Cc: Chanwoo Choi
Cc: Tony Lindgren
C
tps65910 RTC IRQ is nested threaded and wired to the tps65910 inerrupt
controller. So, this flag is not required for nested irqs anymore,
since commit 3c646f2c6aa9 ("genirq: Don't suspend nested_thread irqs
over system suspend") was merged.
Cc: Alessandro Zummo
Cc: Alexandre Belloni
Cc: Lee Jone
as3722 RTC IRQ is nested threaded and wired to the as3722 inerrupt
controller. So, this flag is not required for nested irqs anymore,
since commit 3c646f2c6aa9 ("genirq: Don't suspend nested_thread irqs
over system suspend") was merged.
Cc: Alessandro Zummo
Cc: Alexandre Belloni
Cc: Lee Jones
C
>On Fri, Feb 26, 2016 at 06:11:07AM +, Drokin, Oleg wrote:
>>
>> On Feb 26, 2016, at 1:03 AM, Greg Kroah-Hartman wrote:
>>
>> > On Thu, Feb 25, 2016 at 08:07:06PM -0500, James Simmons wrote:
>> >> The module information for Lustre is stale or in some cases
>> >> completely missing. This colle
Palams RTC IRQ is nested threaded and wired to the Palmas inerrupt
controller. So, this flag is not required for nested irqs anymore,
since commit 3c646f2c6aa9 ("genirq: Don't suspend nested_thread irqs
over system suspend") was merged.
Cc: Alessandro Zummo
Cc: Alexandre Belloni
Cc: Tony Lindgre
tps80031 RTC IRQ is nested threaded and wired to the tps80031
inerrupt controller. So, this flag is not required for nested irqs
anymore, since commit 3c646f2c6aa9 ("genirq: Don't suspend
nested_thread irqs over system suspend") was merged.
Cc: Alessandro Zummo
Cc: Alexandre Belloni
Cc: Lee Jone
This patch applies the two introduced helpers to
figure out the 1st and last bvec.
Reviewed-by: Sagi Grimberg
Reviewed-by: Christoph Hellwig
Signed-off-by: Ming Lei
---
block/blk-merge.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/block/blk-merge.c b/block/blk-m
Am Freitag, den 26.02.2016, 12:06 +0100 schrieb Joerg Roedel:
> Hi Philipp,
>
> On Fri, Feb 26, 2016 at 09:55:55AM +0100, Philipp Zabel wrote:
> > Do you have a stable branch that I could base the mediatek-drm patches
> > on and that I may include in a pull request to be merged via drm-next?
>
>
Palmas gpadc IRQs are nested threaded and this flag is not required for nested
irqs anymore, since commit 3c646f2c6aa9 ("genirq: Don't suspend nested_thread
irqs over system suspend") was merged.
Cc: Hartmut Knaack
Cc: Lars-Peter Clausen
Cc: Peter Meerwald
Cc: Lee Jones
Cc: Nishanth Menon
Sig
The IRQF_EARLY_RESUME flag is not required for nested irqs anymore,
since commit 3c646f2c6aa9 ("genirq: Don't suspend nested_thread irqs
over system suspend") was merged.
Hence, this flag can be dropped for MFD cell's devices where MFD interrupt
controller defines nested IRQs as nested threaded IRQ
tps6586x RTC IRQ is nested threaded and wired to the tps6586x inerrupt
controller. So, this flag is not required for nested irqs anymore,
since commit 3c646f2c6aa9 ("genirq: Don't suspend nested_thread irqs
over system suspend") was merged.
Cc: Alessandro Zummo
Cc: Alexandre Belloni
Cc: Lee Jone
Austin S. Hemmelgarn wrote:
> Added linux-btrfs as this should be documented there as a known issue
> until it gets fixed (although I have no idea which side is the issue).
This is a very bad behavior, as it makes impossible to safely use btrfs
loop bind mounts in fstab. (Well, it is possible to
On Mon, Feb 22, 2016 at 1:17 AM, Wolfram Sang wrote:
> On Thu, Feb 18, 2016 at 05:53:05PM +0200, Daniel Baluta wrote:
>> Sending this as an RFC because I don't know if style fixes are appropriate
>> for this driver and also not sure if deadlock fix is the best solution.
>>
>> I2C people should onl
of_clk_init() uses for_each_matching_node_and_match() to find clock
providers, which returns all matching device nodes, whether they are
enabled or not. Hence clock providers that are disabled explicitly in DT
using e.g.
"status = "disabled";
are still activated.
Add a check to ignore de
When nested interrupts are handled with regmap irq framework, we need to
mark the interrupts to be resend for pending interrupts on enable_irq.
Else the events might be lost for nested irqs.
Signed-off-by: Grygorii Strashko
---
drivers/base/regmap/regmap-irq.c | 1 +
1 file changed, 1 insertion(
Hi Kelly,
On Wed, Feb 24, 2016 at 06:29:56PM +, Zytaruk, Kelly wrote:
> I don't know if the asynchronous nature of the iommu attach/detach is
> by design or if it is broken somewhere up the tree and just not
> working in my case. Maybe one of the iommu owners could answer this.
Thanks a lot
The Home Agent and PCU PCI devices in Broadwell-EP have a non-BAR register
where a BAR should be. We don't know what the side effects of sizing the
"BAR" would be, and we don't know what address space the "BAR" might appear
to describe.
Mark these devices as having non-compliant BARs so the PCI c
After the addition of V2 support, there was a regression observed
when testing it on MSM8996. The reason is driver puts the controller
in to RUN state and writes the data to be 'tx' ed in fifo. But controller
has to be put in to 'PAUSE' state and data has to written to fifo. Then
should be put in t
Hi guys,
Here's a proposal for dealing with these devices that have non-BAR
registers where BARs are supposed to be. The idea is to:
- have an early quirk mark these devices,
- disable IO & MEM decoding so the devices don't consume address space
we don't know about, and
- skip BAR sizi
Broadcom Vulcan bridges have a BAR 0 for internal debug registers. But
writing certain addresses to the BAR can trigger a hardware problem in the
device. Linux doesn't need any BARs on these devices, so we can ignore
them.
Mark these bridges as having non-compliant BARs so the PCI core doesn't
t
The PCI config header (first 64 bytes of each device's config space) is
defined by the PCI spec so generic software can identify the device and
manage its usage of I/O, memory, and IRQ resources.
Some non-spec-compliant devices put registers other than BARs where the
BARs should be. When the PCI
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
T
Make it clear exactly how many keys and values are supported through
better defines, and add 1 to the vals count, since normally clients
want support for at least a hitcount and two other values.
Also, note the error return value for tracing_map_add_key/val_field()
in the comments.
Signed-off-by:
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
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
Reviewed-by: Namhyung Kim
---
kernel/t
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 hist:keys=xxx:vals=yyy:sor
'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 exhausti
This is v15 of the 'hist triggers' patchset.
This is the same as v14 but with Masami's log2 test case added.
Patch 1 can be merged into patch 8 from v13, 'tracing: Add lock-free
tracing_map'. Following the v13 suggestions, I made a couple changes
to the tracing map constants to clarify the field
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 t
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: Masami Hiramatsu
Reviewed-by:
Update the Ci20's defconfig to enable the JZ4780's NAND driver and
therefore access to the UBIFS rootfs.
Signed-off-by: Harvey Hunt
Cc: Paul Burton
Cc: linux-kernel@vger.kernel.org
---
arch/mips/configs/ci20_defconfig | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --
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 trigg
Add documentation and usage examples for 'hist' triggers.
Signed-off-by: Tom Zanussi
Tested-by: Masami Hiramatsu
Reviewed-by: Namhyung Kim
---
Documentation/trace/events.txt | 1155
1 file changed, 1155 insertions(+)
diff --git a/Documentation/trace/ev
On Thu, Feb 25, 2016 at 3:15 PM, Laura Abbott wrote:
> On 02/25/2016 09:35 AM, Kees Cook wrote:
>> Ah-ha, yes, that was one of the missing pieces:
>>
>> [ 10.790970] lkdtm: Performing direct entry READ_AFTER_FREE
>> [ 10.790992] lkdtm: Value in memory before free: 12345678
>> [ 10.790996] lk
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: 1
{ bytes_req:
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 ...
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 trigger modifiers (execname, hex, sysca
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 the
On Fri, 26 Feb 2016, js1...@gmail.com wrote:
> From: Joonsoo Kim
>
> Some of "#if DEBUG" are for reporting slab implementation bug rather than
> user usecase bug. It's not really needed because slab is stable for a
> quite long time and it makes code too dirty. This patch remove it.
Acked-by:
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.
# ./ftracetest test.d/trigg
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 Hiramatsu
Reviewed-by: Namhyung Kim
Hi Linus,
Please pull the following Ceph fixes for -rc6 from
git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus
There are two small messenger bug fixes and a log spam regression fix.
Thanks!
sage
Ilya
The Zodiac watchdog is implemented on a microcontoller. The reset reason
currently labelled "trigger" is not to detect when the watchdog has
triggered (as had been initially understood and suggested by the naming),
but to inform the reader that the watchdog, which in fact has it's own
hardware watc
Acked-by: Christoph Lameter
On Fri, Feb 26, 2016 at 10:42:55AM +0800, Joao Pinto wrote:
> Hi! This patch seems OK also.
> I did not received the 3/4 and 4/4 patches.
Huh. I do see them in the list archives:
http://marc.info/?l=linux-pci&m=145642190422528&w=2
http://marc.info/?l=linux-pci&m=145642190522529&w=2
> On 2/2
From: Masami Hiramatsu
Add a test for log2 modifier of hist trigger in hist_mod.tc.
Here is the test result.
# ./ftracetest test.d/trigger/trigger-hist-mod.tc
=== Ftrace unit tests ===
[1] event trigger - test histogram modifiers [PASS]
# of passed: 1
# of failed: 0
# of u
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 hist:keys=stackt
1 - 100 of 1072 matches
Mail list logo
