lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2504081115310.29566@angie.orcam.me.uk>
Date: Tue, 8 Apr 2025 11:37:02 +0100 (BST)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Oerg866 <oerg866@...glemail.com>
cc: Borislav Petkov <bp@...en8.de>, Kevin Koster <lkml@...ertech.com>, 
    Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org, 
    Ingo Molnar <mingo@...hat.com>, Dave Hansen <dave.hansen@...ux.intel.com>, 
    x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] x86/microcode: Fix crashes on early 486 CPUs due to
 usage of 'cpuid'.

On Mon, 7 Apr 2025, Oerg866 wrote:

> One of my projects uses a modern Linux kernel to install Windows 9x (sorry!)
> onto a legacy (or modern, if that's your thing) systems, including
> magical things like VESA Local Bus 486 systems, way faster than the
> official MS installer ever could. There's quirks here and there, especially
> with regards to libata and obscure IDE/SCSI controllers, but other than
> that the kernel does its job and it does it extremely well.

 FWIW I run a plain EISA 486 box to verify our defxx driver keeps working 
with an EISA FDDI network interface, one of the host bus attachments the 
driver supports.  I also run a dual Pentium MMX box (i430HX chipset), 
which I recently used for i386 GNU toolchain/C library verification in the 
course of upstreaming some stuff for my day job (it's the very box I used 
for APIC fiddling some 25 years ago, which Ingo may remember).

 Both machines are permanently wired for continuous use and remote control 
in my remote lab and run fairly recent versions of the kernel (as my time 
permits upgrading).

 I note that the lack of support for SW DMA mode in libata has degraded 
performance of a PATA drive (the rest is SCSI) in the MMX box compared to 
old IDE code, forcing the drive to use PIO 1.  Alas, I've found no time so 
far to look into porting that stuff over and said drive is not essential 
for that system.

  Maciej

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ