qemu VS UnnaturalScrollWheels

https://gitlab.com/qemu-project/qemu/-/blob/master/hw/scsi/s...

QEMU's IOThreads allow the user to configure the threads and get something similar to thread per core architecture. But if 1 thread becomes a bottleneck, then some form of thread synchronization is needed again even with thread per core architecture. Some problems can be parallelized and they work well with thread per core.

Add `ENV ERL_FLAGS="+JPperf true"` to your Dockerfile and it will build just fine cross platform. The flag just changes some things during build time and won’t affect runtime performance.

[1] https://gitlab.com/qemu-project/qemu/-/issues/1034

> I don't know how rdcycle works on qemu.

That's a good question! I had to look it up myself ...

Obviously qemu TCG isn't a cycle-accurate emulation. Using RDCYCLE / reading the corresponding CSR eventually calls https://gitlab.com/qemu-project/qemu/-/blob/69680740eafa1838... which calls cpu_get_host_ticks is basically an arch-independent wrapper around RDTSC.

So it just measures the time taken to run using RDTSC. Which I guess is what you would want (maybe?). It would measure the time taken to emulate the vector instruction in host instructions.

> This benchmark is more meant for developers to figure out how to vectorize algorithms effectively, as in which instructions to choose.

Absolutely, I'm not saying the qemu results would say anything very deep, but they're kind of interesting from the point of view of either optimizing qemu or if you have to use qemu because the hardware you want isn't available / isn't cheap enough.

I see the commits that started switch support from RVV 071 to 100 start here, https://gitlab.com/qemu-project/qemu/-/commit/9ec6622db30df1c00d863c1ffc33341f9e0a534d

>> https://gitlab.com/qemu-project/qemu/-/issues/1696 ]

> Can I please just get the detail in mail instead of having to go look at random websites?

Maybe it's me but if I did boot boot linux 292.612 times to find a bug, you might as well click a link to a repository of a major open source project on a major git hosting service.

Is it really that weird to ask people online to check a website? Maybe I don't know the etiquette of these mail lists so this is a geniune question.

Capstone is used[1] by QEMU as disassembly engine in debug logs and in monitor mode debugger, by the way, so it's in the scope of the RISE effort.

[1] https://gitlab.com/qemu-project/qemu/-/blob/master/disas/cap...

A user on the qemu bugtracker found a way to get the Intel Arc working across resets without crashing the host: Just don't passthrough the audio device of the GPU and everything works!

[1]https://gitlab.com/qemu-project/qemu/-/commit/3412d8ec9810b819f8b79e8e0c6b87217c876e32 [2]https://gitlab.com/alex.williamson/qemu/-/commit/9a6d1822a2bd55f5dee1aec1b6529ae57949d5ba.patch

For gaming, you want to use Crossover or the FOSS Whisky app. Parallels only runs Arm Windows which then emulates x86. This is much much slower than using Wine to translate system calls and Apple's Game Porting Toolkit to handle the Vulkan or DirectX graphics. Crossover and Whisky take care of the internals of those for you. Give those a shot, I think you'll find it much better than a full VM. In my experience some games do run better this way than the MacOS versions, though that's usually because the Mac client wasn't compiled for Apple Silicon and so Rosetta is emulating. Unfortunately, I'm pretty sure WOW is already Apple Silicon native, so you probably won't get better performance this way.

For the mouse stuff, try a USB mouse if you're not already using one, combined with https://github.com/ther0n/UnnaturalScrollWheels

That works really well for me to get a Windows-like mouse curve.

TLDR skip the emulation and go for translation layers via Crossover, Whisky, and GPT. It'll be much faster. The mouse thing is separate and has nothing to do with the graphics layer.

------

Personally though, I'd just pay $20 a month for Geforce Now. It is much much faster than even the highest end Mac.

Was the utility UnnaturalScrollWheels?

I use this tool to keep natural scrolling on trackpad and normal scrolling on my wheely mouse: https://github.com/ther0n/UnnaturalScrollWheels

A Free Tool UnnaturalScrollWheels is a MacOS app that allows you to invert the scroll direction for physical scroll wheels while maintaining the normal function for trackpads. aew3 recommends it "for those like me who go between dock and laptop and prefer my mouse to have a different scroll direction to the trackpad." Another Free Tool Locust is an open-source load testing tool that allows you to define whatever user behavior you like, and then swarm your system with millions of those users simultaneously. certTaker suggests, "If you want to test an actual application and how it handles network latency, potential buffering, QoS etc, then you could use Locust to stress-test REST-based applications and their APIs." A Tip Synssins shares a method for replacing an older Windows File Server with new, while keeping all shares and DNS intact:

UnnaturalScrollWheels is a MacOS app that allows you to invert the scroll direction for physical scroll wheels while maintaining the normal function for trackpads. aew3 recommends it "for those like me who go between dock and laptop and prefer my mouse to have a different scroll direction to the trackpad."

“For some reason in macOS, toggling the "Scroll direction: Natural" option in Mouse settings also changes it in Trackpad settings despite being in separate places.” Check out this app too which also takes care of acceleration. https://github.com/ther0n/UnnaturalScrollWheels