From: Dominik Csapak <d.csapak@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH qemu-server 1/2] tests: improve multiarch build support
Date: Tue, 3 Feb 2026 16:04:15 +0100 [thread overview]
Message-ID: <96b3810e-bb32-4045-bbeb-f5aa4c82d3f4@proxmox.com> (raw)
In-Reply-To: <ee782cc6-5e62-4d56-91bc-e9fe57af2916@proxmox.com>
On 2/3/26 3:59 PM, Thomas Lamprecht wrote:
> Am 03.02.26 um 15:21 schrieb Dominik Csapak:
>> The CPUConfig module sets the local 'host_arch' on loading, so instead
>> to try to mock all subs that access this variable, provide a setter only
>> intended for tests (and warn when using this).
>
> Would be nicer to get a local get_host_arch that just return's the PVE::Tools'
> method result, as we then could override the getter without having to worry
> about this method being misused in the future by accident.
>
> Moving the CPU model initialization into a sub, like suggested in my reply
> to Fiona's patches, and redoing that on a simulated switch of the host
> architecture would be also the slightly nicer interface IMO.
>
ok, makes sense, i'd do that in a v2
>>
>> Also, we have to override the 'get_host_arch' in the Helpers module too.
>
> The helper module has no such method? There is only get_vm_arch there and
> some usage of PVE::Tools' get_host_arch? Or is it because we import the one
> from PVE::Tools there?
>
yes, exactly. The importing and using of a sub means that when mocking
we have to mock it in the module we're using it.
alternatively, we could write out 'PVE::Tools::get_host_arch' everywhere
without importing, then we'd only have to mock once
(but makes the code slightly less readable)
next prev parent reply other threads:[~2026-02-03 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 14:16 Dominik Csapak
2026-02-03 14:16 ` [PATCH qemu-server 2/2] tests: cfg2cmd: add some architecture tests Dominik Csapak
2026-02-03 15:01 ` [PATCH qemu-server 1/2] tests: improve multiarch build support Thomas Lamprecht
2026-02-03 15:04 ` Dominik Csapak [this message]
2026-02-03 15:09 ` Thomas Lamprecht
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=96b3810e-bb32-4045-bbeb-f5aa4c82d3f4@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/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.