From: Vince Weaver <vincent.weaver@maine.edu>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Li Huafei <lihuafei1@huawei.com>,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>,
Vince Weaver <vincent.weaver@maine.edu>
Subject: Re: [PATCH] perf/x86/intel: Restrict period on Haswell
Date: Thu, 15 Aug 2024 15:01:42 -0400 (EDT) [thread overview]
Message-ID: <201991b2-d77a-c10f-d46d-ee9b34ba11e5@maine.edu> (raw)
In-Reply-To: <166fdbdf-b24d-4267-b42d-f11348b87b1b@linux.intel.com>
On Thu, 15 Aug 2024, Liang, Kan wrote:
> I also found a related discussion about 9 years ago.
> https://lore.kernel.org/lkml/alpine.DEB.2.11.1505181343090.32481@vincent-weaver-1.umelst.maine.edu/
> Vince tried the workaround but it seems not work.
>
> So limiting the min period of the fixed counter 0 to 32 seems the only
> workaround for now.
I'm actually still lurking on this discussion. My regular fuzzing machine
is still a Haswell machine (the same one from 9 years ago) and it reliably
hits this issue within hours. I hadn't realized there was an official
reproducer.
If a patch does come out of this I'll be glad to test it.
Vince Weaver
vincent.weaver@maine.edu
prev parent reply other threads:[~2024-08-15 19:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 22:33 [PATCH] perf/x86/intel: Restrict period on Haswell Li Huafei
2024-07-31 19:20 ` Thomas Gleixner
2024-08-13 13:13 ` Li Huafei
2024-08-14 14:43 ` Thomas Gleixner
2024-08-14 14:52 ` Thomas Gleixner
2024-08-14 18:15 ` Liang, Kan
2024-08-14 19:01 ` Thomas Gleixner
2024-08-14 19:37 ` Liang, Kan
2024-08-14 22:47 ` Thomas Gleixner
2024-08-15 15:39 ` Liang, Kan
2024-08-15 18:26 ` Thomas Gleixner
2024-08-15 20:15 ` Liang, Kan
2024-08-15 23:43 ` Thomas Gleixner
2024-08-16 19:27 ` Liang, Kan
2024-08-17 12:22 ` Liang, Kan
2024-08-17 12:23 ` Thomas Gleixner
2024-08-15 19:01 ` Vince Weaver [this message]
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=201991b2-d77a-c10f-d46d-ee9b34ba11e5@maine.edu \
--to=vincent.weaver@maine.edu \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=lihuafei1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).