On Wed, Nov 21, 2012 at 7:33 AM, Axel Lin wrote:
> This is introduced by commit 9ab6e988
> "gpiolib: return any error code from range creation".
>
> Signed-off-by: Axel Lin
> ---
> This patch is against LinusW's linux-pinctrl tree, for-next branch.
> Axel
Oops thanks a lot for catching this Axe
On 21 November 2012 13:20, Linus Walleij wrote:
> From: Linus Walleij
>
> To be crystal clear on what the arguments mean in this
> funtion dealing with both GPIO and PIN ranges with confusing
> naming, we now have gpio_offset and pin_offset and we are
> on the clear that these are offsets into th
On Wed, 21 Nov 2012 02:48:51 +0100 Jan Kara wrote:
> +/*
> + * Add inode to LRU if needed (inode is unused and clean).
> + *
> + * Needs inode->i_lock held.
> + */
> +void inode_add_lru(struct inode *inode)
> +{
> + if (!(inode->i_state & (I_DIRTY | I_FREEING | I_SYNC)) &&
> + !atomic
Hello,
On 11/20/2012 8:33 PM, Andrew Morton wrote:
On Tue, 20 Nov 2012 15:31:45 +0100
Marek Szyprowski wrote:
> dmapool always calls dma_alloc_coherent() with GFP_ATOMIC flag,
> regardless the flags provided by the caller. This causes excessive
> pruning of emergency memory pools without any g
> Curious. Added linux-mm list to CC to catch more attention. If you run
> echo 1 >/proc/sys/vm/drop_caches does it evict data-1 pages from memory?
I'm guessing it'd evict the entries, but am wondering if we could run any more
diagnostics before trying this.
We regularly use a setup where we
* Rik van Riel wrote:
> >+}
> >+
> >+/*
> >+ * Add a simple loop to also fetch ptes within the same pmd:
> >+ */
>
> That's not a very useful comment. How about something like:
>
> /*
>* Also fault over nearby ptes from within the same pmd and vma,
>* in order to minimize the overhea
> Curious. Added linux-mm list to CC to catch more attention. If you run
> echo 1 >/proc/sys/vm/drop_caches does it evict data-1 pages from memory?
I'm guessing it'd evict the entries, but am wondering if we could run any more
diagnostics before trying this.
We regularly use a setup where we ha
On Mon, Nov 19, 2012 at 7:31 PM, Stephen Warren wrote:
> From: Stephen Warren
>
> Move ux500's timer suspend/resume functions from struct sys_timer
> ux500_timer into struct clock_event_device nmdk_clkevt. This
> will allow the sys_timer suspend/resume fields to be removed, and
> eventually lead
On 2012-11-21 03:56, Alex Courbot wrote:
> Hi Tomi,
>
> On Tuesday 20 November 2012 22:48:18 Tomi Valkeinen wrote:
>> I guess there's a reason, but the above looks a bit inconsistent. For
>> gpio you define the gpio resource inside the step. For power and pwm the
>> resource is defined before the
This patch adds the values related to buddy system to vmcoreinfo data
so that makedumpfile (dump filtering command) can filter out all free
pages with the new logic.
It's faster than the current logic because it can distinguish free page
by analyzing page structure at the same time as filtering for
>>> On 20.11.12 at 23:42, Dan Magenheimer wrote:
> Konrad: Any chance this can get in for the upcoming window?
> (Or is it enough of a bug fix that it can go in at an -rcN?)
>
> It was just pointed out to me that some kernels have
> cleancache and frontswap and xen_tmem enabled but NOT
> xen_self
On Mon, Nov 19, 2012 at 7:31 PM, Stephen Warren wrote:
> From: Stephen Warren
>
> These fields duplicate e.g. struct clock_event_device's suspend and
> resume fields, so remove them now that nothing is using them. The aim
> is to remove all fields from struct sys_timer except .init, then replace
On Wed, Nov 21, 2012 at 12:05:33AM -0800, Andrew Morton wrote:
> On Wed, 21 Nov 2012 02:48:51 +0100 Jan Kara wrote:
>
> > +/*
> > + * Add inode to LRU if needed (inode is unused and clean).
> > + *
> > + * Needs inode->i_lock held.
> > + */
> > +void inode_add_lru(struct inode *inode)
> > +{
> >
On 11/20/2012 10:23 PM, David Rientjes wrote:
> Anton can correct me if I'm wrong, but I certainly don't think this is
> where mempressure is headed: I don't think any accounting needs to be done
> and, if it is, it's a design issue that should be addressed now rather
> than later. I believe no
Oh and there was this comment/TODO:
On Mon, Nov 19, 2012 at 7:31 PM, Stephen Warren wrote:
> @@ -17,15 +17,6 @@
> * Initialise the kernels jiffy timer source, claim interrupt
> * using setup_irq. This is called early on during initialisation
> * while interrupts are still disabled o
On 11/21/2012 12:18 AM, Andrew Morton wrote:
> On Tue, 20 Nov 2012 13:18:19 +0400
> Glauber Costa wrote:
>
>> On 11/12/2012 03:37 PM, Mel Gorman wrote:
>>> diff --git a/include/linux/gfp.h b/include/linux/gfp.h
>>> index 02c1c971..d0a7967 100644
>>> --- a/include/linux/gfp.h
>>> +++ b/include/lin
On Mon, 19 Nov 2012 18:07:01 -0800 Derek Basehore
wrote:
> 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 Wednesday 21 November 2012 16:13:47 Tomi Valkeinen wrote:
> * PGP Signed by an unknown key
>
> On 2012-11-21 03:56, Alex Courbot wrote:
> > Hi Tomi,
> >
> > On Tuesday 20 November 2012 22:48:18 Tomi Valkeinen wrote:
> >> I guess there's a reason, but the above looks a bit inconsistent. For
> >
> This patch implements map_voltage and list_voltage callbacks to properly
> handle
> the case voltage range that doesn't start with 0 offset.
>
> Now we adjust the selector in map_voltage() before calling set_voltage_sel().
> And return 0 in list_voltage() for invalid selectors.
>
> With above
On Tue, Nov 20, 2012 at 04:45:00PM +0200, Johan Meiring wrote:
> This commit fixes an inconsistent spacing issue around *
>
The others are good, but this one is not right.
> Signed-off-by: Johan Meiring
> ---
> drivers/staging/wlags49_h2/ap_h2.c |8
> 1 file changed, 4 insertions(
Cc Fengguang Wu.
On 11/21/2012 04:13 PM, metin d wrote:
Curious. Added linux-mm list to CC to catch more attention. If you run
echo 1 >/proc/sys/vm/drop_caches does it evict data-1 pages from memory?
I'm guessing it'd evict the entries, but am wondering if we could run any more
diagnostics
On Tue 20-11-12 13:49:32, Andrew Morton wrote:
> On Mon, 19 Nov 2012 17:44:34 -0800 (PST)
> David Rientjes wrote:
>
> > While profiling numa/core v16 with cgroup_disable=memory on the command
> > line, I noticed mem_cgroup_count_vm_event() still showed up as high as
> > 0.60% in perftop.
> >
>
On Wed, 21 Nov 2012 09:08:52 +0100 Marek Szyprowski
wrote:
> Hello,
>
> On 11/20/2012 8:33 PM, Andrew Morton wrote:
> > On Tue, 20 Nov 2012 15:31:45 +0100
> > Marek Szyprowski wrote:
> >
> > > dmapool always calls dma_alloc_coherent() with GFP_ATOMIC flag,
> > > regardless the flags provided b
Hi alls,
Today, I saw below complain of lockdep.
As a matter of fact, I knew it long time ago but forgot that.
The reason lockdep complains is that now zram uses GFP_KERNEL
in reclaim path(ex, __zram_make_request) :(
I can fix it via replacing GFP_KERNEL with GFP_NOIO.
But more big problem is vzal
>
> Those of you who would like to test all the latest patches are
> welcome to pick up latest bits at tip:master:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
>
I am wondering if it is a problem, but it still exists on HEAD: c418de93e39891
http://article.gmane.org/gmane
Add NumaChip-specific PCI access mechanism via MMCONFIG cycles, but
preventing access to AMD Northbridges which shouldn't respond.
v2: Use PCI_DEVFN in precomputed constant limit; drop unneeded includes
Signed-off-by: Daniel J Blueman
---
arch/x86/include/asm/numachip/numachip.h | 20 +
a
The driver requires a custom slave configuration to be present to be able to
make the slave transfers. Nevertheless, in some cases we need only the request
line as an additional information to the generic slave configuration. The
request line is provided by slave_id parameter of the dma_slave_conf
Currently the direction value comes from the generic slave configuration
structure and explicitly as a preparation function parameter. The first one is
kinda obsoleted. Thus, we have to store the value passed to the preparation
function somewhere in our structures to be able to use it later. The be
Previously a new line is implicitly added in the no GSI case:
[7.185182] pci 0001:00:12.0: can't derive routing for PCI INT A
[7.191352] pci 0001:00:12.0: PCI INT A: no GSI
[7.195956] - using ISA IRQ 10
The code thus prints a blank line where no legacy IRQ is available:
[1.65012
On 2012-11-21 10:32, Alex Courbot wrote:
>> Ok. I'll need to dig up the conversation
>
> IIRC it was somewhere around here:
>
> https://lkml.org/lkml/2012/9/7/662
>
> See the parent messages too.
Thanks.
>> Did you consider any examples
>> of how some driver could handle the error cases?
>
>
On Wed, Nov 21, 2012 at 12:27:28PM +0400, Glauber Costa wrote:
> On 11/20/2012 10:23 PM, David Rientjes wrote:
> > Anton can correct me if I'm wrong, but I certainly don't think this is
> > where mempressure is headed: I don't think any accounting needs to be done
Yup, I'd rather not do any accou
Hi Jason, Hi Kent,
>
>Discussion on this got a bit sidetracked talking about
>suspend/resume.. To be clear, this fixes a real, serious, problem on
>normal embedded cases where the kernel refuses to attach the TPM driver
>at all.
>
>Key, are you happy with this as-is for the next merge window?
>
>Th
On Wed, Nov 21, 2012 at 04:34:40PM +0800, Jaegeuk Hanse wrote:
> Cc Fengguang Wu.
>
> On 11/21/2012 04:13 PM, metin d wrote:
> >> Curious. Added linux-mm list to CC to catch more attention. If you run
> >>echo 1 >/proc/sys/vm/drop_caches does it evict data-1 pages from memory?
> >I'm guessing it
Hi, Amit,
As THERMAL_TREND_RAISE_FULL/THERMAL_TREND_DROP_FULL
has been introduced to thermal next tree,
I'd like to get your plan about this patch set?
Thanks,
Rui
> -Original Message-
> From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi-
> ow...@vger.kernel.org] On Behalf Of Amit
Instead of devfreq device driver explicitly calling devfreq suspend
and resume apis perhaps from runtime-pm suspend and resume callbacks,
let devfreq core handle it automatically.
Attach devfreq core to runtime-pm framework so that, devfreq device
driver pm_runtime_suspend() will automatically sus
On Tue, Nov 20, 2012 at 07:28:52PM +0200, Johan Meiring wrote:
> This commit sorts out a single case where a line was longer than
> 80 characters.
>
> Signed-off-by: Johan Meiring
> ---
> drivers/staging/cxt1e1/sbecrc.c |3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git
3.7-rc6 booted with nmi_watchdog=0 fails to suspend to RAM or
offline CPUs. It's reproducable with a KVM guest and physical
system.
git bisect identified (config used for bisecting attached):
commit bcd951cf10f24e341defcd002c15a1f4eea13ddb
Author: Thomas Gleixner
Date: Mon Jul 16 10:42:3
On Tue, Nov 20, 2012 at 07:28:48PM +0200, Johan Meiring wrote:
> This commit fixes several incorrect placements of parantheses, as
> identified by the checkpatch.pl tool.
>
This patch is fine, and all.
Acked-by: Dan Carpenter
But you could go beyond fixing just checkpatch.pl warnings.
> Signed
On Wed, Nov 21, 2012 at 05:02:04PM +0800, Fengguang Wu wrote:
> On Wed, Nov 21, 2012 at 04:34:40PM +0800, Jaegeuk Hanse wrote:
> > Cc Fengguang Wu.
> >
> > On 11/21/2012 04:13 PM, metin d wrote:
> > >> Curious. Added linux-mm list to CC to catch more attention. If you run
> > >>echo 1 >/proc/sys
On Mon, Nov 19, 2012 at 08:45:53AM -0600, Rob Herring wrote:
> Arnd, Olof,
>
> Please pull cpuidle support for highbank. This is the first driver in
> drivers/cpuidle. All the existing drivers for ARM are in arch/arm. I'm
> asking for you to pull since there seems to be a lack of maintainer for
>
Hello,
On 11/21/2012 9:36 AM, Andrew Morton wrote:
On Wed, 21 Nov 2012 09:08:52 +0100 Marek Szyprowski
wrote:
> Hello,
>
> On 11/20/2012 8:33 PM, Andrew Morton wrote:
> > On Tue, 20 Nov 2012 15:31:45 +0100
> > Marek Szyprowski wrote:
> >
> > > dmapool always calls dma_alloc_coherent() with G
On 11/21/2012 12:46 PM, Anton Vorontsov wrote:
> On Wed, Nov 21, 2012 at 12:27:28PM +0400, Glauber Costa wrote:
>> On 11/20/2012 10:23 PM, David Rientjes wrote:
>>> Anton can correct me if I'm wrong, but I certainly don't think this is
>>> where mempressure is headed: I don't think any accounting
Because of_i2c_register_devices() do not check status property,
all i2c clients are registered.
This patch add checking status property for i2c client.
After this patch, if status property is absent or "okay" or "ok",
i2c client will be registered.
Signed-off-by: Bongkyu Kim
---
drivers/of/of_i
This patch supports more interrupt specifiers for i2c client.
Signed-off-by: Bongkyu Kim
---
drivers/of/of_i2c.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/of/of_i2c.c b/drivers/of/of_i2c.c
index 3550f3b..c6d9b7e 100644
--- a/drivers/of/of_i2c.c
+++ b/drivers
On Tue, Nov 20, 2012 at 10:02:45AM -0800, David Rientjes wrote:
> On Mon, 19 Nov 2012, Glauber Costa wrote:
>
> > >> In the case I outlined below, for backwards compatibility. What I
> > >> actually mean is that memcg *currently* allows arbitrary notifications.
> > >> One way to merge those, while
* David Rientjes wrote:
> Ok, this is significantly better, it almost cut the regression
> in half on my system. [...]
The other half still seems to be related to the emulation faults
that I fixed in the other patch:
> 0.49% [kernel] [k] page_fault
* David Rientjes wrote:
> I started profiling on a new machine that is an exact
> duplicate of the 16-way, 4 node, 32GB machine I was profiling
> with earlier to rule out any machine-specific problems. I
> pulled master and ran new comparisons with THP enabled at
> c418de93e398 ("Merge bran
On Tue, Nov 20, 2012 at 07:33:49PM -0200, Marcelo Tosatti wrote:
> On Tue, Nov 20, 2012 at 06:09:48PM +0800, Hu Tao wrote:
> > Hi Marcelo,
> >
> > On Tue, Nov 13, 2012 at 12:19:08AM -0200, Marcelo Tosatti wrote:
> > > On Fri, Nov 09, 2012 at 03:17:39PM -0500, Sasha Levin wrote:
> > > > On Mon, Nov
Expose another DMA operations function: arm_dma_set_mask. This
function will be added to a custom DMA ops for Armada 370/XP.
Depending of its configuration Armada 370/XP can be set as a "nearly"
coherent architecture. In this case the DMA ops is made of:
- specific functions for this architecture
-
Armada 370 and XP come with an unit called coherency fabric. This unit
allows to use the Armada 370/XP as a nearly coherent architecture. The
coherency mechanism uses snoop filters to ensure the coherency between
caches, DRAM and devices. This mechanism needs a synchronization
barrier which guarant
Recent SoC such as Armada 370/XP came with the possibility to deal
with the I/O coherency by hardware. In this case the transaction
attribute of the window must be flagged as "Shared transaction". Once
this flag is set, then the transactions will be forced to be sent
through the coherency block, in
On 11/21/2012 02:13 AM, Luis R. Rodriguez wrote:
> Ah so keep the original in place to let references to the original in
> whatever way those may exist to keep pointing but promote new usage to
> a copy and.. perhaps refer to the new copy in master, or just leave
> that in place as is?
It depends
The purpose of this patch set is to add hardware I/O Coherency support
for Armada 370 and Armada XP. Theses SoCs come with an unit called
coherency fabric. A beginning of the support for this unit have been
introduced with the SMP patch set. This series extend this support:
the coherency fabric uni
On 11/21/2012 05:02 PM, Fengguang Wu wrote:
On Wed, Nov 21, 2012 at 04:34:40PM +0800, Jaegeuk Hanse wrote:
Cc Fengguang Wu.
On 11/21/2012 04:13 PM, metin d wrote:
Curious. Added linux-mm list to CC to catch more attention. If you run
echo 1 >/proc/sys/vm/drop_caches does it evict data-1 pag
On Tue, 2012-11-20 at 15:41 -0800, Joe Perches wrote:
> On Tue, 2012-11-20 at 23:19 +, Andy Whitcroft wrote:
> > On Tue, Nov 20, 2012 at 01:58:48PM -0800, Joe Perches wrote:
> >
> > > +# check for multiple blank lines, warn only on the second one in a block
> > > + if ($rawline =~ /^.\
Doug Anderson wrote:
>
> This is similar to a recent commit for exynos5250 titled:
> ARM: EXYNOS: Add aliases for i2c controller
>
> Adding aliases will be useful to prevent warnings in a future
> change. See:
> i2c: s3c2410: Get the i2c bus number from alias id
>
> Signed-off-by: Doug Ande
Doug Anderson wrote:
>
> From: Padmavathi Venna
>
> Get the i2c bus number that the device is connected to using the alias
> id. This makes debugging / grokking of kernel messages much easier.
>
> [dianders: slight patch cleanup from Padmavathi's original.]
>
> Signed-off-by: Padmavathi Venna
Doug Anderson wrote:
>
> From: Olof Johansson
>
> Needed to match device ids for clocks, etc.
>
> Signed-off-by: Olof Johansson
> Signed-off-by: Doug Anderson
>
> ---
> arch/arm/mach-exynos/mach-exynos5-dt.c | 10 ++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --
Kukjin Kim wrote:
>
> Olof Johansson wrote:
> >
[...]
> >
> > Acked-by: Olof Johansson
> >
> > Kukjin, since your pull requests came in today, can you ack this and
> > I'll just apply it on top of your branches?
> >
> Hi Olof, yeah, I sent pull-request but there are some patches for dt and
> ex
Il 20/11/2012 19:54, David Miller ha scritto:
From: Paolo Valente
Date: Tue, 20 Nov 2012 18:45:13 +0100
- struct sk_buff *skb;
+ struct sk_buff *skb = NULL;
This is not really an improvement,
Sorry for trying this silly short cut
now the compiler can think
that NULL is passed
On 20 November 2012 11:23, Zhang Rui wrote:
> On Tue, 2012-11-20 at 10:39 +0900, Kyungmin Park wrote:
>> On 11/20/12, Jonghwan Choi wrote:
>> > [0]bit is used to enable/disable tmu core. [1] bit is a reserved bit.
>> >
>> > Signed-off-by: Jonghwan Choi
>> Acked-by: Kyungmin Park
>
> Amit and Do
From: Xuelin Shi
The RaidEngine is a new Freescale hardware that used for parity
computation offloading in RAID5/6.
This patch adds the device node in device tree and related binding
documentation.
Signed-off-by: Harninder Rai
Signed-off-by: Naveen Burmi
Signed-off-by: Xuelin Shi
---
.../de
From: Xuelin Shi
The RaidEngine is a new FSL hardware that used as hardware acceration
for RAID5/6.
This patch enables the RaidEngine functionality and provides hardware
offloading capability for memcpy, xor and raid6 pq computation. It works
under dmaengine control with async_layer interface.
Olof Johansson wrote:
>
> On Tue, Nov 20, 2012 at 02:48:58PM -0800, Doug Anderson wrote:
> > From: Olof Johansson
> >
> > UART3 is used for debugging on exynos5250-snow.
> >
> > [dianders: cleaned commit message.]
> >
> > Signed-off-by: Olof Johansson
> > Signed-off-by: Doug Anderson
>
> >
> >
On Tuesday 20 November 2012, Stephen Warren wrote:
> However, this results in iterating over table twice; the second time
> inside of_match_node(). The implementation of for_each_matching_node()
> already found the match, so this is redundant. Invent new function
> of_find_matching_node_and_match()
> Hi,
>
> It looks like find_device_opp() (called from opp_get_notifier()) needs
> to be under RCU read lock, but this doesn't seem to be happening in
> drivers/devfreq/devfreq.c. Doesn't this run the risk of referencing a
> freed variable?
>
> Thanks,
>
> -Kees
Yes, that's an issue requiring u
On Mon, Nov 19, 2012 at 10:39 AM, Sebastian Hesselbarth
wrote:
> This patch relies on a patch set for mvebu pinctrl taken through
> Linus' pinctrl branch. As there is no other platform than Dove
> involved, I suggest to take it though Jason's tree to avoid any
> further conflicts.
Sounds like a
Hi Fengguang,
I run tests and attached the results. The line below I guess shows the data-1
page caches.
0x0008006c 6584051 25718
__RU_lA___P referenced,uptodate,lru,active,private
Metin
From: Jaegeuk Hanse
To: F
On Wednesday 21 November 2012 16:48:45 Tomi Valkeinen wrote:
> If the power-off sequence disables a regulator that was supposed to be
> enabled by the power-on sequence (but wasn't enabled because of an
> error), the regulator_disable is still called when the driver runs the
> power-off sequence, i
Dear Ezequiel Garcia,
On Tue, 20 Nov 2012 19:39:38 -0300, Ezequiel Garcia wrote:
> * Read/write support
>
> Yes, this implementation supports read/write access.
While I think the original ubiblk that was read-only made sense to
allow the usage of read-only filesystems like squashfs, I am not su
On Mon, Nov 19, 2012 at 10:39 AM, Sebastian Hesselbarth
wrote:
> From: Axel Lin
>
> When setting audio1 pinmux the bits in the corresponding registers
> are not cleared. This fix first clears all bits and then sets the
> required bits according to the selected function.
>
> Signed-off-by: Axel L
On Mon, Nov 19, 2012 at 10:39 AM, Sebastian Hesselbarth
wrote:
> There has been a change in readl/writel to require registers
> addresses marked as IOMEM(). This patch takes care of this and
> also replaces ORing address offsets with adding them.
>
> Signed-off-by: Sebastian Hesselbarth
Acked-b
Fixed coding style on numerious lines.
Signed-off-by: Michael L. Hobbs
---
drivers/pnp/card.c | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/drivers/pnp/card.c b/drivers/pnp/card.c
index bc00693..400568a 100644
--- a/drivers/pnp/card.c
+++ b/drivers/pnp
On 21 November 2012 14:12, Andy Shevchenko
wrote:
> Currently the direction value comes from the generic slave configuration
> structure and explicitly as a preparation function parameter. The first one is
> kinda obsoleted. Thus, we have to store the value passed to the preparation
> function som
On Wed, Nov 21, 2012 at 9:53 AM, Arnd Bergmann wrote:
> On Tuesday 20 November 2012, Stephen Warren wrote:
>> However, this results in iterating over table twice; the second time
>> inside of_match_node(). The implementation of for_each_matching_node()
>> already found the match, so this is redund
On Wed, Nov 21, 2012 at 12:00 PM, Jaegeuk Hanse wrote:
>
> On 11/21/2012 05:58 PM, metin d wrote:
>
> Hi Fengguang,
>
> I run tests and attached the results. The line below I guess shows the data-1
> page caches.
>
> 0x0008006c 658405125718
> __RU_lA___P___
On Mon, Nov 19, 2012 at 11:41:23PM -0800, Darrick J. Wong wrote:
> Provide VFS helpers for handling O_SYNC AIO DIO writes. Filesystems wanting
> to
> use the helpers have to pass DIO_SYNC_WRITES to __blockdev_direct_IO. If the
> filesystem doesn't provide its own direct IO end_io handler, the ge
On Mon, Nov 19, 2012 at 11:41:38PM -0800, Darrick J. Wong wrote:
> Hi,
>
> Fsyncing is tricky business, so factor out the bits of the xfs_file_fsync
> function that can be used from the I/O post-processing path.
Why would we need to skip the filemap_write_and_wait_range call here?
If we're doing
On Wed, 21 Nov 2012 10:06:16 +, Grant Likely wrote:
> On Wed, Nov 21, 2012 at 9:53 AM, Arnd Bergmann wrote:
> > On Tuesday 20 November 2012, Stephen Warren wrote:
> >> However, this results in iterating over table twice; the second time
> >> inside of_match_node(). The implementation of for_e
opp_get_notifier() uses find_device_opp(), which requires to
held rcu_read_lock. In order to keep the notifier-header
valid, we have added rcu_read_lock().
Reported-by: Kees Cook
Signed-off-by: MyungJoo Ham
---
drivers/devfreq/devfreq.c | 26 --
1 files changed, 20 ins
Le 20/11/2012 15:25, Dan Carpenter a écrit :
> On Tue, Nov 20, 2012 at 02:26:42PM +0100, MAACHE Mehdi wrote:
>> This is a patch to the r8180_wx.c file that fixes up some warnings and
>> errors found by the checkpatch.pl tool
>> - WARNING: line over 80 characters
>> - ERROR: "(foo*)" should be "(f
> Use the value obtained from the function instead of -EINVAL.
>
> Signed-off-by: Sachin Kamat
Acked-by: MyungJoo Ham
Both patches applied as they are obvious bugfixes.
I'll send pull request with other bugfixes within days.
> ---
> drivers/devfreq/devfreq.c |2 +-
> 1 files changed, 1 i
On Tue, Nov 20, 2012 at 8:59 PM, richard -rw- weinberger
wrote:
> On Tue, Nov 20, 2012 at 11:39 PM, Ezequiel Garcia
> wrote:
>> Block device emulation on top of ubi volumes with read/write support.
>> Block devices get automatically created for each ubi volume present.
>>
>> Each ubiblock is fai
On 11/21/2012 10:59 AM, Linus Walleij wrote:
On Mon, Nov 19, 2012 at 10:39 AM, Sebastian Hesselbarth
wrote:
This patch relies on a patch set for mvebu pinctrl taken through
Linus' pinctrl branch. As there is no other platform than Dove
involved, I suggest to take it though Jason's tree to avoi
From: Rik van Riel
The function ptep_set_access_flags() is only ever invoked to set access
flags or add write permission on a PTE. The write bit is only ever set
together with the dirty bit.
Because we only ever upgrade a PTE, it is safe to skip flushing entries on
remote TLBs. The worst that c
Compaction already has tracepoints to count scanned and isolated pages
but it requires that ftrace be enabled and if that information has to be
written to disk then it can be disruptive. This patch adds vmstat counters
for compaction called compact_migrate_scanned, compact_free_scanned and
compact_
From: Andrea Arcangeli
Implement pte_numa and pmd_numa.
We must atomically set the numa bit and clear the present bit to
define a pte_numa or pmd_numa.
Once a pte or pmd has been set as pte_numa or pmd_numa, the next time
a thread touches a virtual address in the corresponding virtual range,
a
From: Lee Schermerhorn
NOTE: Once again there is a lot of patch stealing and the end result
is sufficiently different that I had to drop the signed-offs.
Will re-add if the original authors are ok with that.
This patch adds another mbind() flag to request "lazy migration". The
f
The use of MPOL_NOOP and MPOL_MF_LAZY to allow an application to
explicitly request lazy migration is a good idea but the actual
API has not been well reviewed and once released we have to support it.
For now this patch prevents an application using the services. This
will need to be revisited.
Si
From: Andrea Arcangeli
This defines the per-node data used by Migrate On Fault in order to
rate limit the migration. The rate limiting is applied independently
to each destination node.
Signed-off-by: Andrea Arcangeli
Signed-off-by: Mel Gorman
---
include/linux/mmzone.h | 13 +
This patch introduces a last_nid field to the page struct. This is used
to build a two-stage filter in the next patch that is aimed at
mitigating a problem whereby pages migrate to the wrong node when
referenced by a process that was running off its home node.
Signed-off-by: Mel Gorman
---
inclu
NOTE: This is heavily based on "autonuma: CPU follows memory algorithm"
and "autonuma: mm_autonuma and task_autonuma data structures"
with bits taken but worked within the scheduler hooks and home
node mechanism as defined by schednuma.
This patch adds per-mm and per-task d
The implementation of CPU follows memory was intended to reflect
the considerations made by autonuma on the basis that it had the
best performance figures at the time of writing. However, a major
criticism was the use of kernel threads and the impact of the
cost of the load balancer paths. As a con
---
kernel/sched/fair.c | 112 +++
1 file changed, 15 insertions(+), 97 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 5cc5b60..fd53f17 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -877,118 +877,36 @@ sta
From: Hillf Danton
Node is selected on behalf of given task, but no reason to punish
the currently running tasks on other nodes. That punishment maybe benifit,
who knows. Better if they are treated not in random way.
Signed-off-by: Hillf Danton
---
kernel/sched/fair.c | 15 ++-
1
From: Peter Zijlstra
Introduce the home-node concept for tasks. In order to keep memory
locality we need to have a something to stay local to, we define the
home-node of a task as the node we prefer to allocate memory from and
prefer to execute on.
These are no hard guarantees, merely soft prefe
Note: This is very heavily based on a patch from Peter Zijlstra with
fixes from Ingo Molnar, Hugh Dickins and Johannes Weiner. That patch
put a lot of migration logic into mm/huge_memory.c where it does
not belong. This version puts tries to share some of the migration
Rename the policy to reflect that while allocations and migrations are
based on reference that the home node is taken into account for
migration decisions.
Signed-off-by: Mel Gorman
---
include/uapi/linux/mempolicy.h |9 -
mm/mempolicy.c |9 ++---
2 files chan
NOTE: This is heavily based on "autonuma: CPU follows memory algorithm"
and "autonuma: mm_autonuma and task_autonuma data structures"
At the most basic level, any placement policy is going to make some
sort of smart decision based on per-mm and per-task statistics. This
patch simply introd
NOTE: Entirely on "sched, numa, mm: Implement home-node awareness" but
only a subset of it. There was stuff in there that was disabled
by default and generally did slightly more than what I felt was
necessary at this stage. In particular the random queue selection
lo
1 - 100 of 473 matches
Mail list logo
