public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Cygwin Patches <cygwin-patches@cygwin.com>
Subject: Re: [PATCH 1/3] Cygwin: New tool: profiler
Date: Mon, 19 Jul 2021 16:43:30 +0100	[thread overview]
Message-ID: <5acddcda-7fa9-e854-911c-27af2f13a22c@dronecode.org.uk> (raw)
In-Reply-To: <616e4815-1b8b-8c3d-0dfc-ff6c6dc6fd85@dronecode.org.uk>

On 19/07/2021 15:23, Jon Turney wrote:
> On 19/07/2021 11:04, Corinna Vinschen wrote:
>> Hi Matt,
>>
>> On Jul 15 21:49, Mark Geisert wrote:
>>> The new tool formerly known as cygmon is renamed to 'profiler'.  For the
>>> name I considered 'ipsampler' and could not think of any others.  I'm 
>>> open
>>> to a different name if any is suggested.
>>>
>>> I decided that a discussion of the pros and cons of this profiler vs the
>>> existing ssp should probably be in the "Profiling Cygwin Programs" 
>>> section
>>> of the Cygwin User's Guide rather than in the help for either.  That
>>> material will be supplied at some point.
>>>
>>> CONTEXT buffers are made child-specific and thus thread-specific since
>>> there is one profiler thread for each child program being profiled.
>>>
>>> The SetThreadPriority() warning comment has been expanded.
>>>
>>> chmod() works on Cygwin so the "//XXX ineffective" comment is gone.
>>>
>>> I decided to make the "sample all executable sections" and "sample
>>> dynamically generated code" suggestions simply expanded comments for 
>>> now.
>>>
>>> The profiler program is now a Cygwin exe rather than a native exe.
>>
>> The patchset LGTM, but for the details I'd like jturney to have a look
>> and approve it eventually.
> 
> Thanks.  I applied these patches.
> 
> A few small issues you might consider addressing in follow-ups.

It also seems there are some format warnings on x86, see

https://ci.appveyor.com/project/cygwin/cygwin/builds/40046785/job/fie6x4ta11v5nrjo

  reply	other threads:[~2021-07-19 15:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16  4:49 Mark Geisert
2021-07-16  4:49 ` [PATCH 2/3] Cygwin: New tool: gmondump Mark Geisert
2021-07-16  4:49 ` [PATCH 3/3] Cygwin: updates to wire in profiler, gmondump Mark Geisert
2021-07-19 10:04 ` [PATCH 1/3] Cygwin: New tool: profiler Corinna Vinschen
2021-07-19 14:23   ` Jon Turney
2021-07-19 15:43     ` Jon Turney [this message]
2021-07-21  8:00       ` [PATCH] Cygwin: fix format warnings in profiler.cc Mark Geisert
2021-07-21  8:09         ` Corinna Vinschen
2021-07-21  8:07       ` [PATCH 1/3] Cygwin: New tool: profiler Corinna Vinschen

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=5acddcda-7fa9-e854-911c-27af2f13a22c@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-patches@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).