[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aAqxei2pAfDbmiTy@x1>
Date: Thu, 24 Apr 2025 18:47:38 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Venkat Rao Bagalkote <venkat88@...ux.ibm.com>,
Athira Rajeev <atrajeev@...ux.ibm.com>, jolsa@...nel.org,
adrian.hunter@...el.com, irogers@...gle.com,
linux-perf-users@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
maddy@...ux.ibm.com, disgoel@...ux.vnet.ibm.com,
hbathini@...ux.vnet.ibm.com, Aditya.Bodkhe1@....com,
jiang.peng9@....com.cn, Tejas.Manhas1@....com,
sshegde@...ux.ibm.com, sfr@...b.auug.org.au,
linux-kernel@...r.kernel.org, mingo@...hat.com,
ravi.bangoria@....com, bp@...en8.de
Subject: Re: [PATCH] perf build: Add tools/arch/x86/include/asm/amd/ibs.h to
sync the headers
On Thu, Apr 24, 2025 at 01:54:44PM -0700, Namhyung Kim wrote:
> > On Thu, Apr 24, 2025 at 10:39:56PM +0530, Venkat Rao Bagalkote wrote:
> > > On 24/04/25 10:00 pm, Athira Rajeev wrote:
> > > Tested this patch by applying on tip HEAD:
> > > 7ab869c799fc0fb22f9b4c2f36aaa603d9c7cc9d and it fixes the reported issue.
> > This is just a long list of characters, can you please next time provide
> > something like, humm, tip/head, not really:
>
> > ⬢ [acme@...lbx perf-tools-next]$ git remote -v | grep tip
> > tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git (fetch)
> > tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git (push)
> > ⬢ [acme@...lbx perf-tools-next]$ git remote update tip
> > Fetching tip
> > ⬢ [acme@...lbx perf-tools-next]$ git show 7ab869c799fc0fb22f9b4c2f36aaa603d9c7cc9d
> > fatal: bad object 7ab869c799fc0fb22f9b4c2f36aaa603d9c7cc9d
> > ⬢ [acme@...lbx perf-tools-next]$
> > So please add the summary, that way we can try to figure out if this is
> > a rebase and they look for the description instead of this sha1 that I'm
> > not finding even after doing a 'git remore update tip'.
> Does this mean the kernel change broke the tool build but we don't have
> it in the perf-tools-next yet? Then probably we need to wait for the
> next merge window to fix it in the tool side, no?
I'm not noticing this with perf-tools-next on a 9950x3d fedora:42 and
the referenced commit is not present in it nor in upstream nor in tip
master, so I need the reporter to check his environment and report back.
- Arnaldo
Powered by blists - more mailing lists