On Tue, Sep 11, 2012 at 10:38:06PM +0200, Rafael J. Wysocki wrote:
> It turns out that there are ACPI BIOSes defining device objects with
> _PSx and without either _PSC or _PRx. For devices corresponding to
> those ACPI objetcs __acpi_bus_get_power() returns ACPI_STATE_UNKNOWN
> and their initial
Le Tue, 11 Sep 2012 16:23:19 -0600,
Stephen Warren a écrit :
> On 09/10/2012 02:39 AM, Sebastian Hesselbarth wrote:
> > From: Thomas Petazzoni
> >
> > The Armada 370 and XP SoCs have configurable muxing for a certain
> > number of their pins, controlled through a pinctrl driver.
>
> Hmmm. I'd
Le Tue, 11 Sep 2012 16:17:13 -0600,
Stephen Warren a écrit :
>
> +static struct mvebu_mpp_mode dove_mpp_modes[] = {
> + MPP_MODE(0,
> + MPP_FUNCTION(0x00, "gpio", NULL),
> + MPP_FUNCTION(0x02, "uart2", "rts"),
> + MPP_FUNCTION(0x03, "sdio0", "cd"),
> +
On Tue, 2012-09-11 at 22:57 -0700, Marc MERLIN wrote:
> On Wed, Sep 12, 2012 at 07:16:28AM +0200, Eric Dumazet wrote:
> > On Tue, 2012-09-11 at 16:25 -0700, Andrew Morton wrote:
> >
> > > Asking for a 256k allocation is pretty crazy - this is an operating
> > > system kernel, not a userspace appli
On 09/10/2012 04:13 AM, Ben Hutchings wrote:
> 3.2-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Trond Myklebust
>
> Fix the following Oops in 3.5.1:
>
> BUG: unable to handle kernel NULL pointer dereference at 0038
> IP:
Hi all,
Today's linux-next merge of the tegra tree got a conflict in
arch/arm/mach-tegra/devices.c arch/arm/mach-tegra/devices.h between
commits 2db4ddfe6e23 ("ARM: pmu: remove arm_pmu_type enumeration") from
the arm-perf tree and 1ba8216f0bc0 ("usb: move phy driver from mach-tegra
to drivers/usb"
From: Namhyung Kim
As a side effect of commit f5951d56a2ab ("perf hists browser: Use
perf_hpp__format functions") perf report TUI got a problem of not
refreshing the first character.
Since the previous patch restores the column width of "overhead" to 7
we can start at column 0 now.
Signed-off-b
From: Namhyung Kim
Current hpp format functions assume that the output will fit to 6
character including % sign (XX.YY%) so used "%5.2f%%" as a format
string. However it might be the case if collapsing resulted in a
single entry which has 100.00% (7 character) of period. In this case
the output
Hi all,
Today's linux-next merge of the tegra tree got a conflict in
drivers/usb/phy/tegra_usb_phy.c between commit 1ba8216f0bc0 ("usb: move
phy driver from mach-tegra to drivers/usb") from the usb tree and commit
b0e51927b1e5 ("ARM: tegra: remove useless includes of ") from
the tegra tree.
I fix
Hi,
On Wed, Sep 12, 2012 at 3:58 AM, Paul Walmsley wrote:
> Hi Kishon, Benoît,
>
> On Fri, 7 Sep 2012, Kishon Vijay Abraham I wrote:
>
>> Made *ocp2scp_usb_phy_phy_48m* as the main_clk for ocp2scp. Since this
>> ocp2scp module does not have any fck but does have a single opt_clock,
>> it is added
Mike Waychison writes:
> On Mon, Sep 10, 2012 at 3:59 PM, Michael S. Tsirkin wrote:
>> On Mon, Sep 10, 2012 at 01:37:06PM -0400, Mike Waychison wrote:
>>> On Mon, Sep 10, 2012 at 5:05 AM, Michael S. Tsirkin wrote:
>>> > On Tue, Jun 26, 2012 at 01:32:58PM -0700, Frank Swiderski wrote:
>>> >> This
sjur.brandel...@stericsson.com writes:
> I actually like this new approach better.
> It solves the issues Michael has pointed out, and we don't have to
> think through side effects of weired combination of feature bits.
Agreed.
Just one thing, should it depend on CONFIG_REMOTEPROC? And have
OMAP
"Michael S. Tsirkin" writes:
>> virtio: don't crash when device is buggy
>>
>> Because of a sanity check in virtio_dev_remove, a buggy device can crash
>> kernel. And in case of rproc it's userspace so it's not a good idea.
>> We are unloading a driver so how bad can it be?
>> Be less aggressive
Thomas Lendacky writes:
> I ran some TCP_RR and TCP_STREAM sessions, both host-to-guest and
> guest-to-host, with a form of the histogram patch applied against a
> RHEL6.3 kernel. The histogram values were reset after each test.
Hey, thanks! This is exactly what I wanted to see...
> 60 session
"Michael S. Tsirkin" writes:
> We have several options:
> 1. No memory overcommit feature. This is always the case ATM!
> 2. Do not hot-plug assigned device.
> 3. Hot-unplug assigned device.
> 4. Some assigned devices can be able to handle memory errors
>e.g. using ATS. Limit hotplug to these.
On Sat, 08 Sep 2012 23:05:43 +0900, Namhyung Kim wrote:
> On Fri, 7 Sep 2012 17:32:18 -0700, Arnaldo Carvalho de Melo wrote:
>> I folded the patch below so that we have the lines starting at column 1
>> like before, i.e. we were using " %5.2f" for the overhead and now you
>> changed it to "%5.2f".
Hi,
On Tue, Sep 11, 2012 at 10:02:48PM +, Paul Walmsley wrote:
>
> Hi Felipe
>
> Just tested these OMAP serial changes at commit
> e36851d0fa94b0f7802b3cc80406dbd3ef4f2f16 ("serial: omap: fix compile
> breakage"). There's good news and bad news...
>
> The good news is that after applying
On Tue, Sep 11, 2012 at 01:18:24PM +0800, Jerry wrote:
> Hi Kim,
>
> Thank you for your kindness. Let me clarify this:
>
> On ARM architecture, there are 32 bits physical addresses space. However,
> the addresses space is divided into 8 banks normally. Each bank
> disabled/enabled by a chip selec
On Wed, Sep 12, 2012 at 7:19 AM, Kuninori Morimoto
wrote:
> This patch fixes it
>
> Reported-by: Fengguang Wu
> Signed-off-by: Kuninori Morimoto
Hey you fix things quicker than I can read my mail :-) :-)
Thanks!
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscrib
On Wednesday 12 September 2012 08:51 AM, Mark Brown wrote:
> On Tue, Sep 11, 2012 at 12:13:20PM +0530, Shubhrajyoti D wrote:
>> > Currently in omap2_mcspi_txrx_dma the tx and the rx support is
>> > interleaved. Make the rx related code in omap2_mcspi_rx_dma
>> > and the tx related code omap2_mcspi_
> I will update simple table for this result in changelog in patch.
That would be good, thanks a lot for the testing!
Thanks,
Fengguang
--
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://v
On Wed, Sep 12, 2012 at 3:13 PM, Dave Airlie wrote:
> On Wed, Sep 12, 2012 at 8:58 AM, Rafael J. Wysocki wrote:
>> On Wednesday, September 12, 2012, Dave Airlie wrote:
>>> On Wed, Sep 12, 2012 at 7:32 AM, Alan Stern
>>> wrote:
>>> > On Tue, 11 Sep 2012, Rafael J. Wysocki wrote:
>>> >
>>> >> Hi,
From: Andi Kleen
When counting a process with perf stat -p check if the process died
and exit collection if yes.
Signed-off-by: Andi Kleen
---
tools/perf/builtin-stat.c |9 -
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/tools/perf/builtin-stat.c b/tools/perf/built
Replace the current (inefficient) for-loop with memcpy, to copy priomap.
Signed-off-by: Srivatsa S. Bhat
---
net/core/netprio_cgroup.c |9 -
1 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/net/core/netprio_cgroup.c b/net/core/netprio_cgroup.c
index fd339bb0..83bbd0e 1
The update_netdev_tables() function appears to be unnecessary, since the
write_update_netdev_table() function will adjust the priomaps as and when
required anyway. So drop the usage of update_netdev_tables() entirely.
Signed-off-by: Srivatsa S. Bhat
---
net/core/netprio_cgroup.c | 32
Hi Greg,
After merging the staging tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/hid/hid-sensor-hub.c: In function 'sensor_hub_probe':
drivers/hid/hid-sensor-hub.c:599:3: error: too few arguments to function
'mfd_add_devices'
Caused by commit 401ca24fb34a ("HID:
On 09/11/2012 05:12 PM, David Laight wrote:
>> -for (i = 0;
>> - old_priomap && (i < old_priomap->priomap_len);
>> - i++)
>> -new_priomap->priomap[i] = old_priomap->priomap[i];
>> +if (old_priomap) {
>> +old_len = old_priomap->priomap_len;
>> +
>> +
On Wed, Sep 12, 2012 at 12:17 AM, Stephen Warren wrote:
> the drivers in this patch seem to invert the data-structures a
> little - in other words, instead of defining a global list of functions,
> they define a list of groups, and for each group, list the functions
> that can be selected on to i
2012/9/12, Namjae Jeon :
> 2012/9/12, Fengguang Wu :
>> On Wed, Sep 12, 2012 at 08:12:40AM +0900, Namjae Jeon wrote:
>>> >>
>>> >> To be frank, no realistic NFS servers will use USB disk as backing
>>> >> storage. So that rational for reducing "initial" delays is weak.
>>> >> Continuous write perfo
Hi Axel,
On Wed, 12 Sep 2012 13:39:09 Axel Lin wrote:
> Seems this is a left over of commit 4382973
> "workqueue: deprecate flush[_delayed]_work_sync()"
It is, see https://lkml.org/lkml/2012/9/6/297 for a previous patch.
This should fix itself when Linus merges Tejun's workqueue changes and
pico
On Wed, Sep 12, 2012 at 07:16:28AM +0200, Eric Dumazet wrote:
> On Tue, 2012-09-11 at 16:25 -0700, Andrew Morton wrote:
>
> > Asking for a 256k allocation is pretty crazy - this is an operating
> > system kernel, not a userspace application.
> >
> > I'm wondering if this is due to a recent change
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in
drivers/staging/omap-thermal/omap-thermal-common.c between commit
76f726fb24bd ("Thermal: Remove tc1/tc2 in generic thermal layer") from
the thermal tree and commit 765a1939a364 ("staging: omap-thermal: fix
polling period sett
At 09/10/2012 09:52 PM, Vasilis Liaskovitis Wrote:
> Hi,
>
> On Mon, Sep 10, 2012 at 10:01:44AM +0800, Wen Congyang wrote:
>> At 09/10/2012 09:46 AM, Yasuaki Ishimatsu Wrote:
>>> Hi Wen,
>>>
>>> 2012/09/01 5:49, Andrew Morton wrote:
On Tue, 28 Aug 2012 18:00:07 +0800
we...@cn.fujitsu.com
Seems this is a left over of commit 4382973
"workqueue: deprecate flush[_delayed]_work_sync()"
This fixes below build warning:
CC [M] drivers/hid/hid-picolcd_fb.o
drivers/hid/hid-picolcd_fb.c: In function 'picolcd_exit_framebuffer':
drivers/hid/hid-picolcd_fb.c:611:2: warning: 'flush_delayed_w
On Wed, Sep 12, 2012 at 11:34 AM, James Morris wrote:
>
> - if (!err && len == hlen)
> - err = memcmp(out2, h, hlen);
> + if (err || len != hlen) {
> + err = -EINVAL;
> + goto err;
> + }
> +
> + err = memcmp(out2, h, hlen);
>
> err
Hi Greg,
Today's linux-next merge of the usb tree got a conflict in
drivers/usb/dwc3/gadget.c between commit f4a53c55117b ("usb: dwc3:
gadget: fix pending isoc handling") from the usb.current tree and commit
348e026fafe2 ("usb: dwc3: gadget: Fix sparse warnings") from the usb tree.
I fixed it up
Hi Greg,
Today's linux-next merge of the usb tree got a conflict in
drivers/usb/musb/tusb6010.c between commit ff41aaa3b6c1 ("usb: musb:
tusb6010: fix error path in tusb_probe()") from the usb.current tree and
commit 65b3d52d02a5 ("usb: musb: add musb_ida for multi instance
support") from the usb
When I hot-added CPUs and memories simultaneously using container driver,
all the hot-added CPUs were mistakenly assigned to node0.
Accoding to my DSDT, hot-added CPUs and memorys have PXM#1. So in my system,
these devices should be assigned to node1 as follows:
--- Expected result
ls /sys/device
Reposting: I realized that this series should have gone out to a broader list.
My apologies to those who those who will recieve a duplicate post.
Hello all,
I've been using this UIO driver for allocation/deallocation
of memory regions through an IOMMU via the dma-mapping API, but
it seems that i
This device extends the uio_pdrv_genirq driver to provide limited
dynamic memory allocation for UIO devices. This allows UIO devices
to use CMA and IOMMU allocated memory regions. This driver is based
on the uio_pdrv_genirq driver and provides the same generic interrupt
handling capabilities. Lik
This allows the VPU memory to be allocated dynamically only when it
is needed.
Signed-off-by: Damian Hobson-Garcia
---
arch/arm/mach-shmobile/setup-sh7372.c | 19 ++-
1 files changed, 14 insertions(+), 5 deletions(-)
diff --git a/arch/arm/mach-shmobile/setup-sh7372.c
b/arch/a
This rule
$IPTABLES -A RULE_0_in -j LOG --log-level notice --log-prefix "DENY in: "
result with linux 3.6-rc5
Sep 12 06:37:29 x kernel: <5>DENY in: IN=eth0 OUT= MAC=...
result with linux 3.5.3 and older:
Sep 9 10:43:01 x kernel: DENY in: IN=eth0 OUT= MAC..
Thanks
--
6e20a0a429bd4dc07d6de16d9c247270e04e4aa0
(gpio: pcf857x: enable gpio_to_irq() support)
added new smatch warnings
drivers/gpio/gpio-pcf857x.c:288 pcf857x_probe() error: we previously \
assumed 'pdata' could be null (see line 277)
drivers/gpio/gpio-pcf857x.c:364 pcf857x_probe() warn: variabl
On Tue, 2012-09-11 at 16:25 -0700, Andrew Morton wrote:
> Asking for a 256k allocation is pretty crazy - this is an operating
> system kernel, not a userspace application.
>
> I'm wondering if this is due to a recent change, but I'm having trouble
> working out where the allocation call site is.
On Wed, Sep 12, 2012 at 8:58 AM, Rafael J. Wysocki wrote:
> On Wednesday, September 12, 2012, Dave Airlie wrote:
>> On Wed, Sep 12, 2012 at 7:32 AM, Alan Stern
>> wrote:
>> > On Tue, 11 Sep 2012, Rafael J. Wysocki wrote:
>> >
>> >> Hi,
>> >>
>> >> On Tuesday, September 11, 2012, Dave Airlie wrot
On Tue, 2012-09-11 at 17:59 +0200, Oleg Nesterov wrote:
> But, again, the caller does free_note_info(), so why
> elf_note_info_init()
> tries to handle the kmalloc failures? Afaics, we can simplify the code
> and fix the bug.
>
> What do you think about the patch below?
Looks reasonable and neat
Hi Tejun,
Today's linux-next merge of the workqueues tree got a conflict in
drivers/video/omap2/displays/panel-taal.c between commit 5e56ad44b4d2
("OMAPDSS: Taal: use devm_* functions") from the omap_dss2 tree and
commit 203b42f73174 ("workqueue: make deferrable delayed_work initializer
names cons
The output 'git describe' is relative to the immediate preceding tag.
When the immediate tag preceding the HEAD is a private tag,
setlocalversion extracts information with respect to the private tag and
wrongly reports them with respect to Linux tag.
Fixing this to extract information with respect
Hi,
3 of my test boxes running v3.5 kernel become unaccessible and I find
two of them kept emitting this dmesg:
vmx_handle_exit: unexpected, valid vectoring info (0x8b0e) and exit reason
is 0x31
The other one has froze and the above lines are the last dmesg.
Any ideas?
Thanks,
Fengguang
--
On Tue, Sep 11, 2012 at 9:06 PM, Anton Vorontsov
wrote:
> On Tue, Sep 11, 2012 at 08:42:46PM -0700, Colin Cross wrote:
> [...]
>> > The "problem" is in the last step. If we exit NMI without making UART
>> > know that we're done with the interrupt, we will reenter the NMI
>> > immediately, even wit
Hi all,
Today's linux-next merge of the kvm tree got a conflict in
arch/x86/kvm/i8259.c between commit 749c59fd15b2 ("KVM: PIC: fix use of
uninitialised variable") from Linus' tree and commit ec798660cf72 ("KVM:
cleanup pic reset") from the kvm tree.
The latter removed the code fixed by the forme
On Sun, Sep 09, 2012 at 04:50:47PM -0400, Jeff Garzik wrote:
> On 09/09/2012 04:36 PM, Hugh Dickins wrote:
> >On Sun, Sep 9, 2012 at 1:28 PM, Jeff Garzik wrote:
> >>I'll send Linus a patch to disable.
> >
> >Thanks, but no, the change in question hasn't reached Linus yet, it's
> >just a linux-next
On 09/11/2012 05:00 PM, Seiji Aguchi wrote:
Thomas,
Please review my patch as we talked in Plumbers.
Is there any measurable latency added here? These are some of the most
performance- (or at least latency-)critical paths in the kernel.
-hpa
--
H. Peter Anvin, Intel Open Source T
On 09/06/2012 11:13 AM, Kees Cook wrote:
Instead of (or in addition to) kernel module signing, being able to reason
about the origin of a kernel module would be valuable in situations
where an OS already trusts a specific file system, file, etc, due to
things like security labels or an existing r
On Tue, Sep 11, 2012 at 08:42:46PM -0700, Colin Cross wrote:
[...]
> > The "problem" is in the last step. If we exit NMI without making UART
> > know that we're done with the interrupt, we will reenter the NMI
> > immediately, even without any new characters from the UART.
>
> The UART irq line sh
On Tue, 2012-09-11 at 19:41 -0700, David Sharp wrote:
> In order to promote interoperability between userspace tracers and ftrace,
> add a trace_clock that reports raw TSC values which will then be recorded
> in the ring buffer. Userspace tracers that also record TSCs are then on
> exactly the same
Hi Jiri,
Today's linux-next merge of the trivial tree got a conflict in
drivers/video/backlight/88pm860x_bl.c between commit a6ccdcd98c39 ("mfd:
88pm860x: Use REG resource for backlight") from the mfd tree and commit
e1c9ac420ef1 ("Revert "backlight: fix memory leak on obscure error
path"") from t
On Tue, Sep 11, 2012 at 8:32 PM, Anton Vorontsov
wrote:
> On Tue, Sep 11, 2012 at 03:15:40PM +0100, Alan Cox wrote:
>> Anton Vorontsov wrote:
>> > This patch implements a new callback: clear_irqs. It is used for the
>>
>> This bit I still really don't like. I would like to know what the generic
>
Please apply for v3.6.
The following changes since commit 0bd1189e239c76eb3a50e458548fbe7e4a5dfff1:
Linus Torvalds (1):
Merge branch 'for-3.6-fixes' of git://git.kernel.org/.../tj/wq
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-s
On Tue, Sep 11, 2012 at 9:34 PM, Steven Rostedt wrote:
> On Sat, 2012-09-08 at 17:01 -0300, Ezequiel Garcia wrote:
>> This patch splits trace event initialization in two stages:
>> * ftrace enable
>> * sysfs event entry creation
>>
>> This allows to capture trace events from an earlier point
>>
On 09/12/2012 10:03 AM, Hugh Dickins wrote:
> What brought me to look at it was hitting "BUG at mm/huge_memory.c:1842!"
> running tmpfs kbuild swapping load (with memcg's memory.limit_in_bytes
> forcing out to swap), while I happened to have CONFIG_NUMA=y.
>
> That's the VM_BUG_ON(*hpage) on entr
On Tue, Sep 11, 2012 at 03:15:40PM +0100, Alan Cox wrote:
> Anton Vorontsov wrote:
> > This patch implements a new callback: clear_irqs. It is used for the
>
> This bit I still really don't like. I would like to know what the generic
> IRQ folks thing about it and if Thomas Gleixner has any brill
On Fri, 7 Sep 2012, Kent Yoder wrote:
> > > James did accept my pull request, so these are already in
> > > security-next...
> >
> > For the driver itself, it's not a big issue (though I did found issue
> > while reviewing it so it will need another round of updates). For the
> > code that chan
On Wed, 2012-09-12 at 03:43 +0530, raghu.prabh...@gmail.com wrote:
> Ratelimited printk will be useful in printing xfs messages which are otherwise
> not required to be printed always due to their high rate (to prevent kernel
> ring
> buffer from overflowing), while at the same time required to be
On Tue, Sep 11, 2012 at 12:13:20PM +0530, Shubhrajyoti D wrote:
> Currently in omap2_mcspi_txrx_dma the tx and the rx support is
> interleaved. Make the rx related code in omap2_mcspi_rx_dma
> and the tx related code omap2_mcspi_tx_dma and call the functions.
I'd ideally like some testing from the
On Tue, 4 Sep 2012, Kent Yoder wrote:
> acpi_os_map_memory expects its return value to be in the __iomem address
> space. Tag the variable we're using as such and use memcpy_fromio to
> avoid further sparse warnings.
>
> Signed-off-by: Kent Yoder
Applied to
git://git.kernel.org/pub/scm/linux/ke
On Tue, Sep 11, 2012 at 6:32 PM, Arnd Bergmann wrote:
> Platform data for device drivers should be defined in
> include/linux/platform_data/*.h, not in the architecture
> and platform specific directories.
>
> This moves such data out of the spear include directories
>
> Signed-off-by: Arnd Bergma
Hi,
We've had some incidents with people destroying Fedore 17 installs
(to the point of reinstall) by installing a kernel tarball generated with
make tar*-pkg
The problem is that the tarball includes /lib/{modules,firmware},
but on FC17 /lib is a symlink. tar when it unpacks the tarball
replace
The block comment style in net/ and drivers/net is non-standard.
Document it.
Signed-off-by: Joe Perches
---
> This conflicts with the preferred style for long (multi-line) comments
> documented in
> ./Documentation/CodingStyle. If this is the way comments should be done in
> the
> networking
On Mon, 10 Sep 2012, Rusty Russell wrote:
> Kees Cook writes:
> > On Fri, Sep 7, 2012 at 10:12 AM, Mimi Zohar
> > wrote:
> >> This method is a consistent and extensible approach to verifying the
> >> integrity of file data/metadata, including kernel modules. The only
> >> downside to this appro
On Sat, 8 Sep 2012, Heiko Carstens wrote:
> >From cea999ef4e68e23c70e64baf054768bdebe15e1b Mon Sep 17 00:00:00 2001
> From: Heiko Carstens
> Date: Sat, 8 Sep 2012 10:23:42 +0200
> Subject: [PATCH] samples/seccomp: fix 31 bit build on s390
>
> On s390 the flag to force 31 builds is -m31 instead o
On Tue, Sep 11, 2012 at 08:33:43PM +0530, Ashish Chavan wrote:
> +/* LDO voltage level value */
> +static const char * const da9055_ldo_lvl_select_txt[] = {
> + "1.05V", "1.1V", "1.2V", "1.4V"
> +};
> +static const struct soc_enum da9055_ldo_lvl_select =
> + SOC_ENUM_SINGLE(DA9055_LDO_CTR
Hi Samuel,
Today's linux-next merge of the mfd tree got a conflict in
Documentation/devicetree/bindings/regulator/tps6586x.txt between commit
7f852e0584f6 ("regulator: tps6586x: correct vin pin for sm0/sm1/sm2")
from Linus' tree and commit 566a725dff0d ("mfd: dt: tps6586x: Add power
off control")
Because the "tsc" clock isn't in nanoseconds, the ring buffer must be
reset when changing clocks so that incomparable timestamps don't end up
in the same trace.
Tested: Confirmed switching clocks resets the trace buffer.
Signed-off-by: David Sharp
---
kernel/trace/trace.c |8
1 file
On Wed, Sep 12, 2012 at 03:28:42AM +0900, OGAWA Hirofumi wrote:
>
> If bdi has BDI_CAP_NO_WRITEBACK, bdi_forker_thread() doesn't start
> writeback thread. This means there is no consumer of work item made
> by bdi_queue_work().
>
> This adds to checking of !bdi_cap_writeback_dirty(sb->s_bdi) befo
With the addition of the "tsc" clock, formatting timestamps to look like
fractional seconds is misleading. Mark clocks as either in nanoseconds or
not, and format non-nanosecond timestamps as decimal integers.
Tested:
$ cd /sys/kernel/debug/tracing/
$ cat trace_clock
[local] global tsc
$ echo sche
In order to promote interoperability between userspace tracers and ftrace,
add a trace_clock that reports raw TSC values which will then be recorded
in the ring buffer. Userspace tracers that also record TSCs are then on
exactly the same time base as the kernel and events can be unambiguously
inter
As discussed at Plumbers, here are my patches to add a TSC clock to ftrace.
Also noticeable is that the formatting patch improves the output of the
"counter" clock.
David Sharp (3):
tracing,x86: add a TSC trace_clock; reset buffer on clock change
tracing: reset ring buffer when changing trace_
Hi all,
I would like to promote zram/zsmalloc from staging tree.
I already tried it https://lkml.org/lkml/2012/8/8/37 but I didn't get
any response from you guys.
I think zram/zsmalloc's code qulity is good and they
are used for many embedded vendors for a long time.
So it's proper time to promot
On 09/12/2012 10:03 AM, Hugh Dickins wrote:
> On Mon, 13 Aug 2012, Xiao Guangrong wrote:
>
>> They are used to abstract the difference between NUMA enabled and NUMA
>> disabled
>> to make the code more readable
>>
>> Signed-off-by: Xiao Guangrong
>> ---
>> mm/huge_memory.c | 166
>> ++
On Tue, 2012-09-11 at 09:43 +0200, Bjørn Mork wrote:
> Thomas Schäfer writes:
>
> > Am Montag, 10. September 2012 um 00:42:24 schrieb Ben Hutchings:
> >> 3.2-stable review patch. If anyone has any objections, please let me know.
> >
> >
> >
> > referring to
> >
> > http://www.spinics.net/lists/l
On Tue, 11 Sep 2012 20:53:08 -0300, Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> Wrappers to the libtraceevent routines, so that we can further reduce
> the surface contact perf builtins have with it.
I just realized that this breaks the python extension:
namhyung@sejong:
Arnd Bergmann wrote:
>
> Platform data for device drivers should be defined in
> include/linux/platform_data/*.h, not in the architecture
> and platform specific directories.
>
> This moves such data out of the samsung include directories
>
> Signed-off-by: Arnd Bergmann
> Cc: Kukjin Kim
Yeah
From: Namhyung Kim
The commit a116e05dcf61 ("perf sched: Remove die() calls") replaced
die() call to pr_debug + return -1, but it should be pr_err otherwise
it'll not show up unless -v option is given. Fix it.
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-sched.c | 14 +++---
1 f
From: Namhyung Kim
The commit 32c7f7383a09 ("perf test: Remove die() calls") replaced
die() call to pr_debug + return -1, but it should be pr_err otherwise
it'll not show up unless -v option is given. Fix it.
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-test.c | 8
1 file chang
On Mon, 13 Aug 2012, Xiao Guangrong wrote:
> They are used to abstract the difference between NUMA enabled and NUMA
> disabled
> to make the code more readable
>
> Signed-off-by: Xiao Guangrong
> ---
> mm/huge_memory.c | 166
> --
> 1 files
On Tue, 11 Sep 2012 20:53:08 -0300, Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> Wrappers to the libtraceevent routines, so that we can further reduce
> the surface contact perf builtins have with it.
[snip]
> +char *perf_evsel__strval(struct perf_evsel *evsel, struct perf_
On 09/11/2012 06:18 PM, Yasuaki Ishimatsu wrote:
> Hi Lai,
>
> 2012/09/11 18:44, Lai Jiangshan wrote:
>> On 09/11/2012 08:40 AM, Yasuaki Ishimatsu wrote:
>>> Hi Lai,
>>>
>>> Using memory_online to hot-added node's memory, the following kernel
>>> messages
>>> were shown. Is this a known issue?
>>
On Tue, 11 Sep 2012, Hugh Dickins wrote:
> > > This does revert 2.6.27's dfe195fb79e88 ("mm: fix uninitialized variables
> > > for find_vma_prepare callers"), but it looks like gcc 4.3.0 was one of
> > > those releases too eager to shout about uninitialized variables: only
> > > copy_vma() warns w
[1] reporeted that lowmem pages could be replaced by
highmem pages during migration of CMA and fixed.
Quote from [1]'s description
"
The filesystem layer expects pages in the block device's mapping to not
be in highmem (the mapping's gfp mask is set in bdget()), but CMA can
currently r
__alloc_contig_migrate_alloc can be used by memory-hotplug so
refactor out(move + rename as a common name) it into
page_isolation.c.
Cc: Kamezawa Hiroyuki
Cc: Yasuaki Ishimatsu
Cc: Michal Nazarewicz
Cc: Marek Szyprowski
Cc: Wen Congyang
Signed-off-by: Minchan Kim
---
This patch is intended
On 12/09/12 00:50, Artem Bityutskiy wrote:
On Tue, 2012-09-11 at 16:44 +0200, Lars-Peter Clausen wrote:
On 09/10/2012 02:39 AM, Russell King - ARM Linux wrote:
On Mon, Sep 10, 2012 at 08:20:21AM +0800, Mark Brown wrote:
[...]
OK, that's what I'd thought was going on - it was the fact that you'
On 09/11/2012 10:05 PM, Jiri Olsa wrote:
> On Mon, Sep 10, 2012 at 03:53:51PM +0800, Yan, Zheng wrote:
>> From: "Yan, Zheng"
>>
>
> SNIP
>
>> +int parse_events_add_pmu(struct list_head **_list, int *idx,
>> char *name, struct list_head *head_config)
>> {
>> struct per
> v2: update cgroups.txt instead of creating a new file
>
> Cc: Li Zefan
> Cc: Tejun Heo
> Cc: Hugh Dickins
> Cc: Hillf Danton
> Cc: Lennart Poettering
> Signed-off-by: Aristeu Rozanski
>
Acked-by: Li Zefan
> ---
> Documentation/cgroups/cgroups.txt | 24 ++--
> 1 f
On Tue, 11 Sep 2012 18:03:10 -0700, Arnaldo Carvalho de Melo wrote:
> Em Wed, Sep 12, 2012 at 09:24:33AM +0900, Namhyung Kim escreveu:
>> Hi, Arnaldo
>>
>> On Tue, 11 Sep 2012 20:52:53 -0300, Arnaldo Carvalho de Melo wrote:
>> > From: Arnaldo Carvalho de Melo
>> >
>> > Just use pr_err() + return
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-
> ow...@vger.kernel.org] On Behalf Of Joe Perches
> Sent: Tuesday, September 11, 2012 5:48 PM
> To: Andrew Morton
> Cc: Andy Whitcroft; David Miller; LKML; netdev
> Subject: [PATCH] checkpatch: Check networking specif
On Wed, Sep 12, 2012 at 01:55:52AM +0100, Meredydd Luff wrote:
> Al (in particular): I've reworked this on top of your generic
> execve() changes, as well as incorporating feedback from HPA.
> Could you take another look please (and merge if all is well)?
>
> [v3: now rebased onto signal.git#execv
-Original Message-
From: Bjorn Helgaas [mailto:bhelg...@google.com]
Sent: Tuesday, September 11, 2012 4:35 PM
To: Jiang Wang
Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Chaitanya Lala;
Francis St. Amant; Jiang Wang
Subject: Re: [PATCH 1/1] pci-iov: Fix warnings when CONF
On Tue, 11 Sep 2012 20:53:07 -0300, Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> So that we can remove all the globals.
>
> Before:
>
>text data bss dec hex filename
> 1586833110368 1438600 3135801 2fd939 /tmp/oldperf
>
> After:
>
>text
On Fri, Sep 07, 2012 at 11:16:07AM -0400, Steven Rostedt wrote:
> On Fri, 2012-09-07 at 07:47 -0700, Josh Triplett wrote:
> > On Fri, Sep 07, 2012 at 07:24:41AM -0700, Paul E. McKenney wrote:
> > > On Thu, Sep 06, 2012 at 11:09:40PM -0700, Josh Triplett wrote:
> > > > On Thu, Sep 06, 2012 at 03:54:
1 - 100 of 561 matches
Mail list logo
