linux-kernel - Getting rid of inside

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 29 Mar 2016 14:37:32 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	Luis Rodriguez <mcgrof@...e.com>,
	Konstantin Ozerkov <kozerkov@...allels.com>,
	Takashi Iwai <tiwai@...e.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	ALSA development <alsa-devel@...a-project.org>
Subject: Getting rid of inside_vm in intel8x0

Would it be possible to revert:

commit 228cf79376f13b98f2e1ac10586311312757675c
Author: Konstantin Ozerkov <kozerkov@...allels.com>
Date:   Wed Oct 26 19:11:01 2011 +0400

    ALSA: intel8x0: Improve performance in virtual environment

Presumably one or more of the following is true:

a) The inside_vm == true case is just an optimization and should apply
unconditionally.

b) The inside_vm == true case is incorrect and should be fixed or disabled.

c) The inside_vm == true case is a special case that makes sense then
IO is very very slow but doesn't make sense when IO is fast.  If so,
why not literally measure the time that the IO takes and switch over
to the "inside VM" path when IO is slow?

There are a pile of nonsensical "are we in a VM" checks of various
sorts scattered throughout the kernel, they're all a mess to maintain
(there are lots of kinds of VMs in the world, and Linux may not even
know it's a guest), and, in most cases, it appears that the correct
solution is to delete the checks.  I just removed a nasty one in the
x86_32 entry asm, and this one is written in C so it should be a piece
of cake :)

--Andy