linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Serge Belyshev <belyshev@depni.sinp.msu.ru>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: BUG: crash in __tlb_remove_page_size with STRICT_KERNEL_RWX on BOOK3S_32
Date: Fri, 26 Apr 2019 12:07:00 -0500	[thread overview]
Message-ID: <20190426170700.GD8599@gate.crashing.org> (raw)
In-Reply-To: <878svwn85h.fsf@depni.sinp.msu.ru>

On Fri, Apr 26, 2019 at 05:38:50PM +0300, Serge Belyshev wrote:
> ---[ Instruction Block Address Translation ]---
> 0: 0xc0000000-0xc07fffff 0x00000000 Kernel EXEC coherent 
> 1: 0xc0800000-0xc087ffff 0x00800000 Kernel EXEC coherent 
> 2:         -
> 3:         -
> 4:         -
> 5:         -
> 6:         -
> 7:         -
> 
> ---[ Data Block Address Translation ]---
> 0: 0xc0000000-0xc07fffff 0x00000000 Kernel RO coherent 
> 1: 0xc0800000-0xc0bfffff 0x00800000 Kernel RO coherent 
> 2: 0xc0c00000-0xc13fffff 0x00c00000 Kernel RW coherent 
> 3: 0xc1400000-0xc23fffff 0x01400000 Kernel RW coherent 
> 4: 0xc2400000-0xc43fffff 0x02400000 Kernel RW coherent 
> 5: 0xc4400000-0xc83fffff 0x04400000 Kernel RW coherent 
> 6: 0xc8400000-0xd03fffff 0x08400000 Kernel RW coherent 
> 7: 0xd0400000-0xe03fffff 0x10400000 Kernel RW coherent 

The starting address of a BAT block is always aligned to the block size.
All of DBAT2..DBAT7 are wrong?


Segher

  reply	other threads:[~2019-04-26 17:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26  4:54 BUG: crash in __tlb_remove_page_size with STRICT_KERNEL_RWX on BOOK3S_32 Serge Belyshev
2019-04-26  7:27 ` Christophe Leroy
2019-04-26 14:38   ` Serge Belyshev
2019-04-26 17:07     ` Segher Boessenkool [this message]
2019-04-27  9:05       ` christophe leroy
2019-04-29  7:31     ` Christophe Leroy
2019-04-29  8:20       ` Serge Belyshev
2019-04-29  8:49         ` Christophe Leroy

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=20190426170700.GD8599@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=belyshev@depni.sinp.msu.ru \
    --cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).