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: Fri, 16 Jan 2015 10:05:51 +0100 From: Alexandre Belloni <alexandre.belloni@...e-electrons.com> To: Thomas Gleixner <tglx@...utronix.de> Cc: Daniel Lezcano <daniel.lezcano@...aro.org>, Nicolas Ferre <nicolas.ferre@...el.com>, Boris Brezillon <boris.brezillon@...e-electrons.com>, Maxime Ripard <maxime.ripard@...e-electrons.com>, sylvain.rochet@...secur.com, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, Alexandre Belloni <alexandre.belloni@...e-electrons.com> Subject: [PATCH] clockevents: don't suspend/resume if unused There is no point in calling suspend/resume for unused clockevents as they are already stopped and disabled. Furthermore, it can take some time to wait for some IPs to stop counting. Signed-off-by: Alexandre Belloni <alexandre.belloni@...e-electrons.com> Reported-by: Sylvain Rochet <sylvain.rochet@...secur.com> --- kernel/time/clockevents.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/time/clockevents.c b/kernel/time/clockevents.c index 55449909f114..0eff982c1c11 100644 --- a/kernel/time/clockevents.c +++ b/kernel/time/clockevents.c @@ -525,7 +525,7 @@ void clockevents_suspend(void) struct clock_event_device *dev; list_for_each_entry_reverse(dev, &clockevent_devices, list) - if (dev->suspend) + if (dev->suspend && dev->mode != CLOCK_EVT_MODE_UNUSED) dev->suspend(dev); } @@ -537,7 +537,7 @@ void clockevents_resume(void) struct clock_event_device *dev; list_for_each_entry(dev, &clockevent_devices, list) - if (dev->resume) + if (dev->resume && dev->mode != CLOCK_EVT_MODE_UNUSED) dev->resume(dev); } -- 2.1.0 -- 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