From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86: mmu.h: move mm_context_t::lock member inside CONFIG_MODIFY_LDT_SYSCALL
Date: Mon, 7 Oct 2019 10:56:09 +0200 [thread overview]
Message-ID: <29e830f8-65fe-c2b9-1c3f-4359bdf8ac64@rasmusvillemoes.dk> (raw)
In-Reply-To: <20190828193836.16791-1-linux@rasmusvillemoes.dk>
On 28/08/2019 21.38, Rasmus Villemoes wrote:
> The placement of the lock member in mm_context_t suggests that it is
> used to protect the vdso* members, but AFAICT, it is only ever used
> under #ifdef CONFIG_MODIFY_LDT_SYSCALL. So guarding the member by the
> same config option is a cheap way to reduce sizeof(mm_struct) by 32
> bytes (only for !CONFIG_MODIFY_LDT_SYSCALL kernels, of course).
Ping
prev parent reply other threads:[~2019-10-07 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 19:38 Rasmus Villemoes
2019-08-28 19:38 ` [PATCH 2/2] x86: mmu.h: move mm_context_t::ia32_compat member a bit down Rasmus Villemoes
2019-10-07 8:56 ` Rasmus Villemoes [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=29e830f8-65fe-c2b9-1c3f-4359bdf8ac64@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®