From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751919AbdJRLFo (ORCPT ); Wed, 18 Oct 2017 07:05:44 -0400 Received: from mx1.redhat.com ([209.132.183.28]:33842 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751596AbdJRLFn (ORCPT ); Wed, 18 Oct 2017 07:05:43 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 095A649034 Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=jpoimboe@redhat.com Date: Wed, 18 Oct 2017 06:05:41 -0500 From: Josh Poimboeuf To: Miroslav Benes Cc: Jason Baron , linux-kernel@vger.kernel.org, live-patching@vger.kernel.org, jeyu@kernel.org, jikos@kernel.org, pmladek@suse.com Subject: Re: [PATCH v3 2/2] livepatch: add atomic replace Message-ID: <20171018110541.53mhxtskgbyhr3fl@treble> References: <20171006223247.fkkrrtxydq33c7dw@treble> <3b0c1c00-e4ae-13ab-434d-73d8a5e5a60d@akamai.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0.1 (2016-04-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Wed, 18 Oct 2017 11:05:43 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 18, 2017 at 11:10:09AM +0200, Miroslav Benes wrote: > 3. Drop immediate. It causes problems only and its advantages on x86_64 > are theoretical. You would still need to solve the interaction with atomic > replace on other architecture with immediate preserved, but that may be > easier. Or we can be aggressive and drop immediate completely. The force > transition I proposed earlier could achieve the same. I like this idea. When can we expect v3 of the force patches? :-) -- Josh