mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
	Bin Yang <bin.yang@intel.com>,
	Dave Hansen <dave.hansen@intel.com>,
	Mark Gross <mark.gross@intel.com>
Subject: [patch 00/10] x86/mm/cpa: Improve large page preservation handling
Date: Fri, 07 Sep 2018 17:01:19 +0200	[thread overview]
Message-ID: <20180907150119.325866892@linutronix.de> (raw)

Bin reported that try_preserve_large_page() in the page attribute code
consumes an large amount of CPU time. His initial attempts of addressing
this made me look deeper into the code.

The logic in this code is not really intelligent. It requires to check a
large page in 4k steps for conflicts. That's insane as most operations do
not conflict at all.

The code also lacks sanity checks which allow to detect whether the
existing mapping is incorrect vs. the static protections.

Any form of debugging or statistics is missing as well.

The following series addresses this:

  - Clean up the code so it becomes extensible

  - Provide the ability to check a full range for conflicts

  - Add debug output and statistics to quantify the changes and to allow
    observation of the mechanism in the future.

  - Add a sanity check for existing mappings with a fixup for the 2M case
    and a warning for the 1G case. The 2M case is trivial to address, the
    1G case requires larger changes and is just warned about for now.

  - Avoid conflict checks for operations which clear the PRESENT bit

  - Utilize the range checks to detect conflicts in one operation

  - Drop the 4k wise checking which turned out to provide no extra large
    page preservation in testing. There might be corner cases where a page
    would be preserved, but that's overkill for the common cases.

Before:
 1G pages checked:                    2
 1G pages sameprot:                   0
 1G pages preserved:                  0
 2M pages checked:                  540
 2M pages sameprot:                 466
 2M pages preserved:                 47
 4K pages checked:               800770
 4K pages set-checked:             7668

After:
 1G pages checked:                    2
 1G pages sameprot:                   0
 1G pages preserved:                  0
 2M pages checked:                  538
 2M pages sameprot:                 466
 2M pages preserved:                 47
 4K pages set-checked:             7668

This gets rid of ~800000 checks whether a particular address is with a
static protection region. Each check tests against 4 different regions,
which adds up to several million instructions.

Thanks,

	tglx

---
 Kconfig       |    8 
 mm/pageattr.c |  515 +++++++++++++++++++++++++++++++++++++++++++---------------
 2 files changed, 391 insertions(+), 132 deletions(-)




             reply	other threads:[~2018-09-07 15:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07 15:01 Thomas Gleixner [this message]
2018-09-07 15:01 ` [patch 01/10] x86/mm/cpa: Split, rename and clean up try_preserve_large_page() Thomas Gleixner
2018-09-10  2:03   ` Yang, Bin
2018-09-10  7:04     ` Thomas Gleixner
2018-09-07 15:01 ` [patch 02/10] x86/mm/cpa: Rework static_protections() Thomas Gleixner
2018-09-07 16:21   ` Dave Hansen
2018-09-07 15:01 ` [patch 03/10] x86/mm/cpa: Allow range check for static protections Thomas Gleixner
2018-09-07 15:01 ` [patch 04/10] x86/mm/cpa: Add debug mechanism Thomas Gleixner
2018-09-07 15:01 ` [patch 05/10] x86/mm/cpa: Add large page preservation statistics Thomas Gleixner
2018-09-07 15:01 ` [patch 06/10] x86/mm/cpa: Avoid static protection checks on unmap Thomas Gleixner
2018-09-07 15:01 ` [patch 07/10] x86/mm/cpa: Add sanity check for existing mappings Thomas Gleixner
2018-09-07 15:01 ` [patch 08/10] x86/mm/cpa: Optimize same protection check Thomas Gleixner
2018-09-07 15:01 ` [patch 09/10] x86/mm/cpa: Do the range check early Thomas Gleixner
2018-09-07 15:01 ` [patch 10/10] x86/mm/cpa: Avoid the 4k pages check completely Thomas Gleixner

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=20180907150119.325866892@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=bin.yang@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.gross@intel.com \
    --cc=peterz@infradead.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