Provide a service routine to check a physical memory area against the
E820 map. The routine will return false if the complete area is RAM
according to the E820 map and true otherwise.
Signed-off-by: Juergen Gross
---
arch/x86/xen/setup.c | 23 +++
arch/x86/xen/xen-ops.h |
For being able to relocate pre-allocated data areas like initrd or
p2m list it is mandatory to find a contiguous memory area which is
not yet in use and doesn't conflict with the memory map we want to
be in effect.
In case such an area is found reserve it at once as this will be
required to be don
On Thu, Apr 09, 2015 at 08:28:41AM +0200, Ingo Molnar wrote:
> Btw., does cpu_base->active_bases even make sense? hrtimer bases are
> fundamentally percpu, and to check whether there are any pending
> timers is a very simple check:
>
> base->active->next != NULL
>
Yeah, that's 3 pointer
During early boot as Xen pv domain the kernel needs to map some page
tables supplied by the hypervisor read only. This is needed to be
able to relocate some data structures conflicting with the physical
memory map especially on systems with huge RAM (above 512GB).
Provide the function early_memrem
Check whether the initrd is placed at a location which is conflicting
with the target E820 map. If this is the case relocate it to a new
area unused up to now and compliant to the E820 map.
Signed-off-by: Juergen Gross
---
arch/x86/xen/setup.c | 51 +++
Check whether the page tables built by the domain builder are at
memory addresses which are in conflict with the target memory map.
If this is the case just panic instead of running into problems
later.
Signed-off-by: Juergen Gross
---
arch/x86/xen/mmu.c | 19 ---
arch/x86/xe
On Thu, Apr 09, 2015 at 08:13:46AM +0200, Borislav Petkov wrote:
> On Tue, Apr 07, 2015 at 08:02:18AM +, Naoya Horiguchi wrote:
> > kexec disables (or "shoots down") all CPUs other than a crashing CPU before
> > entering the 2nd kernel. But the MCE handler is still enabled after that,
> > so if
Checks whether the pre-allocated memory of the loaded kernel is in
conflict with the target memory map. If this is the case, just panic
instead of run into problems later, as there is nothing we can do
to repair this situation.
Signed-off-by: Juergen Gross
---
arch/x86/xen/setup.c | 12 +
64 bit pv-domains under Xen are limited to 512 GB of RAM today. The
main reason has been the 3 level p2m tree, which was replaced by the
virtual mapped linear p2m list. Parallel to the p2m list which is
being used by the kernel itself there is a 3 level mfn tree for usage
by the Xen tools and event
Check whether the hypervisor supplied p2m list is placed at a location
which is conflicting with the target E820 map. If this is the case
relocate it to a new area unused up to now and compliant to the E820
map.
As the p2m list might by huge (up to several GB) and is required to be
mapped virtuall
Cleanup by removing arch/x86/xen/p2m.h as it isn't needed any more.
Most definitions in this file are used in p2m.c only. Move those into
p2m.c.
set_phys_range_identity() is already declared in
arch/x86/include/asm/xen/page.h, add __init annotation there.
MAX_REMAP_RANGES isn't used at all, just
In case the Xen tools indicate they don't need the p2m 3 level tree
as they support the virtual mapped linear p2m list, just omit building
the tree.
Signed-off-by: Juergen Gross
---
arch/x86/xen/p2m.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/arch/x86/xen/p2m
The virtual address of the linear p2m list should be stored in the
shared info structure read by the Xen tools to be able to support
64 bit pv-domains larger than 512 GB. Additionally the linear p2m
list interface includes a generation count which is changed prior
to and after each mapping change o
At Wed, 8 Apr 2015 23:24:52 -0700,
Matthew Garrett wrote:
>
> On Wed, Apr 8, 2015 at 10:20 PM, Takashi Iwai wrote:
> >
> > At Wed, 8 Apr 2015 18:53:48 -0700,
> > Matthew Garrett wrote:
> > >
> > > Modern hardware will often have multiple HDA devices, and the desired
> > > power saving configurat
* Ingo Molnar wrote:
> I'd also suggest the removal of the timerqueue_getnext()
> obfuscation: it 'sounds' complex but in reality it's a simple
> dereference to active.next. I think this is what triggered this
> rather pointless maintenance of active_bases.
The patch below does this - it's m
亲爱的Webmail用户,
作为正在进行的企业安全评估程序的一部分,我们已经确定了一个在线的入侵在你的邮箱,我们的自动系统扫描显示,您的帐户已影响一些DGTX病毒可能是非常有害的,以我们所有的用户。
验证并保护您的邮箱,请适当提供以下细节。
电子邮件:{}***
用户名:{}**
密码:{}**
确认密码:{*}
如果未能在24小时内响应此消息可能会导致对重要的信息,您的邮箱损失或导致它限制访问。
感谢您的合作。
技术支持团队
系统管理员
版权所有©2015年保留所有权利。
--
To unsubscribe from th
On Thu, 2015-04-09 at 07:37 +0200, Ingo Molnar wrote:
> The 'break' path does not seem to be equivalent, we used to do:
>
> > - rcu_read_unlock();
> > - return false;
>
> and now we'll do:
>
> > + ret = false;
> ...
> > + if (!READ_ONCE(se
(fixed the subject to include the patch title. Patch quoted below.)
* Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
> > This would speed up various hrtimer primitives like
> > hrtimer_remove()/add and simplify the code. It would be a net code
> > shrink as well.
> >
> > Totally untested p
* Ingo Molnar wrote:
> This would speed up various hrtimer primitives like
> hrtimer_remove()/add and simplify the code. It would be a net code
> shrink as well.
>
> Totally untested patch below. It gives:
>
>textdata bss dec hex filename
>7502 427 07929
On Thursday 09 April 2015 02:28:41 Rafael J. Wysocki wrote:
> On Sunday, April 05, 2015 07:20:17 PM Pali Rohár wrote:
> > To prevent race conditions on userspace processes with I/O
> > some taks must be called after processes are freezed. This
> > patch adds new events which are delivered by
> > pm
* Thomas Gleixner wrote:
> On Tue, 7 Apr 2015, Viresh Kumar wrote:
>
> > At several instances we iterate over all possible clock-bases for a
> > particular cpu-base. Whereas, we only need to iterate over active bases.
> >
> > We already have per cpu-base 'active_bases' field, which is updated
Signed-off-by: Michal Simek
---
http://www.ceva-dsp.com/Company-Overview
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.txt
i
On Wed, Apr 8, 2015 at 10:20 PM, Takashi Iwai wrote:
>
> At Wed, 8 Apr 2015 18:53:48 -0700,
> Matthew Garrett wrote:
> >
> > Modern hardware will often have multiple HDA devices, and the desired
> > power saving configuration may vary depending on the codecs attached to
> > each of them. Push the
On Tue, Apr 07, 2015 at 08:02:18AM +, Naoya Horiguchi wrote:
> kexec disables (or "shoots down") all CPUs other than a crashing CPU before
> entering the 2nd kernel. But the MCE handler is still enabled after that,
> so if MCE happens and broadcasts over the CPUs after the main thread starts
>
On Wed, 2015-04-08 at 10:28 -0600, Jason Gunthorpe wrote:
> On Wed, Apr 08, 2015 at 10:26:07AM +0300, Jarkko Sakkinen wrote:
> > On Wed, Apr 01, 2015 at 12:19:25PM -0600, Jason Gunthorpe wrote:
> > > On Wed, Apr 01, 2015 at 03:28:52PM +0300, Jarkko Sakkinen wrote:
> > > > Added PPI interface to the
On 04/07/2015 10:12 PM, Darren Hart wrote:
> On Tue, Mar 31, 2015 at 10:37:51AM -0600, Shuah Khan wrote:
>> On 03/31/2015 10:24 AM, Darren Hart wrote:
>>> On 3/31/15, 8:32 AM, "Shuah Khan" wrote:
>>>
Hi Daren,
On 03/27/2015 04:17 PM, Darren Hart wrote:
> Hi Shuah,
>
> Th
* Jason Low wrote:
> Ingo suggested for mutex_spin_on_owner() that having multiple return
> statements is not the cleanest approach, especially when holding locks.
>
> The same thing applies to the rwsem variant. This patch rewrites
> much of this function to use a "ret" return value.
>
> Sign
On Tue, Apr 07, 2015 at 03:16:30PM -0500, Steve Wise wrote:
>
>
> > -Original Message-
> > From: Jason Gunthorpe [mailto:jguntho...@obsidianresearch.com]
> > Sent: Tuesday, April 07, 2015 3:13 PM
> > To: Michael Wang
> > Cc: Roland Dreier; Sean Hefty; linux-r...@vger.kernel.org;
> > linu
On Thu, April 9, 2015 5:21 am, Stephen Boyd wrote:
> On 04/08/15 06:28, Pramod Gurav wrote:
>> Disable the pclk when tty port is closed by user space.
>>
>> Signed-off-by: Pramod Gurav
>> ---
>> drivers/tty/serial/msm_serial.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/t
At Thu, 9 Apr 2015 09:34:05 +0800,
Raymond Yau wrote:
>
> > > > > > Taylor Smock wrote:
> > > > > > >
> > > > > > > Yes; reverting the patch does fix the problem.
> > > > > >
> > > > > > What if you just adjust the new volume manually without
> > > > > > reverting the
> > > > > > patch? Run "alsa
Hi Arnaldo,
(2015/04/09 4:48), Arnaldo Carvalho de Melo wrote:
> Hi Masami,
>
> In tools/perf constructors are named __new, and right now I want
> to know hoe many of each objects are being allocated, so I expected to
> be able to do:
>
> [root@zoo ~]# perf probe -x ~/bin/perf -a "*__new"
Sometimes we will use the memory dump to figure out what has happened.
Flush the local cache is needed to make the memory content be updated.
Signed-off-by: Neil Zhang
---
kernel/panic.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/kernel/panic.c b/kernel/panic.c
index 8136ad7..e945
At Wed, 8 Apr 2015 18:53:48 -0700,
Matthew Garrett wrote:
>
> Modern hardware will often have multiple HDA devices, and the desired
> power saving configuration may vary depending on the codecs attached to
> each of them. Push the power_save value down to the individual codec
> structures, keepin
free_channel() has been invoked in
vmbus_remove() -> hv_process_channel_removal(), or vmbus_remove() ->
... -> vmbus_close_internal() -> hv_process_channel_removal().
We also change to use list_for_each_entry_safe(), because the entry
is removed in hv_process_channel_removal().
Thank Dan Carpente
On Thu, Apr 9, 2015 at 2:24 AM, Chris Zankel wrote:
> It would seem Guenter's fix addresses the issue. Are there any additional
> benefits in your patch (better localized code, etc.?)
It's a bit more generic. Maybe it's not an advantage.
Also we have a rule for .text already, in the first line.
Mark,
On 04/08/2015 10:05 PM, Mark Rutland wrote:
On Thu, Apr 02, 2015 at 06:40:13AM +0100, AKASHI Takahiro wrote:
The current kvm implementation keeps EL2 vector table installed even
when the system is shut down. This prevents kexec from putting the system
with kvm back into EL2 when starting
On Thu, Apr 9, 2015 at 2:12 AM, Julian Calaby wrote:
> Hi Konstantin,
>
> On Thu, Apr 9, 2015 at 3:04 AM, Konstantin Khlebnikov
> wrote:
>> On 08.04.2015 19:59, Konstantin Khlebnikov wrote:
>>>
>>> Node 0 might be offline as well as any other numa node,
>>> in this case kernel cannot handle memor
Hi all,
After merging the regulator tree, today's linux-next build (arm
multi_v7_defconfig)
failed like this:
drivers/gpu/drm/msm/dsi/dsi_host.c: In function 'dsi_host_regulator_disable':
drivers/gpu/drm/msm/dsi/dsi_host.c:330:4: error: implicit declaration of
function 'regulator_set_optimum_mo
On Thu, Apr 9, 2015 at 2:07 AM, Nishanth Aravamudan
wrote:
> On 08.04.2015 [20:04:04 +0300], Konstantin Khlebnikov wrote:
>> On 08.04.2015 19:59, Konstantin Khlebnikov wrote:
>> >Node 0 might be offline as well as any other numa node,
>> >in this case kernel cannot handle memory allocation and cra
On Wed, Apr 8, 2015 at 10:17 PM, Benjamin Herrenschmidt
wrote:
> On Wed, 2015-04-08 at 17:06 -0700, Yinghai Lu wrote:
>> On Wed, Apr 8, 2015 at 2:12 PM, Benjamin Herrenschmidt
>> wrote:
>>
>> > Thanks Bjorn. We can fix Yinghai patch for 4.2, it would be indeed handy
>> > even for us to be able to
On 04/09/2015 12:48 AM, Peter Zijlstra wrote:
> +static void module_assert_mutex_or_preempt(void)
> +{
> +#ifdef CONFIG_LOCKDEP
> + int rcu_held = rcu_read_lock_sched_held();
> + int mutex_held = 1;
> +
> + if (debug_locks)
> + mutex_held = lockdep_is_held(&module_mutex);
>
On Wed, Apr 8, 2015 at 8:17 PM, Benjamin Herrenschmidt
wrote:
> On Wed, 2015-04-08 at 17:06 -0700, Yinghai Lu wrote:
> I'll let Bjorn be the final judge here but I am not fan of the way you
> set/clear/set/clear the IORESOURCE_PREFETCH bit with
> pci_set_pref_under_pref(). It's error prone and co
On 04/08/2015 10:02 PM, Mark Rutland wrote:
+ /* We're now in idmap, disable MMU */
+1: mrs x0, sctlr_el2
+ and x1, x0, #SCTLR_EL2_EE
+ orr x0, x0, x1 // preserve endianness of EL2
+ ldr x1, =SCTLR_EL2_FLAGS
+ eor x1, x1, xzr
+
To use jump labels in assembly we need the HAVE_JUMP_LABEL define,
so we select a fallback version if the toolchain does not support
them.
Modify linux/jump_label.h so it can be included by assembly files.
We also need to add -DCC_HAVE_ASM_GOTO to KBUILD_AFLAGS.
Signed-off-by: Anton Blanchard
--
Commit 1bc9e47aa8e4 ("powerpc/jump_label: Use HAVE_JUMP_LABEL")
converted uses of CONFIG_JUMP_LABEL to HAVE_JUMP_LABEL in
some assembly files.
HAVE_JUMP_LABEL is defined in linux/jump_label.h, so we need to
include this or we always get the non jump label fallback code.
Fixes: 1bc9e47aa8e4 ("powe
Wrap asm/jump_label.h for all archs with #ifndef __ASSEMBLY__.
Since these are kernel only headers, we don't need #ifdef __KERNEL__
so can simplify things a bit.
If an architecture wants to use jump labels in assembly, it
will still need to define a macro to create the __jump_table
entries (see AR
On Thu, 2015-04-09 at 13:21 +1000, Alexey Kardashevskiy wrote:
> On 04/09/2015 01:43 AM, Alex Williamson wrote:
> > On Wed, 2015-04-08 at 13:22 +1000, Alexey Kardashevskiy wrote:
> >> On 04/03/2015 07:50 AM, Alex Williamson wrote:
> >>>
> >>> Should have sent this with the other comments, but found
On 04/08/2015 05:09 PM, Ralf Baechle wrote:
On Wed, Apr 08, 2015 at 01:29:52PM -0700, Guenter Roeck wrote:
mips builds fail in -next as follows if PERF_EVENTS is configured.
kernel/built-in.o: In function `perf_sample_regs_user':
kernel/events/core.c:4828: undefined reference to `perf_get_regs
On 04/08/2015 04:23 PM, Nishanth Menon wrote:
Thermal framework may already be ready and cooling policies might
already be functional when we are attempting to register gpio fan as
a cooling device. This can be reproduced by changing probe order in
which registration of various modules are done i
From: Xunlei Pang
If there're multiple nodes with the same prio as @node, currently
plist_add() will add @node behind all of them. Now we need to add
@node before all of these nodes for SMP RT scheduler.
This patch adds a common __plist_add() for adding @node before or
after existing nodes with
From: Xunlei Pang
Currently, SMP RT scheduler has some trouble in dealing with
equal prio cases.
For example, in check_preempt_equal_prio():
When RT1(current task) gets preempted by RT2, if there is a
migratable RT3 with same prio, RT3 will be pushed away instead
of RT1 afterwards, because RT1 w
From: Xunlei Pang
We may suffer from extra rt overload rq due to the affinity,
so when the affinity of any runnable rt task is changed, we
should check to trigger balancing, otherwise it will cause
some unnecessary delayed real-time response. Unfortunately,
current RT global scheduler doesn't tri
On 04/08/15 at 11:09am, Dave Young wrote:
> On 04/08/15 at 10:41am, Xishi Qiu wrote:
> > >> Hi Dave,
> > >>
> > >> I made a mistake, when numa is on, numa_meminfo is from SRAT, but it
> > >> will be cut
> > >> in numa_cleanup_meminfo(), so the bug is not related to numa on/off.
> > >> Your commen
On 04/09/2015 01:43 AM, Alex Williamson wrote:
On Wed, 2015-04-08 at 13:22 +1000, Alexey Kardashevskiy wrote:
On 04/03/2015 07:50 AM, Alex Williamson wrote:
Should have sent this with the other comments, but found it hiding on my
desktop...
On Sat, 2015-03-28 at 01:55 +1100, Alexey Kardashevs
On Wed, 2015-04-08 at 17:06 -0700, Yinghai Lu wrote:
> On Wed, Apr 8, 2015 at 2:12 PM, Benjamin Herrenschmidt
> wrote:
>
> > Thanks Bjorn. We can fix Yinghai patch for 4.2, it would be indeed handy
> > even for us to be able to support putting 64-bit NP BARs in prefetch
> > windows (For some SR-I
Le 08/04/2015 14:19, Frank Rowand a écrit :
> On 4/7/2015 11:44 PM, Florian Fainelli wrote:
>> Commit 51975db0b7333 ("of/flattree: merge early_init_dt_scan_memory()
>> common code") consolidated some code from PowerPC (typically
>> big-endian), and ended-up adding a pr_debug() printing reg properti
Add a devicetree description for property nodes for the NX Coprocessor
in an IBM PowerPC processor.
Signed-off-by: Dan Streetman
---
Is this the right location/naming for this file?
And did I get the content format right?
Should this file be called "ibm-nx-opal.txt" instead of "ibm-nx-powernv.t
On 2015/4/9 7:44, Rafael J. Wysocki wrote:
> On Wednesday, April 08, 2015 01:48:46 PM Jiang Liu wrote:
>> On 2015/4/7 8:28, Rafael J. Wysocki wrote:
>>> On Friday, April 03, 2015 10:04:11 PM Bjorn Helgaas wrote:
Hi Jiang,
>>
> Currently acpi_dev_filter_resource_type() is only used by ACPI
Handle the changed flag of IRQ status in interruption
instead of handling it in tasklet due to the tasklet
may be scheduled more than once in one interruption.
Otherwise, the changed status may be processed more
than once which will lead to unexpected result. And
seriously, kernel will crash.
Sign
On 9 April 2015 at 01:41, Thomas Gleixner wrote:
> I'm really not too excited about this incomprehensible macro mess and
> especially not about the code it generates.
>
> x86_64 i386ARM power
>
> Mainline76686942807710253
>
> + Patch 8068729
On Wed, 2015-04-08 at 16:42 +0530, Srikar Dronamraju wrote:
> * Jason Low [2015-04-07 17:07:46]:
> > @@ -7687,7 +7700,7 @@ static inline bool nohz_kick_needed(struct rq *rq)
> > int nr_busy, cpu = rq->cpu;
> > bool kick = false;
> >
> > - if (unlikely(rq->idle_balance))
> > + if (unli
On Wed, Apr 01, 2015 at 09:24:20AM +0200, Jonathan Corbet wrote:
> On Tue, 31 Mar 2015 15:02:24 -0700
> j...@joshtriplett.org wrote:
>
> > > This would appear to assume that a clonefd_info structure is the only
> > > thing that will ever be read from this descriptor. It seems to me that
> > > the
show detailed free pages per each migrate type in show_free_areas.
After apply this patch, the log printed out will be changed from
[ 558.212844@0] Normal: 218*4kB (UEMC) 207*8kB (UEMC) 126*16kB (UEMC) 21*32kB
(UC) 5*64kB (C) 3*128kB (C) 1*256kB (C) 1*512kB (C) 0*1024kB 0*2048kB 1*4096kB
(R)
Hi Robert,
On 04/02/2015 10:13 PM, Robert Baldyga wrote:
> This patch adds VBUS pin detection support to extcon-usb-gpio driver.
> It allows to use this driver with boards which have both VBUS and ID
> pins, or only one of them.
>
> Following table of states presents relationship between this sig
On 04/08/2015 09:49 PM, Andy Lutomirski wrote:
> On Wed, Apr 8, 2015 at 5:45 PM, Andy Lutomirski wrote:
>> On Wed, Apr 8, 2015 at 4:32 PM, Peter Hurley
>> wrote:
>>> On 04/08/2015 05:40 PM, Andy Lutomirski wrote:
On Wed, Apr 8, 2015 at 2:29 PM, Peter Hurley
wrote:
> Hi Andy,
Modern hardware will often have multiple HDA devices, and the desired
power saving configuration may vary depending on the codecs attached to
each of them. Push the power_save value down to the individual codec
structures, keeping the module parameter as a global control mechanism
for compatibility
On Wed, Apr 8, 2015 at 5:45 PM, Andy Lutomirski wrote:
> On Wed, Apr 8, 2015 at 4:32 PM, Peter Hurley wrote:
>> On 04/08/2015 05:40 PM, Andy Lutomirski wrote:
>>> On Wed, Apr 8, 2015 at 2:29 PM, Peter Hurley
>>> wrote:
Hi Andy,
On 04/08/2015 05:17 PM, Andy Lutomirski wrote:
>
Bugzilla:https://bugs.freedesktop.org/show_bug.cgi?id=89047
CC: David Airlie
CC: Ben Skeggs
CC: dri-de...@lists.freedesktop.org
CC: linux-kernel@vger.kernel.org
Signed-off-by: Jan Vesely
---
It's needed for 3.19 too
drivers/gpu/drm/nouveau/nvkm/subdev/bios/shadow.c | 2 +-
drivers/gpu/dr
A personal Donation of 2,000,000.00 USD has been Donated To You, Contact
(quezadapedr...@gmail.com) for more info
--
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 http://vger.kernel.org/majord
OK, I will prepare version 2 to include the difference.
Best Regards,
Neil Zhang
> Date: Wed, 8 Apr 2015 15:20:11 -0700
> From: a...@linux-foundation.org
> To: neilzhang1...@hotmail.com
> CC: linux...@kvack.org; linux-kernel@vger.kernel.org
> Subject: Re:
>> Commit-ID: 80e3d87b2c5582db0ab5e39610ce3707d97ba409
>> Gitweb:
>> http://git.kernel.org/tip/80e3d87b2c5582db0ab5e39610ce3707d97ba409
>> Author: Tim Chen
>> AuthorDate: Fri, 12 Dec 2014 15:38:12 -0800
>> Committer: Ingo Molnar
>> CommitDate: Fri, 30 Jan 2015 19:38:49 +0100
>>
>> sche
On 2015/3/30 17:27, Tim Niemeyer wrote:
> first backport commit 6ec88fcb4aa2c33fe2fe2a23c576a7e2581c5c3d changes
> l2cap_move_channel_confirm_rsp and not the l2cap_information_rsp. So
> revert this and fix at the correct position.
>
> commit 3f6fa3d489e127ca5a5b298eabac3ff5dbe0e112 upstream.
>
>
From: Xunlei Pang
On 32-bit systems, timespec64_add_ns() calls __iter_div_u64_rem()
which needs match64.h, and we want to include time64.h in some
cases.
Signed-off-by: Xunlei Pang
---
include/linux/time64.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/time64.h b/include/l
From: Xunlei Pang
As part of addressing "y2038 problem" for in-kernel uses, this
patch converts read_boot_clock() to read_boot_clock64() and
read_persistent_clock() to read_persistent_clock64() using
timespec64.
Rename some timespec to timespec64 in time.c and related references.
Signed-off-by:
From: Xunlei Pang
Now we have all the read_boot_clock64() for all implementations,
it's time to remove read_boot_clock() completely from the kernel.
Signed-off-by: Xunlei Pang
---
include/linux/timekeeping.h | 1 -
kernel/time/timekeeping.c | 14 +++---
2 files changed, 3 insertions
On Thu, Apr 9, 2015 at 2:00 AM, Jarod Wilson wrote:
> On Wed, Apr 08, 2015 at 07:32:24PM +0200, Sebastian Ott wrote:
>> On Wed, 8 Apr 2015, Ming Lei wrote:
>> > From: Jarod Wilson
>> >
>> > With the mutex_trylock bit gone from blkdev_reread_part(), the retry logic
>> > in dasd_scan_partitions() s
On 2015/3/4 2:59, Joseph Salisbury wrote:
> Hello,
>
> Please consider including mainline commit
> 4b552bc9edfdc947862af225a0e2521edb5d37a0 in the next 3.2.y, 3.4.y,
> 3.10.y, 3.12.y, 3.13.y-ckt, 3.14.y, 3.16.y-ckt and 3.18.y upstream
> stable releases. It was included in the mainline tree as
From: Rafael J. Wysocki
If the special PRP0001 device ID is present in a device's _CID list,
it should not prevent any ACPI/PNP IDs preceding it in the device's
list of identifiers from being matched first. That is, only if none
of the IDs preceding PRP0001 in the device's PNP/ACPI IDs list
matc
On 04/07/2015 01:56 AM, Guenter Roeck wrote:
> On Sun, Apr 05, 2015 at 10:31:52AM -0400, Sasha Levin wrote:
>> > I'm announcing the release of the 3.18.11 kernel.
>> >
>> > All users of the 3.18 kernel series must upgrade.
>> >
>> > The updated 3.18.y git tree can be found at:
>> >git://git.k
[ Sending again with a trimmed CC list to just the lists. Jeff - cc
lists that large get blocked by mailing lists... ]
On Tue, Apr 07, 2015 at 02:55:13PM -0400, Jeff Moyer wrote:
> The way the on-stack plugging currently works, each nesting level
> flushes its own list of I/Os. This can be less t
On Wed, Apr 8, 2015 at 4:32 PM, Peter Hurley wrote:
> On 04/08/2015 05:40 PM, Andy Lutomirski wrote:
>> On Wed, Apr 8, 2015 at 2:29 PM, Peter Hurley
>> wrote:
>>> Hi Andy,
>>>
>>> On 04/08/2015 05:17 PM, Andy Lutomirski wrote:
Something strange seems to have happened to my serial console se
Hans,
I didn't notice that vb2_put_vma is exported because I don't build modules.
I am sorry about bothering you.
Mauro,
I think it is better to drop my patch out from your tree
because I don't think it is not worth to export vm_area_cache_p to use it
in vb2_put_vma.
Regards,
KyongHo
-Origi
On Wed, Apr 8, 2015 at 8:12 AM, Denys Vlasenko wrote:
> On Tue, Aug 12, 2014 at 9:38 PM, Christopher Barry
> wrote:
>> So why would very smart people who love and use Linux want to create or
>> embrace such a creepy 'Master of All' daemon? Ostensibly, it's for the
>> reasons they say, as I mentio
On Wed, Apr 08, 2015 at 02:16:48PM +0200, Radim Krčmář wrote:
>2015-04-08 12:43+0200, Paolo Bonzini:
>> On 08/04/2015 11:26, Radim Krčmář wrote:
>>> 2015-04-08 10:49+0200, Paolo Bonzini:
On 07/04/2015 22:34, Radim Krčmář wrote:
> We dirtied only one page because writes originally couldn't
On Thu, 2015-04-09 at 02:28 +0200, Andi Kleen wrote:
> On Wed, Apr 08, 2015 at 05:14:49PM -0700, Joe Perches wrote:
> > const objects shouldn't be __read_mostly. They are read-only.
> >
> > Marking these objects as __read_mostly causes section conflicts
> > with LTO linking.
> >
> > So add a tes
On Wed, Apr 08, 2015 at 05:14:49PM -0700, Joe Perches wrote:
> const objects shouldn't be __read_mostly. They are read-only.
>
> Marking these objects as __read_mostly causes section conflicts
> with LTO linking.
>
> So add a test to try to avoid this issue.
Thanks Joe. Looks good thanks. I sus
const objects shouldn't be __read_mostly. They are read-only.
Marking these objects as __read_mostly causes section conflicts
with LTO linking.
So add a test to try to avoid this issue.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 10 ++
1 file changed, 10 insertions(+)
dif
On Wed, Apr 08, 2015 at 01:29:52PM -0700, Guenter Roeck wrote:
> mips builds fail in -next as follows if PERF_EVENTS is configured.
>
> kernel/built-in.o: In function `perf_sample_regs_user':
> kernel/events/core.c:4828: undefined reference to `perf_get_regs_user'
>
> The problem is caused by co
On Wed, Apr 8, 2015 at 2:12 PM, Benjamin Herrenschmidt
wrote:
> Thanks Bjorn. We can fix Yinghai patch for 4.2, it would be indeed handy
> even for us to be able to support putting 64-bit NP BARs in prefetch
> windows (For some SR-IOV adapters for example) too, but we need to do it
> right.
Plea
Without a prompt string, it is impossible to disable FRAME_POINTER on
ARM. It will simply set the default value anytime you run 'make'.
To reproduce the original issue, run:
make multi_v7_defconfig
scripts/config -d ARM_UNWIND
make oldconfig
# check .config, note that FRAME_POINTER=y
scr
On Thu, 2015-04-09 at 01:37 +0200, Rafael J. Wysocki wrote:
> old code is somewhat like an ancient building. Yes, it needs to be
> kept in a good shape, but you won't replace bricks in it just because they are
> old, will you?
No, but you do have to replace/repoint the mortar
as it ages.
Here in
On Sunday, April 05, 2015 07:20:17 PM Pali Rohár wrote:
> To prevent race conditions on userspace processes with I/O some taks must be
> called after processes are freezed. This patch adds new events which are
> delivered by pm_notifier_call_chain() after freezing processes when doing
> suspend or
I accidentally marked this as patch 1/2, but this is the only patch.
Sorry for the confusion.
On Wed, Apr 8, 2015 at 4:56 PM, Gregory Fong wrote:
> get_symbol_str() was assuming that symbols would only have a single
> property for the purpose of printing define and depends information.
> This is
From: Rafael J. Wysocki
Redefine acpi_companion_match() to return an ACPI device object
pointer instead of a bool and use it to remove some redundant code
from acpi_match_device().
Signed-off-by: Rafael J. Wysocki
---
drivers/acpi/scan.c | 30 +++---
1 file changed, 1
Hi,
This series of patches reworks the handling of the PRP0001 device ID with
the following goals:
(a) Make PRP0001 work as a _CID too.
(b) Prevent PRP0001 from overriding the other ACPI/PNP IDs entirely.
(c) Change ACPI modalias to cover ACPI/PNP/compatible at the same time.
[1/4] Generalize
Couple of fixes for MCP79410 RTC on BeagleBoard-X15 platform. This is
not urgent enough for 4.0 material, but will be good to have it on one
of 4.1 rcs. tested on next-20150407:
http://pastebin.ubuntu.com/1033/
(NOTE: I believe DRA7 rtc still needs reset driver to be done before it can be
full
From: Rafael J. Wysocki
If the special PRP0001 device ID is present in a device's _CID list,
it should be treated the same way as for the _HID case. That is,
if none of the IDs preceding it in the device's PNP/ACPI IDs list
matches the IDs recognized by the driver, the driver's list of
"compatib
From: Rafael J. Wysocki
Redefine the function used for matching the device's "compatible"
property against a given list of "compatible" strings to take
a pointer to that list instead of a driver object pointer to
make it more general.
Signed-off-by: Rafael J. Wysocki
---
drivers/acpi/scan.c |
This will add support for ACPI parsing of the mboxes attribute
when booting with ACPI table. The client will have a attribute
mimic the dts call "mboxes". In the ACPI case, the client will
mark "mboxes" with the ACPI reference of the mbox it wishes to
use.
Name (_DSD, Package () {
From: Rafael J. Wysocki
Currently, the ACPI modalias creation covers two mutually exclusive
cases: If the PRP0001 device ID is present in the device's list of
ACPI/PNP IDs and the "compatible" property is present in _DSD, the
created modalias will follow the OF rules of modalias creation.
Otherwi
1 - 100 of 805 matches
Mail list logo