Viewing profile — emily-c
emily-c
HN member- Joined
- Mon, Nov 09, 2015, 9:45 PM UTC
- HN karma
- 315
- Public activity
- 57 items
- HN profile
- View on Hacker News ↗
About emily-c
https://www.linkedin.com/in/emily-c/
Recent public activity
-
comment
Comment #49252035
On commodity PC platforms there are both upsides and downsides of having runtime firmware in a special mode like SMM (or the secure world on ARM64 which is a whole other topic). Fo…
-
comment
Comment #41492967
>In many ways NT was a new, ground up implementation of “VMS NT”. Most definitely. There was a lot of design cleanup from VMS (e.g. fork processes -> DPCs, removing global PTEs and…
-
comment
Comment #41491817
Before VMS there was the family of RSX-11 operating systems which also had ASTs (now called APCs in NT parlance), IRPs, etc. Dave Cutler led the RSX-11M variant which significantly…
-
comment
Comment #38922244
>I don’t think anyone has ever bothered to make FS code async, it’s already quite horrible as it is. Not in a mainstream kernel anyway. [...] Same for Windows disk IO with IOCPs. I…
-
comment
Comment #38102587
I hope this is a joke.
-
comment
Comment #36172846
"Embedded software" and "embedded system" also have similar issues with being nebulously defined in various situations. Some things will never perfect and at least firmware is kind…
-
comment
Comment #36132839
Usually this is still host firmware and not a secondary controller, at least on x86 platforms. To detect/use the USB controller you still need to configure the chipset/root complex…
-
comment
Comment #35965143
Recording of the opening: https://www.youtube.com/watch?v=Dfd6J3M-FSk
-
comment
Comment #35852848
Thanks :) I wish there was a consolidated list of what kinds of information gets measured that is easy to point to.
-
comment
Comment #35848790
Unfortunately, I don't believe there is any up to date and detailed public documentation on the modern DRTM flows that exist on both Intel and AMD platforms. Maybe documentation ha…
-
comment
Comment #35848680
DRTM does not remove any malicious firmware provided code or data. Traditionally it is merely a measurement mechanism that happens after ExitBootServices which measures platform st…
-
comment
Comment #35847134
>Did we mention that a TPM isn’t going to protect you from UEFI malware that was planted on the device by a rogue agent at manufacture time? DRTM, a technology supported by Windows…
-
comment
Comment #27657511
I am talking about the platform more than the ISA. Some interesting resources: https://sites.google.com/site/pinczakko/system-address-map-i... https://www.youtube.com/playlist?list…
-
comment
Comment #27657138
I'm not sure why you have legacy in quotes, that is what it is. Modern platforms do not act like a PC AT and there is a ton of cruft to keep those interfaces working which is set u…
-
comment
Comment #27656329
These are good examples and this might be slightly off topic but I wish that there were more resources on how modern x86 platforms actually work instead of using these legacy inter…
-
comment
Comment #27582618
A lot of critical system configuration is stored in the SYSTEM hive which isn't explicitly backed by a file mapping and is loaded at boot via firmware services so this will be fast…
-
comment
Comment #26297119
This is awesome. It’s always nice to see new Win32 productivity software. Thank you!
-
comment
Comment #25838309
This is correct. The functionality of LOADALL now largely happens in the RSM instruction which returns back to normal execution context from an SMI. In modern firmware, before the …
-
comment
Comment #22656847
Most legacy code is this way unfortunately. The actual techniques employed by the "called out" code are not uncommon. I don't think that people are defending the lack of clarity bu…
-
comment
Comment #22656222
You see similar code to his unconditional executeNoMatch at the end of the table in table based code all the time. Additionally forEachObject is a macro that immediately initialize…
-
comment
Comment #22521433
I second every book recommendation here. Another great one is The Standard C Library .
-
comment
Comment #22170610
This is still pretty common for things like self extracting archives on Windows. copy /b "%windir%\system32\extrac32.exe"+inputarchive.cab selfextract.exe
-
comment
Comment #22153869
It is still possible but is BIOS dependent :) With UEFI, graphics is preferred to be done with the GOP driver/protocol (which will ultimately interact with video BIOS/graphics card…
-
comment
Comment #22153603
You're still relying pretty heavily on the BIOS to write to this region that you otherwise wouldn't be. Getting the legacy framebuffer region set up to be decoded to the graphics c…
-
comment
Comment #22096377
You use WinDbg and do kernel debugging. The newer WinDbgX UI is quite nice lately. However, there's no replacement for live debugging on the same machine the way that SoftICE did i…