Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756319Ab3GKWb4 (ORCPT ); Thu, 11 Jul 2013 18:31:56 -0400 Received: from cantor2.suse.de ([195.135.220.15]:36092 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753484Ab3GKWbz (ORCPT ); Thu, 11 Jul 2013 18:31:55 -0400 Date: Fri, 12 Jul 2013 00:31:51 +0200 (CEST) From: Jiri Kosina To: "H. Peter Anvin" Cc: Masami Hiramatsu , Steven Rostedt , Jason Baron , Borislav Petkov , Joe Perches , linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2 v3] x86: introduce int3-based instruction patching In-Reply-To: <51DF1B3C.8040603@linux.intel.com> Message-ID: References: <51DF1B3C.8040603@linux.intel.com> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 994 Lines: 28 On Thu, 11 Jul 2013, H. Peter Anvin wrote: > > synchronization after replacing "all but first" instructions should not > > be necessary (on Intel hardware), as the syncing after the subsequent > > patching of the first byte provides enough safety. > > But there's not only Intel HW out there, and we'd rather be on a safe > > side. > > Has anyone talked to AMD or VIA about this at all? Did anyone else ever > make SMP-capable x86? If Boris can verify for AMD, that'd be good; we could then just remove one extra syncing of the cores as a followup (can be done any time later, both for alternative.c and ftrace in fact). With the "extra" sync, the procedure is already verified to work properly by ftace. Thanks, -- Jiri Kosina SUSE Labs -- 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/