Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933575AbbENRqQ (ORCPT ); Thu, 14 May 2015 13:46:16 -0400 Received: from mail-wg0-f46.google.com ([74.125.82.46]:33690 "EHLO mail-wg0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752305AbbENRqN (ORCPT ); Thu, 14 May 2015 13:46:13 -0400 Date: Thu, 14 May 2015 19:46:08 +0200 From: Ingo Molnar To: Denys Vlasenko Cc: Linus Torvalds , Steven Rostedt , Borislav Petkov , "H. Peter Anvin" , Andy Lutomirski , Oleg Nesterov , Frederic Weisbecker , Alexei Starovoitov , Will Drewry , Kees Cook , the arch/x86 maintainers , Linux Kernel Mailing List Subject: Re: [PATCH] x86/asm/entry/64: Use shorter MOVs from segmers registers Message-ID: <20150514174608.GD19338@gmail.com> References: <1431622519-19718-1-git-send-email-dvlasenk@redhat.com> <5554DE56.5030202@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5554DE56.5030202@redhat.com> 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: 1505 Lines: 38 * Denys Vlasenko wrote: > On 05/14/2015 07:08 PM, Linus Torvalds wrote: > > On Thu, May 14, 2015 at 10:05 AM, Linus Torvalds > > wrote: > >> > >> I don't object to the patch, but did we actually confirm that it > >> always overwrites all of %ecx? > > > > Just to clarify: I don't object to the patch because the code > > doesn't actually end up *depending* on the high bits anyway, and > > does word-sized compares etc. And the instruction size and speed > > things I don't doubt. So it's just the commit message I wanted to > > check wrt that whole "always overwrites all of %ecx". Because > > older CPU's didn't necessarily (things like partial register > > writes are much less of an issue when you're in-order and stupid > > ;) > > This is 64-bit code, and all 64-bit CPUs zero-extend moves from > segment registers. As you said, in this particular code it wouldn't > matter anyway since subsequent code doesn't care about high bits of > %ecx... Mind updating the changelog with all that information? It wasn't obvious to me either, as most of the mnemonics 'look' 32-bit. I'd also say that a changelog is not complete, by definition, if Linus has to ask about it ;-) Thanks, Ingo -- 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/