| 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: <515AF0D9.80805@citrix.com> Date: Tue, 2 Apr 2013 15:53:13 +0100 From: David Vrabel <david.vrabel@...rix.com> To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> CC: <linux-kernel@...r.kernel.org>, <xen-devel@...ts.xensource.com>, Keir Fraser <keir.fraser@...rix.com> Subject: Re: [Xen-devel] [PATCH] xen/evtchn: Handle VIRQ_TIMER before any other hardirq in event loop. On 01/04/13 15:07, Konrad Rzeszutek Wilk wrote: > From: Keir Fraser <keir.fraser@...rix.com> > > This avoids any other hardirq handler seeing a very stale jiffies > value immediately after wakeup from a long idle period. The one > observable symptom of this was a USB keyboard, with software keyboard > repeat, which would always repeat a key immediately that it was > pressed. This is due to the key press waking the guest, the key > handler immediately runs, sees an old jiffies value, and then that > jiffies value significantly updated, before the key is unpressed. It's a bit of hack but what else can you do when there is no generic mechanism to have different event priorities. Reviewed-by: David Vrabel <david.vrabel@...rix.com> The subject should be prefixed with: "xen/events" as this isn't a patch to the evtchn driver. David -- 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