public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: Sandeepa Prabhu <sandeepa.prabhu@linaro.org>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	       systemtap@sourceware.org,
	Deepak Saxena <dsaxena@linaro.org>
Subject: Re: Regarding systemtap support for AArch64
Date: Mon, 14 Oct 2013 16:38:00 -0000	[thread overview]
Message-ID: <525C1DFE.1020100@redhat.com> (raw)
In-Reply-To: <CA+b37P2Bh_=YypANEhcLKv_M-AFRJF17EPJA2R3HMzJ-595O0g@mail.gmail.com>

On 10/08/2013 12:39 AM, Sandeepa Prabhu wrote:
> On 8 October 2013 09:58, Sandeepa Prabhu <sandeepa.prabhu@linaro.org> wrote:
>>>
>>> Hi Sandeepa,
>>>
>>> The fedora 19 work is publicly available.  The following page talks about setting things up:
>>>
>>> http://fedoraproject.org/wiki/Architectures/ARM/AArch64/QuickStart
>>>
>>> -Will
>> Hi Will,
>>
>> Thanks, I could get the console, but very slow.  Where can I look for
>> kernel sources and the systemtap packages? Wanted to try my kernel
>> changes on this and experiment systemtap, I can clone and create
>> kernel devel branch on linaro git for kprobes, if this work out well.
>>
> This is single CPU version, has it been tested on 4-core models
> (RTSM)? Responsiveness might improve with 4-core model [atleast LAMP
> stack run faster]
> 
>> Thanks,
>> Sandeepa

Hi Sandeepa,

Yes, the Foundation model is very slow.  I have read that there has been some work to get aarch64 support in qemu, but I have not personally tried it:

http://news.opensuse.org/2013/10/01/suse-speeds-up-building-aarch64-software-in-qemu/

For systemtap your best bet is to use a git clone which has the current aarch64 patches:

git clone git://sourceware.org/git/systemtap.git

Then build (you may need to do a "yum-builddep systemtap" as root to pull in dependencies that systemtap needs to build):

cd systemtap
./configure --disable-docs
make
make install

At this point should have a systemtap that will build stuff for aarch64

For the current state of aarch64 package you can look at what is in http://arm-temp.ausil.us/pub/fedora-arm/stage4/
Each of the packages is in a subdirectory.  You should be able to do something like the following to get the sources:

wget http://arm-temp.ausil.us/pub/fedora-arm/stage4/kernel-3.12.0-0.rc4.git0.1.x2.fc19/kernel-3.12.0-0.rc4.git0.1.x2.fc19.src.rpm
rpm -Uvh kernel*.src.rpm
cd rpmbuild/SPECS
yum-builddep kernel
rpmbuild -bp kernel.spec

Generally when fedora builds kernels it produces a /boot/config-`uname -r` file describing the configure used to build the kernel.  This is in the kernel rpm.  I don't recall if the kernel rpm is installed in the basic aarch64 image.  You may need to do a "yum install kernel" to get that installed on the machine.

-Will

  reply	other threads:[~2013-10-14 16:38 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24  3:13 Sandeepa Prabhu
2013-09-24  8:43 ` Mark Wielaard
2013-09-24  9:36   ` Sandeepa Prabhu
2013-09-25 18:45   ` William Cohen
2013-09-26  3:13     ` Sandeepa Prabhu
2013-09-26 14:35       ` William Cohen
2013-09-26 14:57         ` Sandeepa Prabhu
2013-09-27 14:16           ` William Cohen
2013-09-30  2:36       ` Masami Hiramatsu
2013-09-30  2:57         ` Sandeepa Prabhu
2013-09-30 12:11         ` William Cohen
2013-10-02  4:17           ` Sandeepa Prabhu
2013-10-02 11:24             ` Masami Hiramatsu
2013-10-03  3:12               ` Sandeepa Prabhu
2013-10-03 13:01                 ` Masami Hiramatsu
2013-10-04  3:24                   ` Sandeepa Prabhu
2013-10-05  3:24                     ` Masami Hiramatsu
2013-10-07  9:51                       ` Sandeepa Prabhu
2013-10-07 10:11                         ` Masami Hiramatsu
2013-10-07 11:12                           ` Sandeepa Prabhu
2013-10-15  9:39                             ` Masami Hiramatsu
2013-10-24  4:26                               ` Sandeepa Prabhu
2013-10-24  5:08                                 ` Masami Hiramatsu
2013-10-04 15:57             ` William Cohen
2013-10-07  9:26               ` Sandeepa Prabhu
2013-10-08  4:28               ` Sandeepa Prabhu
2013-10-08  4:39                 ` Sandeepa Prabhu
2013-10-14 16:38                   ` William Cohen [this message]
2013-10-14 21:21                     ` William Cohen
2013-10-15  2:29                       ` Sandeepa Prabhu
2013-10-15  3:02                         ` William Cohen
2013-10-16  2:33                       ` William Cohen
2013-10-16  2:38                     ` William Cohen
2013-10-24  1:50             ` William Cohen
2013-10-24  4:19               ` Sandeepa Prabhu
2013-10-24 13:49                 ` William Cohen
2013-10-28 14:03                 ` William Cohen
2013-11-01 21:06                   ` William Cohen
2013-09-25  4:42 ` Masami Hiramatsu
2013-12-02 15:45 ` An attempt for systemtap "make installcheck" AArch64 William Cohen
2013-12-03  5:25   ` Sandeepa Prabhu
2013-12-03 15:21     ` William Cohen
2013-12-03 16:36       ` William Cohen
2013-12-09 20:35         ` William Cohen
2013-12-16  6:06           ` Sandeepa Prabhu
2013-12-16 12:41             ` William Cohen
2013-12-03 19:48       ` William Cohen

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=525C1DFE.1020100@redhat.com \
    --to=wcohen@redhat.com \
    --cc=dsaxena@linaro.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=sandeepa.prabhu@linaro.org \
    --cc=systemtap@sourceware.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).