From: Harsh Prateek Bora <harshpb@linux.ibm.com>
To: npiggin@gmail.com, qemu-ppc@nongnu.org
Cc: danielhb413@gmail.com, clg@kaod.org, david@gibson.dropbear.id.au,
qemu-devel@nongnu.org, harshpb@linux.ibm.com
Subject: [PATCH v3 0/2] Introduce SPAPR_IRQ_NR_IPIS and fix max-cpus
Date: Thu, 23 Nov 2023 11:27:31 +0530 [thread overview]
Message-ID: <20231123055733.1002890-1-harshpb@linux.ibm.com> (raw)
On spapr, the max number of CPU IPIs are 4096 which is accounted during
spapr_irq_init but currently existing macro SPAPR_XIRQ_BASE is being
used to refer to that. Introducing SPAPR_IRQ_NR_IPIS to refer to the range
of CPU IPIS which is being further used to initialize mc->max_cpus
during spapr_machine_class_init().
v3:
- addressed further review comments from Cedric
v2:
- addressed review comments from Cedric
Harsh Prateek Bora (2):
ppc/spapr: Introduce SPAPR_IRQ_NR_IPIS to refer IRQ range for CPU
IPIs.
ppc/spapr: Initialize max_cpus limit to SPAPR_IRQ_NR_IPIS.
include/hw/ppc/spapr_irq.h | 14 +++++++++++++-
hw/ppc/spapr.c | 9 +++------
hw/ppc/spapr_irq.c | 6 ++++--
3 files changed, 20 insertions(+), 9 deletions(-)
--
2.39.3
next reply other threads:[~2023-11-23 5:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 5:57 Harsh Prateek Bora [this message]
2023-11-23 5:57 ` [PATCH v3 1/2] ppc/spapr: Introduce SPAPR_IRQ_NR_IPIS to refer IRQ range for CPU IPIs Harsh Prateek Bora
2023-11-23 8:50 ` Cédric Le Goater
2023-11-23 9:31 ` Harsh Prateek Bora
2023-11-23 14:12 ` Cédric Le Goater
2023-11-24 8:01 ` Harsh Prateek Bora
2023-11-24 8:09 ` Cédric Le Goater
2024-01-03 12:05 ` Kowshik Jois B S
2023-11-23 5:57 ` [PATCH v3 2/2] ppc/spapr: Initialize max_cpus limit to SPAPR_IRQ_NR_IPIS Harsh Prateek Bora
2023-11-23 8:51 ` Cédric Le Goater
2024-01-03 12:23 ` Kowshik Jois B S
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=20231123055733.1002890-1-harshpb@linux.ibm.com \
--to=harshpb@linux.ibm.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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).