linux-kernel - Re: [PATCH v2] x86: hpet: Don't default CONFIG_HPET_TIMER to be y for X86

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: <53352DE5.2090600@ladisch.de>
Date:	Fri, 28 Mar 2014 09:08:05 +0100
From:	Clemens Ladisch <clemens@...isch.de>
To:	Feng Tang <feng.tang@...el.com>, Ingo Molnar <mingo@...nel.org>
CC:	tglx@...utronix.de, mingo@...e.hu, hpa@...or.com,
	linux-kernel@...r.kernel.org, John Stultz <john.stultz@...aro.org>,
	Andy Lutomirski <luto@...capital.net>
Subject: Re: [PATCH v2] x86: hpet: Don't default CONFIG_HPET_TIMER to be y
 for X86_64

Feng Tang wrote:
> On Fri, Mar 28, 2014 at 08:17:16AM +0100, Ingo Molnar wrote:
>> * Feng Tang <feng.tang@...el.com> wrote:
>>  - or the kernel should have a quirk to reliably disable it. Why
>>    should we crash or misbehave if a driver is built into the
>>    kernel?
>
> I thought about this before, HPET doesn't have PCI ID like stuff,

HPET does have the PCI vendor ID in the first register.

> only thing I can think of to identify them may be the CPU family/ID.

The HPET is implemented by some actual chip, and that chip also has lots
of PCI devices.  (In the case of a SoC, the CPU ID would work, too).


Regards,
Clemens
--
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/