From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH] xen/Kconfig: livepatch-build-tools requires debug information
Date: Thu, 7 Nov 2024 12:25:14 +0100 [thread overview]
Message-ID: <Zyyjmu9tm1KEGiqQ@macbook> (raw)
In-Reply-To: <22c59035-67e3-4e43-bfe0-26675a93e9ae@suse.com>
On Thu, Nov 07, 2024 at 10:48:21AM +0100, Jan Beulich wrote:
> On 07.11.2024 10:40, Roger Pau Monné wrote:
> > On Thu, Nov 07, 2024 at 09:21:26AM +0000, Andrew Cooper wrote:
> >> On 07/11/2024 8:49 am, Roger Pau Monne wrote:
> >>> The tools infrastructure used to build livepatches for Xen
> >>> (livepatch-build-tools) consumes some DWARF debug information present in
> >>> xen-syms to generate a livepatch (see livepatch-build script usage of readelf
> >>> -wi).
> >>>
> >>> The current Kconfig defaults however will enable LIVEPATCH without DEBUG_INFO
> >>> on release builds, thus providing a default Kconfig selection that's not
> >>> suitable for livepatch-build-tools even when LIVEPATCH support is enabled,
> >>> because it's missing the DWARF debug section.
> >>>
> >>> Fix by forcing the selection of DEBUG_INFO from LIVEPATCH.
> >>>
> >>> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> >>
> >> Oops, yes.
> >>
> >> Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
> >>
> >> Fixes tag ?
> >
> > Was borderline on adding one, but wasn't sure since it's strictly
> > livepatch-build-tools that requires the DWARF data, but custom made
> > livepatches (like the examples in tests) do not require such
> > information.
>
> At which point: Is "select" really appropriate then? Wouldn't it be more
> logical then to change DEBUG_INFO's default to take LIVEPATCH into account
> (still permitting people to turn debug info off if they know they won't
> need it)?
At least right now the only way to build useful livepatches for Xen
(not dummy tests) is using livepatch-build-tools (that requires DWARF
sections). My concern with using the Fixes tag was that I don't know
whether initially the DWARF info was needed or not, or maybe whether
people used a different tool rather than livepatch-build-tools.
I don't mind changing, but I also don't think an hypervisor built with
LIVEPATCH but without DEBUG_INFO is going to be useful to anyone given
the requirements of the tools we provide to build livepatches.
Thanks, Roger.
next prev parent reply other threads:[~2024-11-07 11:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 8:49 [PATCH] xen/Kconfig: livepatch-build-tools requires debug information Roger Pau Monne
2024-11-07 9:21 ` Andrew Cooper
2024-11-07 9:40 ` Roger Pau Monné
2024-11-07 9:48 ` Jan Beulich
2024-11-07 11:25 ` Roger Pau Monné [this message]
2024-11-07 11:42 ` Jan Beulich
2024-11-07 11:30 ` Andrew Cooper
2024-11-07 11:57 ` Jan Beulich
2024-11-07 12:17 ` Andrew Cooper
2024-11-07 13:25 ` Jan Beulich
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=Zyyjmu9tm1KEGiqQ@macbook \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 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.