Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755235AbbGVEpk (ORCPT ); Wed, 22 Jul 2015 00:45:40 -0400 Received: from mail.skyhub.de ([78.46.96.112]:32960 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751836AbbGVEpi (ORCPT ); Wed, 22 Jul 2015 00:45:38 -0400 Date: Wed, 22 Jul 2015 06:45:31 +0200 From: Borislav Petkov To: Andy Lutomirski Cc: Michal Marek , Thomas Gleixner , Ingo Molnar , Josh Poimboeuf , "linux-kernel@vger.kernel.org" , Andi Kleen , Pedro Alves , live-patching@vger.kernel.org, X86 ML , "H. Peter Anvin" , Linus Torvalds , Peter Zijlstra Subject: Re: [RFC PATCH 04/21] x86/hweight: Add stack frame dependency for __arch_hweight*() Message-ID: <20150722044531.GC6345@nazgul.tnic> References: <20150717171726.GA21568@nazgul.tnic> <20150717173220.GA12761@treble.redhat.com> <20150718050536.GA23478@nazgul.tnic> <20150718134415.GA24587@treble.redhat.com> <20150718145629.GB30713@nazgul.tnic> <20150718155714.GB19968@treble.redhat.com> <20150719041235.GA3683@nazgul.tnic> <20150722042548.GB6345@nazgul.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 745 Lines: 22 On Tue, Jul 21, 2015 at 09:39:23PM -0700, Andy Lutomirski wrote: > So your shiny perf profile shows cumulative time in whatever called > them. Sure, this is arguably silly if we're stuck with frame > pointers. You can count 20ish cycles tops for any one of them. At least that was from the last time when comparing POPCNT perf to the __sw_hweight* ones. IOW, POPCNT didn't show any improvement vs those sw versions. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. -- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/