[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen master] xenalyze: AMD's VMEXIT_VINTR doesn't need a trace record
commit 4ef752733bd7cfb13b55ed8a01499ffe3f1f4ef5 Author: George Dunlap <george.dunlap@xxxxxxxxx> AuthorDate: Thu Oct 5 17:26:38 2023 +0100 Commit: George Dunlap <george.dunlap@xxxxxxxxx> CommitDate: Mon Oct 16 15:01:48 2023 +0100 xenalyze: AMD's VMEXIT_VINTR doesn't need a trace record Just like Intel's PENDING_VIRT_INTR, AMD's VINTR doesn't need an HVM trace record. Expect that. Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxx> Release-acked-by: Henry Wang <Henry.Wang@xxxxxxx> Acked-by: Anthony PERARD <anthony.perard@xxxxxxxxxx> --- tools/xentrace/xenalyze.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/tools/xentrace/xenalyze.c b/tools/xentrace/xenalyze.c index 1359e096f9..fc25ac3589 100644 --- a/tools/xentrace/xenalyze.c +++ b/tools/xentrace/xenalyze.c @@ -4628,6 +4628,13 @@ void hvm_generic_postprocess(struct hvm_data *h) /* Some exits we don't expect a handler; just return */ if(opt.svm_mode) { + switch(h->exit_reason) + { + case VMEXIT_VINTR: /* Equivalent of PENDING_VIRT_INTR */ + return; + default: + break; + } } else { -- generated by git-patchbot for /home/xen/git/xen.git#master
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |