public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Filip Schauer <f.schauer@proxmox.com>
Subject: Re: [pve-devel] [PATCH common 1/1] tools: Add is_native sub to compare the CPU architecture
Date: Mon, 19 Feb 2024 15:46:56 +0100	[thread overview]
Message-ID: <848a06d3-a136-482b-9fa4-07971c956a55@proxmox.com> (raw)
In-Reply-To: <20231219094023.25726-2-f.schauer@proxmox.com>

Am 19.12.23 um 10:40 schrieb Filip Schauer:
> Add an is_native($arch) subroutine to compare a CPU architecture to the
> host CPU architecture. This is brought in from PVE::QemuServer.
> 
> Signed-off-by: Filip Schauer <f.schauer@proxmox.com>
> ---
>  src/PVE/Tools.pm | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/src/PVE/Tools.pm b/src/PVE/Tools.pm
> index 766c809..7bb1809 100644
> --- a/src/PVE/Tools.pm
> +++ b/src/PVE/Tools.pm
> @@ -52,6 +52,7 @@ extract_param
>  extract_sensitive_params
>  file_copy
>  get_host_arch
> +is_native
>  O_PATH
>  O_TMPFILE
>  AT_EMPTY_PATH
> @@ -1841,6 +1842,11 @@ sub get_host_arch {
>      return $host_arch;
>  }
>  
> +sub is_native($) {

This is a too generic name to put in such a generic module like Tools.
Admittedly, it's also a too generic name in QemuServer IMHO ;) Maybe
arch_is_native() or is_native_arch()?

I'm not fully convinced the move is worth it, but it does belong to
get_host_arch() semantically, so fine by me.

> +    my ($arch) = @_;
> +    return get_host_arch() eq $arch;
> +}
> +
>  # Devices are: [ (12 bits minor) (12 bits major) (8 bits minor) ]
>  sub dev_t_major($) {
>      my ($dev_t) = @_;




  reply	other threads:[~2024-02-19 14:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  9:40 [pve-devel] [PATCH-SERIES v7 qemu-server, common] Prevent starting a 32-bit VM using a 64-bit OVMF BIOS Filip Schauer
2023-12-19  9:40 ` [pve-devel] [PATCH common 1/1] tools: Add is_native sub to compare the CPU architecture Filip Schauer
2024-02-19 14:46   ` Fiona Ebner [this message]
2024-02-21 14:37     ` Filip Schauer
2023-12-19  9:40 ` [pve-devel] [PATCH qemu-server 1/4] cpu config: Add helper to get the default CPU type Filip Schauer
2024-02-19 14:47   ` Fiona Ebner
2023-12-19  9:40 ` [pve-devel] [PATCH v7 qemu-server 2/4] Prevent starting a 32-bit VM using a 64-bit OVMF BIOS Filip Schauer
2024-02-19 14:47   ` Fiona Ebner
2024-02-19 14:58     ` Fiona Ebner
2023-12-19  9:40 ` [pve-devel] [PATCH qemu-server 3/4] Move is_native from PVE::QemuServer to PVE::Tools Filip Schauer
2023-12-19  9:40 ` [pve-devel] [PATCH qemu-server 4/4] cpu config: Unify the default value for 'kvm' Filip Schauer
2024-02-19 14:47   ` Fiona Ebner
2024-02-21 15:39     ` Filip Schauer
2024-02-22  9:35       ` Fiona Ebner
2024-02-23 11:59         ` Filip Schauer

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=848a06d3-a136-482b-9fa4-07971c956a55@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=f.schauer@proxmox.com \
    --cc=pve-devel@lists.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal