public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Song Seok Ho <0xdevssh@gmail.com>,
	linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH] perf tools: set GUI mode after returning from perf_session__new()
Date: Mon, 4 Dec 2017 12:45:41 -0300	[thread overview]
Message-ID: <20171204154541.GD13698@kernel.org> (raw)
In-Reply-To: <CAM9d7cjM_LyExc2j0Zr=RdON4KQ-VB8b_iTxGiiz8DW=i0g_Dw@mail.gmail.com>

Em Tue, Dec 05, 2017 at 12:05:18AM +0900, Namhyung Kim escreveu:
> Hi SeokHo,
> 
> On Sun, Dec 3, 2017 at 10:50 PM, Song Seok Ho <0xdevssh@gmail.com> wrote:
> > If perf_session__new() returns NULL with use_browser set to 2 via --gtk option
> > previously, perf dies quietly without printing any errors.
> >
> > The reason behind this is that GTK is not yet initialized when the caller
> > inside perf_session__new() is trying to print error message to the screen.
> >
> > Reorder code to print the messages to stdio when GTK is not yet ready.
> 
> I'm ok with this change, but it needs to consider other error messages too.
> There are more pr_err() calls between perf_session__new() and
> setup_browser(), so I think they have same problem.

So I think I can apply this one, with Namhyung's acked-by and then Song
can continue with followup patches?

- Arnaldo
 
> Thanks,
> Namhyung
> 
> 
> >
> > Signed-off-by: Song Seok Ho <0xdevssh@gmail.com>
> > ---
> >  tools/perf/builtin-report.c | 14 +++++++-------
> >  1 file changed, 7 insertions(+), 7 deletions(-)
> >
> > diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c
> > index 1394cd8d96f7..0cd80b8c432e 100644
> > --- a/tools/perf/builtin-report.c
> > +++ b/tools/perf/builtin-report.c
> > @@ -918,13 +918,6 @@ int cmd_report(int argc, const char **argv)
> >                 return -EINVAL;
> >         }
> >
> > -       if (report.use_stdio)
> > -               use_browser = 0;
> > -       else if (report.use_tui)
> > -               use_browser = 1;
> > -       else if (report.use_gtk)
> > -               use_browser = 2;
> > -
> >         if (report.inverted_callchain)
> >                 callchain_param.order = ORDER_CALLER;
> >         if (symbol_conf.cumulate_callchain && !callchain_param.order_set)
> > @@ -949,6 +942,13 @@ int cmd_report(int argc, const char **argv)
> >         if (session == NULL)
> >                 return -1;
> >
> > +       if (report.use_stdio)
> > +               use_browser = 0;
> > +       else if (report.use_tui)
> > +               use_browser = 1;
> > +       else if (report.use_gtk)
> > +               use_browser = 2;
> > +
> >         if (report.queue_size) {
> >                 ordered_events__set_alloc_size(&session->ordered_events,
> >                                                report.queue_size);
> > --
> > 2.15.1
> >

  reply	other threads:[~2017-12-04 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03 13:50 [PATCH] perf tools: set GUI mode after returning from perf_session__new() Song Seok Ho
2017-12-04 15:05 ` Namhyung Kim
2017-12-04 15:45   ` Arnaldo Carvalho de Melo [this message]
2017-12-04 16:11     ` SeokHo Song
2017-12-04 16:28       ` Arnaldo Carvalho de Melo

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=20171204154541.GD13698@kernel.org \
    --to=acme@kernel.org \
    --cc=0xdevssh@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.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