All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>,
	Mirela Simonovic <mirela.simonovic@aggios.com>
Cc: Oleksandr Tyshchenko <olekstysh@gmail.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Xen Devel <xen-devel@lists.xen.org>
Subject: Re: [RFC v2] xen/arm: Suspend to RAM Support in Xen for ARM
Date: Fri, 26 Jan 2018 15:37:49 +0000	[thread overview]
Message-ID: <400ce04f-2c3b-5020-00af-d44a148a23c0@linaro.org> (raw)
In-Reply-To: <20180125141544.GD1706@toto>

Hi Edgar,

On 25/01/18 14:15, Edgar E. Iglesias wrote:
> On Wed, Jan 24, 2018 at 07:04:35PM +0100, Mirela Simonovic wrote:
>> Hi Oleksandr, Edgar,
>>
>>
>> Thanks, you're right.
>>
>>
>> On 01/23/2018 12:58 PM, Edgar E. Iglesias wrote:
>>> On Tue, Jan 23, 2018 at 01:52:50PM +0200, Oleksandr Tyshchenko wrote:
>>>> Hi Mirela,
>>>>
>>>> Just some remarks regarding the scope of work:
>>>>
>>>> +In addition, the following have to be implemented:
>>>> +* Suspend/resume vCPU (triggered by vSYSTEM_SUSPEND call)
>>>> +* Suspend/resume Xen (triggered by vSYSTEM_SUSPEND called by Dom0), including:
>>>> +       * Disable wathdog on suspend, enable it on resume
>>>> +       * Pause domains on suspend, unpause them on resume
>>>> +       * Disable non-boot pCPUs on suspend, enable them on resume
>>>> +       * Save/restore of GIC configuration
>>>> +       * Suspend/resume timer
>>>> +       * Save/restore of EL2 context
>>>> +       * Implement resume entry point in Xen, including MMU configuration
>>>>
>>>> I think that saving/restoring IOMMU registers/context should be
>>>> implemented as well.
>>> Yes, good point.
>>> Mirela, I think that in the ZU+ case the IOMMU actually gets powered down
>>> with the FPD.
>>
>> Yes, it is in FPD.
> 
> Having said that it may still be useful from a patch review perspective
> to incrementally add things. Perhaps the IOMMU suspending support could
> come in follow-up patch series if others agree.

+1 :). I suspect the suspend/resume patch set will be quite big. So 
anything that can help the review (e.g splitting patch series, moving 
out some parts of the initial work...) would be greatly appreciated.

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-01-26 15:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22 17:41 [RFC v2] xen/arm: Suspend to RAM Support in Xen for ARM Mirela Simonovic
2018-01-11  0:55 ` Stefano Stabellini
2018-01-11 14:00 ` Julien Grall
2018-01-23 11:52   ` Oleksandr Tyshchenko
2018-01-23 11:58     ` Edgar E. Iglesias
2018-01-24 18:04       ` Mirela Simonovic
2018-01-25 14:15         ` Edgar E. Iglesias
2018-01-26 15:37           ` Julien Grall [this message]
2018-01-24 17:55   ` Mirela Simonovic
2018-01-26 16:08     ` Julien Grall
2018-04-17 12:13       ` Mirela Simonovic
2018-03-26  9:51 ` Peng Fan
2018-03-26 11:42   ` Edgar E. Iglesias
2018-04-12  2:26     ` Peng Fan
2018-04-12 14:13       ` Mirela Simonovic

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=400ce04f-2c3b-5020-00af-d44a148a23c0@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=edgar.iglesias@xilinx.com \
    --cc=mirela.simonovic@aggios.com \
    --cc=olekstysh@gmail.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.