On 2016-03-24 at 18:12 Gan Shun <[email protected]> wrote: > This is on my branch vmm-msr > > We now have date running. > > The following changes since commit > 24c7dd20c8a5a6983083c97d7492a994c67355d0: > > Upgrade parlib fp state handling, use proc_global_info (XCC) > (2016-03-22 16:54:53 -0400) > > are available in the git repository at: > > [email protected]:GanShun/akaros.git HEAD
Thanks! Merged to master at 9cfe7eab94eb..82f3db6bf2c9 (from, to] You can see the entire diff with 'git diff' or at https://github.com/brho/akaros/compare/9cfe7eab94eb...82f3db6bf2c9 For my own clarification, these MSRs will only kick in when the VMX hardware doesn't handle it in some manner, right? Specifically, for the APIC MSRs, our current setup is: - All MSR reads are allowed by the hardware (k/a/x/v/i/vmx.c@1318) - MSR writes to EOI, TPR, and SELF_IPI are allowed (""@1320-1322) For the reads and those specific writes, the VMX hardware performs the operation directly on the VAPIC page, right? (that's the picture I have drawn in my notebook). So the MSR reads probably never make it to userspace at all (since the kernel never saw the MSR_READ vmexits), and only a few of the writes do. I dropped a printf in vmxmsr and didn't see it fire, so it seems like this is right. Barret -- You received this message because you are subscribed to the Google Groups "Akaros" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
