Received: by 2002:ac0:a591:0:0:0:0:0 with SMTP id m17-v6csp264436imm; Wed, 4 Jul 2018 23:17:03 -0700 (PDT) X-Google-Smtp-Source: AAOMgpeMuwiFACXAo7tULCYpLT4fQyW9DhkIjQlCDlwbUo8itZwgHJm/IIbj1VSXOIjalTzg8Agl X-Received: by 2002:a63:4811:: with SMTP id v17-v6mr4258007pga.379.1530771423572; Wed, 04 Jul 2018 23:17:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530771423; cv=none; d=google.com; s=arc-20160816; b=VKXuH4xxFGN5Xh/+41NvEaX3uKNqlmME5iNYrWNxntzbMIINOO2c3OyzKYU2RSgEWs 5rkNMNWoCm7O4icSya5YuwpixpQ5BarDj9I6ba0BHTybRWR1ECMQC+mQ1A3unUMYflLb l8sSci4snBe3U2X+8WFerAbLHhEWP5rMd4NO7Xjgn5gQHN+C0x8ElTP4c1wppk3vxg6R 1im2HEaop1oRRU0nJ8yoKHKyf1wTv1/qkN2QKRF4O+DlEb9wkt4H3aCp1pVWJ/icBZs9 aZMypNdP17EYyGS47keTOkjNg6jHlIzd758qDG2Wm0DbIqDO5IXnsPLhCIR40b8fwu7V 2w7w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=okketwDZQY+cqwiJw1v6BlUaHUrAZvNASp3HgeJyrVM=; b=LyJfU/MGcUCViq2csKervQUOyCkUNPPxENEVlvPklXhY7FJnvtni/Q6n/ZS+EkxDCn FA42Xgo473MqOrzVLhdVbYkLxWisR44iP9fMacNPt9EUIb5oMzjYYTT6BiQt6w+tOkBL w/T8qAV/AX490gMV58D4OvFhHxN520ZHXUbgkt5FXlzDNHrotHMGk5bIpSj8jHLJsNJN nD6WlDs6emEJmgi2iq6eyUWMR9/hxbjjHKjKHUzaf3fnsFmgUG83WaXbT8JqfZc31Dbn LadyDYcrfnNQ9MtuMF/beBe73rR8z0xsvPw5+ofA8rDD/LFtHePXcrq98VGwP+VO5+aw kXFw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v24-v6si5132323plo.159.2018.07.04.23.16.47; Wed, 04 Jul 2018 23:17:03 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753075AbeGEGQE (ORCPT + 99 others); Thu, 5 Jul 2018 02:16:04 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:49177 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751983AbeGEGQD (ORCPT ); Thu, 5 Jul 2018 02:16:03 -0400 Received: from p4fea482e.dip0.t-ipconnect.de ([79.234.72.46] helo=nanos.glx-home) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1faxYW-0003r5-RJ; Thu, 05 Jul 2018 08:15:52 +0200 Date: Thu, 5 Jul 2018 08:15:52 +0200 (CEST) From: Thomas Gleixner To: "Yang, Bin" cc: "mingo@kernel.org" , "hpa@zytor.com" , "linux-kernel@vger.kernel.org" , "peterz@infradead.org" , "x86@kernel.org" Subject: Re: [PATCH] x86/mm: fix cpu stuck issue in __change_page_attr_set_clr In-Reply-To: <404E7043-0ADB-4A40-9A07-EBE33F26C8CB@intel.com> Message-ID: References: <1530180340-18593-1-git-send-email-bin.yang@intel.com> <0131cecd5d0456c2a109f4b8bdbfe558389671dd.camel@intel.com> <3224aae1d09788aba687fd7bd9e088f233016fc8.camel@intel.com> <34a76fad5c43c11ce8ceb491537b453d8053bdb2.camel@intel.com> <404E7043-0ADB-4A40-9A07-EBE33F26C8CB@intel.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 5 Jul 2018, Yang, Bin wrote: > Sorry for the misunderstanding. I mean I will improve the check loop in patch v2. > I just submitted patch v2. Thanks in advance for your kind review. Did you actually read what I wrote? > On Thu, 5 Jul 2018, Yang, Bin wrote: > > Please do not top post. Here again: Please do not top post. and further down: > and that can be done smart without massive looping in 4K steps, but we > really want to analyze _first_ whether the checks are just silently fixing > up sloppy callers and whether they are needed at all. I can't see any analysis of that in your V2. Thanks, tglx