All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linuxppc-dev@lists.ozlabs.org, darren@stevens-zone.net,
	Michael Ellerman <michaele@au1.ibm.com>,
	Julian Margetson <runaway@candw.ms>,
	Adrian Cox <adrian@humboldt.co.uk>
Subject: Kernel 4.7: PAGE_GUARDED and _PAGE_NO_CACHE
Date: Sat, 4 Jun 2016 09:40:54 +0200	[thread overview]
Message-ID: <66397458-c40a-4e83-c5e5-0ba69fb48986@xenosoft.de> (raw)
In-Reply-To: <9690f9a4-70c7-8acc-42d0-779bcc93db52@xenosoft.de>

Aneesh,

Could you please send me only your patch for the Power ISA 3.0 (Power9) 
Radix Tree MMU? You have done the most modifications for the kernel 4.7. 
If the kernel boots with your modifications then I have to look to the 
other few modifications.

Thanks in advance,

Christian

On 04 June 2016 at 09:19 AM, Christian Zigotzky wrote:
> Hi All,
>
> The commit powerpc-4.7-2 [2] was released yesterday.
>
> There is a conflict in my local kernel git directory if I use git pull 
> because I have reverted the commit powerpc-4.7-1. [1]
>
> The commit powerpc-4.7-2 [2] needs the commit powerpc-4.7-1. [1]
>
> I created a new local kernel git directory for the RC2 with:
>
> git clone 
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 
> linux-git-without-powerpc-commits
>
> After that I reverted the two commits:
>
> powerpc-4.7-2 [2]:
>
> git revert 5306d766f15e72bc79c61d88f77e5a6b1fcc0e68 -m 1
>
> powerpc-4.7-1 [1]:
>
> git revert c04a5880299eab3da8c10547db96ea9cdffd44a6 -m 1
>
> Afterwards I successfully tested our latest Nemo patch 4.7-1 [3] with 
> the following commands:
>
> cp -R linux-git-without-powerpc-commits linux-4.7
>
> patch -p0 < nemo_4.7-1.patch
>
> I tried to solve the boot issue last week. I modified the code a lot 
> and I replaced some files. Unfortunately without any success. The RC1 
> without the commit powerpc-4.7-1 [1] boots and works fantastic. I 
> don't have any ideas anymore. Please help me to solve the boot problems.
>
> Thanks in advance,
>
> Christian
>
> [1] 
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c04a5880299eab3da8c10547db96ea9cdffd44a6
> [2] 
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5306d766f15e72bc79c61d88f77e5a6b1fcc0e68
> [3] http://www.xenosoft.de/nemo_4.7-1.patch
>
> On 28 May 2016 at 8:51 PM, Darren Stevens wrote:
>> Hello Adrian
>>
>> On 28/05/2016, Adrian Cox wrote:
>>>> From: Christian Zigotzky [mailto:chzigotzky@xenosoft.de]
>>>> Sent: 28 May 2016 07:06
>>>> Adrian, what is the expected WIMG bit mapping for the Nemo board?
>>>>
>>> I'm not able to help much here, I'm afraid. I don't have a Nemo 
>>> board at
>>> the moment, and it's been a few years. From memory all the peripherals
>>> required standard uncached and guarded mappings on Nemo.
>> Before everybody gets too involved, from what I've seen with my tests 
>> today
>> the kernel is crashing long before it gets to the pci-common code.
>>
>> I've attached 2 boot logs, one from a 4.4 kernel I've been working 
>> on, and
>> from a build of the latest git.
>>
>> You can see from this that the 4.7 kernel hangs right after the 
>> booting linux
>> via __start(), whereas in the 4.4 there's about 29 lines of output 
>> before it
>> gets to the Initialised io_base_virt printk in our patch.
>>
>> The last time we had a hang this early in the boot it turned out to be a
>> problem in head_64.S, I think there is something else wrong in the 
>> commit
>> Christian has identified
>>
>> I will see if this is something I can fix, but it may need better low 
>> level
>> knowledge of PPC hardware than I have.
>>
>> Regards
>> Darren
>
> On 28 May 2016 at 6:53 PM, Adrian Cox wrote:
>>> From: Christian Zigotzky [mailto:chzigotzky@xenosoft.de]
>>> Sent: 28 May 2016 07:06
>>> Adrian, what is the expected WIMG bit mapping for the Nemo board?
>>>
>> I'm not able to help much here, I'm afraid. I don't have a Nemo board 
>> at the moment, and it's been a few years. From memory all the 
>> peripherals required standard uncached and guarded mappings on Nemo.
>>
>> The difficult bit that usually breaks on kernel upgrades is not the 
>> WIMG settings, but the PCI probing routine.  The SB600 doesn't follow 
>> normal PCIe address decoding rules, as in its original use as an AMD 
>> south bridge it was designed to appear as if it were integrated into 
>> the north bridge.
>>
>> -- 
>> Adrian
>>
>
>
>

  reply	other threads:[~2016-06-04  7:41 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23  4:38 PAGE_GUARDED Christian Zigotzky
2016-05-23  8:01 ` PAGE_GUARDED Benjamin Herrenschmidt
2016-05-24 10:48   ` PAGE_GUARDED Christian Zigotzky
2016-05-24 11:16     ` PAGE_GUARDED Benjamin Herrenschmidt
2016-05-24 13:37       ` PAGE_GUARDED Christian Zigotzky
2016-05-24 15:37         ` PAGE_GUARDED Aneesh Kumar K.V
2016-05-25  6:58           ` PAGE_GUARDED Christian Zigotzky
2016-05-25 11:44             ` PAGE_GUARDED Christian Zigotzky
2016-06-04  7:19           ` Kernel 4.7: PAGE_GUARDED and _PAGE_NO_CACHE Christian Zigotzky
2016-06-04  7:40             ` Christian Zigotzky [this message]
2016-06-04 11:08               ` Christian Zigotzky
2016-06-04 14:46                 ` Aneesh Kumar K.V
2016-06-04 15:13                   ` Christian Zigotzky
2016-06-04 15:25                     ` Christian Zigotzky
2016-06-05 16:09                       ` Christian Zigotzky
2016-06-06  0:57                         ` Michael Ellerman
2016-06-06  1:23                           ` Julian Margetson
2016-06-06  2:00                             ` Michael Ellerman
2016-06-06  8:59                               ` Julian Margetson
2016-06-06  0:54                   ` Michael Ellerman
2016-06-04 14:42               ` Aneesh Kumar K.V
2016-06-04 15:07                 ` Christian Zigotzky
2016-06-06  0:51                   ` Michael Ellerman
2016-06-06  5:21                     ` Christian Zigotzky
2016-06-07 20:17                     ` Christian Zigotzky
2016-06-07 22:14                       ` Christian Zigotzky
2016-06-08  1:51                         ` Michael Ellerman
2016-06-08  2:52                       ` Michael Ellerman
2016-06-08 10:58                         ` Christian Zigotzky
2016-06-08 11:30                           ` Michael Ellerman
2016-06-08 12:50                             ` Christian Zigotzky
2016-06-08 11:33                       ` Darren Stevens
2016-06-08 13:24                         ` Christian Zigotzky
2016-06-08 13:51                         ` Christian Zigotzky
2016-06-08 13:52                         ` Michael Ellerman
2016-06-08 15:11                         ` Aneesh Kumar K.V
2016-06-08 15:47                           ` Christian Zigotzky
2016-06-09  8:48                             ` Christian Zigotzky
2016-06-09 11:15                               ` Michael Ellerman
2016-06-09 13:13                                 ` Christian Zigotzky
2016-06-13  8:14                                   ` Christian Zigotzky
2016-06-13  8:19                                     ` Benjamin Herrenschmidt
2016-06-13 18:09                                       ` Christian Zigotzky
2016-06-22 19:07                                         ` Christian Zigotzky
2016-06-22 19:58                                           ` luigi burdo

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=66397458-c40a-4e83-c5e5-0ba69fb48986@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=adrian@humboldt.co.uk \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=darren@stevens-zone.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michaele@au1.ibm.com \
    --cc=runaway@candw.ms \
    /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.