From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH] docs: remove ia64 from kexec_and_kdump.txt Date: Fri, 6 Dec 2013 11:10:56 +0000 Message-ID: <52A1B0C0.3070403@citrix.com> References: <1386274886-13105-1-git-send-email-olaf@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1386274886-13105-1-git-send-email-olaf@aepfle.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Olaf Hering Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 05/12/13 20:21, Olaf Hering wrote: > Signed-off-by: Olaf Hering Acked-by: David Vrabel > --- a/docs/misc/kexec_and_kdump.txt > +++ b/docs/misc/kexec_and_kdump.txt > @@ -137,10 +137,9 @@ command line parameter to the Xen hypervisor. It has two forms: > e.g. crashkernel=128M@256M > > Regardless of which of the two forms of the crashkernel command line you > - use, the crash kernel region should appear in /proc/iomem on x86 or > - /proc/iomem_machine on ia64. If it doesn't then either the crashkernel > - parameter is missing, or for some reason the region couldn't be placed - > - for instance because it is too large. > + use, the crash kernel region should appear in /proc/iomem on x86. If it > + doesn't then either the crashkernel parameter is missing, or for some > + reason the region couldn't be placed - for instance because it is too large. Not related to this patch really, but this section talking about /proc/iomem is only true for classic kernels. Upstream kernels don't have this information in /proc/iomem and it must be obtained by the appropriate libxc call. David