Difference between pages "Install/Scraps" and "Subarches"

From Funtoo
< Install(Difference between pages)
Jump to navigation Jump to search
 
 
Line 1: Line 1:
{{Note| This page contains scraps that were removed from the Install Guide to preserve the Install Guide's simplicity. We need to find new ways to integrate this content. Or in some cases, this is just random stuff I removed that can be thrown away.}}
{{:Install/Header}}
= Funtoo Linux Sub-Architectures =
__NOTITLE__
This page provides an overview of Funtoo Linux sub-architectures (also called ''subarches'',) designed for quick and easy reference. While this information is available in other places, such as Wikipedia, it often takes some time to study and cross-reference the various articles to get a good understanding of each type of sub-architecture, and this information generally isn't all collected neatly in one place. That is the purpose of this page. When possible, links to more detailed Wikipedia pages are provided. You are encouraged to help maintain this page as well as the Wikipedia articles referenced here.


If you have a system with UEFI, you will want to use this documentation along with the [[UEFI Install Guide]], which will augment these instructions and explain how to get your system to boot. You may need to change your PC BIOS settings to enable or disable UEFI booting. The [[UEFI Install Guide]] has more information on this, and steps on how to determine if your system supports UEFI.
== 64-bit Suport (Generic) ==


We also offer a [[ZFS Install Guide]], which augment the instructions on this page for those who want to install Funtoo Linux on ZFS.  I
=== generic_64 ===
<console>
CFLAGS: -mtune=generic -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2
</console>


New  [[F2FS Install Guide]] is in progress  which will augment the instructions on this page for those who want to install Funtoo Linux on F2FS.
The '''generic_64''' subarch is designed to support 64-bit PC-compatible CPUs, such as the [[Wikipedia:AMD_K8|AMD K8-series processors]], which were introduced in late 2003. They were notable as the first processors that supported the [[Wikipedia:X86-64|AMD64 (also called X86-64) 64-bit instruction set]] for PC-compatible systems, which was introduced as a backwards-compatible 64-bit alternative to Intel's IA-64 architecture. Intel followed suit and also began supporting this 64-bit instruction set, which they called "[[Wikipedia:X86-64#Intel_64|Intel 64]]", by releasing X86-64 64-bit compatible CPUs from mid-2004 onwards (See [[Wikipedia:X86-64#Intel_64_implementations|Intel 64 implementations]].)


AMD desktop 64-bit CPUs include the Athlon 64, Athlon 64 FX, Athlon 64 X2, Athlon X2, Turion 64, Turion 64 X2 and Sempron series processors. AMD server processors were released under the Opteron brand and have codenames SledgeHammer, Venus, Troy, Athens, Denmark, Italy, Egypt, Santa Ana and Santa Rosa. All Opterons released through late 2006 were based on the K8 microarchitecture with original X86-64 instructions.


==== Partitions ====
== 64-bit AMD Processors ==


Funtoo Linux fully supports traditional MBR partitions, as well as newer GPT/GUID partition formats. See below to determine which partitioning scheme to use:
=== amd64-k10 ===
<console>
CFLAGS: -march=amdfam10 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 3dnow 3dnowext
</console>


===== MBR Partitions =====
The '''amd64-k10''' subarch provides support for the [[Wikipedia:AMD_10h|AMD Family 10h processors]], which were released in late 2007 as a successor to the AMD K8 series processors.


* '''Recommended if your system disk is <=2TB in size'''
Desktop amd64-k10 CPUs include [[Wikipedia:AMD Phenom|AMD Phenom]], [[Wikipedia:AMD_10h#Phenom_II_Models|AMD Phenom II]] and [[Wikipedia:AMD_10h#Athlon_II_Models|AMD Athlon II]]. Server CPUs include Opterons with codenames Budapest, Barcelona, Suzuka, Shanghai, Istanbul, Lisbon, and Magny-Cours. A full listing of amd64-k10 Opteron models [[Wikipedia:List_of_AMD_Opteron_microprocessors#K10_based_Opterons|can be found here]].
* Legacy, DOS partitioning scheme
* Only 4 primary partitions per disk; after that, you must use "logical" partitions
* Does not support 2 TB+ disks for booting
* Compatible with certain problematic systems (such as the HP ProBook 4520)
* Dual-boot with Windows for BIOS systems (Windows handle GPT only on true EFI systems, whatever version it is)
* Multiple boot loader options, e.g. GRUB 2, GRUB Legacy, lilo


{{fancynote|Due to the fact that it is more widely supported on PC hardware, it is best to use MBR partitions if possible.}}
=== amd64-bulldozer ===
<console>
CFLAGS: -march=bdver1 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 sse4 3dnow 3dnowext
</console>


===== GPT Partitions =====
The '''amd64-bulldozer''' subarch supports the [[Wikipedia:Bulldozer (microarchitecture)|AMD bulldozer microarchitecture]] CPUs, which were released from late 2011 through the first quarter of 2012 as a replacement for the [[Wikipedia:AMD_10h|K10 microarchitecture]] CPUs.
Bulldozer desktop CPUs use the [[Wikipedia:Socket_AM3+|AM3+ socket]] and server CPUs use the  [[Wikipedia:Socket_G34|G34 socket]].


* '''Recommended if your disk is >2TB in size'''
Desktop bulldozer CPUs include the [[Wikipedia:List_of_AMD_FX_microprocessors#.22Zambezi.22_.2832_nm_SOI.29|Zambezi FX-series CPUs]]. Server bulldozer CPUs include Opterons with codenames Zurich (Opteron 3200-series), Valencia (Opteron 4200-series) and Interlagos (Opteron 6200 series). A complete list of Opteron models [[Wikipedia:http://en.wikipedia.org/wiki/Opteron#Opteron_.2832_nm_SOI.29-_First_Generation_Bulldozer_Microarchitecture|can be found here.]].
* Newer format for Linux systems
* Supports 2 TB+ hard drives for booting
* Supports hundreds of partitions per disk of any size
* Requires legacy BIOS boot partition (~32 MB) to be created if system does not use EFI
* Requires bootloader with support for GPT such as GRUB 2, EXTLINUX, or a patched version of GRUB Legacy


{{fancyimportant|If you have a system disk that is 2TB or greater and want to use the space beyond 2TB, you ''must'' partition using the GPT/GUID format. Otherwise, MBR is recommended as the most reliable boot method.}}
=== amd64-piledriver ===
<console>
CFLAGS: -march=bdver2 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 sse4 3dnow 3dnowext
</console>


For a generation 2 Hyper-V system, the [http://www.ubuntu.com/ Ubuntu] desktop install DVD as of version 14.04.1 works well enough. Gentoo CDs don't support EFI boot, and the System Rescue CD lacks appropriate graphics support for Hyper-V as of version 4.4.0.
The '''amd64-piledriver''' subarch supports the [[Wikipedia:Piledriver (microarchitecture)|AMD Piledriver microarchitecture]] produced by AMD from mid-2012 through 2015, which is the successor to the [[Wikipedia:Bulldozer (microarchitecture)|AMD bulldozer microarchitecture]].  
Piledriver CPUs and APUs are available that use the [[Wikipedia:FM2 Socket|FM2 socket]]. Desktop Piledriver CPUs use the [[Wikipedia:Socket_AM3+|AM3+ socket]]. Server Piledriver CPUs use a variety of sockets, including [[Wikipedia:Socket_AM3+|AM3+]], [[Wikipedia:Socket_C32|C32]] and [[Wikipedia:Socket_G34|G34]].


It is also possible to install Funtoo Linux using many other Linux-based live CDs. Generally, any modern bootable Linux live CD or live USB media will work. See [[Requirements|requirements]] for an overview of what the Live Media must provide to allow a problem-free install of Funtoo Linux.
Desktop piledriver CPU and APUs include FX-series with codename Vishera (FX-8350, FX-8370),  [[Wikipedia:List_of_AMD_accelerated_processing_unit_microprocessors#Virgo:_.22Trinity.22_.282012.2C_32_nm.29|A-series with codename Trinity]] (A6-5400K, A10-5800K) and [[Wikipedia:http://en.wikipedia.org/wiki/List_of_AMD_accelerated_processing_unit_microprocessors#.22Richland.22_.282013.2C_32_nm.29_2|A-series with codename Richland]].  


To begin a Funtoo Linux installation, download System Rescue CD from:
Server piledriver CPUs include Opterons with codenames Delhi (Opteron 3300-series, [[Wikipedia:Socket_AM3+|AM3+]]), Seoul (Opteron 4300-series, [[Wikipedia:Socket_C32|C32]])  and Abu Dhabi (Opteron 6300-series, [[Wikipedia:Socket_G34|G34]]). A full listing of Opteron models [[Wikipedia:Opteron#Opteron_.2832_nm_SOI.29_-_Piledriver_Microarchitecture|is available here]].


Or, use your preferred live media. Insert it into your disc drive, and boot from it. I
Piledriver adds several new instructions over bulldozer, so AMD bulldozer systems cannot run amd64-piledriver-optimized stages. However, this subarch is  instruction-compatible with its successor, the, so amd64-piledriver stages can run on amd64-steamroller systems, and vice versa.


===== Filesystem Resources =====
=== amd64-steamroller ===
<console>
CFLAGS: -march=bdver3 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 sse4 3dnow 3dnowext
</console>


Advanced users may be interested in the following topics:
The '''amd64-steamroller''' subarch supports the [[Wikipedia:Steamroller (microarchitecture)|AMD steamroller microarchitecture]], produced from early 2014. It is the successor to the [[Wikipedia:Piledriver (microarchitecture)|AMD Piledriver microarchitecture]].
Steamroller APUs are available that use the [[Wikipedia:FM2+ Socket|FM2+ socket]] and  [[Wikipedia:Socket_FP3|FP3 socket]] (mobile.)


* [[GUID Booting Guide]]
Desktop steamroller APUs include the [[Wikipedia:AMD_Accelerated_Processing_Unit#Steamroller_architecture_.282014.29:_Kaveri|A-Series with codename Kaveri]], such as the quad-core AMD A10-7850K APU. Steamroller APUs are also available in mobile versions. Server steamroller APUs will include the Berlin APUs, which are expected to be released some time in 2015.
* [[LVM Install Guide]]
* [[Rootfs over encrypted lvm]]
* [[Rootfs over encrypted lvm over raid-1 on GPT]]
* '''NEW!''' '''[[ZFS Install Guide]] (Also contains instructions for Rootfs over Encrypted ZFS!)'''


===== Partitioning Recommendations =====
Amd64-steamroller subarches are instruction-compatible with amd64-piledriver, but add new instructions over amd64-bulldozer.


Below are our partitioning recommendations in table form. For MBR-based partitions, use the MBR Block Device and MBR code columns with <code>fdisk</code>. For GPT-based partitions, use the GPT Block Device and GPT Code columns with <code>gdisk</code>:
=== amd64-jaguar ===
<console>
CFLAGS: -march=btver2 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 sse4 3dnow 3dnowext
</console>


{{TableStart}}
The '''amd64-jaguar''' (also called AMD Family 16h) subarch supports the  [[Wikipedia:Jaguar (microarchitecture)|AMD jaguar microarchitecture]], which is targeted at low-power devices, including notebooks, tablets and small form-factor desktops and servers. It is perhaps most well-known for being the microarchitecture used for the [[Wikipedia:Playstation 4|Playstation 4]] and [[Wikipedia:Xbox One|Xbox One]], which each use custom 8-core Jaguar APUs.
<tr class="active"><th>Partition</th>
Socketed Jaguar APUs use the [[Wikipedia:AM1 Socket|AM1 socket]], and [[Wikipedia:Socket_FT3|FT3 socket]] for mobile devices. G-series [[Wikipedia:System_on_a_chip|"system on a chip" (SoC)]] APUs are available for non-socketed devices such as tablets and embedded system boards.
<th>Size</th>
<th>MBR Block Device (<code>fdisk</code>)</th>
<th>GPT Block Device (<code>gdisk</code>)</th>
<th>Filesystem</th>
<th>MBR Code</th>
<th>GPT Code</th>
</tr><tr>
<td><code>/boot</code></td>
<td>512 MB</td>
<td><code>/dev/sda1</code></td>
<td><code>/dev/sda1</code></td>
<td>ext2</td>
<td>83</td>
<td>8300</td>
</tr><tr>
<td>swap</td>
<td>2x RAM for low-memory systems and production servers; otherwise 2GB.</td>
<td><code>/dev/sda2</code></td>
<td><code>/dev/sda3</code></td>
<td>swap (default)</td>
<td>82</td>
<td>8200</td>
</tr><tr>
<td><code>/</code> (root)</td>
<td>Rest of the disk, minimum of 10GB. Note: to compile the <code>debian-sources</code> kernel, as described later on this page, requires a minimum of 14GB free space in <code>/tmp</code>; consider a minimum of 20GB in this case.</td>
<td><code>/dev/sda3</code></td>
<td><code>/dev/sda4</code></td>
<td>XFS recommended, alternatively ext4</td>
<td>83</td>
<td>8300</td>
</tr><tr>
<td><code>/home</code> (optional) </td>
<td>User storage and media. Typically most of the disk.</td>
<td><code>/dev/sda4</code> (if created)</td>
<td><code>/dev/sda5</code> (if created)</td>
<td>XFS recommended, alternatively ext4</td>
<td>83</td>
<td>8300</td>
</tr><tr>
<td>LVM (optional)</td>
<td>If you want to create an LVM volume.</td>
<td><code>/dev/sda4</code> (PV, if created)</td>
<td><code>/dev/sda5</code> (PV, if created)</td>
<td>LVM PV</td>
<td>8E</td>
<td>8E00</td>
</tr>{{TableEnd}}


Desktop Jaguar APUs include the [[Wikipedia:List_of_AMD_accelerated_processing_unit_microprocessors#.22Kabini.22.2C_.22Temash.22_.282013.2C_28_nm.29|Kabini A-series APUs and Temash E-series APUs]], such as the Athlon 5150 and 5350 APUs, and Sempron 2650 and 3850.


{{note|These install instructions assume you are installing Funtoo Linux to an hard disk using Master Boot Record partition tables (MBR). If you are installing Funtoo Linux on a machine where another OS is installed, there is an existing Linux distribution on your system that you want to keep or any other scenario (such as differing swap size requirements), then you will need to adapt these instructions to suit your needs.}}
Amd64-jaguar subarches use the MOVBE instruction which is not available on amd64-bulldozer, amd64-piledriver or amd64-steamroller. They are thus not instruction-compatible with any of these subarches.


===== Partitioning Using fdisk (MBR) =====
== 64-bit Intel Processors ==
=== core2_64 ===
<console>
CFLAGS: -march=core2 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 ssse3
</console>


{{important|If you need to create a GPT partition table, see [[Partitioning using gdisk]] or [[Partitioning using parted]].}}
The '''core2_64''' subarch supports 64-bit-capable [[Wikipedia:Intel_Core_2|Intel Core 2 Processors]], which includes ''some'' processors of the [[Wikipedia:Intel Core (microarchitecture)|Core]] and all processors of the [[Wikipedia:Penryn_(microarchitecture)|Penryn]] microarchitecture. All "Core 2" branded processors are 64-bit-capable. These processors were introduced in July of 2006 and were phased out in July of 2011, in favor of  [[Wikipedia:Nehalem_(microarchitecture)|Nehalem-based]] processors.


<code>fdisk</code> is the tool used to create an MBR partition table. MBR is well-supported on PCs and is recommended if your system disk is 2TB or smaller.
For a full list of 64-bit capable Core 2 processors, [http://ark.intel.com/search/advanced?s=t&FamilyText=Legacy%20Intel%C2%AE%20Core%E2%84%A22%20Processor&InstructionSet=64-bit see this link].


==== Partitioning Using gdisk ====
The 64-bit capable ''Core 2''-branded CPUs include: "Conroe"/"Allendale" (dual-core for desktops), "Merom" (dual-core for laptops), "Merom-L" (single-core for laptops), "Kentsfield" (quad-core for desktops), and the updated variants named "Wolfdale" (dual-core for desktops), "Penryn" (dual-core for laptops),  and "Yorkfield" (quad-core for desktops). (Note: ''For the server and workstation "Woodcrest", "Tigerton", "Harpertown" and "Dunnington" CPUs see the [[Wikipedia:Xeon|Xeon]] brand''.)


===== Notes Before We Begin =====
=== corei7 ===
<console>
CFLAGS: -march=corei7 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 ssse3 sse4
</console>


These install instructions assume you are installing Funtoo Linux to an empty hard disk using GUID partition tables (GPT). If you are installing Funtoo Linux on a machine where another OS is installed, or there is an existing Linux distribution on your system that you want to keep, then you will need to adapt these instructions to suit your needs.
Beginning in November 2008, Intel launched the first Core i7 processor, codenamed [[Wikipedia:Bloomfield_(microprocessor)|Bloomfield]], based on the [[Wikipedia:Nehalem_(microarchitecture)|Nehalem]] microarchitecture. With this launch, they also added to and modified the conventions of the [[Wikipedia:Intel_Core|Intel Core]] branding scheme. '''(Not to be confused with the [[Wikipedia:Intel Core (microarchitecture)|Intel Core microarchitecture]], which has only been supported by the processors sold under the Core2 brand. See [[Subarches#core2_64|core2_64]].)'''. This new naming scheme distinguishes between grades of processors rather than microarchitectures or design. Therefore, the '''corei7''' subarch supports the [[Wikipedia:Nehalem_(microarchitecture)|Nehalem]], [[Wikipedia:Westmere_(microarchitecture)|Westmere]], [[Wikipedia:Sandy_Bridge_(microarchitecture)|Sandy Bridge]],  [[Wikipedia:Ivy_Bridge_(microarchitecture)|Ivy Bridge]], and [[Wikipedia:Haswell_(microarchitecture)|Haswell]] microarchitectures under the follow brand names:


If you are going to create a legacy MBR partition table instead of GUID/GPT, you will use the <tt>fdisk</tt> command instead of <tt>gdisk</tt>, and you will not need to create the GRUB boot loader partition. See the table under [[#Partitioning Recommendations|Partitioning Recommendations]], in particular the
* Intel Core i3 (entry-level consumer)
'''MBR Block Device (<tt>fdisk</tt>)''' and '''MBR Code''' columns. <tt>fdisk</tt> works just like <tt>gdisk</tt>, but creates legacy MBR partition tables instead of the newer GPT/GUID partition tables.
* Intel Core i5 (mainstream consumer)
* Intel Corei7 (high-end consumer/business)
* Intel Xeon (business server/workstation)


Advanced users may be interested in the following topics:
=== atom_64 ===
<console>
CFLAGS: -O2 -fomit-frame-pointer -march=atom -pipe -mno-movbe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3
</console>


* [[GUID Booting Guide]]
The Intel Atom Processor is the common name for Intel's  [[Wikipedia:Bonnell_(microarchitecture)|Bonnell microarchitecture]],  which represents a partial revival of the principles used in earlier Intel designs such as P5 and the i486, with the sole purpose of enhancing the performance per watt ratio.  Successor to the [[Wikipedia:Stealey_(microprocessor)|Intel A100 series (Stealey)]], which was derived from the [[Wikipedia:Pentium_M|Pentium M]], the Intel Atom has been produced since 2008. Targeted at low-power devices, Atom processors can be found in a wide range of notebooks, tablets and small form-factor desktops and servers.
* [[Rootfs over encrypted lvm]]
* [[Rootfs over encrypted lvm over raid-1 on GPT]]
* '''NEW!''' '''[[ZFS Install Guide]] (Also contains instructions for Rootfs over Encrypted ZFS!)'''


===== Using gdisk =====
The '''atom_64''' sub-architecture supports 64-bit capable Intel Atom CPUs.  The first 64-bit capable Intel Atom CPUs were the Intel Atom 230 and 330, released in late 2008. However, Intel also continued to produce new 32-bit Atom Processors after this date. For example, the Atom N2xx series Atom Diamondville models cannot support 64-bit operation, while the 2xx and 3xx Diamondville, Pineview, Cedarview and Centerton can. A full list of 64-bit capable Intel Atom Processors [http://ark.intel.com/search/advanced?s=t&FamilyText=Intel%C2%AE%20Atom%E2%84%A2%20Processor&InstructionSet=64-bit can be seen here.]


The first step after booting SystemRescueCd is to use <tt>gdisk</tt> to create GPT (also known as GUID) partitions, specifying the disk you want to use, which is typically <tt>/dev/sda</tt>, the first disk in the system:
{{Important|For 64-bit support to be functional, a 64-bit capable Atom Processor must be paired ''with a processor, chipset, and BIOS'' that all support [[Wikipedia:X86-64#Intel_64|Intel 64]]. If not all hardware supports 64-bit, then you must use the '''atom_32''' subarch instead.}}


<console># ##i##gdisk /dev/sda</console>
{{:Install/Footer}}
You should find <tt>gdisk</tt> very similar to <tt>fdisk</tt>. Here is the partition table we want to end up with:
 
<console>Command (? for help): ##i##p
Disk /dev/sda: 234441648 sectors, 111.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): A4E5208A-CED3-4263-BB25-7147DC426931
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 234441614
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
 
Number  Start (sector)    End (sector)  Size      Code  Name
  1            2048          206847  500.0 MiB  8300  Linux filesystem
  2          206848          272383  32.0 MiB    EF02  BIOS boot partition
  3          272384        8660991  4.0 GiB    8200  Linux swap
  4        8660992      234441614  107.7 GiB  8300  Linux filesystem
 
Command (? for help): </console>
 
Above, you'll see that we have a 500 MiB boot partition, a 32 MiB "BIOS boot partition" (also known as the GRUB boot loader partition), 4 GiB of swap, and the remaining disk used by a 107.7 GiB root partition.
 
 
{{fancynote|An alternate boot loader called extlinux can be used instead of GRUB if you desire. See the [[Extlinux|extlinux Guide]] for information on how to do this.}}

Revision as of 19:33, November 19, 2014

Funtoo Linux Sub-Architectures

This page provides an overview of Funtoo Linux sub-architectures (also called subarches,) designed for quick and easy reference. While this information is available in other places, such as Wikipedia, it often takes some time to study and cross-reference the various articles to get a good understanding of each type of sub-architecture, and this information generally isn't all collected neatly in one place. That is the purpose of this page. When possible, links to more detailed Wikipedia pages are provided. You are encouraged to help maintain this page as well as the Wikipedia articles referenced here.

64-bit Suport (Generic)

generic_64

CFLAGS: -mtune=generic -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2

The generic_64 subarch is designed to support 64-bit PC-compatible CPUs, such as the AMD K8-series processors, which were introduced in late 2003. They were notable as the first processors that supported the AMD64 (also called X86-64) 64-bit instruction set for PC-compatible systems, which was introduced as a backwards-compatible 64-bit alternative to Intel's IA-64 architecture. Intel followed suit and also began supporting this 64-bit instruction set, which they called "Intel 64", by releasing X86-64 64-bit compatible CPUs from mid-2004 onwards (See Intel 64 implementations.)

AMD desktop 64-bit CPUs include the Athlon 64, Athlon 64 FX, Athlon 64 X2, Athlon X2, Turion 64, Turion 64 X2 and Sempron series processors. AMD server processors were released under the Opteron brand and have codenames SledgeHammer, Venus, Troy, Athens, Denmark, Italy, Egypt, Santa Ana and Santa Rosa. All Opterons released through late 2006 were based on the K8 microarchitecture with original X86-64 instructions.

64-bit AMD Processors

amd64-k10

CFLAGS: -march=amdfam10 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 3dnow 3dnowext

The amd64-k10 subarch provides support for the AMD Family 10h processors, which were released in late 2007 as a successor to the AMD K8 series processors.

Desktop amd64-k10 CPUs include AMD Phenom, AMD Phenom II and AMD Athlon II. Server CPUs include Opterons with codenames Budapest, Barcelona, Suzuka, Shanghai, Istanbul, Lisbon, and Magny-Cours. A full listing of amd64-k10 Opteron models can be found here.

amd64-bulldozer

CFLAGS: -march=bdver1 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 sse4 3dnow 3dnowext

The amd64-bulldozer subarch supports the AMD bulldozer microarchitecture CPUs, which were released from late 2011 through the first quarter of 2012 as a replacement for the K10 microarchitecture CPUs. Bulldozer desktop CPUs use the AM3+ socket and server CPUs use the G34 socket.

Desktop bulldozer CPUs include the Zambezi FX-series CPUs. Server bulldozer CPUs include Opterons with codenames Zurich (Opteron 3200-series), Valencia (Opteron 4200-series) and Interlagos (Opteron 6200 series). A complete list of Opteron models can be found here..

amd64-piledriver

CFLAGS: -march=bdver2 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 sse4 3dnow 3dnowext

The amd64-piledriver subarch supports the AMD Piledriver microarchitecture produced by AMD from mid-2012 through 2015, which is the successor to the AMD bulldozer microarchitecture. Piledriver CPUs and APUs are available that use the FM2 socket. Desktop Piledriver CPUs use the AM3+ socket. Server Piledriver CPUs use a variety of sockets, including AM3+, C32 and G34.

Desktop piledriver CPU and APUs include FX-series with codename Vishera (FX-8350, FX-8370), A-series with codename Trinity (A6-5400K, A10-5800K) and A-series with codename Richland.

Server piledriver CPUs include Opterons with codenames Delhi (Opteron 3300-series, AM3+), Seoul (Opteron 4300-series, C32) and Abu Dhabi (Opteron 6300-series, G34). A full listing of Opteron models is available here.

Piledriver adds several new instructions over bulldozer, so AMD bulldozer systems cannot run amd64-piledriver-optimized stages. However, this subarch is instruction-compatible with its successor, the, so amd64-piledriver stages can run on amd64-steamroller systems, and vice versa.

amd64-steamroller

CFLAGS: -march=bdver3 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 sse4 3dnow 3dnowext

The amd64-steamroller subarch supports the AMD steamroller microarchitecture, produced from early 2014. It is the successor to the AMD Piledriver microarchitecture. Steamroller APUs are available that use the FM2+ socket and FP3 socket (mobile.)

Desktop steamroller APUs include the A-Series with codename Kaveri, such as the quad-core AMD A10-7850K APU. Steamroller APUs are also available in mobile versions. Server steamroller APUs will include the Berlin APUs, which are expected to be released some time in 2015.

Amd64-steamroller subarches are instruction-compatible with amd64-piledriver, but add new instructions over amd64-bulldozer.

amd64-jaguar

CFLAGS: -march=btver2 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 sse4 3dnow 3dnowext

The amd64-jaguar (also called AMD Family 16h) subarch supports the AMD jaguar microarchitecture, which is targeted at low-power devices, including notebooks, tablets and small form-factor desktops and servers. It is perhaps most well-known for being the microarchitecture used for the Playstation 4 and Xbox One, which each use custom 8-core Jaguar APUs. Socketed Jaguar APUs use the AM1 socket, and FT3 socket for mobile devices. G-series "system on a chip" (SoC) APUs are available for non-socketed devices such as tablets and embedded system boards.

Desktop Jaguar APUs include the Kabini A-series APUs and Temash E-series APUs, such as the Athlon 5150 and 5350 APUs, and Sempron 2650 and 3850.

Amd64-jaguar subarches use the MOVBE instruction which is not available on amd64-bulldozer, amd64-piledriver or amd64-steamroller. They are thus not instruction-compatible with any of these subarches.

64-bit Intel Processors

core2_64

CFLAGS: -march=core2 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 ssse3

The core2_64 subarch supports 64-bit-capable Intel Core 2 Processors, which includes some processors of the Core and all processors of the Penryn microarchitecture. All "Core 2" branded processors are 64-bit-capable. These processors were introduced in July of 2006 and were phased out in July of 2011, in favor of Nehalem-based processors.

For a full list of 64-bit capable Core 2 processors, see this link.

The 64-bit capable Core 2-branded CPUs include: "Conroe"/"Allendale" (dual-core for desktops), "Merom" (dual-core for laptops), "Merom-L" (single-core for laptops), "Kentsfield" (quad-core for desktops), and the updated variants named "Wolfdale" (dual-core for desktops), "Penryn" (dual-core for laptops), and "Yorkfield" (quad-core for desktops). (Note: For the server and workstation "Woodcrest", "Tigerton", "Harpertown" and "Dunnington" CPUs see the Xeon brand.)

corei7

CFLAGS: -march=corei7 -O2 -pipe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3 ssse3 sse4

Beginning in November 2008, Intel launched the first Core i7 processor, codenamed Bloomfield, based on the Nehalem microarchitecture. With this launch, they also added to and modified the conventions of the Intel Core branding scheme. (Not to be confused with the Intel Core microarchitecture, which has only been supported by the processors sold under the Core2 brand. See core2_64.). This new naming scheme distinguishes between grades of processors rather than microarchitectures or design. Therefore, the corei7 subarch supports the Nehalem, Westmere, Sandy Bridge, Ivy Bridge, and Haswell microarchitectures under the follow brand names:

  • Intel Core i3 (entry-level consumer)
  • Intel Core i5 (mainstream consumer)
  • Intel Corei7 (high-end consumer/business)
  • Intel Xeon (business server/workstation)

atom_64

CFLAGS: -O2 -fomit-frame-pointer -march=atom -pipe -mno-movbe
CHOST: x86_64-pc-linux-gnu
USE: mmx sse sse2 sse3

The Intel Atom Processor is the common name for Intel's Bonnell microarchitecture, which represents a partial revival of the principles used in earlier Intel designs such as P5 and the i486, with the sole purpose of enhancing the performance per watt ratio. Successor to the Intel A100 series (Stealey), which was derived from the Pentium M, the Intel Atom has been produced since 2008. Targeted at low-power devices, Atom processors can be found in a wide range of notebooks, tablets and small form-factor desktops and servers.

The atom_64 sub-architecture supports 64-bit capable Intel Atom CPUs. The first 64-bit capable Intel Atom CPUs were the Intel Atom 230 and 330, released in late 2008. However, Intel also continued to produce new 32-bit Atom Processors after this date. For example, the Atom N2xx series Atom Diamondville models cannot support 64-bit operation, while the 2xx and 3xx Diamondville, Pineview, Cedarview and Centerton can. A full list of 64-bit capable Intel Atom Processors can be seen here.

   Important

For 64-bit support to be functional, a 64-bit capable Atom Processor must be paired with a processor, chipset, and BIOS that all support Intel 64. If not all hardware supports 64-bit, then you must use the atom_32 subarch instead.