From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933051Ab2AEXXU (ORCPT ); Thu, 5 Jan 2012 18:23:20 -0500 Received: from terminus.zytor.com ([198.137.202.10]:49448 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932869Ab2AEXXT (ORCPT ); Thu, 5 Jan 2012 18:23:19 -0500 Message-ID: <4F0630CC.7050001@zytor.com> Date: Thu, 05 Jan 2012 15:22:52 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0 MIME-Version: 1.0 To: Andi Kleen CC: Jan Beulich , mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org Subject: Re: x86-64: memset()/memcpy() not fully standards compliant References: <4F05BBFE020000780006A983@nat28.tlf.novell.com> <20120105182846.GQ11715@one.firstfloor.org> In-Reply-To: <20120105182846.GQ11715@one.firstfloor.org> X-Enigmail-Version: 1.3.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/05/2012 10:28 AM, Andi Kleen wrote: >> >> Otherwise, is there any rationale for this sort of lurking bug? > > Most (all?) of the CPUs I cared about when writing that code had > bugs with string instructions and >4GB. > Is that still true, and do we even use string instructions still on those old CPUs? Jan's fixes don't introduce any additional delays in the non-string-instruction paths. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.