0-
22 0day head guard for 'devel-hourly-2015033101'
# extra tests on tree/branch next/master
git bisect bad e954104e2b634b42811dad8d502cbf240f206df2 # 20:35 0-
1 Add linux-next specific files for 20150401
# extra tests on tree/branch linus/master
git bisect good 6c3
Hi Rafael,
watchdog_active() function is not implemented in your patch. Pls. add it.
static int watchdog_active(struct device *dev)
{
unsigned int val;
spin_lock(&iTCO_wdt_private.io_lock);
val = inw(TCO1_CNT);
spin_unlock(&iTCO_wdt_private.io_lock);
/* Bit 11
A user-space thermal governor does not currently know which trip point
caused a uevent to trigger. Let's add this information to the payload.
This is just an RFC, because this patch (on its own) is not very useful.
The only current caller of the .throttle callback is in
thermal_zone_device_update(
On Wed, 2015-04-01 at 14:03 +0100, Morten Rasmussen wrote:
Hi Morten,
> > Alright I see. But it is one additional wake up. And the wake up will be
> > within the cluster. We will not wake up any CPU in the neighboring
> > cluster unless there are tasks to be pulled. So, we can wake up a core
> >
On Thu, Mar 19, 2015 at 06:14:29PM +0100, Nicolas Ferre wrote:
> Arnd, Olof, Kevin,
>
> This is the real switch to multi-platform for AT91: after all the preparation
> work that has been done, here we are! And there's also an additional cleanup
> on
> top of that...
> I stacked this material on t
uot;
job_file:
"/lkp/scheduled/wsm/boot_boot-performance-1-x86_64-rhel-4a5cba20d58c8acccab671b13c83165be9cba0fb-0-20150401-18244-52f40d.yaml"
dequeue_time: 2015-04-01 13:38:26.975590830 +08:00
nr_cpu: "$(nproc)"
max_uptime: 3600
modules_initrd:
"/kernel/x86_64-rhel/4a5cba20d58c8
On 04/01/2015 03:22 PM, James Hogan wrote:
Hi Andrew,
On Wed, Apr 01, 2015 at 10:43:14AM -0700, Andrew Bresticker wrote:
Since the heartbeat is statically initialized to its default value,
watchdog_init_timeout() will never look in the device-tree for a
timeout-sec value. Instead of statically
On 04/01/2015 05:52 PM, Fu, Borun wrote:
Hi Rafael,
watchdog_active() function is not implemented in your patch. Pls. add it.
Please explain why using the standard watchdog_active() would not work here.
Guenter
static int watchdog_active(struct device *dev)
{
unsigned int val;
On 2015/4/1 21:21, Jiri Olsa wrote:
> On Wed, Apr 01, 2015 at 10:33:14AM +, Wang Nan wrote:
>> This patch introduces a --map-adjustment argument for perf report. The
>> goal of this option is to deal with private dynamic loader used in some
>> special program.
>>
>
> SNIP
>
>> diff --git a/to
On 04/01/2015 05:31 PM, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki
If the target sleep state of the system is not an ACPI sleep state
(S1, S2 or S3), the TCO watchdog needs to be stopped during system
suspend, because it may not be possible to ping it any more after
timekeeping has been s
On 2015/4/1 23:04, Tao Chen wrote:
Define pr_fmt macro with {xen-blkback: } prefix, then remove all use
of DRV_PFX in the pr sentences. Replace all DPRINTK with pr sentences,
and get rid of DPRINTK macro. It will simplify the code.
And if the pr sentences miss a \n, add it in the end. If the D
On 04/01/2015 03:22 PM, James Hogan wrote:
Hi Andrew,
On Wed, Apr 01, 2015 at 10:43:14AM -0700, Andrew Bresticker wrote:
Since the heartbeat is statically initialized to its default value,
watchdog_init_timeout() will never look in the device-tree for a
timeout-sec value. Instead of statically
It is only necessary to raise timer softirq
in case there are active timers or irq work
to do.
Limit the ksoftirqd wakeup to those cases.
Fixes a latency spike with isolated CPUs and
nohz full mode.
Reported-and-tested-by: Luiz Capitulino
Signed-off-by: Marcelo Tosatti
diff --git a/include
On 2015/4/1 13:11, Dave Young wrote:
> Ccing Xishi Qiu who wrote the clear_kernel_node_hotplug code.
>
> On 04/01/15 at 12:53pm, Dave Young wrote:
>> I got below kernel panic during kdump test on Thinkpad T420 laptop:
>>
>> [0.00] No NUMA configuration found
Hi Kame, TJ,
On 04/01/2015 04:30 PM, Kamezawa Hiroyuki wrote:
> On 2015/04/01 12:02, Tejun Heo wrote:
>> On Wed, Apr 01, 2015 at 11:55:11AM +0900, Kamezawa Hiroyuki wrote:
>>> Now, hot-added cpus will have the lowest free cpu id.
>>>
>>> Because of this, in most of systems which has only cpu-hot-
Hi Vincent,
On Fri, Feb 27, 2015 at 04:54:03PM +0100, Vincent Guittot wrote:
>This patchset consolidates several changes in the capacity and the usage
>tracking of the CPU. It provides a frequency invariant metric of the usage of
>CPUs and generally improves the accuracy of load/usage tracking in t
On Mon, Mar 9, 2015 at 1:27 PM, Peter Hurley wrote:
> setup_earlycon() will now match and register the desired earlycon
> from the param string (as if 'earlycon=...' had been set on the
> command line). Use setup_earlycon() from existing arch call sites
> which start an earlycon directly.
>
Hi,
From: "Steven Rostedt (Red Hat)"
New code will require TRACE_SYSTEM to be a valid C variable name,
but some tracepoints have TRACE_SYSTEM with '-' and not '_', so
it can not be used. Instead, add a TRACE_SYSTEM_VAR that can
give the tracing infrastructure a unique name for the trace system.
Cc:
As there are many tracepoints that use __print_symbolic() to translate
numbers into ASCII strings, and several of these translate enums as
well, it causes a problem for user space tools that read the tracepoint
format files and have to translate the binary data to their associated
strings.
For exa
From: "Steven Rostedt (Red Hat)"
Enums used by tracepoints for __print_symbolic() are shown in the
tracepoint format files with just their names and not their values.
This makes it difficult for user space tools to know how to convert the
binary data into their string representations.
By adding
From: "Steven Rostedt (Red Hat)"
Update the infrastructure such that modules that declare TRACE_DEFINE_ENUM()
will have those enums shown in the enum_map files in the tracing directory.
Link: http://lkml.kernel.org/r/87vbhjp74q@rustcorp.com.au
Acked-by: Rusty Russell
Signed-off-by: Steven
From: "Steven Rostedt (Red Hat)"
The enums used in the tracepoints for __print_symbolic() have their
names shown in the tracepoint format files. User space tools do not know
how to convert those names into their values to be able to convert the
binary data.
Use TRACE_DEFINE_ENUM() to export the
From: "Steven Rostedt (Red Hat)"
The enums used in tracepoints for __print_symbolic() do not have their
values shown in the tracepoint format files and this makes it difficult
for user space tools to convert the binary values to the strings they
are to represent.
Add TRACE_DEFINE_ENUM(x) macros
From: "Steven Rostedt (Red Hat)"
Several tracepoints use the helper functions __print_symbolic() or
__print_flags() and pass in enums that do the mapping between the
binary data stored and the value to print. This works well for reading
the ASCII trace files, but when the data is read via userspa
On Tue, 2015-03-31 at 14:07 +0530, Preeti U Murthy wrote:
> On 03/31/2015 12:25 AM, Jason Low wrote:
> > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> > index fdae26e..ba8ec1a 100644
> > --- a/kernel/sched/fair.c
> > +++ b/kernel/sched/fair.c
> > @@ -7644,7 +7644,7 @@ static void nohz_i
From: "Steven Rostedt (Red Hat)"
The tracepoints that use __print_symbolic() use enums as the value
to convert to strings. Unfortunately, the format files for these
tracepoints show the enum name and not their value. This causes some
userspace tools not to know how to convert __print_symbolic() t
From: "Steven Rostedt (Red Hat)"
New code will require TRACE_SYSTEM to be a valid C variable name,
but some tracepoints have TRACE_SYSTEM with '-' and not '_', so
it can not be used. Instead, add a TRACE_SYSTEM_VAR that can
give the tracing infrastructure a unique name for the trace system.
Cc:
From: "Steven Rostedt (Red Hat)"
New code will require TRACE_SYSTEM to be a valid C variable name,
but some tracepoints have TRACE_SYSTEM with '-' and not '_', so
it can not be used. Instead, add a TRACE_SYSTEM_VAR that can
give the tracing infrastructure a unique name for the trace system.
Cc:
From: "Steven Rostedt (Red Hat)"
The enums used in tracepoints with __print_symbolic() have their
names shown in the tracepoint format files and not their values.
This makes it difficult for user space tools to convert the binary
data to the strings as user space does not know what those enums
ar
From: "Steven Rostedt (Red Hat)"
Add documentation about TRACE_SYSTEM needing to be alpha-numeric or with
underscores, and that if it is not, then the use of TRACE_SYSTEM_VAR is
required to make something that is.
An example of this is shown in samples/trace_events/trace-events-sample.h
Signed
From: "Steven Rostedt (Red Hat)"
Document the use of TRACE_DEFINE_ENUM() by adding enums to the
trace-event-sample.h and using this macro to convert them in the format
files.
Also update the comments and sho the use of __print_symbolic() and
__print_flags() as well as adding comments abount __pr
From: "Steven Rostedt (Red Hat)"
The tracepoints in the 9p code use a lot of enums for the __print_symbolic()
function. These enums are shown in the tracepoint format files, and user
space tools such as trace-cmd does not have the information to parse it.
Add helper macros to export the enums wit
From: "Steven Rostedt (Red Hat)"
Add a enum_map file in the tracing directory to see what enums have been
saved to convert in the print fmt files.
Signed-off-by: Steven Rostedt
---
kernel/trace/trace.c | 110 +--
1 file changed, 107 insertions(+)
Sorry, my fault. It should work as well.
-Original Message-
From: Guenter Roeck [mailto:li...@roeck-us.net]
Sent: Thursday, April 02, 2015 9:11
To: Fu, Borun; Rafael J. Wysocki; linux-watch...@vger.kernel.org
Cc: Linux Kernel Mailing List; Linux PM list; Wim Van Sebroeck; Li, Aubrey;
Wa
From: "Steven Rostedt (Red Hat)"
Normally the compiler will use the same pointer for a string throughout
the file. But there's no guarantee of that happening. Later changes will
require that all events have the same pointer to the system string.
Name the system string and have all events point t
From: "Steven Rostedt (Red Hat)"
Have the enums used in __print_symbolic() by the trace_tlb_flush()
tracepoint exported to userpace such that they can be parsed by
userspace tools.
Cc: Dave Hansen
Signed-off-by: Steven Rostedt
---
include/trace/events/tlb.h | 30 +-
From: "Steven Rostedt (Red Hat)"
The enums used by the softirq mapping is what is shown in the output
of the __print_symbolic() and not their values, that are needed
to map them to their strings. Export them to userspace with the
TRACE_DEFINE_ENUM() macro so that user space tools can map the enum
On Tue, Mar 31, 2015 at 11:31:40AM +0530, Kishon Vijay Abraham I wrote:
> On Saturday 28 March 2015 05:58 AM, Brian Norris wrote:
> >On Thu, Mar 26, 2015 at 03:29:44AM +0530, Kishon Vijay Abraham I wrote:
> >>On Thursday 19 March 2015 06:53 AM, Brian Norris wrote:
> >>>+static struct phy *brcm_sata
On 04/02/2015 08:48 AM, Alex Williamson wrote:
On Sat, 2015-03-28 at 01:54 +1100, Alexey Kardashevskiy wrote:
This makes use of the it_page_size from the iommu_table struct
as page size can differ.
This replaces missing IOMMU_PAGE_SHIFT macro in commented debug code
as recently introduced IOMMU
On 04/02/2015 08:48 AM, Alex Williamson wrote:
On Sat, 2015-03-28 at 01:54 +1100, Alexey Kardashevskiy wrote:
Modern IBM POWERPC systems support multiple (currently two) TCE tables
per IOMMU group (a.k.a. PE). This adds a iommu_table_group container
for TCE tables. Right now just one table is su
On Thu, 2015-04-02 at 13:30 +1100, Alexey Kardashevskiy wrote:
> On 04/02/2015 08:48 AM, Alex Williamson wrote:
> > On Sat, 2015-03-28 at 01:54 +1100, Alexey Kardashevskiy wrote:
> >> This makes use of the it_page_size from the iommu_table struct
> >> as page size can differ.
> >>
> >> This replace
On Thu, 2015-04-02 at 13:33 +1100, Alexey Kardashevskiy wrote:
> On 04/02/2015 08:48 AM, Alex Williamson wrote:
> > On Sat, 2015-03-28 at 01:54 +1100, Alexey Kardashevskiy wrote:
> >> Modern IBM POWERPC systems support multiple (currently two) TCE tables
> >> per IOMMU group (a.k.a. PE). This adds
On 04/02/2015 08:48 AM, Alex Williamson wrote:
On Sat, 2015-03-28 at 01:55 +1100, Alexey Kardashevskiy wrote:
We are adding support for DMA memory pre-registration to be used in
conjunction with VFIO. The idea is that the userspace which is going to
run a guest may want to pre-register a user sp
On 2015/04/02 10:36, Gu Zheng wrote:
Hi Kame, TJ,
On 04/01/2015 04:30 PM, Kamezawa Hiroyuki wrote:
On 2015/04/01 12:02, Tejun Heo wrote:
On Wed, Apr 01, 2015 at 11:55:11AM +0900, Kamezawa Hiroyuki wrote:
Now, hot-added cpus will have the lowest free cpu id.
Because of this, in most of syste
On Wed, 01 Apr 2015 21:56:57 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Add a enum_map file in the tracing directory to see what enums have been
> saved to convert in the print fmt files.
Hmm, I'm thinking of dropping this patch, and adding it later with a
config option
tree: git://people.freedesktop.org/~airlied/linux.git drm-next
head: 502e95c6678505474f1056480310cd9382bacbac
commit: 502e95c6678505474f1056480310cd9382bacbac [23/23] drm/vgem: implement
virtual GEM
reproduce:
# apt-get install sparse
git checkout 502e95c6678505474f1056480310cd9382bacbac
Signed-off-by: Fengguang Wu
---
vgem_drv.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/vgem/vgem_drv.c b/drivers/gpu/drm/vgem/vgem_drv.c
index cb3b435..f7440e8c8 100644
--- a/drivers/gpu/drm/vgem/vgem_drv.c
+++ b/drivers/gpu/drm/vgem/vgem_drv.c
@@
On Thu, 2015-04-02 at 10:59 +0800, kbuild test robot wrote:
> Signed-off-by: Fengguang Wu
[]
> diff --git a/drivers/gpu/drm/vgem/vgem_drv.c b/drivers/gpu/drm/vgem/vgem_drv.c
[]
> @@ -195,7 +195,7 @@ static int vgem_gem_dumb_create(struct drm_file *file,
> struct drm_device *dev,
> return 0;
Hi Yinghai,
On 04/01/2015 10:04 PM, Yinghai Lu wrote:
> On Mon, Mar 9, 2015 at 1:27 PM, Peter Hurley wrote:
>> setup_earlycon() will now match and register the desired earlycon
>> from the param string (as if 'earlycon=...' had been set on the
>> command line). Use setup_earlycon() from existing
Hi Morten,
On 04/01/2015 06:33 PM, Morten Rasmussen wrote:
>> Alright I see. But it is one additional wake up. And the wake up will be
>> within the cluster. We will not wake up any CPU in the neighboring
>> cluster unless there are tasks to be pulled. So, we can wake up a core
>> out of a deep id
Hi, Xishi
[snip]
> >> arch/x86/mm/numa.c |3 ++-
> >> 1 file changed, 2 insertions(+), 1 deletion(-)
> >>
> >> --- linux.orig/arch/x86/mm/numa.c
> >> +++ linux/arch/x86/mm/numa.c
> >> @@ -484,7 +484,8 @@ static void __init numa_clear_kernel_nod
> >>
> >>/* Mark all kernel nodes. */
> >>
On Sun, 03/29 17:04, Michael S. Tsirkin wrote:
> move pci_msi_set_enable and pci_msix_clear_and_set_ctrl out of msi.c, so
> we can use them will be used which MSI isn't configured in kernel.
if
s/will be used which/when/
then
Reviewed-by: Fam Zheng
>
> Signed-off-by: Michael S. Tsirkin
> ---
On Wed, 2015-04-01 at 18:04 +0100, Morten Rasmussen wrote:
> On Wed, Apr 01, 2015 at 07:49:56AM +0100, Preeti U Murthy wrote:
> >
> > On 04/01/2015 12:24 AM, Jason Low wrote:
> > > On Tue, 2015-03-31 at 14:07 +0530, Preeti U Murthy wrote:
> > >> Hi Jason,
> > >>
> > >> On 03/31/2015 12:25 AM, Jaso
> --- a/kernel/time/tick-sched.c
> +++ b/kernel/time/tick-sched.c
> @@ -568,6 +568,7 @@ static ktime_t tick_nohz_stop_sched_tick(struct
> tick_sched *ts,
> unsigned long rcu_delta_jiffies;
> struct clock_event_device *dev =
> __this_cpu_read(tick_cpu_device.evtdev);
> u64 time_d
From: Xunlei Pang
As part of addressing in-kernel y2038 issues, this patch adds
read_boot_clock64() and replaces all the call sites of read_boot_clock()
with this function. This is a __weak implementation, which simply
calls the existing y2038 unsafe read_boot_clock().
This allows architecture s
From: Xunlei Pang
This driver has a number of y2038/y2106 issues.
This patch resolves them by:
- Repalce get_seconds() with ktime_get_real_seconds()
- Replace rtc_time_to_tm() with rtc_time64_to_tm()
Also add test_rtc_set_mmss64() for testing rtc_class_ops's
set_mmss64(), which can be activated
From: Xunlei Pang
We want to convert mxc_rtc_set_mmss() to use rtc_class_ops's set_mmss64(),
but it uses get_alarm_or_time()/set_alarm_or_time() internal interfaces
which are y2038 unsafe.
So here as a separate patch, it converts these two internal interfaces
of "mxc" to use safe time64_t to mak
From: Xunlei Pang
rtc_read_time() has already judged valid tm by rtc_valid_tm(),
so just remove it.
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Ingo Molnar
Signed-off-by: Xunlei Pang
Signed-off-by: John Stultz
---
drivers/rtc/class.c | 4
1 file changed, 4 deletions(-)
diff --git a/dr
From: Xunlei Pang
If a system does not provide a persistent_clock(), the time
will be updated on resume by rtc_resume(). With the addition
of the non-stop clocksources for suspend timing, those systems
set the time on resume in timekeeping_resume(), but may not
provide a valid persistent_clock().
From: Xunlei Pang
This driver has a number of y2038/y2106 issues.
This patch resolves them by:
- Replace rtc_time_to_tm() with rtc_time64_to_tm()
- Change mc13xxx_rtc_set_mmss() to use rtc_class_ops's set_mmss64()
After this patch, the driver should not have any remaining
y2038/y2106 issues.
C
Ingo noted there was no reason to pass the timekeeper structure
to timekeeping_check_update(), and the tk_read_base would be fine,
which simplifies the amount of dereferencing to get to values we
care about.
So this patch simply changes the function as suggested.
Cc: Ingo Molnar
Cc: Thomas Gleix
Ingo suggested that the timekeeping debugging variables
recently added should not be global, and should be tied
to the timekeeper's read_base.
Thus this patch implements that suggestion.
I'm a little hesitant here, since the tkr structure
has been carefully designed to fit in a cacheline.
However
Ingo noted that the description of clocks_calc_max_nsecs()'s
50% safety margin was somewhat circular. So this patch tries
to improve the comment to better explain what we mean by the
50% safety margin and why we need it.
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Prarit Bhargava
From: Xunlei Pang
This driver has a number of y2038/y2106 issues.
This patch resolves them by:
- Replace rtc_time_to_tm() with rtc_time64_to_tm()
- Replace rtc_tm_to_time() with rtc_tm_to_time64()
- Change mxc_rtc_set_mmss() to use rtc_class_ops's set_mmss64()
After this patch, the driver shoul
From: Xunlei Pang
timekeeping_inject_sleeptime64() is only used by RTC suspend/resume,
so add build dependencies on the necessary RTC related macros.
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Ingo Molnar
Signed-off-by: Xunlei Pang
[jstultz: Improve commit message clarity]
Signed-off-by: Joh
From: Xunlei Pang
When there's no persistent clock, normally timekeeping_suspend_time
should always be zero, but this can break in timekeeping_suspend().
At T1, there was a system suspend, so old_delta was assigned T1.
After some time, one time adjustment happened, and xtime got the
value of T1-
From: Xunlei Pang
Currently the rtc_class_op's set_mmss() function takes a 32bit second
value (on 32bit systems), which is problematic for dates past y2038.
This patch provides a safe version named set_mmss64() using y2038 safe
time64_t.
After this patch, set_mmss() is deprecated and all its us
From: Xunlei Pang
Change alpha_rtc_set_mmss() and remote_set_mmss() to use
rtc_class_ops's set_mmss64().
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Ingo Molnar
Acked-by: Alessandro Zummo
Signed-off-by: Xunlei Pang
Signed-off-by: John Stultz
---
arch/alpha/kernel/rtc.c | 8
1 file
From: Xunlei Pang
This driver has a number of y2038/y2106 issues.
This patch resolves them by:
- Replace rtc_tm_to_time() with rtc_tm_to_time64()
- Replace rtc_time_to_tm() with rtc_time64_to_tm()
- Change ab3100_rtc_set_mmss() to use rtc_class_ops's set_mmss64()
After this patch, the driver sh
On Sun, 03/29 17:04, Michael S. Tsirkin wrote:
> commit d5dea7d95c48d7bc951cee4910a7fd9c0cd26fb0
> "PCI: msi: Disable msi interrupts when we initialize a pci device"
> fixes kexec when the booting kernel does not enable msi interupts.
>
> Unfortunately the relevant functionality is in msi.c so
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 by converting clock_access_fn to use timespec64.
Cc: Peter Zijlstra
Cc: Thomas Gleix
From: Xunlei Pang
rtc_class_ops's set_alarm() shouldn't deal with the alarm date,
as this is handled in the rtc core.
See rtc_dev_ioctl()'s RTC_ALM_SET and RTC_WKALM_SET cases.
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Ingo Molnar
Acked-by: Alessandro Zummo
Signed-off-by: Xunlei Pang
Sign
From: Xunlei Pang
As part of addressing "y2038 problem" for in-kernel uses, this
patch adds the y2038-safe tegra_read_persistent_clock64() using
timespec64.
Because we rely on some subsequent changes to convert arm multiarch
support, tegra_read_persistent_clock() will be removed then.
Cc: Peter
From: Xunlei Pang
As part of addressing in-kernel y2038 issues, this patch adds
read_persistent_clock64() and replaces all the call sites of
read_persistent_clock() with this function. This is a __weak
implementation, which simply calls the existing y2038 unsafe
read_persistent_clock().
This all
On 04/02/2015 01:50 PM, Alex Williamson wrote:
On Thu, 2015-04-02 at 13:30 +1100, Alexey Kardashevskiy wrote:
On 04/02/2015 08:48 AM, Alex Williamson wrote:
On Sat, 2015-03-28 at 01:54 +1100, Alexey Kardashevskiy wrote:
This makes use of the it_page_size from the iommu_table struct
as page siz
From: Xunlei Pang
As part of addressing in-kernel y2038 issues, this patch adds
update_persistent_clock64() and replaces all the call sites of
update_persistent_clock() with this function. This is a __weak
implementation, which simply calls the existing y2038 unsafe
update_persistent_clock().
Th
From: Xunlei Pang
As part of addressing "y2038 problem" for in-kernel uses, this
patch adds the y2038-safe omap_read_persistent_clock64() using
timespec64.
Because we rely on some subsequent changes to convert arm multiarch
support, omap_read_persistent_clock() will be removed then.
Also remove
Hey Ingo, Thomas, Peter,
I wanted to send along my remaining 4.1 queue, which contains:
* y2038 fixes for the timekeeping persistent- and boot-clock interfaces.
(Xunlei)
* y2038 fixes for RTC drivers (Xunlei)
* Small suspend/resume timing fixes (Xunlei)
* Minor cleanups requested by Ingo (Me)
On Tue, Mar 31, 2015 at 8:55 AM, Shuah Khan wrote:
> Hi John,
>
> I am seeing checkpatch warnings on this patch. See below.
Sorry!
> On 03/26/2015 05:31 AM, Prarit Bhargava wrote:
>>
>>
>> On 03/25/2015 07:44 PM, John Stultz wrote:
>>> The set-timer-lat test fails when testing CLOCK_BOOTTIME_ALA
The set-timer-lat test fails when testing CLOCK_BOOTTIME_ALARM
or CLOCK_REALTIME_ALARM when the user isn't running as root or
with CAP_WAKE_ALARM.
So this patch improves the error checking so we report the
issue more clearly and continue rather then reporting a failure.
Cc: Shuah Khan
Cc: Prarit
On Thu, 2015-04-02 at 14:40 +1100, Alexey Kardashevskiy wrote:
> On 04/02/2015 01:50 PM, Alex Williamson wrote:
> > On Thu, 2015-04-02 at 13:30 +1100, Alexey Kardashevskiy wrote:
> >> On 04/02/2015 08:48 AM, Alex Williamson wrote:
> >>> On Sat, 2015-03-28 at 01:54 +1100, Alexey Kardashevskiy wrote:
Hi Andrew,
Both patches looks fine to us.
Thank You
> On Wed, Apr 01, 2015 at 05:18:46AM +, Maninder Singh wrote:
> > Hi Andrew,
> > Thanks for making new patch, Actually there is some problem with our mail
> > editor.
> > It changes tabs with spaces and corrupts the patch, we are solving th
(2015/04/01 23:41), Arnaldo Carvalho de Melo wrote:
> Em Wed, Apr 01, 2015 at 06:08:17PM +0900, Masami Hiramatsu escreveu:
>> Ping?
>
>
>
>>> With this patch, perf probe can access unnamed fields.
>>> -
>>> #./perf probe -nfx ./perf lock__delete ops 'locked_ops=ops->locked.ops'
>>> Add
On Wed, Apr 01, 2015 at 01:22:42PM +0200, David Sterba wrote:
> On Wed, Apr 01, 2015 at 12:03:28AM -0700, Omar Sandoval wrote:
> > --- a/fs/btrfs/super.c
> > +++ b/fs/btrfs/super.c
> > @@ -1024,6 +1024,10 @@ static int btrfs_show_options(struct seq_file *seq,
> > struct dentry *dentry)
> > str
On Sun, 03/29 17:04, Michael S. Tsirkin wrote:
> pci_msi_setup_pci_dev and pci_msi_off share a lot of code.
> This used to be justified since pci_msi_setup_pci_dev
> wasn't compiled in when CONFIG_PCI_MSI is off.
> Now that it is, let's reuse code.
>
> Since pci_msi_off is used by early quirks, do
On Sun, 03/29 17:04, Michael S. Tsirkin wrote:
> This partially reverts commit d52877c7b1afb8c37ebe17e2005040b79cb618b0:
> "pci/irq: let pci_device_shutdown to call pci_msi_shutdown v2"
>
> It's un-necessary now that we disable msi at start, and it actually
> turns out to cause problems: som
On Sun, 03/29 17:04, Michael S. Tsirkin wrote:
> pci_msi_shutdown and pci_msix_shutdown are now internal to msi.c, drop
> them from header and make them static.
Reviewed-by: Fam Zheng
>
> Signed-off-by: Michael S. Tsirkin
> ---
> include/linux/pci.h | 4
> drivers/pci/msi.c | 4 ++--
>
On Sun, 03/29 17:04, Michael S. Tsirkin wrote:
> pci core now disables msi on probe automatically,
> drop this from device-specific code.
>
> Cc: Bjorn Helgaas
> Cc: linux-...@vger.kernel.org
> Signed-off-by: Michael S. Tsirkin
> ---
> drivers/virtio/virtio_pci_common.c | 3 ---
> 1 file change
On Thu, Apr 02, 2015 at 08:52:11AM +0800, Fengguang Wu wrote:
> Hi Herbert,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>
> commit ccd57b1bd32460d27bbb9c599e795628a3c66983
> Author:
From: Borislav Petkov
Date: Wed, 1 Apr 2015 12:49:52 +0200
Subject: [PATCH v1.1] x86/mm/ASLR: Propagate ASLR status to kernel proper
Commit
e2b32e678513 ("x86, kaslr: randomize module base load address")
made module base address randomization unconditional and didn't regard
disabled KASLR due
]
> > [0.554400] ===
> > [0.555285] [ INFO: suspicious RCU usage. ]
> > [0.556176] 4.0.0-rc4-01225-gccd57b1 #171 Not tainted
> > [0.557156] ---
> > [0.558044] lib/rhashtable.c:400 suspicious rcu_dereference_check()
&
On Thu, Apr 02, 2015 at 12:11:35PM +0800, Fengguang Wu wrote:
>
> Yes it is contained in next-20150401 which is bad:
>
> # extra tests on tree/branch next/master
> git bisect bad e954104e2b634b42811dad8d502cbf240f206df2 # 21:22 0-
> 60 Add linux-next specific
The usleep is only provided on distros from Redhat so running ftracetest
on other distro resulted in failures due to the missing usleep.
The reason of using [u]sleep in the test was to generate (scheduler)
events. It can be done various ways like this:
yield() { pinc localhost -c 1 || sleep .00
On Wed, Apr 01, 2015 at 10:32:04PM +0100, Mark Einon wrote:
> Two static functions are only used if CONFIG_PCI is defined,so only build them
> if this is the case. Fixes the build warnings:
>
> arch/x86/kernel/early_printk.c:98:13: warning: ‘mem32_serial_out’ defined but
> not used [-Wunused-func
On Wed, Apr 1, 2015 at 7:12 AM, Michael Turquette wrote:
> Quoting Jassi Brar (2015-03-02 02:28:44)
>> On 2 March 2015 at 15:48, Lee Jones wrote:
>> > On Mon, 02 Mar 2015, Jassi Brar wrote:
>> >
>> >> On Mon, Mar 2, 2015 at 2:06 PM, Lee Jones wrote:
>> >> > On Sat, 28 Feb 2015, Jassi Brar wrote:
On Thu, Apr 2, 2015 at 12:32 AM, Tim Bird wrote:
> I didn't see an Ack from Mark or Rob. But I did see a question from
> Mark and response from Bjorn.
>
> Ohad - did you take this or are you still waiting for something?
>
> Who should I pester about this? :-)
Sorry, I can't take this without a D
The usleep is only provided on distros from Redhat so running ftracetest
on other distro resulted in failures due to the missing usleep.
The reason of using [u]sleep in the test was to generate (scheduler)
events. It can be done various ways like this:
yield() { ping localhost -c 1 || sleep .00
On Thursday 02 April 2015 04:57 AM, AKASHI Takahiro wrote:
Please try my latest kexec-tools in my linaro repo (branch name is
kdump/v0.11)
and let me know the result.
Thanks a lot.. Just fetched your repo and found v.0.11.
With this crash kernel loaded successfully, if I do not use initrd.
On 2015/4/1 22:48, Ingo Molnar wrote:
>
> * Wang Nan wrote:
>
>> Perf passes incorrect segbase and table_data to libunwind when
>> map->pgoff != 0, causes unwind failure. This patch fixes this
>> problem.
>>
>> segbase is an absolute offset from the head of object file, directly
>> read from
On Sun, Mar 29, 2015 at 03:38:50PM +0200, Pali Rohár wrote:
Please include why. No empty commit messages please.
For example, you've written nearly a third of the dell-wmi.c driver, and all the
dell-smo8800.c driver.
Dell Laptop is still pending the keyboard backlight patches though I believe
(h
1 - 100 of 742 matches
Mail list logo
