neel 46721cc2c7 Restructure the MSR handling so it is entirely handled by processor-specific
code. There are only a handful of MSRs common between the two so there isn't
too much duplicate functionality.

The VT-x code has the following types of MSRs:

- MSRs that are unconditionally saved/restored on every guest/host context
  switch (e.g., MSR_GSBASE).

- MSRs that are restored to guest values on entry to vmx_run() and saved
  before returning. This is an optimization for MSRs that are not used in
  host kernel context (e.g., MSR_KGSBASE).

- MSRs that are emulated and every access by the guest causes a trap into
  the hypervisor (e.g., MSR_IA32_MISC_ENABLE).

Reviewed by:	grehan
2014-09-20 02:35:21 +00:00
..
2013-03-17 06:54:04 +00:00
2013-07-10 07:40:30 +00:00
2014-07-29 19:49:27 +00:00
2014-07-07 00:27:09 +00:00
2014-07-17 06:57:26 +00:00
2012-10-07 19:53:04 +00:00
2014-07-29 19:49:27 +00:00
2012-03-26 21:22:53 +00:00
2014-09-13 18:40:12 +00:00
2014-07-07 00:27:09 +00:00
2014-09-19 23:38:44 +00:00
2013-04-11 18:46:41 +00:00
2012-05-17 11:50:12 +00:00
2014-07-18 06:48:02 +00:00
2014-08-06 22:17:26 +00:00
2014-07-29 19:49:27 +00:00
2013-09-07 20:25:22 +00:00
2014-09-01 16:12:29 +00:00
2014-09-08 09:16:07 +00:00
2012-03-26 21:22:53 +00:00