From: Denys Vlasenko <dvlasenk@redhat.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>, Oleg Nesterov <oleg@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Alexei Starovoitov <ast@plumgrid.com>,
Will Drewry <wad@chromium.org>, Kees Cook <keescook@chromium.org>,
X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] x86: stop using PER_CPU_VAR(kernel_stack)
Date: Fri, 24 Apr 2015 17:29:42 +0200 [thread overview]
Message-ID: <553A6166.4050104@redhat.com> (raw)
In-Reply-To: <CALCETrUNFp02sbX4+AhfSqHqxAW3Rcq+QmjvRb55gfzA=2Gx4w@mail.gmail.com>
On 03/23/2015 07:27 PM, Andy Lutomirski wrote:
> On Mon, Mar 23, 2015 at 10:51 AM, Denys Vlasenko <dvlasenk@redhat.com> wrote:
>> On 03/23/2015 06:45 PM, Steven Rostedt wrote:
>>> On Mon, 23 Mar 2015 18:38:09 +0100
>>> Denys Vlasenko <dvlasenk@redhat.com> wrote:
>>>
>>>>> Can we do a:
>>>>>
>>>>> #define cpu_current_top_of_stack (cpu_tss + TSS_sp0)
>>>>
>>>> We already do something similar:
>>>>
>>>> static inline unsigned long current_top_of_stack(void)
>>>> {
>>>> #ifdef CONFIG_X86_64
>>>> return this_cpu_read_stable(cpu_tss.x86_tss.sp0);
>>>> #else
>>>> /* sp0 on x86_32 is special in and around vm86 mode. */
>>>> return this_cpu_read_stable(cpu_current_top_of_stack);
>>>> #endif
>>>> }
>>>
>>> So can we then have:
>>>
>>> #ifdef __ASSEMBLY__
>>> # define cpu_current_top_of_stack (cpu_tss + TSS_sp0)
>>> #else
>>> # define cpu_current_top_of_stack (cpu_tss.x86_tss.sp0)
>>> #endif
>>>
>>> And get rid of that if statement in the static inline?
>>
>> I prefer less macro indirection in assembly code,
>> but I won't object too strongly if this would be done.
>>
>> It's up to other x86 maintainers to agree - I'm touching
>> the code recently changed by Andy, he may see the way forward
>> somewhat differently.
>>
>
> I kind of like Steven's idea. Although.. shouldn't we go all the way and do:
>
> #ifdef __ASSEMBLY__
> #ifdef CONFIG_X86_64
> #define cpu_current_top_of_stack %gs:(cpu_tss + TSS_sp0)
> #else
> #define cpu_current_top_of_stack %gs:(current_top_of_stack)
> #endif
> #endif
Which .h file do you propose to have this in? processor.h is not suitable,
it is not __ASSEMBLY__-fied.
I'm looking at a place where to put it.
For example, one of the users of the (cpu_tss + TSS_sp0) expression,
xen-asm_64.S, has only these few includes:
#include <asm/errno.h>
#include <asm/percpu.h>
#include <asm/processor-flags.h>
#include <asm/segment.h>
#include <asm/asm-offsets.h>
#include <xen/interface/xen.h>
#include "xen-asm.h"
None seems suitable. I will probably have to include thread_info.h too,
and put the define there. Ugly ugly ugly.
I'll resend a patchset where a new patch #3 attempts to do this
"unification". I personally don't see it as a clear improvement.
prev parent reply other threads:[~2015-04-24 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 20:44 Denys Vlasenko
2015-03-21 20:44 ` [PATCH 2/2] x86: remove unused kernel_stack per-cpu variable Denys Vlasenko
2015-03-23 14:18 ` [PATCH 1/2] x86: stop using PER_CPU_VAR(kernel_stack) Steven Rostedt
2015-03-23 17:10 ` Denys Vlasenko
2015-03-23 17:14 ` Borislav Petkov
2015-03-23 17:28 ` Steven Rostedt
2015-03-23 17:38 ` Denys Vlasenko
2015-03-23 17:45 ` Steven Rostedt
2015-03-23 17:51 ` Denys Vlasenko
2015-03-23 18:27 ` Andy Lutomirski
2015-04-24 15:29 ` Denys Vlasenko [this message]
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=553A6166.4050104@redhat.com \
--to=dvlasenk@redhat.com \
--cc=ast@plumgrid.com \
--cc=bp@alien8.de \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=wad@chromium.org \
--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
Powered by JetHome