Continuous Double "the" in a comment. Changed it to single "the"
Signed-off-by: Hari
---
drivers/net/ethernet/intel/e1000/e1000_hw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/intel/e1000/e1000_hw.c
b/drivers/net/ethernet/in
Continuous Double "the" in a comment. Changed it to single "the"
Signed-off-by: Hari
---
drivers/net/ethernet/intel/e1000/e1000_hw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/intel/e1000/e1000_hw.c
b/drivers/net/ethernet/in
to test the patches in other scenarios though..
Thanks
Hari
On Friday 18 August 2017 01:44 AM, Michal Suchanek wrote:
From: Hari Bathini
With fadump (dump capture) kernel booting like a regular kernel, it needs
almost the same amount of memory to boot as the production kernel, which is
un
On Friday 18 August 2017 05:27 PM, Michal Suchánek wrote:
On Fri, 18 Aug 2017 16:20:53 +0530
Hari Bathini wrote:
Hi Michal,
Thanks for the patches. I tried testing with the patches:
[0.00] fadump: Firmware-assisted dump is active.
[0.00] fadump: Modifying command line
param_info->shortening += shortening;
@@ -550,7 +529,7 @@ static int __init fadump_rework_cmdline_params(char *param,
char *val,
strlen(FADUMP_EXTRA_ARGS_PARAM) - 1))
return 0;
- fadump_update_params(param_info, param, val);
+ fadump_update_params(param_info, param, val, currant, next);
return 0;
}
Thanks
Hari
On 3 August 2017 at 18:53, Dan Carpenter wrote:
> On Thu, Aug 03, 2017 at 06:23:54PM +0530, hari prasath wrote:
>> On 3 August 2017 at 11:52, kbuild test robot wrote:
>> > Hi Hari,
>> >
>> > [auto build test WARNING on staging/staging-testing]
>> &
Remove explicit typecasting of return value in the interrupt handlers.
Signed-off-by: Hari Prasath
---
drivers/staging/pi433/pi433_if.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/pi433/pi433_if.c b/drivers/staging/pi433/pi433_if.c
index ed737f4
On 3 August 2017 at 11:52, kbuild test robot wrote:
> Hi Hari,
>
> [auto build test WARNING on staging/staging-testing]
> [also build test WARNING on next-20170802]
> [cannot apply to v4.13-rc3]
> [if your patch is applied to the wrong git tree, please drop us a note to
> he
On 8 July 2017 at 16:31, Sakari Ailus wrote:
> Hi Hari,
>
> On Fri, Jul 07, 2017 at 08:15:21PM +0530, Hari Prasath wrote:
>> kstrdup kernel primitive can be used to replace kmalloc followed by
>> string copy. This was reported by coccinelle tool
>>
>
kstrdup kernel primitive can be used to replace kmalloc followed by
string copy. This was reported by coccinelle tool.
Signed-off-by: Hari Prasath
---
v1: Replace kmalloc followed by memcpy with kmemdup. Based on
review comments from Alan Cox, this could better be done
On 10 July 2017 at 01:22, Sakari Ailus wrote:
> On Sun, Jul 09, 2017 at 05:56:15PM +0530, hari prasath wrote:
>> On 8 July 2017 at 16:31, Sakari Ailus wrote:
>> > Hi Hari,
>> >
>> > On Fri, Jul 07, 2017 at 08:15:21PM +0530, Hari Prasath wrote:
>&g
kmemdup can be used to replace kmalloc followed by a memcpy.This was
pointed out by the coccinelle tool.
Signed-off-by: Hari Prasath
---
drivers/staging/media/atomisp/pci/atomisp2/css2400/sh_css_firmware.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git
a/drivers/staging
On 07-Jul-2017 5:25 PM, "Alan Cox" wrote:
On Fri, 2017-07-07 at 17:20 +0530, Hari Prasath wrote:
> kmemdup can be used to replace kmalloc followed by a memcpy.This was
> pointed out by the coccinelle tool.
And kstrdup could do the job even better I think ?
> Yes & thanks
kstrdup kernel primitive can be used to replace kmalloc followed by
string copy. This was reported by coccinelle tool
Signed-off-by: Hari Prasath
---
.../media/atomisp/pci/atomisp2/css2400/sh_css_firmware.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git
From: Hari Prasath
Adding missing indio_dev->dev.of_node references to allow iio consumers
to access the device channels.
Signed-off-by: Hari Prasath
---
drivers/staging/iio/adc/ad7192.c | 1 +
drivers/staging/iio/adc/ad7780.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/driv
Adding missing indio_dev->dev.of_node references to allow iio consumers
to access the device channels.
Signed-off-by: Hari Prasath
---
v2: Wrong from email ID in first version of patch
---
drivers/staging/iio/adc/ad7192.c | 1 +
drivers/staging/iio/adc/ad7780.c | 1 +
2 files chan
Kindly discard this patch versions. I will send a new one.
On 17 July 2017 at 17:49, Hari Prasath wrote:
> Adding missing indio_dev->dev.of_node references to allow iio consumers
> to access the device channels.
>
> Signed-off-by: Hari Prasath
> ---
> v2: Wrong f
Adding missing indio_dev->dev.of_node references to allow iio consumers
to access the device channels.
Signed-off-by: Hari Prasath
---
v2: Wrong from mail ID in first version of patch
---
drivers/staging/iio/adc/ad7192.c | 1 -
drivers/staging/iio/adc/ad7780.c | 1 -
2 files changed
Hi,
I agree that it's initialized in the core IIO driver. Also I have
screwed up the patch.
Regards,
Hari
On 17 July 2017 at 18:47, Lars-Peter Clausen wrote:
> Hi,
>
> The patch seems to be reverted?
>
> Also should this part in the IIO core take care of automatically settin
Fix checkpatch warning to add space around the substraction operation
Signed-off-by: Hari Prasath
---
drivers/staging/iio/adc/ad7280a.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/iio/adc/ad7280a.c
b/drivers/staging/iio/adc/ad7280a.c
index d5ab83f
error appropriately.
Tested-by: Hari Bathini
---
v2: fix return in register_fadump()
---
arch/powerpc/kernel/fadump.c | 24
1 file changed, 16 insertions(+), 8 deletions(-)
diff --git a/arch/powerpc/kernel/fadump.c b/arch/powerpc/kernel/fadump.c
index 2fa582092d42
+---
1 file changed, 1 insertion(+), 19 deletions(-)
I think this looks OK to me, but I don't have a setup to test it easily.
I've added Hari to Cc who might be able to.
But I'll give you an ack in the hope that it works :)
Actually, I did some digging in the git log and the traversal was added
eah,
there won't be a hang in regular kexec_file_load case but for
correctness, that kernel should also not see stale CPU info in FDT?
Thanks
Hari
s.
Therefore change kexec_fdt_totalsize_ppc64() to calculate just the extra
space needed by the kdump kernel, and change the function name so that it
better reflects what the function is now doing.
Thanks for fixing this, Thiago.
Reviewed-by: Hari Bathini
Signed-off-by: Thiago Jung Bauermann
Reviewed-by: Lak
and the other, a
local reset is only for the M4F processing core. When loading the image,
the driver first releases the subsystem reset, loads the firmware image
and then releases the local reset to let the M4F processing core run.
Signed-off-by: Martyn Welch
Signed-off-by: Hari Nagalla
subsystems.
The YAML binding document provides the various node properties to be
configured by the consumers of the M4F subsystem.
Signed-off-by: Martyn Welch
Signed-off-by: Hari Nagalla
---
Changes since v1:
- Spelling corrections
- Corrected to pass DT checks
Changes since v2:
- Missed spelling
From: Martyn Welch
In the next commit we will be adding the M4F driver which shares a lot of
commonality with the DSP driver. Split this shared functionality out so
that it can be used by both drivers.
Signed-off-by: Martyn Welch
Signed-off-by: Hari Nagalla
---
Changes since v2:
- New patch
From: Martyn Welch
We will be adding the M4F driver which shares a lot of commonality
with the DSP driver. Common data structures are introduced here.
Signed-off-by: Martyn Welch
Signed-off-by: Hari Nagalla
---
Changes in v6:
- Created a separate patch for data structures to ease review
2022) for
further details: https://www.ti.com/lit/pdf/SPRUIV7A
Hari Nagalla (1):
dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs
Martyn Welch (3):
remoteproc: k3: Split out data structures common with M4 driver
remoteproc: k3: Split out functions common with M4 driver
remoteproc: k3-m4
.yaml#
>> +$schema:http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: TI K3 M4F processor subsystems
>> +
>> +maintainers:
>> + - Hari Nagalla
>> + - Mathieu Poirier
> Are you sure Mathieu has this device and is a maintainer of this device?
On 11/2/23 11:43, Jan Kiszka wrote:
RTI1 watchdog also powers up R5F core 1. And this could happen either in
When writing "... also powers up...", other than R5F core 1, what else is being
powered?
Would be a question for the SoC vendor - I assumed that only mcu_rti1
[1] goes on when enabling
From: Martyn Welch
In the next commit we will be adding the M4F driver which shares a lot of
commonality with the DSP driver. Move this shared functionality out so
that it can be used by both drivers.
Signed-off-by: Martyn Welch
Signed-off-by: Hari Nagalla
---
Changes since v2:
- New patch
/5ba77847343f22b5f9ec2b7aeabc410aaf8cdf45
Hari Nagalla (2):
dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs
arm64: defconfig: Enable TI K3 M4 remote proc driver
Martyn Welch (3):
remoteproc: k3: Move out data structures common with M4 driver
remoteproc: k3: Move out functions common with M4
From: Martyn Welch
We will be adding the M4F driver which shares a lot of commonality
with the DSP driver. Common data structures are introduced here.
Signed-off-by: Martyn Welch
Signed-off-by: Hari Nagalla
---
Changes since v5:
- Created a separate patch for data structures to ease review
and the other, a
local reset is only for the M4F processing core. When loading the image,
the driver first releases the subsystem reset, loads the firmware image
and then releases the local reset to let the M4F processing core run.
Signed-off-by: Martyn Welch
Signed-off-by: Hari Nagalla
Enable CONFIG_TI_K3_M4_REMOTEPROC
Some K3 platform devices (AM64x, AM62x) have a Cortex M4 core. Build
the M4 remote proc driver as a module for these platforms.
Signed-off-by: Hari Nagalla
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs
subsystems.
The YAML binding document provides the various node properties to be
configured by the consumers of the M4F subsystem.
Signed-off-by: Martyn Welch
Signed-off-by: Hari Nagalla
---
Changes since v1:
- Spelling corrections
- Corrected to pass DT checks
Changes since v2:
- Missed spelling
On 3/25/24 12:20, Andrew Davis wrote:
static int omap_mbox_chan_send_noirq(struct omap_mbox *mbox, u32 msg)
{
- int ret = -EBUSY;
+ if (mbox_fifo_full(mbox))
+ return -EBUSY;
- if (!mbox_fifo_full(mbox)) {
- omap_mbox_enable_irq(mbox, IRQ_RX);
-
On 3/25/24 12:20, Andrew Davis wrote:
The kernel FIFO queue has a couple issues. The biggest issue is that
it causes extra latency in a path that can be used in real-time tasks,
such as communication with real-time remote processors.
The whole FIFO idea itself looks to be a leftover from before
The C7xv-dsp on AM62A have 32KB L1 I-cache and a 64KB L1 D-cache. It
does not have an addressable l1dram . So, remove this optional sram
property from the bindings to fix device tree build warnings.
Signed-off-by: Hari Nagalla
---
Changes from v1 to v2:
*) Kept back memory-regions property
The C7xv-dsp on AM62A have 32KB L1 I-cache and a 64KB L1 D-cache. It
does not have an addressable l1dram . So, remove this optional sram
property from the bindings to fix device tree build warnings.
Signed-off-by: Hari Nagalla
---
Changes in v3:
*) Use allOf keyword with separate ifs for each
This patch adds a new PPC64 partition type to be used for opal
specific nvram partition. A new partition type is needed as none
of the existing type matches this partition type.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
fs/pstore/inode.c |3 +++
include/linux/pstore.h
CONFIG_PPC_PSERIES or CONFIG_PPC_POWERNV
flag is used in this patchset, it is to reduce the kernel size in cases
where this flag is not set and doesn't have any impact logic wise.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
arch/powerpc/kernel/nvram_64.c | 25
While we are here, let us make timestamp related code
y2038-safe.
Suggested-by: Arnd Bergmann a...@arndb.de
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
arch/powerpc/include/asm/rtas.h|3 ++-
arch/powerpc/kernel/nvram_64.c |6 +++---
arch/powerpc/platforms
With minor checks, we can move most of the code for nvram
under pseries to a common place to be re-used by other
powerpc platforms like powernv. This patch moves such
common code to arch/powerpc/kernel/nvram_64.c file.
Signed-off-by: Hari Bathini hbath...@linux.vnet.ibm.com
---
arch/powerpc
the patches successfully on both pseries and powernv
platforms. Also, tested the patches successfully, on a kernel
compiled with both CONFIG_PPC_PSERIES=y CONFIG_PPC_POWERNV=y.
Changes from v4:
1. Added a patch for y2038-safe code changes
---
Hari Bathini (4):
powerpc/nvram: move generic
On 30 April 2015 at 19:44, gre...@linuxfoundation.org
gre...@linuxfoundation.org wrote:
On Thu, Apr 23, 2015 at 04:09:28PM +0100, Alan Cox wrote:
On Thu, 2015-04-23 at 13:43 +, Gujulan Elango, Hari Prasath (H.)
wrote:
This patch removes unwanted semicolon around close braces of code
l.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c1caae3de46a072d0855729aed6e793e536a4a55
opal/powernv:
https://github.com/open-power/skiboot/commit/9ee56b5
Thanks
Hari
---
arch/powerpc/kernel/crash.c | 20
1 file changed, 20 insertions(+)
diff --git a/arch/powerp
to reserve
memory for fadump based on system memory size.
---
Hari Bathini (2):
refactor code parsing size based on memory range
powerpc/fadump: parse fadump reserve memory size based on memory range
arch/powerpc/kernel/fadump.c | 64
include/linux/kernel.h
parameter for different system
memory sizes.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
Reviewed-by: Mahesh J Salgaonkar <mah...@linux.vnet.ibm.com>
---
Changes in v2:
1. Changed subject from "[PATCH v2 2/2] powerpc/fadump: add support to parse
size based on memory r
.
Cc: Eric Biederman <ebied...@xmission.com>
Cc: Vivek Goyal <vgo...@redhat.com>
Cc: Rusty Russell <ru...@rustcorp.com.au>
Cc: ke...@lists.infradead.org
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
changes in v2:
1. Rebased to latest upstream.
2. Mark
On 06/24/2016 10:56 AM, Michael Ellerman wrote:
On Wed, 2016-22-06 at 19:25:26 UTC, Hari Bathini wrote:
Currently, crashkernel parameter supports the below syntax to parse size
based on memory range:
crashkernel=:[,:,...]
While such parsing is implemented for crashkernel parameter
parameter for different system
memory sizes.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
Changes from v1:
1. Changed subject from "powerpc/fadump: add support to specify memory range
based size"
2. Reused crashkernel parsing code that was moved to kernel/params.c
.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
While this patch in itself has nothing to do with powerpc,
the powerpc patch (2/2) depends on this patch..
include/linux/kernel.h |5 +++
kernel/kexec_core.c| 63 +++-
kernel/pa
uprobe events can be added to the uprobe_events file under the instance
directory and the profile information for these events will be available in
uprobe_profile file in the same instance directory.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
include/linux/trace_events.h
)
$
while another container/host has a completely different view:
$ perf probe --list
probe_libc:memset(on __libc_memset in /lib64/libc.so.6)
$
This patch reuses the code that provides support to create new instances
under tracefs instances directory.
Signed-off-by: Hari Bathini
nf.org/2015/ocw/sessions/2667.html
[3] Notes for container-aware tracing:
https://etherpad.openstack.org/p/LPC2015_Containers
Signed-off-by: Aravinda Prasad <aravi...@linux.vnet.ibm.com>
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
kernel/ev
for uprobe events in
tracefs filesystem
3/3. New patch that adds "newinstance" mount option for tracefs
filesystem
[1] https://lkml.org/lkml/2015/7/15/192
---
Aravinda Prasad (1):
perf: filter container events based on cgroup namespace
Hari Bathini (2):
tracefs: add
Hi Steve,
Thanks for the review
On Tuesday 02 August 2016 03:15 AM, Steven Rostedt wrote:
On Thu, 28 Jul 2016 02:57:38 +0530
Hari Bathini <hbath...@linux.vnet.ibm.com> wrote:
If a uprobe event is set on a library function, and if a similar uprobe
event trace is needed for a con
to reserve
memory for fadump based on system memory size.
---
Hari Bathini (2):
kexec: refactor code parsing size based on memory range
powerpc/fadump: parse fadump reserve memory size based on memory range
arch/powerpc/kernel/fadump.c | 63 ++---
include/linux/kernel.h
s.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
Reviewed-by: Mahesh J Salgaonkar <mah...@linux.vnet.ibm.com>
---
Changes from v2:
1. Updated changelog
arch/powerpc/kernel/fadump.c | 63 --
1 file changed, 54 insertions(+), 9 de
in parsing the crashkernel
parameter.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
Changes from v2:
1. Moved the code to lib/cmdline.c instead of kernel/params.c
include/linux/kernel.h |5 ++
kernel/kexec_core.c| 63 ++---
lib/cmdline.c
to reserve
memory for fadump based on system memory size.
---
Hari Bathini (2):
kexec: refactor code parsing size based on memory range
powerpc/fadump: parse fadump reserve memory size based on memory range
arch/powerpc/kernel/fadump.c | 64
include/linux
in parsing the crashkernel
parameter.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
Changes from v1:
1. Updated changelog
include/linux/kernel.h |5 +++
kernel/kexec_core.c| 63 +++-
kernel/params.c
parameter for different system
memory sizes.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
Reviewed-by: Mahesh J Salgaonkar <mah...@linux.vnet.ibm.com>
---
arch/powerpc/kernel/fadump.c | 64 --
1 file changed, 55 insertions(+),
Hi Eric,
Thanks for the comments..
On Thursday 04 August 2016 08:24 AM, Eric W. Biederman wrote:
Hari Bathini <hbath...@linux.vnet.ibm.com> writes:
When tracefs is mounted inside a container, its files are visible to
all containers. This implies that a user from within a container ca
Ping..
On Friday 24 June 2016 10:45 PM, Hari Bathini wrote:
On 06/24/2016 10:56 AM, Michael Ellerman wrote:
On Wed, 2016-22-06 at 19:25:26 UTC, Hari Bathini wrote:
Currently, crashkernel parameter supports the below syntax to parse
size
based on memory range:
crashkernel
On 07/05/2016 10:48 AM, Michael Ellerman wrote:
On 06/24/2016 10:56 AM, Michael Ellerman wrote:
On Wed, 2016-22-06 at 19:25:26 UTC, Hari Bathini wrote:
...
While the code is moved to kernel/params.c file, there is no change in logic
for crashkernel parameter parsing as the moved code
Hi Dave
Thanks for the review..
On Thursday 04 August 2016 02:56 PM, Dave Young wrote:
Hi Hari,
On 08/04/16 at 01:03am, Hari Bathini wrote:
crashkernel parameter supports different syntaxes to specify the amount
of memory to be reserved for kdump kernel. Below is one of the supported
On Thursday 04 August 2016 03:15 PM, Michael Ellerman wrote:
Hari Bathini <hbath...@linux.vnet.ibm.com> writes:
...
/**
* fadump_calculate_reserve_size(): reserve variable boot area 5% of System
RAM
*
@@ -212,12 +262,17 @@ static inline unsigned long
fadump_calculate_reserv
On Friday 05 August 2016 12:23 AM, Hari Bathini wrote:
On Thursday 04 August 2016 03:15 PM, Michael Ellerman wrote:
Hari Bathini <hbath...@linux.vnet.ibm.com> writes:
...
/**
* fadump_calculate_reserve_size(): reserve variable boot area 5%
of System RAM
*
@@ -212,12 +
On Monday 08 August 2016 02:26 PM, Michael Ellerman wrote:
Hari Bathini <hbath...@linux.vnet.ibm.com> writes:
On Friday 05 August 2016 12:23 AM, Hari Bathini wrote:
On Thursday 04 August 2016 03:15 PM, Michael Ellerman wrote:
The code already knows how to reserve 5% based on th
On Tuesday 02 August 2016 10:57 PM, Hari Bathini wrote:
Hi Steve,
Thanks for the review
On Tuesday 02 August 2016 03:15 AM, Steven Rostedt wrote:
On Thu, 28 Jul 2016 02:57:38 +0530
Hari Bathini <hbath...@linux.vnet.ibm.com> wrote:
If a uprobe event is set on a library fu
are running in a given container context. Also, scripts
to map device and inode info to containers sounds plausible for better
tracing of containers.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
tools/perf/util/hist.c |7 +++
tools/perf/util/hist.h |1 +
tools/per
/$PID/ns. These changes make way for analyzing
events with regard to namespaces.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
tools/include/uapi/linux/perf_event.h | 38 +
tools/perf/builtin-annotate.c |1
tools/perf/builtin-diff.c |1
for every namespace
lets the userspace take a call on the definition of a container and
update perf tool accordingly.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
include/linux/perf_event.h |2 +
include/uapi/linux/perf_event.h | 38 ++
kernel/events/
tip
---
Hari Bathini (3):
perf: add PERF_RECORD_NAMESPACES to include namespaces related info
perf tool: add PERF_RECORD_NAMESPACES to include namespaces related info
perf tool: add cgroup identifier entry in perf report
include/linux/perf_event.h|2
include/
On Friday 20 January 2017 11:17 AM, Michael Ellerman wrote:
Hari Bathini <hbath...@linux.vnet.ibm.com> writes:
Get rid of multiple definitions of append_elf_note() & final_note()
functions. Reuse these functions compiled under CONFIG_CRASH_CORE
Also, define Elf_Word and use
On Tuesday 17 January 2017 10:36 PM, Hari Bathini wrote:
On Friday 06 January 2017 07:33 AM, Dave Young wrote:
On 01/05/17 at 11:01pm, Hari Bathini wrote:
Get rid of multiple definitions of append_elf_note() & final_note()
functions. Reuse these functions compiled under CONFIG_CRASH_
On Tuesday 24 January 2017 11:53 PM, Tony Luck wrote:
On Tue, Jan 24, 2017 at 10:11 AM, Hari Bathini
<hbath...@linux.vnet.ibm.com> wrote:
Hello IA64 folks,
Could you please review this patch..?
It looks OK in principal. My lab is in partial disarray at the
moment (just got bac
Hi Jiri,
On Wednesday 08 February 2017 06:27 PM, Jiri Olsa wrote:
On Wed, Feb 08, 2017 at 02:01:49PM +0530, Hari Bathini wrote:
This patch updates perf tool to examine PERF_RECORD_NAMESPACES events
emitted by the kernel when fork, clone, setns or unshare are invoked.
Also, it synthesizes
are running in a given container context. Also, scripts
to map device and inode info to containers sounds plausible for better
tracing of containers.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
tools/perf/util/hist.c |7 +++
tools/perf/util/hist.h |1 +
tools/per
Synthesize PERF_RECORD_NAMESPACES events for processes that were
running prior to invocation of perf record, the data for which is
taken from /proc/$PID/ns. These changes make way for analyzing
events with regard to namespaces.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
Add print support for events of type PERF_RECORD_NAMESPACES.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
tools/perf/util/event.c | 30 ++
tools/perf/util/event.h |1 +
tools/perf/util/machine.c |3 +++
3 files changed, 34 inse
Add script print support for events of type PERF_RECORD_NAMESPACES.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
tools/perf/builtin-script.c | 40
1 file changed, 40 insertions(+)
diff --git a/tools/perf/builtin-script.c b/tool
Now that we have a new option to show namespace events, update
the perf-script documentation accordingly.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
tools/perf/Documentation/perf-script.txt |3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/perf/Documentatio
Update perf tool to examine PERF_RECORD_NAMESPACES events emitted by
the kernel when fork, clone, setns or unshare are invoked.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
tools/include/uapi/linux/perf_event.h | 32 +++-
tools/perf/builtin-anno
of namespaces. Considering
such possibility, record both device and inode numbers separately for
each namespace.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
include/linux/perf_event.h |2 +
include/uapi/linux/perf_event.h | 32 +
kernel/events/
patches
* Updated record and script documenatation
* Dropped name field from ns_link_info struct
Changes from v5:
* Updated changelogs of patches 1 & 3
* Rebased the patches on perf/core in tip
---
Hari Bathini (8):
perf: add PERF_RECORD_NAMESPACES to include namespaces related info
Now that we have a new option to record namespace events, update
the perf-record documentation accordingly.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
tools/perf/Documentation/perf-record.txt |3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/perf/Documen
Hi Jirka,
On Wednesday 22 February 2017 04:41 PM, Jiri Olsa wrote:
On Tue, Feb 21, 2017 at 07:31:11PM +0530, Hari Bathini wrote:
Currently, there is no trivial mechanism to analyze events based on
containers. perf -G can be used, but it will not filter events for the
containers created after
Hi Peter,
On Thursday 16 February 2017 03:58 PM, Peter Zijlstra wrote:
On Wed, Feb 08, 2017 at 02:01:24PM +0530, Hari Bathini wrote:
With the advert of container technologies like docker, that depend
on namespaces for isolation, there is a need for tracing support for
namespaces. This patch
to be.
Agreed. Will drop name field from the structure and use an indexing
table to get names in userspace..
Thanks
Hari
/$PID/ns. These changes make way for analyzing
events with regard to namespaces.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
Changes from v4:
* Added warning when nr_namespaces values of the kernel
and perf tool mismatch.
* Improved printing of namespace records.
the cgroup namespace's device and inode
numbers. This is based on the assumption that each container is created
with it's own cgroup namespace. The third patch has scope for improvement
based on the conventions a container is attributed with, going forward.
---
Hari Bathini (3):
perf: add
With the advert of container technologies like docker, that depend
on namespaces for isolation, there is a need for tracing support for
namespaces. This patch introduces new PERF_RECORD_NAMESPACES event
for tracing based on namespaces related info.
Signed-off-by: Hari Bathini <hb
49
2.16% 0/0x047
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
* No changes since v4.
tools/perf/util/hist.c |7 +++
tools/perf/util/hist.h |1 +
tools/perf/util/sort.c
On Friday 06 January 2017 07:33 AM, Dave Young wrote:
On 01/05/17 at 11:01pm, Hari Bathini wrote:
Get rid of multiple definitions of append_elf_note() & final_note()
functions. Reuse these functions compiled under CONFIG_CRASH_CORE
Also, define Elf_Word and use it instead of generic
49
2.16% 0/0x047
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
tools/perf/util/hist.c |7 +++
tools/perf/util/hist.h |1 +
tools/perf/util/sort.c | 41 +
tools/per
/$PID/ns. These changes make way for analyzing
events with regard to namespaces.
Signed-off-by: Hari Bathini <hbath...@linux.vnet.ibm.com>
---
Changes from v4:
* Added warning when nr_namespaces values of the kernel
and perf tool mismatch.
* Improved printing of namespace records.
1 - 100 of 569 matches
Mail list logo
