On Thu, Oct 11, 2012 at 7:41 AM, Konrad Rzeszutek Wilk
wrote:
> On Wed, Oct 10, 2012 at 08:49:05AM -0700, Yinghai Lu wrote:
>>
>> yes that is some extreme case:
>> assume that 2M range is [2T-2M, 2T),
>
> What is T in here? Terabyte? Is the '[' vs ')' a significance in your
> explanation? Should
On Fri, 12 Oct 2012 00:45:06 +0200
richard -rw- weinberger wrote:
> On Fri, Oct 12, 2012 at 12:19 AM, Andrew Morton
> wrote:
> > On Thu, 11 Oct 2012 21:54:18 +1100 (EST)
> > James Morris wrote:
> >
> >> Please pull these fixes for the TPM code.
> >>
> >> The following changes since commit
>
On Fri, Oct 12, 2012 at 12:19 AM, Andrew Morton
wrote:
> On Thu, 11 Oct 2012 21:54:18 +1100 (EST)
> James Morris wrote:
>
>> Please pull these fixes for the TPM code.
>>
>> The following changes since commit 12250d843e8489ee00b5b7726da855e51694e792:
>>
>> Merge branch 'i2c-embedded/for-next'
Ezequiel Garcia writes:
> Hello,
>
> While I've always thought SLUB was the default and recommended allocator,
> I'm surprise to find that it's not always the case:
iirc the main performance reasons for slab over slub have mostly
disappeared, so in theory slab could be finally deprecated now.
Patch series looks good to me. Thanks for doing this properly.
Reviewed-by: Andi Kleen
-Andi
--
a...@linux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info
On Thu, Oct 11, 2012 at 4:57 AM, Michal Hocko wrote:
> oom_badness takes totalpages argument which says how many pages are
> available and it uses it as a base for the score calculation. The value
> is calculated by mem_cgroup_get_limit which considers both limit and
> total_swap_pages (resp.
On Thu, Oct 11, 2012 at 1:26 AM, Yasuaki Ishimatsu
wrote:
> When calling unregister_node(), the function shows following message at
> device_release().
>
> "Device 'node2' does not have a release() function, it is broken and must
> be fixed."
>
> The reason is node's device struct does not have a
On Thu, Oct 11, 2012 at 1:22 AM, Yasuaki Ishimatsu
wrote:
> When calling remove_memory_block(), the function shows following message at
> device_release().
>
> "Device 'memory528' does not have a release() function, it is broken and must
> be fixed."
>
> The reason is memory_block's device struct
On 10/12/2012 12:14 AM, Andrew Morton wrote:
> Could you please do a sysrq-T a few times while it's spinning, to
> confirm that this trace is consistently the culprit?
For me yes, shrink_slab is in the most of the traces.
--
js
suse labs
--
To unsubscribe from this list: send the line
From: Steven Rostedt
Date: Thu, 11 Oct 2012 18:09:45 -0400
> Can you add this to the 3.2 stable tree.
>
> commit 3a3847e007aae732d64d8fd1374126393e9879a3
> Author: Jesse Brandeburg
> Date: Wed Jan 4 20:23:33 2012 +
>
> e1000: fix lockdep splat in shutdown handler
Acked-by: David S.
Hi Linus,
please pull the changes below. Actually there was more stuff but due to
writing my thesis I didn't have time to review it, so the pull request
for the next merge window might be somewhat larger.
Thanks,
Florian Tobias Schandinat
The following changes since commit
On Thu, 11 Oct 2012 21:54:18 +1100 (EST)
James Morris wrote:
> Please pull these fixes for the TPM code.
>
> The following changes since commit 12250d843e8489ee00b5b7726da855e51694e792:
>
> Merge branch 'i2c-embedded/for-next' of
> git://git.pengutronix.de/git/wsa/linux (2012-10-11 10:27:51
Hi Linus,
in the non-critical part of kbuild, I have
* Some make coccicheck improvements and two new tests
* Support for a cleaner html output in scripts/kernel-doc, named html5
(no, it does not play videos, yet)
BTW, Randy wants to route further kernel-doc patches through the kbuild
tree.
[Cc'ed lkml, hence the full-quote]
On Fri, 12 Oct 2012 at 08:33, Dave Chinner wrote:
> On Thu, Oct 11, 2012 at 11:13:14AM -0700, Christian Kujau wrote:
> > Hi,
> >
> > since Linux 3.5 I'm seeing these "inconsistent lock state" lockdep
> > warnings [0]. They show up in 3.6 as well [1]. I was
On Thu, 11 Oct 2012 10:52:28 +0200
Jiri Slaby wrote:
> with 3.6.0-next-20121008, kswapd0 is spinning my CPU at 100% for 1
> minute or so. If I try to suspend to RAM, this trace appears:
> kswapd0 R running task0 577 2 0x
> 00c0
Ben, David,
I posted before a lockdep splat that showed a possible deadlock that was
later fixed by Jesse. I'm now hitting this deadlock on my box while
testing the 3.2-rt kernel.
Please stand by while rebooting the system...
<5>sd 0:0:0:0: [sda] Synchronizing SCSI cache
<3>INFO: task
On 10/11/2012 08:19 PM, valdis.kletni...@vt.edu wrote:
> # zgrep COMPAC /proc/config.gz
> CONFIG_COMPACTION=y
>
> Hope that tells you something useful.
It just supports my another theory. This seems to fix it for me:
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -1830,8 +1830,8 @@ static inline bool
PVH: privcmd changes. PVH only supports the batch interface. To map a
foreign page to a process, pfn must be allocated. PVH path uses
ballooning for that purpose. The returned pfn is then mapped to the
foreign page. xen_unmap_domain_mfn_range() is introduced to unmap these
pages via the privcmd
PVH: balloon and grant changes. For balloon changes we skip setting of
local p2m as it's updated in xen. For grant, the shared grant frame is
the pfn and not mfn, hence its mapped via the same code path as HVM
Signed-off-by: Mukesh R
---
drivers/xen/balloon.c | 18 +++---
Hi Linus,
kconfig in v3.7 is going to
* initialize ncurses only once in menuconfig
* be able to jump to a search result in menuconfig
* change the misnomer oldnoconfig to a more meaningful name
olddefconfig, keeping the old name as alias
Please pull from the below branch.
Thanks,
Michal
The
PVH: smp changes. This pertains to bringing up smp vcpus. PVH runs in
ring 0, so syscalls are native. Also, the vcpu context is send down via
the hcall to be set in the vmcs. gdtaddr and gdtsz are unionionized as
PVH only needs to send these two to be set in the vmcs
Signed-off-by: Mukesh R
---
PVH: bootup and setup related changes. enlighten.c: for PVH we can trap
cpuid via vmexit, so don't need to use emulated prefix call. Check for
vector callback early on, as it is a required feature. PVH runs at
default kernel iopl. setup.c: in xen_add_extra_mem() we can skip
updating p2m as it's
PVH: This patch implements mmu changes for PVH. First the set/clear
mmio pte function makes a hypercall to update the p2m in xen with 1:1
mapping. PVH uses mostly native mmu ops. Two local functions are
introduced to add to xen physmap for xen remap interface. xen unmap
interface is introduced so
PVH: make gdt_frames[]/gdt_ents into a union with {gdtaddr, gdtsz}, PVH
only needs to send down gdtaddr and gdtsz. irq.c: PVH uses
native_irq_ops. vcpu hotplug is currently not available for PVH.
events.c: setup callback vector for PVH. Finally, PVH ring ops uses HVM
paths for xenbus.
Hi Linus,
The main part of kbuild for v3.7 contains:
* Fix for scripts/Makefile.modpost to not choke on a '.ko' substring in
the build directory path
* Two warning fixes (modpost and main Makefile)
* __compiletime_error works also with gcc 4.3
* make tar{gz,bz2,xz}-pkg uses default compression
PVH: is a PV linux guest that has extended capabilities. This patch allows it
to be configured and enabled. Also, basic header file changes to add new
subcalls to physmap hypercall. Lastly, mfn_to_local_pfn must return mfn for
paging mode translate
Signed-off-by: Mukesh R
---
On Thu, Oct 11, 2012 at 11:37:07PM +0200, Henrik Rydberg wrote:
> Hi Hans,
>
> > Oh what fun (not). The best way to figure out what really is going
> > on is to get some usb level traces. Note my first hunch is that what
> > you're seeing is a device firmware bug, as this patch together with
> >
In disk_clear_events, do not put work on system_nrt_freezable_wq. Instead, put
it on system_nrt_wq.
There is a race between probing a usb and suspending the device. Since probing a
usb calls disk_clear_events, which puts work on a frozen workqueue, probing
cannot finish after the workqueue is
On Thu, Oct 11, 2012 at 08:50:33AM +0200, Peter Stuge wrote:
> Henrik Rydberg wrote:
> > > What is the programming cable and software that uses it?
> >
> > The programmer is impact, using libusbx-1.0.14-1.
>
> Do you know for a fact that your version calls libusb-1.0? Did you
> establish this
Hi guys,
Ok, I've made all the changes from prev RFC patch submissions. Tested
all the combinations. The patches are organized slightly differently
from prev version because of the nature of changes after last review. I
am building xen patch just for the corresponding header file changes.
On Thu, Oct 11, 2012 at 10:31:58PM +0100, Grant Likely wrote:
> Hey Matt,
>
> Do you know now similar are the EDMA engines on the am33xx and am389x? I've
> been working on am389x upstreaming and I'll try these patches out if it is
> the same engine.
Hi Grant,
It's the same one. am389x/ti816x
Henrik Rydberg wrote:
> Hi Hans,
>
> > Oh what fun (not). The best way to figure out what really is going
> > on is to get some usb level traces. Note my first hunch is that what
> > you're seeing is a device firmware bug, as this patch together with
> > a new libusb (which you seem to also have)
Hi Hans,
> Oh what fun (not). The best way to figure out what really is going
> on is to get some usb level traces. Note my first hunch is that what
> you're seeing is a device firmware bug, as this patch together with
> a new libusb (which you seem to also have) will make bulk transfers
> run
Removes the DaVinci private SRAM API and replaces it with
the genalloc API. The SRAM gen_pool is passed in pdata since
DaVinci is in the early stages of DT conversion.
Signed-off-by: Matt Porter
---
include/linux/platform_data/davinci_asp.h |3 +++
sound/soc/davinci/davinci-mcasp.c
Passes the DA850 shared SRAM gen_pool to the McASP driver
and enables the ping-pong buffer DMA support.
Signed-off-by: Matt Porter
---
arch/arm/mach-davinci/board-da850-evm.c | 25 +++--
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git
Changes since v1:
- Rebased against uio_pruss/genalloc series v4 patches,
requiring another header to be included.
This series converts davinci ASoC to use genalloc and enables
that support on DA850. It applies to mainline on top of the
uio_pruss/genalloc series [1]
On Fri, Oct 5, 2012 at 10:24 AM, Kim, Milo wrote:
> The LP55xx common driver provides a new header, leds-lp55xx.h.
> This driver enables removing duplicate code for both drivers and
> making coherent driver structure.
> LP5521 and LP5523/55231 platform data were merged into one common file.
On Thu, Oct 11, 2012 at 12:13:33PM -0700, Ian Applegate wrote:
> On machines serving mainly http traffic we are seeing the following
> panic, which is not yet reproducible.
Must be this BUG_ON:
if (!nf_ct_is_confirmed(ct)) {
On Thu, 11 Oct 2012 16:03:07 +0800
Qing Zhu wrote:
> Panic log should be printed on the console, but if someone lock the
> console when panic, console won't print out panic log.
>
> The incomplete panic log issue will happen in below scenarios:
> 1. One task call console_lock(), then panic
On Thu, Oct 11, 2012 at 8:49 PM, Sjur BRENDELAND
wrote:
> This driver is intended for NovaThor SoC and for a configuration with
> LLI as the shared memory interface between the host and modem.
> When using LLI as the shared memory interface the modem could be used
> with any platform/architecture
On Thu, Oct 11, 2012 at 12:51:44PM -0700, John Stultz wrote:
> On 10/11/2012 11:52 AM, Prarit Bhargava wrote:
> >I've been tracking an odd bug that may involve the RCU NOHZ code and
> >just want to know if you have any ideas on debugging and/or what might be
> >wrong. Note the bug happens on
On Thu, 2012-10-11 at 19:40 +0530, Thirumalesha N wrote:
>
> Dear Sir,
>
>I'm new to linux, is there any possibility to install
> kernel-2.4.18-14 in fedora 7?. If not in which fedora version i can
> install this kernel? and if yes how do i proceed ?
I do not know the answer, but
On Tue, Oct 02, 2012 at 11:25:12PM -0700, David Rientjes wrote:
> On Fri, 28 Sep 2012, Daniel Santos wrote:
>
> > NOTE: this is has already been comitted to -mm
> >
> > __attribute__((error(msg))) was introduced in gcc 4.3 (not 4.4) and as I
> > was unable to find any gcc bugs pertaining to it,
While debugging the __pa_symbol inline patch I found that there were a couple
spots where __pa_symbol was used as follows:
__pa_symbol(x) - __pa_symbol(y)
The compiler had reduced them to:
x - y
Since we also support a debug case where __pa_symbol is a function call it
would probably be useful
The function lguest_write_cr3 is using __pa to convert swapper_pg_dir and
initial_page_table from virtual addresses to physical. The correct function
to use for these values is __pa_symbol since they are C visible symbols.
Cc: Rusty Russell
Signed-off-by: Alexander Duyck
---
This change updates a few of the functions to use __pa_symbol when
translating C visible symbols instead of __pa. By using __pa_symbol we are
able to drop a few extra lines of code as don't have to test to see if the
virtual pointer is a part of the kernel text or just standard virtual memory.
This change just updates one spot where __pa was being used when __pa_symbol
should have been used. By using __pa_symbol we are able to drop a few extra
lines of code as we don't have to test to see if the virtual pointer is a
part of the kernel text or just standard virtual memory.
Cc: Len
Instead of using __pa which is meant to be a general function for converting
virtual addresses to physical addresses we can use __pa_symbol which is the
preferred way of decoding kernel text virtual addresses to physical addresses.
In this case we are not directly converting C visible symbols
When I made an attempt at separating __pa_symbol and __pa I found that there
were a number of cases where __pa was used on an obvious symbol.
I also caught one non-obvious case as _brk_start and _brk_end are based on the
address of __brk_base which is a C visible symbol.
Signed-off-by: Alexander
I submitted an earlier patch that make __phys_addr an inline. This obviously
results in an increase in the code size. One step I can take to reduce that
is to make it so that the __pa_symbol call does a direct translation for
kernel addresses instead of covering all of virtual memory.
On my
This patch is meant to improve overall system performance when making use of
the __phys_addr call. To do this I have implemented several changes.
First if CONFIG_DEBUG_VIRTUAL is not defined __phys_addr is made an inline,
similar to how this is currently handled in 32 bit. However in order to
This patch series is meant to address several issues I encountered with VM
translations on x86_64. In my testing I found that swiotlb was incurring up
to a 5% processing overhead due to calls to __phys_addr. To address that I
have updated swiotlb to use physical addresses instead of virtual
Andrew Morton writes:
> On Wed, 10 Oct 2012 16:34:37 -0700
> Jeremy Fitzhardinge wrote:
>
>> On 10/09/2012 06:14 PM, Andrew Morton wrote:
>> > On Wed, 10 Oct 2012 00:09:12 + KY Srinivasan
>> > wrote:
>> >
>> + if (!pg) {
>> + *alloc_error =
Wei Yongjun writes:
> From: Wei Yongjun
>
> Use the module_pci_driver() macro to make the code simpler
> by eliminating module_init and module_exit calls.
>
> dpatch engine is used to auto generate this patch.
> (https://github.com/weiyj/dpatch)
>
> Signed-off-by: Wei Yongjun
Thanks, applied!
Nishanth Menon writes:
> From: Liam Girdwood
>
> Export the OPP functions for use by driver modules.
>
> Cc: "Rafael J. Wysocki"
> Cc: Kevin Hilman
> Cc: linux...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
>
> [n...@ti.com: expansion of functions exported]
> Signed-off-by: Nishanth
Michal, Martin, All,
On Thursday 11 October 2012 22:27:36 Michal Marek wrote:
> Dne 10.10.2012 02:17, Martin Walch napsal(a):
> > The file linux/Documentation/kbuild/kconfig-language.txt says:
> >
> >> The following two methods produce the same kconfig symbol
> >> dependencies but differ greatly
On Mon, 2012-10-01 at 20:31 -0700, David Sharp wrote:
> static int
> -lat_print_timestamp(struct trace_seq *s, u64 abs_usecs,
> - unsigned long rel_usecs)
> +lat_print_timestamp(struct trace_iterator *iter, u64 next_ts)
> {
> - return trace_seq_printf(s, " %4lldus%c: ",
While working on 10Gb/s routing performance I found a significant amount of
time was being spent in the swiotlb DMA handler. Further digging found that a
significant amount of this was due to virtual to physical address translation
and calling the function that did it. It accounted for nearly 60%
This change makes it so that the sync functionality also uses physical
addresses. This helps to further reduce the use of virt_to_phys and
phys_to_virt functions.
In order to clarify things since we now have 2 physical addresses in use
inside of swiotlb_tbl_sync_single I am renaming phys to
Currently swiotlb is the only consumer for swiotlb_bounce. Since that is the
case it doesn't make much sense to be exporting it so make it a static
function only.
In addition we can save a few more lines of code by making it so that it
accepts the DMA address as a physical address instead of a
This change makes it so that the unmap functionality also uses physical
addresses. This helps to further reduce the use of virt_to_phys and
phys_to_virt functions.
In order to clarify things since we now have 2 physical addresses in use
inside of swiotlb_tbl_unmap_single I am renaming phys to
This change makes it so that swiotlb_tbl_map_single will return a physical
address instead of a virtual address when called. The advantage to this once
again is that we are avoiding a number of virt_to_phys and phys_to_virt
translations by working with everything as a physical address.
One
This change makes it so that we can avoid virt_to_phys overhead when using the
io_tlb_overflow_buffer. My original plan was to completely remove the value
and replace it with a constant but I had seen that there were recent patches
that stated this couldn't be done until all device drivers that
This change replaces all references to the virtual address for io_tlb_start
with references to the physical address io_tlb_end. The main advantage of
replacing the virtual address with a physical address is that we can avoid
having to do multiple translations from the virtual address to the
This change replaces all references to the virtual address for io_tlb_end
with references to the physical address io_tlb_end. The main advantage of
replacing the virtual address with a physical address is that we can avoid
having to do multiple translations from the virtual address to the
On Thu, 11 Oct 2012, Yasuaki Ishimatsu wrote:
> When calling unregister_node(), the function shows following message at
> device_release().
>
> "Device 'node2' does not have a release() function, it is broken and must
> be fixed."
>
> The reason is node's device struct does not have a release()
On Thu, 11 Oct 2012 14:55:42 -0500, Jay Purohit said:
> I noticed that the iPhone ethernet driver did not support
> iPhone 5. I quickly added support to it in my kernel, here's
> a patch.
Missing a Signed-off-by: line, and should be cc'ed to net...@vger.kernel.org
so the network people see it.
Dne 10.10.2012 02:17, Martin Walch napsal(a):
> The file linux/Documentation/kbuild/kconfig-language.txt says:
>
>> The following two methods produce the same kconfig symbol
>> dependencies but differ greatly in kconfig symbol existence
>> (production) in the generated config file.
>>
>> case 1:
On Thu, 11 Oct 2012, Yasuaki Ishimatsu wrote:
> When calling remove_memory_block(), the function shows following message at
> device_release().
>
> "Device 'memory528' does not have a release() function, it is broken and must
> be fixed."
>
> The reason is memory_block's device struct does not
On 15:42-20121011, Lee Jones wrote:
> From: Jonas Aaberg
>
> The overhead is very low and the results will be found under
> sysfs/bootime, as well as detailed results in debugfs under
> boottime/. The bootgraph* files are compatible with
> scripts/bootgraph.pl. The rea
On Thu, Oct 11, 2012 at 07:34:42PM +0200, Andrea Arcangeli wrote:
> On Thu, Oct 11, 2012 at 02:46:43PM +0100, Mel Gorman wrote:
> > Should this be a SCHED_FEATURE flag?
>
> I guess it could. It is only used by kernel/sched/numa.c which isn't
> even built unless CONFIG_AUTONUMA is set. So it would
Dne 11.10.2012 15:46, Nicolas Palix napsal(a):
> Hi,
>
> On Thu, Oct 11, 2012 at 3:34 PM, Michal Marek wrote:
>> On Thu, Sep 20, 2012 at 10:30:46PM +0200, Nicolas Palix wrote:
>>> This adds a 'rep+ctxt' mode which prints the warning
>>> message followed by the context.
>>>
>>> Signed-off-by:
Ingo,
Please pull the latest tip/perf/urgent tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/perf/urgent
Head SHA1: 8e49f418c9632790bf456634742d34d97120a784
Vaibhav Nagarnaik (1):
ring-buffer: Check for uninitialized cpu buffer
Dne 11.10.2012 19:04, Yang Bai napsal(a):
> Signed-off-by: Yang Bai
> ---
> scripts/basic/.gitignore |1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/scripts/basic/.gitignore b/scripts/basic/.gitignore
> index a776371..b372870 100644
> --- a/scripts/basic/.gitignore
> +++
On Wed, 10 Oct 2012 14:24:14 +0400
Andrew Vagin wrote:
> A size of pid depends on a level of pidns and now a level of pidns
> is not limited, so it can be more than one page.
>
> Looks reasonable, that it should be limited to a page size. On x86_64
> it will allow to create 125 nested pid
agenhei...@oracle.com
> Cc: konrad.w...@oracle.com
> ---
> drivers/staging/ramster/Kconfig |1 +
> 1 file changed, 1 insertion(+)
>
> --- linux-next-20121011.orig/drivers/staging/ramster/Kconfig
> +++ linux-next-20121011/drivers/staging/ramster/Kconfig
> @@ -18,6 +
A release candidate Git v1.8.0-rc2 is now available for testing
at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
6c8076b3bcf08ffc53a64bbfb0fa69f82096f711 git-1.8.0.rc2.tar.gz
On Thu, Oct 11, 2012 at 07:15:20PM +0200, Andrea Arcangeli wrote:
> On Thu, Oct 11, 2012 at 01:28:27PM +0100, Mel Gorman wrote:
> > s/togehter/together/
>
> Fixed.
>
> >
> > > + * knumad_scan structure.
> > > + */
> > > +struct mm_autonuma {
> >
> > Nit but this is very similar in principle to
On Thu, Oct 11, 2012 at 3:07 PM, wrote:
> From: Jerome Glisse
>
> If do_coredump fails for any reason make sure that the task
> is actualy wakeup and properly kill otherwise we endup with
> zombies task.
>
> Signed-off-by: Jerome Glisse
> ---
> fs/coredump.c | 2 +-
> 1 file changed, 1
On Thu, Oct 11, 2012 at 07:05:33PM +0200, Andrea Arcangeli wrote:
> On Thu, Oct 11, 2012 at 01:22:55PM +0100, Mel Gorman wrote:
> > On Thu, Oct 04, 2012 at 01:50:48AM +0200, Andrea Arcangeli wrote:
> > > In the special "pmd" mode of knuma_scand
> > > (/sys/kernel/mm/autonuma/knuma_scand/pmd == 1),
I noticed that the iPhone ethernet driver did not support
iPhone 5. I quickly added support to it in my kernel, here's
a patch.
--- linux-3.6.1/drivers/net/usb/ipheth.c2012-10-07 10:41:28.0
-0500
+++ new/linux-3.6.1/drivers/net/usb/ipheth.c2012-10-11 11:38:17.242000596
-0500
On 10/11/2012 11:52 AM, Prarit Bhargava wrote:
I've been tracking an odd bug that may involve the RCU NOHZ code and
just want to know if you have any ideas on debugging and/or what might be
wrong. Note the bug happens on *BOTH* upstream and the current RHEL6 tree.
The data in this email is from
On Thu, Oct 11, 2012 at 06:58:47PM +0200, Andrea Arcangeli wrote:
> On Thu, Oct 11, 2012 at 12:15:45PM +0100, Mel Gorman wrote:
> > huh?
> >
> > #define _PAGE_NUMA _PAGE_PROTNONE
> >
> > so this is effective _PAGE_PRESENT | _PAGE_PROTNONE | _PAGE_PROTNONE
> >
> > I suspect you are doing
On Thu, Oct 11, 2012 at 06:43:00PM +0200, Andrea Arcangeli wrote:
> On Thu, Oct 11, 2012 at 12:01:37PM +0100, Mel Gorman wrote:
> > On Thu, Oct 04, 2012 at 01:50:46AM +0200, Andrea Arcangeli wrote:
> > > The objective of _PAGE_NUMA is to be able to trigger NUMA hinting page
> > > faults to
On Thu, Oct 11, 2012 at 06:07:02PM +0200, Andrea Arcangeli wrote:
> Hi,
>
> On Thu, Oct 11, 2012 at 11:50:36AM +0100, Mel Gorman wrote:
> > On Thu, Oct 04, 2012 at 01:50:43AM +0200, Andrea Arcangeli wrote:
> > > +The AutoNUMA logic is a chain reaction resulting from the actions of
> > > +the
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
v4l_for_linus
For the second part of media patches for v3.7-rc1.
Despite its size, most of the stuff here is trivial. This series contain:
- s5p-mfc: additions at the driver and at the core
From: Joe Perches
Date: Wed, 10 Oct 2012 12:23:25 -0700
> Reduces object size and should be slightly faster.
>
> allyesconfig:
> $ size net/core/pktgen.o*
>text data bss dec hex filename
> 52284 4321 11840 68445 10b5d net/core/pktgen.o.new
> 52310
From: Ondrej Zary
Date: Thu, 11 Oct 2012 12:33:28 +0200
> The device had an undocumented "feature": it can provide a sequence of
> spurious link-down status data even if the link is up all the time.
> A sequence of 10 was seen so update the link state only after the device
> reports the same
From: David Howells
Date: Thu, 11 Oct 2012 09:07:52 +0100
> Can you pull wimax as well?
>
> Sorry about this, but it seems like the majority of the non-arch trees need to
> go through the networking tree.
Done.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
From: Catalin Marinas
Date: Thu, 11 Oct 2012 17:18:05 +0100
> This patch removes several trivial UAPI headers that were simply including
> the asm-generic files as they can be automatically generated.
>
> Signed-off-by: Catalin Marinas
Acked-by: David S. Miller
--
To unsubscribe from this
On machines serving mainly http traffic we are seeing the following
panic, which is not yet reproducible.
[180926.566743] [ cut here ]
[180926.572034] kernel BUG at net/netfilter/nf_conntrack_core.c:220!
[180926.578873] invalid opcode: [#1] SMP
[180926.583594]
Move mach-davinci/dma.c to common/edma.c so it can be used
by OMAP (specifically AM33xx) as well. This just moves the
private EDMA API but does not support OMAP.
Signed-off-by: Matt Porter
---
arch/arm/Kconfig |1 +
arch/arm/common/Kconfig
The binding definition is based on the generic DMA controller
binding.
Signed-off-by: Matt Porter
---
Documentation/devicetree/bindings/dma/ti-edma.txt | 49 +
1 file changed, 49 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma/ti-edma.txt
diff
From: Jerome Glisse
If do_coredump fails for any reason make sure that the task
is actualy wakeup and properly kill otherwise we endup with
zombies task.
Signed-off-by: Jerome Glisse
---
fs/coredump.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/coredump.c
Adds AM33XX EDMA support to the am33xx.dtsi as documented in
Documentation/devicetree/bindings/dma/ti-edma.txt
Signed-off-by: Matt Porter
---
arch/arm/boot/dts/am33xx.dtsi | 30 ++
1 file changed, 30 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi
Adds a dma_request_slave_channel_compat() wrapper which accepts
both the arguments from dma_request_channel() and
dma_request_slave_channel(). Based on whether the driver is
instantiated via DT, the appropriate channel request call will be
made.
This allows for a much cleaner migration of drivers
Fix build on OMAP, the irqs are undefined on AM33xx.
These error interrupt handlers were hardcoded as disabled
so since they are unused code, simply remove them.
Signed-off-by: Matt Porter
---
arch/arm/common/edma.c | 37 -
1 file changed, 37 deletions(-)
Convert dmaengine channel requests to use
dma_request_slave_channel_compat(). This supports the DT case of
platforms requiring channel selection from either the OMAP DMA or
the EDMA engine. AM33xx only boots from DT and is the only user
implementing EDMA so in the !DT case we can default to the
Adds support for parsing the TI EDMA DT data into the required
EDMA private API platform data.
Calls runtime PM API only in the DT case in order to unidle the
associated hwmods on AM335x.
TODO: add AM33XX crossbar support and DT binding
Signed-off-by: Matt Porter
---
arch/arm/common/edma.c
The EDMA DMAC has a hardware limitation that prevents supporting
scatter gather lists with any number of segments. Since the EDMA
DMA Engine driver sets the maximum segments to 16, we do the
same.
TODO: this will be replaced once the DMA Engine API supports an
API to query the DMAC's segment size
101 - 200 of 1022 matches
Mail list logo
