* [PATCH] automation/eclair: export XEN_TARGET_ARCH during assignment
@ 2026-05-19 10:27 Dmytro Prokopchuk1
2026-05-19 10:32 ` Jan Beulich
2026-05-19 10:45 ` Nicola Vetrini
0 siblings, 2 replies; 5+ messages in thread
From: Dmytro Prokopchuk1 @ 2026-05-19 10:27 UTC (permalink / raw)
To: xen-devel@lists.xenproject.org
Cc: Dmytro Prokopchuk1, Nicola Vetrini, Doug Goldstein,
Stefano Stabellini
Move XEN_TARGET_ARCH export into the architecture selection
branches instead of exporting the variable before assignment.
This ensures the selected architecture value is correctly
propagated.
No functional changes.
Signed-off-by: Dmytro Prokopchuk <dmytro_prokopchuk1@epam.com>
---
automation/eclair_analysis/prepare.sh | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/automation/eclair_analysis/prepare.sh b/automation/eclair_analysis/prepare.sh
index e941e6edc4..fde83c2d2d 100755
--- a/automation/eclair_analysis/prepare.sh
+++ b/automation/eclair_analysis/prepare.sh
@@ -22,12 +22,10 @@ if [ $# -ne 1 ]; then
exit 1
fi
-export XEN_TARGET_ARCH
-
if [ "$1" = "X86_64" ]; then
- XEN_TARGET_ARCH=x86_64
+ export XEN_TARGET_ARCH=x86_64
elif [ "$1" = "ARM64" ]; then
- XEN_TARGET_ARCH=arm64
+ export XEN_TARGET_ARCH=arm64
else
fatal "Unknown configuration: $1"
fi
--
2.43.0
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH] automation/eclair: export XEN_TARGET_ARCH during assignment
2026-05-19 10:27 [PATCH] automation/eclair: export XEN_TARGET_ARCH during assignment Dmytro Prokopchuk1
@ 2026-05-19 10:32 ` Jan Beulich
2026-05-19 10:45 ` Nicola Vetrini
1 sibling, 0 replies; 5+ messages in thread
From: Jan Beulich @ 2026-05-19 10:32 UTC (permalink / raw)
To: Dmytro Prokopchuk1
Cc: Nicola Vetrini, Doug Goldstein, Stefano Stabellini,
xen-devel@lists.xenproject.org
On 19.05.2026 12:27, Dmytro Prokopchuk1 wrote:
> Move XEN_TARGET_ARCH export into the architecture selection
> branches instead of exporting the variable before assignment.
> This ensures the selected architecture value is correctly
> propagated.
This reads as if something is being corrected, while ...
> No functional changes.
... this says the opposite. Is the whole purpose ...
> --- a/automation/eclair_analysis/prepare.sh
> +++ b/automation/eclair_analysis/prepare.sh
> @@ -22,12 +22,10 @@ if [ $# -ne 1 ]; then
> exit 1
> fi
>
> -export XEN_TARGET_ARCH
> -
> if [ "$1" = "X86_64" ]; then
> - XEN_TARGET_ARCH=x86_64
> + export XEN_TARGET_ARCH=x86_64
> elif [ "$1" = "ARM64" ]; then
> - XEN_TARGET_ARCH=arm64
> + export XEN_TARGET_ARCH=arm64
> else
> fatal "Unknown configuration: $1"
> fi
... the reduction in line count then (at the expense of some redundancy,
which would increase when further arches get put here)?
Jan
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] automation/eclair: export XEN_TARGET_ARCH during assignment
2026-05-19 10:27 [PATCH] automation/eclair: export XEN_TARGET_ARCH during assignment Dmytro Prokopchuk1
2026-05-19 10:32 ` Jan Beulich
@ 2026-05-19 10:45 ` Nicola Vetrini
2026-05-19 11:03 ` Dmytro Prokopchuk1
1 sibling, 1 reply; 5+ messages in thread
From: Nicola Vetrini @ 2026-05-19 10:45 UTC (permalink / raw)
To: Dmytro Prokopchuk1; +Cc: xen-devel, Doug Goldstein, Stefano Stabellini
On 2026-05-19 12:27, Dmytro Prokopchuk1 wrote:
> Move XEN_TARGET_ARCH export into the architecture selection
> branches instead of exporting the variable before assignment.
> This ensures the selected architecture value is correctly
> propagated.
>
Did you see a case where this is not correctly propagated? As far as I
understand, the value of XEN_TARGET_ARCH seen by subprocesses is the
last value set for the variable, regardless of where the export command
is placed.
> No functional changes.
>
> Signed-off-by: Dmytro Prokopchuk <dmytro_prokopchuk1@epam.com>
> ---
> automation/eclair_analysis/prepare.sh | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/automation/eclair_analysis/prepare.sh
> b/automation/eclair_analysis/prepare.sh
> index e941e6edc4..fde83c2d2d 100755
> --- a/automation/eclair_analysis/prepare.sh
> +++ b/automation/eclair_analysis/prepare.sh
> @@ -22,12 +22,10 @@ if [ $# -ne 1 ]; then
> exit 1
> fi
>
> -export XEN_TARGET_ARCH
> -
> if [ "$1" = "X86_64" ]; then
> - XEN_TARGET_ARCH=x86_64
> + export XEN_TARGET_ARCH=x86_64
> elif [ "$1" = "ARM64" ]; then
> - XEN_TARGET_ARCH=arm64
> + export XEN_TARGET_ARCH=arm64
> else
> fatal "Unknown configuration: $1"
> fi
--
Nicola Vetrini, B.Sc.
Software Engineer
BUGSENG (https://bugseng.com)
LinkedIn: https://www.linkedin.com/in/nicola-vetrini-a42471253
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] automation/eclair: export XEN_TARGET_ARCH during assignment
2026-05-19 10:45 ` Nicola Vetrini
@ 2026-05-19 11:03 ` Dmytro Prokopchuk1
2026-05-19 11:09 ` Nicola Vetrini
0 siblings, 1 reply; 5+ messages in thread
From: Dmytro Prokopchuk1 @ 2026-05-19 11:03 UTC (permalink / raw)
To: Nicola Vetrini
Cc: xen-devel@lists.xenproject.org, Doug Goldstein,
Stefano Stabellini
Hello Nicola,
On 5/19/26 13:45, Nicola Vetrini wrote:
> On 2026-05-19 12:27, Dmytro Prokopchuk1 wrote:
>> Move XEN_TARGET_ARCH export into the architecture selection
>> branches instead of exporting the variable before assignment.
>> This ensures the selected architecture value is correctly
>> propagated.
>>
>
> Did you see a case where this is not correctly propagated? As far as I
I didn't see a case.
> understand, the value of XEN_TARGET_ARCH seen by subprocesses is the
> last value set for the variable, regardless of where the export command
> is placed.
Yes, you are right. It works in that way.
IMO, exporting empty variable looks strange...
Anyway up to you to judge if this patch is needed or not.
BR, Dmytro.
>> No functional changes.
>>
>> Signed-off-by: Dmytro Prokopchuk <dmytro_prokopchuk1@epam.com>
>> ---
>> automation/eclair_analysis/prepare.sh | 6 ++----
>> 1 file changed, 2 insertions(+), 4 deletions(-)
>>
>> diff --git a/automation/eclair_analysis/prepare.sh b/automation/
>> eclair_analysis/prepare.sh
>> index e941e6edc4..fde83c2d2d 100755
>> --- a/automation/eclair_analysis/prepare.sh
>> +++ b/automation/eclair_analysis/prepare.sh
>> @@ -22,12 +22,10 @@ if [ $# -ne 1 ]; then
>> exit 1
>> fi
>>
>> -export XEN_TARGET_ARCH
>> -
>> if [ "$1" = "X86_64" ]; then
>> - XEN_TARGET_ARCH=x86_64
>> + export XEN_TARGET_ARCH=x86_64
>> elif [ "$1" = "ARM64" ]; then
>> - XEN_TARGET_ARCH=arm64
>> + export XEN_TARGET_ARCH=arm64
>> else
>> fatal "Unknown configuration: $1"
>> fi
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] automation/eclair: export XEN_TARGET_ARCH during assignment
2026-05-19 11:03 ` Dmytro Prokopchuk1
@ 2026-05-19 11:09 ` Nicola Vetrini
0 siblings, 0 replies; 5+ messages in thread
From: Nicola Vetrini @ 2026-05-19 11:09 UTC (permalink / raw)
To: Dmytro Prokopchuk1; +Cc: xen-devel, Doug Goldstein, Stefano Stabellini
On 2026-05-19 13:03, Dmytro Prokopchuk1 wrote:
> Hello Nicola,
>
> On 5/19/26 13:45, Nicola Vetrini wrote:
>> On 2026-05-19 12:27, Dmytro Prokopchuk1 wrote:
>>> Move XEN_TARGET_ARCH export into the architecture selection
>>> branches instead of exporting the variable before assignment.
>>> This ensures the selected architecture value is correctly
>>> propagated.
>>>
>>
>> Did you see a case where this is not correctly propagated? As far as I
> I didn't see a case.
>> understand, the value of XEN_TARGET_ARCH seen by subprocesses is the
>> last value set for the variable, regardless of where the export
>> command
>> is placed.
> Yes, you are right. It works in that way.
> IMO, exporting empty variable looks strange...
>
> Anyway up to you to judge if this patch is needed or not.
>
Indeed it is a bit strange. To avoid this we should perhaps move the
export after the if, so that it is obvious that it contains the correct
value
> BR, Dmytro.
>>> No functional changes.
>>>
>>> Signed-off-by: Dmytro Prokopchuk <dmytro_prokopchuk1@epam.com>
>>> ---
>>> automation/eclair_analysis/prepare.sh | 6 ++----
>>> 1 file changed, 2 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/automation/eclair_analysis/prepare.sh b/automation/
>>> eclair_analysis/prepare.sh
>>> index e941e6edc4..fde83c2d2d 100755
>>> --- a/automation/eclair_analysis/prepare.sh
>>> +++ b/automation/eclair_analysis/prepare.sh
>>> @@ -22,12 +22,10 @@ if [ $# -ne 1 ]; then
>>> exit 1
>>> fi
>>>
>>> -export XEN_TARGET_ARCH
>>> -
>>> if [ "$1" = "X86_64" ]; then
>>> - XEN_TARGET_ARCH=x86_64
>>> + export XEN_TARGET_ARCH=x86_64
>>> elif [ "$1" = "ARM64" ]; then
>>> - XEN_TARGET_ARCH=arm64
>>> + export XEN_TARGET_ARCH=arm64
>>> else
>>> fatal "Unknown configuration: $1"
>>> fi
>>
--
Nicola Vetrini, B.Sc.
Software Engineer
BUGSENG (https://bugseng.com)
LinkedIn: https://www.linkedin.com/in/nicola-vetrini-a42471253
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2026-05-19 11:09 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-19 10:27 [PATCH] automation/eclair: export XEN_TARGET_ARCH during assignment Dmytro Prokopchuk1
2026-05-19 10:32 ` Jan Beulich
2026-05-19 10:45 ` Nicola Vetrini
2026-05-19 11:03 ` Dmytro Prokopchuk1
2026-05-19 11:09 ` Nicola Vetrini
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.