From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 0C06678E70 for ; Fri, 1 Jul 2022 02:10:38 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 02E673A51 for ; Fri, 1 Jul 2022 02:10:08 +0200 (CEST) Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Fri, 1 Jul 2022 02:10:03 +0200 (CEST) Received: by mail-pg1-x52c.google.com with SMTP id 23so857834pgc.8 for ; Thu, 30 Jun 2022 17:10:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bowdernet.com; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=yVjohYMsBLyB7njn1ApOwDR4roOTLvbkAWFjr+NXbU0=; b=CSTUfVEh0raLPli9sYupLA6D9mJaXEkPneca9OFP28/mrA/hKmOuiPSoYfHjXoUMIc gB1sDah0/lgxb/OupCvRCvKOTtWCY97mxI1jyWPpMSIKRQOr6Nv4SXungFJZbFneEmcS PzA+5gTiwgvfaVqc43E7vO6TIuYk/xpcZCIpWX9mU3V4R6npvtuFAXyvwehAg/DHsHG3 O+hNJb2I9dtjlDMZgAJq5lvc6vWqJI5UGDPwSZlPH6qfyfr0KxHWiThVt2NEIHq6fgSn P83PL1A7GbW7NFfajC+/hSOzah7EWXrq0PJdLo5UKKxqHSVGmdhMjXF4NoQGSZGZCyST v4Eg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=yVjohYMsBLyB7njn1ApOwDR4roOTLvbkAWFjr+NXbU0=; b=fPrk6powNBbclMHSURj6RFWs5L1l0svxSp/vzlhm3albBIIMB/+T0de7AX4iu80erN Yz2fJ+5H6jrvctBlsF+XkTAypX/b/mNs9TM8i9ocSppKHveLCohaKJe0TT1Z7s7voCC7 nudIF9dsCOqY2OkjGpdQOu/3378apDgyfDCMl8Kfntf18mWRGsFEqlgS40CTT+enhOTz +bkMaA4uZWkR+IZ+B4rlstwyM0YSkCsRR1WCqDKfz7ayWTVwAcoRFJ2nFrW/+MMEYCQL UipAWLK7ggQRkn7BTpUoOm8CbT5XdBHn15FmPyvt7C+/ZxK8W1Jz5ZCf0S0NdwgtI1mz yGdA== X-Gm-Message-State: AJIora/pZW8z4ildWUpOl6oBFHF4P0TxglhWUWhYxRrCIYYnIo5QKNx5 4MinxAgbdAtJO6d7Mg67xImqm0Xcfv956qrA X-Google-Smtp-Source: AGRyM1s7FjeFqyybexstws+t2TsUzrAwzySq2lKH+7GplWXc51mhn4kkOG+LriI85NyW5MxJA01duA== X-Received: by 2002:a63:3848:0:b0:40c:8ad3:d170 with SMTP id h8-20020a633848000000b0040c8ad3d170mr9719038pgn.175.1656634194683; Thu, 30 Jun 2022 17:09:54 -0700 (PDT) Received: from localhost.localdomain (c-24-19-168-226.hsd1.wa.comcast.net. [24.19.168.226]) by smtp.gmail.com with ESMTPSA id g6-20020a631106000000b004114aad90ebsm7296066pgl.49.2022.06.30.17.09.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 30 Jun 2022 17:09:54 -0700 (PDT) From: Daniel Bowder To: pve-devel@lists.proxmox.com Cc: Daniel Bowder Date: Thu, 30 Jun 2022 17:09:44 -0700 Message-Id: <20220701000948.148496-1-daniel@bowdernet.com> X-Mailer: git-send-email 2.36.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.250 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain KAM_NUMSUBJECT 0.5 Subject ends in numbers excluding current years RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pve-devel] [PATCH SERIES v2 manager/docs/widget-toolkit/qemu-server 0/4] fix #3593 X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2022 00:10:38 -0000 Summary: Allows for virtual machines to be pinned to CPU cores via an affinity value added to the qemu configuration. I previously created a v1 of this patch, but it was my first submission and had lots of formatting issues. This patch is v2. The affinity input can be found on the CPU Edit page for virtual machines. v1 can be found here: https://lists.proxmox.com/pipermail/pve-devel/2022-June/053219.html V1 -> V2: * Adhere better to style guides * Reuse PVE::CpuSet instead of reinventing the wheel * Change new qemu conf parameter from 'cpuset' to 'affinity' * Exec kvm using taskset to pin processes qemu-server: Daniel Bowder (1): fix #3593: add affinity to qemu conf, launch taskset before kvm PVE/QemuServer.pm | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) docs: Daniel Bowder (1): fix #3593: add affinity to qm.conf docs qm.adoc | 15 +++++++++++++++ qm.conf.5-opts.adoc | 4 ++++ 2 files changed, 19 insertions(+) widget-toolkit: Daniel Bowder (1): fix #3593: add CpuSet type to js frontend src/Toolkit.js | 20 ++++++++++++++++++++ src/Utils.js | 2 ++ 2 files changed, 22 insertions(+) manager: Daniel Bowder (1): fix #3593: add js input for affinity www/manager6/qemu/ProcessorEdit.js | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) -- 2.36.1