There is a psi module that exists under kernel/sched/psi.
Add a basic test to test the psi.
This test just add the basic support to check cpu/memory/io interface.
Further test will be added on top of this.
Signed-off-by: Pintu Kumar
---
MAINTAINERS | 2 +
tools
.
No functionality is broken or changed this way.
Signed-off-by: Pintu Kumar
Signed-off-by: Pintu Agarwal
---
v2: completely get rid of this variable and set .data to NULL
Suggested-by: Vlastimil Babka
include/linux/compaction.h | 1 -
kernel/sysctl.c| 2 +-
mm/compaction.c
changed this way.
Signed-off-by: Pintu Kumar
Signed-off-by: Pintu Agarwal
---
include/linux/compaction.h | 1 -
kernel/sysctl.c| 1 +
mm/compaction.c| 3 ---
3 files changed, 1 insertion(+), 4 deletions(-)
diff --git a/include/linux/compaction.h b/include/linux/compaction.h
ode is filled with default
or current value.
There could be few other use cases where this can be useful.
Signed-off-by: Pintu Kumar
Signed-off-by: Pintu Agarwal
---
Documentation/admin-guide/sysctl/vm.rst | 8
include/linux/vmstat.h | 7 +++
kernel/sysct
y: commitment overflow: ppid:150, pid:164, pages:62451
fork failed[count:0]: Cannot allocate memory
Signed-off-by: Pintu Kumar
---
mm/util.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/mm/util.c b/mm/util.c
index 5ef378a..9431ce7a 100644
--- a/mm/util.c
+++ b/mm/util.c
@@ -895,6
As I was browsing through this code, I found that linux/kmemleak.h
was declared twice.
When I run ./scripts/checkincludes.pl it reported the same:
mm/slab.h: linux/kmemleak.h is included more than once.
Thus removing the last included header.
Signed-off-by: Pintu Kumar
---
mm/slab.h | 1 -
1
ed ?
What can I interpret from this?
And, what does it mean by: pages_volatile:1 ?
Basically, I wanted to understand, is there any problem with the above
output, or it is fine.
If it is fine, how to prove it?
Thanks,
Pintu
On Mon, Sep 17, 2018 at 8:29 PM Mike Rapoport wrote:
>
> On Mon,
On Mon, Sep 17, 2018 at 11:46 AM Pintu Kumar wrote:
> > > But still no effect.
> > > And I checked LTP test cases. It almost doing the same thing.
> > >
> > > I observed that [ksmd] thread is not waking up at all.
> > > I gave some print inside
On Mon, Sep 17, 2018 at 10:07 AM Mike Rapoport wrote:
>
> On Sun, Sep 16, 2018 at 10:35:17PM +0530, Pintu Kumar wrote:
> > On Sun, Sep 16, 2018 at 9:02 PM Mike Rapoport
> > wrote:
> > >
> > > On Fri, Sep 14, 2018 at 07:58:01PM +0530, Pintu Kumar wrote:
&
On Sun, Sep 16, 2018 at 9:02 PM Mike Rapoport wrote:
>
> On Fri, Sep 14, 2018 at 07:58:01PM +0530, Pintu Kumar wrote:
> > Hi All,
> >
> > Board: Hikey620 ARM64
> > Kernel: 4.9.20
> >
> > I am trying to verify KSM (Kernel Same Page Merging) functionality
On Fri, 14 Sep 2018, 10:42 pm Yang Shi, wrote:
>
> Hi Pintu,
>
> I recall there are some ksm test cases in LTP. Did you try them out?
No. I haven't seen the LTP test. I will check out now.
But I wonder what is the problem with my test?
> On Fri, Sep 14, 2018 at 7:28 A
Hi All,
Board: Hikey620 ARM64
Kernel: 4.9.20
I am trying to verify KSM (Kernel Same Page Merging) functionality on
4.9 Kernel using "mmap" and madvise user space test utility.
But to my observation, it seems KSM is not working for me.
CONFIG_KSM=y is enabled in kernel.
ksm_init is also called dur
On Thu, Jul 26, 2018 at 9:08 PM Sebastian Andrzej Siewior
wrote:
>
> On 2018-07-18 20:19:15 [+0530], Pintu Kumar wrote:
> > Hi All,
> Hi,
>
> > I have a question about PREEMPT_RT patch for 3.10 kernel.
> > I am trying to port this rt patch: 0224-printk-rt-aware.
s this the expected behavior, even on PREEMPT_RT kernel?
Is there a way we can fix this issue on non-rt kernel?
Please help us with your suggestions.
Thanks,
Pintu
On Wed, Jun 13, 2018 at 8:02 PM Pintu Kumar wrote:
>
> Dear Thomas,
>
> I was looking into this RT patches fo
On Tue, Jul 10, 2018 at 8:20 PM Shuah Khan wrote:
>
> Hi Li Zhijian,
>
> On 07/01/2018 09:53 PM, Li Zhijian wrote:
> > root@vm-lkp-nex04-8G-7 ~/linux-v4.18-rc2/tools/testing/selftests/android#
> > make
> > make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make
> > rule.
> >
l I am not familiar with this.
So, I need your help.
Thank You!
Regards,
Pintu
On Thu, May 17, 2018 at 6:58 PM, Pintu Kumar wrote:
> On Mon, May 14, 2018 at 7:58 PM, Pintu Kumar wrote:
>>
>> On Mon, May 14, 2018 at 6:41 PM, Lucas Stach wrote:
>> > Am Montag, den 14.0
On Mon, May 14, 2018 at 7:58 PM, Pintu Kumar wrote:
>
> On Mon, May 14, 2018 at 6:41 PM, Lucas Stach wrote:
> > Am Montag, den 14.05.2018, 17:42 +0530 schrieb Pintu Kumar:
> >> Hi,
> >>
> >> Is there any work around possible to set IRQ affinity for some
On Mon, May 14, 2018 at 6:41 PM, Lucas Stach wrote:
> Am Montag, den 14.05.2018, 17:42 +0530 schrieb Pintu Kumar:
>> Hi,
>>
>> Is there any work around possible to set IRQ affinity for some GPIO
>> interrupt ?
>> How to avoid CPU0 to receive the current GPIO int
be served by another CPU ?
Need your inputs to decide whether it is still possible to set
affinity for GPIO interrupt, or its impossible ?
Thanks,
Pintu
On Fri, May 11, 2018 at 8:07 PM, Pintu Kumar wrote:
> On Fri, May 11, 2018 at 6:34 PM, Lucas Stach wrote:
>> Am Freitag, den 1
On Thu, May 3, 2018 at 2:48 AM, Shuah Khan (Samsung OSG)
wrote:
> Delete RUN_TESTS and EMIT_TESTS overrides and use common defines in
> lib.mk. Common defines work just fine and there is no need to define
> custom overrides.
>
> Signed-off-by: Shuah Khan (Samsung OSG)
> ---
> tools/testing/selft
On Fri, May 11, 2018 at 6:34 PM, Lucas Stach wrote:
> Am Freitag, den 11.05.2018, 13:39 +0100 schrieb Russell King - ARM Linux:
>> On Fri, May 11, 2018 at 05:07:37PM +0530, Pintu Kumar wrote:
>> > Hi,
>> >
>> > I need one help.
>> > I am using
Hi,
I need one help.
I am using i.MX7 Sabre board with kernel version 4.1.15
Let's say I am interested in GPIO number: 21
I wanted to set CPU affinity for particular GPIO->IRQ number, so I
tried the below steps:
root@10:~# echo 21 > /sys/class/gpio/export
root@10:~# echo "rising" > /sys/class/gpi
On Sat, May 5, 2018 at 6:43 AM, Shuah Khan (Samsung OSG)
wrote:
> When ion test is skipped because of unmet dependencies and/or unsupported
> configuration, it returns 0 which is treated as a pass by the Kselftest
> framework. This leads to false positive result even when the test could
> not be r
Hi,
As a simple query,
Is there a way to skip current available clock source (hpet) and allow
to pick the next one ?
I guess this will solve our purpose.
Thanks,
Pintu
On Fri, Apr 6, 2018 at 8:37 PM, Pintu Kumar wrote:
> Hi,
>
> First the few details:
> Kernel: 4.9.20
> Machi
On Thu, Apr 5, 2018 at 1:09 PM, Anders Roxell wrote:
> gcc warns that 'heap_type' is not initialized if we don't come through
> any of the two 'case' statesments before:
>
> ionapp_export.c:91:2: warning: ‘heap_type’ may be used uninitialized in
> this function [-Wmaybe-uninitialized]
> printf("
Hi,
First the few details:
Kernel: 4.9.20
Machine: x86_64 (AMD)
Model: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
Cores: 8
Available clock source:
# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
tsc hpet acpi_pm
Problem:
[ 28.027409] NMI watchdog: Watchdog detected hard L
On Thu, Mar 8, 2018 at 7:18 PM, Anders Roxell wrote:
> gcc warns that 'heap_type' is not initialized if we don't come through
> any of the two 'case' statesments before:
>
OK thanks for your patch.
> ionapp_export.c:91:2: warning: ‘heap_type’ may be used uninitialized in
> this function [-Wmaybe
On Thu, Feb 8, 2018 at 9:41 PM, Lynch, Nathan wrote:
>> I commented the device tree reading property:
>> arm,cpu-registers-not-fw-configured , from the arch/arm/kernel/vdso.c
>
> Don't do that, please. The presence of that property indicates that the
> counter is not suitable for use by the OS. T
rote:
> On Thu, Dec 14, 2017 at 10:50:50AM +0530, Pintu Kumar wrote:
>> Oh ok. Thanks for this information.
>> So, in conclusion, can I summarize like this: VDSO support on ARM 32-bit
>> 1) VDSO works only on Cortex A7/A15 -> where generic timer extension
>> is availabl
On Wed, Feb 7, 2018 at 5:22 AM, Daniel Díaz wrote:
> The Makefile lacks a couple of line continuation backslashes
> in an `if' clause, which can make the subsequent rsync
> command go awry over the whole filesystem (`rsync -a / /`).
>
> /bin/sh: -c: line 5: syntax error: unexpected end of file
>
On Wed, Feb 7, 2018 at 10:46 PM, Daniel Díaz Rodríguez
wrote:
> Hello!
>
>
> On 7 February 2018 at 00:01, Pintu Kumar wrote:
> [...]
>> Thanks for your patch.
>> However, I have copied this Makefile from
>> tools/testing/selftests/futex/Makefile before modifying
On Wed, Feb 7, 2018 at 5:22 AM, Daniel Díaz wrote:
> The Makefile lacks a couple of line continuation backslashes
> in an `if' clause, which can make the subsequent rsync
> command go awry over the whole filesystem (`rsync -a / /`).
>
> /bin/sh: -c: line 5: syntax error: unexpected end of file
>
On Mon, Feb 5, 2018 at 7:24 PM, Masami Hiramatsu wrote:
> On Mon, 5 Feb 2018 15:17:41 +0530
> Pintu Kumar wrote:
>
>> On Sat, Feb 3, 2018 at 6:49 PM, Masami Hiramatsu wrote:
>> > Hi Pintu,
>> >
>> > On Fri, 2 Feb 2018 19:03:30 +0530
>> > Pintu
On Sat, Feb 3, 2018 at 6:49 PM, Masami Hiramatsu wrote:
> Hi Pintu,
>
> On Fri, 2 Feb 2018 19:03:30 +0530
> Pintu Kumar wrote:
>
>> Hi All,
>>
>> I have fixed both the issue with perf test.
>>
>> 1) 16: Try 'import perf' in python, checki
o fix this issue I had to enable full version of CONFIG_DEBUG_INFO in kernel.
Now, my question is:
Is it possible to pass BPF test without enabling CONFIG_DEBUG_INFO in kernel ?
Thanks,
Pintu
On Fri, Feb 2, 2018 at 1:25 PM, Pintu Kumar wrote:
> Hi,
>
> perf test bpf prologue ge
Is there any fix available for this issue?
I searched 4.15, but could not relate any of the patches to this.
Thanks,
Pintu
On Thu, Feb 1, 2018 at 7:34 PM, Pintu Kumar wrote:
> Hi,
>
> After enabling DEBUG_INFO in kernel I still get this error for BPF test.
> Please help.
no member f_mode.
An error occurred in debuginfo analysis (-22).
bpf_probe: failed to convert perf probe eventsFailed to add events
selected by BPF
test child finished with -1
end
Test BPF filter subtest 1: FAILED!
On Thu, Feb 1, 2018 at 10:50 AM, Pintu Kumar wrote:
> Dear Masami,
>
Hiramatsu wrote:
> On Tue, 30 Jan 2018 19:20:36 +0530
> Pintu Kumar wrote:
>
>> On Tue, Jan 30, 2018 at 11:13 AM, Masami Hiramatsu
>> wrote:
>> >
>> > On Mon, 29 Jan 2018 22:00:52 +0530
>> > Pintu Kumar wrote:
>> >
>> > > De
On Tue, Jan 30, 2018 at 11:13 AM, Masami Hiramatsu wrote:
>
> On Mon, 29 Jan 2018 22:00:52 +0530
> Pintu Kumar wrote:
>
> > Dear Masami,
> >
> > Thank you so much for your reply.
> > Please find some of my answers inline.
> >
> >
> > On Mon,
Dear Masami,
Thank you so much for your reply.
Please find some of my answers inline.
On Mon, Jan 29, 2018 at 7:47 PM, Masami Hiramatsu wrote:
> On Mon, 29 Jan 2018 13:40:34 +0530
> Pintu Kumar wrote:
>
>> Hi All,
>>
>> 'perf probe' is failing sometimes o
2018 at 7:09 PM, Pintu Kumar wrote:
> Hi,
>
> ** Changed the subject now, since these issues are related to general
> perf commands.
>
> Following are the issues:
>
> 1) perf probe --add schedule - FAILED
> output:
> schedule is out of .text, skip it.
> Error:
ING_DIR=/lib/modules/4.9.20-sc-amd-x86-64/build
If you have any clue about these failure please help me.
Thanks,
Pintu
On Wed, Jan 24, 2018 at 8:23 PM, Pintu Kumar wrote:
> Hi,
>
> Thanks for your help.
> Yes it was a sub version issue.
>
> Earlier, while building the k
F file
bpf_probe: failed to convert perf probe eventsFailed to add events
selected by BPF
test child finished with -1
end
Test BPF filter subtest 1: FAILED!
Thanks,
Pintu
On Wed, Jan 24, 2018 at 6:39 AM, Wangnan (F) wrote:
>
>
> On 2018/1/23 20:37, Pintu Kumar wrote:
>>
&
Hi All,
I am verifying all perf tests on Ubuntu-16 x86-64 platform using the
kernel version 4.9.20.
I have installed several others packages including: clang, llvm
But, when I run 'perf test' I get some FAILURE.
Specially, 'perf test LLVM' is failing.
Please check the below error logs:
Hi All,
Did anybody tried running vdso_test (under Documentation/vDSO in
kernel 4.1) on an ARM 32 bit system?
When I test it on iMX.7 board (kernel 4.1, ARM 32 bit), I get this:
# ./vdso_test
Could not find __vdso_gettimeofday
When I check more in parse_vdso.c, I found that under vdso_sym
functi
On Wed, Nov 22, 2017 at 9:45 PM, Jon Hunter wrote:
>
> On 22/11/17 12:26, Pintu Kumar wrote:
>> Hello Jon,
>> Yes I raised my query there almost 1 week back here.
>> https://devtalk.nvidia.com/default/topic/1026527/jetson-tx2/-jetson-tx2-mmc-resume-errors-after-booting-fr
C driver between upstream and
>> downstream are currently quite diverged so the upstream folks are
>> unlikely to be able to help with issues with the downstream code.
>>
>> Mikko
>>
>> On 22.11.2017 08:41, Pintu Kumar wrote:
>>> Hi,
>>>
>>>
)
-
On Mon, Nov 20, 2017 at 12:48 PM, Pintu Kumar wrote:
> Hi,
>
> I am trying to verify suspend-to-disk on jetson-tx2 board (nvidia tegra186).
> Suspend is working fine, but during resume emmc is failing to resume.
> Kern
Hi,
I am trying to verify suspend-to-disk on jetson-tx2 board (nvidia tegra186).
Suspend is working fine, but during resume emmc is failing to resume.
Kernel version: 4.4
Repo: https://nv-tegra.nvidia.com/gitweb/?p=linux-4.4.git;a=summary
It returns with:
mmc0: error -110 during resume (card was
On Tue, Nov 7, 2017 at 4:21 AM, Enrico Weigelt, metux IT consult
wrote:
> On 26.10.2017 18:26, Pintu Kumar wrote:
>>
>> Hi,
>>
>> My proposal is to maintain a common base defconfig file for all ARM
>> products and only add the additional configs in the new defco
On Fri, Nov 3, 2017 at 6:02 AM, Shuah Khan wrote:
> On 11/02/2017 05:54 PM, Laura Abbott wrote:
>> On 11/02/2017 10:53 AM, Shuah Khan wrote:
>>> On 11/02/2017 10:19 AM, Shuah Khan wrote:
>>>> On 11/02/2017 10:15 AM, Pintu Kumar wrote:
>>>>> On T
On Thu, Nov 2, 2017 at 8:37 PM, Shuah Khan wrote:
> Hi Pintu,
>
> On 11/01/2017 11:00 AM, Pintu Agarwal wrote:
>> This is a test utility to verify ION buffer sharing in user space
>> between 2 independent processes.
>> It uses unix domain socket (with SCM_RIGHTS) as IPC to transfer an FD to
>> ano
On Wed, Nov 1, 2017 at 10:27 PM, Shuah Khan wrote:
> On 11/01/2017 10:26 AM, Pintu Kumar wrote:
>> On Wed, Nov 1, 2017 at 8:34 PM, Shuah Khan wrote:
>>> On 11/01/2017 04:12 AM, Pintu Kumar wrote:
>>>> On Wed, Nov 1, 2017 at 3:28 AM, Laura Abbott wrote:
>>>
On Wed, Nov 1, 2017 at 8:34 PM, Shuah Khan wrote:
> On 11/01/2017 04:12 AM, Pintu Kumar wrote:
>> On Wed, Nov 1, 2017 at 3:28 AM, Laura Abbott wrote:
>>> On 10/31/2017 03:21 AM, Pintu Kumar wrote:
>>>> On Tue, Oct 31, 2017 at 2:32 AM, Laura Abbott wrote:
>&
On Wed, Nov 1, 2017 at 3:28 AM, Laura Abbott wrote:
> On 10/31/2017 03:21 AM, Pintu Kumar wrote:
>> On Tue, Oct 31, 2017 at 2:32 AM, Laura Abbott wrote:
>>> On 10/30/2017 12:12 AM, Pintu Kumar wrote:
>>>> On Sun, Oct 29, 2017 at 7:51 PM, kernel test robot
>>&g
On Tue, Oct 31, 2017 at 2:32 AM, Laura Abbott wrote:
> On 10/30/2017 12:12 AM, Pintu Kumar wrote:
>> On Sun, Oct 29, 2017 at 7:51 PM, kernel test robot
>> wrote:
>>>
>>> FYI, we noticed the following commit (built with gcc-6):
>>>
>>> commit:
/testing/selftests/android/ion/Makefile
>> new file mode 100644
>> index 000..1399a5e
>> --- /dev/null
>> +++ b/tools/testing/selftests/android/ion/Makefile
>> @@ -0,0 +1,16 @@
>> +
>> +INCLUDEDIR := -I../../../../../drivers/staging/android/uapi/
On Sun, Oct 29, 2017 at 7:51 PM, kernel test robot
wrote:
>
> FYI, we noticed the following commit (built with gcc-6):
>
> commit: 5fb70554d68e2ea032b6a28b082801d8b7b76cb8 ("android/ion: userspace
> test utility for ion buffer sharing")
> url:
> https://github.com/0day-ci/linux/commits/Pintu-Aga
On Fri, Oct 27, 2017 at 2:15 PM, Greg Kroah-Hartman
wrote:
> On Fri, Oct 27, 2017 at 11:04:49AM +0530, Pintu Kumar wrote:
>> Dear Laura, Shuah,
>>
>> Request you to please review the PATCHv4.
>
> A response with only 3 days, while everyone is traveling at conferences,
&
ST_PROGS := ion_test.sh
> +
> +include ../../lib.mk
> +
> +$(OUTPUT)/ionapp_export: ionapp_export.c ipcsocket.c ionutils.c
> +$(OUTPUT)/ionapp_import: ionapp_import.c ipcsocket.c ionutils.c
> diff --git a/tools/testing/selftests/android/ion/README
> b/tools/testing/selftes
Hi,
My proposal is to maintain a common base defconfig file for all ARM
products and only add the additional configs in the new defconfig
file.
I am not sure if this is already possible. If this is possible please
let us know the steps.
For example:
Under arch/arm/configs , there are more than 10
On Sat, Oct 21, 2017 at 12:51 AM, Shuah Khan wrote:
> On 10/20/2017 09:18 AM, Pintu Kumar wrote:
>> On Fri, Oct 20, 2017 at 8:10 PM, Shuah Khan wrote:
>>> On 10/18/2017 04:38 AM, Pintu Kumar wrote:
>>>> On Wed, Oct 18, 2017 at 2:28 AM, Shuah Khan wrote:
>&
On Fri, Oct 20, 2017 at 8:10 PM, Shuah Khan wrote:
> On 10/18/2017 04:38 AM, Pintu Kumar wrote:
>> On Wed, Oct 18, 2017 at 2:28 AM, Shuah Khan wrote:
>>> On 10/17/2017 02:21 PM, Laura Abbott wrote:
>>>> On 10/14/2017 04:36 AM, Pintu Agarwal wrote:
>>>
7e6f39
>>> --- /dev/null
>>> +++ b/tools/testing/selftests/android/ion/.gitignore
>>> @@ -0,0 +1,2 @@
>>> +ionapp_export
>>> +ionapp_import
>>> diff --git a/tools/testing/selftests/android/ion/Makefile
>>> b/tools/testing/selftests/androi
On Fri, Oct 6, 2017 at 7:58 PM, Pintu Kumar wrote:
>>> +
>>> + heap_type = ion_info->heap_type;
>>> + heap_size = ion_info->heap_size;
>>> + flag_type = ion_info->flag_type;
>>> + alloc_data.len = heap_size;
>>> +
>> +
>> + heap_type = ion_info->heap_type;
>> + heap_size = ion_info->heap_size;
>> + flag_type = ion_info->flag_type;
>> + alloc_data.len = heap_size;
>> + alloc_data.heap_id_mask = heap_type;
>
> The heap type and heap ID are not the same thing. You need
> to determine the hea
{
>> + fprintf(stderr, "<%s>: Failed opensocket.\n", __func__);
>> + goto err_socket;
>> + }
>> + skinfo.sockfd = sockfd;
>> +
>> + ret = ion_export_buffer_fd(&info);
>> + if (ret < 0) {
&
On Wed, Oct 4, 2017 at 12:50 PM, Greg KH wrote:
> On Tue, Oct 03, 2017 at 12:48:59PM -0400, Pintu Agarwal wrote:
>> This is a test utility to verify ION buffer sharing in user space
>> between 2 independent processes.
>> It uses unix domain socket as IPC to transfer an FD to another process
>> and
On Sun, Oct 1, 2017 at 10:33 PM, Mike Galbraith wrote:
> On Sun, 2017-10-01 at 09:48 -0700, Randy Dunlap wrote:
>> On 10/01/17 09:44, Damian Tometzki wrote:
>>
>> > i resolved the issue with:
>> > sudo /etc/init.d/apparmor stop
>>
>> or boot with: apparmor=0
>
> or systemctl mask apparmor
Ok, tha
On Sat, Sep 30, 2017 at 10:55 AM, Theodore Ts'o wrote:
> On Sat, Sep 30, 2017 at 09:28:09AM +0530, Pintu Kumar wrote:
>> I need to submit a patch to mainline which should be verified against
>> linux-next tree with latest API.
>
> If you want to verify a patch that you
On Thu, Sep 28, 2017 at 11:46 PM, Pintu Kumar wrote:
> On Thu, Sep 28, 2017 at 11:41 PM, Pintu Kumar wrote:
>> On Wed, Sep 27, 2017 at 7:54 PM, Pintu Kumar wrote:
>>> On Wed, Sep 27, 2017 at 12:52 AM, Laura Abbott wrote:
>>>> On 09/26/2017 11:08 AM, Pintu Agarwa
Thanks Mr. Tso for your reply.
Please find my reply inline.
On Sat, Sep 30, 2017 at 3:20 AM, Theodore Ts'o wrote:
> On Fri, Sep 29, 2017 at 07:56:41PM +0530, Pintu Kumar wrote:
>> BTW, I am more interested in my another query about QEMU arm.
>> This will be much quicker and
On Fri, Sep 29, 2017 at 7:56 PM, Pintu Kumar wrote:
> On Fri, Sep 29, 2017 at 6:44 PM, Damian Tometzki
> wrote:
>> Hello,
>>
>> Ubuntu 16.04 with current linux-next Kernel workson virtualbox 5.1.28
>>
>> Host: Windows 10
>> Guest: Ubuntu 16.04
>&g
ieb
> valdis.kletni...@vt.edu:
>> On Fri, 29 Sep 2017 16:08:07 +0530, Pintu Kumar said:
>>
>> >
>> > I have a general question.
>> > How do we normally verify linux-next tree?
>> The same exact way you "verify" any other Linux kernel, for wha
Hi,
I have a general question.
How do we normally verify linux-next tree?
I wanted to work on linux-next but I am facing some issues.
I could able to build linux-next for both x86 and arm, but I could not
verify it on any machine.
Currently I don't have a real Linux PC to boot with linux-next ker
f any better option to use linux-next please tell me.
It will be really helpful.
Thank You!
Regards,
Pintu
On Fri, Sep 29, 2017 at 3:12 PM, Pintu Kumar wrote:
> Hi,
>
> I have a general question.
> How do we normally verify linux-next tree?
>
> I wanted to work on linux-ne
Hi,
I have a general question.
How do we normally verify linux-next tree?
I wanted to work on linux-next but I am facing some issues.
I could able to build linux-next for both x86 and arm, but I could not
verify it on any machine.
Currently I don't have a real Linux PC to boot with linux-next ker
On Thu, Sep 28, 2017 at 11:41 PM, Pintu Kumar wrote:
> On Wed, Sep 27, 2017 at 7:54 PM, Pintu Kumar wrote:
>> On Wed, Sep 27, 2017 at 12:52 AM, Laura Abbott wrote:
>>> On 09/26/2017 11:08 AM, Pintu Agarwal wrote:
>>>>
>>>> This is a test utility
On Wed, Sep 27, 2017 at 7:54 PM, Pintu Kumar wrote:
> On Wed, Sep 27, 2017 at 12:52 AM, Laura Abbott wrote:
>> On 09/26/2017 11:08 AM, Pintu Agarwal wrote:
>>>
>>> This is a test utility to verify ION buffer sharing in user space
>>> between 2 independen
On Wed, Sep 27, 2017 at 12:52 AM, Laura Abbott wrote:
> On 09/26/2017 11:08 AM, Pintu Agarwal wrote:
>>
>> This is a test utility to verify ION buffer sharing in user space
>> between 2 independent processes.
>> It uses unix domain socket as IPC to transfer an FD to another process
>> and install
+ *
> + * It is a user space utility to create and export android
> + * ion memory buffer fd to another process using unix domain socket as IPC.
> + * This acts like a server for ionapp_import(client).
> + * So, this server has to be started first before the client.
> + *
> + * Copy
On Wed, Sep 13, 2017 at 1:05 PM, Konstantin Khlebnikov
wrote:
> On 13.09.2017 07:51, PINTU KUMAR wrote:
>>
>>
>>
>> Hi,
>>
>> I have submitted a similar patch 2 years ago (Oct/2015).
>> But at that time the patch was rejected.
>> Here is
Dear Ankur,
I would suggest you register to linux...@kvack.org and explain your issues in
details.
There are other experts here, who can guide you.
Few comments are inline below.
> From: Ankur Tank [mailto:ankur.t...@lnttechservices.com]
> Sent: Saturday, September 10, 2016 5:26 PM
> To: pint..
Hi,
> -Original Message-
> From: vinayak menon [mailto:vinayakm.l...@gmail.com]
> Sent: Thursday, August 11, 2016 10:23 AM
> To: PINTU KUMAR
> Cc: Pavel Machek; Konstantin Khlebnikov; Minchan Kim; linux-
> ker...@vger.kernel.org; linux...@kvack.org; jaejoon@sa
Hi,
> -Original Message-
> From: Pavel Machek [mailto:pa...@ucw.cz]
> Sent: Saturday, August 06, 2016 2:20 AM
> To: PINTU KUMAR
> Cc: 'Minchan Kim'; linux-kernel@vger.kernel.org; linux...@kvack.org;
> jaejoon@samsung.com; jy0.j...@samsung.com; vishnu.
Hi,
> -Original Message-
> From: Minchan Kim [mailto:minc...@kernel.org]
> Sent: Friday, August 05, 2016 1:50 PM
> To: PINTU KUMAR
> Cc: linux-kernel@vger.kernel.org; linux...@kvack.org;
> jaejoon@samsung.com; jy0.j...@samsung.com; vishnu...@samsung.com
> S
Hi All,
For one of our ARM embedded product, we recently updated the Kernel version from
3.4 to 3.18 and we noticed that the same application memory usage (PSS value)
gone up by ~10% and for some cases it even crossed ~50%.
There is no change in platform part. All platform component was built with
Hi,
Need a help or some pointer about this issue.
Yesterday, received one kernel panic issue on one of our mobile device.
Scenario is: Sender is sending an MMS content to its own number. After MMS is
received, device vibrates and immediately went into kernel panic.
We checked and could not found a
Hi,
> -Original Message-
> From: David Rientjes [mailto:rient...@google.com]
> Sent: Thursday, October 15, 2015 3:35 AM
> To: PINTU KUMAR
> Cc: a...@linux-foundation.org; minc...@kernel.org; d...@stgolabs.net;
> mho...@suse.cz; koc...@gmail.com; han...@cmpxchg.org
Hi,
Thank you very much for your review and comments.
> -Original Message-
> From: David Rientjes [mailto:rient...@google.com]
> Sent: Wednesday, October 14, 2015 8:36 AM
> To: Pintu Kumar
> Cc: a...@linux-foundation.org; minc...@kernel.org; d...@stgolabs.net;
> m
logs.
Signed-off-by: Pintu Kumar
---
V2: Removed oom_stall, Suggested By: Michal Hocko
Renamed oom_kill_count to nr_oom_victims,
Suggested By: Michal Hocko
Suggested By: Anshuman Khandual
include/linux/vm_event_item.h |1 +
mm/oom_kill.c |2 ++
mm/page_alloc.c
Hi,
Sorry, I forgot to mention the V2 update.
I will highlight the V2 changes and RESEND.
> -Original Message-
> From: Pintu Kumar [mailto:pint...@samsung.com]
> Sent: Monday, October 12, 2015 7:03 PM
> To: a...@linux-foundation.org; minc...@kernel.org; d...@stgolabs
logs.
Signed-off-by: Pintu Kumar
---
include/linux/vm_event_item.h |1 +
mm/oom_kill.c |2 ++
mm/page_alloc.c |1 -
mm/vmstat.c |1 +
4 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/include/linux/vm_event_item.h b/include
> -Original Message-
> From: Michal Hocko [mailto:mho...@kernel.org]
> Sent: Thursday, October 08, 2015 10:01 PM
> To: PINTU KUMAR
> Cc: a...@linux-foundation.org; minc...@kernel.org; d...@stgolabs.net;
> koc...@gmail.com; rient...@google.com; han...@cmpxchg.org; p
Hi,
Thank you very much for your reply and comments.
> -Original Message-
> From: Michal Hocko [mailto:mho...@kernel.org]
> Sent: Thursday, October 08, 2015 7:49 PM
> To: PINTU KUMAR
> Cc: a...@linux-foundation.org; minc...@kernel.org; d...@stgolabs.net;
> koc..
Hi,
> -Original Message-
> From: Michal Hocko [mailto:mho...@kernel.org]
> Sent: Tuesday, October 06, 2015 9:12 PM
> To: PINTU KUMAR
> Cc: a...@linux-foundation.org; minc...@kernel.org; d...@stgolabs.net;
> koc...@gmail.com; rient...@google.com; han...@cmpxchg.org; p
Hi,
> -Original Message-
> From: Michal Hocko [mailto:mho...@kernel.org]
> Sent: Monday, October 05, 2015 5:53 PM
> To: PINTU KUMAR
> Cc: a...@linux-foundation.org; minc...@kernel.org; d...@stgolabs.net;
> koc...@gmail.com; rient...@google.com; han...@cmpxchg.org; p
Hi,
> -Original Message-
> From: Anshuman Khandual [mailto:khand...@linux.vnet.ibm.com]
> Sent: Thursday, October 01, 2015 7:00 PM
> To: Pintu Kumar; a...@linux-foundation.org; minc...@kernel.org;
> d...@stgolabs.net; mho...@suse.cz; koc...@gmail.com; rient...@go
Hi,
> -Original Message-
> From: Michal Hocko [mailto:mho...@kernel.org]
> Sent: Thursday, October 01, 2015 7:09 PM
> To: Pintu Kumar
> Cc: a...@linux-foundation.org; minc...@kernel.org; d...@stgolabs.net;
> koc...@gmail.com; rient...@google.com; han...@cmpxchg.org; p
are 610 times, kernel entered into OOM
cases. However, there were around 1763 oom killing happens.
The OOM is bad for the any system. So, this counter can help the developer
in tuning the memory requirement at least during initial bringup.
Signed-off-by: Pintu Kumar
---
include/linux
1 - 100 of 149 matches
Mail list logo
