From: "Cédric Le Goater" <clg@kaod.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: "Satheesh Rajendran" <sathnaga@linux.vnet.ibm.com>,
"Cédric Le Goater" <clg@kaod.org>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
"Greg Kurz" <groug@kaod.org>
Subject: [Qemu-devel] [PATCH v2 0/2] spapr: reduce the number of IRQ
Date: Wed, 11 Sep 2019 15:39:35 +0200 [thread overview]
Message-ID: <20190911133937.2716-1-clg@kaod.org> (raw)
Hello,
A typical pseries VM with 16 vCPUs, one disk, one network adapater
uses less than 100 interrupts but the whole IRQ number space of the
QEMU machine is allocated at reset time and it is 8K wide. This is
wasting a considerable amount of interrupt numbers in the global IRQ
space which has 1M interrupts per socket on a POWER9.
To optimise the HW resources, only request at the KVM level interrupts
which have been claimed by the guest. This will help to increase the
maximum number of VMs per system and also help supporting nested
guests using the XIVE interrupt mode.
Thanks,
C.
Changes since v1:
- split the patch
- removed useless 'reset_all' machine flag which supposed to preserve
migration compatibility
Cédric Le Goater (2):
spapr/irq: Introduce an ics_irq_free() helper
spapr/irq: Only claim VALID interrupts at the KVM level
include/hw/ppc/xics.h | 5 +++++
hw/intc/spapr_xive_kvm.c | 29 ++++++++++++++++++++++++++---
hw/intc/xics_kvm.c | 8 ++++++++
hw/ppc/spapr_irq.c | 9 +++------
4 files changed, 42 insertions(+), 9 deletions(-)
--
2.21.0
next reply other threads:[~2019-09-11 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 13:39 Cédric Le Goater [this message]
2019-09-11 13:39 ` [Qemu-devel] [PATCH v2 1/2] spapr/irq: Introduce an ics_irq_free() helper Cédric Le Goater
2019-09-11 14:09 ` Greg Kurz
2019-09-16 0:38 ` David Gibson
2019-09-11 13:39 ` [Qemu-devel] [PATCH v2 2/2] spapr/irq: Only claim VALID interrupts at the KVM level Cédric Le Goater
2019-09-11 14:14 ` Greg Kurz
2019-09-16 0:44 ` David Gibson
2019-09-25 15:41 ` Greg Kurz
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=20190911133937.2716-1-clg@kaod.org \
--to=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sathnaga@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).