Date:   Thu, 23 Dec 2021 12:05:51 +0100
From:   Borislav Petkov <bp@alien8.de>
To:     Mateusz =?utf-8?Q?Jo=C5=84czyk?= <mat.jonczyk@o2.pl>
Cc:     linux-kernel@vger.kernel.org, x86@kernel.org,
        Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH RESEND v2] x86: warn on native_io_delay() before DMI scan
Message-ID: <YcRYD9drK5lRgEyY@zn.tnic>
References: <20211017192558.266809-1-mat.jonczyk@o2.pl>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20211017192558.266809-1-mat.jonczyk@o2.pl>
Precedence: bulk

On Sun, Oct 17, 2021 at 09:25:58PM +0200, Mateusz Jończyk wrote:
> Writing to IO port 0x80 in native_io_delay() causes system lockups on
> some laptops. This is handled by io_delay_init(), which scans DMI info
> and changes io_delay_type on these laptops.
> 
> Therefore, calling native_io_delay() / outb_p() / inb_p() / etc. before
> io_delay_init() may cause problems there and may constitute a kernel
> bug. Warn if this happens.

When/how does this happen?

io_delay_init() gets called pretty early in setup_arch()...

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette