Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> writes:
On 09/25/2015 03:35 PM, Konrad Rzeszutek Wilk wrote:Xen hypervisor doesn't analyzie the reason, it is being analyzed by the
On Fri, Sep 25, 2015 at 03:19:57PM -0400, Boris Ostrovsky wrote:OK. But the I don't see anyone checking that 'reason' (or
On 09/25/2015 03:01 PM, Konrad Rzeszutek Wilk wrote:The hypervisor ends up calling:
On Fri, Sep 25, 2015 at 01:17:40PM -0400, Boris Ostrovsky wrote:That's toolstack issuing hypercalls from dom0.
On 09/25/2015 12:07 PM, Vitaly Kuznetsov wrote:Yes:
OK, so I was looking at the right tree. Then I don't understand howAlso, I am not sure I see how this new op will be used in thePlease see my Xen series:
hypervisor --- currently AFAICS it is only processed under
is_hardware_domain(). Are there other patches that will support HVM
(last 'full' submission).
All patches from my 'toolstack-assisted approach to PVHVM guest kexec'
are already merged to xen.git (first 10 are already in 'master' and the
last one is in 'staging').
SHUTDOWN_soft_reset would be reached for a non-privileged domain. The only
path that I see is
if ( is_hardware_domain(d) )
Is there another path to handle this op?
e1bd9812966de9a16f30a58e7162b80bd6af361b libxc: support XEN_DOMCTL_soft_reset operation
c57e6ebd8c3e490e353e68d96abec1dad01e72f5 (lib)xl: soft reset support
I am asking about (non-privileged) guest itself calling SCHEDOP_shutdown.
__domain_finalise_shutdown which sends an VIRQ_DOM_EXC to dom0 which
makes the toolstack do all of those operations.
'shutdown_code') is SHUTDOWN_soft_reset. In other words, the guest can
do 'xen_reboot(23)' or 'xen_reboot(154)'. Or, it seems, even
'xen_reboot(SHUTDOWN_reboot)'? The only value it shouldn't be is
toolstack (XEN_DOMCTL_getdomaininfo returns this info encoded in flags
with XEN_DOMINF_shutdownshift shift).