acrn-hypervisor/hypervisor/release/sbuf.c

/*
 * Copyright (C) 2019 Intel Corporation. All rights reserved.
 *
 * SPDX-License-Identifier: BSD-3-Clause
 */

void sbuf_reset(void) {}
hv: reset per cpu sbuf pointers during vcpu reset When shutting down SOS VM, the shared sbuf is released from guest OS, but the per cpu sbuf pointers in hypervisor keep inact. This creates a problem that after SOS is re-launched, hypervisor could write to the shared buffer that no longer exists. This patch implements sbuf_reset() and call it from reset_vcpu() to reset sbuf pointers. Tracked-On: #2700 Signed-off-by: Zide Chen <zide.chen@intel.com> Acked-by: Anthony Xu <anthony.xu@intel.com> 2019-04-18 02:41:21 +08:00			`/*`
			`* Copyright (C) 2019 Intel Corporation. All rights reserved.`
			`*`
			`* SPDX-License-Identifier: BSD-3-Clause`
			`*/`

hv: bugfix for sbuf reset The sbuf is allocated for each pcpu by hypercall from SOS. Before launch Guest OS, the script will offline cpus, which will trigger vcpu reset and then reset sbuf pointer. But sbuf only initiate once by SOS, so these cpus for Guest OS has no sbuf to use. Thus, when run 'acrntrace' on SOS, there is no trace data for Guest OS. To fix the issue, only reset the sbuf for SOS. Tracked-On: #3335 Signed-off-by: Conghui Chen <conghui.chen@intel.com> Reviewed-by: Eddie Dong <eddie.dong@intel.com> Reviewed-by: Yan, Like <like.yan@intel.com> 2019-06-27 00:50:00 +08:00			`void sbuf_reset(void) {}`