Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Alexandru Elisei <alexandru.elisei@arm.com>
Cc: julien.thierry.kdev@gmail.com, maz@kernel.org, oupton@kernel.org,
	jean-philippe@linaro.org, andre.przywara@arm.com,
	suzuki.poulose@arm.com, kvm@vger.kernel.org
Subject: Re: [PATCH kvmtool 0/6] x86 compilation fixes and arm64 PMU improvements
Date: Thu, 18 Jun 2026 13:58:46 +0100	[thread overview]
Message-ID: <ajPrhvfDIRefmRMd@willie-the-truck> (raw)
In-Reply-To: <ajPo4C3I-VBAkJ0O@raptor>

On Thu, Jun 18, 2026 at 01:47:28PM +0100, Alexandru Elisei wrote:
> Hi Will,
> 
> On Tue, Jun 16, 2026 at 10:11:11AM +0100, Will Deacon wrote:
> > Hey Alexandru,
> > 
> > On Mon, Mar 23, 2026 at 03:02:15PM +0000, Alexandru Elisei wrote:
> > > The first two patches fix the following compilation errors on x86 when
> > > using gcc 15.2.1:
> > > 
> > > disk/core.c: In function ‘disk_img_name_parser’:
> > > disk/core.c:27:21: error: assignment discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]
> > >    27 |                 sep = strstr(arg, ":");
> > >       |                     ^
> > > disk/core.c:39:21: error: assignment discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]
> > >    39 |                 sep = strstr(cur, ",");
> > >       |                     ^
> > > virtio/9p.c: In function ‘virtio_9p_rootdir_parser’:
> > > virtio/9p.c:1503:18: error: assignment discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]
> > >  1503 |         tag_name = strstr(arg, ",");
> > >       |                  ^
> > > 
> > > I couldn't reproduce the errors on arm64 using aarch64-linux-gnu-gcc 15.1.0
> > > and 14.2.0. I tried doing make with V=1 and it looked to me like kvmtool
> > > uses the same flags on x86 as on arm64, so I assumed it's because of the
> > > difference in compilers and I didn't dig further.
> > > 
> > > The remaining of the patches are there to improve PMU initialisation and
> > > error reporting.
> > 
> > Do you plan to post a v2 of these? I just ran into the 'const' issue
> > myself, so I'd love to see this stuff land after addressing the handful
> > of review comments I left on this version.
> 
> Yes, I was just about to put the finishing touches on v2 locally, I'll send
> it soon.

Thank you!

Will

      reply	other threads:[~2026-06-18 12:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 15:02 [PATCH kvmtool 0/6] x86 compilation fixes and arm64 PMU improvements Alexandru Elisei
2026-03-23 15:02 ` [PATCH kvmtool 1/6] virtio: Do not modify const strings in virtio_9p_rootdir_parser() Alexandru Elisei
2026-03-23 15:02 ` [PATCH kvmtool 2/6] disk/core: Do not modify const strings in disk_img_name_parser() Alexandru Elisei
2026-05-17  8:29   ` Will Deacon
2026-05-18  9:51     ` Alexandru Elisei
2026-03-23 15:02 ` [PATCH kvmtool 3/6] arm64: Initialise the PMU last Alexandru Elisei
2026-05-17  8:33   ` Will Deacon
2026-05-18  9:53     ` Alexandru Elisei
2026-03-23 15:02 ` [PATCH kvmtool 4/6] util: Set exit status to errno in die_perror() Alexandru Elisei
2026-03-23 15:02 ` [PATCH kvmtool 5/6] util: Allow die_perror() to take a variable list of argument Alexandru Elisei
2026-05-17  8:44   ` Will Deacon
2026-05-18 10:12     ` Alexandru Elisei
2026-05-18 15:06       ` Will Deacon
2026-05-18 15:22         ` Alexandru Elisei
2026-03-23 15:02 ` [PATCH kvmtool 6/6] arm64: Improve KVM_ARM_VCPU_PMU_V3_CTRL diagnostics Alexandru Elisei
2026-06-16  9:11 ` [PATCH kvmtool 0/6] x86 compilation fixes and arm64 PMU improvements Will Deacon
2026-06-18 12:47   ` Alexandru Elisei
2026-06-18 12:58     ` Will Deacon [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=ajPrhvfDIRefmRMd@willie-the-truck \
    --to=will@kernel.org \
    --cc=alexandru.elisei@arm.com \
    --cc=andre.przywara@arm.com \
    --cc=jean-philippe@linaro.org \
    --cc=julien.thierry.kdev@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=oupton@kernel.org \
    --cc=suzuki.poulose@arm.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