> -Original Message-
> From: christophe leroy
> Sent: 2019年8月24日 14:45
> To: Xiaowei Bao ; Andrew Murray
>
> Cc: mark.rutl...@arm.com; Roy Zang ;
> lorenzo.pieral...@arm.co; a...@arndb.de; devicet...@vger.kernel.org;
> gre...@linuxfoundation.org; linuxppc-dev@lists.ozlabs.org;
>
On 8/23/19 9:48 AM, Michael Ellerman wrote:
> Hi Claudio,
Hi Michael,
>
> Claudio Carvalho writes:
>> Ultravisor (UV) provides an in-memory console which follows the OPAL
>> in-memory console structure.
>>
>> This patch extends the OPAL msglog code to also initialize the UV memory
>> console
On Fri, Aug 23, 2019 at 09:58:04PM +, Paul Burton wrote:
> So I believe uncached & uncached accelerated are another case like that
> described above - they're 2 different CCAs but the same "access type",
> namely uncached.
>
> Section 4.9 then goes on to forbid mixing access types, but not
linux-next is currently broken on POWER8 non virtualized. Kernel
fails to reach login prompt with following kernel warning
repeatedly shown during boot.
The problem dates back atleast till next-20190816.
[ 40.285606] WARNING: CPU: 1 PID: 0 at
arch/powerpc/platforms/powernv/smp.c:160
Michael Ellerman wrote:
Currently if we oops or warn while function_graph is active the stack
trace looks like:
.trace_graph_return+0xac/0x100
.ftrace_return_to_handler+0x98/0x140
.return_to_handler+0x20/0x40
.return_to_handler+0x0/0x40
.return_to_handler+0x0/0x40
Le 24/08/2019 à 02:18, Xiaowei Bao a écrit :
-Original Message-
From: Andrew Murray
Sent: 2019年8月23日 22:28
To: Xiaowei Bao
Cc: bhelg...@google.com; robh...@kernel.org; mark.rutl...@arm.com;
shawn...@kernel.org; Leo Li ; kis...@ti.com;
lorenzo.pieral...@arm.co; a...@arndb.de;
