[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [PATCH for-4.18 3/5] xenalyze: Don't expect an HVM_HANDLER trace for PAUSE vmexits
Neither vmx nor svm trace anything, nor is there anything obvious worth tracing. Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxx> --- Release justification: This is a bug fix; a minor one, but also in a non-critical part of the code. CC: Anthony Perard <anthony.perard@xxxxxxxxx> CC: Stefano Stabellini <sstabellini@xxxxxxxxxx> CC: Xenia Ragiodakou <xenia.ragiadakou@xxxxxxx> --- tools/xentrace/xenalyze.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/xentrace/xenalyze.c b/tools/xentrace/xenalyze.c index fc25ac3589..2faf66500d 100644 --- a/tools/xentrace/xenalyze.c +++ b/tools/xentrace/xenalyze.c @@ -4631,6 +4631,7 @@ void hvm_generic_postprocess(struct hvm_data *h) switch(h->exit_reason) { case VMEXIT_VINTR: /* Equivalent of PENDING_VIRT_INTR */ + case VMEXIT_PAUSE: return; default: break; @@ -4643,6 +4644,7 @@ void hvm_generic_postprocess(struct hvm_data *h) /* These just need us to go through the return path */ case EXIT_REASON_PENDING_VIRT_INTR: case EXIT_REASON_TPR_BELOW_THRESHOLD: + case EXIT_REASON_PAUSE_INSTRUCTION: /* Not much to log now; may need later */ case EXIT_REASON_WBINVD: return; -- 2.25.1
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |