All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: James Morse <james.morse@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
	Will Deacon <will.deacon@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Kevin Kang <kkang@intrinsyc.com>,
	Geoff Levand <geoff@infradead.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	AKASHI Takahiro <takahiro.akashi@linaro.org>,
	wangfei <w.f@huawei.com>, Marc Zyngier <marc.zyngier@arm.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 11/11] arm64: kernel: Add support for hibernate/suspend-to-disk.
Date: Mon, 16 Nov 2015 13:41:16 +0100	[thread overview]
Message-ID: <20151116124116.GC9125@amd> (raw)
In-Reply-To: <5649CC40.9010805@arm.com>

Hi!

> On 14/11/15 21:34, Pavel Machek wrote:
> >> The implementation assumes that exactly the same kernel is booted on the
> >> same hardware, and that the kernel is loaded at the same physical address.
> > 
> > BTW... on newer implementations (and I have patch for x86, too), we
> > try to make it so that resume kernel does not have to be same as
> > suspend one. It would be nice to move there with arm64, too. 
> 
> Yes, that is a neat trick, can I leave it as future work?

Yes. But it is really not hard.

> >> + * Because this code has to be copied to a safe_page, it can't call out to
> >> + * other functions by pc-relative address. Also remember that it
> > 
> > PC-relative?
> 
> The linker may (often!) use program-counter relative addresses for loads
> and stores. This code gets copied, so the linker doesn't know where the
> code will be executed from, so any instructions using pc-relative addresses
> will get the wrong result, (if they reference something outside the
> function).

I was wondering if it should be spelled "PC-relative", not
"pc-relative" :-).

> >> + * and executable pages mapped to user space are also written as data, we
> >> + * clean all pages we touch to the PoU.
> > 
> > What is PoC and PoU?
> 
> They are points in the CPU's cache hierarchy:
> 
> ARM processors are of a 'modified Harvard' architecture, their paths to
> read instructions and data are different. The 'Point of Unification' is the
> first point in the cache hierarchy that is the same for both. On ARM,
> flush_icache_range() makes sure code written as data is pushed through any
> data caches to this point, and then evicts any stale copies in the
> instruction caches.
> 
> PoC is the 'Point of Coherency', it is the first point that is the same for
> all devices, (e.g. a cpu with caches turned on, and one with them off), it
> is normally main memory. The kernel text has to be pushed to this point, so
> that secondary cores, while running early-boot code with their MMU and
> caches turned off, don't get incorrect code/data from before resume.
> 
> I have resisted the urge to draw some ascii-art!

That's ok, you just might want to replace PoI -> 'Point of
Unification' and PoC -> 'Point of Coherency' in the comments. That
should make googling easier for people not familiar with arm
terminology.

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 11/11] arm64: kernel: Add support for hibernate/suspend-to-disk.
Date: Mon, 16 Nov 2015 13:41:16 +0100	[thread overview]
Message-ID: <20151116124116.GC9125@amd> (raw)
In-Reply-To: <5649CC40.9010805@arm.com>

Hi!

> On 14/11/15 21:34, Pavel Machek wrote:
> >> The implementation assumes that exactly the same kernel is booted on the
> >> same hardware, and that the kernel is loaded at the same physical address.
> > 
> > BTW... on newer implementations (and I have patch for x86, too), we
> > try to make it so that resume kernel does not have to be same as
> > suspend one. It would be nice to move there with arm64, too. 
> 
> Yes, that is a neat trick, can I leave it as future work?

Yes. But it is really not hard.

> >> + * Because this code has to be copied to a safe_page, it can't call out to
> >> + * other functions by pc-relative address. Also remember that it
> > 
> > PC-relative?
> 
> The linker may (often!) use program-counter relative addresses for loads
> and stores. This code gets copied, so the linker doesn't know where the
> code will be executed from, so any instructions using pc-relative addresses
> will get the wrong result, (if they reference something outside the
> function).

I was wondering if it should be spelled "PC-relative", not
"pc-relative" :-).

> >> + * and executable pages mapped to user space are also written as data, we
> >> + * clean all pages we touch to the PoU.
> > 
> > What is PoC and PoU?
> 
> They are points in the CPU's cache hierarchy:
> 
> ARM processors are of a 'modified Harvard' architecture, their paths to
> read instructions and data are different. The 'Point of Unification' is the
> first point in the cache hierarchy that is the same for both. On ARM,
> flush_icache_range() makes sure code written as data is pushed through any
> data caches to this point, and then evicts any stale copies in the
> instruction caches.
> 
> PoC is the 'Point of Coherency', it is the first point that is the same for
> all devices, (e.g. a cpu with caches turned on, and one with them off), it
> is normally main memory. The kernel text has to be pushed to this point, so
> that secondary cores, while running early-boot code with their MMU and
> caches turned off, don't get incorrect code/data from before resume.
> 
> I have resisted the urge to draw some ascii-art!

That's ok, you just might want to replace PoI -> 'Point of
Unification' and PoC -> 'Point of Coherency' in the comments. That
should make googling easier for people not familiar with arm
terminology.

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2015-11-16 12:41 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 17:29 [PATCH v2 00/11] arm64: kernel: Add support for hibernate/suspend-to-disk James Morse
2015-10-27 17:29 ` James Morse
2015-10-27 17:29 ` [PATCH v2 01/11] arm64: kernel: fix tcr_el1.t0sz restore on systems with extended idmap James Morse
2015-10-27 17:29   ` James Morse
2015-10-27 17:29 ` [PATCH v2 02/11] arm64: Fold proc-macros.S into assembler.h James Morse
2015-10-27 17:29   ` James Morse
2015-11-14 21:25   ` Pavel Machek
2015-11-14 21:25     ` Pavel Machek
2015-11-16 18:44     ` Geoff Levand
2015-11-16 18:44       ` Geoff Levand
2015-10-27 17:29 ` [PATCH v2 03/11] arm64: Convert hcalls to use HVC immediate value James Morse
2015-10-27 17:29   ` James Morse
2015-10-27 17:29 ` [PATCH v2 04/11] arm64: Add new hcall HVC_CALL_FUNC James Morse
2015-10-27 17:29   ` James Morse
2015-10-27 17:29 ` [PATCH v2 05/11] arm64: kvm: allows kvm cpu hotplug James Morse
2015-10-27 17:29   ` James Morse
2015-10-27 17:29 ` [PATCH v2 06/11] arm64: kernel: Rework finisher callback out of __cpu_suspend_enter() James Morse
2015-10-27 17:29   ` James Morse
2015-10-27 17:29 ` [PATCH v2 07/11] arm64: Change cpu_resume() to enable mmu early then access sleep_sp by va James Morse
2015-10-27 17:29   ` James Morse
2015-10-27 17:29 ` [PATCH v2 08/11] arm64: kernel: Include _AC definition in page.h James Morse
2015-10-27 17:29   ` James Morse
2015-10-27 17:29 ` [PATCH v2 09/11] arm64: Promote KERNEL_START/KERNEL_END definitions to a header file James Morse
2015-10-27 17:29   ` James Morse
2015-10-27 17:29 ` [PATCH v2 10/11] PM / Hibernate: clean cached pages on architectures that require it James Morse
2015-10-27 17:29   ` James Morse
2015-11-11 11:40   ` Lorenzo Pieralisi
2015-11-11 11:40     ` Lorenzo Pieralisi
2015-11-12  0:48     ` Rafael J. Wysocki
2015-11-12  0:48       ` Rafael J. Wysocki
2015-11-12 11:47       ` Lorenzo Pieralisi
2015-11-12 11:47         ` Lorenzo Pieralisi
2015-11-13 23:38         ` Rafael J. Wysocki
2015-11-13 23:38           ` Rafael J. Wysocki
2015-11-17 12:38           ` Lorenzo Pieralisi
2015-11-17 12:38             ` Lorenzo Pieralisi
2015-11-17 13:13             ` Pavel Machek
2015-11-17 13:13               ` Pavel Machek
2015-11-17 13:43               ` Lorenzo Pieralisi
2015-11-17 13:43                 ` Lorenzo Pieralisi
2015-11-12  2:53     ` Chen, Yu C
2015-11-12  2:53       ` Chen, Yu C
2015-11-12 11:52       ` Lorenzo Pieralisi
2015-11-12 11:52         ` Lorenzo Pieralisi
2015-11-14 20:26   ` Pavel Machek
2015-11-14 20:26     ` Pavel Machek
2015-11-16 12:27     ` James Morse
2015-11-16 12:27       ` James Morse
2015-11-16 12:36       ` Pavel Machek
2015-11-16 12:36         ` Pavel Machek
2015-11-26 14:23   ` James Morse
2015-11-26 14:23     ` James Morse
2015-10-27 17:29 ` [PATCH v2 11/11] arm64: kernel: Add support for hibernate/suspend-to-disk James Morse
2015-10-27 17:29   ` James Morse
2015-11-14 21:34   ` Pavel Machek
2015-11-14 21:34     ` Pavel Machek
2015-11-16 12:29     ` James Morse
2015-11-16 12:29       ` James Morse
2015-11-16 12:41       ` Pavel Machek [this message]
2015-11-16 12:41         ` Pavel Machek
2015-11-16 14:01         ` James Morse
2015-11-16 14:01           ` James Morse
2015-11-16 14:23           ` Mark Rutland
2015-11-16 14:23             ` Mark Rutland
2015-11-16 18:01           ` Pavel Machek
2015-11-16 18:01             ` Pavel Machek

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=20151116124116.GC9125@amd \
    --to=pavel@ucw.cz \
    --cc=catalin.marinas@arm.com \
    --cc=geoff@infradead.org \
    --cc=james.morse@arm.com \
    --cc=kkang@intrinsyc.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=rjw@rjwysocki.net \
    --cc=sudeep.holla@arm.com \
    --cc=takahiro.akashi@linaro.org \
    --cc=w.f@huawei.com \
    --cc=will.deacon@arm.com \
    /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.