From: Dominik Csapak <d.csapak@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH qemu-server v2 1/2] tests: improve multiarch build support
Date: Thu, 5 Feb 2026 08:51:15 +0100 [thread overview]
Message-ID: <7fd01f54-4148-4cb4-8d22-bf68d2e9855e@proxmox.com> (raw)
In-Reply-To: <88e10fbe-3231-40da-8ea2-d95fc1576715@proxmox.com>
On 2/4/26 4:45 PM, Thomas Lamprecht wrote:
> Am 04.02.26 um 11:04 schrieb Dominik Csapak:
[snip]
>>
>> +initialize_cpu_models();
>
> this now still always does this on module load, would be nicer to actually
> only pay for that if needed by adding getter methods for each variable, like
>
> sub get_all_cpu_models {
> initialize_cpu_models() if !defined($all_cpu_models);
> return $all_cpu_models;
> }
>
> Same with a get_cpu_models_by_arch getter.
not sure if that gains us anything, since we need the 'all_cpu_models'
hash statically for the 'reported-model' enum of $cpu_fmt, so even if i
put it in a getter, it would still get initialized on module load...
also not sure if having two seperate getters make sense, since
the 'all_cpu_models' one depends on the cpu_models_by_arch one.
So in that case we'd have to initialize both anyway (again, on module load).
so this would make code a bit more complicated, but I don't really see
the gain here.
>
> And I'd split this and the host_arch change into separate patches, they are rather
> unrelated to each other.
yes, this make sense of course
next prev parent reply other threads:[~2026-02-05 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 10:01 Dominik Csapak
2026-02-04 10:01 ` [PATCH qemu-server v2 2/2] tests: cfg2cmd: add some architecture tests Dominik Csapak
2026-02-04 15:46 ` [PATCH qemu-server v2 1/2] tests: improve multiarch build support Thomas Lamprecht
2026-02-05 7:51 ` Dominik Csapak [this message]
2026-02-05 8:26 ` Dominik Csapak
2026-02-05 8:27 ` Thomas Lamprecht
2026-02-05 8:48 ` Dominik Csapak
2026-02-05 14:25 ` superseded: " Dominik Csapak
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=7fd01f54-4148-4cb4-8d22-bf68d2e9855e@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox