linux-kernel - [PATCH v4 0/2] clocksource/drivers/dw_apb

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-next>] [day] [month] [year] [list]

Date:	Thu, 26 Nov 2015 00:01:51 +0800
From:	Jisheng Zhang <jszhang@...vell.com>
To:	<daniel.lezcano@...aro.org>, <tglx@...utronix.de>, <arnd@...db.de>
CC:	<linux-kernel@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>,
	Jisheng Zhang <jszhang@...vell.com>
Subject: [PATCH v4 0/2] clocksource/drivers/dw_apb_timer: improve performance a bit

These two patches try to improve the dw_apb_timer clocksource/clockevent
performance.

These patches depend on the apbt_readl return value fix patch:

http://lists.infradead.org/pipermail/linux-arm-kernel/2015-November/388250.html

since v3:
 - fix commit msg: we measured 4096 rounds of function call. So add this
   information into commit msg to avoid confusion.

since v2:
 - only use relaxed version in critical path
 - inline apbt_readl/apbt_writel
 - add some performance numbers

since v1:
 - correct the wrong sentence in commit msg about writel performance on
   CA9 with outer L2 cache. Thank Arnd for pointing out this in another
   thread.


Jisheng Zhang (2):
  clocksource/drivers/dw_apb_timer: Inline apbt_readl and apbt_writel
  clocksource/drivers/dw_apb_timer: Use {readl|writel}_relaxed in
    critical path

 drivers/clocksource/dw_apb_timer.c | 30 +++++++++++++++++++++---------
 1 file changed, 21 insertions(+), 9 deletions(-)

-- 
2.6.2

--
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/