linux/Documentation/ia64
Tiejun Chen c32a42721c kvm: Documentation: remove ia64
kvm/ia64 is gone, clean up Documentation too.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2014-11-20 11:08:55 +01:00
..
.gitignore .gitignore updates 2008-10-30 11:38:45 -07:00
aliasing-test.c doc: aliasing-test: close fd on write error 2012-09-01 09:57:10 -07:00
aliasing.txt Documentation: update broken web addresses. 2010-08-04 15:21:40 +02:00
efirtc.txt Documentation: remove duplicated words 2006-10-03 22:57:56 +02:00
err_inject.txt Fix example error_injection_tool 2013-04-02 09:39:55 -07:00
fsys.txt
IRQ-redir.txt
Makefile Documentation: use subdir-y to avoid unnecessary built-in.o files 2014-09-26 11:02:55 +02:00
mca.txt Documentation: remove duplicated words 2006-10-03 22:57:56 +02:00
paravirt_ops.txt [IA64] pvops: documentation on ia64/pv_ops 2008-05-27 15:16:47 -07:00
README
serial.txt Documentation: update broken web addresses. 2010-08-04 15:21:40 +02:00
xen.txt ia64/xen: a recipe for using xen/ia64 with pv_ops. 2008-10-17 10:11:39 -07:00

        Linux kernel release 2.4.xx for the IA-64 Platform

   These are the release notes for Linux version 2.4 for IA-64
   platform.  This document provides information specific to IA-64
   ONLY, to get additional information about the Linux kernel also
   read the original Linux README provided with the kernel.

INSTALLING the kernel:

 - IA-64 kernel installation is the same as the other platforms, see
   original README for details.


SOFTWARE REQUIREMENTS

   Compiling and running this kernel requires an IA-64 compliant GCC
   compiler.  And various software packages also compiled with an
   IA-64 compliant GCC compiler.


CONFIGURING the kernel:

   Configuration is the same, see original README for details.


COMPILING the kernel:

 - Compiling this kernel doesn't differ from other platform so read
   the original README for details BUT make sure you have an IA-64
   compliant GCC compiler.

IA-64 SPECIFICS

 - General issues:

    o Hardly any performance tuning has been done. Obvious targets
      include the library routines (IP checksum, etc.). Less
      obvious targets include making sure we don't flush the TLB
      needlessly, etc.

    o SMP locks cleanup/optimization

    o IA32 support.  Currently experimental.  It mostly works.