From patchwork Wed Sep 4 09:14:23 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Olaf Hering X-Patchwork-Id: 11129791 Return-Path: Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id B191814DE for ; Wed, 4 Sep 2019 09:18:25 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 8CF692339E for ; Wed, 4 Sep 2019 09:18:25 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=aepfle.de header.i=@aepfle.de header.b="WFBof1XJ" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8CF692339E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=aepfle.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1i5ROQ-0002A7-9r; Wed, 04 Sep 2019 09:15:58 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1i5ROO-0002A2-HE for xen-devel@lists.xenproject.org; Wed, 04 Sep 2019 09:15:57 +0000 X-Inumbo-ID: 98e91bf4-cef4-11e9-b299-bc764e2007e4 Received: from mo6-p01-ob.smtp.rzone.de (unknown [2a01:238:20a:202:5301::4]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 98e91bf4-cef4-11e9-b299-bc764e2007e4; Wed, 04 Sep 2019 09:15:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1567588554; s=strato-dkim-0002; d=aepfle.de; h=Message-Id:Date:Subject:Cc:To:From:X-RZG-CLASS-ID:X-RZG-AUTH:From: Subject:Sender; bh=devvDzd++G9AK6d3xsk9Z5UJatMqMg7tgy9kCJKCyeI=; b=WFBof1XJQVrmG+Zx1BjjXtdxRT13QaP9B9j9dB+2WDRpsiPelHtcTY4/c9iigl3sky 1TD96cwxRZ+IADkEPU5RncTeawwtvyKqRYljqqXTp+lS7CYEWdRAMblQPHz05T4V1ZH9 7BhWeF8BcxO8V1RpGUuyVEKnarHhdACIa939DB5ptBXyVfsO8dVvJoaQ4VUCHfIBVZwt LJ97k2KLEEeJUcBVjcpMPY6A6xqp3ixoMYZUB0h2KilgmU+AGcazVIvRueSD7nuUJ4sE QyRQSzSE/Sih04SGB3rUn5EqdRAQvDSmUC/f45pKjhyR4N83tPmDIv+hf5zBoiqPZhO4 zzxg== X-RZG-AUTH: ":P2EQZWCpfu+qG7CngxMFH1J+3q8wa/QXkBR9MXjAuzBW/OdlBZQ4AHSS3GhOjw==" X-RZG-CLASS-ID: mo00 Received: from sender by smtp.strato.de (RZmta 44.27.0 SBL|AUTH) with ESMTPSA id x0a054v849ESSwc (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Wed, 4 Sep 2019 11:14:28 +0200 (CEST) From: Olaf Hering To: xen-devel@lists.xenproject.org Date: Wed, 4 Sep 2019 11:14:23 +0200 Message-Id: <20190904091423.23963-1-olaf@aepfle.de> X-Mailer: git-send-email 2.16.4 MIME-Version: 1.0 Subject: [Xen-devel] [PATCH v1] Remove stale crashkernel= example from documentation X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Cc: Olaf Hering , Stefano Stabellini , Wei Liu , Konrad Rzeszutek Wilk , George Dunlap , Andrew Cooper , Ian Jackson , Tim Deegan , Julien Grall , Jan Beulich Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" A plain crashkernel=size is apparently not supported by the code anymore. In case kdump ever worked like that, the code which removed support for this notation did not update the documentation. Signed-off-by: Olaf Hering --- docs/misc/kexec_and_kdump.txt | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/docs/misc/kexec_and_kdump.txt b/docs/misc/kexec_and_kdump.txt index 0842b3d58f..fea62ffa5c 100644 --- a/docs/misc/kexec_and_kdump.txt +++ b/docs/misc/kexec_and_kdump.txt @@ -116,17 +116,7 @@ to run without disrupting the memory used by the first kernel. This area is called the crash kernel region and is reserved using the crashkernel command line parameter to the Xen hypervisor. It has two forms: - i) crashkernel=size - - This is the simplest and recommended way to reserve the crash kernel - region. Just specify how large the region should be and the hypervisor - will find a good location for it. A good size to start with is 128Mb - - e.g. - - crashkernel=128M - - ii) crashkernel=size@base + i) crashkernel=size@base In this form the base address is provided in addition to the size. Use this if auto-placement doesn't work for some reason. @@ -136,7 +126,7 @@ command line parameter to the Xen hypervisor. It has two forms: e.g. crashkernel=128M@256M - iii) crashkernel=size,below=offset + ii) crashkernel=size,below=offset This allows us to place the crash kernel within the usuable address space without having to worry about a specific phyiscal address.