public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
	xen-devel@lists.xenproject.org, x86@kernel.org,
	David Vrabel <david.vrabel@citrix.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen/pvhvm: add soft reset on kexec/kdump support
Date: Fri, 25 Sep 2015 15:35:41 -0400	[thread overview]
Message-ID: <20150925193541.GG21231@l.oracle.com> (raw)
In-Reply-To: <56059E5D.4000604@oracle.com>

On Fri, Sep 25, 2015 at 03:19:57PM -0400, Boris Ostrovsky wrote:
> On 09/25/2015 03:01 PM, Konrad Rzeszutek Wilk wrote:
> >On Fri, Sep 25, 2015 at 01:17:40PM -0400, Boris Ostrovsky wrote:
> >>On 09/25/2015 12:07 PM, Vitaly Kuznetsov wrote:
> >>>>Also, I am not sure I see how this new op will be used in the
> >>>>hypervisor --- currently AFAICS it is only processed under
> >>>>is_hardware_domain(). Are there other patches that will support HVM
> >>>>guests?
> >>>Please see my Xen series:
> >>>http://lists.xenproject.org/archives/html/xen-devel/2015-09/msg00547.html
> >>>(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').
> >>>
> >>
> >>OK, so I was looking at the right tree. Then I don't understand how
> >>SHUTDOWN_soft_reset would be reached for a non-privileged domain. The only
> >>path that I see is
> >>
> >>     domain_shutdown()
> >>     {
> >>         ...
> >>         if ( is_hardware_domain(d) )
> >>             hwdom_shutdown(reason);
> >>         ...
> >>     }
> >>
> >>Is there another path to handle this op?
> >Yes:
> >  e1bd9812966de9a16f30a58e7162b80bd6af361b libxc: support XEN_DOMCTL_soft_reset operation
> >and
> >  c57e6ebd8c3e490e353e68d96abec1dad01e72f5 (lib)xl: soft reset support
> >
> 
> 
> That's toolstack issuing hypercalls from dom0.
> 
> I am asking about (non-privileged) guest itself calling SCHEDOP_shutdown.

The hypervisor ends up calling:
__domain_finalise_shutdown which sends an VIRQ_DOM_EXC to dom0 which
makes the toolstack do all of those operations.

> 
> -boris

  reply	other threads:[~2015-09-25 19:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25  9:59 [PATCH] xen/pvhvm: add soft reset on kexec/kdump support Vitaly Kuznetsov
2015-09-25 13:59 ` Konrad Rzeszutek Wilk
2015-09-25 15:54   ` Boris Ostrovsky
2015-09-25 16:07     ` Vitaly Kuznetsov
2015-09-25 17:17       ` Boris Ostrovsky
2015-09-25 19:01         ` Konrad Rzeszutek Wilk
2015-09-25 19:19           ` Boris Ostrovsky
2015-09-25 19:35             ` Konrad Rzeszutek Wilk [this message]
2015-09-25 21:00               ` Boris Ostrovsky
2015-09-29 11:39                 ` Vitaly Kuznetsov
2015-09-29 13:08                   ` Boris Ostrovsky
2015-09-28 14:16 ` [Xen-devel] " David Vrabel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150925193541.GG21231@l.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox