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
| ||
|
Date: Thu, 18 Jul 2013 15:04:25 -0700 From: Richard Henderson <rth@...ddle.net> To: Michael Cree <cree@...kato.ac.nz> CC: linux-kernel@...r.kernel.org, ink@...assic.park.msu.ru, mattst88@...il.com, linux-alpha@...r.kernel.org Subject: Re: [RFC PATCH 00/10] Alpha support for QEMU On 07/18/2013 02:28 PM, Michael Cree wrote: > The kernel without the patch set has the "Using epoch 2000" line and > the kernel with the patch set is missing the "Using epoch 2000" line. Ah hah. You appear to be missing CONFIG_RTC_DRV_ALPHA in the new kernel, so you have no support for the RTC at all. Please re-try. > On the kernel without the patch set the dummy-RTC timer interrupt received > 30876 interrupts in a 30s period which is within measurement uncertainty of > the expected 30*1024 = 30720 interrupts. > > On the kernel with the patch set the dummy-RTC timer interrupt received 14419 > interrupts on CPU-1, 13935 interrupts on CPU-2 and 2619 interrupts on CPU-3 > over a 30s period. Grr. Naturally, the old kernel obfuscates which timers are being delivered where. So a direct comparison doesn't appear possible. But those separated numbers seem uncomfortably low. I've just pushed a new branch to git://github.com/rth7680/linux.git axp-qemu-7 Please try that with CONFIG_ALPHA_WTINT disabled. I'd like to eliminate that as a source of uncertainty for your system. r~ -- 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