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;
Date:   Thu, 4 Oct 2018 09:37:19 +0200
From:   Peter Zijlstra <peterz@infradead.org>
To:     Nadav Amit <namit@vmware.com>
Cc:     Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org,
        x86@kernel.org, David Woodhouse <dwmw@amazon.co.uk>,
        Andy Lutomirski <luto@kernel.org>
Subject: Re: [RFC] x86/cpu_entry_area: move part of it back to fixmap
Message-ID: <20181004073719.GD19272@hirez.programming.kicks-ass.net>
References: <20181004045948.129142-1-namit@vmware.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20181004045948.129142-1-namit@vmware.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Oct 03, 2018 at 09:59:48PM -0700, Nadav Amit wrote:
> This patch proposes to do something different: break
> it into two. One part holds code+data that is needed for the entry
> (trampoline code, entry stack and TSS), which is mapped in the fixmap.

> The other part holds the exception_stacks, debug store and buffers, and
> is left in its current (new) position.

> The name
> "cpu_entry_area_aux" for the second area is awful (ideas are welcomed),

How about: cpu_data_area ? Since none of that is required for the entry,
that should also not be part of its name.