mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Veronika Molnarova <vmolnaro@redhat.com>,
	 Adrian Hunter <adrian.hunter@intel.com>,
	Ian Rogers <irogers@google.com>,
	 James Clark <james.clark@linaro.org>,
	Jiri Olsa <jolsa@kernel.org>,
	 Kan Liang <kan.liang@linux.intel.com>,
	Michael Petlan <mpetlan@redhat.com>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 1/1 perf-tools] perf machine: Initialize machine->env to address a segfault
Date: Tue, 03 Dec 2024 13:58:38 -0800	[thread overview]
Message-ID: <173326311856.2683269.6372380713007833609.b4-ty@kernel.org> (raw)
In-Reply-To: <Z0XffUgNSv_9OjOi@x1>

On Tue, 26 Nov 2024 11:47:25 -0300, Arnaldo Carvalho de Melo wrote:

> Its used from trace__run(), for the 'perf trace' live mode, i.e. its
> strace-like, non-perf.data file processing mode, the most common one.
> 
> The trace__run() function will set trace->host using machine__new_host()
> that is supposed to give a machine instance representing the running
> machine, and since we'll use perf_env__arch_strerrno() to get the right
> errno -> string table, we need to use machine->env, so initialize it in
> machine__new_host().
> 
> [...]

Applied to perf-tools, thanks!

Best regards,
Namhyung


      parent reply	other threads:[~2024-12-03 21:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 14:47 Arnaldo Carvalho de Melo
2024-11-26 15:02 ` Veronika Molnarova
2024-12-03 10:22 ` Michael Petlan
2024-12-03 21:58 ` Namhyung Kim [this message]

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=173326311856.2683269.6372380713007833609.b4-ty@kernel.org \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mpetlan@redhat.com \
    --cc=vmolnaro@redhat.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

all inboxes | Powered by JetHome®