From: Stefan Reiter <s.reiter@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC 0/9] Unfinished: Custom CPU type API and GUI
Date: Thu, 28 Oct 2021 13:41:41 +0200 [thread overview]
Message-ID: <20211028114150.3245864-1-s.reiter@proxmox.com> (raw)
For someone to pick up, please :)
This is some rather old code I had lying around, rebased and slightly fixed up
to build. Doesn't currently work as intended, but gets somewhat close.
Includes the API (mostly stable AFAICT, only some stuff broken during the time
it was lying around) and the GUI (structure looks decent, but editor window is
bugged heavily).
The QEMU patch is necessary to query the CPU flags added by default CPU and
machine type combinations, it could also be exported the same way we do for the
"all recognized flags" file, but that would be quite many files and would have
to stay up-to-date with supported CPU models in QEMU.
pve-qemu: Stefan Reiter (1):
Add -list-flags command line option
...E-Add-list-flags-command-line-option.patch | 213 ++++++++++++++++++
debian/patches/series | 1 +
2 files changed, 214 insertions(+)
create mode 100644 debian/patches/pve/0049-PVE-Add-list-flags-command-line-option.patch
qemu-server: Stefan Reiter (3):
api: add recognized-flags and supported-flags endpoints
api: add /cpu/model/* get endpoint
api: add /cpu/model/* get/create/delete/update endpoints
PVE/API2/Qemu/CPU.pm | 334 +++++++++++++++++++++++++++++++++++-
PVE/QemuServer/CPUConfig.pm | 24 ++-
2 files changed, 356 insertions(+), 2 deletions(-)
manager: Stefan Reiter (5):
gui: VMCPUFlagSelector: fix unknownFlags behaviour
gui: CPUModelSelector: fix dirty state on default
gui: CPUModelSelector: add 'allowCustom'
gui: add basic custom CPU model editor
Initial attempt at CPU flag editor for custom models
www/css/ext6-pve.css | 4 +
www/manager6/Makefile | 3 +
www/manager6/dc/CPUTypeEdit.js | 89 +++++++++++++++
www/manager6/dc/CPUTypeView.js | 148 +++++++++++++++++++++++++
www/manager6/dc/Config.js | 6 +
www/manager6/form/CPUModelSelector.js | 22 ++++
www/manager6/form/PhysBitsSelector.js | 128 +++++++++++++++++++++
www/manager6/form/VMCPUFlagSelector.js | 127 ++++++++++++++++-----
8 files changed, 501 insertions(+), 26 deletions(-)
create mode 100644 www/manager6/dc/CPUTypeEdit.js
create mode 100644 www/manager6/dc/CPUTypeView.js
create mode 100644 www/manager6/form/PhysBitsSelector.js
--
2.30.2
next reply other threads:[~2021-10-28 11:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 11:41 Stefan Reiter [this message]
2021-10-28 11:41 ` [pve-devel] [RFC pve-qemu 1/9] Add -list-flags command line option Stefan Reiter
2021-10-28 11:41 ` [pve-devel] [RFC qemu-server 2/9] api: add recognized-flags and supported-flags endpoints Stefan Reiter
2021-10-28 11:41 ` [pve-devel] [RFC qemu-server 3/9] api: add /cpu/model/* get endpoint Stefan Reiter
2021-10-28 11:41 ` [pve-devel] [RFC qemu-server 4/9] api: add /cpu/model/* get/create/delete/update endpoints Stefan Reiter
2021-10-28 11:41 ` [pve-devel] [RFC manager 5/9] gui: VMCPUFlagSelector: fix unknownFlags behaviour Stefan Reiter
2021-10-28 11:41 ` [pve-devel] [RFC manager 6/9] gui: CPUModelSelector: fix dirty state on default Stefan Reiter
2021-10-28 11:41 ` [pve-devel] [RFC manager 7/9] gui: CPUModelSelector: add 'allowCustom' Stefan Reiter
2021-10-28 11:41 ` [pve-devel] [RFC manager 8/9] gui: add basic custom CPU model editor Stefan Reiter
2021-10-28 11:41 ` [pve-devel] [RFC manager 9/9] Initial attempt at CPU flag editor for custom models Stefan Reiter
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=20211028114150.3245864-1-s.reiter@proxmox.com \
--to=s.reiter@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