From: Ingo Molnar
Date: Thu, 15 Apr 2010 08:49:40 +0200
> Btw., WARN_ON trapping on PowerPC is clearly a PowerPC bug - there's a good
> reason we have WARN_ON versus BUG_ON - it should be fixed.
I disagree, an implementation should be allowed to use the most
efficient implementation possible fo
On Thu, 2010-04-15 at 16:12 +1000, Stephen Rothwell wrote:
>
> Caused by commit bd6d29c25bb1a24a4c160ec5de43e0004e01f72b ("lockstat:
> Make lockstat counting per cpu"). This added a WARN_ON_ONCE to
> debug_atomic_inc() which is called from trace_hardirqs_on_caller()
> with
> irqs enabled.
>
> Li
Hi all,
Yesterday's (and today's) linux-next boot (PowerPC) failed like this:
[ cut here ]
Badness at kernel/lockdep.c:2301
NIP: c00a35c8 LR: c00084c4 CTR:
REGS: c0bf77e0 TRAP: 0700 Not tainted (2.6.34-rc4-autokern1)
MSR: 800
In message <1271208670.2834.55.ca...@sbs-t61.sc.intel.com> you wrote:
> On Tue, 2010-04-13 at 05:29 -0700, Peter Zijlstra wrote:
> > On Fri, 2010-04-09 at 16:21 +1000, Michael Neuling wrote:
> > > With the asymmetric packing infrastructure, fix_small_imbalance is
> > > causing idle higher threads t
On Wed, 2010-04-14 at 22:07 -0500, Bill Gatliff wrote:
>
> Anyone have any suggestions on where to start with this one? Anyone
> else running a similar configuration with any success? I'm completely
> lost, and running out of hair *fast*...
Most probably endian bugs in the Lime driver ...
Chee
> On Fri, 2010-04-09 at 16:21 +1000, Michael Neuling wrote:
> > need_active_balance() gates the asymmetric packing based due to power
> > save logic, but for packing we don't care.
>
> This explanation lacks a how/why.
>
> So the problem is that need_active_balance() ends up returning false and
>
From: Ian Munsie
This patch adds mappings from the register numbers from DWARF to the
register names used in the PowerPC Regs and Stack Access API. This
allows perf probe to be used to record variable contents on PowerPC.
This patch depends on functionality in the powerpc/next tree, though it
wi
From: Ian Munsie
The perf userspace tool included some architecture specific code to map
registers from the DWARF register number into the names used by the regs
and stack access API.
This patch moves the architecture specific code out into a separate
arch/x86 directory along with the infrastruc
These patches add the required mappings to use perf probe on PowerPC.
Part 1 of the patch series moves the arch dependent x86 32 and 64 bit DWARF
register number mappings out into a separate arch directory and adds the
necessary Makefile foo to use it.
Part 2 of the patch series adds the PowerPC
Guys:
I'm not quite sure where to ask this question, but all my attempts
elsewhere have come up short, so...
Put simply, I have an MPC5200b platform with a Fujitsu "Lime" GDC, and
I'm trying to run Debian squeeze's xorg on it.
Actually, I *have* Debian squeeze's xorg running on the platform jus
I don't think the internal RTC is workable. I've read the RTC section in the
MPC5121 data sheet, and I found that the RTC only keep the time tick
register using VBAT. So if there is a power failure, the RTC will lost its
minute and hour information. After the system boot up, the kernel will read
th
On Wed, 2010-04-14 at 08:55 -0500, Jake Magee wrote:
> On Thu, Mar 25, 2010 at 8:26 PM, Dan Wilson
> wrote:
> We are building a PCI-E device for use in an embedded system
> with an 85xx processor. One of our customers is adamant that
> linux PCI-E hot-swap support will not
Dear =?iso-8859-1?Q?CTAG_/_Mois=E9s_Dom=EDnguez?=,
In message you wrote:
>
> Looking in rtc-mpc5121.c code I didn't find anything related to Keep Alive
> Register (where TAMP bit is) so I would like to know where this issue is
> taking into account or if it is really being taking into account in
Heiko Carstens wrote:
> On Wed, Apr 14, 2010 at 07:46:12AM -0700, Masami Hiramatsu wrote:
>> Ian Munsie wrote:
>>> From: Ian Munsie
>>>
>>> The perf userspace tool included some architecture specific code to map
>>> registers from the DWARF register number into the names used by the regs
>>> and s
On Wed, Apr 14, 2010 at 07:46:12AM -0700, Masami Hiramatsu wrote:
> Ian Munsie wrote:
> > From: Ian Munsie
> >
> > The perf userspace tool included some architecture specific code to map
> > registers from the DWARF register number into the names used by the regs
> > and stack access API.
> >
>
Ian Munsie wrote:
> From: Ian Munsie
>
> The perf userspace tool included some architecture specific code to map
> registers from the DWARF register number into the names used by the regs
> and stack access API.
>
> This patch moves the architecture specific code out into a separate
> arch/x86 d
Dan,
Were you able to get PCI-E hotplug working? I could not get this working
myself and assumed that driver support was lacking. I'm actually using a
PPC405.
Thanks,
Jake
On Thu, Mar 25, 2010 at 8:26 PM, Dan Wilson wrote:
> We are building a PCI-E device for use in an embedded system with a
On Wed, 2010-04-14 at 16:46 +1000, Paul Mackerras wrote:
> Anton Blanchard found that large POWER systems would occasionally
> crash in the exception exit path when profiling with perf_events.
> The symptom was that an interrupt would occur late in the exit path
> when the MSR[RI] (recoverable inte
Hi,
I am trying to use internal Real Time Clock of my ads5121 board .So that I
am using /dev/rtc-0 device with linux/Documentation/rtc.txt example. I can
read and write time/date but I notice RTC is not being updated as if VBAT
was off or there was not oscillator (I tested oscillator and VBAT)
Dear all,
I'm new to PPC Linux development. Recently I'm learning how to write a
Linux device driver on MPC5121 based embedded system. I'm just confused
about the OF related code in the kernel.
I know in the Linux device driver model, a driver is attached to a
device through the bus_type me
20 matches
Mail list logo
