From: Daniel Bowder <daniel@bowdernet.com>
To: pve-devel@lists.proxmox.com, Matthias Heiserer <m.heiserer@proxmox.com>
Subject: Re: [pve-devel] [PATCH 3/5] fix #3593: Added vm core pinning qemu-server
Date: Thu, 9 Jun 2022 08:46:14 -0700 [thread overview]
Message-ID: <CA+=Vt23JrT=mVLZ2vecZFztEtUDuCryEni2DxCsDpOjP5_zJRg@mail.gmail.com> (raw)
> Can we avoid showing them? I don't think they offer any insight, because
> as I understand it, when starting, the current affinity list is always
> all available cores.
Yes, I have made this change and will add it to my next patch. The change
is simple
adding the 'quiet => 1' argument to the PVE::Tools::run_command() function.
next reply other threads:[~2022-06-09 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 15:46 Daniel Bowder [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-08 11:54 [pve-devel] [PATCH 0/5] fix #3593: Added vm core pinning Daniel Bowder
2022-06-08 11:54 ` [pve-devel] [PATCH 3/5] fix #3593: Added vm core pinning qemu-server Daniel Bowder
2022-06-08 14:45 ` Matthias Heiserer
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='CA+=Vt23JrT=mVLZ2vecZFztEtUDuCryEni2DxCsDpOjP5_zJRg@mail.gmail.com' \
--to=daniel@bowdernet.com \
--cc=m.heiserer@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