Re: Blocking CR and MSR writes via mem_access?

[Razvan Cojocaru <rcojocaru@bitdefender.com>]

On 10/07/2014 03:58 PM, Tamas K Lengyel wrote:
> 
> 
> On Tue, Oct 7, 2014 at 2:55 PM, Razvan Cojocaru
> <rcojocaru@bitdefender.com <mailto:rcojocaru@bitdefender.com>> wrote:
> 
>     On 10/07/2014 03:49 PM, Andrew Cooper wrote:
>     > The "xen" ought to be explicit given the prefix on the hypercalls.
>     > "vm-events" as a name?
> 
>     It's a good name.
> 
> 
>     Thanks,
>     Razvan
> 
> 
> Provided that in the future we might want to include events generated by
> hypervisor emulation / memory accesses into this event delivery system
> it might be a bit misleading. Perhaps just events or monitor-events?
> Either way, vm-events is already an improvement and for now it 
> certainly sounds appropriate.

I suppose that it might be possible to send non-VM related events in the
future (unless we count dom0 as a VM and any event not related to
another VM a dom0-related event?). I'd be happy with any of the choices.


Thanks,
Razvan Cojocaru