From: "DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH V2 qemu-server 0/2] add virtio-mem support
Date: Fri, 23 Sep 2022 11:20:09 +0000 [thread overview]
Message-ID: <c43aba154ed378306beceaece69c77e8892ffc6e.camel@groupe-cyllene.com> (raw)
In-Reply-To: <20220824113443.936256-1-aderumier@odiso.com>
Hi,
does somebody had time to review this patch series ?
Does I need to rework it ? Any commment ?
Regards,
Alexandre
Le mercredi 24 août 2022 à 13:34 +0200, Alexandre Derumier a écrit :
> This patch add virtio-mem support, through a new maxmemory option.
>
> a 4GB static memory is needed for DMA+boot memory, as this memory
> is almost always un-unpluggeable.
>
> 1 virtio-mem pci device is setup for each numa node on pci.4 bridge
>
> virtio-mem use a fixed blocksize with 32k max blocksize,
> so blocksize is computed from the maxmemory/32000 with a minimum of
> 2MB to map THP.
> (lower blocksize = more chance to unplug memory).
>
> guests tested:
> - ubuntu 22.04 : kernel 5.15 : works out of the box
> - debian11: kernel 5.10 : don't display new memory value
>
> more info about virtio-mem:
> https://antiphishing.cetsi.fr/proxy/v3?i=RTNLd2NGeE1RTDFrR25iaMqX4l6Z4vdhOnd7odh9trs&r=ZnVkMm1UMHFmWHNzejI1TlfXqTIFgoT3RRT8SRpkUCzNU_sadVHVE4gmJHKxU2tEI-v-lvK2LprrEOT08up8vw&f=UU1XcHkxazJBTmIySlBBMWR_zLcv5a0_cIOSeWbIK2KapikXx8zXaPqWjlzjA2kV1Dznkr2dclNPHmvBavMw9A&u=https%3A//virtio-mem.gitlab.io/&k=ywmE
>
>
> Changelog v2:
>
> - Allow only multiple of 32MB for memory. With lower values, guest
> sometimes
> hang. I have tested with step of 32MB from 4G to 768G, it's
> working fine.
>
> - rebase tests
>
> Alexandre Derumier (2):
> add virtio-mem support
> tests: add virtio-mem tests
>
> PVE/QemuServer.pm | 9 +-
> PVE/QemuServer/Memory.pm | 133 +++++++++++++++---
> --
> PVE/QemuServer/PCI.pm | 8 ++
> test/cfg2cmd/simple-virtio-mem-big.conf | 12 ++
> test/cfg2cmd/simple-virtio-mem-big.conf.cmd | 59 +++++++++
> test/cfg2cmd/simple-virtio-mem.conf | 13 ++
> test/cfg2cmd/simple-virtio-mem.conf.cmd | 31 +++++
> 7 files changed, 236 insertions(+), 29 deletions(-)
> create mode 100644 test/cfg2cmd/simple-virtio-mem-big.conf
> create mode 100644 test/cfg2cmd/simple-virtio-mem-big.conf.cmd
> create mode 100644 test/cfg2cmd/simple-virtio-mem.conf
> create mode 100644 test/cfg2cmd/simple-virtio-mem.conf.cmd
>
prev parent reply other threads:[~2022-09-23 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 11:34 Alexandre Derumier
2022-08-24 11:34 ` [pve-devel] [PATCH V2 qemu-server 1/2] " Alexandre Derumier
2022-08-24 11:34 ` [pve-devel] [PATCH V2 qemu-server 2/2] tests: add virtio-mem tests Alexandre Derumier
2022-09-23 11:20 ` DERUMIER, Alexandre [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=c43aba154ed378306beceaece69c77e8892ffc6e.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.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