Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756675Ab3GKUxg (ORCPT ); Thu, 11 Jul 2013 16:53:36 -0400 Received: from mga03.intel.com ([143.182.124.21]:33465 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756638Ab3GKUxf (ORCPT ); Thu, 11 Jul 2013 16:53:35 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.89,647,1367996400"; d="scan'208";a="363907696" Message-ID: <51DF1B3C.8040603@linux.intel.com> Date: Thu, 11 Jul 2013 13:53:16 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Jiri Kosina 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 References: In-Reply-To: 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 Content-Length: 677 Lines: 19 On 07/11/2013 01:26 PM, Jiri Kosina 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? -hpa -- 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/