From: Igor Mammedov <imammedo@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [PATCH] x86: q35: require split irqchip for large CPU count
Date: Mon, 14 Mar 2022 11:35:32 +0100 [thread overview]
Message-ID: <20220314113532.10518837@redhat.com> (raw)
In-Reply-To: <8d4912d595bcaca36013e22060c22c1bfe3c44c1.camel@infradead.org>
On Fri, 11 Mar 2022 14:58:41 +0000
David Woodhouse <dwmw2@infradead.org> wrote:
> On Fri, 2022-03-11 at 09:39 -0500, Igor Mammedov wrote:
> > if VM is started with:
> >
> > -enable-kvm -smp 256
> >
> > without specifying 'split' irqchip, VM might eventually boot
> > but no more than 255 CPUs will be operational and following
> > error messages in guest could be observed:
> > ...
> > smpboot: native_cpu_up: bad cpu 256
> > ...
> > It's a regression introduced by [1], which removed dependency
> > on intremap=on that were implicitly requiring 'split' irqchip
> > and forgot to check for 'split' irqchip.
> > Instead of letting VM boot a broken VM, error out and tell
> > user how to fix CLI.
>
> Hm, wasn't that already fixed in the patches I posted in December?
It might be, could you point to the commit/series that fixed it.
Regardless of that, fixing it in recent kernels doesn't help
as still supported kernels are still affected by it.
If there is a way to detect that fix, I can add to q35 a compat
property and an extra logic to enable kernel-irqchip if fix is present.
Otherwise the fix does not exist until minimum supported kernel
version reaches version where it was fixed.
next prev parent reply other threads:[~2022-03-14 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 14:39 [PATCH] x86: q35: require split irqchip for large CPU count Igor Mammedov
2022-03-11 14:58 ` David Woodhouse
2022-03-14 10:35 ` Igor Mammedov [this message]
2022-03-14 12:59 ` David Woodhouse
2022-03-14 13:21 ` Daniel P. Berrangé
2022-03-14 14:21 ` David Woodhouse
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=20220314113532.10518837@redhat.com \
--to=imammedo@redhat.com \
--cc=dwmw2@infradead.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).