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

[Xen-users] A fundamental doubt.


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Anuj Bhatt" <anuj.bhatt@xxxxxxxxx>
  • Date: Thu, 5 Apr 2007 18:23:12 +0530
  • Delivery-date: Thu, 05 Apr 2007 05:52:07 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=puVCNtJRmlqIKZ/zLpc+Cr97QCQcPAu0KsqZc9AX/F5iE+4Bg3NMUzTgjz7GMjnQ4Yj73ETqEL8HgnxECCApOPpcpKT8UQ2mEVfHIJtk7ZVE2atYAnV2JzEfkS8zjWF8aEMEDOGN3eq/5TLtTpEh7wZvUv1/g1deeJ+sgw1vFEQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,

I read an article on the ring architecture of Xen which is based on
the protection ring architecture of x86. It said that the host kernel
as well as the guest xenified kernels run in ring1 and xen on ring0.
Since xen is in ring0 and hypercalls are basically calls made from
user space to kernel space(in this case ring1) how does one block
calls from reaching to dom0 from an event that has occurred from domU?
Is this done by the event channel which is monitored?

Have I got my facts right?

Thanks a ton.

Regards,
Anuj Bhatt.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

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