Live data from Hacker News

Viewing profile — andreiw

andreiw

HN member
Joined
Mon, Nov 24, 2014, 11:04 PM UTC
HN karma
289
Public activity
209 items

About andreiw

No profile information was provided.

Recent public activity

  1. comment
    Comment #17545761

    Dumb question, but how would it fare on a ppc64le box like the (OpenPower) Power9 Talos II? https://www.raptorcs.com/TALOSII/prerelease.php

  2. comment
    Comment #17351587

    On a related note, another interesting CPU design - http://multiclet.com/index.php/en/support/general-technical-...

  3. comment
    Comment #17351526

    Also 64-bit Arm...

  4. comment
  5. comment
    Comment #17308279

    Yeah I’d say that modern OoO Arm implementations (A57, A72, ...) are worth trying to speculate into trapped VFP state. Lazy FPU is definitly a thing everywhere. My hunch says that …

  6. comment
    Comment #17307510

    Not numerating it? Variant 6 is as good as anything...

  7. comment
    Comment #17307501

    Do we have PoC code? Has anyone tried attacking FP/SIMD state on other ISAs like Power or AArch64?

  8. comment
    Comment #17307485

    What are we calling this Spectre variant?

  9. comment
    Comment #17200304

    As usual, Carl Icahn...

  10. comment
    Comment #17200286

    Then tell your SiP to do better. On Arm the conditional speculation barrier couldn’t be more lightweight (CSDB).

  11. comment
    Comment #17190196

    “break”? no, but spectre is a confidentiality attack, and not even the only confidentiality attack that can be done... yes you could, but the noise floor won’t be great

  12. comment
    Comment #17190168

    Depends on how you define hardware and software. There are global workarounds that amount to crippling CPU behavior, to provide guarantees for code not written to be spectre safe. …

  13. comment
    Comment #17190134

    Considering the hardware mitigations aren’t some magic bullet, but are a “big hammer” that cripples CPU OoO behavior in crrtain ways for everything , software mitigations don’t see…

  14. comment
    Comment #17079010

    Anyone else use the hex “assembler” on the TI-83+? After a while you just memorize the hex opcodes for z80 insns... TI-GCC for my TI-89 was nice...a few years back I tried to dust-…

  15. comment
    Comment #16950671

    Not yet... the good news is that iPXE supports the SMSC USB NIC on the Pi. I don't know if iPXE will work out of the box, but I certainly intend on porting the iPXE NIC driver as a…

  16. comment
    Comment #16950664

    Maybe. I'll look.

  17. comment
    Comment #16925369

    There's a few problems there, but these amount to UEFI being a terrible, abominable spec. The specification doesn't say that an implementation must not change the memory map inside…

  18. comment
    Comment #16924518

    Author here, feel free to AMA.

  19. comment
    Comment #16924501

    If you run the “mmap” command in UEFI shell, and count the memory regions marked as Runtime Code and Runtime Data, that will give you the total resident (after booting OS) memory f…

  20. comment
    Comment #16924487

    Yep, and being able to claim that U-boot can boot Windows (on x64 or Arm) would be a really strong statement around completeness. I hope someone gets to work on it soon (Alexander …

  21. comment
    Comment #16924460

    RaspberriPiPkg can’t boot Raspbian today, since the latter is 32-bit. Can boot stock 64-bit SUSE and Ubuntu, though.

  22. comment
    Comment #16924446

    A lot of it really is code quality issues, both in the core and some of the contributed I/O drivers.

  23. comment
    Comment #16924435

    Author here. If you wanted to run you own drivers, or had code written specifically against protocols exported by Tiano components I believe the answer is - yes. RaspberryPiPkg is …

  24. comment
    Comment #16861766

    Actually, good question to flip back to you. As a random person stumbling upon this, what value would you assign to it? What could you imagine the end goal to be?

  25. comment
    Comment #16861754

    Arm derived: 32-bit Cortex-A and a Cortex-M for radio. Curious what the security arch is...