From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Daniel Bowder <daniel@bowdernet.com>
Cc: pve-devel@lists.proxmox.com
Subject: [pve-devel] applied-series: [PATCH SERIES v2 manager/docs/widget-toolkit/qemu-server 0/4] fix #3593
Date: Thu, 10 Nov 2022 10:57:30 +0100 [thread overview]
Message-ID: <20221110095730.2wazqzfp5yvk65y3@casey.proxmox.com> (raw)
In-Reply-To: <20220701000948.148496-1-daniel@bowdernet.com>
sorry for the delay, applied, thanks
On Thu, Jun 30, 2022 at 05:09:44PM -0700, Daniel Bowder wrote:
> 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
prev parent reply other threads:[~2022-11-10 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 0:09 [pve-devel] " Daniel Bowder
2022-07-01 0:09 ` [pve-devel] [PATCH v2 qemu-server 1/4] fix #3593: add affinity to qemu Daniel Bowder
2022-07-01 0:09 ` [pve-devel] [PATCH v2 pve-docs 2/4] fix #3593: add affinity to docs Daniel Bowder
2022-07-01 0:09 ` [pve-devel] [PATCH v2 proxmox-widget-toolkit 3/4] fix #3593: add CpuSet type to js Daniel Bowder
2022-07-01 0:09 ` [pve-devel] [PATCH v2 pve-manager 4/4] fix #3593: add js input for affinity Daniel Bowder
2022-11-10 9:57 ` Wolfgang Bumiller [this message]
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=20221110095730.2wazqzfp5yvk65y3@casey.proxmox.com \
--to=w.bumiller@proxmox.com \
--cc=daniel@bowdernet.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