All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] tracing/pt_test: TCONF if Intel PT across VMXON is not supported
Date: Mon, 17 Mar 2025 13:23:51 +0100	[thread overview]
Message-ID: <20250317122351.GA247824@pevik> (raw)
In-Reply-To: <d1d830051aea3f077995c30b2183731cd2f04cf2.1742054500.git.jstancek@redhat.com>

Hi Jan,

> As noted in 1c5ac21a0e9b ("perf/x86/intel/pt: Don't die on VMXON"),
> some Broadwell systems don't support Intel PT across VMXON.
+1

> If the test fails to find any events, check whether there is a
> kvm_intel module loaded, and if so check for IA32_VMX_MISC[bit 14].
> If this bit is 0, it's not supported. From commit mentioned above:
>     Intel SDM, 36.5 "Tracing post-VMXON" says that
>     "IA32_VMX_MISC[bit 14]" being 1 means PT can trace
>     post-VMXON.

LGTM.

Reviewed-by: Petr Vorel <pvorel@suse.cz>

...
>  static void intel_pt_trace_check(void)
>  {
>  	uint64_t aux_head = 0;
> @@ -117,6 +150,12 @@ static void intel_pt_trace_check(void)
>  	pmp = (struct perf_event_mmap_page *)bufm[0];
>  	aux_head = *(volatile uint64_t *)&pmp->aux_head;
>  	if (aux_head == 0) {
> +		if ((access("/sys/module/kvm_intel", F_OK) == 0)
> +			&& (!is_supported_across_vmxon())) {
> +			tst_brk(TCONF, "Intel PT on this system can not"
> +				" run at the same time as virtualization");

As we discussed at the issue, please join the string before merge.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-03-17 12:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-15 16:01 [LTP] [PATCH] tracing/pt_test: TCONF if Intel PT across VMXON is not supported Jan Stancek via ltp
2025-03-17 12:23 ` Petr Vorel [this message]
2025-03-20 11:24   ` Jan Stancek via ltp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250317122351.GA247824@pevik \
    --to=pvorel@suse.cz \
    --cc=jstancek@redhat.com \
    --cc=ltp@lists.linux.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.