621b509048
Replace the existing ad-hoc configuration via various global variables with a small database of key-value pairs. The database supports heirarchical keys using a MIB-like syntax to name the path to a given key. Values are always stored as strings. The API used to manage configuation values does include wrappers to handling boolean values. Other values use non-string types require parsing by consumers. The configuration values are stored in a tree using nvlists. Leaf nodes hold string values. Configuration values are permitted to reference other configuration values using '%(name)'. This permits constructing template configurations. All existing command line arguments now set configuration values. For devices, the "-s" option parses its option argument to generate a list of key-value pairs for the given device. A new '-o' command line option permits setting an individual configuration variable. The key name is always given as a full path of dot-separated components. A new '-k' command line option parses a simple configuration file. This configuration file holds a flat list of 'key=value' lines where the 'key' is the full path of a configuration variable. Lines starting with a '#' are comments. In general, bhyve starts by parsing command line options in sequence and applying those settings to configuration values. Once this is complete, bhyve then begins initializing its state based on the configuration values. This means that subsequent configuration options or files may override or supplement previously given settings. A special 'config.dump' configuration value can be set to true to help debug configuration issues. When this value is set, bhyve will print out the configuration variables as a flat list of 'key=value' lines. Most command line argments map to a single configuration variable, e.g. '-w' sets the 'x86.strictmsr' value to false. A few command line arguments have less obvious effects: - Multiple '-p' options append their values (as a comma-seperated list) to "vcpu.N.cpuset" values (where N is a decimal vcpu number). - For '-s' options, a pci.<bus>.<slot>.<function> node is created. The first argument to '-s' (the device type) is used as the value of a "device" variable. Additional comma-separated arguments are then parsed into 'key=value' pairs and used to set additional variables under the device node. A PCI device emulation driver can provide its own hook to override the parsing of the additonal '-s' arguments after the device type. After the configuration phase as completed, the init_pci hook then walks the "pci.<bus>.<slot>.<func>" nodes. It uses the "device" value to find the device model to use. The device model's init routine is passed a reference to its nvlist node in the configuration tree which it can query for specific variables. The result is that a lot of the string parsing is removed from the device models and centralized. In addition, adding a new variable just requires teaching the model to look for the new variable. - For '-l' options, a similar model is used where the string is parsed into values that are later read during initialization. One key note here is that the serial ports use the commonly used lowercase names from existing documentation and examples (e.g. "lpc.com1") instead of the uppercase names previously used internally in bhyve. Reviewed by: grehan MFC after: 3 months Differential Revision: https://reviews.freebsd.org/D26035
92 lines
3.4 KiB
C
92 lines
3.4 KiB
C
/*-
|
|
* SPDX-License-Identifier: BSD-2-Clause-FreeBSD
|
|
*
|
|
* Copyright (c) 2013 Peter Grehan <grehan@freebsd.org>
|
|
* All rights reserved.
|
|
*
|
|
* Redistribution and use in source and binary forms, with or without
|
|
* modification, are permitted provided that the following conditions
|
|
* are met:
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
* notice, this list of conditions and the following disclaimer.
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
* documentation and/or other materials provided with the distribution.
|
|
*
|
|
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
* SUCH DAMAGE.
|
|
*
|
|
* $FreeBSD$
|
|
*/
|
|
|
|
/*
|
|
* The block API to be used by bhyve block-device emulations. The routines
|
|
* are thread safe, with no assumptions about the context of the completion
|
|
* callback - it may occur in the caller's context, or asynchronously in
|
|
* another thread.
|
|
*/
|
|
|
|
#ifndef _BLOCK_IF_H_
|
|
#define _BLOCK_IF_H_
|
|
|
|
#include <sys/nv.h>
|
|
#include <sys/uio.h>
|
|
#include <sys/unistd.h>
|
|
|
|
struct vm_snapshot_meta;
|
|
|
|
|
|
/*
|
|
* BLOCKIF_IOV_MAX is the maximum number of scatter/gather entries in
|
|
* a single request. BLOCKIF_RING_MAX is the maxmimum number of
|
|
* pending requests that can be queued.
|
|
*/
|
|
#define BLOCKIF_IOV_MAX 128 /* not practical to be IOV_MAX */
|
|
#define BLOCKIF_RING_MAX 128
|
|
|
|
struct blockif_req {
|
|
int br_iovcnt;
|
|
off_t br_offset;
|
|
ssize_t br_resid;
|
|
void (*br_callback)(struct blockif_req *req, int err);
|
|
void *br_param;
|
|
struct iovec br_iov[BLOCKIF_IOV_MAX];
|
|
};
|
|
|
|
struct blockif_ctxt;
|
|
int blockif_legacy_config(nvlist_t *nvl, const char *opts);
|
|
struct blockif_ctxt *blockif_open(nvlist_t *nvl, const char *ident);
|
|
off_t blockif_size(struct blockif_ctxt *bc);
|
|
void blockif_chs(struct blockif_ctxt *bc, uint16_t *c, uint8_t *h,
|
|
uint8_t *s);
|
|
int blockif_sectsz(struct blockif_ctxt *bc);
|
|
void blockif_psectsz(struct blockif_ctxt *bc, int *size, int *off);
|
|
int blockif_queuesz(struct blockif_ctxt *bc);
|
|
int blockif_is_ro(struct blockif_ctxt *bc);
|
|
int blockif_candelete(struct blockif_ctxt *bc);
|
|
int blockif_read(struct blockif_ctxt *bc, struct blockif_req *breq);
|
|
int blockif_write(struct blockif_ctxt *bc, struct blockif_req *breq);
|
|
int blockif_flush(struct blockif_ctxt *bc, struct blockif_req *breq);
|
|
int blockif_delete(struct blockif_ctxt *bc, struct blockif_req *breq);
|
|
int blockif_cancel(struct blockif_ctxt *bc, struct blockif_req *breq);
|
|
int blockif_close(struct blockif_ctxt *bc);
|
|
#ifdef BHYVE_SNAPSHOT
|
|
void blockif_pause(struct blockif_ctxt *bc);
|
|
void blockif_resume(struct blockif_ctxt *bc);
|
|
int blockif_snapshot_req(struct blockif_req *br,
|
|
struct vm_snapshot_meta *meta);
|
|
int blockif_snapshot(struct blockif_ctxt *bc,
|
|
struct vm_snapshot_meta *meta);
|
|
#endif
|
|
|
|
#endif /* _BLOCK_IF_H_ */
|