From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: "Liang, Kan" <kan.liang@linux.intel.com>,
mingo@redhat.com, peterz@infradead.org, mark.rutland@arm.com,
namhyung@kernel.org, jolsa@kernel.org, adrian.hunter@intel.com,
ravi.bangoria@amd.com, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, Ammy Yi <ammy.yi@intel.com>
Subject: Re: [PATCH] perf mem: Fix perf mem error on hybrid
Date: Mon, 4 Dec 2023 17:17:02 -0300 [thread overview]
Message-ID: <ZW4zvk2ZUnLuFgFK@kernel.org> (raw)
In-Reply-To: <CAP-5=fW=b7KmiJKgFOxWd4ayG9A+f4E6QuTKCV0bZmf=SWSQ4Q@mail.gmail.com>
Em Fri, Dec 01, 2023 at 06:08:13PM -0800, Ian Rogers escreveu:
> On Fri, Dec 1, 2023 at 1:43 PM Liang, Kan <kan.liang@linux.intel.com> wrote:
> > On 2023-11-30 3:36 p.m., Ian Rogers wrote:
> > > On Wed, Nov 29, 2023 at 1:15 PM Liang, Kan <kan.liang@linux.intel.com> wrote:
> > > Anyway, if you don't feel like the refactor we can move forward with
> > > this or a v2, let me know.
> > I think the refactor is doable. I will work on it next week.
> > But I think it should be on top of this fix.
> > If you are OK with the fix, I think it's better to have it merged first.
> > So everything would work properly. The validation work will not be blocked.
> > Then I can send a patch set to cleanup the perf mem events separately.
> Thanks Kan.
> Acked-by: Ian Rogers <irogers@google.com>
Thanks, applied to perf-tools-next.
- Arnaldo
prev parent reply other threads:[~2023-12-04 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 20:39 [PATCH] perf mem: Fix perf mem error on hybrid kan.liang
2023-11-29 6:24 ` Ian Rogers
2023-11-29 13:52 ` Liang, Kan
2023-11-29 16:17 ` Ian Rogers
2023-11-29 21:15 ` Liang, Kan
2023-11-30 20:36 ` Ian Rogers
2023-12-01 21:43 ` Liang, Kan
2023-12-02 2:08 ` Ian Rogers
2023-12-04 20:17 ` Arnaldo Carvalho de Melo [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=ZW4zvk2ZUnLuFgFK@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ammy.yi@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.