From: Nadav Amit <namit@vmware.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@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:41:15 +0000 [thread overview]
Message-ID: <6C089922-C70D-4FF3-9B80-1F21FA80B175@vmware.com> (raw)
In-Reply-To: <20181004073719.GD19272@hirez.programming.kicks-ass.net>
at 12:37 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> 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.
I’m fine with your name. But I want to know whether the solution in general
is acceptable.
next prev parent reply other threads:[~2018-10-04 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 4:59 Nadav Amit
2018-10-04 7:37 ` Peter Zijlstra
2018-10-04 9:41 ` Nadav Amit [this message]
[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=6C089922-C70D-4FF3-9B80-1F21FA80B175@vmware.com \
--to=namit@vmware.com \
--cc=dwmw@amazon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®