[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Blocking CR and MSR writes via mem_access?


  • To: Tamas K Lengyel <tamas.lengyel@xxxxxxxxxxxx>
  • From: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>
  • Date: Tue, 07 Oct 2014 16:06:29 +0300
  • Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
  • Comment: DomainKeys? See http://domainkeys.sourceforge.net/
  • Delivery-date: Tue, 07 Oct 2014 13:05:58 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=bitdefender.com; b=FRK8WYZ62NV+tldEzxW/+SOvi3bivUODWoNpFwqWXRtokbMbKYtr9B6lLv49dWzLDODkaA/0ROUhpHM+D26/QB4cNe+f6LK5ul3Tz26niWOi87FNiO+eUUU20xLhweUzneKJ9pyVNyiy17GKXR0n6/OrIUGxmHp5jnumDDQ30FU5O188I8TBDwdsN5gXTfXwHxlLLnvXnfVcs0bmF8IWVuICX6D6Qtvs1PImhr2P0K/vyyf4TIBRjIYgSwe9jx5cg4bWiqku3f0wGxmowovRyFpc/+JhmQJGA5+DujLXKqf4Uy9/xy4tiyzMdw1//AXUBHPpNPORlg5zrsg3lrVXTQ==; h=Received:Received:Received:Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-BitDefender-Scanner:X-BitDefender-Spam:X-BitDefender-SpamStamp:X-BitDefender-CF-Stamp;
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 10/07/2014 03:58 PM, Tamas K Lengyel wrote:
> 
> 
> On Tue, Oct 7, 2014 at 2:55 PM, Razvan Cojocaru
> <rcojocaru@xxxxxxxxxxxxxxx <mailto:rcojocaru@xxxxxxxxxxxxxxx>> 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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.