From: Dave Hansen <dave.hansen@intel.com>
To: Hillf Danton <hdanton@sina.com>,
tip-bot2 for Peter Zijlstra <tip-bot2@linutronix.de>
Cc: Seth Jenkins <sethjenkins@google.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Kees Cook <keescook@chromium.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [tip: x86/mm] x86/mm: Randomize per-cpu entry area
Date: Fri, 21 Oct 2022 17:56:02 -0700 [thread overview]
Message-ID: <dbc0ad82-28dc-a7c5-8973-4ddae671a2ae@intel.com> (raw)
In-Reply-To: <20221022000010.1802-1-hdanton@sina.com>
On 10/21/22 17:00, Hillf Danton wrote:
>> -#define CPU_ENTRY_AREA_MAP_SIZE (CPU_ENTRY_AREA_PER_CPU + CPU_ENTRY_AREA_ARRAY_SIZE - CPU_ENTRY_AREA_BASE)
>> +#ifdef CONFIG_X86_32
>> +#define CPU_ENTRY_AREA_MAP_SIZE (CPU_ENTRY_AREA_PER_CPU + \
>> + (CPU_ENTRY_AREA_SIZE * NR_CPUS) - \
>> + CPU_ENTRY_AREA_BASE
> My vi editor finds un-paired bracket here.
> Feel free to ignore it if nothing hurt.
Thanks for finding that! Looks like Peter and I need to dust off our
32-bit .configs!
I just fixed the issue and pushed a new commit out to tip/x86/mm.
next parent reply other threads:[~2022-10-22 0:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221022000010.1802-1-hdanton@sina.com>
2022-10-22 0:56 ` Dave Hansen [this message]
2022-10-22 14:40 ` Peter Zijlstra
2022-12-17 18:55 tip-bot2 for Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2022-10-28 17:39 tip-bot2 for Peter Zijlstra
2022-10-28 6:43 tip-bot2 for Peter Zijlstra
2022-10-22 0:56 tip-bot2 for Peter Zijlstra
2022-10-21 22:25 tip-bot2 for Peter Zijlstra
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=dbc0ad82-28dc-a7c5-8973-4ddae671a2ae@intel.com \
--to=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hdanton@sina.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sethjenkins@google.com \
--cc=tip-bot2@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®