This fixes following errors:
- ERROR: "(foo*)" should be "(foo *)"
- ERROR: "foo ** bar" should be "foo **bar"
Signed-off-by: Vladimir Cernov
---
mm/madvise.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/mm/madvise.c b/mm/madvise.c
index 70
On Thu, Jul 11, 2013 at 10:00 AM, Vladimir Cernov
wrote:
> This fixes following errors:
> - ERROR: "(foo*)" should be "(foo *)"
> - ERROR: "foo ** bar" should be "foo **bar"
>
> Signed-off-by: Vladimir Cernov
Reviewed-by: Pekka Enberg
--
To unsubscribe from this list: send the l
On Thursday, July 11, 2013 3:40 PM, Kishon Vijay Abraham I wrote:
> On Thursday 11 July 2013 11:19 AM, Jingoo Han wrote:
> >
> > drivers/pci/host/Makefile |1 +
> > drivers/pci/host/pcie-designware.c | 963
> > +---
> > drivers/pci/host/pcie-designwar
On Wed 10-07-13 18:25:06, azurIt wrote:
> >> Now i realized that i forgot to remove UID from that cgroup before
> >> trying to remove it, so cgroup cannot be removed anyway (we are using
> >> third party cgroup called cgroup-uid from Andrea Righi, which is able
> >> to associate all user's processe
On Wed, Jul 10, 2013 at 11:52 PM, Sergei Shtylyov
wrote:
> On 07/11/2013 01:45 AM, Geert Uytterhoeven wrote:
>
>> When builtin (CONFIG_USB_FOTG210_UDC=y):
>
>>LD drivers/usb/gadget/built-in.o
>> WARNING: drivers/usb/gadget/built-in.o(.data+0xbf8): Section mismatch in
>> reference from the
On 07/10/2013 10:08 PM, Alan Stern wrote:
> On Wed, 10 Jul 2013, Roger Quadros wrote:
>
>> Some platforms e.g. ehci-omap can generate an interrupt
>> (i.e. remote wakeup) even when the controller is suspended i.e.
>> HW_ACCESSIBLE is cleared.
>>
>> Introduce a flag "has_wakeup_irq" in struct usb_h
On Wed, Jul 10, 2013 at 06:56:35PM +0200, Christian Ruppert wrote:
> On Wed, Jul 10, 2013 at 01:52:15PM +0300, Mika Westerberg wrote:
> > On Tue, Jul 09, 2013 at 06:19:28PM +0200, Christian Ruppert wrote:
> > > What I meant is the following: The clock cycle time Tc is composed of
> > > the four com
On 07/10/2013 09:45 PM, Alan Stern wrote:
> On Wed, 10 Jul 2013, Roger Quadros wrote:
>
>> Some platforms e.g. ehci-omap can generate an interrupt
>> (i.e. remote wakeup) even when the controller is suspended i.e.
>> HW_ACCESSIBLE is cleared.
>>
>> Introduce a flag "has_wakeup_irq" in struct usb_h
Greetings,
Linux 2.6.35 had a driver for sysfs access to the MXS persistent bits
(drivers/misc/mxs-persistent.c).
I haven't seen this is supported upstream. Is anybody working on that?
Where would such a driver fit?
Best regards,
--
Hector Palacios
--
To unsubscribe from this list: send the li
Dear RT Folks,
I'm pleased to announce the 3.8.13-rt14 release.
changes since v3.8.13-rt13:
- added a patch from Uwe Kleine-König to fix the UP breakage introduced by
the recent s/sbin spinlocks/raw_spin_lock/ change.
- added a fix for a livelock of workqueue vs ata-piix. Found by Carsten
Emd
On Thu, 11 Jul 2013 16:53:43 +1000, Stephen Rothwell wrote:
> On Thu, 11 Jul 2013 07:57:00 +0200 Jean Delvare wrote:
> > On Thu, 11 Jul 2013 10:27:24 +1000, Stephen Rothwell wrote:
> > > Why have you just rebased the jdelvare-hwmon series
> > > (http://khali.linux-fr.org/devel/linux-3/jdelvare-hwm
On 10/07/2013 17:57, Wolfram Sang :
Since commit ab78029 (drivers/pinctrl: grab default handles from device core),
we can rely on device core for setting the default pins. Compile tested only.
Acked-by: Linus Walleij (personally at LCE13)
Signed-off-by: Wolfram Sang
Acked-by: Nicolas Ferre
On 10/07/2013 17:57, Wolfram Sang :
Since commit ab78029 (drivers/pinctrl: grab default handles from device core),
we can rely on device core for setting the default pins. Compile tested only.
Acked-by: Linus Walleij (personally at LCE13)
Signed-off-by: Wolfram Sang
---
drivers/tty/serial/at
Mark Brown wrote:
> On Fri, Jun 21, 2013 at 09:16:16AM -0700, Nick Dyer wrote:
>> Mark Brown wrote:
>>> Yes, to be honest. I'd hope it wouldn't be increasing the number of
>>> read/write operations...
>
>> For some operations it does. For example updating the whole chip config
>> (which is a comm
On Wed, Jul 10, 2013 at 10:49:56PM +0900, Takuya Yoshikawa wrote:
> On Wed, 10 Jul 2013 11:24:39 +0300
> "Michael S. Tsirkin" wrote:
>
> > On x86, kvm_arch_create_memslot assumes that rmap/lpage_info for the
> > slot are zeroed out: if they weren't, error handling code after out_free
> > label wi
On 07/11/2013 09:30 AM, Hector Palacios wrote:
Greetings,
Linux 2.6.35 had a driver for sysfs access to the MXS persistent bits
(drivers/misc/mxs-persistent.c).
I haven't seen this is supported upstream. Is anybody working on that?
Where would such a driver fit?
Adding Steffen Trumtrar, as I c
On Thu, Jul 11, 2013 at 3:01 AM, Alan Stern wrote:
> On Thu, 11 Jul 2013, Arnd Bergmann wrote:
>
>> On Wednesday 10 July 2013, Alan Stern wrote:
>> > This isn't right. There are USB host controllers that use PIO, not
>> > DMA. The HAS_DMA dependency should go with the controller driver, not
>> >
On Wed, Jul 10, 2013 at 7:30 PM, Gustavo Padovan wrote:
> Hi Sedat,
>
> * Sedat Dilek [2013-04-26 19:40:20 +0200]:
>
>> On Fri, Apr 26, 2013 at 7:32 PM, Sedat Dilek wrote:
>> > On Fri, Apr 26, 2013 at 7:30 PM, Sedat Dilek wrote:
>> >> On Fri, Apr 26, 2013 at 10:03 AM, Stephen Rothwell
>> >> w
On Wed, 10 Jul 2013 16:18:20 +0200, Jiri Olsa wrote:
> On Wed, Jun 26, 2013 at 04:14:09PM +0900, Namhyung Kim wrote:
>> From: Namhyung Kim
>>
>> The -p (--pid) option enables to trace existing process by its pid.
>
> hi,
> I can't get any output from -p for live subcommand:
>
> [jolsa@krava perf]
On Wed, 10 Jul 2013 16:28:21 +0200, Jiri Olsa wrote:
> On Wed, Jun 26, 2013 at 04:14:12PM +0900, Namhyung Kim wrote:
>> From: Namhyung Kim
>
> SNIP
>
>> +
>> +static int create_perf_directory(struct perf_ftrace *ftrace)
>> +{
>> +int err;
>> +char buf[PATH_MAX];
>> +struct stat statbuf
On Wed, 10 Jul 2013 16:41:48 +0200, Jiri Olsa wrote:
> On Wed, Jun 26, 2013 at 04:14:13PM +0900, Namhyung Kim wrote:
>> From: Namhyung Kim
>>
>> The ftrace show subcommand is for viewing recorded ftrace files. It
>> enters perf.data.dir directory and open perf.header file to find out
>> necessar
From: Liu ShuoX
In shutdown progress, system is possible to do power transition
(such as suspend-to-ram) in parallel. It is unreasonable. So,
fixes it by adding a system_state checking and queue try_to_suspend
again when system status is not running.
Signed-off-by: Liu ShuoX
---
kernel/power/a
Dear Zhang, Eduardo
Do you have any comments/feedback for me regarding this thermal
framework related patch?
I've already received some feedback from Durga for this patch, but I
think that maintainers are most welcome to express their opinion :-)
Thanks in advance.
> This patch provides auto di
On Wed, 10 Jul 2013 16:45:39 +0200, Jiri Olsa wrote:
> On Wed, Jun 26, 2013 at 04:14:14PM +0900, Namhyung Kim wrote:
>
> SNIP
>
>>
>> +static int
>> +__cmd_ftrace_report(struct perf_ftrace *ftrace, int argc, const char **argv)
>> +{
>> +int ret = -1;
>> +const char * const report_usage[]
On Wed, Jul 10, 2013 at 10:21:57PM -0300, Marcelo Tosatti wrote:
>
> Linux as a guest on KVM hypervisor, the only user of the pvclock
> vsyscall interface, does not require notification on task migration
> because:
>
> 1. cpu ID number maps 1:1 to per-CPU pvclock time info.
> 2. per-CPU pv
Geert Uytterhoeven writes:
> On Wed, 10 Jul 2013, Linux Kernel Mailing List wrote:
>> --- /dev/null
>> +++ b/drivers/net/wireless/ath/ath10k/hw.h
>
>> +#define SUPPORTED_FW_MAJOR 1
>> +#define SUPPORTED_FW_MINOR 0
>> +#define SUPPORTED_FW_RELEASE0
>> +#define SUPPORTED_FW_BUILD 629
>
>
On Wed, 10 Jul 2013 16:22:19 +0200, Jiri Olsa wrote:
> On Wed, Jun 26, 2013 at 04:14:18PM +0900, Namhyung Kim wrote:
>> From: Namhyung Kim
>>
>> Cc: Steven Rostedt
>> Cc: Frederic Weisbecker
>> Signed-off-by: Namhyung Kim
>> ---
>
> SNIP
>
>> +OPTIONS
>> +---
>> +...::
>> +Any command
On (07/11/13 10:43), Michael Wang wrote:
> Hi, Sergey
>
> On 07/11/2013 07:13 AM, Sergey Senozhatsky wrote:
> [snip]
> >
> >
> > Please kindly review the following patch.
> >
> >
> >
> > Remove cpu device only upon succesful cpu down on CPU_POST_DEAD event,
> > so we can kill off CPU_DOWN_FAI
Hi Hector,
On Thu, Jul 11, 2013 at 09:30:34AM +0200, Hector Palacios wrote:
> Greetings,
>
> Linux 2.6.35 had a driver for sysfs access to the MXS persistent
> bits (drivers/misc/mxs-persistent.c).
Freescale's 2.6.35 I suspect, right?
> I haven't seen this is supported upstream. Is anybody work
Hi,
On Thursday 11 July 2013 12:35 PM, Jingoo Han wrote:
> On Thursday, July 11, 2013 3:40 PM, Kishon Vijay Abraham I wrote:
>> On Thursday 11 July 2013 11:19 AM, Jingoo Han wrote:
>>>
>>> drivers/pci/host/Makefile |1 +
>>> drivers/pci/host/pcie-designware.c | 963
>>> +---
On 07/11/2013 01:13 AM, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Wed, Jul 10, 2013 at 07:29:57PM +0800, Wei Ni wrote:
>> Enable thermal sensor nct1008 for t30 cardhu.
>
> Nit: "Tegra30 Cardhu"
>
>> diff --git a/arch/arm/boot/dts/tegra30-cardhu.dtsi
>> b/arch/arm/boot/dts/te
On 07/11/2013 02:12 AM, Guenter Roeck wrote:
> On Wed, Jul 10, 2013 at 10:05:53AM -0700, Thierry Reding wrote:
>> On Wed, Jul 10, 2013 at 07:25:38PM +0800, Wei Ni wrote:
>>> When the temperature exceed the limit range value,
>>> the driver can handle the interrupt.
>>>
>>> Signed-off-by: Wei Ni
>>
Hi,
On Wednesday 10 July 2013 06:38 PM, Pali Rohár wrote:
* On RX-51 probing for acx565akm driver is later then for omapfb which cause
that omapfb probe fail and framebuffer is not working
* EPROBE_DEFER causing that kernel try to probe for omapfb later again which
fixing this problem
* Witho
On 07/11/2013 02:18 AM, Guenter Roeck wrote:
> On Wed, Jul 10, 2013 at 07:25:38PM +0800, Wei Ni wrote:
>> When the temperature exceed the limit range value,
>> the driver can handle the interrupt.
>>
>> Signed-off-by: Wei Ni
>> ---
>> drivers/hwmon/lm90.c | 77
>> ++
On 07/11/2013 02:21 AM, Guenter Roeck wrote:
> On Wed, Jul 10, 2013 at 07:25:37PM +0800, Wei Ni wrote:
>> Split set&show temp codes as common functions, so we can use it directly when
>> implement linux thermal framework.
>>
>> Signed-off-by: Wei Ni
>> ---
>> drivers/hwmon/lm90.c | 118
>> +
On 07/11/2013 04:22 PM, Sergey Senozhatsky wrote:
[snip]
>>
>
> Hello Michael,
> nice job! works fine for me.
>
> Reported-and-Tested-by: Sergey Senozhatsky
Thanks for the test :)
Borislav may also doing some testing, let's wait for few days and see
whether there are any point we missed.
And
Hi Guenter, Justin,
On Wed, 3 Jul 2013 07:42:01 -0700, Guenter Roeck wrote:
> On Wed, Jul 03, 2013 at 08:35:59AM -0400, Justin Piszcz wrote:
> > I also found:
> > http://www.lm-sensors.org/wiki/Configurations/SuperMicro/X9SRA
> >
> > Does Super Micro also have such a config file for the X9SRL-F?
On 07/11/2013 04:47 PM, Michael Wang wrote:
> On 07/11/2013 04:22 PM, Sergey Senozhatsky wrote:
> [snip]
>>>
>>
>> Hello Michael,
>> nice job! works fine for me.
>>
>> Reported-and-Tested-by: Sergey Senozhatsky
>
> Thanks for the test :)
>
> Borislav may also doing some testing, let's wait for f
On 07/10/2013 10:04 PM, Alan Stern wrote:
> On Wed, 10 Jul 2013, Roger Quadros wrote:
>
>> Call ehci_suspend/resume() during runtime suspend/resume
>> as well as system suspend/resume.
>>
>> Use a flag "bound" to indicate that the HCD structures are valid.
>> This is only true between usb_add_hcd(
Hi,
On Thursday 11 July 2013 11:19 AM, Jingoo Han wrote:
> Exynos PCIe IP consists of Synopsys specific part and Exynos
> specific part. Only core block is a Synopsys designware part;
> other parts are Exynos specific.
> Also, the Synopsys designware part can be shared with other
> platforms; thus
On 07/10/2013 03:32 AM, Alexander Graf wrote:
> On 07/06/2013 05:07 PM, Alexey Kardashevskiy wrote:
>> This adds special support for huge pages (16MB). The reference
>> counting cannot be easily done for such pages in real mode (when
>> MMU is off) so we added a list of huge pages. It is populate
On (07/11/13 16:47), Michael Wang wrote:
> On 07/11/2013 04:22 PM, Sergey Senozhatsky wrote:
> [snip]
> >>
> >
> > Hello Michael,
> > nice job! works fine for me.
> >
> > Reported-and-Tested-by: Sergey Senozhatsky
>
> Thanks for the test :)
>
> Borislav may also doing some testing, let's wait
Dear Maxime,
On 07/11/2013 10:24 AM, maxime.rip...@free-electrons.com wrote:
Hi Hector,
On Thu, Jul 11, 2013 at 09:30:34AM +0200, Hector Palacios wrote:
Greetings,
Linux 2.6.35 had a driver for sysfs access to the MXS persistent
bits (drivers/misc/mxs-persistent.c).
Freescale's 2.6.35 I sus
On Wed, Jul 10, 2013 at 02:59:55PM +0200, Dominik Dingel wrote:
> This patch enables async page faults for s390 kvm guests.
> It provides the userspace API to enable, disable or get the status of this
> feature. Also it includes the diagnose code, called by the guest to enable
> async page faults.
On 07/10/2013 04:03 PM, Gleb Natapov wrote:
[...] trimmed
Yes. you are right. dynamic ple window was an attempt to solve it.
Probelm is, reducing the SPIN_THRESHOLD is resulting in excess halt
exits in under-commits and increasing ple_window may be sometimes
counter productive as it affects oth
On Monday 08 July 2013 08:02 PM, Felipe Balbi wrote:
Hi,
On Mon, Jul 08, 2013 at 07:12:59PM +0530, Sourav Poddar wrote:
+static inline unsigned long dra7xxx_readl(struct dra7xxx_qspi *qspi,
+ unsigned long reg)
+{
+ return readl(qspi->base + reg);
+}
+
+static inline void dr
On Thu, Jul 11, 2013 at 09:44:12AM +0200, Hector Palacios wrote:
> On 07/11/2013 09:30 AM, Hector Palacios wrote:
> >Greetings,
> >
> >Linux 2.6.35 had a driver for sysfs access to the MXS persistent bits
> >(drivers/misc/mxs-persistent.c).
> >I haven't seen this is supported upstream. Is anybody w
Hi, Alsa Maintainer:
I just provided a patch to enhance dynamic pcm feature. And It is important
for our platform. In our platform, the cpu_dai in FE is dummy, but codec_dai in
FE is specific interface. And it is convenient for us to use codec_dai to
derive fe dapm widget. I don't know who ca
Stephen Gianino.doc
Description: MS-Word document
Add "host-off-card-on" dt property and parse it to support the
quirk SDHCI_QUIRK2_HOST_OFF_CARD_ON.
Signed-off-by: Wei Ni
---
Documentation/devicetree/bindings/mmc/mmc.txt |2 ++
drivers/mmc/host/sdhci-pltfm.c|3 +++
2 files changed, 5 insertions(+)
diff --git a/Document
> Hello Grant,
> > Hi Grant,
> > > Hello Grant,
> > >
> > > Could you pull this Please?
> > A gentle ping on this.
> A gentle ping on this. Could you pull this one?
> > > > Signed-off-by: J Keerthy
> > > > Acked-by: Samuel Ortiz
Why does Grant have to pull this?
Do you know why Sam didn't take
hi,
i wnat to test usb driver example of ldd3 book, i able to compile ldd3`s
examples with zero error, i have study ldd3 book and its examples, For this
exmaple can anyone tell me after replace this driver oto usb-storage how i can
properly use it and get practical knowledge from it.
its a lit
If device was removed from slot and reinsert a new device during
suspend, pciehp can not identify the physical device change now.
So the old driver .resume() method will be called for the new device,
this is bad. If device support device serial number capability,
we can identify this by DSN. So the
v1->v2: Modify pci_get_dsn to pci_device_serial_number,
power off slot before remove the old device during resume to avoid
old .remove() method to touch new hardware.
Fix other typo and fail check problems.
Split the list_empty() guard int
Currently, pciehp_resume() try to hot add device if the slot adapter
status return true. But if there are already some devices exist,
namely list_empty(bus->devices) return false. We should not add the device
again, because the device add action will fail. Also print some uncomfortable
messages lik
Introduce PCIe Ext Capability Device Serial Number support,
so we can use the unique device serial number to identify
the physical device. During system suspend, if the PCIe
device was removed and inserted a new same device, after
system resume there is no good way to identify it, maybe
Device Seri
Signed-off-by: Mel Gorman
---
Documentation/sysctl/kernel.txt | 66 +
1 file changed, 66 insertions(+)
diff --git a/Documentation/sysctl/kernel.txt b/Documentation/sysctl/kernel.txt
index ccd4258..0fe678c 100644
--- a/Documentation/sysctl/kernel.txt
+++ b/
Now that lz4 kernel compression is available, add *.lz4 to .gitignore.
Signed-off-by: Markus Trippelsdorf
Acked-by: Kyungsik Lee
diff --git a/.gitignore b/.gitignore
index 3b8b9b3..7e9932e 100644
--- a/.gitignore
+++ b/.gitignore
@@ -29,6 +29,7 @@ modules.builtin
*.bz2
*.lzma
*.xz
+*.lz4
*.
task_numa_work skips small VMAs. At the time the logic was to reduce the
scanning overhead which was considerable. It is a dubious hack at best.
It would make much more sense to cache where faults have been observed
and only rescan those regions during subsequent PTE scans. Remove this
hack as moti
This patch replaces find_idlest_cpu_node with task_numa_find_cpu.
find_idlest_cpu_node has two critical limitations. It does not take the
scheduling class into account when calculating the load and it is unsuitable
for using when comparing loads between NUMA nodes.
task_numa_find_cpu uses similar
Ideally it would be possible to distinguish between NUMA hinting faults that
are private to a task and those that are shared. If treated identically
there is a risk that shared pages bounce between nodes depending on
the order they are referenced by tasks. Ultimately what is desirable is
that task
NUMA hinting faults counts and placement decisions are both recorded in the
same array which distorts the samples in an unpredictable fashion. The values
linearly accumulate during the scan and then decay creating a sawtooth-like
pattern in the per-node counts. It also means that placement decision
The NUMA PTE scan rate is controlled with a combination of the
numa_balancing_scan_period_min, numa_balancing_scan_period_max and
numa_balancing_scan_size. This scan rate is independent of the size
of the task and as an aside it is further complicated by the fact that
numa_balancing_scan_size contr
Currently automatic NUMA balancing is unable to distinguish between false
shared versus private pages except by ignoring pages with an elevated
page_mapcount entirely. This avoids shared pages bouncing between the
nodes whose task is using them but that is ignored quite a lot of data.
This patch k
A preferred node is selected based on the node the most NUMA hinting
faults was incurred on. There is no guarantee that the task is running
on that node at the time so this patch rescheules the task to run on
the most idle CPU of the selected node when selected. This avoids
waiting for the balancer
This patch favours moving tasks towards the preferred NUMA node when it
has just been selected. Ideally this is self-reinforcing as the longer
the task runs on that node, the more faults it should incur causing
task_numa_placement to keep the task running on that node. In reality a
big weakness is
The NUMA PTE scan is reset every sysctl_numa_balancing_scan_period_reset
in case of phase changes. This is crude and it is clearly visible in graphs
when the PTE scanner resets even if the workload is already balanced. This
patch increases the scan rate if the preferred node is updated and the
task
I upgraded to kernel 3.10.0 and decided to try the new "Full
dynticks system (tickless)" option, but now the system load is always
at 1 or above.
Using the previous "Idle dynticks system (tickless idle)" solves
the problem, so it seems the new Full dynticks code is causing this.
On Thu, Jul 11, 2013 at 02:43:03PM +0530, Raghavendra K T wrote:
> On 07/10/2013 04:03 PM, Gleb Natapov wrote:
> [...] trimmed
>
> >>>Yes. you are right. dynamic ple window was an attempt to solve it.
> >>>
> >>>Probelm is, reducing the SPIN_THRESHOLD is resulting in excess halt
> >>>exits in unde
Ideally it would be possible to distinguish between NUMA hinting faults
that are private to a task and those that are shared. This patch prepares
infrastructure for separately accounting shared and private faults by
allocating the necessary buffers and passing in relevant information. For
now, all
The zero page is not replicated between nodes and is often shared
between processes. The data is read-only and likely to be cached in
local CPUs if heavily accessed meaning that the remote memory access
cost is less of a concern. This patch stops accounting for numa hinting
faults on the zero page
task_numa_placement checks current->mm but after buffers for faults
have already been uselessly allocated. Move the check earlier.
[pet...@infradead.org: Identified the problem]
Signed-off-by: Mel Gorman
---
kernel/sched/fair.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --
This patch selects a preferred node for a task to run on based on the
NUMA hinting faults. This information is later used to migrate tasks
towards the node during balancing.
Signed-off-by: Mel Gorman
---
include/linux/sched.h | 1 +
kernel/sched/core.c | 1 +
kernel/sched/fair.c | 17 +
On 11.07.2013, at 10:57, Alexey Kardashevskiy wrote:
> On 07/10/2013 03:32 AM, Alexander Graf wrote:
>> On 07/06/2013 05:07 PM, Alexey Kardashevskiy wrote:
>>> This adds special support for huge pages (16MB). The reference
>>> counting cannot be easily done for such pages in real mode (when
>>>
THP NUMA hinting fault on pages that are not migrated are being
accounted for incorrectly. Currently the fault will be counted as if the
task was running on a node local to the page which is not necessarily
true.
Signed-off-by: Mel Gorman
---
mm/huge_memory.c | 10 +-
1 file changed, 5 i
This patch tracks what nodes numa hinting faults were incurred on. Greater
weight is given if the pages were to be migrated on the understanding
that such faults cost significantly more. If a task has paid the cost to
migrating data to that node then in the future it would be preferred if the
task
This continues to build on the previous feedback and further testing. Peter
posted a patch that avoids overloading a destination node relative to a
source node by postponing the reschedule of tasks on a preferred node. I
took the load calculations but dropped the balancing part as it performed
badl
On Wed, Jul 10, 2013 at 10:21:57PM -0300, Marcelo Tosatti wrote:
>
> Linux as a guest on KVM hypervisor, the only user of the pvclock
> vsyscall interface, does not require notification on task migration
> because:
>
> 1. cpu ID number maps 1:1 to per-CPU pvclock time info.
> 2. per-CPU pv
On Wed, Jul 10, 2013 at 10:47:40AM -0400, Sasha Levin wrote:
> On 07/10/2013 05:54 AM, Peter Zijlstra wrote:
> >On Tue, Jul 09, 2013 at 06:35:27PM -0400, Sasha Levin wrote:
> >>While going through the NMI dump, I noticed that it's very incomplete, and
> >>full of:
> >>
> >>[ 2536.500130] INFO: NMI
On Thu, Jul 11, 2013 at 11:38:37AM +0200, Rolf Eike Beer wrote:
> Hi,
>
> I'm running 3.10.0 (from openSUSE packages) on an "Intel(R) Core(TM) i7-2600
> CPU @ 3.40GHz". I got a hard lockup on one of my CPUs twice, once with
> backtrace (see attached image). Graphics is the builtin Intel, used wi
On 07/11/2013 03:18 PM, Gleb Natapov wrote:
On Thu, Jul 11, 2013 at 02:43:03PM +0530, Raghavendra K T wrote:
On 07/10/2013 04:03 PM, Gleb Natapov wrote:
[...] trimmed
Yes. you are right. dynamic ple window was an attempt to solve it.
Probelm is, reducing the SPIN_THRESHOLD is resulting in exc
On Thu, Jul 11, 2013 at 10:36:00AM +0300, Mika Westerberg wrote:
> On Wed, Jul 10, 2013 at 06:56:35PM +0200, Christian Ruppert wrote:
> > On Wed, Jul 10, 2013 at 01:52:15PM +0300, Mika Westerberg wrote:
> > > On Tue, Jul 09, 2013 at 06:19:28PM +0200, Christian Ruppert wrote:
> > > > What I meant is
On Mon, 2013-07-08 at 20:26 -0400, Konrad Rzeszutek Wilk wrote:
> Could you explain to me please why the check in the scripts is
> superfluous?
The discussion has since moved on a bit, but I haven't answered this
question yet.
The check grub2 currently performs in one of its configuration scripts
On Wed, 10 Jul 2013, H. Peter Anvin wrote:
> > If any CPU instruction execution would collide with the patching,
> > it'd be trapped by the int3 breakpoint and redirected to the provided
> > "handler" (which would typically mean just skipping over the patched
> > region, acting as "nop" has been t
On 11.07.2013, at 07:12, Alexey Kardashevskiy wrote:
> On 07/10/2013 08:05 PM, Alexander Graf wrote:
>>
>> On 10.07.2013, at 07:00, Alexey Kardashevskiy wrote:
>>
>>> On 07/10/2013 03:02 AM, Alexander Graf wrote:
On 07/06/2013 05:07 PM, Alexey Kardashevskiy wrote:
> This adds real mode
On Thu, Jul 11, 2013 at 03:40:38PM +0530, Raghavendra K T wrote:
> Gleb,
> Can you elaborate little more on what you have in mind regarding per
> VM ple_window. (maintaining part of it as a per vm variable is clear
> to
> me), but is it that we have to load that every time of
ping...
On 07/08/2013 06:38 PM, Gu Zheng wrote:
> Introduce a new lib function anon_inode_getfile_private(), it creates a new
> file
> instance by hooking it up to an anonymous inode, and a dentry that describe
> the
> "class" of the file, similar to anon_inode_getfile(), but each file holds a
ping...
On 07/08/2013 06:38 PM, Gu Zheng wrote:
> Currently aio ring pages use get_user_pages() to allocate pages from movable
> zone,as discussed in thread https://lkml.org/lkml/2012/11/29/69, it is easy to
> pin user pages for a long time, which is fatal for memory hotplug/remove
> framework.
ping...
On 07/08/2013 06:38 PM, Gu Zheng wrote:
> As the aio job will pin the ring pages, that will lead to mem migrated
> failed. In order to fix this problem we use an anon inode to manage the aio
> ring
> pages, and setup the migratepage callback in the anon inode's address space,
> so
> th
On Thu, Jul 11, 2013 at 12:07:21PM +0200, Borislav Petkov wrote:
> On Thu, Jul 11, 2013 at 11:38:37AM +0200, Rolf Eike Beer wrote:
> > Hi,
> >
> > I'm running 3.10.0 (from openSUSE packages) on an "Intel(R) Core(TM)
> > i7-2600
> > CPU @ 3.40GHz". I got a hard lockup on one of my CPUs twice, onc
Yijing,
On Thu, 2013-07-11 at 11:55 +0800, Yijing Wang wrote:
> Can you provide the lspci -vvv and lspci - info messages ?
> I want to confirm your hardware information which cause your resume error.
> You can get these messages in any kernel version, that's ok.
Would it be sufficient to send
(2013/07/11 6:31), Jiri Kosina wrote:
> +/*
> + * text_poke_bp() -- update instructions on live kernel on SMP
> + * @addr:address to patch
> + * @opcode: opcode of new instruction
> + * @len: length to copy
> + * @handler: address to jump to when the temporary breakpoint is hit
> + *
> +
>
On Wed, May 22, 2013 at 07:03:05PM +0200, Jens Axboe wrote:
> On Wed, May 22 2013, Alexander Gordeev wrote:
> > On Wed, May 22, 2013 at 08:50:03AM +0900, Tejun Heo wrote:
> > > Hmm. I'd normally apply this patch but block layer is just
> > > growing multi-queue support and libata is likely
Hello,
I have following error while compiling new stable kernel 3.10:
CC kernel/fork.o
CC kernel/exec_domain.o
CC kernel/panic.o
CC kernel/printk.o
CC kernel/cpu.o
CC kernel/exit.o
CC kernel/itimer.o
make[1]: *** No rule to make target `kernel/timec
On Tue, Jul 9, 2013 at 10:41 PM, Jiri Kosina wrote:
> On Tue, 9 Jul 2013, Benjamin Tissoires wrote:
>
>> For those who wants to try, I have set up a project [1] to implement
>> part of the spec Nestor released. I implemented various features: list
>> devices paired to a receiver, pair/unpair a dev
On Thu, Jul 11, 2013 at 08:41:41AM +0100, Nick Dyer wrote:
> Mark Brown wrote:
> > On Fri, Jun 21, 2013 at 09:16:16AM -0700, Nick Dyer wrote:
> >> For some operations it does. For example updating the whole chip config
> >> (which is a common thing to want to do), it would turn a couple of write
>
On Wed, Jul 10, 2013 at 04:00:48PM +0200, Jonas Jensen wrote:
> +++ b/drivers/rtc/Makefile
> @@ -77,6 +77,7 @@ obj-$(CONFIG_RTC_DRV_MAX6902) += rtc-max6902.o
> obj-$(CONFIG_RTC_DRV_MAX77686) += rtc-max77686.o
> obj-$(CONFIG_RTC_DRV_MC13XXX)+= rtc-mc13xxx.o
> obj-$(CONFIG_RTC
On Wed, Jul 10, 2013 at 10:38:18AM -0600, Stephen Warren wrote:
> From: Stephen Warren
>
> Commit 24778be "spi: convert drivers to use bits_per_word_mask" removed
> what appeared to be redundant code from many drivers. However, it
> appears that in the spi-bitbang case, these functions are requir
On 11/07/13 11:04, Gleb Natapov wrote:
> On Wed, Jul 10, 2013 at 02:59:55PM +0200, Dominik Dingel wrote:
>> This patch enables async page faults for s390 kvm guests.
>> It provides the userspace API to enable, disable or get the status of this
>> feature. Also it includes the diagnose code, called
On Thu, Jul 11, 2013 at 12:28:20PM +0200, Konrad Vrba wrote:
> Hello,
> I have following error while compiling new stable kernel 3.10:
>
> CC kernel/fork.o
> CC kernel/exec_domain.o
> CC kernel/panic.o
> CC kernel/printk.o
> CC kernel/cpu.o
> CC kernel/exi
1 - 100 of 718 matches
Mail list logo
