| Message ID | 20231009125137.1329146-3-george.dunlap@cloud.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | xenalyze: Miscellaneous fixes | expand |
On Mon, Oct 09, 2023 at 01:51:34PM +0100, George Dunlap wrote: > 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@cloud.com> Acked-by: Anthony PERARD <anthony.perard@citrix.com> Thanks,
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 {
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@cloud.com> --- Release justification: This is a bug fix. It's a *very* small one, but then the code path is not very critical either. CC: Stefano Stabellini <sstabellini@kernel.org> CC: Xenia Ragiadakou <xenia.ragiadakou@amd.com> CC: Anthony Perard <anthony.perard@cloud.com> --- tools/xentrace/xenalyze.c | 7 +++++++ 1 file changed, 7 insertions(+)