linux-kernel - Re: [PATCH] x86: Bypass legacy PIC and PIT on ACPI hardware reduced platform

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150304095011.GH3233@pd.tnic>
Date:	Wed, 4 Mar 2015 10:50:11 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Arjan van de Ven <arjan@...ux.intel.com>
Cc:	Ingo Molnar <mingo@...nel.org>,
	"Li, Aubrey" <aubrey.li@...ux.intel.com>,
	"alan@...ux.intel.com" <alan@...ux.intel.com>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>, Len.Brown@...el.com,
	x86@...nel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: Bypass legacy PIC and PIT on ACPI hardware reduced
 platform

On Wed, Mar 04, 2015 at 12:43:08AM -0800, Arjan van de Ven wrote:
> >
> >Using 'acpi_gbl_reduced_hardware' flag outside the ACPI code
> >is a mistake.
> 
> ideally, the presence of that flag in the firmware table will clear/set more global settings,
> for example, having that flag should cause the 8042 input code to not probe for the 8042.
> 
> for interrupts, there really ought to be a "apic first/only" mode, which is then used on
> all modern systems (not just hw reduced).

Do we need some sort of platform-specific querying interfaces now too,
similar to cpu_has()? I.e., platform_has()...

	if (platform_has(X86_PLATFORM_REDUCED_HW))
		do stuff..

Hmmm.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/