[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v4 0/4] Add Kconfig option to remove microcode loading support
- To: Alejandro Vallejo <alejandro.garciavallejo@xxxxxxx>
- From: Nicola Vetrini <nicola.vetrini@xxxxxxxxxxx>
- Date: Tue, 20 Jan 2026 12:30:25 +0100
- Arc-authentication-results: i=1; bugseng.com; arc=none smtp.remote-ip=162.55.131.47
- Arc-message-signature: i=1; d=bugseng.com; s=openarc; a=rsa-sha256; c=relaxed/relaxed; t=1768908625; h=MIME-Version:Date:From:To:Cc:Subject:In-Reply-To:References: Message-ID:X-Sender:Organization:Content-Type: Content-Transfer-Encoding; bh=T0dpN5Yol5j6OhB+Xjhb7MHZC+YeHMALVWycAZpPAp8=; b=tTEZwiQSRNoDYee+5lQJ6IoBu0Dpe5cjFLz7wO/AhsIaxSmdW5yw5rDczLoIwNJIXEjX q5XmjFz7tU9GQvr6PNKjitMyVeNd5UA03PJMQvL8TN30O71lyNWJsF/Dk2ZuMklTliRsX IvXx6Hmoh7aR74jvrkMgxquvMC+aijwXL78j7KcAvXu4M3m+JuJgOyyF3zzzsHzG3glY+ ZcbebCwPVCOTkqL04ykvIpilWAi+D068vDDPzsivzUscXtxx+G8iH6AxikiDxdCecEale 5nkZjWZyQ6nnd6GBPtojLkDCeJctk4zDby9jY2OYDomCEAkqM08EQZAOWCHBWouDqPZxx qo+pyeytJM3m0I1u1WUDb1p+2z3/aUIxwAUFrx3T1ZlboWlaJdhPU03RYwuYl65lvzX80 wMFJFnw13QUW5o2q4P8n/5rGtc7SUOFoNBXAZuhiVU5h5GNY989iVd6Bh06GvfKqAPj8D bdShHpsKvEopYYVg6lAXzC3OYSQijZEqHplPsvknZR9AHhTAv1V1bbV8jMktryq6qM9xv Al6qbd9TlfUhNoaFWeQ6zbz9R3uQNpPu6FlrMHOBpkKjEWjKnmkoV2kceNrZORxyo/NSD ifWx+ueJXu3rM8VZE7OBQLwY7Z1cKwGLUMTkmU7zRNZ8wFGGMDuAAWjksmGS4Uo=
- Arc-seal: i=1; d=bugseng.com; s=openarc; a=rsa-sha256; cv=none; t=1768908625; b=lCq4b98Mf0PertI5RkWj5GXlQfVErI68gGYMI6R7fmi1qXQB4YBi+BktvgZDzF4/Up5x jqC2OvrTwwpCfg5End/WBV/YLACcD4v4n58qBs2VyGu4bMdTxKNKhiNKbivSJLVoCRFX8 hp5aLqz2BqxviEZQPyIDJkoilMoE7HDE7XUPoq85Wp0UDJd1ay7h9O8zfyJaXQ3BPQyGl a+TpSct0Uy7oTiy0Lo5PzZzgHbR5oe9bktHc1O5m+L3U7mY9vpLbAk07VDVhnFCkWHDpw sxDXX3boJYSznHnqbNlGoCAgI1yCJaakRKhDeuJZ8PsAJmu1WuR0QzqiT9AQr4Tauttuc +oZxBTjs1imRPngFKdbGnRX57LC5lmc9zewWlGS3uSIAop2N4fh3swDijJoHZrldgixju nIknXUfOr8zc2ZDF54vGKc1MgCLS1tNQdaA69952nh0HZ6LPI9nWndw0WMGKhguYSgMLR 1DQNgOcjrMDrbQR+1C/joW//o1Lz6klALdarurFuWqaLO9L0iilacqJG3P9SAgmrR6IaC W67ClhpBOfgLe2yK1hIagPLGIIhK46SavTQRdHbz3zx5yTKD3Q6zd+ONMQXHxihdSfM6C aHZv6FZX2Rt9hVkeLS74OqGKf8vo5oHW4chmAw6KR1Lpw/Wqple+t2SAvdpTskU=
- Authentication-results: bugseng.com; arc=none smtp.remote-ip=162.55.131.47
- Cc: Jan Beulich <jbeulich@xxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Anthony PERARD <anthony.perard@xxxxxxxxxx>, Michal Orzel <michal.orzel@xxxxxxx>, Julien Grall <julien@xxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, "Daniel P. Smith" <dpsmith@xxxxxxxxxxxxxxxxxxxx>, Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx>, Doug Goldstein <cardoe@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
- Delivery-date: Tue, 20 Jan 2026 11:30:29 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 2026-01-20 12:03, Alejandro Vallejo wrote:
On Tue Jan 20, 2026 at 11:52 AM CET, Jan Beulich wrote:
On 20.01.2026 11:38, Alejandro Vallejo wrote:
On Tue Jan 20, 2026 at 11:20 AM CET, Jan Beulich wrote:
On 20.01.2026 10:38, Alejandro Vallejo wrote:
The only dependency here is patch 2 going in before patch 3.
Everything else
can be freely rearranged.
Is this correct? Didn't you say (confirming what I observed
elsewhere a little
while back) that there's a complaint when a file listed in the
exclusions doesn't
exist anymore (which may have been cppcheck, not Eclair, but still
breaking CI)?
IOW can patch 4 really be separate from patch 3? Or, if its
description was to
be trusted, wouldn't it need to go ahead of what is now patch 3?
Doh, you're right, they are out of order. Patch 4 now just removes
the exclusion
so it's fine to do it separately.
I.e. the description there saying "it's clean" is accurate, and it was
excluded
for (effectively) no reason?
All I can say is that I looked at the report after running Eclair and
found no
trace of earlycpio.c in the violations. It's not clean, but I don't
think it
is as of now.
As to why it was excluded in the first place, your guess is as good as
mine.
Maybe all decompressors were excluded regardless of them being clean or
not
(e.g: zstd is also excluded).
Well, the list was devised by AMD before even plumbing the MISRA
checking infrastructure, so it may well be that some files in there can
be removed because they have no violations on clean guidelines (that is
not to say that they contain no violations at all: it may be that they
have some additional ones in non-clean guidelines).
Cheers,
Alejandro
--
Nicola Vetrini, B.Sc.
Software Engineer
BUGSENG (https://bugseng.com)
LinkedIn: https://www.linkedin.com/in/nicola-vetrini-a42471253
|
