lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 1 Apr 2013 15:17:06 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Vivek Goyal <vgoyal@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, WANG Chao <chaowang@...hat.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kexec: use Crash kernel for Crash kernel low

On Mon, Apr 1, 2013 at 3:02 PM, H. Peter Anvin <hpa@...or.com> wrote:
> On 04/01/2013 02:10 PM, Yinghai Lu wrote:
>> On Mon, Apr 1, 2013 at 1:47 PM, H. Peter Anvin <hpa@...or.com> wrote:

> It sounds that the "never DMA'd to memory" notion requires that we have
> some low memory for the iommu, no?
>
> Or am I misunderstanding what you are asking here?

No. just find where to put second kernel.

When vivek raise the problem at beginning, he suggested
1. try 896M under at first, if it fails, will allocate under 4G, and
if it still fail
    try above 4G.
2. or keep crashkernel=XM, only to low, and add crashkernel_high if someone
    really want it to be high.

and then you said, we should keep consistent to keep all above 4G.

Now Vivek says we should use crashkernel=XM,low and crashkernel=XM,high
, also crashkernel=XM is treated as low.

And his last suggestion is just as his old second suggestion.

I just check the code again, it looks it is easy to change it to support:
1. crashkernel=XM
2. crashkernel_high=XM
3. crashkernel_high=XM crashkernel_low=YM

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ