From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>, xen-devel@lists.xenproject.org
Cc: Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH] xen/Kconfig: livepatch-build-tools requires debug information
Date: Thu, 7 Nov 2024 09:21:26 +0000 [thread overview]
Message-ID: <66fd7b53-25f5-459b-8563-e33fccba90ef@citrix.com> (raw)
In-Reply-To: <20241107084927.37748-1-roger.pau@citrix.com>
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 ?
next prev parent reply other threads:[~2024-11-07 9:21 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 [this message]
2024-11-07 9:40 ` Roger Pau Monné
2024-11-07 9:48 ` Jan Beulich
2024-11-07 11:25 ` Roger Pau Monné
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=66fd7b53-25f5-459b-8563-e33fccba90ef@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=roger.pau@citrix.com \
--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.