From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
Cc: Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf build: Fix a build error on 32-bit x86
Date: Mon, 03 Aug 2026 10:33:23 -0700 [thread overview]
Message-ID: <178577840379.2174330.3697546596918863933.b4-ty@kernel.org> (raw)
In-Reply-To: <20260730235946.618096-1-namhyung@kernel.org>
On Thu, 30 Jul 2026 16:59:46 -0700, Namhyung Kim wrote:
> The commit d7507a94a072 ("KVM: SVM: Treat exit_code as an unsigned
> 64-bit value through all of KVM") added "ull" suffix to SVM exit codes
> and it makes the 32-bit build fail like below.
>
> In file included from util/kvm-stat-arch/kvm-stat-x86.c:4:
> util/kvm-stat-arch/../../../arch/x86/include/uapi/asm/svm.h:137:32:
> error: conversion from 'long long unsigned int' to 'long unsigned int' changes
> value from '18446744073709551615' to '4294967295' [-Werror=overflow]
> 137 | #define SVM_EXIT_ERR -1ull
> | ^
> util/kvm-stat-arch/../kvm-stat.h:131:17: note: in definition of macro 'define_exit_reasons_table'
> 131 | symbols, { -1, NULL } \
> | ^~~~~~~
> util/kvm-stat-arch/../../../arch/x86/include/uapi/asm/svm.h:249:11: note: in expansion of macro 'SVM_EXIT_ERR'
> 249 | { SVM_EXIT_ERR, "invalid_guest_state" }
> | ^~~~~~~~~~~~
> util/kvm-stat-arch/kvm-stat-x86.c:12:45: note: in expansion of macro 'SVM_EXIT_REASONS'
> 12 | define_exit_reasons_table(svm_exit_reasons, SVM_EXIT_REASONS);
> | ^~~~~~~~~~~~~~~~
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
prev parent reply other threads:[~2026-08-03 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 23:59 [PATCH] perf build: Fix a build error on 32-bit x86 Namhyung Kim
2026-08-03 17:33 ` 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=178577840379.2174330.3697546596918863933.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=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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