From: Marc Zyngier <maz@kernel.org>
To: Eric Auger <eric.auger@redhat.com>
Cc: yuzenghui@huawei.com, peter.maydell@linaro.org,
qemu-arm@nongnu.org, qemu-devel@nongnu.org,
eric.auger.pro@gmail.com
Subject: Re: [PATCH v4 0/3] KVM/ARM: Fix >256 vcpus
Date: Thu, 03 Oct 2019 18:43:59 +0100 [thread overview]
Message-ID: <86d0fdrag0.wl-maz@kernel.org> (raw)
In-Reply-To: <20191003154640.22451-1-eric.auger@redhat.com>
On Thu, 03 Oct 2019 16:46:37 +0100,
Eric Auger <eric.auger@redhat.com> wrote:
>
> Since 4.18, KVM/ARM exposes a KVM_MAX_VCPUS equal to 512. However it was
> reported [1] that a VM with more than 256 vcpus cannot be launched. 5.4
> fixes the situation with 2 patches:
> - one upgrade of the KVM_IRQ_LINE API [2] supporting a vcpu id encoded
> on 12 bits,
> - the reduction of KVM IO devices consumed by each GICv3 redistributor [3]
>
> This series uses the new KVM_IRQ_LINE API and also checks the associated
> capability (KVM_CAP_ARM_IRQ_LINE_LAYOUT_2) in machvirt.
>
> Without the series, as soon as the -smp arguments exceeds 256, QEMU exits
> with "kvm_set_irq: Invalid argument".
FWIW, and for the whole series:
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Jazz is not dead, it just smells funny.
next prev parent reply other threads:[~2019-10-03 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 15:46 [PATCH v4 0/3] KVM/ARM: Fix >256 vcpus Eric Auger
2019-10-03 15:46 ` [PATCH v4 1/3] linux headers: update against v5.4-rc1 Eric Auger
2019-10-03 15:46 ` [PATCH v4 2/3] intc/arm_gic: Support IRQ injection for more than 256 vpus Eric Auger
2019-10-03 15:46 ` [PATCH v4 3/3] ARM: KVM: Check KVM_CAP_ARM_IRQ_LINE_LAYOUT_2 for smp_cpus > 256 Eric Auger
2019-10-03 17:43 ` Marc Zyngier [this message]
2019-10-14 12:48 ` [PATCH v4 0/3] KVM/ARM: Fix >256 vcpus Peter Maydell
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=86d0fdrag0.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=yuzenghui@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.