From: Juergen Gross <jgross@suse.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org,
virtualization@lists.linux.dev, kvm@vger.kernel.org,
linux-block@vger.kernel.org
Cc: Juergen Gross <jgross@suse.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Ajay Kaher <ajay.kaher@broadcom.com>,
Alexey Makhalov <alexey.makhalov@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xenproject.org, Denis Efremov <efremov@linux.com>,
Jens Axboe <axboe@kernel.dk>
Subject: [PATCH v2 0/5] x86: Cleanups around slow_down_io()
Date: Tue, 16 Dec 2025 14:41:44 +0100 [thread overview]
Message-ID: <20251216134150.2710-1-jgross@suse.com> (raw)
While looking at paravirt cleanups I stumbled over slow_down_io() and
the related REALLY_SLOW_IO define.
Do several cleanups, resulting in a deletion of REALLY_SLOW_IO and the
io_delay() paravirt function hook.
Patch 4 is removing the config options for selecting the default delay
mechanism and sets the default to "no delay". This is in preparation of
removing the io_delay() functionality completely, as suggested by Ingo
Molnar.
Patch 5 is adding an additional config option allowing to avoid
building io_delay.c (default is still to build it).
Changes in V2:
- patches 2 and 3 of V1 have been applied
- new patches 4 and 5
Juergen Gross (5):
x86/paravirt: Replace io_delay() hook with a bool
block/floppy: Don't use REALLY_SLOW_IO for delays
x86/io: Remove REALLY_SLOW_IO handling
x86/io_delay: Switch io_delay() default mechanism to "none"
x86/io_delay: Add config option for controlling build of io_delay.
arch/x86/Kconfig | 8 +++
arch/x86/Kconfig.debug | 30 ----------
arch/x86/include/asm/floppy.h | 31 ++++++++--
arch/x86/include/asm/io.h | 17 +++---
arch/x86/include/asm/paravirt.h | 11 +---
arch/x86/include/asm/paravirt_types.h | 3 +-
arch/x86/kernel/Makefile | 3 +-
arch/x86/kernel/cpu/vmware.c | 2 +-
arch/x86/kernel/io_delay.c | 81 +--------------------------
arch/x86/kernel/kvm.c | 8 +--
arch/x86/kernel/paravirt.c | 3 +-
arch/x86/kernel/setup.c | 4 +-
arch/x86/xen/enlighten_pv.c | 6 +-
drivers/block/floppy.c | 2 -
14 files changed, 55 insertions(+), 154 deletions(-)
--
2.51.0
next reply other threads:[~2025-12-16 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 13:41 Juergen Gross [this message]
2025-12-16 13:41 ` [PATCH v2 1/5] x86/paravirt: Replace io_delay() hook with a bool Juergen Gross
2026-01-09 12:07 ` [PATCH v2 0/5] x86: Cleanups around slow_down_io() 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=20251216134150.2710-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=ajay.kaher@broadcom.com \
--cc=alexey.makhalov@broadcom.com \
--cc=axboe@kernel.dk \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=efremov@linux.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux.dev \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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