[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a04918d1-975e-5869-1ecd-c9df4ae5b1c1@suse.com>
Date: Mon, 15 Jul 2019 15:22:57 +0200
From: Juergen Gross <jgross@...e.com>
To: Andrew Cooper <andrew.cooper3@...rix.com>,
LKML <linux-kernel@...r.kernel.org>
Cc: Borislav Petkov <bp@...en8.de>,
Stephane Eranian <eranian@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
FengTang <feng.tang@...el.com>,
Andy Lutomirski <luto@...nel.org>, x86@...nel.org,
virtualization@...ts.linux-foundation.org,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
"Rafael J.Wysocki" <rjw@...ysocki.net>,
Pavel Machek <pavel@....cz>,
Alok Kataria <akataria@...are.com>,
Nadav Amit <namit@...are.com>
Subject: Re: [PATCH] x86/paravirt: Drop {read,write}_cr8() hooks
On 15.07.19 15:00, Andrew Cooper wrote:
> There is a lot of infrastructure for functionality which is used
> exclusively in __{save,restore}_processor_state() on the suspend/resume
> path.
>
> cr8 is an alias of APIC_TASKPRI, and APIC_TASKPRI is saved/restored
> independently by lapic_{suspend,resume}().
Aren't those called only with CONFIG_PM set?
Juergen
Powered by blists - more mailing lists