[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b8445e93-deed-1a28-cd3b-993d42c78251@xen.org>
Date: Wed, 22 Jul 2020 10:08:05 +0100
From: Julien Grall <julien@....org>
To: Anchal Agarwal <anchalag@...zon.com>, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, hpa@...or.com, x86@...nel.org,
boris.ostrovsky@...cle.com, jgross@...e.com,
linux-pm@...r.kernel.org, linux-mm@...ck.org, kamatam@...zon.com,
sstabellini@...nel.org, konrad.wilk@...cle.com,
roger.pau@...rix.com, axboe@...nel.dk, davem@...emloft.net,
rjw@...ysocki.net, len.brown@...el.com, pavel@....cz,
peterz@...radead.org, eduval@...zon.com, sblbir@...zon.com,
xen-devel@...ts.xenproject.org, vkuznets@...hat.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
dwmw@...zon.co.uk, benh@...nel.crashing.org
Subject: Re: [PATCH v2 04/11] x86/xen: add system core suspend and resume
callbacks
Hi,
On 02/07/2020 19:22, Anchal Agarwal wrote:
> diff --git a/include/xen/xen-ops.h b/include/xen/xen-ops.h
> index 2521d6a306cd..9fa8a4082d68 100644
> --- a/include/xen/xen-ops.h
> +++ b/include/xen/xen-ops.h
> @@ -41,6 +41,8 @@ u64 xen_steal_clock(int cpu);
> int xen_setup_shutdown_event(void);
>
> bool xen_is_xen_suspend(void);
> +void xen_setup_syscore_ops(void);
The function is only implemented and used by x86. So shouldn't this be
declared in an x86 header?
Cheers,
--
Julien Grall
Powered by blists - more mailing lists