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 17:13:53 +0200 [thread overview]
Message-ID: <2bf8f412-2631-75b4-70a3-cb5ecee5cf48@xenosoft.de> (raw)
In-Reply-To: <871t4dui4g.fsf@skywalker.in.ibm.com>
Aneesh,
It's from the Nemo patch. I patch the kernel 4.7 with our Nemo patch. [1]
Cheers,
Christian
[1] http://www.xenosoft.de/nemo_4.7-1.patch
On 04 June 2016 at 4:46 PM, Aneesh Kumar K.V wrote:
>
> Which kernel is that ? For upstream I have at that line
>
> 729 hose->pci_io_size = range.pci_addr + range.size;
> 730 hose->io_base_phys = range.cpu_addr - range.pci_addr;
> 731
> 732 /* Build resource */
> 733 res = &hose->io_resource;
> 734 range.cpu_addr = range.pci_addr;
> 735 break;
> 736 case IORESOURCE_MEM:
>
>
> -aneesh
>
>
next prev parent reply other threads:[~2016-06-04 15:14 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
2016-06-04 11:08 ` Christian Zigotzky
2016-06-04 14:46 ` Aneesh Kumar K.V
2016-06-04 15:13 ` Christian Zigotzky [this message]
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=2bf8f412-2631-75b4-70a3-cb5ecee5cf48@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 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).