All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Pratyush Anand <panand@redhat.com>
Cc: Geoff Levand <geoff@infradead.org>,
	james.morse@arm.com, Dave Young <dyoung@redhat.com>,
	kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] arm64: Pass RAM boundary and enable-dcache flag to purgatory
Date: Wed, 23 Nov 2016 09:08:19 +0100	[thread overview]
Message-ID: <20161123080816.GA30255@verge.net.au> (raw)
In-Reply-To: <81975e6e-b97a-0401-0e18-b2d26722c1dd@redhat.com>

On Wed, Nov 23, 2016 at 07:41:52AM +0530, Pratyush Anand wrote:
> 
> 
> On Wednesday 23 November 2016 07:33 AM, Dave Young wrote:
> >>Although this is very unlikely that a hardware will support only 16K page
> >>> sizes, however it is possible. Therefore, its better to keep it disabled by
> >>> default.
> >If it is *unlikely* it could be better to make it as default and add a
> >--disable-dcache instead.
> >
> 
> I think, I can do that.

Can this be detected at run-time?

It sounds like it will be painful if on some setups the default
doesn't work.

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: Pass RAM boundary and enable-dcache flag to purgatory
Date: Wed, 23 Nov 2016 09:08:19 +0100	[thread overview]
Message-ID: <20161123080816.GA30255@verge.net.au> (raw)
In-Reply-To: <81975e6e-b97a-0401-0e18-b2d26722c1dd@redhat.com>

On Wed, Nov 23, 2016 at 07:41:52AM +0530, Pratyush Anand wrote:
> 
> 
> On Wednesday 23 November 2016 07:33 AM, Dave Young wrote:
> >>Although this is very unlikely that a hardware will support only 16K page
> >>> sizes, however it is possible. Therefore, its better to keep it disabled by
> >>> default.
> >If it is *unlikely* it could be better to make it as default and add a
> >--disable-dcache instead.
> >
> 
> I think, I can do that.

Can this be detected at run-time?

It sounds like it will be painful if on some setups the default
doesn't work.

  reply	other threads:[~2016-11-23  8:08 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22  4:32 [PATCH 0/2] kexec-tools: arm64: Add dcache enabling facility Pratyush Anand
2016-11-22  4:32 ` Pratyush Anand
2016-11-22  4:32 ` [PATCH 1/2] arm64: Add enable/disable d-cache support for purgatory Pratyush Anand
2016-11-22  4:32   ` Pratyush Anand
2016-11-25 18:30   ` James Morse
2016-11-25 18:30     ` James Morse
2016-12-14  9:38     ` Pratyush Anand
2016-12-14  9:38       ` Pratyush Anand
2016-12-14 10:12       ` Pratyush Anand
2016-12-14 10:12         ` Pratyush Anand
2016-12-14 11:16         ` James Morse
2016-12-14 11:16           ` James Morse
2016-12-14 11:37           ` Mark Rutland
2016-12-14 11:37             ` Mark Rutland
2016-12-14 12:11             ` James Morse
2016-12-14 12:11               ` James Morse
2016-12-14 12:21             ` Pratyush Anand
2016-12-14 12:21               ` Pratyush Anand
2016-12-14 13:44               ` Mark Rutland
2016-12-14 13:44                 ` Mark Rutland
2016-12-14 14:13                 ` Pratyush Anand
2016-12-14 14:13                   ` Pratyush Anand
2016-12-14 12:13           ` Pratyush Anand
2016-12-14 12:13             ` Pratyush Anand
2016-12-14 11:16       ` James Morse
2016-12-14 11:16         ` James Morse
2016-12-14 11:28         ` Mark Rutland
2016-12-14 11:28           ` Mark Rutland
2016-11-22  4:32 ` [PATCH 2/2] arm64: Pass RAM boundary and enable-dcache flag to purgatory Pratyush Anand
2016-11-22  4:32   ` Pratyush Anand
2016-11-22 18:57   ` Geoff Levand
2016-11-22 18:57     ` Geoff Levand
2016-11-23  1:46     ` Pratyush Anand
2016-11-23  1:46       ` Pratyush Anand
2016-11-23  2:03       ` Dave Young
2016-11-23  2:03         ` Dave Young
2016-11-23  2:11         ` Pratyush Anand
2016-11-23  2:11           ` Pratyush Anand
2016-11-23  8:08           ` Simon Horman [this message]
2016-11-23  8:08             ` Simon Horman
2016-11-23  8:17             ` Pratyush Anand
2016-11-23  8:17               ` Pratyush Anand
2016-11-22 18:56 ` [PATCH 0/2] kexec-tools: arm64: Add dcache enabling facility Geoff Levand
2016-11-22 18:56   ` Geoff Levand
2016-11-23  1:39   ` Pratyush Anand
2016-11-23  1:39     ` Pratyush Anand
2016-11-25 18:30   ` James Morse
2016-11-25 18:30     ` James Morse

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=20161123080816.GA30255@verge.net.au \
    --to=horms@verge.net.au \
    --cc=dyoung@redhat.com \
    --cc=geoff@infradead.org \
    --cc=james.morse@arm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=panand@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.