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

Re: XSM and the idle domain

  • To: Hongyan Xia <hx242@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, <jbeulich@xxxxxxxx>, <jandryuk@xxxxxxxxx>, <dgdegra@xxxxxxxxxxxxx>
  • From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  • Date: Thu, 22 Oct 2020 13:51:41 +0100
  • Authentication-results: esa5.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none
  • Delivery-date: Thu, 22 Oct 2020 12:52:18 +0000
  • Ironport-sdr: ayDclvKFRdNuUlZcvTc8wwZoFBH417P0zV7UvJO/5QTHiPLiq5XcF8jM+6u7hKMXDBAqxG9POO clqMeZnz9K3SevTcxf9yqypAvC48xd/+JqrnKPBWZW4cVjlbvfPCyW3nINQCT5SSBXYQRbPa7x pPuBNqPM6eRX6rY2mnMC+rUrhvzTpcwsCDMlKqGT33c1xo8Pad9Fs4bdooNBeCqjkOezXLBiCb EAik/6Yu/vPzmsnenLbBlhzPjQ/b/JcwwT3hAfBl1A/6XOORWwkcYc3uaJyPKKmzUo7FNvEtIw tWg=
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 21/10/2020 15:34, Hongyan Xia wrote:
> The first question came up during ongoing work in LiveUpdate. After an
> LU, the next Xen needs to restore all domains. To do that, some
> hypercalls need to be issued from the idle domain context and
> apparently XSM does not like it.

There is no such thing as issuing hypercalls from the idle domain
(context or otherwise), because the idle domain does not have enough
associated guest state for anything to make the requisite

I presume from this comment that what you mean is that you're calling
the plain hypercall functions, context checks and everything, from the
idle context?

If so, this is buggy for more reasons than just XSM objecting to its
calling context, and that XSM is merely the first thing to explode. 
Therefore, I don't think modifications to XSM are applicable to solving
the problem.

(Of course, this is all speculation because there's no concrete
implementation to look at.)




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