All of lore.kernel.org
 help / color / mirror / Atom feed
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 RESEND v2 0/2] Introduce SPAPR_NR_IPIS and fix max-cpus
Date: Wed, 22 Nov 2023 14:58:43 +0530	[thread overview]
Message-ID: <20231122092845.973949-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_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().

Harsh Prateek Bora (2):
  ppc/spapr: Introduce SPAPR_NR_IPIS to refer IRQ range for CPU IPIs.
  ppc/spapr: Initialize max_cpus limit to SPAPR_NR_IPIS.

 hw/ppc/spapr.c             | 9 +++------
 hw/ppc/spapr_irq.c         | 4 ++--
 include/hw/ppc/spapr_irq.h | 1 +
 3 files changed, 6 insertions(+), 8 deletions(-)

-- 
2.39.3



             reply	other threads:[~2023-11-22  9:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22  9:28 Harsh Prateek Bora [this message]
2023-11-22  9:28 ` [PATCH v2 1/2] ppc/spapr: Introduce SPAPR_NR_IPIS to refer IRQ range for CPU IPIs Harsh Prateek Bora
2023-11-22 11:12   ` Philippe Mathieu-Daudé
2023-11-22 11:13   ` Philippe Mathieu-Daudé
2023-11-22 11:16     ` Cédric Le Goater
2023-11-22 11:31   ` Cédric Le Goater
2023-11-23  5:04     ` Harsh Prateek Bora
2023-11-22  9:28 ` [PATCH v2 2/2] ppc/spapr: Initialize max_cpus limit to SPAPR_NR_IPIS Harsh Prateek Bora
2023-11-22 11:16   ` Philippe Mathieu-Daudé
2023-11-23  5:03     ` Harsh Prateek Bora
2023-11-23  8:47       ` Cédric Le Goater
2023-11-23 10:26         ` Philippe Mathieu-Daudé
2023-11-23 13:51           ` Cédric Le Goater

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=20231122092845.973949-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 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.