This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Regarding systemtap support for AArch64


On 10/14/2013 05:21 PM, William Cohen wrote:
> On 10/14/2013 12:38 PM, William Cohen wrote:
>> 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,
> 
> There is a new fedora image which uses uefi to boot just announce today.  This might be a bit easier to use use that the older image.  The following URL mentions it:
> 
> https://lists.fedoraproject.org/pipermail/arm/2013-October/006964.html
> 
> -Will

Hi Sandeepa,

I have that new aarch64 image set up with a kernel-3.12.0-0.rc4.git0.1.x2.fc19.aarch64 and all the other related software to natively build systemtap and have systemtap build instrumentation natively.  This evening it showed signs of life.  A trivial hello world on the aarch64 foundation simulator:

$ sudo ../install/bin/stap  -v -k -e 'probe begin {printf("hello world\n"); exit()}'
Pass 1: parsed user script and 92 library script(s) using 140944virt/25340res/2736shr/23292data kb, in 4760usr/140sys/5313real ms.
Pass 2: analyzed script: 1 probe(s), 1 function(s), 0 embed(s), 0 global(s) using 141468virt/26264res/2952shr/23816data kb, in 80usr/10sys/90real ms.
Pass 3: translated to C into "/tmp/stapUPFYHe/stap_14454_src.c" using 141468virt/26264res/2952shr/23816data kb, in 10usr/0sys/9real ms.
Pass 4: compiled C into "stap_14454.ko" in 34870usr/3060sys/42182real ms.
Pass 5: starting run.
[62727.772309] stap_14598: systemtap: 2.4/0.156, base: ffffffbffc0a4000, memory: 13data/18text/0ctx/2058net/11alloc kb, probes: 1
hello world
Pass 5: run completed in 80usr/90sys/501real ms.
Keeping temporary directory "/tmp/stapUPFYHe"

Yes, it is really, really slow as seen in the times that each of the passes took. Pass 1 took 5.3 seconds and pass 4 took 42 seconds for this example that didn't have to search any debuginfo information and only had two statements in it.  It is unlikely to be practical for the simulator to run "make installcheck"

-Will


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]