On Tue, Apr 29, 2014 at 02:21:19PM -0700, John Stultz wrote:
> Another few weeks and another volatile ranges patchset...
>
> After getting the sense that the a major objection to the earlier
> patches was the introduction of a new syscall (and its somewhat
> strange dual length/purged-bit return
On 8 May 2014 07:37, Jonghwan Choi wrote:
As asked earlier by Nishanth:
- Avoid top-posting (the practice of putting your answer above the quoted
text you are responding to). It makes your response harder to read and
makes a poor impression.
Reference:
On Wed, May 07, 2014 at 04:59:07PM +0200, Vlastimil Babka wrote:
> On 05/07/2014 03:33 AM, Minchan Kim wrote:
> > On Mon, May 05, 2014 at 05:50:46PM +0200, Vlastimil Babka wrote:
> >> On 05/05/2014 04:36 PM, Sasha Levin wrote:
> >>> On 05/02/2014 08:08 AM, Vlastimil Babka wrote:
> On
Hi Lee
Sorry for previous email, only [PATCH 2/2] mmc: rtsx: Revert "mmc: rtsx:
add support for pre_reqand post_req"
if need for 3.15 fix.
Best Regards.
micky.
On 04/29/2014 03:36 PM, Ulf Hansson wrote:
On 29 April 2014 03:54, wrote:
>From: Micky Ching
>
>This reverts commit
On Thu, May 8, 2014 at 7:25 AM, Nishanth Menon wrote:
>> Is it acceptiable?
>
> Personally, I feel that filling up driver_data should be left to the
> driver(caller of dev_pm_opp_init_cpufreq_table).
Exactly, and I never advised Jonghwan to update the common routine
for this. I wanted him to
Hi Lee
It seems Chris is too busy to responding, so would you help to pick this
patch for 3.15 fix.
Best Regards.
micky.
On 04/29/2014 03:30 PM, Ulf Hansson wrote:
On 29 April 2014 03:54, wrote:
>From: Micky Ching
>
>This reverts commit 1f7b581b3ffcb2a8437397a02f4af89fa6934d08.
>
>The
(2014/05/08 13:47), Ananth N Mavinakayanahalli wrote:
> On Wed, May 07, 2014 at 08:55:51PM +0900, Masami Hiramatsu wrote:
>
> ...
>
>> +#if defined(CONFIG_PPC64) && (!defined(_CALL_ELF) || _CALL_ELF == 1)
>> +/*
>> + * On PPC64 ABIv1 the function pointer actually points to the
>> + * function's
On Thu, May 08, 2014 at 01:14:56AM -0400, Vince Weaver wrote:
> >
> > There were a bug in p4 pmu Don (CC'ed) fixed not that long ago but I fear
> > not all corner cases might be covered yet.
>
> I hit the NMI warnings somewhat often on Intel hardware (Haswell, Core2)
> but it usually doesn't
On 7 May 2014 22:03, Stratos Karafotis wrote:
> On platforms that use cpufreq_for_each_* macros, build fails if
> CONFIG_CPU_FREQ=n, e.g. ARM/shmobile/koelsch/non-multiplatform:
>
> drivers/built-in.o: In function `clk_round_parent':
> clkdev.c:(.text+0xcf168): undefined reference to
On Wed, May 07, 2014 at 10:00:50PM -0400, Don Zickus wrote:
> >
> > If i'm right (btw it's possible to use addr2line helper?) then hwc->config
> > is corrupted and p4_config_get_bind returned nil simply because proper event
> > was not found. And I don't understand how it could happen because
mm-thp-avoid-excessive-compaction-latency-during-fault.patch excludes sync
compaction for all high order allocations other than thp. What we really
want to do is suppress sync compaction for thp, but only during the page
fault path.
Orders greater than PAGE_ALLOC_COSTLY_ORDER aren't necessarily
On Wed, May 07, 2014 at 02:09:10PM +0200, Vlastimil Babka wrote:
> The compaction free scanner in isolate_freepages() currently remembers PFN of
> the highest pageblock where it successfully isolates, to be used as the
> starting pageblock for the next invocation. The rationale behind this is that
From: "Lad, Prabhakar"
this patch removes drops the entries form Makefile, fixing
following issues when make clean was run,
scripts/Makefile.clean:17: sound/soc/intel/board/Makefile: No such file or
directory
scripts/Makefile.clean:17: sound/soc/intel/sst/Makefile: No such file or
directory
On Tue, May 06, 2014 at 07:22:52PM -0700, David Rientjes wrote:
> Async compaction terminates prematurely when need_resched(), see
> compact_checklock_irqsave(). This can never trigger, however, if the
> cond_resched() in isolate_migratepages_range() always takes care of the
> scheduling.
>
>
Christian Engelmayer writes:
> Fix a potential leak in the error path of function update_bcn_wps_ie().
> Move the affected input verification to the beginning of the function so
> that it may return directly without leaking already allocated memory.
> Detected by Coverity - CID 1077718.
>
>
On Tue, Apr 29, 2014 at 02:21:23PM -0700, John Stultz wrote:
> This patch adds the hooks in the vmscan logic to purge volatile pages
> and mark their pte as purged. With this, volatile pages will be purged
> under pressure, and their ptes swap entry's marked. If the purged pages
> are accessed
On Thu, 8 May 2014, Cyrill Gorcunov wrote:
> > > The NMI issue is probably the only one that is p4 related, and I do get
> > > the NMI warnings on other machines too, it's just the p4 is the only one
> > > where it brings down the machine.
> >
> > Vince, could you please provde more details on
On Wed, 7 May 2014 23:04:11 +0200
Peter Zijlstra wrote:
> On Wed, May 07, 2014 at 10:46:56PM +0200, Fabian Frederick wrote:
> > This patch also fixes function prototype over 80 characters
>
> And does it wrong.. Also does it really matter to GCC that we init the
> bool? Surely it can see its 0
On Wed, May 7, 2014 at 8:25 PM, Xiubo Li wrote:
> The OOM message of individual driver is unnecessary, and this is
> duplicate the memory subsystem generic OOM message.
>
Thanks, applied.
-Bryan
> Signed-off-by: Xiubo Li
> ---
> drivers/leds/leds-adp5520.c | 5 +
>
On Wed, May 07, 2014 at 08:55:51PM +0900, Masami Hiramatsu wrote:
...
> +#if defined(CONFIG_PPC64) && (!defined(_CALL_ELF) || _CALL_ELF == 1)
> +/*
> + * On PPC64 ABIv1 the function pointer actually points to the
> + * function's descriptor. The first entry in the descriptor is the
> + * address
I use the btree which pickes up the latest version of kernel source
3.14-rc2 in my own module. When the btree module is removed, a warning arised:
kmem_cache_destroy btree_node: Slab cache still has objects
CPU: 13 PID: 9150 Comm: rmmod Tainted: GF O 3.14.0-rc2 #1
Hardware name: Inspur
Hello Daniel,
On 2014년 05월 07일 23:14, Daniel Kurtz wrote:
> On Wed, May 7, 2014 at 1:14 PM, Seung-Woo Kim wrote:
>> Hi Daniel,
>>
>> On 2014년 05월 05일 00:26, Daniel Kurtz wrote:
>>> Mixer hardware supports offsetting dma from start of source buffer using
>>> the MXR_GRP_SXY register.
>>>
>>>
On 05/08/2014 01:52 AM, Thomas Gleixner wrote:
> On Wed, 7 May 2014, Andrew Morton wrote:
>> On Wed, 7 May 2014 21:57:41 +0200 Borislav Petkov wrote:
>>
>>> We have all those eager tester dudes which scratch up a dirty script to
>>> pound on CPU hotplug senselessly and then report bugs they've
The OOM message of individual driver is unnecessary, and this is
duplicate the memory subsystem generic OOM message.
Signed-off-by: Xiubo Li
---
drivers/leds/leds-adp5520.c | 5 +
drivers/leds/leds-bd2802.c | 4 +---
drivers/leds/leds-da903x.c | 4 +---
drivers/leds/leds-da9052.c | 3 +--
Peter Zijlstra writes:
> How about something like this for the itrace thing?
It's much nicer than the page swizzling draft I was about to send you.
> You would mmap() the regular buffer; when write ->aux_{offset,size} in
> the control page. After which you can do a second mmap() with the
On Wed, May 07, 2014 at 12:59:06PM -0400, Alan Stern wrote:
> On Thu, 8 May 2014, Zhuang Jin Can wrote:
>
> > > A similar problem can occur in the opposite sense: The thread queuing
> > > the delayed status request might be delayed for so long that another
> > > SETUP packet arrives from the host
This patch moves data allocated using kzalloc to managed data allocated
using devm_kzalloc and cleans now unnecessary kfrees in probe and remove
functions. This data is the third argument to da9052_request_irq in the
two cases below.
The following Coccinelle semantic patch was used for making the
This patch adds new Kconfig file for adding new COMMON_CLK_SAMSUNG option.
Samsung platforms can select this for using common clock infrastructure.
CC: Mike Turquette
Signed-off-by: Pankaj Dubey
---
drivers/clk/Kconfig |2 ++
drivers/clk/samsung/Kconfig |3 +++
2 files changed,
This patch replaces PLAT_SAMSUNG with COMMON_CLK_SAMSUNG for Samsung
common clock support. Any Samsung SoC want to use Samsung common clock
infrastructure can simply select COMMON_CLK_SAMSUNG.
CC: Mike Turquette
Signed-off-by: Pankaj Dubey
---
drivers/clk/Makefile |2 +-
1 file changed, 1
This patch selects COMMON_CLK_SAMSUNG for EXYNOS and S3C64XX SoC
and removes COMMON_CLK selection as COMMON_CLK_SAMSUNG selects it's dependency.
CC: Russell King
Signed-off-by: Pankaj Dubey
---
arch/arm/Kconfig |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
This patch moves S3C24XX specific clock Kconfig options into
"clk/samsung/Kconfig" and also removes COMMON_CLK selection from
"mach-s3c24xx/Kconfig" as S3C24XX_COMMON_CLK is selecting it's dependency.
CC: Ben Dooks
CC: Kukjin Kim
CC: Russell King
Signed-off-by: Pankaj Dubey
---
Introduce a new Kconfig file for Samsung common clock infrastructure
related config options. As current Samsung common clock gets compiled
based on PLAT_SAMSUNG, but moving ahead with ARM64 we can not have any
more such config options, so this patch introduce new COMMON_CLK_SAMSUNG
invisible
On Thu, May 8, 2014 at 11:17 AM, Maxime Ripard
wrote:
> On Wed, May 07, 2014 at 07:25:54PM +0200, Boris BREZILLON wrote:
>> Add DT definitions for PRCM (Power/Reset/Clock Management) clock and reset
>> controller subdevices.
>>
>> Signed-off-by: Boris BREZILLON
>> ---
>>
On Wed, May 07, 2014 at 05:09:59PM +0200, Juan Solano wrote:
> This flag is a NOOP and can be removed now.
>
> Signed-off-by: Juan Solano
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Wed, May 7, 2014 at 8:10 PM, Sudeep Dutt wrote:
> On Thu, 2014-04-24 at 11:10 -0700, Siva Krishna Yerramreddy wrote:
>> On Mon, 2014-04-14 at 13:14 -0700, Siva Yerramreddy wrote:
>> > I am sending all these patches to char-misc because there is a dependency
>> > between the patches for dma
Peter Zijlstra writes:
> On Wed, May 07, 2014 at 02:08:43PM -0700, Andi Kleen wrote:
>> > Then, when data inside that aux data store changes they should inject an
>> > PERF_RECORD_AUX to indicate this did happen, which ties it back into the
>> > normal event flow.
>>
>> What happens when the
On Fri, May 02, 2014 at 10:04:29PM +0530, Vinod Koul wrote:
> On Wed, Apr 30, 2014 at 02:53:22PM -0700, Maxime Ripard wrote:
> > Hi Vinod,
> >
> > On Wed, Apr 30, 2014 at 12:34:08PM +0530, Vinod Koul wrote:
> > > On Thu, Apr 24, 2014 at 04:22:44PM +0200, Maxime Ripard wrote:
> > > > +static
On Wed, May 07, 2014 at 07:25:54PM +0200, Boris BREZILLON wrote:
> Add DT definitions for PRCM (Power/Reset/Clock Management) clock and reset
> controller subdevices.
>
> Signed-off-by: Boris BREZILLON
> ---
> arch/arm/boot/dts/sun6i-a31.dtsi | 39 ++-
> 1
On Wed, May 07, 2014 at 07:25:50PM +0200, Boris BREZILLON wrote:
> The PRCM (Power/Reset/Clock Management) block exposes several subdevices
> in different subsystems (clk, reset ...)
>
> Add basic support for the PRCM unit with clk (AR100, AHB0, and APB0 clks)
> and reset controller subdevices.
>
On Wed, May 07, 2014 at 07:25:52PM +0200, Boris BREZILLON wrote:
> The PRCM (Power/Reset/Clock Management) unit provides several clock
> devices:
> - AR100 clk: used to clock the Power Management co-processor
> - AHB0 clk: used to clock the AHB0 bus
> - APB0 clk and gates: used to clk peripherals
On Wed, May 07, 2014 at 07:25:49PM +0200, Boris BREZILLON wrote:
> The current implementation uses sunxi_reset_init function for both early
> init and platform device probe.
>
> The sunxi_reset_init function uses DT to retrieve device resources, which
> will be an issue if reset controllers are
On Wed, May 07, 2014 at 07:25:48PM +0200, Boris BREZILLON wrote:
> Add DT bindings documentation for sunxi's reset controllers.
>
> Signed-off-by: Boris BREZILLON
Acked-by: Maxime Ripard
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
Freescale's Integrated Flash controller(IFC) module is used to handle
devices such as NOR, NAND, FPGA and ASIC.
Update same in Help section of Kconfig for IFC.
Signed-off-by: Prabhakar Kushwaha
---
Changes for v2: Resending again keeping maintainer in 'CC'
drivers/memory/Kconfig |4
On Thu, 2014-04-24 at 11:10 -0700, Siva Krishna Yerramreddy wrote:
> On Mon, 2014-04-14 at 13:14 -0700, Siva Yerramreddy wrote:
> > I am sending all these patches to char-misc because there is a dependency
> > between the patches for dma driver and other drivers.
> >
> Greg, any feedback on the
Atmel actually has this issue in the Errata of the SAM9G25 and SAM9G35
datasheets which might be worth referencing in the description?
>49.7.1 RTC: Interrupt Mask Register cannot be used
>Interrupt Mask Register read always returns 0.
--
To unsubscribe from this list: send the line "unsubscribe
On Tue, 21 Jan 2014, David Rientjes wrote:
> On Wed, 8 Jan 2014, David Rientjes wrote:
>
> > > There used to be only one path out of __slab_alloc(), and
> > > ALLOC_SLOWPATH got bumped in that exit path. Now there are two,
> > > and a bunch of gotos. ALLOC_SLOWPATH can now get set more than
On 5/7/2014 3:52 PM, Frank Rowand wrote:
> On 5/7/2014 2:48 PM, Rob Herring wrote:
>> From: Rob Herring
>>
>> This series fixes the device naming collisions that can occur with
>> nultiple devices having the same name and non-translatable unit
>> addresses. This issue was raised in this
On Wed, May 07, 2014 at 06:48:52PM +0200, Maxime COQUELIN wrote:
> Commit 1d9fe6b97 ("clk: divider: Fix best div calculation for power-of-two and
> table dividers") introduces a regression in its _table_round_up function.
>
> When the divider passed to this function is greater than the max
On 5/7/2014 2:48 PM, Rob Herring wrote:
> From: Rob Herring
>
> Add a test case for nodes which have the same name and same
> non-translatable unit address.
If I apply patch 1 and 2 without applying 3 and 4 then console
warnings are printed, but from a different area of code than
the original
On Wed, May 07, 2014 at 07:12:30PM +0200, Boris BREZILLON wrote:
>
> On 29/04/2014 01:40, Maxime Ripard wrote:
> > On Mon, Apr 28, 2014 at 04:58:48PM +0200, Boris BREZILLON wrote:
> >> The PRCM (Power/Reset/Clock Management) unit provides several clock
> >> devices:
> >> - AR100 clk: used to
On Wed, May 07, 2014 at 06:54:08PM -0700, Josh Triplett wrote:
> On Wed, May 07, 2014 at 04:52:40PM -0700, Paul E. McKenney wrote:
> > On Wed, May 07, 2014 at 02:22:19PM -0700, j...@joshtriplett.org wrote:
> > > On Mon, Apr 28, 2014 at 05:24:55PM -0700, Paul E. McKenney wrote:
> > > > From: "Paul
The __vlan_find_dev_deep should always called in RCU, according
David's suggestion, rename to __vlan_find_dev_deep_rcu looks more
reasonable.
Signed-off-by: Ding Tianhong
---
drivers/net/ethernet/chelsio/cxgb3/cxgb3_offload.c | 2 +-
drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c| 2 +-
On Mon, May 05, 2014 at 12:17:23PM -0700, Mark Brown wrote:
> On Sun, May 04, 2014 at 11:21:47PM -0500, Maxime Ripard wrote:
> > On Fri, May 02, 2014 at 10:40:48AM -0700, Mark Brown wrote:
> > > > i2c-dev works great in these cases, because you always have access to
> > > > all the bus, and all
Hi Greg,
Sorry for the late reply.
(2014/04/26 1:01), Greg Kroah-Hartman wrote:
On Fri, Apr 25, 2014 at 05:53:02PM +0900, Yoshihiro YUNOMAE wrote:
Hi Greg,
Thank you for your review.
(2014/04/25 8:11), Greg Kroah-Hartman wrote:
On Thu, Apr 17, 2014 at 03:06:44PM +0900, Yoshihiro YUNOMAE
I believe that 3 item is required for DVFS. Those are frequency, voltage,
divider value.
Currently OPP only supports voltage and frequency.
So some cpufreq and devfreq driver get a divider value from struct divider
table.
How about adding that divider value into struct dev_pm_opp like this;
-next-20140507-sasha-4-g14be78b-dirty #448
Tainted: GW
[ 262.798430] ---
[ 262.799804] runtrin.sh/9791 is trying to acquire lock:
[ 262.801168] ((console_sem).lock){-.-...}, at: down_trylock
(kernel/locking/semaphore.c:137
From: Brian Lilly
Data: Thursday, May 08, 2014 3:52 AM
>To: Florian Fainelli
>Cc: Uwe Kleine-König; David S. Miller; Estevam Fabio-R49496; Jim Baxter; Li
>Frank-
>B20596; Duan Fugang-B38611; netdev; linux-kernel@vger.kernel.org; kernel
>Subject: Re: i.MX28 based system losing eth0 on boot
>
On Wed, May 07, 2014 at 12:23:08AM +0400, Cyrill Gorcunov wrote:
> On Tue, May 06, 2014 at 11:42:58AM -0400, Vince Weaver wrote:
> >
> > So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
> >
> > It crashes more or less instantly (sorry for the line wrapping,
> > just
On Mon, May 5, 2014 at 9:48 AM, Christoph Lameter wrote:
> Would you merge this patch please?
>
>
Sure, I merged it to my my tree
Thanks,
-Bryan
> Use this_cpu_ptr for the address calculation instead of __get_cpu_var.
>
> Acked-by: Bryan Wu
> Signed-off-by: Christoph Lameter
>
> Index:
On Wed, May 7, 2014 at 8:22 PM, Jonghwan Choi wrote:
>> @Jonghwan: Please consider doing this:
>> - Don't play with the order of frequencies in table.
>> - Instead initialize .driver_data filed with values that you need to write
>> in the registers for all frequencies. i.e. 0 for highest
On Wed, May 07, 2014 at 04:52:40PM -0700, Paul E. McKenney wrote:
> On Wed, May 07, 2014 at 02:22:19PM -0700, j...@joshtriplett.org wrote:
> > On Mon, Apr 28, 2014 at 05:24:55PM -0700, Paul E. McKenney wrote:
> > > From: "Paul E. McKenney"
> > >
> > > Some environments require some variation on
On Tue, Apr 29, 2014 at 02:21:22PM -0700, John Stultz wrote:
> Users of volatile ranges will need to know if memory was discarded.
> This patch adds the purged state tracking required to inform userland
> when it marks memory as non-volatile that some memory in that range
> was purged and needs to
(Oops, previous e-mail was sent halfway through composition in error.)
> I'm not sure it's even correct since
> you're now clearing after doing recheck_pfmemalloc_active().
I thought this through before rearranging the code.
recheck_pfmemalloc_active() checks global lists, but __ac_get_obj()
is
On Wed, May 07, 2014 at 07:50:48PM +, Elliott, Robert (Server Storage)
wrote:
> Don Zickus wrote:
> > The main reason for this patch is because I have a hard time knowing
> > what NMI handlers are registered on the system when debugging NMI issues.
> >
> > This info is provided in
> @Jonghwan: Please consider doing this:
> - Don't play with the order of frequencies in table.
> - Instead initialize .driver_data filed with values that you need to write
> in the registers for all frequencies. i.e. 0 for highest frequency and
> FREQ_COUNT-1 for lowest one.
-> For that, I
Hey John,
On Tue, Apr 29, 2014 at 02:21:21PM -0700, John Stultz wrote:
> This patch introduces MADV_VOLATILE/NONVOLATILE flags to madvise(),
> which allows for specifying ranges of memory as volatile, and able
> to be discarded by the system.
>
> This initial patch simply adds flag handling to
On Wed, 7 May 2014, Joonsoo Kim wrote:
> Factor out initialization of array cache to use it in following patch.
>
> Acked-by: Christoph Lameter
> Signed-off-by: Joonsoo Kim
>
Acked-by: David Rientjes
s/arracy/array/ in patch title.
> diff --git a/mm/slab.c b/mm/slab.c
> index
On 05/07/2014 05:45 PM, 管雪涛 wrote:
> Cc: Greg Kroah-Hartman
>
>> On 05/01/2014 02:48 AM, Guenter Roeck wrote:
>
>>> Build results are at http://server.roeck-us.net:8010/builders.
>>>
>
> I'll fix it in this month.
>
> Also, Cc greg
>
Thank you for your work, it will be great if can finish
On Wed, 7 May 2014, Joonsoo Kim wrote:
> In free_block(), if freeing object makes new free slab and number of
> free_objects exceeds free_limit, we start to destroy this new free slab
> with holding the kmem_cache node lock. Holding the lock is useless and,
> generally, holding a lock as least as
On 05/07/2014 06:02 PM, Andrew Morton wrote:
> On Wed, 07 May 2014 12:59:28 -0400 Sasha Levin wrote:
>
>> Hi all,
>>
>> While fuzzing with trinity inside a KVM tools guest running the latest -next
>> kernel I've stumbled on the following spew:
>>
>> [ 1139.410483] general protection fault:
On Wed, 7 May 2014, Joonsoo Kim wrote:
> node isn't changed, so we don't need to retreive this structure
> everytime we move the object. Maybe compiler do this optimization,
> but making it explicitly is better.
>
> Acked-by: Christoph Lameter
> Signed-off-by: Joonsoo Kim
Acked-by: David
> A function called clear_obj_pfmemalloc() doesn't indicate it's returning
> anything, I think the vast majority of people would believe that it
> returns void just as it does. There's no complier generated code
> optimization with this patch and
> I'm not sure it's even correct since
>
tpm_add_ppi fails without ACPI support now, but loading the tpm without an ACPI
entry is a valid use case. This changes the init of the tpm to not fail when
tpm_add_ppi fails.
Signed-off-by: Derek Basehore
---
drivers/char/tpm/tpm-interface.c | 3 +--
1 file changed, 1 insertion(+), 2
commit d95ea5d1('cma: fix watermark checking') introduces ALLOC_CMA flag
for alloc flag and treats free cma pages as free pages if this flag is
passed to watermark checking. Intention of that patch is that movable page
allocation can be be handled from cma reserved region without starting
kswapd.
We already have retry logic in migrate_pages(). It does retry 10 times.
So if we keep this retrying code in __alloc_contig_migrate_range(), we
would try to migrate some unmigratable page in 50 times. There is just one
small difference in -ENOMEM case. migrate_pages() don't do retry
in this case,
CMA is introduced to provide physically contiguous pages at runtime.
For this purpose, it reserves memory at boot time. Although it reserve
memory, this reserved memory can be used for movable memory allocation
request. This usecase is beneficial to the system that needs this CMA
reserved memory
Hello,
This series tries to improve CMA.
CMA is introduced to provide physically contiguous pages at runtime
without reserving memory area. But, current implementation works like as
reserving memory approach, because allocation on cma reserved region only
occurs as fallback of migrate_movable
On Wed, May 07, 2014 at 09:58:58AM +0200, Arnd Bergmann wrote:
> On Tuesday 06 May 2014 16:48:40 Bjorn Helgaas wrote:
> > Convert the "iova" arguments of iommu_map(), iommu_unmap(), etc., from
> > "unsigned long" to dma_addr_t.
> >
> > bb5547acfcd8 ("iommu/fsl: Make iova dma_addr_t in the
On Wed, May 07, 2014 at 02:34:26PM -0700, j...@joshtriplett.org wrote:
> On Mon, Apr 28, 2014 at 05:25:07PM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney"
> >
> > The srcu_torture_stats() function prints SRCU's per-CPU c[] array with
> > an unsigned format, which means that the
On Wed, May 7, 2014 at 2:37 AM, Marc Zyngier wrote:
> On Wed, May 07 2014 at 1:53:45 am BST, Feng Kan wrote:
>> This change is made to preserve the GIC v2 bypass bits in the
>> GIC_CPU_CTRL register (also known as the GICC_CTLR register in spec).
>> This code will preserve all bits configured
On Wed, May 07, 2014 at 02:33:27PM -0700, j...@joshtriplett.org wrote:
> On Mon, Apr 28, 2014 at 05:25:06PM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney"
> >
> > In a normal torture-test run, the script inherits its environment
> > variables, but this does not work when producing a
This change is made to preserve the GIC v2 bypass bits in the
GIC_CPU_CTRL register (also known as the GICC_CTLR register in spec).
This code will preserve all bits configured by the bootload regarding
v2 bypass group bits. In the X-Gene platform, the bypass functionality
is not used and bypass
On Wed, May 07, 2014 at 02:29:37PM -0700, j...@joshtriplett.org wrote:
> On Mon, Apr 28, 2014 at 05:25:03PM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney"
> >
> > The torture tests need to set specific values for their respective
> > Kconfig options (e.g., CONFIG_LOCK_TORTURE_TEST),
On Wed, May 07, 2014 at 02:26:09PM -0700, j...@joshtriplett.org wrote:
> On Mon, Apr 28, 2014 at 05:24:59PM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney"
> >
> > This commit makes the torture scripts a bit more RCU-independent.
> >
> > Signed-off-by: Paul E. McKenney
>
> Bug
On Wed, May 07, 2014 at 02:27:56PM -0700, j...@joshtriplett.org wrote:
> On Mon, Apr 28, 2014 at 05:25:00PM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney"
> >
> > This commit makes the torture scripts a bit more RCU-independent.
> >
> > Signed-off-by: Paul E. McKenney
>
> One
On Wed, May 07, 2014 at 02:27:08PM -0700, j...@joshtriplett.org wrote:
> On Mon, Apr 28, 2014 at 05:24:59PM -0700, Paul E. McKenney wrote:
> > - if test -n "$RCU_QEMU_INTERACTIVE" -a -n "$RCU_QEMU_MAC"
> > + if test -n "$TORTURE_QEMU_INTERACTIVE" -a -n "$RCU_QEMU_MAC"
> >
On Wed, May 07, 2014 at 02:20:15PM -0700, j...@joshtriplett.org wrote:
> On Mon, Apr 28, 2014 at 05:24:54PM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney"
> >
> > The current lock_torture_writer() spends too much time sleeping and not
> > enough time hammering locks, as in an
John,
On Wed, May 7, 2014 at 3:46 PM, John Stultz wrote:
> On 05/07/2014 11:32 AM, Doug Anderson wrote:
>> John,
>>
>> On Wed, May 7, 2014 at 11:10 AM, John Stultz wrote:
>>> On 05/06/2014 09:19 PM, Doug Anderson wrote:
John,
On Tue, May 6, 2014 at 5:25 PM, John Stultz wrote:
On Wed, May 07, 2014 at 02:22:19PM -0700, j...@joshtriplett.org wrote:
> On Mon, Apr 28, 2014 at 05:24:55PM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney"
> >
> > Some environments require some variation on "make defconfig" to initialize
> > the .config file. This commit therefore
The loops_per_jiffy count continues to be updated as each CPU is
brought up. This causes problems when we've got an HMP system and
different CPUs have different loops per jiffy. On exynos 542x
systems, for instance, the A7s will have significantly lower loops per
jiffy than their big brothers.
On Wed, May 07, 2014 at 02:16:49PM -0700, j...@joshtriplett.org wrote:
> On Mon, Apr 28, 2014 at 05:24:49PM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney"
> >
> > The rcutorture output currently does not distinguish between stalls in
> > the RCU implementation and stalls in the
Hi Andrey,
On Mon, May 05, 2014 at 11:11:13AM +0400, Andrey Ryabinin wrote:
> memset doesn't work right for following example:
>
> signed char c = 0xF0;
> memset(addr, c, size);
>
> Variable c is signed, so after typcasting to int the value will be 0xFFF0.
> This value will be
On 05/07/2014 05:40 PM, Alex Courbot wrote:
> On 05/08/2014 12:57 AM, Stephen Warren wrote:
>> On 05/06/2014 09:18 PM, Alexandre Courbot wrote:
>>> Console rotation is needed for devices like Tegra Note 7 and NVIDIA
>>> SHIELD to get the boot console in the expected orientation.
>>
>> I've
On 05/08/2014 12:57 AM, Stephen Warren wrote:
On 05/06/2014 09:18 PM, Alexandre Courbot wrote:
Console rotation is needed for devices like Tegra Note 7 and NVIDIA
SHIELD to get the boot console in the expected orientation.
I've squashed this into Tegra's for-3.16/defconfig branch.
Can you
On Monday, May 05, 2014 10:49:49 PM Igor Mammedov wrote:
> acpi_processor_add() assumes that present at boot CPUs
> are always onlined, it is not so if a CPU failed to become
> onlined. As result acpi_processor_add() will mark such CPU
> device as onlined in sysfs and following attempts to
>
bump
On Mon, Apr 21, 2014 at 10:56:08AM +0900, Minchan Kim wrote:
> Linux doesn't have an ability to free pages lazy while other OS
> already have been supported that named by madvise(MADV_FREE).
>
> The gain is clear that kernel can discard freed pages rather than
> swapping out or OOM if
The bindings for CPU enable methods are defined in ".../arm/cpus.txt". As
additional 32-bit ARM CPUS are converted to use the "enable-method" CPU
property to imply a particular set of SMP operations to use, the list of these
methods is likely to become unwieldy. The current documentation already
Downscaling loops_per_jiffy on SMP ARM systems really doesn't work.
You could really only do this if:
* Each CPU is has independent frequency changes (changing one CPU
doesn't affect another).
* We change the generic ARM udelay() code to actually look at percpu
loops_per_jiffy.
I don't know
[+cc Magnus, linux-sh (sorry, I forgot to tell stgit to cc you)]
On Wed, May 07, 2014 at 10:15:10AM +0200, Arnd Bergmann wrote:
> On Wednesday 07 May 2014 09:55:16 Arnd Bergmann wrote:
> > On Tuesday 06 May 2014 16:48:33 Bjorn Helgaas wrote:
> > > @@ -51,8 +53,12 @@ static void
Users want to know the features of their hardware and we need a better
way to get it than parsing it out of dmesg. This series adds a simple
registration interface for IOMMUs and an example base implementation
for intel-iommu.
One key hardware feature for device assignment is the IOMMU support
1 - 100 of 1824 matches
Mail list logo
