linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: leo.yan@linaro.org (Leo Yan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: cpufeature: check translation granule size based on kernel config
Date: Thu, 18 May 2017 21:01:30 +0800	[thread overview]
Message-ID: <20170518130130.GD25294@leoy-ThinkPad-T440> (raw)
In-Reply-To: <9db90634-6bb1-23e0-5cc8-19c02eceac04@arm.com>

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

      reply	other threads:[~2017-05-18 13:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18 10:21 [PATCH] arm64: cpufeature: check translation granule size based on kernel config Leo Yan
2017-05-18 10:39 ` Suzuki K Poulose
2017-05-18 11:36   ` Leo Yan
2017-05-18 12:38     ` Will Deacon
2017-05-18 12:41       ` Mark Rutland
2017-05-18 13:02         ` Leo Yan
2017-05-18 14:24           ` Mark Rutland
2017-05-18 15:13             ` Will Deacon
2017-05-18 12:39     ` Suzuki K Poulose
2017-05-18 13:01       ` Leo Yan [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=20170518130130.GD25294@leoy-ThinkPad-T440 \
    --to=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).