From: "Jürgen Groß" <jgross@suse.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v4 5/6] x86/io_delay: Switch io_delay() default mechanism to "none"
Date: Sat, 21 Mar 2026 07:29:11 +0100 [thread overview]
Message-ID: <4db42461-e2e4-42e3-ac67-dc147dd2683d@suse.com> (raw)
In-Reply-To: <20260320220240.GYab3EAHaSKb0LMzP8@fat_crate.local>
[-- Attachment #1.1.1: Type: text/plain, Size: 809 bytes --]
On 20.03.26 23:02, Borislav Petkov wrote:
> On Mon, Jan 19, 2026 at 07:26:31PM +0100, Juergen Gross wrote:
>> The habit to delay some port operations via io_delay() is probably a
>> no longer needed relict from i386 times.
>>
>> Switch the default to no longer do delays for port operations. In case
>> this is breaking some still supported hardware, the default can still
>> be overwritten via boot parameter.
>
> So machines which worked perfectly fine until now, would break and would all
> of a sudden need a cmdline param?
This patch is the result of a suggestion by Ingo [1]. He even wanted to rip out
the io_delay() code completely.
If you don't like that, we can just drop patches 5 and 6 of the series.
Juergen
[1]: https://lore.kernel.org/lkml/aUFjRDqbfWMsXvvS@gmail.com/
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2026-03-21 6:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 18:26 [PATCH v4 0/6] x86: Cleanups around slow_down_io() Juergen Gross
2026-01-19 18:26 ` [PATCH v4 1/6] x86/irqflags: Fix build failure Juergen Gross
2026-03-21 15:47 ` [tip: x86/cleanups] x86/irqflags: Preemptively move include paravirt.h directive where it belongs tip-bot2 for Juergen Gross
2026-03-22 7:47 ` tip-bot2 for Juergen Gross
2026-01-19 18:26 ` [PATCH v4 2/6] x86/paravirt: Replace io_delay() hook with a bool Juergen Gross
2026-03-21 15:47 ` [tip: x86/cleanups] " tip-bot2 for Juergen Gross
2026-03-22 7:46 ` tip-bot2 for Juergen Gross
2026-01-19 18:26 ` [PATCH v4 3/6] block/floppy: Don't use REALLY_SLOW_IO for delays Juergen Gross
2026-03-21 15:47 ` [tip: x86/cleanups] " tip-bot2 for Juergen Gross
2026-03-22 7:46 ` tip-bot2 for Juergen Gross
2026-01-19 18:26 ` [PATCH v4 4/6] x86/io: Remove REALLY_SLOW_IO handling Juergen Gross
2026-03-26 8:39 ` Juergen Gross
2026-03-26 10:04 ` Borislav Petkov
2026-03-26 10:23 ` Jürgen Groß
2026-01-19 18:26 ` [PATCH v4 5/6] x86/io_delay: Switch io_delay() default mechanism to "none" Juergen Gross
2026-03-20 22:02 ` Borislav Petkov
2026-03-21 6:29 ` Jürgen Groß [this message]
2026-03-21 11:32 ` Borislav Petkov
2026-01-19 18:26 ` [PATCH v4 6/6] x86/io_delay: Add config option for controlling build of io_delay Juergen Gross
2026-02-02 10:27 ` [PATCH v4 0/6] x86: Cleanups around slow_down_io() Juergen Gross
2026-02-09 9:11 ` Juergen Gross
2026-02-09 10:19 ` Borislav Petkov
2026-03-11 9:16 ` Juergen Gross
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=4db42461-e2e4-42e3-ac67-dc147dd2683d@suse.com \
--to=jgross@suse.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.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