Xen devel - Dec 2013 - [PATCH] docs: remove ia64 from kexec_and_kdump.txt

Signed-off-by: Olaf Hering <olaf@aepfle.de>
---
 docs/misc/kexec_and_kdump.txt | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/docs/misc/kexec_and_kdump.txt b/docs/misc/kexec_and_kdump.txt
index 9ec3fcc..2f93771 100644
--- 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.
 
    # cat /proc/iomem
    ...
@@ -179,8 +178,6 @@ On x86 systems the crash kernel may be either
 - Relocatability is controlled by the CONFIG_RELOCATABLE kernel
   compile configuration parameter. This option may not be available
   depending on the kernel version
-On ia64
-  Either a vmlinuz or vmlinux.gz image may be used
 
 
 2. Execute

On 05/12/13 20:21, Olaf Hering wrote:
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
Acked-by: David Vrabel <david.vrabel@citrix.com>
> --- 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