On Tue, 2010-05-11 at 16:28 +1000, Michael Neuling wrote:
> Currently for kexec the PTE tear down on 1TB segment systems normally
> requires 3 hcalls for each PTE removal. On a machine with 32GB of
> memory it can take around a minute to remove all the PTEs.
>
..
> - /* TODO: Use bulk call */
Hello all,
I'm looking for hints on a curious problem.
I have a working kernel on a custom embedded device and it works fine.
We came up with a variation of the device with a few hardware changes, one
of them being the number of serial ports that goes from 4 to 2.
In order to save time I tried
add_dyn_reconf_usable_mem_property() iterates over memory spans
in /ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory and intersects
these with usablemem_rgns ranges. Not only did it seem to write
null properties for every range that didn't match, but it used an unchecked
fixed-size array whi
In usual workload, the number of dirty pages varies a lot for each
iteration
and we should gain really a lot for relatively clean cases.
Can you post such a test, for an idle large guest?
OK, I'll do!
Result of "low workload test" (running top during migration) first,
4GB guest
picked u
On May 10, 2010, at 2:15 PM, Felix Radensky wrote:
> Fix legacy PCI-E interrupt mapping for PCI-E slot 0 of
> P2020DS evaluation board. The patch is based on P2020DS
> device tree from Freescale BSP for this board.
>
> Signed-off-by: Felix Radensky
> ---
> arch/powerpc/boot/dts/p2020ds.dts |
On May 10, 2010, at 2:15 PM, Felix Radensky wrote:Fix legacy PCI-E interrupt mapping for PCI-E slot 0 ofP2020DS evaluation board. The patch is based on P2020DSdevice tree from Freescale BSP for this board.Signed-off-by: Felix Radensky ---arch/powerpc/boot/dts/p2020ds.dts | 8 1 files chan
On Tue, 2010-05-11 at 14:59 +1000, Anton Blanchard wrote:
> Author: Milton Miller
>
> On large machines we are running out of room below 256MB. In some cases we
> only need to ensure the allocation is in the first segment, which may be
> 256MB or 1TB.
>
> Add slb0_limit and use it to specify the
ICON is based on the AppliedMicro 440SPe. It is equipped with
64MByte NOR FLASH, SODIMM, Gigabit ethernet, SM502 on PCI(X),
LSI SAS1068E on PCIe0 and custom FPGA on PCIe1.
Signed-off-by: Stefan Roese
Cc: Josh Boyer
---
arch/powerpc/boot/dts/icon.dts | 447 ++
arch/powerpc/c
On Tue, May 11, 2010 at 02:53:54PM +0900, Takuya Yoshikawa wrote:
> (2010/05/11 12:43), Marcelo Tosatti wrote:
> >On Tue, May 04, 2010 at 10:08:21PM +0900, Takuya Yoshikawa wrote:
> >>+How to Get
> >>+
> >>+Before calling this, you have to set the slot member of kvm_user_dirty_log
> >>+to indicate
Hello everybody,
Please find here patch for user land kexec-tools application. Following
patch makes kexec-tools work for both kexec and kdump. I tested it with
git kernel (linus-tree) and Freescale/Logic MPC8360ERDK board with
mpc83xx_defconfig kernel config.
kex
Best regards,
Maxim Uvarov.
From: Maxim Uvarov
Signed-off-by: Maxim Uvarov
---
arch/powerpc/kernel/crash.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/kernel/crash.c b/arch/powerpc/kernel/crash.c
index 6f4613d..341d8af 100644
--- a/arch/powerpc/kern
Takuya Yoshikawa wrote:
> Hi, sorry for sending from my personal account.
> The following series are all from me:
>
> From: Takuya Yoshikawa
>
> The 3rd version of "moving dirty bitmaps to user space".
>
> From this version, we add x86 and ppc and asm-generic people to CC lists.
>
>
> [To KVM
Takuya Yoshikawa wrote:
> During the work of KVM's dirty page logging optimization, we encountered
> the need of manipulating bitmaps in user space efficiantly. To achive this,
> we introduce a uaccess function for setting a bit in user space following
> Avi's suggestion.
>
> KVM is now using dir
Hi,
> diff --git a/arch/powerpc/kernel/crash.c b/arch/powerpc/kernel/crash.c
> index 6f4613d..341d8af 100644
> --- a/arch/powerpc/kernel/crash.c
> +++ b/arch/powerpc/kernel/crash.c
> @@ -375,6 +375,9 @@ void default_machine_crash_shutdown(struct pt_regs *regs)
> for_each_irq(i) {
>
This patch is required in case if you are using new toolchains.
Best regards,
Maxim Uvarov.
From: Maxim Uvarov
Signed-off-by: Maxim Uvarov
---
kexec/arch/ppc/Makefile|2
kexec/arch/ppc/crashdump-powerpc.c | 439 ++
kexec/arch/ppc/crashdump-p
This patch is required in case if you are using new toolchains.
Best regards,
Maxim Uvarov.
From: Maxim Uvarov
Linker does not provide some vital functions when building freestanding
applications with a new toolchain, so we have to provide our own CRT.
p.s.
Without the CRT we won't see any bu
Forgot to add purgatory/arch/ppc/crt.S to the patch. Resending...
--
This patch is required in case if you are using new toolchains.
Best regards,
Maxim Uvarov.
From: Maxim Uvarov
Linker does not provide some vital functions when building freestanding
applications with a new toolchain, so we h
On Tue, 11 May 2010 at 21:47, Maxim Uvarov wrote:
> This patch is required in case if you are using new toolchains.
Ah, thanks I was missing (and looking for) crashdump-powerpc.h
already :-)
Christian
--
make bzImage, not war
___
Linuxppc-dev mailing l
Am Mittwoch 05 Mai 2010 17:20:21 schrieb Peter Hüwe:
> From: Peter Huewe
>
> This patch adds a missing include linux/delay.h to prevent
> build failures[1-5]
>
> Signed-off-by: Peter Huewe
> ---
Any updates on this patch?
Issue still exists with today's linux-next tree
Thanks,
Peter
__
On 10 May 2010 20:38, Anton Blanchard wrote:
>
> If we take an EEH early enough, we oops:
>
>
> Call Trace:
> [c00010483770] [c0013ee4] .show_stack+0xd8/0x218 (unreliable)
> [c00010483850] [c0658940] .dump_stack+0x28/0x3c
> [c000104838d0] [c0057a68] .eeh_dn_chec
Hi Kumar,
On 5/11/2010 3:36 PM, Kumar Gala wrote:
On May 10, 2010, at 2:15 PM, Felix Radensky wrote:
Fix legacy PCI-E interrupt mapping for PCI-E slot 0 of
P2020DS evaluation board. The patch is based on P2020DS
device tree from Freescale BSP for this board.
Signed-off-by: Felix Radensky
On Tue, 11 May 2010 21:03:27 +0200, Andre Prendel wrote:
> On Mon, May 10, 2010 at 10:43:07AM -0400, Jeff Angielski wrote:
>
> Hi Jeff,
>
> A few comments below.
>
> > Add support for reading and writing the n-factor correction
> > registers. This is needed to compensate for the characteristic
On 05/11/2010 03:03 PM, Andre Prendel wrote:
On Mon, May 10, 2010 at 10:43:07AM -0400, Jeff Angielski wrote:
Hi Jeff,
A few comments below.
Add support for reading and writing the n-factor correction
registers. This is needed to compensate for the characteristics
of a particular sensor hangi
The needs_freset bit went in since the last time I touched
all this code, so I don't think this will affect ipr at least.
The way this works for the ipr adapters we needed a warm reset
for was, we would get the hot reset in the generic EEH code, the
the ipr driver would come along after that and is
On Mon, May 10, 2010 at 10:43:07AM -0400, Jeff Angielski wrote:
Hi Jeff,
A few comments below.
> Add support for reading and writing the n-factor correction
> registers. This is needed to compensate for the characteristics
> of a particular sensor hanging off of the remote channels.
>
> Signe
Hi,
I am working with the PowerPC 405 in the Virtex-II Pro FPGA. I've
come across a possible problem where the device tree is located in at
an address that the kernel cannot access if link_address (the location
where zImage executes from, set in the "wrapper" script) is set too
high (somewhere in
In message <1273561463.9209.138.ca...@concordia> you wrote:
>
> --=-S056dRzmrEHDBzKyyTOs
> Content-Type: text/plain; charset="UTF-8"
> Content-Transfer-Encoding: quoted-printable
>
> On Tue, 2010-05-11 at 16:28 +1000, Michael Neuling wrote:
> > Currently for kexec the PTE tear down on 1TB segme
On Wed, 2010-05-12 at 09:29 +1000, Michael Neuling wrote:
>
> In message <1273561463.9209.138.ca...@concordia> you wrote:
> >
> > --=-S056dRzmrEHDBzKyyTOs
> > Content-Type: text/plain; charset="UTF-8"
> > Content-Transfer-Encoding: quoted-printable
> >
> > On Tue, 2010-05-11 at 16:28 +1000, Mich
In message <1273624565.5738.8.ca...@concordia> you wrote:
>
> --=-wnrJa93KBardFtse2eHB
> Content-Type: text/plain; charset="UTF-8"
> Content-Transfer-Encoding: quoted-printable
>
> On Wed, 2010-05-12 at 09:29 +1000, Michael Neuling wrote:
> >=20
> > In message <1273561463.9209.138.ca...@concord
On Wed, May 12, 2010 at 10:43:08AM +1000, Michael Neuling wrote:
> We probably only do the remove on < 1% of the hptes now. So I doubt we
> would get a speedup since most of the time we aren't do the remove
> anymore.
It would be nice to have some actual numbers. Could you add some
counters and
> > We probably only do the remove on < 1% of the hptes now. So I doubt we
> > would get a speedup since most of the time we aren't do the remove
> > anymore.
>
> It would be nice to have some actual numbers. Could you add some
> counters and print the results at the end? (Or don't you have any
On Wed, 2010-05-12 at 11:06 +1000, Michael Neuling wrote:
> > > We probably only do the remove on < 1% of the hptes now. So I doubt we
> > > would get a speedup since most of the time we aren't do the remove
> > > anymore.
> >
> > It would be nice to have some actual numbers. Could you add some
The code to fixup the serial ports on 440SPe uses the incorrect
addresses for these. This fixes it.
Signed-off-by: Benjamin Herrenschmidt
---
I'm surprised nobody noticed, serial is pretty busted for me without
that patch :-)
diff --git a/arch/powerpc/boot/4xx.c b/arch/powerpc/boot/4xx.c
index
Hi Stefan !
(Or somebody from AMCC)
I noticed we still have this old problem on PCIe where some cards don't
seem to work. The link trains but they don't respond on config space.
This is the case for example of that Sunix quad USB card. It seems to be
related to the kind of TI PCIe <-> PCI bridge
In message <4be9102c.6040...@axio.ms> you wrote:
>
> add_dyn_reconf_usable_mem_property() iterates over memory spans
> in /ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory and intersects
> these with usablemem_rgns ranges. Not only did it seem to write
> null properties for every range tha
On Wed, 2010-05-12 at 12:40 +1000, Benjamin Herrenschmidt wrote:
> Hi Stefan !
>
> (Or somebody from AMCC)
>
> I noticed we still have this old problem on PCIe where some cards don't
> seem to work. The link trains but they don't respond on config space.
> This is the case for example of that Sun
Hi Ben/Paul,
Please find a new version of the patchset that implements hw-breakpoint
interfaces for PowerPC Book III S. The changes in this version over the previous
version are as listed below, and are the result of addressing comments
received for the previous version.
Changelog - ver X
Data address breakpoint exceptions are currently handled along with page-faults
which require interrupts to remain in enabled state. Since exception handling
for data breakpoints aren't pre-empt safe, we handle them separately.
Signed-off-by: K.Prasad
Acked-by: Paul Mackerras
---
arch/powerpc/k
Certain architectures (such as PowerPC Book III S) have a need to cleanup
data-structures before the breakpoint is unregistered. This patch introduces
an arch-specific hook in release_bp_slot() along with a weak definition in
the form of a stub funciton.
Signed-off-by: K.Prasad
---
kernel/hw_bre
Implement perf-events based hw-breakpoint interfaces for PowerPC Book III S
processors. These interfaces help arbitrate requests from various users and
schedules them as appropriate.
Signed-off-by: K.Prasad
---
arch/powerpc/Kconfig |1
arch/powerpc/include/asm/cputable.h
On Wed, May 05, 2010 at 02:03:03AM +0530, K.Prasad wrote:
> On Mon, May 03, 2010 at 04:23:30PM +1000, Paul Mackerras wrote:
> > On Wed, Apr 14, 2010 at 09:18:27AM +0530, K.Prasad wrote:
> >
[snipped]
>
> It has been pointed out to me before (Roland's mail Ref:linuxppc-dev
> message-id: 2010011910
> -Original Message-
> From: Benjamin Herrenschmidt [mailto:b...@kernel.crashing.org]
> Sent: Tuesday, May 11, 2010 8:03 PM
> To: Stefan Roese
> Cc: linuxppc-dev; Pravin Bathija
> Subject: Re: 440SPe/Katmai PCIe problems
>
> On Wed, 2010-05-12 at 12:40 +1000, Benjamin Herrenschmidt wrote:
Maxim Uvarov wrote on 2010-05-11 10:47 :
> This patch is required in case if you are using new toolchains.
I'm on Debian/stable (binutils 2.18, gcc 4.3.2), so I applied your patches
to the latest -git checkout:
First, compilation fails with:
cc1: warnings being treated as errors
kexec/arch/ppc/
One alternative would be:
KVM_SWITCH_DIRTY_LOG passing the address of a bitmap. If the active
bitmap was clean, it returns 0, no switch performed. If the active
bitmap was dirty, the kernel switches to the new bitmap and returns 1.
And the responsability of cleaning the new bitmap could also b
r = 0;
@@ -1195,11 +1232,16 @@ void mark_page_dirty(struct kvm *kvm, gfn_t gfn)
gfn = unalias_gfn(kvm, gfn);
memslot = gfn_to_memslot_unaliased(kvm, gfn);
if (memslot&& memslot->dirty_bitmap) {
- unsigned long rel_gfn = gfn - memslot->base_gfn;
+
On Wed, May 05, 2010 at 02:03:03AM +0530, K.Prasad wrote:
> It is true that the breakpoint exceptions will go amiss following the
> alignment exception, and be restored when the thread single-steps due
> to other requests causing undesirable effects. (Borrowing from some of
> the discussions I had
Hi kumar,
I just want to know whether the erratum of MPC8640D has fixed on
u-boot or linux ?
-Thirumalai
CAUTION - Disclaimer *This email may contain
confidential and privileged material for the
sole use of the intended recipient(s). Any review, use,
2010/5/12 Christian Kujau
> Maxim Uvarov wrote on 2010-05-11 10:47 :
> > This patch is required in case if you are using new toolchains.
>
> I'm on Debian/stable (binutils 2.18, gcc 4.3.2), so I applied your patches
> to the latest -git checkout:
>
> First, compilation fails with:
>
> cc1: warnin
On Wed, 12 May 2010 at 10:31, Maxim Uvarov wrote:
> Yes, that is expected result for old tool chains. New tool chains (from code
> sourcery ) need this crt.S.
> I think we can have --with-oldtoolchain option to configure to point to old
> tool chains. (or even rename it to --with-crts,
> I don't k
49 matches
Mail list logo
