From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1756006AbdERNBu (ORCPT <rfc822;w@1wt.eu>);
        Thu, 18 May 2017 09:01:50 -0400
Received: from mail-pg0-f47.google.com ([74.125.83.47]:36518 "EHLO
        mail-pg0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1754650AbdERNBo (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 18 May 2017 09:01:44 -0400
Date: Thu, 18 May 2017 21:01:30 +0800
From: Leo Yan <leo.yan@linaro.org>
To: Suzuki K Poulose <Suzuki.Poulose@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
        Will Deacon <will.deacon@arm.com>, Mark Rutland <mark.rutland@arm.com>,
        Marc Zyngier <marc.zyngier@arm.com>,
        Ard Biesheuvel <ard.biesheuvel@linaro.org>,
        James Morse <james.morse@arm.com>,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        Guodong Xu <guodong.xu@linaro.org>,
        Haojian Zhuang <haojian.zhuang@linaro.org>,
        Douglas Raillard <douglas.raillard@arm.com>
Subject: Re: [PATCH] arm64: cpufeature: check translation granule size based
 on kernel config
Message-ID: <20170518130130.GD25294@leoy-ThinkPad-T440>
References: <1495102873-10858-1-git-send-email-leo.yan@linaro.org>
 <c0c8bd7b-647d-092d-65ac-08a90000e30c@arm.com>
 <20170518113627.GC25294@leoy-ThinkPad-T440>
 <9db90634-6bb1-23e0-5cc8-19c02eceac04@arm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9db90634-6bb1-23e0-5cc8-19c02eceac04@arm.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, May 18, 2017 at 01:39:12PM +0100, Suzuki K Poulose wrote:

[...]

> >>If we were to suppress the warning (more on that below), we could simply
> >>make this feature a NON_STRICT, since the unsupported CPUs won't boot
> >>with 16K to hit this sanity check.
> >>
> >>However, there is a problem with disabling this warning. If a VM starts
> >>using 16KB page size on a 4K/64K host, the VM could end up in unknown
> >>failures when it switches to an unsupported CPU (after it has booted).
> >>Of course the real fix lies in making the KVM exposing the safe value
> >>for granule support to the VCPUs (which is currently being worked on by
> >>Douglas in Cc). So, when we have that ready, we could make it NON_STRICT
> >>instead of this approach.
> >
> >Thanks for the info :)
> >
> >I will use below patch for production branch temporarily. You could
> 
> Which production branch do you mean above ? Is it something in your intenral
> repository ?

Yeah, I mean Hikey960 branch.

Thanks,
Leo Yan