2002-06-30 08:05:21 +00:00
|
|
|
# $FreeBSD$
|
2003-05-19 22:19:02 +00:00
|
|
|
# Options specific to AMD64 platform kernels
|
2002-06-30 08:05:21 +00:00
|
|
|
|
2003-11-17 08:58:16 +00:00
|
|
|
AUTO_EOI_1 opt_auto_eoi.h
|
|
|
|
|
AUTO_EOI_2 opt_auto_eoi.h
|
Initial support for bhyve save and restore.
Save and restore (also known as suspend and resume) permits a snapshot
to be taken of a guest's state that can later be resumed. In the
current implementation, bhyve(8) creates a UNIX domain socket that is
used by bhyvectl(8) to send a request to save a snapshot (and
optionally exit after the snapshot has been taken). A snapshot
currently consists of two files: the first holds a copy of guest RAM,
and the second file holds other guest state such as vCPU register
values and device model state.
To resume a guest, bhyve(8) must be started with a matching pair of
command line arguments to instantiate the same set of device models as
well as a pointer to the saved snapshot.
While the current implementation is useful for several uses cases, it
has a few limitations. The file format for saving the guest state is
tied to the ABI of internal bhyve structures and is not
self-describing (in that it does not communicate the set of device
models present in the system). In addition, the state saved for some
device models closely matches the internal data structures which might
prove a challenge for compatibility of snapshot files across a range
of bhyve versions. The file format also does not currently support
versioning of individual chunks of state. As a result, the current
file format is not a fixed binary format and future revisions to save
and restore will break binary compatiblity of snapshot files. The
goal is to move to a more flexible format that adds versioning,
etc. and at that point to commit to providing a reasonable level of
compatibility. As a result, the current implementation is not enabled
by default. It can be enabled via the WITH_BHYVE_SNAPSHOT=yes option
for userland builds, and the kernel option BHYVE_SHAPSHOT.
Submitted by: Mihai Tiganus, Flavius Anton, Darius Mihai
Submitted by: Elena Mihailescu, Mihai Carabas, Sergiu Weisz
Relnotes: yes
Sponsored by: University Politehnica of Bucharest
Sponsored by: Matthew Grooms (student scholarships)
Sponsored by: iXsystems
Differential Revision: https://reviews.freebsd.org/D19495
2020-05-05 00:02:04 +00:00
|
|
|
BHYVE_SNAPSHOT
|
2010-06-17 11:54:49 +00:00
|
|
|
COUNT_XINVLTLB_HITS opt_smp.h
|
|
|
|
|
COUNT_IPIS opt_smp.h
|
2002-06-30 08:05:21 +00:00
|
|
|
MAXMEM
|
2010-10-29 18:38:36 +00:00
|
|
|
MPTABLE_FORCE_HTT
|
2005-12-12 10:15:11 +00:00
|
|
|
MP_WATCHDOG
|
2011-08-26 17:08:22 +00:00
|
|
|
NKPT opt_pmap.h
|
2012-03-24 19:43:49 +00:00
|
|
|
PV_STATS opt_pmap.h
|
2004-03-03 09:35:47 +00:00
|
|
|
|
|
|
|
|
# Options for emulators. These should only be used at config time, so
|
|
|
|
|
# they are handled like options for static filesystems
|
|
|
|
|
# (see src/sys/conf/options), except for broken debugging options.
|
2018-06-02 06:40:15 +00:00
|
|
|
COMPAT_AOUT opt_dontuse.h
|
2018-04-06 17:35:35 +00:00
|
|
|
COMPAT_FREEBSD32 opt_global.h
|
2004-03-13 22:16:34 +00:00
|
|
|
#COMPAT_LINUX opt_dontuse.h
|
2004-08-16 07:55:06 +00:00
|
|
|
COMPAT_LINUX32 opt_compat.h
|
2006-05-07 18:12:18 +00:00
|
|
|
LINPROCFS opt_dontuse.h
|
2006-05-10 03:25:45 +00:00
|
|
|
LINSYSFS opt_dontuse.h
|
2002-06-30 08:05:21 +00:00
|
|
|
|
2004-03-03 09:35:47 +00:00
|
|
|
TIMER_FREQ opt_clock.h
|
2002-06-30 08:05:21 +00:00
|
|
|
|
|
|
|
|
VGA_ALT_SEQACCESS opt_vga.h
|
|
|
|
|
VGA_DEBUG opt_vga.h
|
|
|
|
|
VGA_NO_FONT_LOADING opt_vga.h
|
|
|
|
|
VGA_NO_MODE_CHANGE opt_vga.h
|
|
|
|
|
VGA_SLOW_IOACCESS opt_vga.h
|
|
|
|
|
VGA_WIDTH90 opt_vga.h
|
|
|
|
|
|
2009-09-09 09:50:31 +00:00
|
|
|
VESA
|
|
|
|
|
VESA_DEBUG opt_vesa.h
|
|
|
|
|
|
2009-02-06 20:57:10 +00:00
|
|
|
# AGP debugging support
|
|
|
|
|
AGP_DEBUG opt_agp.h
|
|
|
|
|
|
2002-06-30 08:05:21 +00:00
|
|
|
ATKBD_DFLT_KEYMAP opt_atkbd.h
|
|
|
|
|
|
2017-02-10 01:04:11 +00:00
|
|
|
# iWARP client interface support in ixl
|
|
|
|
|
IXL_IW opt_ixl.h
|
|
|
|
|
|
2002-06-30 08:05:21 +00:00
|
|
|
# -------------------------------
|
|
|
|
|
# EOF
|
|
|
|
|
# -------------------------------
|
2003-05-01 02:59:24 +00:00
|
|
|
HAMMER opt_cpu.h
|
|
|
|
|
PSM_HOOKRESUME opt_psm.h
|
|
|
|
|
PSM_RESETAFTERSUSPEND opt_psm.h
|
|
|
|
|
PSM_DEBUG opt_psm.h
|
2003-11-17 08:58:16 +00:00
|
|
|
DEV_ATPIC opt_atpic.h
|
2005-04-30 20:01:00 +00:00
|
|
|
|
2005-12-06 02:58:12 +00:00
|
|
|
# BPF just-in-time compiler
|
|
|
|
|
BPF_JITTER opt_bpf.h
|
2009-03-11 15:30:12 +00:00
|
|
|
|
|
|
|
|
XENHVM opt_global.h
|
2012-01-31 19:38:18 +00:00
|
|
|
|
|
|
|
|
# options for the Intel C600 SAS driver (isci)
|
|
|
|
|
ISCI_LOGGING opt_isci.h
|
Add kernel interfaces to call EFI Runtime Services.
Runtime services require special execution environment for the call.
Besides that, OS must inform firmware about runtime virtual memory map
which will be active during the calls, with the SetVirtualAddressMap()
runtime call, done while the 1:1 mapping is still used. There are two
complication: the SetVirtualAddressMap() effectively must be done from
loader, which needs to know kernel address map in advance. More,
despite not explicitely mentioned in the specification, both 1:1 and
the map passed to SetVirtualAddressMap() must be active during the
SetVirtualAddressMap() call. Second, there are buggy BIOSes which
require both mappings active during runtime calls as well, most likely
because they fail to identify all relocations to perform.
On amd64, we can get rid of both problems by providing 1:1 mapping for
the duration of runtime calls, by temprorary remapping user addresses.
As result, we avoid the need for loader to know about future kernel
address map, and avoid bugs in BIOSes. Typically BIOS only maps
something in low 4G. If not runtime bugs, we would take advantage of
the DMAP, as previous versions of this patch did.
Similar but more complicated trick can be used even for i386 and 32bit
runtime, if and when the EFI boot on i386 is supported. We would need
a trampoline page, since potentially whole 4G of VA would be switched
on calls, instead of only userspace portion on amd64.
Context switches are disabled for the duration of the call, FPU access
is granted, and interrupts are not disabled. The later is possible
because kernel is mapped during calls.
To test, the sysctl mib debug.efi_time is provided, setting it to 1
makes one call to EFI get_time() runtime service, on success the efitm
structure is printed to the control terminal. Load efirt.ko, or add
EFIRT option to the kernel config, to enable code.
Discussed with: emaste, imp
Tested by: emaste (mac, qemu)
Sponsored by: The FreeBSD Foundation
MFC after: 2 weeks
2016-09-21 11:31:58 +00:00
|
|
|
|
|
|
|
|
# EFI Runtime services support
|
|
|
|
|
EFIRT opt_efirt.h
|
