From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965105AbbFCRLP (ORCPT ); Wed, 3 Jun 2015 13:11:15 -0400 Received: from mail-wi0-f180.google.com ([209.85.212.180]:35258 "EHLO mail-wi0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965091AbbFCRLG (ORCPT ); Wed, 3 Jun 2015 13:11:06 -0400 Date: Wed, 3 Jun 2015 19:11:00 +0200 From: Ingo Molnar To: "H. Peter Anvin" Cc: linux-kernel@vger.kernel.org, Andy Lutomirski , Denys Vlasenko , Brian Gerst , Peter Zijlstra , Borislav Petkov , Linus Torvalds , Oleg Nesterov , Thomas Gleixner Subject: Re: [RFC PATCH 0/7] x86/entry: Create a home for the x86 entry code in arch/x86/entry/ Message-ID: <20150603171100.GB14389@gmail.com> References: <1433350757-14247-1-git-send-email-mingo@kernel.org> <556F3368.5060708@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <556F3368.5060708@zytor.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * H. Peter Anvin wrote: > I like the patch set (and you can add my Acked-by:) *except* 7/7, and the reason > for that is that it really isn't entry code, it is user space code. Well, I think arch/x86/entry/ should be a broader category for all things entry code: and the vsyscall code is closely related to the syscall entry/exit code so it's in a better place there than just being in the generic arch/x86/kernel/ directory. I kept it separate in arch/x86/entry/vsyscall/ so it doesn't mix with other entry code. Thanks, Ingo