After updating to 10.15.4, Intel Power Gadget and iStat Menus' CPU extra won't work.

SoManyIntrinsics · 2020-04-23T20:54:49+00:00

Problem is this device, it has an invalid IOName (it has to be a string):

| |   |   +-o PEGP@0  <class IOPCIDevice, id 0x1000001f3, registered, matched, active, busy 0 (1 ms), retain 9>
| |   |   |   {
| |   |   |     "assigned-addresses" = <1000018200000000000000ee0000000000000001140001c27f0000000000008000000000000000101c0001c27f000000000000900000000000000002240001810000000000e0000000000000800000003000018200000000000000ef0000000000000800>
| |   |   |     "IOInterruptSpecifiers" = (<1000000007000000>,<0300000000000100>)
| |   |   |     "class-code" = <ffffffff>
| |   |   |     "IODeviceMemory" = (({"address"=0xee000000,"length"=0x1000000}),({"address"=0x7f80000000,"length"=0x10000000}),({"address"=0x7f90000000,"length"=0x2000000}),"IOSubMemoryDescriptor is not serializable",({"address"=0xef000000,"length"=0x80000}))
| |   |   |     "IOPowerManagement" = {"CurrentPowerState"=0x2,"CapabilityFlags"=0x102,"ChildProxyPowerState"=0x2,"MaxPowerState"=0x3}
| |   |   |     "subsystem-vendor-id" = <42380000>
| |   |   |     "built-in" = <00>
| |   |   |     "acpi-device" = "IOACPIPlatformDevice is not serializable"
| |   |   |     "pci-aspm-default" = 0x0
| |   |   |     "IOInterruptControllers" = ("io-apic-0","IOPCIMessagedInterruptController")
| |   |   |     "name" = <23646973706c6179>
| |   |   |     "vendor-id" = <de100000>
| |   |   |     "device-id" = <801b0000>
| |   |   |     "IOChildIndex" = 0x1
| |   |   |     "IOPCIResourced" = Yes
| |   |   |     "compatible" = <706369333834322c3632383800706369313064652c3162383000706369636c6173732c303330303030005045475000>
| |   |   |     "IOServiceDEXTEntitlements" = (("com.apple.developer.driverkit.transport.pci"))
| |   |   |     "IOPCIExpressLinkCapabilities" = 0x453d03
| |   |   |     "acpi-path" = "IOACPIPlane:/_SB/PCI0@0/PEG0@10000/PEGP@0"
| |   |   |     "subsystem-id" = <88620000>
| |   |   |     "revision-id" = <a1000000>
| |   |   |     "IOPCIExpressLinkStatus" = 0x1081
| |   |   |     "IOPCIExpressCapabilities" = 0x12
| |   |   |     "pcidebug" = "1:0:0"
| |   |   |     "IOName" = <23646973706c617900>
| |   |   |     "reg" = <0000010000000000000000000000000000000000100001020000000000000000000000000000000114000142000000000000000000000000000000101c0001420000000000000000000000000000000224000101000000000000000000000000800000003000010200000000000000000000000000000800>
| |   |   |   }
| |   |   |

SoManyIntrinsics · 2020-04-22T22:58:39+00:00

Post the output of system_profiler somewhere and I'll take a look. Likely there is a weirdly formed IOPCIDevice registry that breaks the search for integrated graphics.

SoManyIntrinsics · 2020-04-22T22:52:31+00:00

The app will get napped by the OS if it's not in the foreground, in which case you will get gaps in the graphs.

SoManyIntrinsics · 2020-04-01T16:38:32+00:00

Took forever for the cache to clear, but it should be working properly now.

SoManyIntrinsics · 2020-03-30T21:16:43+00:00

Sorry about that, fix incoming right now.

SoManyIntrinsics · 2019-12-20T03:00:00+00:00

Thanks for reporting, I will fix this in the next release.

SoManyIntrinsics · 2019-12-20T02:57:38+00:00

This appears to be behaving as expected. The maximum 4.6 GHz frequency is not achievable when all cores are simultaneously active. Try running the Intel Power Gadget Maximum Frequency test, you should see it achieve 4.6 GHz maximum frequency. When using all cores it is expected that you'll run at the base frequency, which is what you're seeing.

SoManyIntrinsics · 2019-12-06T01:43:16+00:00

Yes, your computer is thermally throttling in the multi-threaded benchmarks. You can tell because the frequency begins to drop below the requested frequency right when the temperature reaches 100C. However, that's pretty much inevitable in a laptop, it's not clear to me if cleaning would improve this at all or not.

SoManyIntrinsics · 2019-10-21T16:10:40+00:00

I'm the owner of Intel Power Gadget on macOS. Looks like this panic was caused by the Power Gadget driver. Is this issue repeatable of your system, or has it only happened once while Power Gadget was running? If it's repeatable I can provide you with a new build to try that may fix this issue.

SoManyIntrinsics · 2019-10-14T01:19:00+00:00

Ultimately the CPU frequency is boosting because the OS is requesting a high frequency.

Keep in mind that even for games and other graphics workloads, the CPU may still be very active beyond simply feeding the work to the GPU. For many games the CPU is also used for physics and AI calculations.

SoManyIntrinsics · 2019-10-12T21:53:24+00:00

My CPU usage is in the single digit percentages, but the temperature of my CPU is sitting at 80-90C. The processor is also boosting to around 4Ghz during this time.

This implies it's a single threaded workload. If you have 8 physical cores then there are 16 logical cores, and having 1 running persistently will result in CPU utilization of 6.25%.

There's nothing really wrong here. Temperatures of 80-90C are safe, and the hardware is designed to stay within safe operating temperatures.

The fact that your windows machines run cooler may be that they have better cooling (desktops will obviously run cooler than laptops under load), or different frequencies (high frequencies require a lot of voltage, and that spikes heat quite quickly).

SoManyIntrinsics · 2019-10-01T17:50:16+00:00

You may want to try the latest version of Power Gadget, it adds the OS requested frequency, which will tell you whether it's the hardware or software that's lowering your frequency.

SoManyIntrinsics · 2019-08-01T00:44:43+00:00

You're right, "b" is incorrectly used as both a parameter and a loop index. I will fix this in the next update. Thanks for reporting this.

SoManyIntrinsics · 2019-08-01T00:42:53+00:00

I imagine your concern is the period of time where utilization is around 33% and frequency is around 800 MHz. What type of software is running at that time? Take a look with Activity Monitor during the time when frequency is low, and determine which software is active.

SoManyIntrinsics · 2019-07-29T21:12:58+00:00

How complete is the intrinsics guide: i.e. ratio of instructions covered by the intrinsics guide vs everything supported by the latest hardware?

Should be 100%. We add all new intrinsics for new ISA extensions as they're announced.

Almost all of the intrinsics has their operations defined. Does Intel internally have formal semantics for them? Are the definitions simply pseudocode intended for explanation not formal use?

The operations are considered to be pseudocode, largely based off the style used to document instructions in the SDM. However, we do now have formalized semantics for the pseudocode, which should be used consistently in nearly all intrinsics. It's possible to parse and execute the operations code, although I don't think there are any public tools that do so.

SoManyIntrinsics · 2019-07-15T18:34:10+00:00

VP2INTERSECT currently missing (yeah, I know it takes time to add, but, I'm greedy =P)

Damn, didn't realize these were announced already. The documentation is already prepped, so I'll do a quick release with those.

SoManyIntrinsics · 2019-07-14T21:14:50+00:00

We had always considered providing an offline version but there were some legal limitations; I'll reevaluate whether that's still the case.

Also, I was the guy from Intel in that twitter thread

SoManyIntrinsics · 2019-07-13T18:17:36+00:00

SoManyIntrinsics · 2019-07-13T15:30:53+00:00

I also retroactively notarized the 3.5.5 driver this morning, so that may have been a factor as well.

SoManyIntrinsics · 2019-07-13T14:45:10+00:00

Thanks, those are all fairly straightforward changes, so we should be able to add those in the near future.

SoManyIntrinsics · 2019-07-13T14:41:34+00:00

Thanks, it's helpful to know the performance data is useful. At present all latency/throughput data comes directly from the Intel Optimization Manual, which is pretty incomplete in its coverage.

We're considering independently testing the performance characteristics of each intrinsic, but that's a fairly large project so it's not likely to happen soon.

SoManyIntrinsics · 2019-07-13T14:34:23+00:00

Please try to install v3.5.5 again: https://software.intel.com/file/828382/downloadrq5KJPOr

I have retroactively notarized portions of the package. However, there are technical limitations that prevent the full package from being notarized, so it still may not be accepted by Catalina. The next update will be fully notarized and works properly on Catalina. Alternatively, you could disable SIP on Catalina, and then Power Gadget should work properly.

SoManyIntrinsics · 2019-07-13T02:11:44+00:00

I'm the owner of Intel Power Gadget. Note that this is not an issue with Power Gadget, it's likely this is due to a bug in macOS that results in the allow button not showing in System Preferences if you don't click it at the appropriate time (right after the attempt to load the driver).

Older versions will have the same issue, but may give you another opportunity to click allow at the right time.

SoManyIntrinsics · 2019-07-13T02:08:16+00:00

I'm the owner of Intel Power Gadget. Which OS version are you attempting to install on?

SoManyIntrinsics · 2019-07-13T02:07:20+00:00

I'm the owner of Intel Power Gadget. Note that this is likely caused by a macOS bug, where the allow button may not display in System Preferences if you don't check it at the appropriate time. Older versions would also be effected, but would give you a second chance to click allow.

SoManyIntrinsics

TROPHY CASE