Hi,
I wanted to develop a dummy interrupt handler for an ARM board which
is connected to a remote location. This is required for some debugging
purpose during the interrupt context.
It does not have a keyboard or any GPIO pins.
So, I wonder how to develop a custom interrupt handler, may be using
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 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
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
Hi,
I need some help on QEMU environment setup for ARM so that I am very
my custom Linux Kernel changes for arm.
I know there are lots of references available on internet. Earlier I
spend lots of time and finally I could able to setup basic qemu
working but still I was not completely satisfied. No
On Fri, Feb 9, 2018 at 12:52 AM, Neil Thomas wrote:
> Thanks, I will check it out.
>
> On 09-Feb-2018 12:50 AM, wrote:
>>
>> On Thu, 08 Feb 2018 23:38:01 +0530, Neil Thomas said:
>>
>> > I am just a beginner. I have tried procfs, Netlink socket to communicate
>> > between user space and kernel sp
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:
On Wed, Oct 11, 2017 at 10:21 PM, Greg KH wrote:
> On Wed, Oct 11, 2017 at 08:38:52PM +0530, Pintu Kumar wrote:
>> Yes, I have seen many documentation and also the existing repos under
>> selftests.
>> But my requirement is little different.
>> I think my requirem
On Tue, Oct 10, 2017 at 7:44 PM, Greg KH wrote:
> On Tue, Oct 10, 2017 at 01:15:11PM +0530, Pintu Kumar wrote:
>> Hi All,
>>
>> Is anybody familiar with ktests of selftests framework under: tool/testing/ ?
>> I have some queries.
>>
>> 1) What is the differ
another way?
If anybody have already done a new addition in selftests, please let me know.
Thanks,
Pintu
On Tue, Oct 10, 2017 at 1:15 PM, Pintu Kumar wrote:
> Hi All,
>
> Is anybody familiar with ktests of selftests framework under: tool/testing/ ?
> I have some queries.
>
&
Hi All,
Is anybody familiar with ktests of selftests framework under: tool/testing/ ?
I have some queries.
1) What is the difference between ktests and selftests ? How to choose ?
2) How to invoke a test under ktests?
For example:
I have some user space C program, that tests some kernel d
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
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
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
33 matches
Mail list logo
