From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753729AbdJRL3r (ORCPT ); Wed, 18 Oct 2017 07:29:47 -0400 Received: from mx2.suse.de ([195.135.220.15]:51952 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753607AbdJRL3h (ORCPT ); Wed, 18 Oct 2017 07:29:37 -0400 Date: Wed, 18 Oct 2017 13:29:35 +0200 (CEST) From: Miroslav Benes To: Josh Poimboeuf 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 In-Reply-To: <20171018110541.53mhxtskgbyhr3fl@treble> Message-ID: References: <20171006223247.fkkrrtxydq33c7dw@treble> <3b0c1c00-e4ae-13ab-434d-73d8a5e5a60d@akamai.com> <20171018110541.53mhxtskgbyhr3fl@treble> User-Agent: Alpine 2.21 (LSU 202 2017-01-01) 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 On Wed, 18 Oct 2017, Josh Poimboeuf wrote: > 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? :-) Hopefully soon. First I wanted to eliminate the amount of unreaded/unreviewed patches. Almost there. However there is OSS next week :/. But soon... :) Miroslav