On Thu, 2015-03-26 at 17:37 +0100, Mathias Krause wrote:
> On 26 March 2015 at 17:13, Joe Perches wrote:
> > On Thu, 2015-03-26 at 13:40 +0100, Mason wrote:
> >> On 25/03/2015 19:01, Joe Perches wrote:
> >> > On Wed, 2015-03-25 at 18:56 +0100, Mason wrote:
> >> >
> >> >> AFAIU, functions only
On Thu, Mar 26, 2015 at 10:24 AM, Christian Borntraeger
wrote:
>
> Oh I just added that check back then because some guy named
> Linus suggested something like that ;-)
Yes, my bad.
In my defense, that was when we were talking about ACCESS_ONCE()
causing bugs with gcc due to the blind use of
On Thu, Mar 26, 2015 at 05:47:00PM +, Peter Zijlstra wrote:
> On Thu, Mar 26, 2015 at 05:38:45PM +, Morten Rasmussen wrote:
> > Another potential solution is to stay with weak functions but move the
> > multiplication and shift into the arch_scale_*() functions by passing
> > the value we
On Thu, Mar 26, 2015 at 05:38:45PM +, Morten Rasmussen wrote:
> Another potential solution is to stay with weak functions but move the
> multiplication and shift into the arch_scale_*() functions by passing
> the value we want to scale into the arch_scale_*() function. That way we
> can
The arch_scale_{freq, cpu}_capacity() functions currently return a
scaling factor that need to be multiplied and shifted by the caller. The
default weak functions don't result in any scaling by the the
multiplication and shift is still done. By moving the multiplication and
shift into the
Apply frequency scale-invariance correction factor to usage tracking.
Each segment of the running_load_avg geometric series is now scaled by the
current frequency so the utilization_avg_contrib of each entity will be
invariant with frequency scaling. As a result, utilization_load_avg which is
the
On Thu, Mar 26, 2015 at 05:38:45PM +, Morten Rasmussen wrote:
> The only downside is that for frequency invariance we need three
> arch_scale_freq_capacity() calls instead of two.
It should have been instead of one...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Some architecture would like to be triggered when a memory area is moved
through the mremap system call.
This patch is introducing a new arch_remap mm hook which is placed in the
path of mremap, and is called before the old area is unmapped (and the
arch_unmap hook is called).
The architectures
* Nishanth Menon [150325 16:32]:
> On 03/25/2015 06:25 PM, Praneeth Bajjuri wrote:
> > ARM errata 798181 is applicable for OMAP5/DRA7 based devices. So enable
> > the same in the build.
> >
> > DRA7xx is based on Cortex-A15 r2p2 revision.
> >
> > ARM Errata extract and workaround information is
CRIU is recreating the process memory layout by remapping the checkpointee
memory area on top of the current process (criu). This includes remapping
the vDSO to the place it has at checkpoint time.
However some architectures like powerpc are keeping a reference to the vDSO
base address to build
* Stefan Agner [150321 17:00]:
> The NULL pointer check for superset->muxnames will always evaluate
> true since muxnames is an array within struct omap_mux. Remove the
> superfluous check to avoid warnings when using LLVM/clang.
>
> Signed-off-by: Stefan Agner
Applying into
Some processes (CRIU) are moving the vDSO area using the mremap system
call. As a consequence the kernel reference to the vDSO base address is
no more valid and the signal return frame built once the vDSO has been
moved is not pointing to the new sigreturn address.
This patch handles vDSO
On Wed, Mar 25, 2015 at 06:08:42PM +, Vincent Guittot wrote:
> On 25 March 2015 at 18:33, Peter Zijlstra wrote:
> > On Tue, Mar 24, 2015 at 11:00:57AM +0100, Vincent Guittot wrote:
> >> On 23 March 2015 at 14:19, Peter Zijlstra wrote:
> >> > On Fri, Feb 27, 2015 at 04:54:07PM +0100, Vincent
On 26 March 2015 at 09:29, John Stultz wrote:
> On Thu, Mar 26, 2015 at 4:31 AM, Prarit Bhargava wrote:
>> On 03/25/2015 07:44 PM, John Stultz wrote:
>>> + printf("%-22s %s missing CAP_WAKE_ALARM?:
>>> [UNSUPPORTED]\n",
>>> +
On 03/26/2015 07:18 PM, Christoph Hellwig wrote:
> On Thu, Mar 26, 2015 at 06:57:47PM +0200, Boaz Harrosh wrote:
>> For one this auto discovery of yours is very (very) nice but is a bit
>> inconvenience. Before I would reserve a big chuck on each NUMA range
>> on Kernel's memmap= And then at pmem
On Fri, 20 Feb 2015 12:28:48 -0500
Nicholas Mc Guire wrote:
> This hopfully address all of the issues Ingo Molnar noted
> in https://lkml.org/lkml/2015/2/18/690.
This looks OK to me, modulo some small English quibbles. Ingo, does this
satisfy your concerns?
Thanks,
jon
--
To unsubscribe
Am 26.03.2015 um 17:15 schrieb Linus Torvalds:
> On Thu, Mar 26, 2015 at 7:22 AM, Peter Zijlstra wrote:
>>
>> So we can either just remove the READ_ONCE(), or replace it with a
>> leading barrier() call just to be on the paranoid side of things.
>
> NOOO!
>
>> Any preferences?
>
> Not a
On Thu, Mar 26, 2015 at 07:02:17PM +0200, Boaz Harrosh wrote:
> Christoph why did you choose the fat and ugly version of
> pmem.c beats me. Anyway, here are the cleanups you need on
> top of your pmem patch.
>
> Among other it does:
> * Remove getgeo. It is not needed for modern fdisk and was
Am 26.03.2015 um 18:07 schrieb Peter Zijlstra:
> On Thu, Mar 26, 2015 at 09:45:07AM -0700, Linus Torvalds wrote:
>
>> Stop this idiocy.
>
> Yeah, clearly I can type faster than I can think straight :/
>
>
> In any case, I've the below patch; do you want to take it now or do you
> want me to
On 03/26/2015 09:47 AM, Ben Romer wrote:
On 03/26/2015 08:01 AM, Greg Kroah-Hartman wrote:
I need an ack from Benjamin and/or David before I can take these, as
they are the maintainers of the driver, and have the ability to test
these patches.
I'll just wait to apply them until that happens.
On 03/19/15 14:11, Chanwoo Choi wrote:
> Hi Bartlomiej,
>
Hi,
> I tested this patch-set for AFTR mode.
> When CPU1 is offline state, I checked that CPU0 enter the AFTR mode.
>
> Tested-by: Chanwoo Choi
>
Thanks for your test.
> Best Regards,
> Chanwoo Choi
>
> On 03/19/2015 01:00 AM,
On Thu, Mar 26, 2015 at 06:57:47PM +0200, Boaz Harrosh wrote:
> For one this auto discovery of yours is very (very) nice but is a bit
> inconvenience. Before I would reserve a big chuck on each NUMA range
> on Kernel's memmap= And then at pmem map= would slice and dice it
> as I want hot style on
On Thu, Mar 26, 2015 at 05:07:48PM +, Peter Zijlstra wrote:
> On Thu, Mar 26, 2015 at 09:45:07AM -0700, Linus Torvalds wrote:
>
> > Stop this idiocy.
>
> Yeah, clearly I can type faster than I can think straight :/
>
>
> In any case, I've the below patch; do you want to take it now or do
On Tue, 24 Mar 2015 17:37:19 +0800
w...@redhat.com wrote:
> This is a update of Chinese documentation:
> Documentation/zh_CN/arm64/booting.txt
>
Applied to the docs tree, thanks.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Mon, Mar 09, 2015 at 04:27:11PM -0400, Peter Hurley wrote:
> Changes from v2:
> * remainder of unapplied series
> * Changed the title and commit log for
> "serial: earlycon: Allow earlycon params with name only" to
> "serial: earlycon: Skip parse_options() for empty string" per Rob's
>
On Thu, Mar 26, 2015 at 09:37:50AM -0700, Linus Torvalds wrote:
> On Mar 26, 2015 9:29 AM, "Peter Zijlstra" wrote:
> >
> > And the size check in READ_ONCE() helps asserting this.
>
> No it d does NOT.
>
> Even the documentation you quoted agrees with me: the shearing issue is
> only for sizes
On Thu, Mar 26, 2015 at 08:47:36PM +0530, Ramneek Mehresh wrote:
> Add controller version based ULPI and UTMI phy initialization for
> otg driver
>
> Signed-off-by: Shengzhou Liu
> Signed-off-by: Ramneek Mehresh
> Reviewed-by: Fleming Andrew-AFLEMING
> Tested-by: Fleming Andrew-AFLEMING
this
On 03/26/2015 11:52 AM, Joerg Roedel wrote:
Hi Mark,
On Thu, Mar 26, 2015 at 10:58:15AM -0400, Mark Hounschell wrote:
Sorry but CMA was still badly broken. I have a patch below that works.
In which way is it broken? What happens when you try to allocate memory
with dma_alloc_coherent?
I
On 03/26/2015 10:03 AM, Geert Uytterhoeven wrote:
Hi David,
On Thu, Mar 26, 2015 at 5:44 PM, David Daney wrote:
--- a/Documentation/stable_kernel_rules.txt
+++ b/Documentation/stable_kernel_rules.txt
@@ -81,6 +81,16 @@ format in the sign-off area:
git cherry-pick fd21073
git
On Tue, Mar 24, 2015 at 11:50:47AM -0700, Matt Mullins wrote:
> We're also developing a user of direct_access, and we ended up with some
> questions about the sleeping guarantees of the direct_access API.
That's a great question. Since DAX can always sleep when it's calling
into
From: David Daney
Signed-off-by: David Daney
---
v3: s/the the/the/
v2: Rebased, because first version no longer applied.
Documentation/stable_kernel_rules.txt | 10 ++
1 file changed, 10 insertions(+)
diff --git a/Documentation/stable_kernel_rules.txt
On Thu, Mar 26, 2015 at 09:45:07AM -0700, Linus Torvalds wrote:
> Stop this idiocy.
Yeah, clearly I can type faster than I can think straight :/
In any case, I've the below patch; do you want to take it now or do you
want me to route it through tip/locking/urgent or something like that?
---
On Sun, 22 Mar 2015 11:35:55 -0700
Michael Opdenacker wrote:
> This is a fix for the only broken link in kernel documentation,
> at least according to the "linkchecker" tool that we are running
> on the Free Electrons website once a day.
>
> As kernel documentation is part of our website
> (on
Hi David,
On Thu, Mar 26, 2015 at 5:44 PM, David Daney wrote:
> --- a/Documentation/stable_kernel_rules.txt
> +++ b/Documentation/stable_kernel_rules.txt
> @@ -81,6 +81,16 @@ format in the sign-off area:
> git cherry-pick fd21073
> git cherry-pick
>
> +Also, some patches may have
On Thu, 2015-03-26 at 18:32 +0530, Preeti U Murthy wrote:
> kernel/sched/fair.c |8 +---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index bcfe320..8b6d0d5 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
>
Christoph why did you choose the fat and ugly version of
pmem.c beats me. Anyway, here are the cleanups you need on
top of your pmem patch.
Among other it does:
* Remove getgeo. It is not needed for modern fdisk and was never
needed for libgparted and cfdisk.
* remove 89 lines of code to do a
On 03/26/2015 05:27 PM, Doug Ledford wrote:
> On Thu, 2015-03-26 at 17:04 +0100, Michael Wang wrote:
>> [snip]
>>
>> Few more questions here is:
>> 1. when to setup? (maybe inside ib_register_device() before doing
>> client->add() callback?)
> I don't think "we" can set it up here. The driver's
On 03/26/2015 10:32 AM, Christoph Hellwig wrote:
> Here is another version of the same trivial pmem driver, because two
> obviously aren't enough. The first patch is the same pmem driver
> that Ross posted a short time ago, just modified to use platform_devices
> to find the persistant memory
Hi Lee,
On Thu, Mar 26, 2015 at 2:51 PM, Lee Jones wrote:
> On Wed, 25 Mar 2015, Geert Uytterhoeven wrote:
>> On Mon, Mar 9, 2015 at 10:28 AM, Lee Jones wrote:
>> > On Fri, 06 Mar 2015, Mike Turquette wrote:
>> >> This approach looks fine to me. In practice I think it is restricted to
>> >>
From: Sjoerd Simons
When disabling the samsung PWM the output state remains at the level it
was in the end of a pwm cycle. In other words, calling pwm_disable when
at 100% duty will keep the output active, while at all other setting the
output will go/stay inactive. On top of that the samsung
On Thu, Mar 26, 2015 at 10:40:15AM +, Build bot for Mark Brown wrote:
For the past couple of days -next has been failing to build an ARM
allmodconfig due to the use of defines which don't appear anywhere in
the kernel, introduced in f35ba5c9f6043 (mfd: qcom_rpm: Add support for
IPQ8064):
>
Hi:
Boot of an 8-socket T5 sparc system fails on top of tree. git bisect
points to this commit:
commit 904bf6bd150bdafb42ddbb3257ea8
Author: Yinghai Lu
Date: Thu Jan 15 16:21:51 2015 -0600
sparc/PCI: Clip bridge windows to fit in upstream windows
Every PCI-PCI bridge window should fit
On 03/26/15 04:08, Javier Martinez Canillas wrote:
> This patch enables the options to mount a rootfs over NFS and also support
> for automatic configuration of IP addresses during boot as needed by NFS.
>
> Signed-off-by: Javier Martinez Canillas
> ---
>
> Changes since v1:
> - Found a typo
On Thu, Mar 26, 2015 at 05:02:57PM +0800, w...@redhat.com wrote:
> From: Fu Wei
>
> This is a Chinese translated version of
> Documentation/arm64/legacy_instructions.txt
>
> It is based on the modifications of
> Documentation/arm64/legacy_instructions.txt in submission:
> "587064b6",
On Thu, Mar 26, 2015 at 04:07:16PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > I don't know. This seems exactly like the kind of thing
> > we had in mind when we added the virtio pci capability.
> > For example, we have text in spec that requires drivers
> > to skip unknown capabilities.
> >
> >
On Thu, Mar 26, 2015 at 05:44:42PM +0100, Peter Zijlstra wrote:
> On Thu, Mar 26, 2015 at 05:36:47PM +0100, Peter Zijlstra wrote:
> > Can't we make an argument that these barrier calls are not required? The
> > memcpy() call already guarantees we emit the loads and its opaque so the
> > compiler
On 03/25/2015 07:05 AM, Greg Kroah-Hartman wrote:
On Mon, Feb 09, 2015 at 03:39:23PM -0800, David Daney wrote:
From: David Daney
Signed-off-by: David Daney
---
Documentation/stable_kernel_rules.txt | 10 ++
1 file changed, 10 insertions(+)
diff --git
On Thu, Mar 26, 2015 at 05:36:47PM +0100, Peter Zijlstra wrote:
> Can't we make an argument that these barrier calls are not required? The
> memcpy() call already guarantees we emit the loads and its opaque so the
> compiler cannot 'cache' the value. So I see not immediate reason for the
> dual
On Thu, Mar 26, 2015 at 05:49:38PM +0200, Boaz Harrosh wrote:
> > + memmap=nn[KMG]!ss[KMG]
> > + [KNL,X86] Mark specific memory as protected.
> > + Region of memory to be used, from ss to ss+nn.
> > + The memory region may be marked as e820
From: David Daney
Signed-off-by: David Daney
---
v2: Rebased, because first version no longer applied.
Documentation/stable_kernel_rules.txt | 10 ++
1 file changed, 10 insertions(+)
diff --git a/Documentation/stable_kernel_rules.txt
b/Documentation/stable_kernel_rules.txt
index
On 2015/03/27 0:18, Tejun Heo wrote:
Hello,
On Thu, Mar 26, 2015 at 01:04:00PM +0800, Gu Zheng wrote:
wq generates the numa affinity (pool->node) for all the possible cpu's
per cpu workqueue at init stage, that means the affinity of currently un-present
ones' may be incorrect, so we need to
The Logitech T650 used to report 3 fingers swipes to the up as a press on
the Super key. When we switched the touchpad to the raw mode, we also
disable such firmware gesture and some users may rely on it.
Unfortunately, 3 finger swipes are still not supported in most of the
Linux environments,
update the cooling level for cpu0 to avoid following message.
root@odroidxu3:~# dmesg | grep ther
[0.241511] /thermal-zones/cpu-thermal/cooling-maps/map0:
could not get #cooling-cells for /cpus/cpu@0
Signed-off-by: Anand Moon
---
arch/arm/boot/dts/exynos5420.dtsi |
Add pwm-fan node to the OdroidXU3 board.
Tested on OdroidXU3 board.
Signed-off-by: Anand Moon
---
arch/arm/boot/dts/exynos5422-odroidxu3.dts | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5422-odroidxu3.dts
This commit enables TMU IP block on the Exynos5422 OdroidXU3
device.
Tested on OdroidXU3 board.
Signed-off-by: Anand Moon
---
arch/arm/boot/dts/exynos5422-odroidxu3.dts | 25 +
1 file changed, 25 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5422-odroidxu3.dts
Below changes depend on following patch.
https://patchwork.kernel.org/patch/5944061/
Update the pwm_config with duty then update the pwm_disable
to poweroff the cpu fan.
Tested on OdroidXU3 board.
Signed-off-by: Anand Moon
---
drivers/hwmon/pwm-fan.c | 10 --
1 file changed, 4
Move the registration of thermal sensors for tmu_cpu0 from exynos5420.dtsi
to exynos5-cpu-thermal.dtsi, to avoid duplicate registration of the sensors.
Tested on OdroidXU3 board.
Signed-off-by: Anand Moon
---
arch/arm/boot/dts/exynos5-cpu-thermal.dtsi | 58 ++
This work depeds upon work done by Lukasz Majewski
and Sjoerd Simons regarding the pwm-fan.
-Anand Moon
--
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 at
On 26 March 2015 at 17:13, Joe Perches wrote:
> On Thu, 2015-03-26 at 13:40 +0100, Mason wrote:
>> On 25/03/2015 19:01, Joe Perches wrote:
>> > On Wed, 2015-03-25 at 18:56 +0100, Mason wrote:
>> >
>> >> AFAIU, functions only used at system init are tagged __init to have
>> >> the linker store
On Thu, Mar 26, 2015 at 09:21:50AM -0700, Linus Torvalds wrote:
> So the proper patch looks something like this:
>
> diff --git a/include/linux/compiler.h b/include/linux/compiler.h
> index 1b45e4a0519b..f36e1abf56ea 100644
> --- a/include/linux/compiler.h
> +++
On Thu, Mar 26, 2015 at 4:01 AM, Holger Dengler wrote:
> On 03/26/2015 10:41 AM, Daniel Lezcano wrote:
>>
>> config CLKSRC_FLEXCARD
>> bool
>> select CLKSRC_MMIO
>
> The Flexcard PMC II, which provides this clocksrc functionality, is a
> PCI card. According to the PMC specs, this
On 2015/03/26 13:55, Gu Zheng wrote:
> Hi Kame-san,
> On 03/26/2015 11:19 AM, Kamezawa Hiroyuki wrote:
>
>> On 2015/03/26 11:17, Gu Zheng wrote:
>>> Previously, we build the apicid <--> cpuid mapping when the cpu is present,
>>> but
>>> the relationship will be changed if the cpu/node hotplug
On Mon, Mar 23, 2015 at 8:34 PM, Yijing Wang wrote:
> Introduce pci_host_bridge_list to manage pci host
> bridges in system, this make us have the ability
> to check whether the new host would conflict with
> existing one. Then we could remove bus alreay exist
> check in __pci_create_root_bus().
Hi Richard,
At Wed, 25 Mar 2015 23:50:23 +0100,
Richard Weinberger wrote:
>
> Hi!
>
> Am 25.03.2015 um 15:48 schrieb Hajime Tazaki:
> >
> > At Tue, 24 Mar 2015 16:27:51 +0100,
> > Richard Weinberger wrote:
> >>
> >> I'd say you should try hard to re-use/integrate your work in arch/um.
> >>
On Thu, Mar 26, 2015 at 4:31 AM, Prarit Bhargava wrote:
> On 03/25/2015 07:44 PM, John Stultz wrote:
>> + printf("%-22s %s missing CAP_WAKE_ALARM?:
>> [UNSUPPORTED]\n",
>> + clockstring(clock_id),
>> +
On Thu, Mar 26, 2015 at 09:15:21AM -0700, Linus Torvalds wrote:
> Notice how it is *not* about atomicitiy. The compiler can read the
> value in fifteen pieces, randomly mixing one bit or five. Nobody
> cares.
If you read Documentation/memory-barriers.txt you'll find that it very
much also is
On Thu, Mar 26, 2015 at 5:00 PM, Octavian Purdila
wrote:
> On Thu, Mar 26, 2015 at 4:47 PM, Mika Westerberg
> wrote:
>> On Thu, Mar 26, 2015 at 04:37:39PM +0200, Octavian Purdila wrote:
>>> On Thu, Mar 26, 2015 at 4:04 PM, Mika Westerberg
>>> wrote:
>>> > On Thu, Mar 26, 2015 at 02:04:35PM
On Thu, 2015-03-26 at 17:04 +0100, Michael Wang wrote:
> Hi, Doug
>
> Thanks for the excellent comments :-)
>
> On 03/26/2015 03:09 PM, Doug Ledford wrote:
> > On Wed, 2015-03-25 at 16:09 +0100, Michael Wang wrote:
> >> [snip]
> >>
> > [snip]
> >
> > So, I would suggest that we fix things up
On 24/03/15 22:53, Mark Brown wrote:
On Tue, Mar 24, 2015 at 10:30:08PM +, Srinivas Kandagatla wrote:
+static ssize_t bin_attr_eeprom_write(struct file *filp, struct kobject *kobj,
+struct bin_attribute *attr,
+char
On 03/26/15 11:26, Vitaly Kuznetsov wrote:
> Commit 79208c57da53 ("Drivers: hv: hv_balloon: Make adjustments in computing
> the floor") was inacurate as it introduced a jump in our piecewiese linear
> 'floor' function:
>
> At 2048MB we have:
> Left limit:
> 104 + 2048/8 = 360
> Right limit:
> 256
On Thu, 26 Mar 2015 17:46:14 +0800
Fu Wei wrote:
> Sorry, I didn't notice that you are the DOCUMENTATION Maintainers now.
> I just checked the MAINTAINERS file.
> will cc to you for all the documentation patch.
The MAINTAINERS entry actually explicitly excludes the translation
directories; it
On Thu, Mar 26, 2015 at 9:15 AM, Linus Torvalds
wrote:
>
> Really. Just get rid of the checks - they were wrong. They were
> clearly very close to *introducing* a bug, rather than fixing anything
> at all.
Side note: we will continue to expect the compiler to do single-word
accesses as a single
On Thu, Mar 26, 2015 at 4:32 AM, Prarit Bhargava wrote:
> On 03/25/2015 07:44 PM, John Stultz wrote:
>> For the default run_timers target, the timers tests takes the
>> majority of kselftests runtime.
>>
>> So this patch reduces the default runtime for inconsistentcy-check
>> and set-timer-lat,
On 03/26/15 17:07, Vitaly Kuznetsov wrote:
> ... and simplify alloc_balloon_pages() interface by removing redundant
> alloc_error from it.
>
> If we happen to enter balloon_up() with balloon_wrk.num_pages = 0 we will
> enter
> infinite 'while (!done)' loop as alloc_balloon_pages() will be always
On Thu, Mar 26, 2015 at 7:22 AM, Peter Zijlstra wrote:
>
> So we can either just remove the READ_ONCE(), or replace it with a
> leading barrier() call just to be on the paranoid side of things.
NOOO!
> Any preferences?
Not a preference: a _requirement_.
Get rid of the f*cking size checks etc
On Thu, 2015-03-26 at 13:40 +0100, Mason wrote:
> On 25/03/2015 19:01, Joe Perches wrote:
> > On Wed, 2015-03-25 at 18:56 +0100, Mason wrote:
> >
> >> AFAIU, functions only used at system init are tagged __init to have
> >> the linker store them in a separate .init.text section, so memory can
> >>
On 03/26/2015 12:55 AM, Andrew Morton wrote:
> On Tue, 24 Mar 2015 16:10:01 -0700 (PDT) David Rientjes
> wrote:
>
>> Elements backed by the slab allocator are poisoned when added to a
>> mempool's reserved pool.
>>
>> It is also possible to poison elements backed by the page allocator
>>
On 03/26/2015 06:02 PM, Dan Williams wrote:
> On Thu, Mar 26, 2015 at 8:49 AM, Boaz Harrosh wrote:
>> On 03/26/2015 11:34 AM, Christoph Hellwig wrote:
>>> +/*
>>> + * This is a non-standardized way to represent ADR or NVDIMM regions that
>>> + * persist over a reboot. The kernel will ignore
... and simplify alloc_balloon_pages() interface by removing redundant
alloc_error from it.
If we happen to enter balloon_up() with balloon_wrk.num_pages = 0 we will enter
infinite 'while (!done)' loop as alloc_balloon_pages() will be always returning
0 and not setting alloc_error. We will also
On Thu 26-03-15 11:17:46, Johannes Weiner wrote:
> On Thu, Mar 26, 2015 at 02:31:11PM +0100, Michal Hocko wrote:
[...]
> > > @@ -795,27 +728,21 @@ bool out_of_memory(struct zonelist *zonelist, gfp_t
> > > gfp_mask,
> > > */
> > > void pagefault_out_of_memory(void)
> > > {
> > > - struct
Hi, Doug
Thanks for the excellent comments :-)
On 03/26/2015 03:09 PM, Doug Ledford wrote:
> On Wed, 2015-03-25 at 16:09 +0100, Michael Wang wrote:
>> [snip]
>>
> [snip]
>
> So, I would suggest that we fix things up thusly:
>
> enum transport {
> TRANSPORT_IB=1,
> TRANSPORT_IWARP=2,
On Thu, Mar 26, 2015 at 04:02:08PM +0100, Daniel Wagner wrote:
> @@ -67,9 +67,9 @@ void lg_global_lock(struct lglock *lg)
> preempt_disable();
> lock_acquire_exclusive(>lock_dep_map, 0, 0, NULL, _RET_IP_);
> for_each_possible_cpu(i) {
> - arch_spinlock_t *lock;
> +
On Thu, Mar 26, 2015 at 8:49 AM, Boaz Harrosh wrote:
> On 03/26/2015 11:34 AM, Christoph Hellwig wrote:
>> +/*
>> + * This is a non-standardized way to represent ADR or NVDIMM regions that
>> + * persist over a reboot. The kernel will ignore their special capabilities
>> + * unless the
On Thu, Mar 26, 2015 at 7:52 AM, Boaz Harrosh wrote:
> On 03/26/2015 04:12 PM, Dan Williams wrote:
>> On Thu, Mar 26, 2015 at 1:32 AM, Christoph Hellwig wrote:
>>> From: Ross Zwisler
>>>
>
> Dan something is Broken with you mailer program it keeps dropping the
> CC when sending replies.
>
> For
On Wed 25-03-15 02:17:12, Johannes Weiner wrote:
> There is not much point in rushing back to the freelists and burning
> CPU cycles in direct reclaim when somebody else is in the process of
> OOM killing, or right after issuing a kill ourselves, because it could
> take some time for the OOM
The .get_trend callback in struct thermal_zone_device_ops has the prototype:
int (*get_trend) (struct thermal_zone_device *, int,
enum thermal_trend *);
whereas the .get_trend callback in struct thermal_zone_of_device_ops has:
int (*get_trend)(void *,
Signed-off-by: Sascha Hauer
---
drivers/thermal/thermal_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
index 0e4ad7c..c735ac4c 100644
--- a/drivers/thermal/thermal_core.c
+++
Now that the thermal core treats -ENOSYS like the callbacks were
not present at all we no longer have to overwrite the ops during
runtime but instead can always set them and return -ENOSYS if no
sensor is registered.
Signed-off-by: Sascha Hauer
---
drivers/thermal/of-thermal.c | 18
Now that the of thermal support no longer changes the
thermal_zone_device_ops it can be const again.
Signed-off-by: Sascha Hauer
---
drivers/thermal/thermal_core.c | 2 +-
include/linux/thermal.h| 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git
The thermal framework uses int, long and unsigned long for temperatures
in millicelsius. The majority of functions uses unsigned long, so change
the remaining functions to use this type aswell.
Signed-off-by: Sascha Hauer
---
drivers/thermal/thermal_core.c | 10 +-
When the thermal zone has no get_temp callback then
thermal_zone_device_register()
calls thermal_zone_device_set_polling() with a polling delay of 0. This
only cancels the poll_queue. Since the poll_queue hasn't been scheduled this
is a no-op. Remove it.
Signed-off-by: Sascha Hauer
---
This adds support for hardware-tracked trip points to the device tree
thermal sensor framework.
The framework supports an arbitrary number of trip points. Whenever
the current temperature is updated, the trip points immediately
below and above the current temperature are found. A .set_trips
Signed-off-by: Sascha Hauer
---
drivers/thermal/of-thermal.c | 12
include/linux/thermal.h | 1 +
2 files changed, 13 insertions(+)
diff --git a/drivers/thermal/of-thermal.c b/drivers/thermal/of-thermal.c
index 9b63193..a3de5de 100644
--- a/drivers/thermal/of-thermal.c
+++
The thermal core uses the existence of the .get_temp, .get_trend and
.set_emul_temp to detect whether this operation exists and should be
used or whether it should be emulated in software. This makes problems
for of-thermal which has to modify the struct thermal_zone_device_ops
during runtime
This series adds support for hardware trip points. It picks up earlier
work from Mikko Perttunen. Mikko implemented hardware trip points as part
of the device tree support. It was suggested back then to move the
functionality to the thermal core instead of putting more code into the
device tree
In the thermal framework it was decided that temperatures can't
be negative, so let the .get_temp callback in struct
thermal_zone_of_device_ops take an unsigned long pointer for
the temperature like the .get_temp callback in
struct thermal_zone_device_ops does.
Signed-off-by: Sascha Hauer
---
commit e6e238c38 (thermal: sysfs: Add a new sysfs node emul_temp for
thermal emulation) promised not to emulate critical temperatures,
but the check for critical temperatures is broken in multiple ways:
- The code should only accept an emulated temperature when the emulated
temperature is
Now that we no longer modify the ops they can be const again. Also
we no longer have to duplicate them.
Signed-off-by: Sascha Hauer
---
drivers/thermal/of-thermal.c | 18 +++---
1 file changed, 3 insertions(+), 15 deletions(-)
diff --git a/drivers/thermal/of-thermal.c
Inline update_temperature into its only caller to make the code
more readable.
Signed-off-by: Sascha Hauer
---
drivers/thermal/thermal_core.c | 16 +---
1 file changed, 5 insertions(+), 11 deletions(-)
diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
Hi Mark,
On Thu, Mar 26, 2015 at 10:58:15AM -0400, Mark Hounschell wrote:
> Sorry but CMA was still badly broken. I have a patch below that works.
In which way is it broken? What happens when you try to allocate memory
with dma_alloc_coherent?
> I've tested it with small (no CMA) and large
301 - 400 of 1610 matches
Mail list logo
