Skip to content

Instantly share code, notes, and snippets.

@arekinath
Last active February 20, 2018 08:26
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save arekinath/cd77d5ad02eacb281bd4f7de405ec468 to your computer and use it in GitHub Desktop.
Save arekinath/cd77d5ad02eacb281bd4f7de405ec468 to your computer and use it in GitHub Desktop.

KPTI to-do list

  • Nicer way to generate MACHCPU_PAD? Maybe break the structs up?
  • int $8 push logic: use addr instead of zero at (%rsp), maybe? seems hacky.
  • Copyrights and cstyle and shiz
  • loader support for kpti=0 flag?
  • verbose boot message confirming kpti status

Testing to-do list

  • Exhaustive trap tester
  • Test weird floating point things like #XM, #MF and so on
  • Test NMI in bad situations (maybe put an infinite loop in a trampoline?)
  • Find a box that takes MCEs a lot
  • #BR?
Copy link

ghost commented Feb 5, 2018

I believe Solaris 10 Branded Zones are currently broken and have been for quite some time. We have to run our last remaining S10 zones on an older SmartOS release (our own build):

uname -v

everycity_20131114T173308Z

So I wouldn't worry too much.

@arekinath
Copy link
Author

@alaslums I'm sorry to hear that :| Would you mind filing a bug about it on the illumos-joyent github? I guess we'll come back to that some time in the future. Hopefully we haven't broken it any more than it already was, anyway.

Copy link

ghost commented Feb 14, 2018

@arekinath I'm not sure there's any benefit in maintaining/keeping Solaris 10 binary compatibility in illumos given that we're probably the only people using it ;-) We're not fussed about it as we only have a few zones that are due to be decommissioned.

I'm also not sure about filing an illumos bug on this as I don't have the technical information to hand regarding whether the issue relates to the Joyent fork of illumos specifically or is in illumos proper. "Solaris 10 Zone compatibility possibly broken" sounds a little vague ;-)

Copy link

ghost commented Feb 14, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment