<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel">
    <title>gmane.linux.ports.ppc64.devel</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91926"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91925"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91923"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91921"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91920"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91918"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91916"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91915"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91914"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91913"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91912"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91910"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91909"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91908"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91907"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91906"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91903"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91902"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91901"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91900"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91926">
    <title>Re: [PATCH] powerpc/kvm: Handle transparent hugepage in KVM</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91926</link>
    <description>&lt;pre&gt;
OK, maybe you can update to reflect that.


How about something like this then?

while (1) {
      if (unlikely(old_pte &amp;amp; _PAGE_BUSY))
    continue;
.....
      if cmpxchg(foo)
       break;
}






Sure.

Mikey
&lt;/pre&gt;</description>
    <dc:creator>Michael Neuling</dc:creator>
    <dc:date>2013-06-19T23:59:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91925">
    <title>Re: DEBUG_PAGEALLOC on PPC not working (kernels 2.6-25, 3.0-34)</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91925</link>
    <description>&lt;pre&gt;
This is not supported on booke -- the tlbcam mapping is required for  
all lowmem.


For e300, I think I had it working at one point a few years ago (see  
commit bde6c6e16aa489ea76c762fb7ffb0abb48660dd8).

The reason we can do it on e300 and not on booke is because e300 takes  
exceptions in real mode.  On e500 the MMU is always enabled, so we need  
bolted TLB1 entries that cover at least all exception code (up to the  
point where a TLB miss could safely be taken) and all page tables (in  
practice, we just bolt all lowmem) and other data that can be  
referenced from said exception code.  There are not enough TLB1 entries  
to do this on a fine-grained basis.

-Scott
&lt;/pre&gt;</description>
    <dc:creator>Scott Wood</dc:creator>
    <dc:date>2013-06-19T21:00:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91923">
    <title>Re: Pull request: scottwood/linux.git for-3.10</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91923</link>
    <description>&lt;pre&gt;
That's the patch I'm asking you to pull. :-P

-Scott
&lt;/pre&gt;</description>
    <dc:creator>Scott Wood</dc:creator>
    <dc:date>2013-06-19T16:50:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91921">
    <title>Re: [PATCH 1/2] perf tools: fix a typo of a Power7 event name</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91921</link>
    <description>&lt;pre&gt;| In the Power7 PMU guide:
| https://www.power.org/documentation/commonly-used-metrics-for-performance-analysis/
| PM_BRU_MPRED is referred to as PM_BR_MPRED.
| 
| This patch fix the typo by changing the name of the event in kernel and
| documentation accordingly.
| 
| Signed-off-by: Runzhen Wang &amp;lt;runzhen&amp;lt; at &amp;gt;linux.vnet.ibm.com&amp;gt;

Reviewed-by: Sukadev Bhattiprolu &amp;lt;sukadev&amp;lt; at &amp;gt;linux.vnet.ibm.com&amp;gt;
&lt;/pre&gt;</description>
    <dc:creator>Sukadev Bhattiprolu</dc:creator>
    <dc:date>2013-06-19T16:13:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91920">
    <title>Re: Pull request: scottwood/linux.git for-3.10</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91920</link>
    <description>&lt;pre&gt;
On Jun 18, 2013, at 3:14 PM, Scott Wood wrote:


What about Rohit's patch: powerpc/pci: Fix setup of Freescale PCI / PCIe controllers?  Seems like also a fix for 3.10

- k
&lt;/pre&gt;</description>
    <dc:creator>Kumar Gala</dc:creator>
    <dc:date>2013-06-19T15:06:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91918">
    <title>Re: Pull request: scottwood/linux.git for-3.10</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91918</link>
    <description>&lt;pre&gt;
On Jun 18, 2013, at 3:14 PM, Scott Wood wrote:


What about Rohit's patch: powerpc/pci: Fix setup of Freescale PCI / PCIe controllers?  Seems like also a fix for 3.10

- k
&lt;/pre&gt;</description>
    <dc:creator>Kumar Gala</dc:creator>
    <dc:date>2013-06-19T15:06:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91916">
    <title>DEBUG_PAGEALLOC on PPC not working (kernels 2.6-25, 3.0-34)</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91916</link>
    <description>&lt;pre&gt;Hi,

We have two Freescale PowerPC boards on which we're trying to enable
DEBUG_PAGEALLOC with the hope that we'll see an exception whenever some
code tries to modify a page that's been already freed. To test it, we wrote
this sample code -

===
#define BUF_SIZE    4096
void
pagealloc_test(void)
{
    char *buf = kmalloc(BUF_SIZE, GFP_KERNEL);

    if (!buf) {
        printk("%s[%d] - alloc failed!\n", __func__, __LINE__);
        return;
    }
    printk("%s[%d] - alloc'd\n", __func__, __LINE__);
    memset(&amp;amp;buf[0], 0, BUF_SIZE);
    printk("%s[%d] - memset'd\n", __func__, __LINE__);
    kfree(buf);
    printk("%s[%d] - free'd\n", __func__, __LINE__);
    memset(&amp;amp;buf[0], 1, BUF_SIZE);
    printk("%s[%d] - memset'd after free!\n", __func__, __LINE__);
}
===

Here, the last memset() should generate an exception if PAGEALLOC code
correctly unmapped the page during kfree(). However, kernel is happily
running after the memset post-free. Any clue?
Also, the 2nd board has Book-E which has a different MMU architect&lt;/pre&gt;</description>
    <dc:creator>saikia.partha</dc:creator>
    <dc:date>2013-06-19T13:09:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91915">
    <title>DEBUG_PAGEALLOC on PPC not working (kernels 2.6-25, 3.0-34)</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91915</link>
    <description>&lt;pre&gt;Hi,

We have two Freescale PowerPC boards on which we're trying to enable
DEBUG_PAGEALLOC with the hope that we'll see an exception whenever some
code tries to modify a page that's been already freed. To test it, we wrote
this sample code -

===
#define BUF_SIZE    4096
void
pagealloc_test(void)
{
    char *buf = kmalloc(BUF_SIZE, GFP_KERNEL);

    if (!buf) {
        printk("%s[%d] - alloc failed!\n", __func__, __LINE__);
        return;
    }
    printk("%s[%d] - alloc'd\n", __func__, __LINE__);
    memset(&amp;amp;buf[0], 0, BUF_SIZE);
    printk("%s[%d] - memset'd\n", __func__, __LINE__);
    kfree(buf);
    printk("%s[%d] - free'd\n", __func__, __LINE__);
    memset(&amp;amp;buf[0], 1, BUF_SIZE);
    printk("%s[%d] - memset'd after free!\n", __func__, __LINE__);
}
===

Here, the last memset() should generate an exception if PAGEALLOC code
correctly unmapped the page during kfree(). However, kernel is happily
running after the memset post-free. Any clue?
Also, the 2nd board has Book-E which has a different MMU architect&lt;/pre&gt;</description>
    <dc:creator>saikia.partha</dc:creator>
    <dc:date>2013-06-19T12:58:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91914">
    <title>Re: [PATCH] powerpc/kvm: Handle transparent hugepage in KVM</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91914</link>
    <description>&lt;pre&gt;

In a way yes. Instead of lock and read as it was before, it is now done
via cmpxchg which still use ldarx/stdcx



No that would be wrong. (I did that in an earlier version :).We really
don't want the below cmpxchg to run if we find _PAGE_BUSY.


it is actually the shift bits represending hugepage size. We set it to 0
if we don't find hugepage in find_linux_pte_or_hugepte. May be something
like hugepage_shift is better ?

-aneesh
&lt;/pre&gt;</description>
    <dc:creator>Aneesh Kumar K.V</dc:creator>
    <dc:date>2013-06-19T12:30:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91913">
    <title>Re: [PATCH 05/31] powerpc/eeh: Trace PCI bus from PE</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91913</link>
    <description>&lt;pre&gt;
Please use the updated [5/31] in the attachment.

Thanks,
Gavin

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev&amp;lt; at &amp;gt;lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev&lt;/pre&gt;</description>
    <dc:creator>Gavin Shan</dc:creator>
    <dc:date>2013-06-19T10:20:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91912">
    <title>Re: [PATCH] powerpc/THP: Wait for all hash_page calls to finish before invalidating HPTE entries</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91912</link>
    <description>&lt;pre&gt;

Right, this is expected. This fix is a result of me asking him to do it
that way on ST and should eventually be folded in the series (or
re-ordered to be in there before the patch that enables THP).

Cheers,
Ben.
&lt;/pre&gt;</description>
    <dc:creator>Benjamin Herrenschmidt</dc:creator>
    <dc:date>2013-06-19T10:18:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91910">
    <title>[PATCH 4/4] powerpc: make the kernel bootable from non 0 address for 6xx</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91910</link>
    <description>&lt;pre&gt;Add the support to boot the kernel from a non 0 address for 6xx.
Setup the exception trampoline if the physical start address is
not 0.

For a kdump kernel, enable the relocatable support implicitly.
Since the memstart_adddr of the kdump is not 0, we definitely
should regard this when setting up the BAT map.

Signed-off-by: Kevin Hao &amp;lt;haokexin&amp;lt; at &amp;gt;gmail.com&amp;gt;
---
 arch/powerpc/Kconfig                            |  2 +-
 arch/powerpc/include/asm/exception_trampoline.h |  4 ++--
 arch/powerpc/kernel/Makefile                    |  3 ++-
 arch/powerpc/kernel/exception_trampoline.c      | 18 +++++++++++++++---
 arch/powerpc/mm/ppc_mmu_32.c                    |  7 +------
 5 files changed, 21 insertions(+), 13 deletions(-)

diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
index 8fe2792..6e03028 100644
--- a/arch/powerpc/Kconfig
+++ b/arch/powerpc/Kconfig
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -382,7 +382,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; config KEXEC
 config CRASH_DUMP
 bool "Build a kdump crash kernel"
 depends on PPC64 || 6xx || FSL_BOOKE || (44x &amp;amp;&amp;amp; !SMP)
-select RELOCA&lt;/pre&gt;</description>
    <dc:creator>Kevin Hao</dc:creator>
    <dc:date>2013-06-19T09:20:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91909">
    <title>[PATCH 3/4] powerpc: s/kdump/exception/ for the exception trampoline functions</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91909</link>
    <description>&lt;pre&gt;These functions are not just kdump specific. Replace the 'kdump' with
the 'exception' to make them more general.

Signed-off-by: Kevin Hao &amp;lt;haokexin&amp;lt; at &amp;gt;gmail.com&amp;gt;
---
 arch/powerpc/include/asm/exception_trampoline.h | 20 ++++++++++----------
 arch/powerpc/kernel/exception_trampoline.c      | 14 +++++++-------
 arch/powerpc/kernel/prom.c                      |  2 +-
 arch/powerpc/kernel/setup_32.c                  |  2 +-
 arch/powerpc/kernel/setup_64.c                  |  2 +-
 5 files changed, 20 insertions(+), 20 deletions(-)

diff --git a/arch/powerpc/include/asm/exception_trampoline.h b/arch/powerpc/include/asm/exception_trampoline.h
index 707ad6c..88281c9 100644
--- a/arch/powerpc/include/asm/exception_trampoline.h
+++ b/arch/powerpc/include/asm/exception_trampoline.h
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -1,10 +1,10 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 #ifndef _EXCEPTION_TRAMPOLINE_H
 #define _EXCEPTION_TRAMPOLINE_H
 
-/* How many bytes to reserve at zero for kdump. The reserve limit should
+/* How many bytes to reserve at zero for exception. The reserve limit should
  * &lt;/pre&gt;</description>
    <dc:creator>Kevin Hao</dc:creator>
    <dc:date>2013-06-19T09:20:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91908">
    <title>[PATCH 2/4] powerpc: move the exception trampoline helper functions to a separate file</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91908</link>
    <description>&lt;pre&gt;For some platform such as 6xx we need to setup the exception
trampoline for a relocatable kernel even through the CONFIG_CRASH_DUMP
is disabled. So move these functions to a separate file so they can
be used by non dump kernel.  This patch doesn't introduce any function
change.

Signed-off-by: Kevin Hao &amp;lt;haokexin&amp;lt; at &amp;gt;gmail.com&amp;gt;
---
 arch/powerpc/include/asm/exception_trampoline.h | 35 +++++++++++++
 arch/powerpc/include/asm/kdump.h                | 32 -----------
 arch/powerpc/kernel/Makefile                    |  2 +-
 arch/powerpc/kernel/crash_dump.c                | 41 ---------------
 arch/powerpc/kernel/exception_trampoline.c      | 70 +++++++++++++++++++++++++
 arch/powerpc/kernel/prom.c                      |  2 +-
 arch/powerpc/kernel/setup_32.c                  |  1 +
 arch/powerpc/kernel/setup_64.c                  |  2 +-
 8 files changed, 109 insertions(+), 76 deletions(-)
 create mode 100644 arch/powerpc/include/asm/exception_trampoline.h
 create mode 100644 arch/powerpc/kernel/exception_trampoline.&lt;/pre&gt;</description>
    <dc:creator>Kevin Hao</dc:creator>
    <dc:date>2013-06-19T09:20:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91907">
    <title>[PATCH 1/4] powerpc: enable relocatable support for 6xx</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91907</link>
    <description>&lt;pre&gt;This is based on the codes in head_44x.S. With this patch the kernel
can only boot from 0 with CONFIG_RELOCATABLE enabled. We will add the
support to boot from a non 0 address in the following patches.

Signed-off-by: Kevin Hao &amp;lt;haokexin&amp;lt; at &amp;gt;gmail.com&amp;gt;
---
 arch/powerpc/Kconfig                   |   2 +-
 arch/powerpc/include/asm/page.h        |   2 +-
 arch/powerpc/kernel/head_32.S          | 103 +++++++++++++++++++++++++++++++++
 arch/powerpc/kernel/prom_init_check.sh |   2 +-
 4 files changed, 106 insertions(+), 3 deletions(-)

diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
index c33e3ad..8fe2792 100644
--- a/arch/powerpc/Kconfig
+++ b/arch/powerpc/Kconfig
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -866,7 +866,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; config DYNAMIC_MEMSTART
 
 config RELOCATABLE
 bool "Build a relocatable kernel"
-depends on ADVANCED_OPTIONS &amp;amp;&amp;amp; FLATMEM &amp;amp;&amp;amp; 44x
+depends on ADVANCED_OPTIONS &amp;amp;&amp;amp; FLATMEM &amp;amp;&amp;amp; (44x || 6xx)
 select NONSTATIC_KERNEL
 help
   This builds a kernel image that is capable of running at the
diff --git a/arch/powerpc/include/asm/page.h&lt;/pre&gt;</description>
    <dc:creator>Kevin Hao</dc:creator>
    <dc:date>2013-06-19T09:20:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91906">
    <title>[PATCH 0/4] powerpc: enable relocatable support for 6xx</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91906</link>
    <description>&lt;pre&gt;This patch series enables the relocatable support for 6xx boards.
With these patches:
  * the kernel can boot from any address between 0x10000 ~ 0x2000000
  * kdump is workable
  * a single kernel image can be used as boot or kdump kernel

Boot test on a mpc8260 board. Also passed the build test for the
following configurations:
ppc40x_defconfig
        ppc64e_defconfig
        ppc64_defconfig
        corenet32_smp_defconfig
        corenet64_smp_defconfig
        ppc44x_defconfig
pmac32_defconfig
pq2fads_defconfig
mpc5200_defconfig
        pseries_defconfig

---
Kevin Hao (4):
  powerpc: enable relocatable support for 6xx
  powerpc: move the exception trampoline helper functions to a separate
    file
  powerpc: s/kdump/exception/ for the exception trampoline functions
  powerpc: make the kernel bootable from non 0 address for 6xx

 arch/powerpc/Kconfig                            |   4 +-
 arch/powerpc/include/asm/exception_trampoline.h |  35 ++++++++
 arch/powerpc/include/asm/kdump.h                |  &lt;/pre&gt;</description>
    <dc:creator>Kevin Hao</dc:creator>
    <dc:date>2013-06-19T09:20:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91903">
    <title>Re: [PATCH 05/31] powerpc/eeh: Trace PCI bus from PE</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91903</link>
    <description>&lt;pre&gt;
.../...


Thanks, Mike. Good catch actually, it won't have side-effect and
possiblly avoid problems during hot-plug: For PCI bus with only
child PCI device, we won't return the PCI bus (without fix) and
the EEH core doesn't do hot-plug on the affected PCI bus then. 

I'm testing on the updated patch and will send that out soon if it
works well.

Thanks,
Gavin
&lt;/pre&gt;</description>
    <dc:creator>Gavin Shan</dc:creator>
    <dc:date>2013-06-19T08:48:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91902">
    <title>Re: [PATCH 01/31] powerpc/eeh: Move common part to kernel directory</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91902</link>
    <description>&lt;pre&gt;
Please use the updated [1/31] in the attachment.

Thanks,
Gavin

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev&amp;lt; at &amp;gt;lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev&lt;/pre&gt;</description>
    <dc:creator>Gavin Shan</dc:creator>
    <dc:date>2013-06-19T07:29:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91901">
    <title>Re: [PATCH 05/31] powerpc/eeh: Trace PCI bus from PE</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91901</link>
    <description>&lt;pre&gt;于 2013/6/18 16:33, Gavin Shan 写道:
Hi Gavin

I have qestion, can we keep pe-&amp;gt;bus for a device pe ? the value is the 
bus which edev belongs to.

so that we can make the code more efficient for device pe.

I have no idea of whether this will cause side effect

Thanks
Mike

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev&amp;lt; at &amp;gt;lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev&lt;/pre&gt;</description>
    <dc:creator>Mike Qiu</dc:creator>
    <dc:date>2013-06-19T07:21:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91900">
    <title>Re: [PATCH] powerpc/THP: Wait for all hash_page calls to finish before invalidating HPTE entries</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91900</link>
    <description>&lt;pre&gt;




Can you make this more obvious in the changelog (as well as making it 80
col).  I don't see 'bug' mentioned anywhere.  'Fix' is mentioned
somewhere in the middle of the changelog.


OK, but V10 THP is not in yet, right?  So why not roll it into that
series rather than pushing broken stuff and fixing it?

Mikey
&lt;/pre&gt;</description>
    <dc:creator>Michael Neuling</dc:creator>
    <dc:date>2013-06-19T07:14:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91899">
    <title>Re: [PATCH] powerpc/kvm: Handle transparent hugepage in KVM</title>
    <link>http://permalink.gmane.org/gmane.linux.ports.ppc64.devel/91899</link>
    <description>&lt;pre&gt;

Can you expand on this more please.  There are a lot of details below
like removing a ldarx/stdcx loop that should be better described here.


This is comment still valid now the ldarx/stdcx is gone?  


continue here?  Please don't create looping primitives.
  

Comment looks much like the code... seems redundant.


Whitespace


'shift' goes into the new 'hugepage' parameter?  Doesn't seem logical?
Can we harmonise the name to make it less confusing?

Mikey

&lt;/pre&gt;</description>
    <dc:creator>Michael Neuling</dc:creator>
    <dc:date>2013-06-19T07:11:42</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.ports.ppc64.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.ports.ppc64.devel</link>
  </textinput>
</rdf:RDF>
