On 19.07.2010, at 03:11, Benjamin Herrenschmidt wrote:
On Thu, 2010-07-15 at 17:05 +0530, Subrata Modak wrote:
commit e62cee42e66dcca83aae02748535f62e0f564a0c solved the problem for
2.6.34-rc6. However some other bad relocation warnings generated against
2.6.35-rc5 on Power7/ppc64 below:
On Fri, 2010-07-16 at 12:04 +1000, Michael Neuling wrote:
commit e62cee42e66dcca83aae02748535f62e0f564a0c solved the problem for
2.6.34-rc6. However some other bad relocation warnings generated against
2.6.35-rc5 on Power7/ppc64 below:
MODPOST 2004 modules^M
WARNING: 2 bad
On Mon Jul 19 2010 at about 03:36:51 EST, Alexander Graf wrote:
On 19.07.2010, at 03:11, Benjamin Herrenschmidt wrote:
On Thu, 2010-07-15 at 17:05 +0530, Subrata Modak wrote:
commit e62cee42e66dcca83aae02748535f62e0f564a0c solved the problem for
2.6.34-rc6. However some other bad
I wrote:
On Mon Jul 19 2010 at about 03:36:51 EST, Alexander Graf wrote:
On 19.07.2010, at 03:11, Benjamin Herrenschmidt wrote:
On Thu, 2010-07-15 at 17:05 +0530, Subrata Modak wrote:
commit e62cee42e66dcca83aae02748535f62e0f564a0c solved the problem for
2.6.34-rc6. However some
Milton Miller wrote:
I wrote:
On Mon Jul 19 2010 at about 03:36:51 EST, Alexander Graf wrote:
On 19.07.2010, at 03:11, Benjamin Herrenschmidt wrote:
On Thu, 2010-07-15 at 17:05 +0530, Subrata Modak wrote:
commit e62cee42e66dcca83aae02748535f62e0f564a0c solved the
On Book3S KVM we directly expose some asm pointers to C code as
variables. These need to be relocated and thus break on relocatable
kernels.
To make sure we can at least build, let's mark them as long instead
of u32 where 64bit relocations don't work.
This fixes the following build error:
On 07/19/2010 05:54 PM, Alexander Graf wrote:
I'm not sure which tree this should go through. Avi and Ben, please
coordinate this.
---
arch/powerpc/include/asm/kvm_book3s.h |4 ++--
arch/powerpc/kvm/book3s_rmhandlers.S |4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
Avi Kivity wrote:
On 07/19/2010 05:54 PM, Alexander Graf wrote:
I'm not sure which tree this should go through. Avi and Ben, please
coordinate this.
---
arch/powerpc/include/asm/kvm_book3s.h |4 ++--
arch/powerpc/kvm/book3s_rmhandlers.S |4 ++--
2 files changed, 4
On Fri, 16 Jul 2010 17:30:01 -0700
Shawn Jin shawnx...@gmail.com wrote:
My RCCR=0x1, meaning the first 512B is for microcode. So the data and
the TxBD should really be starting at 0xfa202200? Then my muram data's
reg should be 0x200 ?? What size shall I specify?
After the muram
thanks very much! it works well now~~
but i found in my system,if i add the 0x prefix it will cause a syntax error
2010-07-19
hacklu
发件人： Grant Likely
发送时间： 2010-07-17 05:46:59
收件人： hacklu
抄送： linuxppc-dev
主题： Re: hi, i have two flashs, but my kernel can only find one , how cani
On Sun, 18 Jul 2010 22:32:38 -0600
Grant Likely grant.lik...@secretlab.ca wrote:
On Sun, Jul 18, 2010 at 10:28 PM, Matthew McClintock m...@freescale.com
wrote:
Upon first examining the details of getting kexec working on our platform I
noticed our device tree passed from u-boot contained
This is a fairly brute force approach to allowing a Kconfig select
to specify an excplicit value for the selected config sybmol.
The syntax of select is changed to:
select symbol [expr] [if expr]
The approach taken is to add a list of value, dependency expression
pairs to the symbol and
Mikael Pettersson writes:
The kernel's math-emu code contains a macro _FP_FROM_INT() which is
used to convert an integer to a raw normalized floating-point value.
It does this basically in three steps:
1. Compute the exponent from the number of leading zero bits.
2. Downshift large
From: Mikael Pettersson mi...@it.uu.se
Date: Mon, 19 Jul 2010 23:58:42 +0200
The kernel's math-emu code contains a macro _FP_FROM_INT() which is
used to convert an integer to a raw normalized floating-point value.
It does this basically in three steps:
1. Compute the exponent from the
The kernel's math-emu code contains a macro _FP_FROM_INT() which is
used to convert an integer to a raw normalized floating-point value.
It does this basically in three steps:
1. Compute the exponent from the number of leading zero bits.
2. Downshift large fractions to put the MSB in the right
This patchset refactor the file spi_mpc8xxx.c to abstract some common code
as a lib used by the SPI/eSPI controller driver, move the SPI controller
driver code to fsl_spi.c, and add the eSPI controller support with fsl_espi.c.
Tested on P4080DS and MPC8536DS board based on latest Linux tree.
For Freescale's eSPI controller, the max transaction length one time
is limitted by the SPCOM[TRANSLEN] field which is 0x1. When used
mkfs.ext2 command to create ext2 filesystem on the flash, the read
length will exceed the max value of the SPCOM[TRANSLEN] field, so
change the read function to
Signed-off-by: Mingkai Hu mingkai...@freescale.com
---
Documentation/powerpc/dts-bindings/fsl/spi.txt | 20
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/Documentation/powerpc/dts-bindings/fsl/spi.txt
b/Documentation/powerpc/dts-bindings/fsl/spi.txt
index
Signed-off-by: Mingkai Hu mingkai...@freescale.com
---
drivers/of/of_spi.c | 11 +++
drivers/spi/spi_mpc8xxx.c |1 +
2 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/drivers/of/of_spi.c b/drivers/of/of_spi.c
index 5fed7e3..284ca0e 100644
---
Add eSPI controller support based on the common code spi_mpc8xxx.c.
The eSPI controller is newer controller 85xx/Pxxx devices supported.
There're some differences comparing to the SPI controller:
1. Has different register map and different bit definition
So leave the code operated the
This set of patches de-couples the idea that there is a single
directory in sysfs for each memory section. The intent of the
patches is to reduce the number of sysfs directories created to
resolve a boot-time performance issue. On very large systems
boot time are getting very long (as seen on
Move the find_me mory_block() routine up to avoid needing a forward
declaration in subsequent patches.
Signed-off-by: Nathan Fontenot nf...@austin.ibm.com
---
drivers/base/memory.c | 62 +-
1 file changed, 31 insertions(+), 31 deletions(-)
Update the 'phys_index' properties of a memory block to include a
'start_phys_index' which is the same as the current 'phys_index' property.
This also adds an 'end_phys_index' property to indicate the id of the
last section in th memory block.
Signed-off-by: Nathan Fontenot nf...@austin.ibm.com
Add a section count property to the memory_block struct to track the number
of memory sections that have been added/removed from a emory block.
Signed-off-by: Nathan Fontenot nf...@asutin.ibm.com
---
drivers/base/memory.c | 19 ---
include/linux/memory.h |2 ++
2 files
Update the memory sysfs code that each sysfs memory directory is now
considered a memory block that can contain multiple memory sections per
memory block. The default size of each memory block is SECTION_SIZE_BITS
to maintain the current behavior of having a single memory section per
memory block
Update the find_memory_block declaration to to take a struct mem_section *
so that it matches the definition.
Signed-off-by: Nathan Fontenot nf...@austin.ibm.com
---
include/linux/memory.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6/include/linux/memory.h
Update the node sysfs code to be aware of the new capability for a memory
block to contain multiple memory sections. This requires an additional
parameter to unregister_mem_sect_under_nodes so that we know which memory
section of the memory block to unregister.
Signed-off-by: Nathan Fontenot
Define a version of memory_block_size_bytes() for powerpc/pseries such that
a memory block spans an entire lmb.
Signed-off-by: Nathan Fontenot nf...@austin.ibm.com
---
arch/powerpc/platforms/pseries/hotplug-memory.c | 66 +++-
1 file changed, 53 insertions(+), 13
Update the memory hotplug documentation to reflect the new behaviors of
memory blocks reflected in sysfs.
Signed-off-by: Nathan Fontent nf...@austin.ibm.com
---
Documentation/memory-hotplug.txt | 40 +++
1 file changed, 24 insertions(+), 16 deletions(-)
Michael Ellerman michael at ellerman.id.au writes:
On Tue, 2010-04-20 at 17:17 -0500, Brian King wrote:
In stress testing enabling and disabling of SMT, we are regularly
seeing the badness warning below. Looking through the cpu offline
path, this is what I see:
1. stop_cpu: IRQ's
30 matches
Mail list logo
