WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

RE: [Xen-ia64-devel] [PATCH]: allow hypercalls only from kernels.

To: "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>, "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>, "Alex Williamson" <alex.williamson@xxxxxx>
Subject: RE: [Xen-ia64-devel] [PATCH]: allow hypercalls only from kernels.
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Tue, 21 Mar 2006 10:07:17 +0800
Delivery-date: Tue, 21 Mar 2006 02:08:36 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZMIcjByX+WHNNzQL6TtW8zxpRmWgAaOgOA
Thread-topic: [Xen-ia64-devel] [PATCH]: allow hypercalls only from kernels.
>From: Tristan Gingold
>Sent: 2006年3月20日 21:28
>To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx; Magenheimer, Dan (HP Labs
>Fort Collins); Alex Williamson
>Subject: [Xen-ia64-devel] [PATCH]: allow hypercalls only from kernels.
>
>Hi,
>
>this patch complete the previous one.
>Hypercalls are only allowed from kernels.
>I have added an 'unsafe_hypercall' boolean command line option to
>enable the
>two debugging hypercalls.  This option is disabled by default, as it may
>be
>used to write in the kernel area.
>
>Tested by boot+shutdown of dom0+domU (option off).
>Tested by boot of dom0 + postat (option on).
>
>Tristan.

Hi, Tristan,
        Good work, and I guess you may want to add an incremental patch 
upon this one. As your concern in the comment, simply return a failure to 
guest doesn't conform to generality well. It's possible that hardcode 
hypercall iim conflicts with guest meaningful iim. Even not, it's better to let 
guest kernel handle the case, like to kill that problematic process. 
Application should observe same behavior exactly like on real system 
where it breaks a kernel-unsupported iim. So a break fault needs to be 
fired back to guest.

Thanks,
Kevin

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

<Prev in Thread] Current Thread [Next in Thread>