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
Date: Thu, 4 Oct 2018 09:37:19 +0200 [thread overview]
Message-ID: <20181004073719.GD19272@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20181004045948.129142-1-namit@vmware.com>
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.
next prev parent reply other threads:[~2018-10-04 7:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 4:59 [RFC] x86/cpu_entry_area: move part of it back to fixmap Nadav Amit
2018-10-04 7:37 ` Peter Zijlstra [this message]
2018-10-04 9:41 ` Nadav Amit
[not found] ` <72B0B378-9515-47C4-8937-9F1E823DD236@amacapital.net>
2018-10-04 16:30 ` Nadav Amit
2018-10-04 17:02 ` Andy Lutomirski
2018-10-05 18:35 ` Nadav Amit
2018-10-05 22:10 ` Andy Lutomirski
2018-10-05 22:17 ` Nadav Amit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181004073719.GD19272@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dwmw@amazon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=namit@vmware.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox