34f804e547
Qemu defines some common fwcfg items. We don't need to support all of them. Only a subset needs to be present for fwcfg to work properly. - signature The signature is used by the guest to check if qemu's fwcfg is available or not. - id The id is used by the guest to check which features are supported by the fwcfg implementation of the hypervisor. - file_dir The file dir reports all fwcfg items which don't have a fixed index. These are mostly user defined fwcfg items. Reviewed by: <If someone else reviewed your modification.> MFC after: 1 week Sponsored by: Beckhoff Automation GmbH & Co. KG Differential Revision: https://reviews.freebsd.org/D38335
22 lines
411 B
C
22 lines
411 B
C
/*-
|
|
* SPDX-License-Identifier: BSD-2-Clause-FreeBSD
|
|
*
|
|
* Copyright (c) 2021 Beckhoff Automation GmbH & Co. KG
|
|
* Author: Corvin Köhne <c.koehne@beckhoff.com>
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <vmmapi.h>
|
|
|
|
#define QEMU_FWCFG_MAX_ARCHS 0x2
|
|
#define QEMU_FWCFG_MAX_ENTRIES 0x4000
|
|
#define QEMU_FWCFG_MAX_NAME 56
|
|
|
|
struct qemu_fwcfg_item {
|
|
uint32_t size;
|
|
uint8_t *data;
|
|
};
|
|
|
|
int qemu_fwcfg_init(struct vmctx *const ctx);
|