aionescu

4 ms·

1.
by aionescu 9y ago
Got some numbers/public information? Would love to know more.
2.
SimpleVisor: a simple, Intel x64 Windows-specific hypervisor(ionescu007.github.io)
3 points by aionescu 11y ago|0 comments
3.
by aionescu 11y ago
Author here. The problem I was trying to get to is that VSM allows itself to be activated without SB (which as you note, can also be done with malicious SB) and therefore there is no way to really 'trust' the VSM implementation. P
4.
by aionescu 12y ago
Actually, AMD basically forgot to implement the instruction. It was in the manuals.
5.
by aionescu 12y ago
Indeed, static libs caused massive duplication and not-always-correct source location in my script. Nice catch :)
6.
by aionescu 12y ago
Actually, static and dynamic libs also show up, as do resource files. So I guessed that .obj is .c (not always accurate), .res is .rc, and dynamic .lib is .exp, and so on and so forth.
7.
by aionescu 12y ago
I hardcoded the .obj extensions to .c -- it's not accurate because of that.
8.
by aionescu 12y ago
The build number comes from the build server, and isn't accurate I believe. Some pretty recent functionality is in the file list, including mobilecore, mincore, and other "One Windows" refactorings from Windows 10.
9.
by aionescu 12y ago
I never worked or interned at Microsoft :)
10.
by aionescu 12y ago
Yep -- if you listen to the talk you'll see I made that joke on purpose :)
11.
by aionescu 13y ago
Yes, my point was that the OS isn't currently doing it on its own, putting the onus on the driver developers -- which have limited information available to them and are pretty much unable to make the right choice -- unless we're talking abo
12.
by aionescu 13y ago
Spreading DPCs across cores will lead to two possibilities: - Typical driver dev: Knows nothing about DPC Importance Levels, and sticks with medium (default): IPIs are not sent to idle cores, so device experiences huge latencies as the DPC
13.
by aionescu 13y ago
Targeting the DPC provides absolutely no help -- how will you as a driver know what core to target to? It's typical design-by-MSDN: provide a feature that looks useful and people will quote, but actually provides no benefits. Drivers target
14.
by aionescu 13y ago
A simple problem is that DPCs are not scheduled in any way (there's some very primitive queueing and delivery algorithms), or more importantly, are not scheduled in any way that correlates with the thread scheduler's view. So between four c