From: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v5 1/2] xen: Allow lib-y targets to also be .init.o
Date: Thu, 22 Jan 2026 13:12:24 +0100 [thread overview]
Message-ID: <DFV3X4D42O0U.Z901YT156HF8@amd.com> (raw)
In-Reply-To: <7304f5e0-f55c-45c5-ae4c-3d3adc53a0b3@suse.com>
On Thu Jan 22, 2026 at 12:04 PM CET, Jan Beulich wrote:
> On 22.01.2026 12:02, Alejandro Vallejo wrote:
>> On Thu Jan 22, 2026 at 11:01 AM CET, Jan Beulich wrote:
>>> On 22.01.2026 10:49, Jan Beulich wrote:
>>>> On 21.01.2026 16:47, Alejandro Vallejo wrote:
>>>>> There's some assumptions as to which targets may be init-only. But
>>>>> there's little reason to preclude libraries from being init-only.
>>>>>
>>>>> Signed-off-by: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
>>>>> Reviewed-by: Jan Beulich <jbeulich@suse.com>
>>>>
>>>> I can't tell (yet) what it is, but as per CI something's clearly wrong with this
>>>> change. Both xilinx-smoke-dom0less-arm64-* and qemu-smoke-dom0*-debug* fail with
>>>> it in place. qemu-smoke-dom0-arm64-gcc (no "debug") was fine, suggesting it may
>>>> be an early assertion triggering.
>>>
>>> Or an early UBSAN failure. I think ...
>>>
>>>>> --- a/xen/Rules.mk
>>>>> +++ b/xen/Rules.mk
>>>>> @@ -130,9 +130,9 @@ endif
>>>>>
>>>>> targets += $(targets-for-builtin)
>>>>>
>>>>> -$(filter %.init.o,$(obj-y) $(obj-bin-y) $(extra-y)): CFLAGS-y += -DINIT_SECTIONS_ONLY
>>>>> +$(filter %.init.o,$(obj-y) $(obj-bin-y) $(extra-y) $(lib-y)): CFLAGS-y += -DINIT_SECTIONS_ONLY
>>>>>
>>>>> -non-init-objects = $(filter-out %.init.o, $(obj-y) $(obj-bin-y) $(extra-y))
>>>>> +non-init-objects = $(filter-out %.init.o, $(obj-y) $(obj-bin-y) $(extra-y) $(lib-y))
>>>
>>> ... this is the problem: You're _adding_ library files here which weren't there
>>> before. Why $(lib-y) isn't here I don't really known, but as per the CI results
>>> there must be a reason for this.
>>
>> Apologies for the unintended breakage. I should've checked the baseline for
>> arm before ruling out this patch being the cause (it did fire in my pipeline,
>> but didn't consider how this could affect arm and attributed it to a spurious
>> failure).
>>
>> So we're neither doing UBSAN nor collecting coverage data from libs? Great. One
>> more task to the pile, I guess. Seeing how...
>>
>> $(non-init-objects): _c_flags += $(cov-cflags-y)
>> [snip]
>> $(non-init-objects): _c_flags += $(UBSAN_FLAGS)
>>
>> I'll try to clean this mess. :/
>
> In the meantime, should I give your patch another try with that one change dropped?
>
> Jan
Sure, thanks.
Cheers,
Alejandro
next prev parent reply other threads:[~2026-01-22 12:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 15:47 [PATCH v5 0/2] Alejandro Vallejo
2026-01-21 15:47 ` [PATCH v5 1/2] xen: Allow lib-y targets to also be .init.o Alejandro Vallejo
2026-01-22 9:49 ` Jan Beulich
2026-01-22 10:01 ` Jan Beulich
2026-01-22 11:02 ` Alejandro Vallejo
2026-01-22 11:04 ` Jan Beulich
2026-01-22 12:12 ` Alejandro Vallejo [this message]
2026-01-23 10:56 ` Orzel, Michal
2026-01-23 11:37 ` Jan Beulich
2026-01-23 12:53 ` Orzel, Michal
2026-01-21 15:47 ` [PATCH v5 2/2] earlycpio: lib-ify earlycpio.c Alejandro Vallejo
2026-01-21 19:37 ` Andrew Cooper
2026-01-22 8:27 ` Jan Beulich
2026-01-22 12:50 ` Andrew Cooper
2026-01-22 14:18 ` Nicola Vetrini
2026-01-22 17:48 ` Alejandro Vallejo
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=DFV3X4D42O0U.Z901YT156HF8@amd.com \
--to=alejandro.garciavallejo@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--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.