On Mon, Aug 01, 2016 at 12:31:50PM -0700, Geoff Levand wrote:
> Hi,
>
> On Fri, 2016-07-29 at 16:58 -0600, Goel, Sameer wrote:
> > In our setup we cannot place the kernel starting at 0 address. So, it it
> > placed at the first valid aligned address after placing the reserved
> > regions in memo
Hello,
Am Donnerstag, 07 Juli 2016, 13:23:26 schrieb Thiago Jung Bauermann:
> Note: We are currently discussing whether we need a new syscall so that
> userspace can provide a custom device tree for the new kernel. Even if
> that ends up being the way forward, it would affect only patches 7 and 8,
Hi,
On Fri, 2016-07-29 at 16:58 -0600, Goel, Sameer wrote:
> In our setup we cannot place the kernel starting at 0 address. So, it it
> placed at the first valid aligned address after placing the reserved
> regions in memory.
>
> The code from the change (https://patchwork.kernel.org/patch/8325
"Wei, Jiangang" writes:
> Ping ...
> May I ask for some community attention to this series?
> I purpose is fixing the dump-capture kernel hangs in
> calibrate_delay_converge() while specifying notsc.
Did you not see my reply to patch 3/3?
The short version of my feedback is that you seem to be
>>> On 13.07.16 at 14:53, wrote:
> On 13/07/16 13:20, Petr Tesarik wrote:
>> If a crash kernel is loaded, do not crash the running domain. This is
>> needed if the kernel is loaded with crash_kexec_post_notifiers, because
>> panic notifiers are run before __crash_kexec() in that case, and this
>>
