2010-05-14 09:29:15 +02:00
|
|
|
/*
|
|
|
|
* QEMU PC System Emulator
|
|
|
|
*
|
|
|
|
* Copyright (c) 2003-2004 Fabrice Bellard
|
|
|
|
*
|
|
|
|
* Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
|
|
* of this software and associated documentation files (the "Software"), to deal
|
|
|
|
* in the Software without restriction, including without limitation the rights
|
|
|
|
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
|
|
* copies of the Software, and to permit persons to whom the Software is
|
|
|
|
* furnished to do so, subject to the following conditions:
|
|
|
|
*
|
|
|
|
* The above copyright notice and this permission notice shall be included in
|
|
|
|
* all copies or substantial portions of the Software.
|
|
|
|
*
|
|
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
|
|
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
|
|
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
|
|
|
|
* THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
|
|
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
|
|
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
|
|
|
* THE SOFTWARE.
|
|
|
|
*/
|
|
|
|
|
2011-08-15 16:17:38 +02:00
|
|
|
#include <glib.h>
|
|
|
|
|
2013-02-04 15:40:22 +01:00
|
|
|
#include "hw/hw.h"
|
2013-08-19 16:26:55 +02:00
|
|
|
#include "hw/loader.h"
|
2013-02-05 17:06:20 +01:00
|
|
|
#include "hw/i386/pc.h"
|
|
|
|
#include "hw/i386/apic.h"
|
2015-08-12 04:08:20 +02:00
|
|
|
#include "hw/smbios/smbios.h"
|
2013-02-04 15:40:22 +01:00
|
|
|
#include "hw/pci/pci.h"
|
|
|
|
#include "hw/pci/pci_ids.h"
|
|
|
|
#include "hw/usb.h"
|
2012-10-24 08:43:34 +02:00
|
|
|
#include "net/net.h"
|
2013-02-04 15:40:22 +01:00
|
|
|
#include "hw/boards.h"
|
|
|
|
#include "hw/ide.h"
|
2012-12-17 18:20:04 +01:00
|
|
|
#include "sysemu/kvm.h"
|
2013-02-04 15:40:22 +01:00
|
|
|
#include "hw/kvm/clock.h"
|
2012-12-17 18:20:04 +01:00
|
|
|
#include "sysemu/sysemu.h"
|
2013-02-04 15:40:22 +01:00
|
|
|
#include "hw/sysbus.h"
|
2012-12-17 18:20:04 +01:00
|
|
|
#include "sysemu/arch_init.h"
|
2014-10-07 13:59:18 +02:00
|
|
|
#include "sysemu/block-backend.h"
|
2013-02-05 17:06:20 +01:00
|
|
|
#include "hw/i2c/smbus.h"
|
|
|
|
#include "hw/xen/xen.h"
|
2012-12-17 18:19:49 +01:00
|
|
|
#include "exec/memory.h"
|
|
|
|
#include "exec/address-spaces.h"
|
2013-04-15 08:19:22 +02:00
|
|
|
#include "hw/acpi/acpi.h"
|
2012-10-18 00:15:48 +02:00
|
|
|
#include "cpu.h"
|
2014-06-20 03:40:25 +02:00
|
|
|
#include "qemu/error-report.h"
|
2010-06-30 13:58:34 +02:00
|
|
|
#ifdef CONFIG_XEN
|
2015-07-15 07:37:49 +02:00
|
|
|
#include <xen/hvm/hvm_info_table.h>
|
|
|
|
#include "hw/xen/xen_pt.h"
|
2010-06-30 13:58:34 +02:00
|
|
|
#endif
|
2015-05-19 13:29:51 +02:00
|
|
|
#include "migration/migration.h"
|
2010-05-14 09:29:15 +02:00
|
|
|
|
|
|
|
#define MAX_IDE_BUS 2
|
|
|
|
|
|
|
|
static const int ide_iobase[MAX_IDE_BUS] = { 0x1f0, 0x170 };
|
|
|
|
static const int ide_iobase2[MAX_IDE_BUS] = { 0x3f6, 0x376 };
|
|
|
|
static const int ide_irq[MAX_IDE_BUS] = { 14, 15 };
|
|
|
|
|
2015-05-15 19:18:59 +02:00
|
|
|
static bool pci_enabled = true;
|
i386: ACPI table generation code from seabios
This adds C code for generating ACPI tables at runtime,
imported from seabios git tree
commit 51684b7ced75fb76776e8ee84833fcfb6ecf12dd
Although ACPI tables come from a system BIOS on real hw,
it makes sense that the ACPI tables are coupled with the
virtual machine, since they have to abstract the x86 machine to
the OS's.
This is widely desired as a way to avoid the churn
and proliferation of QEMU-specific interfaces
associated with ACPI tables in bios code.
Notes:
As BIOS can reprogram devices prior to loading
ACPI tables, we pre-format ACPI tables but defer loading
hardware configuration there until tables are loaded.
The code structure was intentionally kept as close
to the seabios original as possible, to simplify
comparison and making sure we didn't lose anything
in translation.
Minor code duplication results, to help ensure there are no functional
regressions, I think it's better to merge it like this and do more code
changes in follow-up patches.
Cross-version compatibility concerns have been addressed:
ACPI tables are exposed to guest as FW_CFG entries.
When running with -M 1.5 and older, this patch disables ACPI
table generation, and doesn't expose ACPI
tables to guest.
As table content is likely to change over time,
the following measures are taken to simplify
cross-version migration:
- All tables besides the RSDP are packed in a single FW CFG entry.
This entry size is currently 23K. We round it up to 64K
to avoid too much churn there.
- Tables are placed in special ROM blob (not mapped into guest memory)
which is automatically migrated together with the guest, same
as BIOS code.
- Offsets where hardware configuration is loaded in ACPI tables
are also migrated, this is in case future ACPI changes make us
rearrange the tables in memory.
This patch reuses some code from SeaBIOS, which was originally under
LGPLv2 and then relicensed to GPLv3 or LGPLv3, in QEMU under GPLv2+. This
relicensing has been acked by all contributors that had contributed to the
code since the v2->v3 relicense. ACKs approving the v2+ relicensing are
listed below. The list might include ACKs from people not holding
copyright on any parts of the reused code, but it's better to err on the
side of caution and include them.
Affected SeaBIOS files (GPLv2+ license headers added)
<http://thread.gmane.org/gmane.comp.bios.coreboot.seabios/5949>:
src/acpi-dsdt-cpu-hotplug.dsl
src/acpi-dsdt-dbug.dsl
src/acpi-dsdt-hpet.dsl
src/acpi-dsdt-isa.dsl
src/acpi-dsdt-pci-crs.dsl
src/acpi.c
src/acpi.h
src/ssdt-misc.dsl
src/ssdt-pcihp.dsl
src/ssdt-proc.dsl
tools/acpi_extract.py
tools/acpi_extract_preprocess.py
Each one of the listed people agreed to the following:
> If you allow the use of your contribution in QEMU under the
> terms of GPLv2 or later as proposed by this patch,
> please respond to this mail including the line:
>
> Acked-by: Name <email address>
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
Acked-by: Jan Kiszka <jan.kiszka@siemens.com>
Acked-by: Jason Baron <jbaron@akamai.com>
Acked-by: David Woodhouse <David.Woodhouse@intel.com>
Acked-by: Gleb Natapov <gleb@redhat.com>
Acked-by: Marcelo Tosatti <mtosatti@redhat.com>
Acked-by: Dave Frodin <dave.frodin@se-eng.com>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Acked-by: Kevin O'Connor <kevin@koconnor.net>
Acked-by: Laszlo Ersek <lersek@redhat.com>
Acked-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Acked-by: Isaku Yamahata <yamahata@valinux.co.jp>
Acked-by: Magnus Christensson <magnus.christensson@intel.com>
Acked-by: Hu Tao <hutao@cn.fujitsu.com>
Acked-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
Tested-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Tested-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2013-07-24 17:56:14 +02:00
|
|
|
static bool has_acpi_build = true;
|
2015-02-17 10:04:40 +01:00
|
|
|
static bool rsdp_in_ram = true;
|
pc: hack for migration compatibility from QEMU 2.0
Changing the ACPI table size causes migration to break, and the memory
hotplug work opened our eyes on how horribly we were breaking things in
2.0 already.
The ACPI table size is rounded to the next 4k, which one would think
gives some headroom. In practice this is not the case, because the user
can control the ACPI table size (each CPU adds 97 bytes to the SSDT and
8 to the MADT) and so some "-smp" values will break the 4k boundary and
fail to migrate. Similarly, PCI bridges add ~1870 bytes to the SSDT.
This patch concerns itself with fixing migration from QEMU 2.0. It
computes the payload size of QEMU 2.0 and always uses that one.
The previous patch shrunk the ACPI tables enough that the QEMU 2.0 size
should always be enough; non-AML tables can change depending on the
configuration (especially MADT, SRAT, HPET) but they remain the same
between QEMU 2.0 and 2.1, so we only compute our padding based on the
sizes of the SSDT and DSDT.
Migration from QEMU 1.7 should work for guests that have a number of CPUs
other than 12, 13, 14, 54, 55, 56, 97, 98, 139, 140. It was already
broken from QEMU 1.7 to QEMU 2.0 in the same way, though.
Even with this patch, QEMU 1.7 and 2.0 have two different ideas of
"-M pc-i440fx-2.0" when there are PCI bridges. Igor sent a patch to
adopt the QEMU 1.7 definition. I think distributions should apply
it if they move directly from QEMU 1.7 to 2.1+ without ever packaging
version 2.0.
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Tested-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2014-07-28 17:34:15 +02:00
|
|
|
static int legacy_acpi_table_size;
|
2014-04-23 15:42:38 +02:00
|
|
|
static bool smbios_defaults = true;
|
2014-04-23 15:42:42 +02:00
|
|
|
static bool smbios_legacy_mode;
|
smbios: Encode UUID according to SMBIOS specification
Differently from older versions, SMBIOS version 2.6 is explicit about
the encoding of UUID fields:
> Although RFC 4122 recommends network byte order for all fields, the PC
> industry (including the ACPI, UEFI, and Microsoft specifications) has
> consistently used little-endian byte encoding for the first three fields:
> time_low, time_mid, time_hi_and_version. The same encoding, also known as
> wire format, should also be used for the SMBIOS representation of the UUID.
>
> The UUID {00112233-4455-6677-8899-AABBCCDDEEFF} would thus be represented
> as 33 22 11 00 55 44 77 66 88 99 AA BB CC DD EE FF.
The dmidecode tool implements this and decodes the above "wire format"
when SMBIOS version >= 2.6. We moved from SMBIOS version 2.4 to 2.8 when
we started building the SMBIOS entry point inside QEMU, on commit
c97294ec1b9e36887e119589d456557d72ab37b5.
Change smbios_build_type_1_table() to encode the UUID as specified.
To make sure we won't change the guest-visible UUID when upgrading to a
newer QEMU version, keep the old behavior on pc-*-2.1 and older.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2014-10-29 14:26:08 +01:00
|
|
|
static bool smbios_uuid_encoded = true;
|
2013-12-16 12:54:19 +01:00
|
|
|
/* Make sure that guest addresses aligned at 1Gbyte boundaries get mapped to
|
|
|
|
* host addresses aligned at 1Gbyte boundaries. This way we can use 1GByte
|
|
|
|
* pages in the host.
|
|
|
|
*/
|
2013-12-16 10:11:28 +01:00
|
|
|
static bool gigabyte_align = true;
|
2014-06-02 15:25:10 +02:00
|
|
|
static bool has_reserved_memory = true;
|
2015-05-15 19:18:59 +02:00
|
|
|
static bool kvmclock_enabled = true;
|
2013-04-26 05:24:46 +02:00
|
|
|
|
2010-05-14 09:29:15 +02:00
|
|
|
/* PC hardware initialisation */
|
2015-07-15 07:37:42 +02:00
|
|
|
static void pc_init1(MachineState *machine,
|
|
|
|
const char *host_type, const char *pci_type)
|
2010-05-14 09:29:15 +02:00
|
|
|
{
|
2015-08-07 21:55:45 +02:00
|
|
|
PCMachineState *pcms = PC_MACHINE(machine);
|
2013-08-21 20:14:45 +02:00
|
|
|
MemoryRegion *system_memory = get_system_memory();
|
|
|
|
MemoryRegion *system_io = get_system_io();
|
2010-05-14 09:29:15 +02:00
|
|
|
int i;
|
|
|
|
PCIBus *pci_bus;
|
2011-12-15 22:09:51 +01:00
|
|
|
ISABus *isa_bus;
|
2010-05-14 09:29:15 +02:00
|
|
|
PCII440FXState *i440fx_state;
|
|
|
|
int piix3_devfn = -1;
|
2011-10-07 09:19:35 +02:00
|
|
|
qemu_irq *gsi;
|
2010-05-14 09:29:15 +02:00
|
|
|
qemu_irq *i8259;
|
2015-05-26 03:46:05 +02:00
|
|
|
qemu_irq smi_irq;
|
2011-10-07 09:19:35 +02:00
|
|
|
GSIState *gsi_state;
|
2010-05-14 09:29:15 +02:00
|
|
|
DriveInfo *hd[MAX_IDE_BUS * MAX_IDE_DEVS];
|
2010-06-24 19:58:20 +02:00
|
|
|
BusState *idebus[MAX_IDE_BUS];
|
2010-05-14 09:29:17 +02:00
|
|
|
ISADevice *rtc_state;
|
2011-08-15 16:17:38 +02:00
|
|
|
MemoryRegion *ram_memory;
|
|
|
|
MemoryRegion *pci_memory;
|
2011-09-21 20:49:29 +02:00
|
|
|
MemoryRegion *rom_memory;
|
2013-05-30 11:57:26 +02:00
|
|
|
PcGuestInfo *guest_info;
|
2014-06-20 03:40:25 +02:00
|
|
|
ram_addr_t lowmem;
|
2010-05-14 09:29:15 +02:00
|
|
|
|
2013-12-16 12:54:19 +01:00
|
|
|
/* Check whether RAM fits below 4G (leaving 1/2 GByte for IO memory).
|
|
|
|
* If it doesn't, we need to split it in chunks below and above 4G.
|
|
|
|
* In any case, try to make sure that guest addresses aligned at
|
|
|
|
* 1G boundaries get mapped to host addresses aligned at 1G boundaries.
|
|
|
|
* For old machine types, use whatever split we used historically to avoid
|
|
|
|
* breaking migration.
|
|
|
|
*/
|
2014-05-07 16:42:57 +02:00
|
|
|
if (machine->ram_size >= 0xe0000000) {
|
2014-06-20 03:40:25 +02:00
|
|
|
lowmem = gigabyte_align ? 0xc0000000 : 0xe0000000;
|
|
|
|
} else {
|
|
|
|
lowmem = 0xe0000000;
|
|
|
|
}
|
|
|
|
|
2014-07-07 21:00:41 +02:00
|
|
|
/* Handle the machine opt max-ram-below-4g. It is basically doing
|
2014-06-20 03:40:25 +02:00
|
|
|
* min(qemu limit, user limit).
|
|
|
|
*/
|
2015-08-07 21:55:45 +02:00
|
|
|
if (lowmem > pcms->max_ram_below_4g) {
|
|
|
|
lowmem = pcms->max_ram_below_4g;
|
2014-06-20 03:40:25 +02:00
|
|
|
if (machine->ram_size - lowmem > lowmem &&
|
|
|
|
lowmem & ((1ULL << 30) - 1)) {
|
|
|
|
error_report("Warning: Large machine and max_ram_below_4g(%"PRIu64
|
|
|
|
") not a multiple of 1G; possible bad performance.",
|
2015-08-07 21:55:45 +02:00
|
|
|
pcms->max_ram_below_4g);
|
2014-06-20 03:40:25 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (machine->ram_size >= lowmem) {
|
2015-08-07 21:55:51 +02:00
|
|
|
pcms->above_4g_mem_size = machine->ram_size - lowmem;
|
|
|
|
pcms->below_4g_mem_size = lowmem;
|
2011-04-11 20:48:11 +02:00
|
|
|
} else {
|
2015-08-07 21:55:51 +02:00
|
|
|
pcms->above_4g_mem_size = 0;
|
|
|
|
pcms->below_4g_mem_size = machine->ram_size;
|
2011-04-11 20:48:11 +02:00
|
|
|
}
|
|
|
|
|
2015-08-17 20:42:29 +02:00
|
|
|
if (xen_enabled() && xen_hvm_init(pcms, &ram_memory) != 0) {
|
2014-06-20 03:40:24 +02:00
|
|
|
fprintf(stderr, "xen hardware virtual machine initialisation failed\n");
|
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
|
2015-10-15 05:12:12 +02:00
|
|
|
pc_cpus_init(pcms);
|
2014-06-20 03:40:24 +02:00
|
|
|
|
|
|
|
if (kvm_enabled() && kvmclock_enabled) {
|
|
|
|
kvmclock_create();
|
|
|
|
}
|
|
|
|
|
2011-09-21 20:49:29 +02:00
|
|
|
if (pci_enabled) {
|
|
|
|
pci_memory = g_new(MemoryRegion, 1);
|
2013-11-06 19:18:08 +01:00
|
|
|
memory_region_init(pci_memory, NULL, "pci", UINT64_MAX);
|
2011-09-21 20:49:29 +02:00
|
|
|
rom_memory = pci_memory;
|
|
|
|
} else {
|
|
|
|
pci_memory = NULL;
|
|
|
|
rom_memory = system_memory;
|
|
|
|
}
|
2011-08-15 16:17:38 +02:00
|
|
|
|
2015-08-07 21:55:52 +02:00
|
|
|
guest_info = pc_guest_info_init(pcms);
|
i386: ACPI table generation code from seabios
This adds C code for generating ACPI tables at runtime,
imported from seabios git tree
commit 51684b7ced75fb76776e8ee84833fcfb6ecf12dd
Although ACPI tables come from a system BIOS on real hw,
it makes sense that the ACPI tables are coupled with the
virtual machine, since they have to abstract the x86 machine to
the OS's.
This is widely desired as a way to avoid the churn
and proliferation of QEMU-specific interfaces
associated with ACPI tables in bios code.
Notes:
As BIOS can reprogram devices prior to loading
ACPI tables, we pre-format ACPI tables but defer loading
hardware configuration there until tables are loaded.
The code structure was intentionally kept as close
to the seabios original as possible, to simplify
comparison and making sure we didn't lose anything
in translation.
Minor code duplication results, to help ensure there are no functional
regressions, I think it's better to merge it like this and do more code
changes in follow-up patches.
Cross-version compatibility concerns have been addressed:
ACPI tables are exposed to guest as FW_CFG entries.
When running with -M 1.5 and older, this patch disables ACPI
table generation, and doesn't expose ACPI
tables to guest.
As table content is likely to change over time,
the following measures are taken to simplify
cross-version migration:
- All tables besides the RSDP are packed in a single FW CFG entry.
This entry size is currently 23K. We round it up to 64K
to avoid too much churn there.
- Tables are placed in special ROM blob (not mapped into guest memory)
which is automatically migrated together with the guest, same
as BIOS code.
- Offsets where hardware configuration is loaded in ACPI tables
are also migrated, this is in case future ACPI changes make us
rearrange the tables in memory.
This patch reuses some code from SeaBIOS, which was originally under
LGPLv2 and then relicensed to GPLv3 or LGPLv3, in QEMU under GPLv2+. This
relicensing has been acked by all contributors that had contributed to the
code since the v2->v3 relicense. ACKs approving the v2+ relicensing are
listed below. The list might include ACKs from people not holding
copyright on any parts of the reused code, but it's better to err on the
side of caution and include them.
Affected SeaBIOS files (GPLv2+ license headers added)
<http://thread.gmane.org/gmane.comp.bios.coreboot.seabios/5949>:
src/acpi-dsdt-cpu-hotplug.dsl
src/acpi-dsdt-dbug.dsl
src/acpi-dsdt-hpet.dsl
src/acpi-dsdt-isa.dsl
src/acpi-dsdt-pci-crs.dsl
src/acpi.c
src/acpi.h
src/ssdt-misc.dsl
src/ssdt-pcihp.dsl
src/ssdt-proc.dsl
tools/acpi_extract.py
tools/acpi_extract_preprocess.py
Each one of the listed people agreed to the following:
> If you allow the use of your contribution in QEMU under the
> terms of GPLv2 or later as proposed by this patch,
> please respond to this mail including the line:
>
> Acked-by: Name <email address>
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
Acked-by: Jan Kiszka <jan.kiszka@siemens.com>
Acked-by: Jason Baron <jbaron@akamai.com>
Acked-by: David Woodhouse <David.Woodhouse@intel.com>
Acked-by: Gleb Natapov <gleb@redhat.com>
Acked-by: Marcelo Tosatti <mtosatti@redhat.com>
Acked-by: Dave Frodin <dave.frodin@se-eng.com>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Acked-by: Kevin O'Connor <kevin@koconnor.net>
Acked-by: Laszlo Ersek <lersek@redhat.com>
Acked-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Acked-by: Isaku Yamahata <yamahata@valinux.co.jp>
Acked-by: Magnus Christensson <magnus.christensson@intel.com>
Acked-by: Hu Tao <hutao@cn.fujitsu.com>
Acked-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
Tested-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Tested-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2013-07-24 17:56:14 +02:00
|
|
|
|
|
|
|
guest_info->has_acpi_build = has_acpi_build;
|
pc: hack for migration compatibility from QEMU 2.0
Changing the ACPI table size causes migration to break, and the memory
hotplug work opened our eyes on how horribly we were breaking things in
2.0 already.
The ACPI table size is rounded to the next 4k, which one would think
gives some headroom. In practice this is not the case, because the user
can control the ACPI table size (each CPU adds 97 bytes to the SSDT and
8 to the MADT) and so some "-smp" values will break the 4k boundary and
fail to migrate. Similarly, PCI bridges add ~1870 bytes to the SSDT.
This patch concerns itself with fixing migration from QEMU 2.0. It
computes the payload size of QEMU 2.0 and always uses that one.
The previous patch shrunk the ACPI tables enough that the QEMU 2.0 size
should always be enough; non-AML tables can change depending on the
configuration (especially MADT, SRAT, HPET) but they remain the same
between QEMU 2.0 and 2.1, so we only compute our padding based on the
sizes of the SSDT and DSDT.
Migration from QEMU 1.7 should work for guests that have a number of CPUs
other than 12, 13, 14, 54, 55, 56, 97, 98, 139, 140. It was already
broken from QEMU 1.7 to QEMU 2.0 in the same way, though.
Even with this patch, QEMU 1.7 and 2.0 have two different ideas of
"-M pc-i440fx-2.0" when there are PCI bridges. Igor sent a patch to
adopt the QEMU 1.7 definition. I think distributions should apply
it if they move directly from QEMU 1.7 to 2.1+ without ever packaging
version 2.0.
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Tested-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2014-07-28 17:34:15 +02:00
|
|
|
guest_info->legacy_acpi_table_size = legacy_acpi_table_size;
|
i386: ACPI table generation code from seabios
This adds C code for generating ACPI tables at runtime,
imported from seabios git tree
commit 51684b7ced75fb76776e8ee84833fcfb6ecf12dd
Although ACPI tables come from a system BIOS on real hw,
it makes sense that the ACPI tables are coupled with the
virtual machine, since they have to abstract the x86 machine to
the OS's.
This is widely desired as a way to avoid the churn
and proliferation of QEMU-specific interfaces
associated with ACPI tables in bios code.
Notes:
As BIOS can reprogram devices prior to loading
ACPI tables, we pre-format ACPI tables but defer loading
hardware configuration there until tables are loaded.
The code structure was intentionally kept as close
to the seabios original as possible, to simplify
comparison and making sure we didn't lose anything
in translation.
Minor code duplication results, to help ensure there are no functional
regressions, I think it's better to merge it like this and do more code
changes in follow-up patches.
Cross-version compatibility concerns have been addressed:
ACPI tables are exposed to guest as FW_CFG entries.
When running with -M 1.5 and older, this patch disables ACPI
table generation, and doesn't expose ACPI
tables to guest.
As table content is likely to change over time,
the following measures are taken to simplify
cross-version migration:
- All tables besides the RSDP are packed in a single FW CFG entry.
This entry size is currently 23K. We round it up to 64K
to avoid too much churn there.
- Tables are placed in special ROM blob (not mapped into guest memory)
which is automatically migrated together with the guest, same
as BIOS code.
- Offsets where hardware configuration is loaded in ACPI tables
are also migrated, this is in case future ACPI changes make us
rearrange the tables in memory.
This patch reuses some code from SeaBIOS, which was originally under
LGPLv2 and then relicensed to GPLv3 or LGPLv3, in QEMU under GPLv2+. This
relicensing has been acked by all contributors that had contributed to the
code since the v2->v3 relicense. ACKs approving the v2+ relicensing are
listed below. The list might include ACKs from people not holding
copyright on any parts of the reused code, but it's better to err on the
side of caution and include them.
Affected SeaBIOS files (GPLv2+ license headers added)
<http://thread.gmane.org/gmane.comp.bios.coreboot.seabios/5949>:
src/acpi-dsdt-cpu-hotplug.dsl
src/acpi-dsdt-dbug.dsl
src/acpi-dsdt-hpet.dsl
src/acpi-dsdt-isa.dsl
src/acpi-dsdt-pci-crs.dsl
src/acpi.c
src/acpi.h
src/ssdt-misc.dsl
src/ssdt-pcihp.dsl
src/ssdt-proc.dsl
tools/acpi_extract.py
tools/acpi_extract_preprocess.py
Each one of the listed people agreed to the following:
> If you allow the use of your contribution in QEMU under the
> terms of GPLv2 or later as proposed by this patch,
> please respond to this mail including the line:
>
> Acked-by: Name <email address>
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
Acked-by: Jan Kiszka <jan.kiszka@siemens.com>
Acked-by: Jason Baron <jbaron@akamai.com>
Acked-by: David Woodhouse <David.Woodhouse@intel.com>
Acked-by: Gleb Natapov <gleb@redhat.com>
Acked-by: Marcelo Tosatti <mtosatti@redhat.com>
Acked-by: Dave Frodin <dave.frodin@se-eng.com>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Acked-by: Kevin O'Connor <kevin@koconnor.net>
Acked-by: Laszlo Ersek <lersek@redhat.com>
Acked-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Acked-by: Isaku Yamahata <yamahata@valinux.co.jp>
Acked-by: Magnus Christensson <magnus.christensson@intel.com>
Acked-by: Hu Tao <hutao@cn.fujitsu.com>
Acked-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
Tested-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Tested-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2013-07-24 17:56:14 +02:00
|
|
|
|
2013-08-09 19:35:02 +02:00
|
|
|
guest_info->isapc_ram_fw = !pci_enabled;
|
2014-06-02 15:25:10 +02:00
|
|
|
guest_info->has_reserved_memory = has_reserved_memory;
|
2015-02-17 10:04:40 +01:00
|
|
|
guest_info->rsdp_in_ram = rsdp_in_ram;
|
2013-05-30 11:57:26 +02:00
|
|
|
|
2014-04-23 15:42:38 +02:00
|
|
|
if (smbios_defaults) {
|
2014-05-07 16:42:57 +02:00
|
|
|
MachineClass *mc = MACHINE_GET_CLASS(machine);
|
2013-10-30 13:56:40 +01:00
|
|
|
/* These values are guest ABI, do not change */
|
2014-04-23 15:42:38 +02:00
|
|
|
smbios_set_defaults("QEMU", "Standard PC (i440FX + PIIX, 1996)",
|
2015-09-07 11:39:28 +02:00
|
|
|
mc->name, smbios_legacy_mode, smbios_uuid_encoded,
|
|
|
|
SMBIOS_ENTRY_POINT_21);
|
2013-10-30 13:56:40 +01:00
|
|
|
}
|
|
|
|
|
2010-05-14 09:29:15 +02:00
|
|
|
/* allocate ram and load rom/bios */
|
2010-06-30 13:58:34 +02:00
|
|
|
if (!xen_enabled()) {
|
2015-08-07 21:55:50 +02:00
|
|
|
pc_memory_init(pcms, system_memory,
|
2015-04-29 15:20:16 +02:00
|
|
|
rom_memory, &ram_memory, guest_info);
|
2014-07-07 08:34:35 +02:00
|
|
|
} else if (machine->kernel_filename != NULL) {
|
|
|
|
/* For xen HVM direct kernel boot, load linux here */
|
2015-08-07 21:55:53 +02:00
|
|
|
xen_load_linux(pcms, guest_info);
|
2010-06-30 13:58:34 +02:00
|
|
|
}
|
2010-05-14 09:29:15 +02:00
|
|
|
|
2011-10-07 09:19:35 +02:00
|
|
|
gsi_state = g_malloc0(sizeof(*gsi_state));
|
2012-01-31 19:17:52 +01:00
|
|
|
if (kvm_irqchip_in_kernel()) {
|
2012-11-14 21:54:02 +01:00
|
|
|
kvm_pc_setup_irq_routing(pci_enabled);
|
|
|
|
gsi = qemu_allocate_irqs(kvm_pc_gsi_handler, gsi_state,
|
2011-10-16 15:30:27 +02:00
|
|
|
GSI_NUM_PINS);
|
|
|
|
} else {
|
|
|
|
gsi = qemu_allocate_irqs(gsi_handler, gsi_state, GSI_NUM_PINS);
|
|
|
|
}
|
2010-05-14 09:29:15 +02:00
|
|
|
|
|
|
|
if (pci_enabled) {
|
2015-07-15 07:37:42 +02:00
|
|
|
pci_bus = i440fx_init(host_type,
|
|
|
|
pci_type,
|
2015-07-15 07:37:41 +02:00
|
|
|
&i440fx_state, &piix3_devfn, &isa_bus, gsi,
|
2014-05-07 16:42:57 +02:00
|
|
|
system_memory, system_io, machine->ram_size,
|
2015-08-07 21:55:51 +02:00
|
|
|
pcms->below_4g_mem_size,
|
|
|
|
pcms->above_4g_mem_size,
|
2011-08-15 16:17:38 +02:00
|
|
|
pci_memory, ram_memory);
|
2010-05-14 09:29:15 +02:00
|
|
|
} else {
|
|
|
|
pci_bus = NULL;
|
isapc: fix segfault.
https://bugs.launchpad.net/bugs/611646
reports that ./i386-softmmu/qemu -M isapc segfaults.
This patch fixes the segfault introduced by
f885f1eaa8711c06033ceb1599e3750fb37c306f
It's because i440fx_state in pc_init1() isn't initialized.
> Core was generated by `./i386-softmmu/qemu -M isapc'.
> Program terminated with signal 11, Segmentation fault.
> [New process 19686]
> at qemu/hw/piix_pci.c:136
> (gdb) where
> at qemu/hw/piix_pci.c:136
> boot_device=0x7fffe1f5b040 "cad", kernel_filename=0x0,
> kernel_cmdline=0x6469bf "", initrd_filename=0x0,
> cpu_model=0x654d10 "486", pci_enabled=0)
> at qemu/hw/pc_piix.c:178
> boot_device=0x7fffe1f5b040 "cad", kernel_filename=0x0,
> kernel_cmdline=0x6469bf "", initrd_filename=0x0, cpu_model=0x654d10 "486")
> at qemu/hw/pc_piix.c:207
> envp=0x7fffe1f5b188)
> at qemu/vl.c:2871
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
2010-08-04 10:43:20 +02:00
|
|
|
i440fx_state = NULL;
|
2015-02-01 09:12:50 +01:00
|
|
|
isa_bus = isa_bus_new(NULL, get_system_memory(), system_io);
|
2011-09-21 20:49:30 +02:00
|
|
|
no_hpet = 1;
|
2010-05-14 09:29:15 +02:00
|
|
|
}
|
2011-12-15 22:09:51 +01:00
|
|
|
isa_bus_irqs(isa_bus, gsi);
|
2010-05-14 09:29:15 +02:00
|
|
|
|
2012-01-31 19:17:52 +01:00
|
|
|
if (kvm_irqchip_in_kernel()) {
|
2011-10-16 15:30:27 +02:00
|
|
|
i8259 = kvm_i8259_init(isa_bus);
|
|
|
|
} else if (xen_enabled()) {
|
|
|
|
i8259 = xen_interrupt_controller_init();
|
|
|
|
} else {
|
2015-05-29 07:26:59 +02:00
|
|
|
i8259 = i8259_init(isa_bus, pc_allocate_cpu_irq());
|
2011-08-11 00:28:13 +02:00
|
|
|
}
|
|
|
|
|
2011-10-07 09:19:36 +02:00
|
|
|
for (i = 0; i < ISA_NUM_IRQS; i++) {
|
|
|
|
gsi_state->i8259_irq[i] = i8259[i];
|
|
|
|
}
|
2015-05-26 03:46:05 +02:00
|
|
|
g_free(i8259);
|
2011-08-11 00:28:13 +02:00
|
|
|
if (pci_enabled) {
|
2012-11-14 21:54:01 +01:00
|
|
|
ioapic_init_gsi(gsi_state, "i440fx");
|
2011-08-11 00:28:13 +02:00
|
|
|
}
|
|
|
|
|
2011-10-07 09:19:35 +02:00
|
|
|
pc_register_ferr_irq(gsi[13]);
|
2010-05-14 09:29:15 +02:00
|
|
|
|
2012-03-27 18:38:46 +02:00
|
|
|
pc_vga_init(isa_bus, pci_enabled ? pci_bus : NULL);
|
2011-06-16 18:05:17 +02:00
|
|
|
|
2015-08-07 21:55:45 +02:00
|
|
|
assert(pcms->vmport != ON_OFF_AUTO_MAX);
|
|
|
|
if (pcms->vmport == ON_OFF_AUTO_AUTO) {
|
|
|
|
pcms->vmport = xen_enabled() ? ON_OFF_AUTO_OFF : ON_OFF_AUTO_ON;
|
2014-11-21 17:18:52 +01:00
|
|
|
}
|
|
|
|
|
2010-05-14 09:29:15 +02:00
|
|
|
/* init basic PC hardware */
|
2015-06-25 15:35:07 +02:00
|
|
|
pc_basic_device_init(isa_bus, gsi, &rtc_state, true,
|
2015-08-07 21:55:45 +02:00
|
|
|
(pcms->vmport != ON_OFF_AUTO_ON), 0x4);
|
2010-05-14 09:29:15 +02:00
|
|
|
|
2012-11-14 21:54:01 +01:00
|
|
|
pc_nic_init(isa_bus, pci_bus);
|
2010-05-14 09:29:15 +02:00
|
|
|
|
2014-10-01 20:19:27 +02:00
|
|
|
ide_drive_get(hd, ARRAY_SIZE(hd));
|
2010-05-14 09:29:15 +02:00
|
|
|
if (pci_enabled) {
|
2010-06-24 19:58:20 +02:00
|
|
|
PCIDevice *dev;
|
2011-07-18 08:07:02 +02:00
|
|
|
if (xen_enabled()) {
|
|
|
|
dev = pci_piix3_xen_ide_init(pci_bus, hd, piix3_devfn + 1);
|
|
|
|
} else {
|
|
|
|
dev = pci_piix3_ide_init(pci_bus, hd, piix3_devfn + 1);
|
|
|
|
}
|
2010-06-24 19:58:20 +02:00
|
|
|
idebus[0] = qdev_get_child_bus(&dev->qdev, "ide.0");
|
|
|
|
idebus[1] = qdev_get_child_bus(&dev->qdev, "ide.1");
|
2010-05-14 09:29:15 +02:00
|
|
|
} else {
|
|
|
|
for(i = 0; i < MAX_IDE_BUS; i++) {
|
2010-06-24 19:58:20 +02:00
|
|
|
ISADevice *dev;
|
qdev: Keep global allocation counter per bus
When we have 2 separate qdev devices that both create a qbus of the
same type without specifying a bus name or device name, we end up
with two buses of the same name, such as ide.0 on the Mac machines:
dev: macio-ide, id ""
bus: ide.0
type IDE
dev: macio-ide, id ""
bus: ide.0
type IDE
If we now spawn a device that connects to a ide.0 the last created
bus gets the device, with the first created bus inaccessible to the
command line.
After some discussion on IRC we concluded that the best quick fix way
forward for this is to make automated bus-class type based allocation
count a global counter. That's what this patch implements. With this
we instead get
dev: macio-ide, id ""
bus: ide.1
type IDE
dev: macio-ide, id ""
bus: ide.0
type IDE
on the example mentioned above.
This also means that if you did -device ...,bus=ide.0 you got a device
on the first bus (the last created one) before this patch and get that
device on the second one (the first created one) now. Breaks
migration unless you change bus=ide.0 to bus=ide.1 on the destination.
This is intended and makes the bus enumeration work as expected.
As per review request follows a list of otherwise affected boards and
the reasoning for the conclusion that they are ok:
target machine bus id times
------ ------- ------ -----
aarch64 n800 i2c-bus.0 2
aarch64 n810 i2c-bus.0 2
arm n800 i2c-bus.0 2
arm n810 i2c-bus.0 2
-> Devices are only created explicitly on one of the two buses, using
s->mpu->i2c[0], so no change to the guest.
aarch64 vexpress-a15 virtio-mmio-bus.0 4
aarch64 vexpress-a9 virtio-mmio-bus.0 4
aarch64 virt virtio-mmio-bus.0 32
arm vexpress-a15 virtio-mmio-bus.0 4
arm vexpress-a9 virtio-mmio-bus.0 4
arm virt virtio-mmio-bus.0 32
-> Makes -device bus= work for all virtio-mmio buses. Breaks
migration. Workaround for migration from old to new: specify
virtio-mmio-bus.4 or .32 respectively rather than .0 on the
destination.
aarch64 xilinx-zynq-a9 usb-bus.0 2
arm xilinx-zynq-a9 usb-bus.0 2
mips64el fulong2e usb-bus.0 2
-> Normal USB operation not affected. Migration driver needs command
line to use the other bus.
i386 isapc ide.0 2
x86_64 isapc ide.0 2
mips mips ide.0 2
mips64 mips ide.0 2
mips64el mips ide.0 2
mipsel mips ide.0 2
ppc g3beige ide.0 2
ppc mac99 ide.0 2
ppc prep ide.0 2
ppc64 g3beige ide.0 2
ppc64 mac99 ide.0 2
ppc64 prep ide.0 2
-> Makes -device bus= work for all IDE buses. Breaks migration.
Workaround for migration from old to new: specify ide.1 rather than
ide.0 on the destination.
Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Andreas Faerber <afaerber@suse.de>
Signed-off-by: Alexander Graf <agraf@suse.de>
2014-02-06 16:08:15 +01:00
|
|
|
char busname[] = "ide.0";
|
2011-12-15 22:09:51 +01:00
|
|
|
dev = isa_ide_init(isa_bus, ide_iobase[i], ide_iobase2[i],
|
|
|
|
ide_irq[i],
|
2010-06-24 19:58:20 +02:00
|
|
|
hd[MAX_IDE_DEVS * i], hd[MAX_IDE_DEVS * i + 1]);
|
qdev: Keep global allocation counter per bus
When we have 2 separate qdev devices that both create a qbus of the
same type without specifying a bus name or device name, we end up
with two buses of the same name, such as ide.0 on the Mac machines:
dev: macio-ide, id ""
bus: ide.0
type IDE
dev: macio-ide, id ""
bus: ide.0
type IDE
If we now spawn a device that connects to a ide.0 the last created
bus gets the device, with the first created bus inaccessible to the
command line.
After some discussion on IRC we concluded that the best quick fix way
forward for this is to make automated bus-class type based allocation
count a global counter. That's what this patch implements. With this
we instead get
dev: macio-ide, id ""
bus: ide.1
type IDE
dev: macio-ide, id ""
bus: ide.0
type IDE
on the example mentioned above.
This also means that if you did -device ...,bus=ide.0 you got a device
on the first bus (the last created one) before this patch and get that
device on the second one (the first created one) now. Breaks
migration unless you change bus=ide.0 to bus=ide.1 on the destination.
This is intended and makes the bus enumeration work as expected.
As per review request follows a list of otherwise affected boards and
the reasoning for the conclusion that they are ok:
target machine bus id times
------ ------- ------ -----
aarch64 n800 i2c-bus.0 2
aarch64 n810 i2c-bus.0 2
arm n800 i2c-bus.0 2
arm n810 i2c-bus.0 2
-> Devices are only created explicitly on one of the two buses, using
s->mpu->i2c[0], so no change to the guest.
aarch64 vexpress-a15 virtio-mmio-bus.0 4
aarch64 vexpress-a9 virtio-mmio-bus.0 4
aarch64 virt virtio-mmio-bus.0 32
arm vexpress-a15 virtio-mmio-bus.0 4
arm vexpress-a9 virtio-mmio-bus.0 4
arm virt virtio-mmio-bus.0 32
-> Makes -device bus= work for all virtio-mmio buses. Breaks
migration. Workaround for migration from old to new: specify
virtio-mmio-bus.4 or .32 respectively rather than .0 on the
destination.
aarch64 xilinx-zynq-a9 usb-bus.0 2
arm xilinx-zynq-a9 usb-bus.0 2
mips64el fulong2e usb-bus.0 2
-> Normal USB operation not affected. Migration driver needs command
line to use the other bus.
i386 isapc ide.0 2
x86_64 isapc ide.0 2
mips mips ide.0 2
mips64 mips ide.0 2
mips64el mips ide.0 2
mipsel mips ide.0 2
ppc g3beige ide.0 2
ppc mac99 ide.0 2
ppc prep ide.0 2
ppc64 g3beige ide.0 2
ppc64 mac99 ide.0 2
ppc64 prep ide.0 2
-> Makes -device bus= work for all IDE buses. Breaks migration.
Workaround for migration from old to new: specify ide.1 rather than
ide.0 on the destination.
Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Andreas Faerber <afaerber@suse.de>
Signed-off-by: Alexander Graf <agraf@suse.de>
2014-02-06 16:08:15 +01:00
|
|
|
/*
|
|
|
|
* The ide bus name is ide.0 for the first bus and ide.1 for the
|
|
|
|
* second one.
|
|
|
|
*/
|
|
|
|
busname[4] = '0' + i;
|
|
|
|
idebus[i] = qdev_get_child_bus(DEVICE(dev), busname);
|
2010-05-14 09:29:15 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2015-08-07 21:55:54 +02:00
|
|
|
pc_cmos_init(pcms, idebus[0], idebus[1], rtc_state);
|
2010-05-14 09:29:15 +02:00
|
|
|
|
2015-01-06 14:29:14 +01:00
|
|
|
if (pci_enabled && usb_enabled()) {
|
2012-03-07 15:06:32 +01:00
|
|
|
pci_create_simple(pci_bus, piix3_devfn + 2, "piix3-usb-uhci");
|
2010-05-14 09:29:15 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
if (pci_enabled && acpi_enabled) {
|
2014-06-02 15:25:24 +02:00
|
|
|
DeviceState *piix4_pm;
|
2013-08-03 00:18:51 +02:00
|
|
|
I2CBus *smbus;
|
2010-05-14 09:29:15 +02:00
|
|
|
|
2015-05-26 03:46:05 +02:00
|
|
|
smi_irq = qemu_allocate_irq(pc_acpi_smi_interrupt, first_cpu, 0);
|
2010-05-14 09:29:15 +02:00
|
|
|
/* TODO: Populate SPD eeprom data. */
|
|
|
|
smbus = piix4_pm_init(pci_bus, piix3_devfn + 3, 0xb100,
|
2015-05-26 03:46:05 +02:00
|
|
|
gsi[9], smi_irq,
|
2015-08-07 21:55:45 +02:00
|
|
|
pc_machine_is_smm_enabled(pcms),
|
2015-06-18 18:30:52 +02:00
|
|
|
&piix4_pm);
|
2011-04-05 04:07:06 +02:00
|
|
|
smbus_eeprom_init(smbus, 8, NULL, 0);
|
2014-06-02 15:25:24 +02:00
|
|
|
|
|
|
|
object_property_add_link(OBJECT(machine), PC_MACHINE_ACPI_DEVICE_PROP,
|
|
|
|
TYPE_HOTPLUG_HANDLER,
|
2015-08-07 21:55:45 +02:00
|
|
|
(Object **)&pcms->acpi_dev,
|
2014-06-02 15:25:24 +02:00
|
|
|
object_property_allow_set_link,
|
|
|
|
OBJ_PROP_LINK_UNREF_ON_RELEASE, &error_abort);
|
|
|
|
object_property_set_link(OBJECT(machine), OBJECT(piix4_pm),
|
|
|
|
PC_MACHINE_ACPI_DEVICE_PROP, &error_abort);
|
2010-05-14 09:29:15 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
if (pci_enabled) {
|
|
|
|
pc_pci_device_init(pci_bus);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2015-09-28 20:07:21 +02:00
|
|
|
/* Looking for a pc_compat_2_4() function? It doesn't exist.
|
|
|
|
* pc_compat_*() functions that run on machine-init time and
|
|
|
|
* change global QEMU state are deprecated. Please don't create
|
|
|
|
* one, and implement any pc-*-2.4 (and newer) compat code in
|
|
|
|
* HW_COMPAT_*, PC_COMPAT_*, or * pc_*_machine_options().
|
|
|
|
*/
|
|
|
|
|
2015-04-23 08:21:35 +02:00
|
|
|
static void pc_compat_2_3(MachineState *machine)
|
|
|
|
{
|
2015-06-18 18:30:52 +02:00
|
|
|
PCMachineState *pcms = PC_MACHINE(machine);
|
2015-05-19 13:29:51 +02:00
|
|
|
savevm_skip_section_footers();
|
2015-06-18 18:30:52 +02:00
|
|
|
if (kvm_enabled()) {
|
|
|
|
pcms->smm = ON_OFF_AUTO_OFF;
|
|
|
|
}
|
2014-10-08 13:58:24 +02:00
|
|
|
global_state_set_optional();
|
2015-05-13 18:17:43 +02:00
|
|
|
savevm_skip_configuration();
|
2015-04-23 08:21:35 +02:00
|
|
|
}
|
|
|
|
|
2014-12-05 10:51:42 +01:00
|
|
|
static void pc_compat_2_2(MachineState *machine)
|
|
|
|
{
|
2015-04-23 08:21:35 +02:00
|
|
|
pc_compat_2_3(machine);
|
2015-02-17 10:04:40 +01:00
|
|
|
rsdp_in_ram = false;
|
2015-02-23 13:56:43 +01:00
|
|
|
machine->suppress_vmdesc = true;
|
2014-12-05 10:51:42 +01:00
|
|
|
}
|
|
|
|
|
2014-10-29 14:26:07 +01:00
|
|
|
static void pc_compat_2_1(MachineState *machine)
|
|
|
|
{
|
2014-10-31 17:38:39 +01:00
|
|
|
PCMachineState *pcms = PC_MACHINE(machine);
|
2014-12-05 10:51:42 +01:00
|
|
|
|
|
|
|
pc_compat_2_2(machine);
|
smbios: Encode UUID according to SMBIOS specification
Differently from older versions, SMBIOS version 2.6 is explicit about
the encoding of UUID fields:
> Although RFC 4122 recommends network byte order for all fields, the PC
> industry (including the ACPI, UEFI, and Microsoft specifications) has
> consistently used little-endian byte encoding for the first three fields:
> time_low, time_mid, time_hi_and_version. The same encoding, also known as
> wire format, should also be used for the SMBIOS representation of the UUID.
>
> The UUID {00112233-4455-6677-8899-AABBCCDDEEFF} would thus be represented
> as 33 22 11 00 55 44 77 66 88 99 AA BB CC DD EE FF.
The dmidecode tool implements this and decodes the above "wire format"
when SMBIOS version >= 2.6. We moved from SMBIOS version 2.4 to 2.8 when
we started building the SMBIOS entry point inside QEMU, on commit
c97294ec1b9e36887e119589d456557d72ab37b5.
Change smbios_build_type_1_table() to encode the UUID as specified.
To make sure we won't change the guest-visible UUID when upgrading to a
newer QEMU version, keep the old behavior on pc-*-2.1 and older.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2014-10-29 14:26:08 +01:00
|
|
|
smbios_uuid_encoded = false;
|
2015-09-11 17:40:27 +02:00
|
|
|
x86_cpu_change_kvm_default("svm", NULL);
|
2014-10-31 17:38:39 +01:00
|
|
|
pcms->enforce_aligned_dimm = false;
|
2014-10-29 14:26:07 +01:00
|
|
|
}
|
|
|
|
|
2014-05-07 16:42:57 +02:00
|
|
|
static void pc_compat_2_0(MachineState *machine)
|
2014-04-24 12:14:53 +02:00
|
|
|
{
|
2014-10-29 14:26:07 +01:00
|
|
|
pc_compat_2_1(machine);
|
pc: hack for migration compatibility from QEMU 2.0
Changing the ACPI table size causes migration to break, and the memory
hotplug work opened our eyes on how horribly we were breaking things in
2.0 already.
The ACPI table size is rounded to the next 4k, which one would think
gives some headroom. In practice this is not the case, because the user
can control the ACPI table size (each CPU adds 97 bytes to the SSDT and
8 to the MADT) and so some "-smp" values will break the 4k boundary and
fail to migrate. Similarly, PCI bridges add ~1870 bytes to the SSDT.
This patch concerns itself with fixing migration from QEMU 2.0. It
computes the payload size of QEMU 2.0 and always uses that one.
The previous patch shrunk the ACPI tables enough that the QEMU 2.0 size
should always be enough; non-AML tables can change depending on the
configuration (especially MADT, SRAT, HPET) but they remain the same
between QEMU 2.0 and 2.1, so we only compute our padding based on the
sizes of the SSDT and DSDT.
Migration from QEMU 1.7 should work for guests that have a number of CPUs
other than 12, 13, 14, 54, 55, 56, 97, 98, 139, 140. It was already
broken from QEMU 1.7 to QEMU 2.0 in the same way, though.
Even with this patch, QEMU 1.7 and 2.0 have two different ideas of
"-M pc-i440fx-2.0" when there are PCI bridges. Igor sent a patch to
adopt the QEMU 1.7 definition. I think distributions should apply
it if they move directly from QEMU 1.7 to 2.1+ without ever packaging
version 2.0.
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Tested-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2014-07-28 17:34:15 +02:00
|
|
|
/* This value depends on the actual DSDT and SSDT compiled into
|
|
|
|
* the source QEMU; unfortunately it depends on the binary and
|
|
|
|
* not on the machine type, so we cannot make pc-i440fx-1.7 work on
|
|
|
|
* both QEMU 1.7 and QEMU 2.0.
|
|
|
|
*
|
|
|
|
* Large variations cause migration to fail for more than one
|
|
|
|
* consecutive value of the "-smp" maxcpus option.
|
|
|
|
*
|
|
|
|
* For small variations of the kind caused by different iasl versions,
|
|
|
|
* the 4k rounding usually leaves slack. However, there could be still
|
|
|
|
* one or two values that break. For QEMU 1.7 and QEMU 2.0 the
|
|
|
|
* slack is only ~10 bytes before one "-smp maxcpus" value breaks!
|
|
|
|
*
|
|
|
|
* 6652 is valid for QEMU 2.0, the right value for pc-i440fx-1.7 on
|
|
|
|
* QEMU 1.7 it is 6414. For RHEL/CentOS 7.0 it is 6418.
|
|
|
|
*/
|
|
|
|
legacy_acpi_table_size = 6652;
|
2014-04-23 15:42:42 +02:00
|
|
|
smbios_legacy_mode = true;
|
2014-06-02 15:25:10 +02:00
|
|
|
has_reserved_memory = false;
|
2014-08-20 21:58:12 +02:00
|
|
|
pc_set_legacy_acpi_data_size();
|
2014-04-24 12:14:53 +02:00
|
|
|
}
|
|
|
|
|
2014-05-07 16:42:57 +02:00
|
|
|
static void pc_compat_1_7(MachineState *machine)
|
2013-10-30 13:56:40 +01:00
|
|
|
{
|
2014-05-07 16:42:57 +02:00
|
|
|
pc_compat_2_0(machine);
|
2014-04-23 15:42:38 +02:00
|
|
|
smbios_defaults = false;
|
2013-12-16 10:11:28 +01:00
|
|
|
gigabyte_align = false;
|
2014-03-06 13:57:09 +01:00
|
|
|
option_rom_has_mr = true;
|
2014-07-28 23:00:42 +02:00
|
|
|
legacy_acpi_table_size = 6414;
|
2015-09-11 17:40:27 +02:00
|
|
|
x86_cpu_change_kvm_default("x2apic", NULL);
|
2013-10-30 13:56:40 +01:00
|
|
|
}
|
|
|
|
|
2014-05-07 16:42:57 +02:00
|
|
|
static void pc_compat_1_6(MachineState *machine)
|
2013-05-13 19:00:23 +02:00
|
|
|
{
|
2014-05-07 16:42:57 +02:00
|
|
|
pc_compat_1_7(machine);
|
2014-03-09 17:42:06 +01:00
|
|
|
rom_file_has_mr = false;
|
i386: ACPI table generation code from seabios
This adds C code for generating ACPI tables at runtime,
imported from seabios git tree
commit 51684b7ced75fb76776e8ee84833fcfb6ecf12dd
Although ACPI tables come from a system BIOS on real hw,
it makes sense that the ACPI tables are coupled with the
virtual machine, since they have to abstract the x86 machine to
the OS's.
This is widely desired as a way to avoid the churn
and proliferation of QEMU-specific interfaces
associated with ACPI tables in bios code.
Notes:
As BIOS can reprogram devices prior to loading
ACPI tables, we pre-format ACPI tables but defer loading
hardware configuration there until tables are loaded.
The code structure was intentionally kept as close
to the seabios original as possible, to simplify
comparison and making sure we didn't lose anything
in translation.
Minor code duplication results, to help ensure there are no functional
regressions, I think it's better to merge it like this and do more code
changes in follow-up patches.
Cross-version compatibility concerns have been addressed:
ACPI tables are exposed to guest as FW_CFG entries.
When running with -M 1.5 and older, this patch disables ACPI
table generation, and doesn't expose ACPI
tables to guest.
As table content is likely to change over time,
the following measures are taken to simplify
cross-version migration:
- All tables besides the RSDP are packed in a single FW CFG entry.
This entry size is currently 23K. We round it up to 64K
to avoid too much churn there.
- Tables are placed in special ROM blob (not mapped into guest memory)
which is automatically migrated together with the guest, same
as BIOS code.
- Offsets where hardware configuration is loaded in ACPI tables
are also migrated, this is in case future ACPI changes make us
rearrange the tables in memory.
This patch reuses some code from SeaBIOS, which was originally under
LGPLv2 and then relicensed to GPLv3 or LGPLv3, in QEMU under GPLv2+. This
relicensing has been acked by all contributors that had contributed to the
code since the v2->v3 relicense. ACKs approving the v2+ relicensing are
listed below. The list might include ACKs from people not holding
copyright on any parts of the reused code, but it's better to err on the
side of caution and include them.
Affected SeaBIOS files (GPLv2+ license headers added)
<http://thread.gmane.org/gmane.comp.bios.coreboot.seabios/5949>:
src/acpi-dsdt-cpu-hotplug.dsl
src/acpi-dsdt-dbug.dsl
src/acpi-dsdt-hpet.dsl
src/acpi-dsdt-isa.dsl
src/acpi-dsdt-pci-crs.dsl
src/acpi.c
src/acpi.h
src/ssdt-misc.dsl
src/ssdt-pcihp.dsl
src/ssdt-proc.dsl
tools/acpi_extract.py
tools/acpi_extract_preprocess.py
Each one of the listed people agreed to the following:
> If you allow the use of your contribution in QEMU under the
> terms of GPLv2 or later as proposed by this patch,
> please respond to this mail including the line:
>
> Acked-by: Name <email address>
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
Acked-by: Jan Kiszka <jan.kiszka@siemens.com>
Acked-by: Jason Baron <jbaron@akamai.com>
Acked-by: David Woodhouse <David.Woodhouse@intel.com>
Acked-by: Gleb Natapov <gleb@redhat.com>
Acked-by: Marcelo Tosatti <mtosatti@redhat.com>
Acked-by: Dave Frodin <dave.frodin@se-eng.com>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Acked-by: Kevin O'Connor <kevin@koconnor.net>
Acked-by: Laszlo Ersek <lersek@redhat.com>
Acked-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Acked-by: Isaku Yamahata <yamahata@valinux.co.jp>
Acked-by: Magnus Christensson <magnus.christensson@intel.com>
Acked-by: Hu Tao <hutao@cn.fujitsu.com>
Acked-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
Tested-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Tested-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2013-07-24 17:56:14 +02:00
|
|
|
has_acpi_build = false;
|
2013-05-13 19:00:23 +02:00
|
|
|
}
|
|
|
|
|
2014-05-07 16:42:57 +02:00
|
|
|
static void pc_compat_1_5(MachineState *machine)
|
2013-08-01 14:39:11 +02:00
|
|
|
{
|
2014-05-07 16:42:57 +02:00
|
|
|
pc_compat_1_6(machine);
|
2013-08-01 14:39:11 +02:00
|
|
|
}
|
|
|
|
|
2014-05-07 16:42:57 +02:00
|
|
|
static void pc_compat_1_4(MachineState *machine)
|
pc: Kill the "use flash device for BIOS unless KVM" misfeature
Use of a flash memory device for the BIOS was added in series "[PATCH
v10 0/8] PC system flash support", commit 4732dca..1b89faf, v1.1.
Flash vs. ROM is a guest-visible difference. Thus, flash use had to
be suppressed for machine types pc-1.0 and older. This was
accomplished by adding a dummy device "pc-sysfw" with property
"rom_only":
* Non-zero rom_only means "use ROM". Default for pc-1.0 and older.
* Zero rom_only means "maybe use flash". Default for newer machines.
Not only is the dummy device ugly, it was also retroactively added to
the older machine types! Fortunately, it's not guest-visible (thus no
immediate guest ABI breakage), and has no vmstate (thus no immediate
migration breakage). Breakage occurs only if the user unwisely
enables flash by setting rom_only to zero. Patch review FAIL #1.
Why "maybe use flash"? Flash didn't (and still doesn't) work with
KVM. Therefore, rom_only=0 really means "use flash, except when KVM
is enabled, use ROM". This is a Bad Idea, because it makes enabling/
disabling KVM guest-visible. Patch review FAIL #2.
Aside: it also precludes migrating between KVM on and off, but that's
not possible for other reasons anyway.
Fix as follows:
1. Change the meaning of rom_only=0 to mean "use flash, no ifs, buts,
or maybes" for pc-i440fx-1.5 and pc-q35-1.5. Don't change anything
for older machines (to remain bug-compatible).
2. Change the default value from 0 to 1 for these machines.
Necessary, because 0 doesn't work with KVM. Once it does, we can flip
the default back to 0.
3. Don't revert the retroactive addition of device "pc-sysfw" to older
machine types. Seems not worth the trouble.
4. Add a TODO comment asking for device "pc-sysfw" to be dropped once
flash works with KVM.
Net effect is that you get a BIOS ROM again even when KVM is disabled,
just like for machines predating the introduction of flash.
To get flash instead, use "--global pc-sysfw.rom_only=0".
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-id: 1365780303-26398-4-git-send-email-armbru@redhat.com
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-04-12 17:25:03 +02:00
|
|
|
{
|
2014-05-07 16:42:57 +02:00
|
|
|
pc_compat_1_5(machine);
|
pc: Kill the "use flash device for BIOS unless KVM" misfeature
Use of a flash memory device for the BIOS was added in series "[PATCH
v10 0/8] PC system flash support", commit 4732dca..1b89faf, v1.1.
Flash vs. ROM is a guest-visible difference. Thus, flash use had to
be suppressed for machine types pc-1.0 and older. This was
accomplished by adding a dummy device "pc-sysfw" with property
"rom_only":
* Non-zero rom_only means "use ROM". Default for pc-1.0 and older.
* Zero rom_only means "maybe use flash". Default for newer machines.
Not only is the dummy device ugly, it was also retroactively added to
the older machine types! Fortunately, it's not guest-visible (thus no
immediate guest ABI breakage), and has no vmstate (thus no immediate
migration breakage). Breakage occurs only if the user unwisely
enables flash by setting rom_only to zero. Patch review FAIL #1.
Why "maybe use flash"? Flash didn't (and still doesn't) work with
KVM. Therefore, rom_only=0 really means "use flash, except when KVM
is enabled, use ROM". This is a Bad Idea, because it makes enabling/
disabling KVM guest-visible. Patch review FAIL #2.
Aside: it also precludes migrating between KVM on and off, but that's
not possible for other reasons anyway.
Fix as follows:
1. Change the meaning of rom_only=0 to mean "use flash, no ifs, buts,
or maybes" for pc-i440fx-1.5 and pc-q35-1.5. Don't change anything
for older machines (to remain bug-compatible).
2. Change the default value from 0 to 1 for these machines.
Necessary, because 0 doesn't work with KVM. Once it does, we can flip
the default back to 0.
3. Don't revert the retroactive addition of device "pc-sysfw" to older
machine types. Seems not worth the trouble.
4. Add a TODO comment asking for device "pc-sysfw" to be dropped once
flash works with KVM.
Net effect is that you get a BIOS ROM again even when KVM is disabled,
just like for machines predating the introduction of flash.
To get flash instead, use "--global pc-sysfw.rom_only=0".
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-id: 1365780303-26398-4-git-send-email-armbru@redhat.com
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2013-04-12 17:25:03 +02:00
|
|
|
}
|
|
|
|
|
2014-05-07 16:42:57 +02:00
|
|
|
static void pc_compat_1_3(MachineState *machine)
|
2013-01-22 21:25:09 +01:00
|
|
|
{
|
2014-05-07 16:42:57 +02:00
|
|
|
pc_compat_1_4(machine);
|
2013-01-22 21:25:09 +01:00
|
|
|
enable_compat_apic_id_mode();
|
2013-08-21 20:14:43 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
/* PC compat function for pc-0.14 to pc-1.2 */
|
2014-05-07 16:42:57 +02:00
|
|
|
static void pc_compat_1_2(MachineState *machine)
|
2013-08-21 20:14:43 +02:00
|
|
|
{
|
2014-05-07 16:42:57 +02:00
|
|
|
pc_compat_1_3(machine);
|
2015-09-11 17:40:27 +02:00
|
|
|
x86_cpu_change_kvm_default("kvm-pv-eoi", NULL);
|
2013-08-21 20:14:43 +02:00
|
|
|
}
|
|
|
|
|
2015-05-15 19:18:59 +02:00
|
|
|
/* PC compat function for pc-0.10 to pc-0.13 */
|
|
|
|
static void pc_compat_0_13(MachineState *machine)
|
|
|
|
{
|
|
|
|
pc_compat_1_2(machine);
|
|
|
|
kvmclock_enabled = false;
|
|
|
|
}
|
|
|
|
|
2014-05-07 16:42:57 +02:00
|
|
|
static void pc_init_isa(MachineState *machine)
|
2010-05-14 09:29:15 +02:00
|
|
|
{
|
2015-05-15 19:18:59 +02:00
|
|
|
pci_enabled = false;
|
2013-11-04 11:42:46 +01:00
|
|
|
has_acpi_build = false;
|
2014-04-23 15:42:38 +02:00
|
|
|
smbios_defaults = false;
|
2014-06-25 22:19:07 +02:00
|
|
|
gigabyte_align = false;
|
|
|
|
smbios_legacy_mode = true;
|
|
|
|
has_reserved_memory = false;
|
|
|
|
option_rom_has_mr = true;
|
|
|
|
rom_file_has_mr = false;
|
2014-05-07 16:42:57 +02:00
|
|
|
if (!machine->cpu_model) {
|
|
|
|
machine->cpu_model = "486";
|
2013-08-21 20:14:40 +02:00
|
|
|
}
|
2015-09-11 17:40:27 +02:00
|
|
|
x86_cpu_change_kvm_default("kvm-pv-eoi", NULL);
|
2013-01-22 21:25:09 +01:00
|
|
|
enable_compat_apic_id_mode();
|
2015-07-15 07:37:42 +02:00
|
|
|
pc_init1(machine, TYPE_I440FX_PCI_HOST_BRIDGE, TYPE_I440FX_PCI_DEVICE);
|
2010-05-14 09:29:15 +02:00
|
|
|
}
|
|
|
|
|
2010-06-30 13:58:34 +02:00
|
|
|
#ifdef CONFIG_XEN
|
2015-07-15 07:37:49 +02:00
|
|
|
static void pc_xen_hvm_init_pci(MachineState *machine)
|
|
|
|
{
|
|
|
|
const char *pci_type = has_igd_gfx_passthru ?
|
|
|
|
TYPE_IGD_PASSTHROUGH_I440FX_PCI_DEVICE : TYPE_I440FX_PCI_DEVICE;
|
|
|
|
|
|
|
|
pc_init1(machine,
|
|
|
|
TYPE_I440FX_PCI_HOST_BRIDGE,
|
|
|
|
pci_type);
|
|
|
|
}
|
|
|
|
|
2014-05-07 16:42:57 +02:00
|
|
|
static void pc_xen_hvm_init(MachineState *machine)
|
2010-06-30 13:58:34 +02:00
|
|
|
{
|
2013-06-25 13:46:44 +02:00
|
|
|
PCIBus *bus;
|
|
|
|
|
2015-09-28 22:01:23 +02:00
|
|
|
if (!xen_enabled()) {
|
|
|
|
error_report("xenfv machine requires the xen accelerator");
|
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
|
2015-07-15 07:37:49 +02:00
|
|
|
pc_xen_hvm_init_pci(machine);
|
2013-06-25 13:46:44 +02:00
|
|
|
|
2013-06-06 10:48:47 +02:00
|
|
|
bus = pci_find_primary_bus();
|
2013-06-25 13:46:44 +02:00
|
|
|
if (bus != NULL) {
|
|
|
|
pci_create_simple(bus, -1, "xen-platform");
|
|
|
|
}
|
2010-06-30 13:58:34 +02:00
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
#define DEFINE_I440FX_MACHINE(suffix, name, compatfn, optionfn) \
|
|
|
|
static void pc_init_##suffix(MachineState *machine) \
|
|
|
|
{ \
|
|
|
|
void (*compat)(MachineState *m) = (compatfn); \
|
|
|
|
if (compat) { \
|
|
|
|
compat(machine); \
|
|
|
|
} \
|
2015-07-15 07:37:42 +02:00
|
|
|
pc_init1(machine, TYPE_I440FX_PCI_HOST_BRIDGE, \
|
|
|
|
TYPE_I440FX_PCI_DEVICE); \
|
2015-05-15 19:19:01 +02:00
|
|
|
} \
|
|
|
|
DEFINE_PC_MACHINE(suffix, name, pc_init_##suffix, optionfn)
|
2015-05-15 19:18:54 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
m->family = "pc_piix";
|
|
|
|
m->desc = "Standard PC (i440FX + PIIX, 1996)";
|
|
|
|
m->hot_add_cpu = pc_hot_add_cpu;
|
2015-09-11 22:14:24 +02:00
|
|
|
m->default_machine_opts = "firmware=bios-256k.bin";
|
|
|
|
m->default_display = "std";
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
|
|
|
|
2015-09-11 22:14:25 +02:00
|
|
|
static void pc_i440fx_2_5_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_machine_options(m);
|
|
|
|
m->alias = "pc";
|
|
|
|
m->is_default = 1;
|
|
|
|
}
|
2013-12-02 12:47:29 +01:00
|
|
|
|
2015-09-11 22:14:25 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v2_5, "pc-i440fx-2.5", NULL,
|
|
|
|
pc_i440fx_2_5_machine_options);
|
|
|
|
|
|
|
|
|
|
|
|
static void pc_i440fx_2_4_machine_options(MachineClass *m)
|
|
|
|
{
|
|
|
|
PCMachineClass *pcmc = PC_MACHINE_CLASS(m);
|
|
|
|
pc_i440fx_2_5_machine_options(m);
|
|
|
|
m->alias = NULL;
|
|
|
|
m->is_default = 0;
|
|
|
|
pcmc->broken_reserved_end = true;
|
2015-09-29 16:53:29 +02:00
|
|
|
pcmc->inter_dimm_gap = false;
|
2015-09-11 22:14:25 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_2_4);
|
|
|
|
}
|
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v2_4, "pc-i440fx-2.4", NULL,
|
|
|
|
pc_i440fx_2_4_machine_options)
|
2015-04-23 08:21:35 +02:00
|
|
|
|
2014-07-30 09:02:00 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_2_3_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
2015-06-23 19:00:51 +02:00
|
|
|
pc_i440fx_2_4_machine_options(m);
|
2015-05-15 19:18:54 +02:00
|
|
|
m->alias = NULL;
|
|
|
|
m->is_default = 0;
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_2_3);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
2015-04-23 08:21:35 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v2_3, "pc-i440fx-2.3", pc_compat_2_3,
|
|
|
|
pc_i440fx_2_3_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2015-04-23 08:21:35 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_2_2_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_2_3_machine_options(m);
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_2_2);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
2014-12-05 10:51:42 +01:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v2_2, "pc-i440fx-2.2", pc_compat_2_2,
|
|
|
|
pc_i440fx_2_2_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2014-12-05 10:51:42 +01:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_2_1_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_2_2_machine_options(m);
|
|
|
|
m->default_display = NULL;
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_2_1);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
2014-07-30 09:02:00 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v2_1, "pc-i440fx-2.1", pc_compat_2_1,
|
|
|
|
pc_i440fx_2_1_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2013-12-02 12:47:29 +01:00
|
|
|
|
2015-05-15 19:18:54 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_2_0_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_2_1_machine_options(m);
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_2_0);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
2014-04-24 12:14:53 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v2_0, "pc-i440fx-2.0", pc_compat_2_0,
|
|
|
|
pc_i440fx_2_0_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2014-04-24 12:14:53 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_1_7_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_2_0_machine_options(m);
|
|
|
|
m->default_machine_opts = NULL;
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_1_7);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
2013-12-02 12:47:29 +01:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v1_7, "pc-i440fx-1.7", pc_compat_1_7,
|
|
|
|
pc_i440fx_1_7_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
e1000: add interrupt mitigation support
This patch partially implements the e1000 interrupt mitigation mechanisms.
Using a single QEMUTimer, it emulates the ITR register (which is the newer
mitigation register, recommended by Intel) and approximately emulates
RADV and TADV registers. TIDV and RDTR register functionalities are not
emulated (RDTR is only used to validate RADV, according to the e1000 specs).
RADV, TADV, TIDV and RDTR registers make up the older e1000 mitigation
mechanism and would need a timer each to be completely emulated. However,
a single timer has been used in order to reach a good compromise between
emulation accuracy and simplicity/efficiency.
The implemented mechanism can be enabled/disabled specifying the command
line e1000-specific boolean parameter "mitigation", e.g.
qemu-system-x86_64 -device e1000,mitigation=on,... ...
For more information, see the Software developer's manual at
http://download.intel.com/design/network/manuals/8254x_GBe_SDM.pdf.
Interrupt mitigation boosts performance when the guest suffers from
an high interrupt rate (i.e. receiving short UDP packets at high packet
rate). For some numerical results see the following link
http://info.iet.unipi.it/~luigi/papers/20130520-rizzo-vm.pdf
Signed-off-by: Vincenzo Maffione <v.maffione@gmail.com>
Reviewed-by: Andreas Färber <afaerber@suse.de> (for pc-* machines)
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-08-02 18:30:52 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_1_6_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_1_7_machine_options(m);
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_1_6);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
2013-08-27 08:48:06 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v1_6, "pc-i440fx-1.6", pc_compat_1_6,
|
|
|
|
pc_i440fx_1_6_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2010-05-14 09:29:15 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_1_5_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_1_6_machine_options(m);
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_1_5);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
pc: Define MACHINE_OPTIONS macros consistently for all machines
Define a MACHINE_OPTIONS macro for each PC machine, and move every field
inside the QEMUMachine structs to the macros, except for name, init, and
compat_props.
This also ensures that all MACHINE_OPTIONS inherit the fields from the
next version, so their definitions carry only the changes that exist
between one version and the next one.
Comments about specific cases:
pc-*-2.1:
Existing PC_*_2_1_MACHINE_OPTIONS macros were defined as:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin"
PC_*_2_2_MACHINE_OPTIONS is:
PC_*_2_3_MACHINE_OPTIONS
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std"
The only difference between 2_1 and 2_2 is .default_display, that's why
we didn't reuse PC_*_2_2_MACHINE_OPTIONS. The good news is that having
multiple initializers for a field is allowed by C99, and the last
initializer overrides the previous ones.
So we can reuse the 2_2 macro in 2_1 and define PC_*_2_1_MACHINE_OPTIONS
as:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
pc-*-1.7:
PC_*_1_7_MACHINE_OPTIONS was defined as:
PC_*_MACHINE_OPTIONS
PC_*_2_0_MACHINE_OPTIONS is defined as:
PC_*_2_1_MACHINE_OPTIONS
which is expanded to:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_2_3_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std",
.default_display = NULL /* overrides the previous line */
So, the only difference between PC_*_1_7_MACHINE_OPTIONS and
PC_*_2_0_MACHINE_OPTIONS is .default_machine_opts (as .default_display
is not explicitly set by PC_*_MACHINE_OPTIONS so it is NULL).
So we can keep the macro reuse pattern and define
PC_*_2_0_MACHINE_OPTIONS as:
PC_*_2_0_MACHINE_OPTIONS,
.default_machine_opts = NULL
pc-*-2.4 (alias and is_default fields):
Set alias and is_default fields inside the 2.4 MACHINE_OPTIONS macro,
and clear it in the 2.3 macro (that reuses the 2.4 macro).
hw_machine:
As all the machines older than v1.0 set hw_version explicitly, we can
safely move the field to the MACHINE_OPTIONS macros without affecting
the other versions that reuse them.
init function:
Some machines had the init function set inside the MACHINE_OPTIONS
macro. Move it to the QEMUMachine declaration, to keep it consistent
with the other machines.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2015-05-15 19:18:52 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v1_5, "pc-i440fx-1.5", pc_compat_1_5,
|
|
|
|
pc_i440fx_1_5_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2013-05-27 22:23:53 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_1_4_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_1_5_machine_options(m);
|
|
|
|
m->hot_add_cpu = NULL;
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_1_4);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
2013-08-27 08:48:06 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v1_4, "pc-i440fx-1.4", pc_compat_1_4,
|
|
|
|
pc_i440fx_1_4_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2013-02-08 14:06:15 +01:00
|
|
|
|
2012-11-17 12:47:18 +01:00
|
|
|
#define PC_COMPAT_1_3 \
|
2015-05-14 20:53:00 +02:00
|
|
|
PC_COMPAT_1_4 \
|
2012-11-17 12:47:18 +01:00
|
|
|
{\
|
|
|
|
.driver = "usb-tablet",\
|
|
|
|
.property = "usb_version",\
|
|
|
|
.value = stringify(1),\
|
2013-01-22 16:44:45 +01:00
|
|
|
},{\
|
|
|
|
.driver = "virtio-net-pci",\
|
|
|
|
.property = "ctrl_mac_addr",\
|
|
|
|
.value = "off", \
|
2013-01-30 12:12:41 +01:00
|
|
|
},{ \
|
|
|
|
.driver = "virtio-net-pci", \
|
|
|
|
.property = "mq", \
|
|
|
|
.value = "off", \
|
2013-02-14 18:11:27 +01:00
|
|
|
}, {\
|
|
|
|
.driver = "e1000",\
|
|
|
|
.property = "autonegotiation",\
|
|
|
|
.value = "off",\
|
2015-05-14 20:53:00 +02:00
|
|
|
},
|
2012-11-17 12:47:18 +01:00
|
|
|
|
2015-05-15 19:18:54 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_1_3_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_1_4_machine_options(m);
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_1_3);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
pc: Define MACHINE_OPTIONS macros consistently for all machines
Define a MACHINE_OPTIONS macro for each PC machine, and move every field
inside the QEMUMachine structs to the macros, except for name, init, and
compat_props.
This also ensures that all MACHINE_OPTIONS inherit the fields from the
next version, so their definitions carry only the changes that exist
between one version and the next one.
Comments about specific cases:
pc-*-2.1:
Existing PC_*_2_1_MACHINE_OPTIONS macros were defined as:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin"
PC_*_2_2_MACHINE_OPTIONS is:
PC_*_2_3_MACHINE_OPTIONS
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std"
The only difference between 2_1 and 2_2 is .default_display, that's why
we didn't reuse PC_*_2_2_MACHINE_OPTIONS. The good news is that having
multiple initializers for a field is allowed by C99, and the last
initializer overrides the previous ones.
So we can reuse the 2_2 macro in 2_1 and define PC_*_2_1_MACHINE_OPTIONS
as:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
pc-*-1.7:
PC_*_1_7_MACHINE_OPTIONS was defined as:
PC_*_MACHINE_OPTIONS
PC_*_2_0_MACHINE_OPTIONS is defined as:
PC_*_2_1_MACHINE_OPTIONS
which is expanded to:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_2_3_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std",
.default_display = NULL /* overrides the previous line */
So, the only difference between PC_*_1_7_MACHINE_OPTIONS and
PC_*_2_0_MACHINE_OPTIONS is .default_machine_opts (as .default_display
is not explicitly set by PC_*_MACHINE_OPTIONS so it is NULL).
So we can keep the macro reuse pattern and define
PC_*_2_0_MACHINE_OPTIONS as:
PC_*_2_0_MACHINE_OPTIONS,
.default_machine_opts = NULL
pc-*-2.4 (alias and is_default fields):
Set alias and is_default fields inside the 2.4 MACHINE_OPTIONS macro,
and clear it in the 2.3 macro (that reuses the 2.4 macro).
hw_machine:
As all the machines older than v1.0 set hw_version explicitly, we can
safely move the field to the MACHINE_OPTIONS macros without affecting
the other versions that reuse them.
init function:
Some machines had the init function set inside the MACHINE_OPTIONS
macro. Move it to the QEMUMachine declaration, to keep it consistent
with the other machines.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2015-05-15 19:18:52 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v1_3, "pc-1.3", pc_compat_1_3,
|
|
|
|
pc_i440fx_1_3_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2012-12-04 14:39:16 +01:00
|
|
|
|
2012-09-13 11:08:01 +02:00
|
|
|
#define PC_COMPAT_1_2 \
|
2015-05-14 20:53:00 +02:00
|
|
|
PC_COMPAT_1_3 \
|
2012-09-13 11:08:01 +02:00
|
|
|
{\
|
|
|
|
.driver = "nec-usb-xhci",\
|
|
|
|
.property = "msi",\
|
|
|
|
.value = "off",\
|
|
|
|
},{\
|
|
|
|
.driver = "nec-usb-xhci",\
|
|
|
|
.property = "msix",\
|
|
|
|
.value = "off",\
|
2012-09-13 11:08:02 +02:00
|
|
|
},{\
|
|
|
|
.driver = "ivshmem",\
|
|
|
|
.property = "use64",\
|
|
|
|
.value = "0",\
|
2012-10-08 10:05:22 +02:00
|
|
|
},{\
|
|
|
|
.driver = "qxl",\
|
|
|
|
.property = "revision",\
|
|
|
|
.value = stringify(3),\
|
|
|
|
},{\
|
|
|
|
.driver = "qxl-vga",\
|
|
|
|
.property = "revision",\
|
|
|
|
.value = stringify(3),\
|
2012-10-15 08:02:55 +02:00
|
|
|
},{\
|
|
|
|
.driver = "VGA",\
|
|
|
|
.property = "mmio",\
|
|
|
|
.value = "off",\
|
2015-05-14 20:53:00 +02:00
|
|
|
},
|
2012-09-13 11:08:01 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_1_2_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_1_3_machine_options(m);
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_1_2);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
2013-08-27 08:48:06 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v1_2, "pc-1.2", pc_compat_1_2,
|
|
|
|
pc_i440fx_1_2_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2012-09-13 11:08:00 +02:00
|
|
|
|
2012-06-11 10:42:53 +02:00
|
|
|
#define PC_COMPAT_1_1 \
|
2015-05-14 20:53:00 +02:00
|
|
|
PC_COMPAT_1_2 \
|
2012-06-11 10:42:53 +02:00
|
|
|
{\
|
2012-08-20 15:23:28 +02:00
|
|
|
.driver = "virtio-scsi-pci",\
|
|
|
|
.property = "hotplug",\
|
|
|
|
.value = "off",\
|
|
|
|
},{\
|
|
|
|
.driver = "virtio-scsi-pci",\
|
|
|
|
.property = "param_change",\
|
|
|
|
.value = "off",\
|
|
|
|
},{\
|
2012-06-11 10:42:53 +02:00
|
|
|
.driver = "VGA",\
|
|
|
|
.property = "vgamem_mb",\
|
|
|
|
.value = stringify(8),\
|
|
|
|
},{\
|
|
|
|
.driver = "vmware-svga",\
|
|
|
|
.property = "vgamem_mb",\
|
|
|
|
.value = stringify(8),\
|
|
|
|
},{\
|
|
|
|
.driver = "qxl-vga",\
|
|
|
|
.property = "vgamem_mb",\
|
|
|
|
.value = stringify(8),\
|
|
|
|
},{\
|
|
|
|
.driver = "qxl",\
|
|
|
|
.property = "vgamem_mb",\
|
|
|
|
.value = stringify(8),\
|
2012-08-21 15:40:49 +02:00
|
|
|
},{\
|
|
|
|
.driver = "virtio-blk-pci",\
|
|
|
|
.property = "config-wce",\
|
|
|
|
.value = "off",\
|
2015-05-14 20:53:00 +02:00
|
|
|
},
|
2012-06-11 10:42:53 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_1_1_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_1_2_machine_options(m);
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_1_1);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
pc: Define MACHINE_OPTIONS macros consistently for all machines
Define a MACHINE_OPTIONS macro for each PC machine, and move every field
inside the QEMUMachine structs to the macros, except for name, init, and
compat_props.
This also ensures that all MACHINE_OPTIONS inherit the fields from the
next version, so their definitions carry only the changes that exist
between one version and the next one.
Comments about specific cases:
pc-*-2.1:
Existing PC_*_2_1_MACHINE_OPTIONS macros were defined as:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin"
PC_*_2_2_MACHINE_OPTIONS is:
PC_*_2_3_MACHINE_OPTIONS
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std"
The only difference between 2_1 and 2_2 is .default_display, that's why
we didn't reuse PC_*_2_2_MACHINE_OPTIONS. The good news is that having
multiple initializers for a field is allowed by C99, and the last
initializer overrides the previous ones.
So we can reuse the 2_2 macro in 2_1 and define PC_*_2_1_MACHINE_OPTIONS
as:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
pc-*-1.7:
PC_*_1_7_MACHINE_OPTIONS was defined as:
PC_*_MACHINE_OPTIONS
PC_*_2_0_MACHINE_OPTIONS is defined as:
PC_*_2_1_MACHINE_OPTIONS
which is expanded to:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_2_3_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std",
.default_display = NULL /* overrides the previous line */
So, the only difference between PC_*_1_7_MACHINE_OPTIONS and
PC_*_2_0_MACHINE_OPTIONS is .default_machine_opts (as .default_display
is not explicitly set by PC_*_MACHINE_OPTIONS so it is NULL).
So we can keep the macro reuse pattern and define
PC_*_2_0_MACHINE_OPTIONS as:
PC_*_2_0_MACHINE_OPTIONS,
.default_machine_opts = NULL
pc-*-2.4 (alias and is_default fields):
Set alias and is_default fields inside the 2.4 MACHINE_OPTIONS macro,
and clear it in the 2.3 macro (that reuses the 2.4 macro).
hw_machine:
As all the machines older than v1.0 set hw_version explicitly, we can
safely move the field to the MACHINE_OPTIONS macros without affecting
the other versions that reuse them.
init function:
Some machines had the init function set inside the MACHINE_OPTIONS
macro. Move it to the QEMUMachine declaration, to keep it consistent
with the other machines.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2015-05-15 19:18:52 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v1_1, "pc-1.1", pc_compat_1_2,
|
|
|
|
pc_i440fx_1_1_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2012-06-11 10:38:22 +02:00
|
|
|
|
2012-03-26 11:26:16 +02:00
|
|
|
#define PC_COMPAT_1_0 \
|
2015-05-14 20:53:00 +02:00
|
|
|
PC_COMPAT_1_1 \
|
2012-03-26 11:26:16 +02:00
|
|
|
{\
|
2013-04-27 22:18:38 +02:00
|
|
|
.driver = TYPE_ISA_FDC,\
|
2012-03-26 11:26:16 +02:00
|
|
|
.property = "check_media_rate",\
|
|
|
|
.value = "off",\
|
2012-04-03 16:24:11 +02:00
|
|
|
}, {\
|
|
|
|
.driver = "virtio-balloon-pci",\
|
|
|
|
.property = "class",\
|
|
|
|
.value = stringify(PCI_CLASS_MEMORY_RAM),\
|
2012-04-16 19:56:28 +02:00
|
|
|
},{\
|
2014-07-30 09:01:59 +02:00
|
|
|
.driver = "apic-common",\
|
2012-04-16 19:56:28 +02:00
|
|
|
.property = "vapic",\
|
|
|
|
.value = "off",\
|
2011-08-22 09:09:51 +02:00
|
|
|
},{\
|
2012-03-28 18:12:47 +02:00
|
|
|
.driver = TYPE_USB_DEVICE,\
|
2011-08-22 09:09:51 +02:00
|
|
|
.property = "full-path",\
|
|
|
|
.value = "no",\
|
2015-05-14 20:53:00 +02:00
|
|
|
},
|
2012-03-26 11:26:16 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_1_0_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_1_1_machine_options(m);
|
|
|
|
m->hw_version = "1.0";
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_1_0);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
pc: Define MACHINE_OPTIONS macros consistently for all machines
Define a MACHINE_OPTIONS macro for each PC machine, and move every field
inside the QEMUMachine structs to the macros, except for name, init, and
compat_props.
This also ensures that all MACHINE_OPTIONS inherit the fields from the
next version, so their definitions carry only the changes that exist
between one version and the next one.
Comments about specific cases:
pc-*-2.1:
Existing PC_*_2_1_MACHINE_OPTIONS macros were defined as:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin"
PC_*_2_2_MACHINE_OPTIONS is:
PC_*_2_3_MACHINE_OPTIONS
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std"
The only difference between 2_1 and 2_2 is .default_display, that's why
we didn't reuse PC_*_2_2_MACHINE_OPTIONS. The good news is that having
multiple initializers for a field is allowed by C99, and the last
initializer overrides the previous ones.
So we can reuse the 2_2 macro in 2_1 and define PC_*_2_1_MACHINE_OPTIONS
as:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
pc-*-1.7:
PC_*_1_7_MACHINE_OPTIONS was defined as:
PC_*_MACHINE_OPTIONS
PC_*_2_0_MACHINE_OPTIONS is defined as:
PC_*_2_1_MACHINE_OPTIONS
which is expanded to:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_2_3_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std",
.default_display = NULL /* overrides the previous line */
So, the only difference between PC_*_1_7_MACHINE_OPTIONS and
PC_*_2_0_MACHINE_OPTIONS is .default_machine_opts (as .default_display
is not explicitly set by PC_*_MACHINE_OPTIONS so it is NULL).
So we can keep the macro reuse pattern and define
PC_*_2_0_MACHINE_OPTIONS as:
PC_*_2_0_MACHINE_OPTIONS,
.default_machine_opts = NULL
pc-*-2.4 (alias and is_default fields):
Set alias and is_default fields inside the 2.4 MACHINE_OPTIONS macro,
and clear it in the 2.3 macro (that reuses the 2.4 macro).
hw_machine:
As all the machines older than v1.0 set hw_version explicitly, we can
safely move the field to the MACHINE_OPTIONS macros without affecting
the other versions that reuse them.
init function:
Some machines had the init function set inside the MACHINE_OPTIONS
macro. Move it to the QEMUMachine declaration, to keep it consistent
with the other machines.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2015-05-15 19:18:52 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v1_0, "pc-1.0", pc_compat_1_2,
|
|
|
|
pc_i440fx_1_0_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2012-02-22 08:18:55 +01:00
|
|
|
|
2012-03-26 11:26:16 +02:00
|
|
|
#define PC_COMPAT_0_15 \
|
|
|
|
PC_COMPAT_1_0
|
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_0_15_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_1_0_machine_options(m);
|
|
|
|
m->hw_version = "0.15";
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_0_15);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
pc: Define MACHINE_OPTIONS macros consistently for all machines
Define a MACHINE_OPTIONS macro for each PC machine, and move every field
inside the QEMUMachine structs to the macros, except for name, init, and
compat_props.
This also ensures that all MACHINE_OPTIONS inherit the fields from the
next version, so their definitions carry only the changes that exist
between one version and the next one.
Comments about specific cases:
pc-*-2.1:
Existing PC_*_2_1_MACHINE_OPTIONS macros were defined as:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin"
PC_*_2_2_MACHINE_OPTIONS is:
PC_*_2_3_MACHINE_OPTIONS
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std"
The only difference between 2_1 and 2_2 is .default_display, that's why
we didn't reuse PC_*_2_2_MACHINE_OPTIONS. The good news is that having
multiple initializers for a field is allowed by C99, and the last
initializer overrides the previous ones.
So we can reuse the 2_2 macro in 2_1 and define PC_*_2_1_MACHINE_OPTIONS
as:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
pc-*-1.7:
PC_*_1_7_MACHINE_OPTIONS was defined as:
PC_*_MACHINE_OPTIONS
PC_*_2_0_MACHINE_OPTIONS is defined as:
PC_*_2_1_MACHINE_OPTIONS
which is expanded to:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_2_3_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std",
.default_display = NULL /* overrides the previous line */
So, the only difference between PC_*_1_7_MACHINE_OPTIONS and
PC_*_2_0_MACHINE_OPTIONS is .default_machine_opts (as .default_display
is not explicitly set by PC_*_MACHINE_OPTIONS so it is NULL).
So we can keep the macro reuse pattern and define
PC_*_2_0_MACHINE_OPTIONS as:
PC_*_2_0_MACHINE_OPTIONS,
.default_machine_opts = NULL
pc-*-2.4 (alias and is_default fields):
Set alias and is_default fields inside the 2.4 MACHINE_OPTIONS macro,
and clear it in the 2.3 macro (that reuses the 2.4 macro).
hw_machine:
As all the machines older than v1.0 set hw_version explicitly, we can
safely move the field to the MACHINE_OPTIONS macros without affecting
the other versions that reuse them.
init function:
Some machines had the init function set inside the MACHINE_OPTIONS
macro. Move it to the QEMUMachine declaration, to keep it consistent
with the other machines.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2015-05-15 19:18:52 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v0_15, "pc-0.15", pc_compat_1_2,
|
|
|
|
pc_i440fx_0_15_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2011-12-18 19:59:12 +01:00
|
|
|
|
2012-03-26 11:26:16 +02:00
|
|
|
#define PC_COMPAT_0_14 \
|
2015-05-14 20:53:00 +02:00
|
|
|
PC_COMPAT_0_15 \
|
2012-03-26 11:26:16 +02:00
|
|
|
{\
|
|
|
|
.driver = "virtio-blk-pci",\
|
|
|
|
.property = "event_idx",\
|
|
|
|
.value = "off",\
|
|
|
|
},{\
|
|
|
|
.driver = "virtio-serial-pci",\
|
|
|
|
.property = "event_idx",\
|
|
|
|
.value = "off",\
|
|
|
|
},{\
|
|
|
|
.driver = "virtio-net-pci",\
|
|
|
|
.property = "event_idx",\
|
|
|
|
.value = "off",\
|
|
|
|
},{\
|
|
|
|
.driver = "virtio-balloon-pci",\
|
|
|
|
.property = "event_idx",\
|
|
|
|
.value = "off",\
|
2015-05-14 20:53:06 +02:00
|
|
|
},{\
|
|
|
|
.driver = "qxl",\
|
|
|
|
.property = "revision",\
|
|
|
|
.value = stringify(2),\
|
|
|
|
},{\
|
|
|
|
.driver = "qxl-vga",\
|
|
|
|
.property = "revision",\
|
|
|
|
.value = stringify(2),\
|
2015-05-14 20:53:00 +02:00
|
|
|
},
|
2012-03-26 11:26:16 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_0_14_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_0_15_machine_options(m);
|
|
|
|
m->hw_version = "0.14";
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_0_14);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
pc: Define MACHINE_OPTIONS macros consistently for all machines
Define a MACHINE_OPTIONS macro for each PC machine, and move every field
inside the QEMUMachine structs to the macros, except for name, init, and
compat_props.
This also ensures that all MACHINE_OPTIONS inherit the fields from the
next version, so their definitions carry only the changes that exist
between one version and the next one.
Comments about specific cases:
pc-*-2.1:
Existing PC_*_2_1_MACHINE_OPTIONS macros were defined as:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin"
PC_*_2_2_MACHINE_OPTIONS is:
PC_*_2_3_MACHINE_OPTIONS
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std"
The only difference between 2_1 and 2_2 is .default_display, that's why
we didn't reuse PC_*_2_2_MACHINE_OPTIONS. The good news is that having
multiple initializers for a field is allowed by C99, and the last
initializer overrides the previous ones.
So we can reuse the 2_2 macro in 2_1 and define PC_*_2_1_MACHINE_OPTIONS
as:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
pc-*-1.7:
PC_*_1_7_MACHINE_OPTIONS was defined as:
PC_*_MACHINE_OPTIONS
PC_*_2_0_MACHINE_OPTIONS is defined as:
PC_*_2_1_MACHINE_OPTIONS
which is expanded to:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_2_3_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std",
.default_display = NULL /* overrides the previous line */
So, the only difference between PC_*_1_7_MACHINE_OPTIONS and
PC_*_2_0_MACHINE_OPTIONS is .default_machine_opts (as .default_display
is not explicitly set by PC_*_MACHINE_OPTIONS so it is NULL).
So we can keep the macro reuse pattern and define
PC_*_2_0_MACHINE_OPTIONS as:
PC_*_2_0_MACHINE_OPTIONS,
.default_machine_opts = NULL
pc-*-2.4 (alias and is_default fields):
Set alias and is_default fields inside the 2.4 MACHINE_OPTIONS macro,
and clear it in the 2.3 macro (that reuses the 2.4 macro).
hw_machine:
As all the machines older than v1.0 set hw_version explicitly, we can
safely move the field to the MACHINE_OPTIONS macros without affecting
the other versions that reuse them.
init function:
Some machines had the init function set inside the MACHINE_OPTIONS
macro. Move it to the QEMUMachine declaration, to keep it consistent
with the other machines.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2015-05-15 19:18:52 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v0_14, "pc-0.14", pc_compat_1_2,
|
|
|
|
pc_i440fx_0_14_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2011-11-07 16:33:08 +01:00
|
|
|
|
2012-03-26 11:26:16 +02:00
|
|
|
#define PC_COMPAT_0_13 \
|
2015-05-14 20:53:00 +02:00
|
|
|
PC_COMPAT_0_14 \
|
2012-03-26 11:26:16 +02:00
|
|
|
{\
|
2012-03-28 18:12:47 +02:00
|
|
|
.driver = TYPE_PCI_DEVICE,\
|
2012-03-26 11:26:16 +02:00
|
|
|
.property = "command_serr_enable",\
|
|
|
|
.value = "off",\
|
|
|
|
},{\
|
|
|
|
.driver = "AC97",\
|
|
|
|
.property = "use_broken_id",\
|
|
|
|
.value = stringify(1),\
|
2015-05-14 20:53:08 +02:00
|
|
|
},{\
|
|
|
|
.driver = "virtio-9p-pci",\
|
|
|
|
.property = "vectors",\
|
|
|
|
.value = stringify(0),\
|
2015-05-14 20:53:09 +02:00
|
|
|
},{\
|
|
|
|
.driver = "VGA",\
|
|
|
|
.property = "rombar",\
|
|
|
|
.value = stringify(0),\
|
|
|
|
},{\
|
|
|
|
.driver = "vmware-svga",\
|
|
|
|
.property = "rombar",\
|
|
|
|
.value = stringify(0),\
|
2015-05-14 20:53:00 +02:00
|
|
|
},
|
2012-03-26 11:26:16 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_0_13_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_0_14_machine_options(m);
|
|
|
|
m->hw_version = "0.13";
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_0_13);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
2013-08-27 08:48:06 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v0_13, "pc-0.13", pc_compat_0_13,
|
|
|
|
pc_i440fx_0_13_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2010-11-11 12:59:25 +01:00
|
|
|
|
2012-03-26 11:26:16 +02:00
|
|
|
#define PC_COMPAT_0_12 \
|
2015-05-14 20:53:00 +02:00
|
|
|
PC_COMPAT_0_13 \
|
2012-03-26 11:26:16 +02:00
|
|
|
{\
|
|
|
|
.driver = "virtio-serial-pci",\
|
|
|
|
.property = "max_ports",\
|
|
|
|
.value = stringify(1),\
|
|
|
|
},{\
|
|
|
|
.driver = "virtio-serial-pci",\
|
|
|
|
.property = "vectors",\
|
|
|
|
.value = stringify(0),\
|
2013-06-12 13:08:45 +02:00
|
|
|
},{\
|
|
|
|
.driver = "usb-mouse",\
|
|
|
|
.property = "serial",\
|
|
|
|
.value = "1",\
|
|
|
|
},{\
|
|
|
|
.driver = "usb-tablet",\
|
|
|
|
.property = "serial",\
|
|
|
|
.value = "1",\
|
|
|
|
},{\
|
|
|
|
.driver = "usb-kbd",\
|
|
|
|
.property = "serial",\
|
|
|
|
.value = "1",\
|
2015-05-14 20:53:00 +02:00
|
|
|
},
|
2012-03-26 11:26:16 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_0_12_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_0_13_machine_options(m);
|
|
|
|
m->hw_version = "0.12";
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_0_12);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
pc: Define MACHINE_OPTIONS macros consistently for all machines
Define a MACHINE_OPTIONS macro for each PC machine, and move every field
inside the QEMUMachine structs to the macros, except for name, init, and
compat_props.
This also ensures that all MACHINE_OPTIONS inherit the fields from the
next version, so their definitions carry only the changes that exist
between one version and the next one.
Comments about specific cases:
pc-*-2.1:
Existing PC_*_2_1_MACHINE_OPTIONS macros were defined as:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin"
PC_*_2_2_MACHINE_OPTIONS is:
PC_*_2_3_MACHINE_OPTIONS
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std"
The only difference between 2_1 and 2_2 is .default_display, that's why
we didn't reuse PC_*_2_2_MACHINE_OPTIONS. The good news is that having
multiple initializers for a field is allowed by C99, and the last
initializer overrides the previous ones.
So we can reuse the 2_2 macro in 2_1 and define PC_*_2_1_MACHINE_OPTIONS
as:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
pc-*-1.7:
PC_*_1_7_MACHINE_OPTIONS was defined as:
PC_*_MACHINE_OPTIONS
PC_*_2_0_MACHINE_OPTIONS is defined as:
PC_*_2_1_MACHINE_OPTIONS
which is expanded to:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_2_3_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std",
.default_display = NULL /* overrides the previous line */
So, the only difference between PC_*_1_7_MACHINE_OPTIONS and
PC_*_2_0_MACHINE_OPTIONS is .default_machine_opts (as .default_display
is not explicitly set by PC_*_MACHINE_OPTIONS so it is NULL).
So we can keep the macro reuse pattern and define
PC_*_2_0_MACHINE_OPTIONS as:
PC_*_2_0_MACHINE_OPTIONS,
.default_machine_opts = NULL
pc-*-2.4 (alias and is_default fields):
Set alias and is_default fields inside the 2.4 MACHINE_OPTIONS macro,
and clear it in the 2.3 macro (that reuses the 2.4 macro).
hw_machine:
As all the machines older than v1.0 set hw_version explicitly, we can
safely move the field to the MACHINE_OPTIONS macros without affecting
the other versions that reuse them.
init function:
Some machines had the init function set inside the MACHINE_OPTIONS
macro. Move it to the QEMUMachine declaration, to keep it consistent
with the other machines.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2015-05-15 19:18:52 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v0_12, "pc-0.12", pc_compat_0_13,
|
|
|
|
pc_i440fx_0_12_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2010-05-14 09:29:15 +02:00
|
|
|
|
2012-03-26 11:26:16 +02:00
|
|
|
#define PC_COMPAT_0_11 \
|
2015-05-14 20:53:00 +02:00
|
|
|
PC_COMPAT_0_12 \
|
2012-03-26 11:26:16 +02:00
|
|
|
{\
|
|
|
|
.driver = "virtio-blk-pci",\
|
|
|
|
.property = "vectors",\
|
|
|
|
.value = stringify(0),\
|
2012-05-02 13:31:04 +02:00
|
|
|
},{\
|
2012-03-28 18:12:47 +02:00
|
|
|
.driver = TYPE_PCI_DEVICE,\
|
2012-05-02 13:31:04 +02:00
|
|
|
.property = "rombar",\
|
|
|
|
.value = stringify(0),\
|
2015-05-14 20:53:07 +02:00
|
|
|
},{\
|
|
|
|
.driver = "ide-drive",\
|
|
|
|
.property = "ver",\
|
|
|
|
.value = "0.11",\
|
|
|
|
},{\
|
|
|
|
.driver = "scsi-disk",\
|
|
|
|
.property = "ver",\
|
|
|
|
.value = "0.11",\
|
2015-05-14 20:53:00 +02:00
|
|
|
},
|
2012-03-26 11:26:16 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_0_11_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_0_12_machine_options(m);
|
|
|
|
m->hw_version = "0.11";
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_0_11);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
pc: Define MACHINE_OPTIONS macros consistently for all machines
Define a MACHINE_OPTIONS macro for each PC machine, and move every field
inside the QEMUMachine structs to the macros, except for name, init, and
compat_props.
This also ensures that all MACHINE_OPTIONS inherit the fields from the
next version, so their definitions carry only the changes that exist
between one version and the next one.
Comments about specific cases:
pc-*-2.1:
Existing PC_*_2_1_MACHINE_OPTIONS macros were defined as:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin"
PC_*_2_2_MACHINE_OPTIONS is:
PC_*_2_3_MACHINE_OPTIONS
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std"
The only difference between 2_1 and 2_2 is .default_display, that's why
we didn't reuse PC_*_2_2_MACHINE_OPTIONS. The good news is that having
multiple initializers for a field is allowed by C99, and the last
initializer overrides the previous ones.
So we can reuse the 2_2 macro in 2_1 and define PC_*_2_1_MACHINE_OPTIONS
as:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
pc-*-1.7:
PC_*_1_7_MACHINE_OPTIONS was defined as:
PC_*_MACHINE_OPTIONS
PC_*_2_0_MACHINE_OPTIONS is defined as:
PC_*_2_1_MACHINE_OPTIONS
which is expanded to:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_2_3_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std",
.default_display = NULL /* overrides the previous line */
So, the only difference between PC_*_1_7_MACHINE_OPTIONS and
PC_*_2_0_MACHINE_OPTIONS is .default_machine_opts (as .default_display
is not explicitly set by PC_*_MACHINE_OPTIONS so it is NULL).
So we can keep the macro reuse pattern and define
PC_*_2_0_MACHINE_OPTIONS as:
PC_*_2_0_MACHINE_OPTIONS,
.default_machine_opts = NULL
pc-*-2.4 (alias and is_default fields):
Set alias and is_default fields inside the 2.4 MACHINE_OPTIONS macro,
and clear it in the 2.3 macro (that reuses the 2.4 macro).
hw_machine:
As all the machines older than v1.0 set hw_version explicitly, we can
safely move the field to the MACHINE_OPTIONS macros without affecting
the other versions that reuse them.
init function:
Some machines had the init function set inside the MACHINE_OPTIONS
macro. Move it to the QEMUMachine declaration, to keep it consistent
with the other machines.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2015-05-15 19:18:52 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v0_11, "pc-0.11", pc_compat_0_13,
|
|
|
|
pc_i440fx_0_11_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2010-05-14 09:29:15 +02:00
|
|
|
|
2015-05-14 20:53:10 +02:00
|
|
|
#define PC_COMPAT_0_10 \
|
|
|
|
PC_COMPAT_0_11 \
|
|
|
|
{\
|
|
|
|
.driver = "virtio-blk-pci",\
|
|
|
|
.property = "class",\
|
|
|
|
.value = stringify(PCI_CLASS_STORAGE_OTHER),\
|
|
|
|
},{\
|
|
|
|
.driver = "virtio-serial-pci",\
|
|
|
|
.property = "class",\
|
|
|
|
.value = stringify(PCI_CLASS_DISPLAY_OTHER),\
|
|
|
|
},{\
|
|
|
|
.driver = "virtio-net-pci",\
|
|
|
|
.property = "vectors",\
|
|
|
|
.value = stringify(0),\
|
|
|
|
},{\
|
|
|
|
.driver = "ide-drive",\
|
|
|
|
.property = "ver",\
|
|
|
|
.value = "0.10",\
|
|
|
|
},{\
|
|
|
|
.driver = "scsi-disk",\
|
|
|
|
.property = "ver",\
|
|
|
|
.value = "0.10",\
|
|
|
|
},
|
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void pc_i440fx_0_10_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
pc_i440fx_0_11_machine_options(m);
|
|
|
|
m->hw_version = "0.10";
|
2015-05-15 19:18:55 +02:00
|
|
|
SET_MACHINE_COMPAT(m, PC_COMPAT_0_10);
|
2015-05-15 19:18:54 +02:00
|
|
|
}
|
pc: Define MACHINE_OPTIONS macros consistently for all machines
Define a MACHINE_OPTIONS macro for each PC machine, and move every field
inside the QEMUMachine structs to the macros, except for name, init, and
compat_props.
This also ensures that all MACHINE_OPTIONS inherit the fields from the
next version, so their definitions carry only the changes that exist
between one version and the next one.
Comments about specific cases:
pc-*-2.1:
Existing PC_*_2_1_MACHINE_OPTIONS macros were defined as:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin"
PC_*_2_2_MACHINE_OPTIONS is:
PC_*_2_3_MACHINE_OPTIONS
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std"
The only difference between 2_1 and 2_2 is .default_display, that's why
we didn't reuse PC_*_2_2_MACHINE_OPTIONS. The good news is that having
multiple initializers for a field is allowed by C99, and the last
initializer overrides the previous ones.
So we can reuse the 2_2 macro in 2_1 and define PC_*_2_1_MACHINE_OPTIONS
as:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
pc-*-1.7:
PC_*_1_7_MACHINE_OPTIONS was defined as:
PC_*_MACHINE_OPTIONS
PC_*_2_0_MACHINE_OPTIONS is defined as:
PC_*_2_1_MACHINE_OPTIONS
which is expanded to:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_2_3_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std",
.default_display = NULL /* overrides the previous line */
So, the only difference between PC_*_1_7_MACHINE_OPTIONS and
PC_*_2_0_MACHINE_OPTIONS is .default_machine_opts (as .default_display
is not explicitly set by PC_*_MACHINE_OPTIONS so it is NULL).
So we can keep the macro reuse pattern and define
PC_*_2_0_MACHINE_OPTIONS as:
PC_*_2_0_MACHINE_OPTIONS,
.default_machine_opts = NULL
pc-*-2.4 (alias and is_default fields):
Set alias and is_default fields inside the 2.4 MACHINE_OPTIONS macro,
and clear it in the 2.3 macro (that reuses the 2.4 macro).
hw_machine:
As all the machines older than v1.0 set hw_version explicitly, we can
safely move the field to the MACHINE_OPTIONS macros without affecting
the other versions that reuse them.
init function:
Some machines had the init function set inside the MACHINE_OPTIONS
macro. Move it to the QEMUMachine declaration, to keep it consistent
with the other machines.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2015-05-15 19:18:52 +02:00
|
|
|
|
2015-05-15 19:19:01 +02:00
|
|
|
DEFINE_I440FX_MACHINE(v0_10, "pc-0.10", pc_compat_0_13,
|
|
|
|
pc_i440fx_0_10_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2015-07-15 07:37:47 +02:00
|
|
|
typedef struct {
|
|
|
|
uint16_t gpu_device_id;
|
|
|
|
uint16_t pch_device_id;
|
|
|
|
uint8_t pch_revision_id;
|
|
|
|
} IGDDeviceIDInfo;
|
|
|
|
|
|
|
|
/* In real world different GPU should have different PCH. But actually
|
|
|
|
* the different PCH DIDs likely map to different PCH SKUs. We do the
|
|
|
|
* same thing for the GPU. For PCH, the different SKUs are going to be
|
|
|
|
* all the same silicon design and implementation, just different
|
|
|
|
* features turn on and off with fuses. The SW interfaces should be
|
|
|
|
* consistent across all SKUs in a given family (eg LPT). But just same
|
|
|
|
* features may not be supported.
|
|
|
|
*
|
|
|
|
* Most of these different PCH features probably don't matter to the
|
|
|
|
* Gfx driver, but obviously any difference in display port connections
|
|
|
|
* will so it should be fine with any PCH in case of passthrough.
|
|
|
|
*
|
|
|
|
* So currently use one PCH version, 0x8c4e, to cover all HSW(Haswell)
|
|
|
|
* scenarios, 0x9cc3 for BDW(Broadwell).
|
|
|
|
*/
|
|
|
|
static const IGDDeviceIDInfo igd_combo_id_infos[] = {
|
|
|
|
/* HSW Classic */
|
|
|
|
{0x0402, 0x8c4e, 0x04}, /* HSWGT1D, HSWD_w7 */
|
|
|
|
{0x0406, 0x8c4e, 0x04}, /* HSWGT1M, HSWM_w7 */
|
|
|
|
{0x0412, 0x8c4e, 0x04}, /* HSWGT2D, HSWD_w7 */
|
|
|
|
{0x0416, 0x8c4e, 0x04}, /* HSWGT2M, HSWM_w7 */
|
|
|
|
{0x041E, 0x8c4e, 0x04}, /* HSWGT15D, HSWD_w7 */
|
|
|
|
/* HSW ULT */
|
|
|
|
{0x0A06, 0x8c4e, 0x04}, /* HSWGT1UT, HSWM_w7 */
|
|
|
|
{0x0A16, 0x8c4e, 0x04}, /* HSWGT2UT, HSWM_w7 */
|
|
|
|
{0x0A26, 0x8c4e, 0x06}, /* HSWGT3UT, HSWM_w7 */
|
|
|
|
{0x0A2E, 0x8c4e, 0x04}, /* HSWGT3UT28W, HSWM_w7 */
|
|
|
|
{0x0A1E, 0x8c4e, 0x04}, /* HSWGT2UX, HSWM_w7 */
|
|
|
|
{0x0A0E, 0x8c4e, 0x04}, /* HSWGT1ULX, HSWM_w7 */
|
|
|
|
/* HSW CRW */
|
|
|
|
{0x0D26, 0x8c4e, 0x04}, /* HSWGT3CW, HSWM_w7 */
|
|
|
|
{0x0D22, 0x8c4e, 0x04}, /* HSWGT3CWDT, HSWD_w7 */
|
|
|
|
/* HSW Server */
|
|
|
|
{0x041A, 0x8c4e, 0x04}, /* HSWSVGT2, HSWD_w7 */
|
|
|
|
/* HSW SRVR */
|
|
|
|
{0x040A, 0x8c4e, 0x04}, /* HSWSVGT1, HSWD_w7 */
|
|
|
|
/* BSW */
|
|
|
|
{0x1606, 0x9cc3, 0x03}, /* BDWULTGT1, BDWM_w7 */
|
|
|
|
{0x1616, 0x9cc3, 0x03}, /* BDWULTGT2, BDWM_w7 */
|
|
|
|
{0x1626, 0x9cc3, 0x03}, /* BDWULTGT3, BDWM_w7 */
|
|
|
|
{0x160E, 0x9cc3, 0x03}, /* BDWULXGT1, BDWM_w7 */
|
|
|
|
{0x161E, 0x9cc3, 0x03}, /* BDWULXGT2, BDWM_w7 */
|
|
|
|
{0x1602, 0x9cc3, 0x03}, /* BDWHALOGT1, BDWM_w7 */
|
|
|
|
{0x1612, 0x9cc3, 0x03}, /* BDWHALOGT2, BDWM_w7 */
|
|
|
|
{0x1622, 0x9cc3, 0x03}, /* BDWHALOGT3, BDWM_w7 */
|
|
|
|
{0x162B, 0x9cc3, 0x03}, /* BDWHALO28W, BDWM_w7 */
|
|
|
|
{0x162A, 0x9cc3, 0x03}, /* BDWGT3WRKS, BDWM_w7 */
|
|
|
|
{0x162D, 0x9cc3, 0x03}, /* BDWGT3SRVR, BDWM_w7 */
|
|
|
|
};
|
|
|
|
|
|
|
|
static void isa_bridge_class_init(ObjectClass *klass, void *data)
|
|
|
|
{
|
|
|
|
DeviceClass *dc = DEVICE_CLASS(klass);
|
|
|
|
PCIDeviceClass *k = PCI_DEVICE_CLASS(klass);
|
|
|
|
|
|
|
|
dc->desc = "ISA bridge faked to support IGD PT";
|
|
|
|
k->vendor_id = PCI_VENDOR_ID_INTEL;
|
|
|
|
k->class_id = PCI_CLASS_BRIDGE_ISA;
|
|
|
|
};
|
|
|
|
|
|
|
|
static TypeInfo isa_bridge_info = {
|
|
|
|
.name = "igd-passthrough-isa-bridge",
|
|
|
|
.parent = TYPE_PCI_DEVICE,
|
|
|
|
.instance_size = sizeof(PCIDevice),
|
|
|
|
.class_init = isa_bridge_class_init,
|
|
|
|
};
|
|
|
|
|
|
|
|
static void pt_graphics_register_types(void)
|
|
|
|
{
|
|
|
|
type_register_static(&isa_bridge_info);
|
|
|
|
}
|
|
|
|
type_init(pt_graphics_register_types)
|
|
|
|
|
|
|
|
void igd_passthrough_isa_bridge_create(PCIBus *bus, uint16_t gpu_dev_id)
|
|
|
|
{
|
|
|
|
struct PCIDevice *bridge_dev;
|
|
|
|
int i, num;
|
|
|
|
uint16_t pch_dev_id = 0xffff;
|
|
|
|
uint8_t pch_rev_id;
|
|
|
|
|
|
|
|
num = ARRAY_SIZE(igd_combo_id_infos);
|
|
|
|
for (i = 0; i < num; i++) {
|
|
|
|
if (gpu_dev_id == igd_combo_id_infos[i].gpu_device_id) {
|
|
|
|
pch_dev_id = igd_combo_id_infos[i].pch_device_id;
|
|
|
|
pch_rev_id = igd_combo_id_infos[i].pch_revision_id;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (pch_dev_id == 0xffff) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Currently IGD drivers always need to access PCH by 1f.0. */
|
|
|
|
bridge_dev = pci_create_simple(bus, PCI_DEVFN(0x1f, 0),
|
|
|
|
"igd-passthrough-isa-bridge");
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Note that vendor id is always PCI_VENDOR_ID_INTEL.
|
|
|
|
*/
|
|
|
|
if (!bridge_dev) {
|
|
|
|
fprintf(stderr, "set igd-passthrough-isa-bridge failed!\n");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
pci_config_set_device_id(bridge_dev->config, pch_dev_id);
|
|
|
|
pci_config_set_revision(bridge_dev->config, pch_rev_id);
|
|
|
|
}
|
2010-05-14 09:29:15 +02:00
|
|
|
|
2015-05-15 19:18:56 +02:00
|
|
|
static void isapc_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
m->desc = "ISA-only PC";
|
|
|
|
m->max_cpus = 1;
|
|
|
|
}
|
pc: Define MACHINE_OPTIONS macros consistently for all machines
Define a MACHINE_OPTIONS macro for each PC machine, and move every field
inside the QEMUMachine structs to the macros, except for name, init, and
compat_props.
This also ensures that all MACHINE_OPTIONS inherit the fields from the
next version, so their definitions carry only the changes that exist
between one version and the next one.
Comments about specific cases:
pc-*-2.1:
Existing PC_*_2_1_MACHINE_OPTIONS macros were defined as:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin"
PC_*_2_2_MACHINE_OPTIONS is:
PC_*_2_3_MACHINE_OPTIONS
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std"
The only difference between 2_1 and 2_2 is .default_display, that's why
we didn't reuse PC_*_2_2_MACHINE_OPTIONS. The good news is that having
multiple initializers for a field is allowed by C99, and the last
initializer overrides the previous ones.
So we can reuse the 2_2 macro in 2_1 and define PC_*_2_1_MACHINE_OPTIONS
as:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
pc-*-1.7:
PC_*_1_7_MACHINE_OPTIONS was defined as:
PC_*_MACHINE_OPTIONS
PC_*_2_0_MACHINE_OPTIONS is defined as:
PC_*_2_1_MACHINE_OPTIONS
which is expanded to:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_2_3_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std",
.default_display = NULL /* overrides the previous line */
So, the only difference between PC_*_1_7_MACHINE_OPTIONS and
PC_*_2_0_MACHINE_OPTIONS is .default_machine_opts (as .default_display
is not explicitly set by PC_*_MACHINE_OPTIONS so it is NULL).
So we can keep the macro reuse pattern and define
PC_*_2_0_MACHINE_OPTIONS as:
PC_*_2_0_MACHINE_OPTIONS,
.default_machine_opts = NULL
pc-*-2.4 (alias and is_default fields):
Set alias and is_default fields inside the 2.4 MACHINE_OPTIONS macro,
and clear it in the 2.3 macro (that reuses the 2.4 macro).
hw_machine:
As all the machines older than v1.0 set hw_version explicitly, we can
safely move the field to the MACHINE_OPTIONS macros without affecting
the other versions that reuse them.
init function:
Some machines had the init function set inside the MACHINE_OPTIONS
macro. Move it to the QEMUMachine declaration, to keep it consistent
with the other machines.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2015-05-15 19:18:52 +02:00
|
|
|
|
2015-05-15 19:18:53 +02:00
|
|
|
DEFINE_PC_MACHINE(isapc, "isapc", pc_init_isa,
|
2015-05-15 19:18:55 +02:00
|
|
|
isapc_machine_options);
|
2015-05-15 19:18:53 +02:00
|
|
|
|
2010-05-14 09:29:15 +02:00
|
|
|
|
2010-06-30 13:58:34 +02:00
|
|
|
#ifdef CONFIG_XEN
|
2015-05-15 19:18:56 +02:00
|
|
|
static void xenfv_machine_options(MachineClass *m)
|
2015-05-15 19:18:54 +02:00
|
|
|
{
|
|
|
|
m->desc = "Xen Fully-virtualized PC";
|
|
|
|
m->max_cpus = HVM_MAX_VCPUS;
|
|
|
|
m->default_machine_opts = "accel=xen";
|
|
|
|
m->hot_add_cpu = pc_hot_add_cpu;
|
|
|
|
}
|
pc: Define MACHINE_OPTIONS macros consistently for all machines
Define a MACHINE_OPTIONS macro for each PC machine, and move every field
inside the QEMUMachine structs to the macros, except for name, init, and
compat_props.
This also ensures that all MACHINE_OPTIONS inherit the fields from the
next version, so their definitions carry only the changes that exist
between one version and the next one.
Comments about specific cases:
pc-*-2.1:
Existing PC_*_2_1_MACHINE_OPTIONS macros were defined as:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin"
PC_*_2_2_MACHINE_OPTIONS is:
PC_*_2_3_MACHINE_OPTIONS
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std"
The only difference between 2_1 and 2_2 is .default_display, that's why
we didn't reuse PC_*_2_2_MACHINE_OPTIONS. The good news is that having
multiple initializers for a field is allowed by C99, and the last
initializer overrides the previous ones.
So we can reuse the 2_2 macro in 2_1 and define PC_*_2_1_MACHINE_OPTIONS
as:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
pc-*-1.7:
PC_*_1_7_MACHINE_OPTIONS was defined as:
PC_*_MACHINE_OPTIONS
PC_*_2_0_MACHINE_OPTIONS is defined as:
PC_*_2_1_MACHINE_OPTIONS
which is expanded to:
PC_*_2_2_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_2_3_MACHINE_OPTIONS,
.default_display = NULL
which is expanded to:
PC_*_MACHINE_OPTIONS,
.default_machine_opts = "firmware=bios-256k.bin",
.default_display = "std",
.default_display = NULL /* overrides the previous line */
So, the only difference between PC_*_1_7_MACHINE_OPTIONS and
PC_*_2_0_MACHINE_OPTIONS is .default_machine_opts (as .default_display
is not explicitly set by PC_*_MACHINE_OPTIONS so it is NULL).
So we can keep the macro reuse pattern and define
PC_*_2_0_MACHINE_OPTIONS as:
PC_*_2_0_MACHINE_OPTIONS,
.default_machine_opts = NULL
pc-*-2.4 (alias and is_default fields):
Set alias and is_default fields inside the 2.4 MACHINE_OPTIONS macro,
and clear it in the 2.3 macro (that reuses the 2.4 macro).
hw_machine:
As all the machines older than v1.0 set hw_version explicitly, we can
safely move the field to the MACHINE_OPTIONS macros without affecting
the other versions that reuse them.
init function:
Some machines had the init function set inside the MACHINE_OPTIONS
macro. Move it to the QEMUMachine declaration, to keep it consistent
with the other machines.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2015-05-15 19:18:52 +02:00
|
|
|
|
2015-05-15 19:18:53 +02:00
|
|
|
DEFINE_PC_MACHINE(xenfv, "xenfv", pc_xen_hvm_init,
|
2015-05-15 19:18:55 +02:00
|
|
|
xenfv_machine_options);
|
2010-06-30 13:58:34 +02:00
|
|
|
#endif
|