Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp899247ybi; Fri, 14 Jun 2019 05:20:01 -0700 (PDT) X-Google-Smtp-Source: APXvYqxrEipgu5ESfFwL7gOjaurcxGUU6p8jNUhj7opYG7uRvIo0KJTl4panz0dh0fKMBlPxa+Yp X-Received: by 2002:a62:2a0a:: with SMTP id q10mr7549874pfq.237.1560514801545; Fri, 14 Jun 2019 05:20:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560514801; cv=none; d=google.com; s=arc-20160816; b=M/mglv5gYpAM8iX7Ux8shWI26VIN6usxLDJxLdsfasuuQgdPSSCLhVxFd41SLE5EFA XH+s5cGrhx/XFV0In7v+C2CcjPUVDpeQq+IqDSh06yzjSjr0OTEj4rhL1TUiMrmQ4AJ+ zB7v3w0YfuLrR5omlBQ/CGtGt0C44n/NiFtD4fW8qR4hsUqWHN6Kd4SQs8zB8aM0YPYq NU/daV3eRMgj5la3qzT6iGtE7RwLH5k1DkbeMj4fNKpiImOnDaKQYiijlcbRuJ0IMmOk DTUXLrQPqWYRNGYoJCeBN9epzfWeKXQ92eAvcs34G6ElKHiiLngZOGKAA9PGuRftCgVB LhWQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=1bSl+GlgS/ms9IFuKU11Zv4FRFlCGd2m3IuofVnH7QM=; b=tcSG+vPWRseyXQS6e8nlwzFROaGzSPuoufR2BEFVe6LrY2amfnyi+6raM2OdOjyP3W DOPl/HDJ7PvmDh0ZPln3M5Opm3q1RlAyzRp0YTb0jKw+f4+eWav1cO1NeVb+yhc6fOAX M1eFNO9ChvRsPmvyArFbyWAdlTG6Gm51vqRviSSmc0yZGC+lcaHzrbljUpRjGYCuZffW lk7dUaLEi4AMH94GN4O39crMN0KNbZITLMhKyliVhbboUm6XSBZdm87YOELxHCvmKplU Bp9D0h8eDfQ1xT6E9wGy6FNqBJ6VSDYcwN0s/VxJOD+ST4fFpjvxWLk6qm2Z+mR+9LzU p7HA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x204si2398656pgx.354.2019.06.14.05.19.45; Fri, 14 Jun 2019 05:20:01 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727742AbfFNMT3 (ORCPT + 99 others); Fri, 14 Jun 2019 08:19:29 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:37725 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727362AbfFNMT2 (ORCPT ); Fri, 14 Jun 2019 08:19:28 -0400 Received: from [5.158.153.52] (helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1hblAz-0002iH-Sb; Fri, 14 Jun 2019 14:19:26 +0200 Date: Fri, 14 Jun 2019 14:19:25 +0200 (CEST) From: Thomas Gleixner To: Vincenzo Frascino cc: linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org, linux-kselftest@vger.kernel.org, Catalin Marinas , Will Deacon , Arnd Bergmann , Russell King , Ralf Baechle , Paul Burton , Daniel Lezcano , Mark Salyzyn , Peter Collingbourne , Shuah Khan , Dmitry Safonov <0x7f454c46@gmail.com>, Rasmus Villemoes , Huw Davies Subject: Re: [PATCH v6 03/19] kernel: Unify update_vsyscall implementation In-Reply-To: Message-ID: References: <20190530141531.43462-1-vincenzo.frascino@arm.com> <20190530141531.43462-4-vincenzo.frascino@arm.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 14 Jun 2019, Vincenzo Frascino wrote: > On 6/14/19 12:10 PM, Thomas Gleixner wrote: > > On Thu, 30 May 2019, Vincenzo Frascino wrote: > >> + > >> + if (__arch_use_vsyscall(vdata)) { > >> + vdata[CS_HRES_COARSE].cycle_last = > >> + tk->tkr_mono.cycle_last; > >> + vdata[CS_HRES_COARSE].mask = > >> + tk->tkr_mono.mask; > >> + vdata[CS_HRES_COARSE].mult = > >> + tk->tkr_mono.mult; > > > > These line breaks make it really hard to read. Can you fold in the patch > > below please? > > > > Thanks for this. I will do it in v7. Talking about v7. I'd like to get this into 5.3. That means you'd have to rebase it on git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git hyperv-next to avoid the hyperv conflict. I'll sort this out with the hyperv folks how I can get these bits as a base for a tip branch which holds all the vdso pieces. Thanks, tglx