From: Florian Fainelli <f.fainelli@gmail.com>
To: Shubham Bansal <illusionist.neo@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Russell King - ARM Linux <linux@armlinux.org.uk>
Subject: Re: [PATCH] RFC: arm: eBPF JIT compiler
Date: Thu, 25 May 2017 14:12:30 -0700 [thread overview]
Message-ID: <b5191e43-c8d8-6d9b-8c0f-afb31388e0c5@gmail.com> (raw)
In-Reply-To: <CAHgaXdL0JY4DQdhAtFcMF245rqHLo+Lvt4apaSROzPGjv7pcMg@mail.gmail.com>
On 05/25/2017 01:08 PM, Shubham Bansal wrote:
> Hi Florian,
>
> It would be great if you could help me with it.
>
> Currently, what I am doing is.
>
> root@arm$ ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make -j4
>
> Then I am using Busybox to build the root filesystem
>
> root@arm$ qemu-system-arm -M vexpress-a9 -dtb
> ./linux/arch/arm/boot/dts/vexpress-v2p-ca9.dtb -kernel
> ./linux/arch/arm/boot/zImage -append "root=/dev/mmcblk0
> console=ttyAMA0" -sd ./a9rootfs.ext3 --nographic
>
> Which machine I should use for ARMv6 in QEMU. Which dtb file I should
> use for ? All these questions I have. If anybody knows please let me
> know.
You should use realview-eb-mpcore for instance (ARM11MPCORE is ARMv6).
>
>
> Best,
> Shubham Bansal
>
>
> On Fri, May 26, 2017 at 1:14 AM, Florian Fainelli <f.fainelli@gmail.com> wrote:
>> On 05/25/2017 12:09 PM, Shubham Bansal wrote:
>>> Hi Andrew,
>>>
>>> On Fri, May 26, 2017 at 12:18 AM, Andrew Lunn <andrew@lunn.ch> wrote:
>>>> On Fri, May 26, 2017 at 12:05:23AM +0530, Shubham Bansal wrote:
>>>>> Hi Andrew,
>>>>>
>>>>> My Apologies.
>>>>>
>>>>> I will remove the #ifdef CONFIG_CPU_LITTLE_ENDIAN. Do you have the
>>>>> ARMv6 machine you can test it on?
>>>>
>>>> Sorry, i don't have a v6.
>>>>
>>>> Maybe try kzm with qemu-system-qemu?
>>>
>>> I am afraid I not so familiar with qemu, otherwise I would have tried
>>> to test the code on ARMv5,6,7 myself.
>>> If you can help me with that it would be great, Otherwise I think I
>>> have to wait for someone to test it for ARMv6. Although, I am pretty
>>> sure it would work on that as it worked on ARMv5.
>>
>> Using QEMU is far less complex than the patch you wrote, the tricky
>> point me be to find an ARMv6 root filesystem, unless you build the
>> module into the kernel and let it run its tests.
>> --
>> Florian
--
Florian
next prev parent reply other threads:[~2017-05-25 21:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 18:33 Shubham Bansal
2017-05-23 19:00 ` Russell King - ARM Linux
2017-05-23 19:13 ` Shubham Bansal
2017-05-23 20:34 ` Andrew Lunn
2017-05-23 20:46 ` Andrew Lunn
2017-05-23 20:54 ` Shubham Bansal
2017-05-23 23:25 ` Andrew Lunn
2017-05-24 20:31 ` Shubham Bansal
2017-05-25 16:12 ` Shubham Bansal
2017-05-25 17:00 ` Andrew Lunn
2017-05-25 17:22 ` Andrew Lunn
[not found] ` <CAHgaXd+CVrDEA=E2=23Qp6wk50=dBnFS6TiCtvphTBMjUywrGg@mail.gmail.com>
2017-05-25 18:28 ` Andrew Lunn
2017-05-25 18:35 ` Shubham Bansal
2017-05-25 18:48 ` Andrew Lunn
2017-05-25 19:09 ` Shubham Bansal
2017-05-25 19:44 ` Florian Fainelli
2017-05-25 20:08 ` Shubham Bansal
2017-05-25 20:59 ` Kees Cook
2017-05-25 21:12 ` Florian Fainelli [this message]
2017-05-25 22:10 ` Russell King - ARM Linux
2017-05-23 21:17 ` Shubham Bansal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b5191e43-c8d8-6d9b-8c0f-afb31388e0c5@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=illusionist.neo@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®