On 11/23/23 11:26, Philippe Mathieu-Daudé wrote:
On 23/11/23 09:47, Cédric Le Goater wrote:
On 11/23/23 06:03, Harsh Prateek Bora wrote:
Hi Philippe,
On 11/22/23 16:46, Philippe Mathieu-Daudé wrote:
Hi Harsh,
On 22/11/23 10:28, Harsh Prateek Bora wrote:
Initialize the machine specific
On 23/11/23 09:47, Cédric Le Goater wrote:
On 11/23/23 06:03, Harsh Prateek Bora wrote:
Hi Philippe,
On 11/22/23 16:46, Philippe Mathieu-Daudé wrote:
Hi Harsh,
On 22/11/23 10:28, Harsh Prateek Bora wrote:
Initialize the machine specific max_cpus limit as per the maximum range
of CPU IPIs
On 11/23/23 06:03, Harsh Prateek Bora wrote:
Hi Philippe,
On 11/22/23 16:46, Philippe Mathieu-Daudé wrote:
Hi Harsh,
On 22/11/23 10:28, Harsh Prateek Bora wrote:
Initialize the machine specific max_cpus limit as per the maximum range
of CPU IPIs available. Keeping between 4096 to 8192 will
Hi Philippe,
On 11/22/23 16:46, Philippe Mathieu-Daudé wrote:
Hi Harsh,
On 22/11/23 10:28, Harsh Prateek Bora wrote:
Initialize the machine specific max_cpus limit as per the maximum range
of CPU IPIs available. Keeping between 4096 to 8192 will throw IRQ not
free error due to XIVE/XICS
Hi Harsh,
On 22/11/23 10:28, Harsh Prateek Bora wrote:
Initialize the machine specific max_cpus limit as per the maximum range
of CPU IPIs available. Keeping between 4096 to 8192 will throw IRQ not
free error due to XIVE/XICS limitation and keeping beyond 8192 will hit
assert in tcg_region_init
Initialize the machine specific max_cpus limit as per the maximum range
of CPU IPIs available. Keeping between 4096 to 8192 will throw IRQ not
free error due to XIVE/XICS limitation and keeping beyond 8192 will hit
assert in tcg_region_init or spapr_xive_claim_irq.
Logs:
Without patch fix:
Initialize the machine specific max_cpus limit as per the maximum range
of CPU IPIs available. Keeping between 4096 to 8192 will throw IRQ not
free error due to XIVE/XICS limitation and keeping beyond 8192 will hit
assert in tcg_region_init or spapr_xive_claim_irq.
Logs:
Without patch fix:
