From: Thomas Gleixner <tglx@linutronix.de>
To: Michal Necasek <michal.necasek@oracle.com>
Cc: prarit@redhat.com, ville.syrjala@linux.intel.com,
michael.thayer@oracle.com, knut.osmundsen@oracle.com,
frank.mehnert@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: 4.8.2 not booting in 32-bit VM without I/O-APIC
Date: Fri, 28 Oct 2016 21:00:05 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1610282059140.5053@nanos> (raw)
In-Reply-To: <6f385a6a-1f22-4be7-8005-28b714ca271a@default>
On Fri, 28 Oct 2016, Michal Necasek wrote:
>
> Sorry if I wasn't clear. No, it doesn't work for us. The ff8560512b8d
> commit fixes the APIC poking on machines where there is no local APIC
> available (and thus fixes the committer's machine), but it doesn't work
> in our case, where there is a local APIC but no I/O APIC, no ACPI MADT,
> and no MP tables.
> In other words, for us boot_cpu_has(X86_FEATURE_APIC) is true but the
> APIC has not been set up yet because init_apic_mappings() hasn't been
> run.
Gah. Sorry, misunderstood you. Lemme stare in the code.
Thanks,
tglx
next prev parent reply other threads:[~2016-10-28 19:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 18:52 Michal Necasek
2016-10-28 19:00 ` Thomas Gleixner [this message]
2016-10-28 19:34 ` Thomas Gleixner
2016-10-29 10:18 ` Borislav Petkov
2016-10-29 12:04 ` [tip:x86/urgent] x86/smpboot: Init apic mapping before usage tip-bot for Thomas Gleixner
2016-10-29 12:06 ` tip-bot for Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2016-11-03 20:02 4.8.2 not booting in 32-bit VM without I/O-APIC Michal Necasek
2016-11-10 14:21 ` Michael Thayer
2016-11-10 17:18 ` Thomas Gleixner
2016-10-28 18:30 Michal Necasek
2016-10-28 18:38 ` Thomas Gleixner
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=alpine.DEB.2.20.1610282059140.5053@nanos \
--to=tglx@linutronix.de \
--cc=frank.mehnert@oracle.com \
--cc=knut.osmundsen@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.thayer@oracle.com \
--cc=michal.necasek@oracle.com \
--cc=prarit@redhat.com \
--cc=ville.syrjala@linux.intel.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
all inboxes | Powered by JetHome®