| 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
| ||
|
Message-Id: <201010072344.22166.rjw@sisk.pl> Date: Thu, 7 Oct 2010 23:44:21 +0200 From: "Rafael J. Wysocki" <rjw@...k.pl> To: Greg KH <gregkh@...e.de> Cc: Sameer Nanda <snanda@...omium.org>, lenb@...nel.org, stefan.bader@...onical.com, brad.figg@...onical.com, apw@...onical.com, linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] ACPI: Read TSC upon resume On Thursday, October 07, 2010, Greg KH wrote: > On Thu, Oct 07, 2010 at 11:05:21AM -0700, Sameer Nanda wrote: > > On Thu, Oct 7, 2010 at 10:46 AM, Greg KH <gregkh@...e.de> wrote: > > > On Thu, Oct 07, 2010 at 10:43:34AM -0700, Sameer Nanda wrote: > > >> On Wed, Oct 6, 2010 at 7:19 PM, Greg KH <gregkh@...e.de> wrote: > > >> > And are you always going to be printing this out? Why do we want to > > >> > know this every time? > > >> > > > >> > > >> Yes, every time. This helps track variance in BIOS resume times within a > > >> single boot. > > > > > > Is that really something that users can do something about? > > > > Aside from complaining to the BIOS vendors, no :) > > Then I would not recommend adding this patch, as it is irrelevant for > 99.9999% of all Linux users. It may be somewhat useful, but the rdtscll() call seems to be x86-specific, in which case it shouldn't be used at this place. Thanks, Rafael -- 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/
Powered by blists - more mailing lists