From: Alan Mikhak <alanmikhak@gmail.com>
To: Yordan Karadzhov <ykaradzhov@vmware.com>
Cc: "linux-trace-devel@vger.kernel.org"
<linux-trace-devel@vger.kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
Alan Mikhak <amikhak@wirelessfabric.com>
Subject: Re: [PATCH] Fix compiler error in KsSession.cpp on Raspberry Pi 3
Date: Wed, 12 Jun 2019 08:22:22 -0700 [thread overview]
Message-ID: <CAOY98NeuPDgnpiHZqepa1gBuSjaDuyOgySccBeuRwLj4XdVe+g@mail.gmail.com> (raw)
In-Reply-To: <b0108c01-00f4-fc5e-7fef-03e6984f361e@vmware.com>
On Wed, Jun 12, 2019 at 12:34 AM Yordan Karadzhov <ykaradzhov@vmware.com> wrote:
> On 12.06.19 г. 6:59 ч., Alan Mikhak wrote:
> > Fix compiler error at KsSession.cpp:457:30 on Raspberry Pi 3
::
> I am really curious to know how does KernelShark look and feel on
> Raspberry Pi. Would you shared with us your impressions.
> Honestly, I will be surprised if everything works fine ;)
>
Hi Yordan,
KernelShark launches on my Raspberry Pi 3 model B+, loads my trace
file, renders the screen elements, and is responsive. I have enabled a
swap file and GPU acceleration with extra memory for the GPU. From
looking at the code, rendering may even work on the CPU without
acceleration, but haven't tried it.
The abort issue on libkshark-model.c:242 currently limits KernelShark
on my Raspberry Pi 3 model B+:
https://bugzilla.kernel.org/show_bug.cgi?id=203869
Regards,
Alan
next prev parent reply other threads:[~2019-06-12 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 3:59 [PATCH] Fix compiler error in KsSession.cpp on Raspberry Pi 3 Alan Mikhak
2019-06-12 7:34 ` Yordan Karadzhov
2019-06-12 12:12 ` Steven Rostedt
2019-06-12 15:31 ` Alan Mikhak
2019-06-12 15:53 ` Steven Rostedt
2019-06-12 15:22 ` Alan Mikhak [this message]
2019-06-14 4:40 ` Alan Mikhak
2019-06-12 8:17 ` Yordan Karadzhov
2019-06-12 12:11 ` Steven Rostedt
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=CAOY98NeuPDgnpiHZqepa1gBuSjaDuyOgySccBeuRwLj4XdVe+g@mail.gmail.com \
--to=alanmikhak@gmail.com \
--cc=amikhak@wirelessfabric.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=ykaradzhov@vmware.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).