size_t size =3D 0;
FILE *file;
sprintf(buf, /proc/irq/%i/smp_affinity, number);
- file =3D fopen(buf, r);
+ file =3D fopen(buf, r+);
if (!file)
On Friday 24 September 2010 00:39:47 Tirumala Marri wrote:
Will both versions of this driver exist in the same kernel build? For
example the iop-adma driver supports iop13xx and iop3xx, but we select
the archtitecture at build time? Or, as I assume in this case, will
the
two (maybe
On Thu, Sep 16, 2010 at 09:05:03AM +0200, christophe leroy wrote:
This patch applies to 2.6.34.7 and 2.6.35.4
It fixes an issue during the probe for CPM1 with definition of parameter ram
from DTS
Signed-off-by: christophe leroy christophe.le...@c-s.fr
I'm sorry, I don't understand the fix
Hello,
The issue is that cpm_muram_alloc_fixed() allocates memory from the
general purpose muram area (from 0x0 to 0x1bff).
Here we need to return a pointer to the parameter RAM, which is located
somewhere starting at 0x1c00. It is not a dynamic allocation that is
required here but only to
On Thu, Sep 23, 2010 at 12:48:51PM -0700, john stultz wrote:
On Thu, 2010-09-23 at 19:31 +0200, Richard Cochran wrote:
A new syscall is introduced that allows tuning of a POSIX clock. The
syscall is implemented for four architectures: arm, blackfin, powerpc,
and x86.
The new syscall,
On Fri, Sep 24, 2010 at 08:03:43AM +1000, Benjamin Herrenschmidt wrote:
On Thu, 2010-09-23 at 19:31 +0200, Richard Cochran wrote:
A new syscall is introduced that allows tuning of a POSIX clock. The
syscall is implemented for four architectures: arm, blackfin, powerpc,
and x86.
The new
Hello,
On Fri, Sep 24, 2010 at 09:20:27AM +0200, LEROY Christophe wrote:
The issue is that cpm_muram_alloc_fixed() allocates memory from the
general purpose muram area (from 0x0 to 0x1bff).
Here we need to return a pointer to the parameter RAM, which is
located somewhere starting at 0x1c00.
On Thu, Sep 23, 2010 at 12:53:20PM -0500, Christoph Lameter wrote:
On Thu, 23 Sep 2010, Richard Cochran wrote:
3.3 Synchronizing the Linux System Time
One could offer a PHC as a combined clock source and clock event
device. The advantage of
On Thu, Sep 23, 2010 at 02:17:36PM -0500, Christoph Lameter wrote:
On Thu, 23 Sep 2010, Richard Cochran wrote:
+ These properties set the operational parameters for the PTP
+ clock. You must choose these carefully for the clock to work right.
+ Here is how to figure good values:
+
+
On Thu, 23 Sep 2010 15:05:59 -0700, Randy Dunlap wrote:
On Thu, 23 Sep 2010 22:16:32 +0200 Mikael Pettersson wrote:
Randy Dunlap writes:
No kconfig warnings?
Not that I recall. I can check tomorrow if necessary.
No kconfig warnings. I checked with your .config file.
Please
On Fri, Sep 24, 2010 at 02:43:52PM +1000, Benjamin Herrenschmidt wrote:
The DMA is what I use in the real world case to get data into and out
of these buffers. However, I can disable the DMA completely and do only
the kmalloc. In this case I still see the same poor performance. My
On Fri, Sep 24, 2010 at 04:56:34PM +1000, Michael Neuling wrote:
size_t size =3D 0;
FILE *file;
sprintf(buf, /proc/irq/%i/smp_affinity,
number);
- file =3D fopen(buf, r);
+
Jean Delvare writes:
On Thu, 23 Sep 2010 15:05:59 -0700, Randy Dunlap wrote:
On Thu, 23 Sep 2010 22:16:32 +0200 Mikael Pettersson wrote:
Randy Dunlap writes:
No kconfig warnings?
Not that I recall. I can check tomorrow if necessary.
No kconfig warnings. I checked
On Fri, 2010-09-24 at 07:09 +0200, Chen, Tiejun wrote:
Right but this should be done for RC mode, not for EP mode we're
discussing.
Tiejun
According to the Freescale documentation, outbound is just as valid for
endpoint as for root complex - indeed, to generate MSIs from software
REQUIRES
However, if the clock selected by the BMC is switched off, loses its
network connection..., the second best clock is selected by the BMC and
becomes master. This clock may be less accurate and thus our slave clock
has to switch from one notion of time to another. Is that the conflict
you
Hi Mikael,
On Fri, 24 Sep 2010 12:50:01 +0200, Mikael Pettersson wrote:
Jean Delvare writes:
As far as I can see this is caused by this commit from Grant:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=959e85f7751c33d1a2dabc5cc3fe2ed0db7052e5
On Fri, Sep 24, 2010 at 06:30:34AM -0400, Josh Boyer wrote:
On Fri, Sep 24, 2010 at 02:43:52PM +1000, Benjamin Herrenschmidt wrote:
The DMA is what I use in the real world case to get data into and out
of these buffers. However, I can disable the DMA completely and do only
the kmalloc.
On Thu, Sep 23, 2010 at 09:36:54PM +0100, Alan Cox wrote:
Drop the clockid_t and swap it for a file handle like a proper Unix or
Linux interface. The rest is much the same
fd = open /sys/class/timesource/[whatever]
various queries you may want to do to check the name etc
On Fri, 24 Sep 2010 15:14:07 +0200
Richard Cochran richardcoch...@gmail.com wrote:
On Thu, Sep 23, 2010 at 09:36:54PM +0100, Alan Cox wrote:
Drop the clockid_t and swap it for a file handle like a proper Unix or
Linux interface. The rest is much the same
fd = open
You can't do that avoiding as you might like because the behaviour of
file handle numbering is defined by the standards. Hence the f*
versions of the calls (and of lots of other stuff)
Whether you add new syscalls or do the fd passing using flags and hide
the ugly bits in glibc is another
Jean Delvare kh...@linux-fr.org wrote:
Hi Mikael,
On Fri, 24 Sep 2010 12:50:01 +0200, Mikael Pettersson wrote:
Jean Delvare writes:
As far as I can see this is caused by this commit from Grant:
On Thu, Sep 23, 2010 at 12:38:53PM -0700, john stultz wrote:
On Thu, 2010-09-23 at 19:30 +0200, Richard Cochran wrote:
/sys/class/timesource/name/id
/sys/class/ptp/ptp_clock_X/id
So yea, I'm not a fan of the timesource sysfs interface. One, I think
the name is poor (posix_clocks
Instead, I think having the id hanging off the class driver is much
better, as it allows mapping the actual hardware to the id more clearly.
So I'd drop the timesource listing. And maybe change id to
clock_id so its a little more clear what the id is for.
Okay, I will drop
On 09/23/2010 01:40 PM, Balbir Singh wrote:
* Nathan Fontenot nf...@austin.ibm.com [2010-09-22 09:15:43]:
This set of patches decouples the concept that a single memory
section corresponds to a single directory in
/sys/devices/system/memory/. On systems
with large amounts of memory (1+
On Fri, 24 Sep 2010 07:04:28 +0200
Chen, Tiejun tiejun.c...@windriver.com wrote:
-Original Message-
From:
linuxppc-dev-bounces+tiejun.chen=windriver@lists.ozlabs.or
g
[mailto:linuxppc-dev-bounces+tiejun.chen=windriver@lists.o
zlabs.org] On Behalf Of Benjamin
On Fri, 24 Sep 2010 01:10:06 -0600
Grant Likely grant.lik...@secretlab.ca wrote:
On Thu, Sep 16, 2010 at 09:05:03AM +0200, christophe leroy wrote:
This patch applies to 2.6.34.7 and 2.6.35.4
It fixes an issue during the probe for CPM1 with definition of parameter
ram from DTS
On Fri, 24 Sep 2010 11:57:40 +0400
Anton Vorontsov cbouatmai...@gmail.com wrote:
Doesn't explain why that worked on MPC8272 (CPM2) and MPC8560
(also CPM2) machines though. But here's my guess (I no longer
have these boards to test it):
On 8272 I used this node:
+
[Re: [PATCH] powerpc: Fix invalid page flags in create TLB CAM path for
PTE_64BIT] On 24/09/2010 (Fri 07:59) Benjamin Herrenschmidt wrote:
On Thu, 2010-09-23 at 15:33 -0500, Scott Wood wrote:
I don't see a generic accessor that can test PTE flags for user
access -- in the absence of one, I
On Fri, 2010-09-24 at 09:29 +0200, Richard Cochran wrote:
On Thu, Sep 23, 2010 at 12:48:51PM -0700, john stultz wrote:
So I'd still split this patch up a little bit more.
1) Patch that implements the ADJ_SETOFFSET (*and its implementation*)
in do_adjtimex.
2) Patch that adds the
These two patches reduce the frequency that the tlb caches are flushed in
hardware. Both the normal tlb cache and the shadow tlb cache, which
separates the tlbs for data and instruction access (dTLB and iTLB).
Dave Kleikamp (2):
476: Set CCR2[DSTI] to prevent isync from flushing shadow TLB
When the DSTI (Disable Shadow TLB Invalidate) bit is set in the CCR2
register, the isync command does not flush the shadow TLB (iTLB dTLB).
However, since the shadow TLB does not contain context information, we
want the shadow TLB flushed in situations where we are switching context.
In those
On PPC_MMU_NOHASH processors that support a large number of contexts,
implement a lazy flush_tlb_mm() that switches to a free context, marking
the old one stale. The tlb is only flushed when no free contexts are
available.
The lazy tlb flushing is controlled by the global variable tlb_lazy_flush
It would be really preferable to support all those platforms in a
single Linux
image. If technically possible, please try to move this direction.
It is do-able for couple of SoCs. Other SoC DMA engines are quite a bit
different.
Let me first do small steps first and slowly achieve some run
This series adds support for scatterlist to scatterlist transfers to the
generic DMAEngine API. I have unconditionally enabled it when the fsldma
driver is used to make testing easier. This feature should probably be
selected by individual drivers.
This series is intended to lay the groundwork
This adds support for scatterlist to scatterlist DMA transfers. As
requested by Dan, this is hidden behind an ifdef so that it can be
selected by the drivers that need it.
Signed-off-by: Ira W. Snyder i...@ovro.caltech.edu
---
drivers/dma/Kconfig |4 ++
drivers/dma/dmaengine.c | 119
The fsldma driver uses the DMA_SLAVE API to handle scatterlist to
scatterlist DMA transfers. For quite a while now, it has been possible
to mimic the operation by using the device_prep_dma_memcpy() routine
intelligently.
Now that the DMAEngine API has grown generic support for scatterlist to
On Fri, Sep 24, 2010 at 12:46 PM, Ira W. Snyder i...@ovro.caltech.edu wrote:
This adds support for scatterlist to scatterlist DMA transfers. As
requested by Dan, this is hidden behind an ifdef so that it can be
selected by the drivers that need it.
Signed-off-by: Ira W. Snyder
On Fri, Sep 24, 2010 at 01:40:56PM -0700, Dan Williams wrote:
On Fri, Sep 24, 2010 at 12:46 PM, Ira W. Snyder i...@ovro.caltech.edu wrote:
This adds support for scatterlist to scatterlist DMA transfers. As
requested by Dan, this is hidden behind an ifdef so that it can be
selected by the
Add a config option for the (batched) MULTITCE and BULK_REMOVE h-calls.
By default, these options are on and are beneficial for performance and
throughput reasons. If disabled, the code will fall back to using less
optimal TCE and REMOVE hcalls. The ability to easily disable these
options is
On Fri, 2010-09-24 at 14:24 -0700, Ira W. Snyder wrote:
On Fri, Sep 24, 2010 at 01:40:56PM -0700, Dan Williams wrote:
I don't think any dma channels gracefully handle descriptors that were
prepped but not submitted. You would probably need to submit the
backlog, poll for completion, and
On Fri, Sep 24, 2010 at 02:53:14PM -0700, Dan Williams wrote:
On Fri, 2010-09-24 at 14:24 -0700, Ira W. Snyder wrote:
On Fri, Sep 24, 2010 at 01:40:56PM -0700, Dan Williams wrote:
I don't think any dma channels gracefully handle descriptors that were
prepped but not submitted. You would
On Fri, 2010-09-24 at 08:08 -0500, Ayman El-Khashab wrote:
I suppose another option is to to use the kernel profiling option I
always see but have never used. Is that a viable option to figure out
what is happening here?
With perf and stochastic sampling ? If you sample fast enough...
This list is getting way too much unrelated stuff, which I find
annoying, it would be nice if we were all a bit more careful here with
our CC lists.
Sorry, I only added device-tree because some one asked me to do so.
http://marc.info/?l=linux-netdevm=127273157912358
I'll leave
Commit 959e85f7, i2c: add OF-style registration and binding caused a
module dependency loop where of_i2c.c calls functions in i2c-core, and
i2c-core calls of_i2c_register_devices() in of_i2c. This means that
when i2c support is built as a module when CONFIG_OF is set, then
neither i2c_core nor
On Fri, Sep 24, 2010 at 7:48 AM, Grant Likely grant.lik...@secretlab.ca wrote:
Jean Delvare kh...@linux-fr.org wrote:
Hi Mikael,
On Fri, 24 Sep 2010 12:50:01 +0200, Mikael Pettersson wrote:
Jean Delvare writes:
As far as I can see this is caused by this commit from Grant:
Commit 959e85f7, i2c: add OF-style registration and binding caused a
module dependency loop where of_i2c.c calls functions in i2c-core, and
i2c-core calls of_i2c_register_devices() in of_i2c. This means that
when i2c support is built as a module when CONFIG_OF is set, then
neither i2c_core nor
On Fri, 2010-09-24 at 15:04 -0700, Ira W. Snyder wrote:
On Fri, Sep 24, 2010 at 02:53:14PM -0700, Dan Williams wrote:
What about overrun or underrun do we not care if src_total != dst_total?
Otherwise looks ok.
I don't know if we should care about that. The algorithm handles that
On Fri, Sep 24, 2010 at 03:04:19PM -0700, Ira W. Snyder wrote:
On Fri, Sep 24, 2010 at 02:53:14PM -0700, Dan Williams wrote:
On Fri, 2010-09-24 at 14:24 -0700, Ira W. Snyder wrote:
On Fri, Sep 24, 2010 at 01:40:56PM -0700, Dan Williams wrote:
I don't think any dma channels gracefully
This series adds support for scatterlist to scatterlist transfers to the
generic DMAEngine API. I have hidden it behind a configuration option to
allow specific drivers that need this functionality to enable it.
This series is intended to lay the groundwork for further changes to the
series
This adds support for scatterlist to scatterlist DMA transfers. This is
currently hidden behind a configuration option, which will allow drivers
which need this functionality to select it individually.
Signed-off-by: Ira W. Snyder i...@ovro.caltech.edu
---
drivers/dma/Kconfig |3 +
The fsldma driver uses the DMA_SLAVE API to handle scatterlist to
scatterlist DMA transfers. For quite a while now, it has been possible
to mimic the operation by using the device_prep_dma_memcpy() routine
intelligently.
Now that the DMAEngine API has grown generic support for scatterlist to
51 matches
Mail list logo
