Debug Engineer. Windows, drivers and all things kernel mode. I express my views, not my employer's. My views are my own and just my personal opinions.
Joined December 2012
- Tweets4.9K
- Following1.3K
- Followers2.9K
- Likes7.7K
Pinned Tweet
"I have no experience writing Windows drivers. Now I wrote one and without my driver everything works fine but with my driver Windows crashes all the time and my driver is on the callstack. Can you debug Windows for me? It crashes and I don't think my driver causes that"
#KillMe
PSA: Always use both versions and Windows memory test (on Windows of course). I have seen broken memory when one passes but not the other.
When you work for a chipmaker, let's just say you have to run memory checks every now and then... ;)
Finally the opensource version of memtest86 supports Arm.
Passmark's proprietary memtest86 is still slightly superior in it's post test evaluations, especially for DDR5 but for a decent and reliable test the opensource memtest86 is still really good.
phoronix.com/news/memtest86-…
Oh my God! Science has to figure out something unknown?! Nooooooooo!!!!!
Performance is determined by the compiler, not the language. Crappy C compiler will loose to great Rust compiler and vice versa. Compile, measure, inspect assembly, understand and measure. Experiment.
Maybe you can beat this compiler, or maybe it is not worth it.
It is entirely possible to have great compiler and not so great programmer who chose bad was to locate the data and cannot take advantage of space locality. Rewrite might choose a container that C just doesn't have and take full advantage of cache. Result will be improved perf.
That's like one chip these days, right?
US arrests tech CEO accused of smuggling $300M in Nvidia chips into China arstechnica.com/tech-policy/…
It tells us that a lot of people have "negative knowledge" - they need to learn something first to know nothing at all.
Or, in a simpler terms, whatever they know is just not true.
;)
I’m hearing this a lot lately. “AI alone is already better than AI + doctor.” (Last heard here @x @FutureJurvetson). If true, what do you think this tells us?
And by "check the logs" we mean we ask AI agent to check the logs and produce a report which we don't check but we have another AI agent which reads the reports and sends us a summarize email which we occasionally ask email AI to summarize if we don't forget.
Listen to @davepl1968 . NT meant N10 which was the code name for one variant of Intel i860 RISC processor - one of the first targets for the new OS. It was not called Windows at the time either, it was OS/2 3.0 (with 2.0 being developed by IBM).
You can still see a glimps of that distant past in the WDK header file ntstatus.h: "Portable Systems Group 30-Mar-1989",
codemachine.com/downloads/wi…
Fan fact: we used to put "SHOWSTOPPER:" in the title of NT bugs for highest criticality bugs when we filed them. They never stopped the show though...
At the end of the Showstopper! there is a very long list of people Pascal Zachary interviewed while writing the book.
I am very fortunate to work on numerous Windows bugs for many many years and I have met many of these people.
@lauriewired have you read the Showstoppers book? Fascinating insight into the development of NT in the late 80s & early 90s. Cutler was (and still is!) a beast. The approach to threading, I/O, completion ports, and how inexorably it was all linked with tight mem mgr, cache mgr, dispatcher, just chef’s kiss. It’s what enabled PyParallel (pyparallel.org) many years ago.
Every time I would ask if they read the book and is it accurate. And i was always told that it is very accurate book.