dwarves.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luka Perkov <luka.perkov@sartura.hr>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Tony Ambardar <tony.ambardar@gmail.com>,
	Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	Ilya Leoshkevich <iii@linux.ibm.com>, bpf <bpf@vger.kernel.org>,
	dwarves@vger.kernel.org,
	David Marcinkovic <david.marcinkovic@sartura.hr>,
	Juraj Vijtiuk <juraj.vijtiuk@sartura.hr>,
	Jakov Petrina <jakov.petrina@sartura.hr>
Subject: Re: Problem with endianess of pahole BTF output for vmlinux
Date: Mon, 28 Sep 2020 22:27:27 +0200	[thread overview]
Message-ID: <CAKQ-crg3qdQ6=STwQd5NrWWdQSpuKQptUMfZU50sYATfkqf1cw@mail.gmail.com> (raw)
In-Reply-To: <CAEf4Bzb7LZX8Y=qKpO5j3eUYU=tJzvNRYd1CdXXxq8Y-V4=+Vw@mail.gmail.com>

Hello Andrii,

On Mon, Sep 28, 2020 at 10:19 PM Andrii Nakryiko
<andrii.nakryiko@gmail.com> wrote:
> Question to folks that are working with 32-bit and/or big-endian
> architectures. Do you guys have an VM image that you'd be able to
> share with me, such that I can use it with qemu to test patches like
> this. My normal setup is all 64-bit/little-endian, so testing changes
> like this (and a few more I'm planning to do to address mixed 32-bit
> on the host vs 64-bit in BPF cases) is a bit problematic. And it's
> hard to get superpumped about spending lots of time setting up a new
> Linux image (never goes easy or fast for me).
>
> So, if you do have something like this, please share. Thank you!

We thought this would be an issue and we have been working on this but
didn't finalize it yet.

We'll speed it up and send you an easy way to replicate the
development environment.

Luka and Juraj will also share some of our additional findings
regarding 32bit ARM.

Thanks,
Luka

  reply	other threads:[~2020-09-28 20:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPGftE8ipAacAnm9xMHFabXCL-XrCXGmOsX-Nsjvz9wnh3Zx-w@mail.gmail.com>
     [not found] ` <9e99c5301fbbb4f5f601b69816ee1dc9ab0df948.camel@linux.ibm.com>
     [not found]   ` <CAEf4Bza9tZ-Jj0dj9Ne0fmxa95t=9XxxJR+Ce=6hDmw_d8uVFA@mail.gmail.com>
     [not found]     ` <8cf42e2752e442bb54e988261d8bf3cd22ad00f2.camel@linux.ibm.com>
     [not found]       ` <20200909142750.GC3788224@kernel.org>
2020-09-19  7:58         ` Problem with endianess of pahole BTF output for vmlinux Tony Ambardar
2020-09-21 18:19           ` Andrii Nakryiko
2020-09-28 20:18             ` Andrii Nakryiko
2020-09-28 20:27               ` Luka Perkov [this message]
2020-09-29  3:41               ` Tony Ambardar
2020-09-29  4:15                 ` Andrii Nakryiko
2020-09-29  6:48                   ` Tony Ambardar
2020-09-29 17:36                     ` Juraj Vijtiuk
2020-09-29 17:57                     ` Andrii Nakryiko

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='CAKQ-crg3qdQ6=STwQd5NrWWdQSpuKQptUMfZU50sYATfkqf1cw@mail.gmail.com' \
    --to=luka.perkov@sartura.hr \
    --cc=andrii.nakryiko@gmail.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=david.marcinkovic@sartura.hr \
    --cc=dwarves@vger.kernel.org \
    --cc=iii@linux.ibm.com \
    --cc=jakov.petrina@sartura.hr \
    --cc=juraj.vijtiuk@sartura.hr \
    --cc=tony.ambardar@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).