From: Dave Hansen <dave.hansen@intel.com>
To: Jari Ruusu <jariruusu@protonmail.com>
Cc: Ashwin Gundarapu <linuxuser509@zohomail.in>,
tglx <tglx@kernel.org>, mingo <mingo@redhat.com>,
bp <bp@alien8.de>, hpa <hpa@zytor.com>, x86 <x86@kernel.org>,
"dave.hansen" <dave.hansen@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] x86/vm86: Remove deprecated VM86 support
Date: Fri, 29 May 2026 07:26:41 -0700 [thread overview]
Message-ID: <fe9e2cf6-e917-40fd-8c9d-38bb0d6caf5c@intel.com> (raw)
In-Reply-To: <gaAiNfez0nVKHDSXYfXdP2CH6AMK1D2q-osVp7F1fefO0_t_9VjrdpKbWNcXkI1-84OtmP0oF6VAtjt0BPIY-8ojOwqv0ncsMXniEP0pL6Q=@protonmail.com>
On 5/28/26 22:20, Jari Ruusu wrote:
> With CONFIG_X86_LEGACY_VM86=y set in 32-bit Linux kernel,
> currently running linux-6.12.91, one memory+CPU intensive
> operation in DOS version of WordPerfect takes less than 0.5
> seconds. With CONFIG_X86_LEGACY_VM86 not set, same operation
> takes about 2 seconds.
Just out of curiosity, what operation is that? How often do you do that
operation in a day or a month?
>> I'm also curious why modern virtualization hardware
>> doesn't help either.
>
> My current setup uses virtualization:
>
> 64-bit x86 host + 64-bit Linux kernel/distro + Qemu/KVM
> --> boots 32-bit Linux kernel/distro ( X86_LEGACY_VM86=y )
> --> boots dosemu + FreeDOS
> --> runs DOS version of WordPerfect
Just like Brian asked, I'm confused why this needs the 32-bit Linux
distro in the mix.
But, if I were you, I'd just keep the 32-bit distro image around, off
the Internet, and never update it. Just like the version of DOS you have
and WordPerfect. The 32-bit distro doesn't need a mainline kernel. It
just gets frozen in place with a 2026 kernel, just like your 1994
version of WordPerfect and DOS are frozen.
As I'm sure you know, that 32-bit distro is getting harder and harder to
keep updated. I've jumped around distros for 32-bit testing a few times
in the last decade as folks retired their 32-bit x86 ports. With Debian
gone, I'd expect its derivatives to die off in the next few years,
making this whole thing even harder.
next prev parent reply other threads:[~2026-05-29 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 7:49 Jari Ruusu
2026-05-28 8:40 ` Ashwin Gundarapu
2026-05-28 14:06 ` Dave Hansen
2026-05-29 5:20 ` Jari Ruusu
2026-05-29 12:05 ` Brian Gerst
2026-05-29 14:26 ` Dave Hansen [this message]
2026-05-30 5:49 ` Jari Ruusu
2026-05-30 6:52 ` H. Peter Anvin
2026-05-30 16:13 ` Brian Gerst
2026-05-31 6:04 ` Jari Ruusu
-- strict thread matches above, loose matches on Subject: below --
2026-05-27 7:31 Ashwin Gundarapu
2026-05-28 9:44 ` kernel test robot
2026-05-28 9:44 ` kernel test robot
2026-05-30 16:26 ` Brian Gerst
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=fe9e2cf6-e917-40fd-8c9d-38bb0d6caf5c@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jariruusu@protonmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxuser509@zohomail.in \
--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
all inboxes | Powered by JetHome®