From: Andrew Fish <afish@apple.com>
To: prabin ca <prabinca4u@gmail.com>
Cc: Laszlo Ersek <lersek@redhat.com>,
edk2-devel@lists.01.org, dandan.bi@intel.com
Subject: Re: Performance enabling of Event handler
Date: Thu, 06 Sep 2018 19:58:25 -0700 [thread overview]
Message-ID: <17A8CCBE-71A5-44E3-BBAC-7F067D5EB651@apple.com> (raw)
In-Reply-To: <F8ED7AD9-54F4-49D8-BF61-88B39DE3975F@gmail.com>
Prabin,
Last time I looked every call to PERF_START()/PERF_END() creates a new performance record. So it does not work well for a function that is called a large number of times.
Thanks,
Andrew Fish
> On Sep 6, 2018, at 7:30 PM, prabin ca <prabinca4u@gmail.com> wrote:
>
> Hi,
> PerformancePkg is not working with event handlers, but it’s working with normal functions handlers.
>
>> On 06-Sep-2018, at 3:28 PM, Laszlo Ersek <lersek@redhat.com> wrote:
>>
>>> On 09/06/18 08:10, prabin ca wrote:
>>> Hi Team,
>>>
>>> I’m used edk2 PerformancePkg for profiling cpu execution time taken by a event handler. Event is created successfully and event handler is also called successfully, but I can capture the performance of this event handler with PerformancePkg (by using perf_start and perf_end check points). This PerformancePkg is working fine with normal function calls.
>>
>> Do you mean "can not", instead of "can"? (Sorry, I don't understand.)
>>
>>>
>>> Please help me to enable PerformancePkg action on event handler also.
>>>
>>
>> Hmmm, even with the suggested typo correction, I wouldn't know what to
>> suggest. Sorry!
>>
>> Laszlo
next prev parent reply other threads:[~2018-09-07 2:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 6:10 Performance enabling of Event handler prabin ca
2018-09-06 9:58 ` Laszlo Ersek
2018-09-07 2:30 ` prabin ca
2018-09-07 2:58 ` Andrew Fish [this message]
2018-09-07 3:16 ` Bi, Dandan
2018-09-07 15:57 ` prabin ca
2018-09-08 4:15 ` Bi, Dandan
2018-09-10 15:03 ` prabin ca
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-list 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=17A8CCBE-71A5-44E3-BBAC-7F067D5EB651@apple.com \
--to=devel@edk2.groups.io \
/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