From: "Yang, Bin" <bin.yang@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "mingo@kernel.org" <mingo@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH] x86/mm: fix cpu stuck issue in __change_page_attr_set_clr
Date: Thu, 5 Jul 2018 01:08:45 +0000 [thread overview]
Message-ID: <E0B0C3E3-5AA5-4AEC-A11A-B55040A007C3@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1807041221110.1816@nanos.tec.linutronix.de>
This is what my new patch tries to improve.
On 04/07/2018, 10:02 PM, "Thomas Gleixner" <tglx@linutronix.de> wrote:
The check loop itself is stupid as well. Instead of looping in 4K steps
the thing can be rewritten to check for overlapping ranges and then check
explicitely for those. If there is no overlap in the first place the
whole loop thing can be avoided, but that's a pure optimization and needs
more thought than the straight forward and obvious solution to the
problem at hand.
next prev parent reply other threads:[~2018-07-05 1:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 10:05 [PATCH] x86/mm: fix cpu stuck issue in __change_page_attr_set_clr Bin Yang
2018-07-03 13:57 ` Thomas Gleixner
2018-07-04 6:07 ` Yang, Bin
2018-07-04 7:40 ` Thomas Gleixner
2018-07-04 9:16 ` Yang, Bin
2018-07-04 9:20 ` Thomas Gleixner
2018-07-04 10:15 ` Yang, Bin
2018-07-04 14:01 ` Thomas Gleixner
2018-07-05 1:08 ` Yang, Bin [this message]
2018-07-05 5:30 ` Thomas Gleixner
2018-07-05 5:48 ` Yang, Bin
2018-07-05 6:15 ` Thomas Gleixner
2018-07-10 2:18 ` Yang, Bin
2018-07-16 7:48 ` 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=E0B0C3E3-5AA5-4AEC-A11A-B55040A007C3@intel.com \
--to=bin.yang@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).