[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aUFjRDqbfWMsXvvS@gmail.com>
Date: Tue, 16 Dec 2025 14:48:52 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Jürgen Groß <jgross@...e.com>
Cc: linux-kernel@...r.kernel.org, x86@...nel.org,
virtualization@...ts.linux.dev, kvm@...r.kernel.org,
linux-hwmon@...r.kernel.org, linux-block@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>,
Ajay Kaher <ajay.kaher@...adcom.com>,
Alexey Makhalov <alexey.makhalov@...adcom.com>,
Broadcom internal kernel review list <bcm-kernel-feedback-list@...adcom.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
xen-devel@...ts.xenproject.org, Jean Delvare <jdelvare@...e.com>,
Guenter Roeck <linux@...ck-us.net>,
Denis Efremov <efremov@...ux.com>, Jens Axboe <axboe@...nel.dk>
Subject: Re: [PATCH 0/5] x86: Cleanups around slow_down_io()
* Jürgen Groß <jgross@...e.com> wrote:
> > CPUs anymore. Should it cause any regressions, it's easy to bisect to.
> > There's been enough changes around all these facilities that the
> > original timings are probably way off already, so we've just been
> > cargo-cult porting these to newer kernels essentially.
>
> Fine with me.
>
> Which path to removal of io_delay would you (and others) prefer?
>
> 1. Ripping it out immediately.
I'd just rip it out immediately, and see who complains. :-)
Whatever side effects it still may have, I very strongly doubt it has
anything to do with the original purpose of IO delays...
> In cases 2-4 I'd still like to have patch 1 of my series applied, as it will
> make paravirt rework easier.
Sure.
Thanks,
Ingo
Powered by blists - more mailing lists