|
|
|
|
|
|
|
|
|
|
xen-ia64-devel
RE: [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
|
|
|
|
|