From: Andre Przywara <andre.przywara@arm.com>
To: Keir Fraser <keirf@google.com>
Cc: Will Deacon <will@kernel.org>,
kvm@vger.kernel.org, catalin.marinas@arm.com,
kernel-team@android.com,
Alexandru Elisei <Alexandru.Elisei@arm.com>
Subject: Re: [PATCH kvmtool 0/2] Fixes for virtio_balloon stats printing
Date: Mon, 23 May 2022 16:13:23 +0100 [thread overview]
Message-ID: <20220523161323.0e7df3d5@donnerap.cambridge.arm.com> (raw)
In-Reply-To: <Youi7+T1+YG/6ed9@google.com>
On Mon, 23 May 2022 15:06:23 +0000
Keir Fraser <keirf@google.com> wrote:
> On Mon, May 23, 2022 at 03:42:49PM +0100, Andre Przywara wrote:
> > On Fri, 20 May 2022 21:51:07 +0100
> > Will Deacon <will@kernel.org> wrote:
> >
> > Hi,
> >
> > > On Fri, 20 May 2022 14:37:04 +0000, Keir Fraser wrote:
> > > > While playing with kvmtool's virtio_balloon device I found a couple of
> > > > niggling issues with the printing of memory stats. Please consider
> > > > these fairly trivial fixes.
> >
> > Unfortunately patch 2/2 breaks compilation on userland with older kernel
> > headers, like Ubuntu 18.04:
> > ...
> > CC builtin-stat.o
> > builtin-stat.c: In function 'do_memstat':
> > builtin-stat.c:86:8: error: 'VIRTIO_BALLOON_S_HTLB_PGALLOC' undeclared (first use in this function); did you mean 'VIRTIO_BALLOON_S_AVAIL'?
> > case VIRTIO_BALLOON_S_HTLB_PGALLOC:
> > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > VIRTIO_BALLOON_S_AVAIL
> > (repeated for VIRTIO_BALLOON_S_HTLB_PGFAIL and VIRTIO_BALLOON_S_CACHES).
> >
> > I don't quite remember what we did here in the past in those cases,
> > conditionally redefine the symbols in a local header, or protect the
> > new code with an #ifdef?
>
> For what it's worth, my opinion is that the sensible options are to:
> 1. Build against the latest stable, or a specified version of, kernel
> headers; or 2. Protect with ifdef'ery until new definitions are
> considered "common enough".
>
> Supporting older headers by grafting or even modifying required newer
> definitions on top seems a horrid middle ground, albeit I can
> appreciate the pragmatism of it.
Fair enough, although I don't think option 1) is really viable for users,
as upgrading the distro provided kernel headers is often not an option for
the casual user. And even more versed users would probably shy away from
staining their /usr/include directory just for kvmtool.
Which just leaves option 2? If no one hollers, I will send a patch to that
regard.
Cheers,
Andre
>
> Regards,
> Keir
>
>
> > I would lean towards the former (and hacking this in works), but then we
> > would need to redefine VIRTIO_BALLOON_S_NR, to encompass the new symbols,
> > which sounds fragile.
> >
> > Happy to send a patch if we agree on an approach.
> >
> > Cheers,
> > Andre
> >
> > > >
> > > > Keir Fraser (2):
> > > > virtio/balloon: Fix a crash when collecting stats
> > > > stat: Add descriptions for new virtio_balloon stat types
> > > >
> > > > [...]
> > >
> > > Applied to kvmtool (master), thanks!
> > >
> > > [1/2] virtio/balloon: Fix a crash when collecting stats
> > > https://git.kernel.org/will/kvmtool/c/3a13530ae99a
> > > [2/2] stat: Add descriptions for new virtio_balloon stat types
> > > https://git.kernel.org/will/kvmtool/c/bc77bf49df6e
> > >
> > > Cheers,
> >
next prev parent reply other threads:[~2022-05-23 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 14:37 [PATCH kvmtool 0/2] Fixes for virtio_balloon stats printing Keir Fraser
2022-05-20 14:37 ` [PATCH kvmtool 1/2] virtio/balloon: Fix a crash when collecting stats Keir Fraser
2022-05-20 14:37 ` [PATCH kvmtool 2/2] stat: Add descriptions for new virtio_balloon stat types Keir Fraser
2022-05-20 20:51 ` [PATCH kvmtool 0/2] Fixes for virtio_balloon stats printing Will Deacon
2022-05-23 14:42 ` Andre Przywara
2022-05-23 15:06 ` Keir Fraser
2022-05-23 15:13 ` Andre Przywara [this message]
2022-05-23 15:49 ` Alexandru Elisei
2022-05-23 16:35 ` Keir Fraser
2022-05-23 17:07 ` Alexandru Elisei
2022-05-23 17:39 ` Andre Przywara
2022-05-24 8:40 ` Alexandru Elisei
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=20220523161323.0e7df3d5@donnerap.cambridge.arm.com \
--to=andre.przywara@arm.com \
--cc=Alexandru.Elisei@arm.com \
--cc=catalin.marinas@arm.com \
--cc=keirf@google.com \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=will@kernel.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