Support multi-buffer on uprobe-based dynamic events by
using ftrace_event_file.
This patch is based kprobe-based dynamic events multibuffer
support work initially, commited by Masami(commit 41a7dd420c),
but revised as below:
Oleg changed the kprobe-based multibuffer design from
array-pointers of
Since now we have pstore support for nvram in pseries, enable it
in the default config. With this config option enabled, pstore
infra-structure will be used to read/write the messages from/to nvram.
Signed-off-by: Aruna Balakrishnaiah
---
v3:
Move pstore config to right place
v2:
2013/6/23, Dmitry Monakhov :
> On Sun, 23 Jun 2013 15:07:36 +0900, Namjae Jeon
> wrote:
>> From: Namjae Jeon
Hi Dmitry.
> What is the difference between this ioctl and generic punch_hole?
It is different. Dave chinner already answered it.
>>
--
To unsubscribe from this list: send the line "unsubs
Trying to upgrade from 3.9.4 to 3.10-rc7, I encountered the following
persistent oops right around the time that init enters runlevel 2.
The exact timing fluctuates slightly; it doesn't appear to be a particular
init script triggering it.
Trying to boot single-user, it occurred immediately after p
2013/6/24, Andreas Dilger :
> On 2013-06-23, at 0:07, Namjae Jeon wrote:
>
>> From: Namjae Jeon
>>
>> This patch series introduces 2 new ioctls for ext4.
>>
>> Truncate_block_range ioctl truncates blocks from source file.
>
Hi. Andreas.
> How is this different from fallocate(FALLOC_FL_PUNCH_HOLE)
Hi Michael,
On Monday 24 June 2013 06:51 AM, Michael Neuling wrote:
Enable PSTORE in pseries_defconfig
Please add a "why" to your changelogs eg. "Now we have pstore support for
nvram on pseries, enable it in the default config"
"Why" you are changing something is more important than "what", si
On Sun, Jun 23, 2013 at 07:15:39PM +0530, Srivatsa S. Bhat wrote:
> Once stop_machine() is gone from the CPU offline path, we won't be able
> to depend on disabling preemption to prevent CPUs from going offline
> from under us.
>
> Use the get/put_online_cpus_atomic() APIs to prevent CPUs from goi
On 06/20/2013 08:57 PM, Alexandre Belloni wrote:
> The Nuvoton NAU7802 ADC is a 24-bit 2-channels I2C ADC, with adjustable
> gain and sampling rates.
>
> Signed-off-by: Alexandre Belloni
> Signed-off-by: Maxime Ripard
> ---
> .../bindings/iio/adc/nuvoton-nau7802.txt | 17 +
> drivers
Since now we have pstore support for nvram in pseries, enable it
in the default config. With this config option enabled, pstore
infra-structure will be used to read/write the messages from/to nvram.
Signed-off-by: Aruna Balakrishnaiah
---
arch/powerpc/configs/pseries_defconfig |1 +
1 file c
Hi,
On Mon, Jun 24, 2013 at 11:01:56AM +0530, Kishon Vijay Abraham I wrote:
> >>@@ -397,9 +407,10 @@ static int omap2430_musb_init(struct musb *musb)
> >>if (glue->status != OMAP_MUSB_UNKNOWN)
> >>omap_musb_set_mailbox(glue);
> >>
> >>- usb_phy_init(musb->xceiv);
> >>+ phy_init
On Wednesday 19 June 2013 02:52 AM, Sylwester Nawrocki wrote:
Hi Kishon,
I've noticed there is a little inconsistency between the code and documentation.
On 06/13/2013 10:43 AM, Kishon Vijay Abraham I wrote:
+3. Creating the PHY
+
+The PHY driver should create the PHY in order for other periph
Callers of skb_seq_read() are currently forced to call skb_abort_seq_read()
even when consuming all the data because the last call to skb_seq_read (the
one that returns 0 to indicate the end) fails to unmap the last fragment page.
With this patch callers will be allowed to traverse the SKB data by
On 16 April 2013 15:37, Daniel J Blueman wrote:
> When using e4defrag on a ext4 filesystem created a month ago, I ran
> into this fatal page fault [1]
> while running e4defrag on 3.9-rc6 (Ubuntu mainline).
>
> e2fsdump output is at http://quora.org/2012/e2fsdump.txt ; let me know
> if you need an
nvram_compress() and zip_oops() is used by the nvram_pstore_write
API to compress oops messages hence re-organise the functions
accordingly to avoid forward declarations.
Signed-off-by: Aruna Balakrishnaiah
---
arch/powerpc/platforms/pseries/nvram.c | 104
1 fil
The patch set supports compression of oops messages while writing to NVRAM,
this helps in capturing more of oops data to lnx,oops-log. The pstore file
for oops messages will be in decompressed format making it readable.
In case compression fails, the patch takes care of copying the header added
by
pstore_get_header_size will return the size of the header added by pstore
while logging messages to the registered buffer.
Signed-off-by: Aruna Balakrishnaiah
---
fs/pstore/platform.c |7 ++-
include/linux/pstore.h |6 ++
2 files changed, 12 insertions(+), 1 deletion(-)
diff -
The patchset takes care of compressing oops messages while writing to NVRAM,
so that more oops data can be captured in the given space.
big_oops_buf (2.22 * oops_data_sz) is allocated for compression.
oops_data_sz is oops header size less of oops partition size.
Pstore will internally call kmsg_d
> > root@amd:~# dd if=/dev/sda4 of=/dev/zero bs=1 skip=8958947328
> > > dd: reading `/dev/sda4': Input/output error
> > > 0+0 records in
> > > 0+0 records out
> > > 0 bytes (0 B) copied, 5.05805 s, 0.0 kB/s
> >
> > I once noticed a similar problem. The trouble is that the kernel
> > always seems to
On 21 June 2013 18:43, Rafael J. Wysocki wrote:
> Well, to be honest, I don't like the whole thing. The more changes you need
> to make to the common code to support it, the worse.
You meant you didn't like this patch completely? Or the idea that
I gave?
Getting the new frequency would be very
These logs come from tboot (Trusted Boot, an open source,
pre-kernel/VMM module that uses Intel TXT to perform a
measured and verified launch of an OS kernel/VMM.).
Signed-off-by: Qiaowei Ren
---
arch/x86/kernel/tboot.c | 72 +++
1 file changed, 72 i
Hi, Rafael
When can this patch be merged?
2013/6/19 Xiaoguang Chen :
> On 06/19/2013 03:55 PM, Viresh Kumar wrote:
>>
>> On 19 June 2013 12:30, Xiaoguang Chen wrote:
>>>
>>> Cpufreq governor's stop and start operation should be kept in sequence.
>>> If not, there will be unexpected behavior, for
Driver for non-standard on-chip ethernet device ARC EMAC 10/100,
instantiated in some legacy ARC (Synopsys) FPGA Boards such as
ARCAngel4/ML50x.
Signed-off-by: Alexey Brodkin
Cc: Andy Shevchenko
Cc: Francois Romieu
Cc: Joe Perches
Cc: Vineet Gupta
Cc: Mischa Jonker
Cc: Arnd Bergmann
Cc: Gr
Ping!
FYI, I rebased the perf/cleanup branch on top of current acme/perf/core.
Thanks,
Namhyung
2013-06-04 PM 2:20, Namhyung Kim wrote:
Hello,
This patchset is a resend version of previous work and basis of
upcoming perf ftrace patchset. Although I saw no issue on this series
when I posted
On 23 June 2013 04:38, Heiko Stübner wrote:
> Commit 5070158804b5 (cpufreq: rename index as driver_data in
> cpufreq_frequency_table) renamed the index field to driver_data.
>
> But it seems some uses in the s3c2416 driver were forgotten.
>
> So convert the last index users to read driver_data.
>
Hi Rafael,
This is part of my patchset "CPUFreq: Fix {PRE|POST}CHANGE notification
sequence". It contains changes specific to cpufreq core and ARM drivers.
I have left changes to non-ARM cpufreq drivers from this pull request. See if
you can take them for 3.11.
The following changes since commit
Hi Mike,
Today's linux-next merge of the clk tree got a conflict in
drivers/clk/samsung/clk-exynos4.c between commit 6082f908b060 ("clk:
exynos4: Staticize local symbols") from the samsung tree and commit
82ba93b27cf5 ("clk: exynos4: Fix clock aliases for cpufreq related
clocks") from the clk tree
Hi,
On Tuesday 18 June 2013 03:17 PM, Felipe Balbi wrote:
Hi,
On Thu, Jun 13, 2013 at 02:13:57PM +0530, Kishon Vijay Abraham I wrote:
Use the generic PHY framework API to get the PHY. The usb_phy_set_resume
and usb_phy_set_suspend is replaced with power_on/get_sync and
power_off/put_sync to al
Hi,
On Fri, 21 Jun 2013 10:24:44 -0500 Suman Anna wrote:
>
> On 06/21/2013 02:36 AM, Arnd Bergmann wrote:
> > On Friday 21 June 2013, Tony Lindgren wrote:
> >>> I wonder if this mess is caused by the fact that I did the revert
> >>> instead of rebuilding our for-next and dropping the merge in the
Hi,
On Saturday 22 June 2013 06:42 PM, Laxman Dewangan wrote:
On Friday 21 June 2013 07:30 PM, Kishon Vijay Abraham I wrote:
On Friday 21 June 2013 06:55 PM, Laxman Dewangan wrote:
On Thursday 20 June 2013 08:56 PM, Kishon Vijay Abraham I wrote:
Hi,
On Thursday 20 June 2013 08:14 PM, Laxman
On Mon, 2013-06-24 at 13:52 +1000, David Gibson wrote:
> On Sat, Jun 22, 2013 at 08:28:06AM -0600, Alex Williamson wrote:
> > On Sat, 2013-06-22 at 22:03 +1000, David Gibson wrote:
> > > On Thu, Jun 20, 2013 at 08:55:13AM -0600, Alex Williamson wrote:
> > > > On Thu, 2013-06-20 at 18:48 +1000, Alex
On Friday 21 June 2013 11:43 PM, Mike Turquette wrote:
> Quoting Ambresh K (2013-06-17 01:39:44)
>> From: Ambresh K
>>
>> clk_ops's .get_parent member data return's signed value.
>>
>> Signed-off-by: Ambresh K
>
> Unsurprisingly I get the following errors when building
> multi_v7_defconfig:
>
On Mon, Jun 24, 2013 at 11:49:49AM +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2013-06-21 at 09:54 -0700, Guenter Roeck wrote:
>
> > > v2: Ensure that PCI bus fixup code has been executed before calling
> > > device setup code.
> > >
> > Hi Ben,
> >
> > any comments/feedback on this appro
On Sun, Jun 23, 2013 at 5:40 PM, Rafael J. Wysocki wrote:
> On Sunday, June 23, 2013 04:04:52 PM Yinghai Lu wrote:
>> On Sun, Jun 23, 2013 at 2:42 PM, Rafael J. Wysocki wrote:
...
>> > Ah, I overlooked the fact that each dock station is on its own
>> > dependent_list
>> > and can also be on anot
On 06/23/2013 07:56 PM, Ren Qiaowei wrote:
>>
> Well, I guess that I can use iomem related interface to fix these
> warnings caused by sparse.
>
And you SHOULD. Passing around pointers to I/O space without even
annotating them isn't really very clean.
-hpa
--
To unsubscribe from this
On 24/06/2013 04:44, David Miller wrote:
From: Eliezer Tamir
Date: Wed, 19 Jun 2013 13:04:21 +0300
One question: do we need in sock_poll() to test that sock->sk is not null?
(Thanks to Willem de Bruijn for pointing this out.)
We should not have to.
Please clean up various things in this pat
From: Guenter Roeck
Add gpio support for the on-board PLD found on some Kontron embedded modules.
Originally-From: Michael Brunner
Signed-off-by: Guenter Roeck
Signed-off-by: Kevin Strasser
Acked-by: Darren Hart
Reviewed-by: Linus Walleij
---
drivers/gpio/Kconfig | 12 +++
drivers/
Add watchdog timer support for the on-board PLD found on some Kontron embedded
modules.
Originally-From: Michael Brunner
Signed-off-by: Kevin Strasser
Acked-by: Guenter Roeck
Acked-by: Darren Hart
---
drivers/watchdog/Kconfig | 11 +
drivers/watchdog/Makefile |1 +
drivers/watc
Add i2c support for the on-board PLD found on some Kontron embedded
modules.
Originally-From: Michael Brunner
Signed-off-by: Kevin Strasser
Acked-by: Guenter Roeck
Acked-by: Darren Hart
---
drivers/i2c/busses/Kconfig | 10 +
drivers/i2c/busses/Makefile |1 +
drivers/i2c/busses/
Add core MFD driver for the on-board PLD found on some Kontron embedded
modules. The PLD device may provide functions like watchdog, GPIO, UART
and I2C bus.
The following modules are supported:
* COMe-bIP#
* COMe-bPC2 (ETXexpress-PC)
* COMe-bSC# (ETXexpress-SC T#)
*
Changes since v2:
-Change Michael's "Signed-off-by" to "Originally-From" in all patches
-Add "From: Guenter Roeck " to gpio patch
Guenter Roeck (1):
gpio: Kontron PLD gpio driver
Kevin Strasser (3):
mfd: Kontron PLD mfd driver
i2c: Kontron PLD i2c bus driver
watchdog: Kontron PLD watchdog
On Mon, 2013-06-24 at 13:54 +1000, David Gibson wrote:
> > DDW means an API by which the guest can request the creation of
> > additional iommus for a given device (typically, in addition to the
> > default smallish 32-bit one using 4k pages, the guest can request
> > a larger window in 64-bit spac
On Fri, Jun 21, 2013 at 8:01 PM, Eduardo Valentin
wrote:
> On 20-06-2013 22:01, amit daniel kachhap wrote:
>> Hi Eduardo,
>>
>> On Thu, Jun 20, 2013 at 1:25 AM, Eduardo Valentin
>> wrote:
>>> On 17-06-2013 02:46, Amit Daniel Kachhap wrote:
This patch adds some extra register bitfield definat
On Sat, Jun 22, 2013 at 08:28:06AM -0600, Alex Williamson wrote:
> On Sat, 2013-06-22 at 22:03 +1000, David Gibson wrote:
> > On Thu, Jun 20, 2013 at 08:55:13AM -0600, Alex Williamson wrote:
> > > On Thu, 2013-06-20 at 18:48 +1000, Alexey Kardashevskiy wrote:
> > > > On 06/20/2013 05:47 PM, Benjami
On Sun, Jun 23, 2013 at 09:28:13AM +1000, Benjamin Herrenschmidt wrote:
> On Sat, 2013-06-22 at 22:03 +1000, David Gibson wrote:
> > I think the interface should not take the group fd, but the container
> > fd. Holding a reference to *that* would keep the necessary things
> > around. But more to
On 06/22/2013 02:25 AM, Tejun Heo wrote:
Hey,
On Fri, Jun 21, 2013 at 05:19:48PM +0800, Tang Chen wrote:
* As memblock allocator can relocate itself. There's no point in
avoiding setting NUMA node while parsing and registering NUMA
topology. Just parse and register NUMA info and later t
On Mon, 24 Jun 2013, majianpeng wrote:
> Because in func queue_con_delay, it will call con->ops->get(con).
> So if we cancel the work successfully,we must call con->ops->put(con).
> Otherwise some resource can't free like 'struct ceph_mds_session'.
>
> Signed-off-by: Jianpeng Ma
Looks good, appl
On 06/23/2013 10:26 PM, Michael S. Tsirkin wrote:
> get user pages might fail partially in macvtap zero copy
> mode. To recover we need to put all pages that we got,
> but code used a wrong index resulting in double-free
> errors.
>
> Reported-by: Brad Hubbard
> Signed-off-by: Michael S. Tsirkin
On 06/23/2013 10:19 PM, Michael S. Tsirkin wrote:
> get user pages might fail partially in tun zero copy
> mode. To recover we need to put all pages that we got,
> but code used a wrong index resulting in double-free
> errors.
>
> Reported-by: Brad Hubbard
> Signed-off-by: Michael S. Tsirkin
> --
On 06/20/2013 10:18 AM, Alex Shi wrote:
> Resend patchset for more convenient pick up.
> This patch set combine 'use runnable load in balance' serials and 'change
> 64bit variables to long type' serials. also collected Reviewed-bys, and
> Tested-bys.
>
> The only changed code is fixing load to l
On Mon, Jun 24, 2013 at 12:44:59PM +1000, Dave Chinner wrote:
>
> Hence, at minimum, this should be a fallocate() operation, not a ext4
> specific ioctl as it is relatively trivial to implement on most
> extent based filesystems.
The fallocate() uses a units of bytes for the offset and length; wo
On 06/23/2013 04:36 PM, Joe Perches wrote:
On Sun, 2013-06-23 at 15:54 +0800, Qiaowei Ren wrote:
These logs come from tboot (Trusted Boot, an open source,
pre-kernel/VMM module that uses Intel TXT to perform a
measured and verified launch of an OS kernel/VMM.).
[]
diff --git a/arch/x86/kernel/
On Thu, Jun 20, 2013 at 10:00 PM, Geremy Condra wrote:
> With this change dm-verity errors will cause uevents to be
> sent to userspace, notifying it that an error has occurred
> and potentially triggering recovery actions.
>
> Signed-off-by: Geremy Condra
> ---
> Changelog since v1:
> - Removed
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in
drivers/gpu/drm/drm_prime.c between commit ebc0bad4a05a ("drm/prime:
Honor requested file flags when exporting a buffer") from Linus' tree and
commit ca793f75d91d ("drm: move pinning/unpinning to buffer attach") from
the drm tree.
On Friday, June 21, 2013 11:15 PM, Arnd Bergmann wrote:
> On Friday 21 June 2013, Jason Cooper wrote:
> > On Fri, Jun 21, 2013 at 10:30:47AM +0200, Arnd Bergmann wrote:
> > > On Friday 21 June 2013, Thomas Petazzoni wrote:
> > > > I am by far not an expert on how to solve merge strategies and so on
On Sun, Jun 23, 2013 at 08:32:32PM -0400, Eric Sandeen wrote:
> On Jun 23, 2013, at 12:01 PM, Andreas Dilger wrote:
>
> > On 2013-06-23, at 0:07, Namjae Jeon wrote:
> >
> >> From: Namjae Jeon
> >>
> >> This patch series introduces 2 new ioctls for ext4.
> >>
> >> Truncate_block_range ioctl t
On Fri, Jun 21, 2013 at 11:24 PM, Mark Brown wrote:
> On Thu, Jun 20, 2013 at 03:31:07AM -0400, Chao Xie wrote:
>
> Looks pretty good, main thing here is that some of the functionality
> here appears to be reproducing standard code.
>
>> +static int pm800_set_voltage(struct regulator_dev *rdev,
>>
On Sun, Jun 23, 2013 at 06:04:52PM +0200, Oleg Nesterov wrote:
> Could you please do the following:
>
> 1. # cd /sys/kernel/debug/tracing
> # echo 0 >> options/function-trace
> # echo preemptirqsoff >> current_tracer
dammit.
WARNING: at include/linux/list.h:385 rb_hea
On 2013-06-23, at 0:07, Namjae Jeon wrote:
> From: Namjae Jeon
> The EXT4_IOC_TRUNCATE_BLOCK_RANGE removes the data blocks lying
> between [start, "start + length") and updates the logical block numbers
> of data blocks starting from "start + length" block to last block of file.
> This will main
Hi,
On 2013년 06월 22일 00:19, Mark Brown wrote:
> On Thu, Jun 20, 2013 at 04:03:26PM +0900, Jonghwa Lee wrote:
>> This patch adds new regulator driver to support max77693 chip's regulators.
>> max77693 has two linear voltage regulators and one current regulator which
>> can be controlled through I2C
On Fri, 2013-06-21 at 09:54 -0700, Guenter Roeck wrote:
> > v2: Ensure that PCI bus fixup code has been executed before calling
> > device setup code.
> >
> Hi Ben,
>
> any comments/feedback on this approach ?
>
> It is much less invasive than before and should address your concerns.
And a
From: Eliezer Tamir
Date: Wed, 19 Jun 2013 13:04:21 +0300
> One question: do we need in sock_poll() to test that sock->sk is not null?
> (Thanks to Willem de Bruijn for pointing this out.)
We should not have to.
Please clean up various things in this patch:
1) You have cases where you add ton
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem. You will get a few small
fixups for cyttsp, wacom and xpad driver
On Thu, Jun 20, 2013 at 8:51 PM, Jiri Slaby wrote:
> On 06/20/2013 02:28 PM, tingwei liu wrote:
>> Hi, dears:
>>
>> On Suse 11 sp2 3.0.13 kernel. After a few days, Nginx reply
>> packets with src ip 0.0.0.0 and dst ip 0.0.0.0。
>> Just like https://bbs.archlinux.org/viewtopic.php?id=12
From: Wedson Almeida Filho
Date: Fri, 14 Jun 2013 17:54:29 -0700
> Callers of skb_seq_read() are currently forced to call skb_abort_seq_read()
> even when consuming all the data because the last call to skb_seq_read (the
> one that returns 0 to indicate the end) fails to unmap the last fragment p
Hi Al,
After merging the vfs tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from arch/powerpc/xmon/xmon.c:41:0:
arch/powerpc/include/asm/spu.h:245:43: error: 'struct coredump_params' declared
inside parameter list [-Werror]
int (*coredump_extra_note
Because in func queue_con_delay, it will call con->ops->get(con).
So if we cancel the work successfully,we must call con->ops->put(con).
Otherwise some resource can't free like 'struct ceph_mds_session'.
Signed-off-by: Jianpeng Ma
---
net/ceph/messenger.c | 3 ++-
1 file changed, 2 insertions(+)
> Enable PSTORE in pseries_defconfig
Please add a "why" to your changelogs eg. "Now we have pstore support for
nvram on pseries, enable it in the default config"
"Why" you are changing something is more important than "what", since
you can always determine "what" is being changed, by looking at t
On Fri, 2013-06-21 at 17:07 -0400, Eduardo Valentin wrote:
> To reduce thermal maintenance load on Rui, SoC specific patches would be
> applied by me now. Rui Zhang will pull in these changes from time to time (at
> rc's). Additionally I would be sending him pull request for every merge
> window an
On Jun 23, 2013, at 12:01 PM, Andreas Dilger wrote:
> On 2013-06-23, at 0:07, Namjae Jeon wrote:
>
>> From: Namjae Jeon
>>
>> This patch series introduces 2 new ioctls for ext4.
>>
>> Truncate_block_range ioctl truncates blocks from source file.
>
> How is this different from fallocate(FALL
On Sunday, June 23, 2013 04:04:52 PM Yinghai Lu wrote:
> On Sun, Jun 23, 2013 at 2:42 PM, Rafael J. Wysocki wrote:
> > On Sunday, June 23, 2013 01:29:19 PM Yinghai Lu wrote:
> >> On Sun, Jun 23, 2013 at 12:57 PM, Yinghai Lu wrote:
> >> > On Sun, Jun 23, 2013 at 8:54 AM, Jiang Liu wrote:
> >> >>
The aliasing doesn't matter for Linux because we map the high and low half the
same.
Henrique de Moraes Holschuh wrote:
>On Sun, 23 Jun 2013, H. Peter Anvin wrote:
>> On 06/23/2013 02:56 PM, Henrique de Moraes Holschuh wrote:
>> >
>> > And as far as I could find from Intel's not-that-complete
On Sun, Jun 23, 2013 at 06:04:52PM +0200, Oleg Nesterov wrote:
> > [11018.927809] [sched_delayed] sched: RT throttling activated
> > [11054.897670] BUG: soft lockup - CPU#2 stuck for 22s!
> > [trinity-child2:14482]
> > [11054.898503] Modules linked in: bridge stp snd_seq_dummy tun fuse hidp
On Sun, 23 Jun 2013, H. Peter Anvin wrote:
> On 06/23/2013 02:56 PM, Henrique de Moraes Holschuh wrote:
> >
> > And as far as I could find from Intel's not-that-complete public
> > "specification updates", we are applying the errata workaround to a few more
> > processors than strictly required, b
On Sat, 22 Jun 2013 11:04:27 -1000 Linus Torvalds
wrote:
>
> So this is hopefully the last -rc in the series, and things have
> indeed be calming down finally, so assuming that trend continues,
> we're all good.
And you are all going to resist rebasing your trees (for no apparent
reason) this cl
On Fri, 2013-06-21 at 14:34 -0700, Arjan van de Ven wrote:
> On 6/21/2013 2:23 PM, Catalin Marinas wrote:
> >>
> >> oops sorry I misread your mail (lack of early coffee I suppose)
> >>
> >> I can see your point of having a thing for "did we ask for all the
> >> performance
> >> we could ask for" p
On Sun, Jun 23, 2013 at 2:42 PM, Rafael J. Wysocki wrote:
> On Sunday, June 23, 2013 01:29:19 PM Yinghai Lu wrote:
>> On Sun, Jun 23, 2013 at 12:57 PM, Yinghai Lu wrote:
>> > On Sun, Jun 23, 2013 at 8:54 AM, Jiang Liu wrote:
>> >> On 06/23/2013 05:25 AM, Rafael J. Wysocki wrote:
>> >>> From: Raf
On Sun, Jun 23, 2013 at 1:38 PM, H. Peter Anvin wrote:
> On 06/23/2013 01:30 PM, Dave Airlie wrote:
> Why do you care about performance when PAT is disabled?
>>
>> breaking old boxes just because, is just going to get reverted when I
>> get the first regression report that you broke old boxes.
Am Samstag, 15. Juni 2013, 16:23:24 schrieb Lars-Peter Clausen:
> The I2C client driver is not supposed to modify the client's driver
> pointer, this is handled by the I2C core.
>
> Signed-off-by: Lars-Peter Clausen
> ---
Nice catch.
Staged here:
https://github.com/PeterHuewe/linux-tpmdd/commit
This patch should fix the following bug reported by kbuild test robot.
fs/f2fs/recovery.c:233:33: sparse: incorrect type in assignment
(different base types)
parse warnings: (new ones prefixed by >>)
>> fs/f2fs/recovery.c:233:33: sparse: incorrect type in assignment (different
>> base types)
On 13-06-23 05:51 PM, Pavel Machek wrote:
> On Sun 2013-06-23 17:27:52, Mark Lord wrote:
>
>> For all existing drives out there, that's a 512 byte unit.
>
> I guessed so. (It would be good to actually document it, as well as
> documenting exactly why it is dangerous. Is it okay to send patches?)
On 6/23/13 3:09 AM, Ingo Molnar wrote:
If an IO driver is implemented properly then it will batch up requests for
the controller, and gets IRQ-notified on a (sub-)batch of buffers
completed.
If there's any spinning done then it should be NAPI-alike polling: a
single "is stuff completed" polling
On Fri, Jun 14, 2013 at 06:04:34PM -0700, Christian Kujau wrote:
> I just stumbled across another[0] issue when scripts/setlocalversion
> operates on a write-protected source tree. Back then[0] the source tree
> was on an read-only NFS share, so "test -w" was introduced before "git
> update-inde
On 06/23/2013 02:56 PM, Henrique de Moraes Holschuh wrote:
>
> And as far as I could find from Intel's not-that-complete public
> "specification updates", we are applying the errata workaround to a few more
> processors than strictly required, but since I have no idea how to write a
> test case, I
On Fri, Jun 21, 2013 at 04:20:40PM +0200, Stephane Eranian wrote:
> This patch series extends perf_events with the ability to sample
> physical data addresses. This is useful with the memory access
> sampling mode added just recently. In particular, it helps
> disambiguate data addresses between tw
On Sun, 23 Jun 2013, H. Peter Anvin wrote:
> On 06/23/2013 12:29 PM, Henrique de Moraes Holschuh wrote:
> > On Sun, 23 Jun 2013, H. Peter Anvin wrote:
> >> Why do you care about performance when PAT is disabled?
> >
> > It will regress already slow boxes. We blacklist a LOT of P4s, PMs, etc and
>
On Sat, Jun 22, 2013 at 11:17:20PM -0400, Greg Price wrote:
> For example, in an application with an expensive function
> implemented with deeply nested recursive calls, the default
> call-graph presentation is dominated by the different callchains
> within that function. By treating the function
On Sun 2013-06-23 17:27:52, Mark Lord wrote:
> On 13-06-23 03:00 PM, Pavel Machek wrote:
> >
> > Thanks for the hint. (Insert rant about hdparm documentation
> > explaining that it is bad idea, but not telling me _why_ is it bad
> > idea. Can I expect cache consistency issues after that, or is it j
On Sunday, June 23, 2013 04:34:17 AM Joe Perches wrote:
> On Sun, 2013-06-23 at 13:36 +0200, Rafael J. Wysocki wrote:
> > Please keep the existing format as is literally and append any
> > new information to the end of the line.
>
> Hi Shuah.
>
> Perhaps the better long-term approach would be to
On Sunday, June 23, 2013 11:57:46 PM Jiang Liu wrote:
> On 06/23/2013 03:59 AM, Rafael J. Wysocki wrote:
> > On Saturday, June 22, 2013 10:47:24 AM Jiang Liu wrote:
> >> On 06/22/2013 08:13 AM, Rafael J. Wysocki wrote:
> >>> On Saturday, June 22, 2013 12:54:21 AM Jiang Liu wrote:
> On 06/21/20
On Sunday, June 23, 2013 11:57:46 PM Jiang Liu wrote:
> On 06/23/2013 03:59 AM, Rafael J. Wysocki wrote:
> > On Saturday, June 22, 2013 10:47:24 AM Jiang Liu wrote:
> >> On 06/22/2013 08:13 AM, Rafael J. Wysocki wrote:
> >>> On Saturday, June 22, 2013 12:54:21 AM Jiang Liu wrote:
> On 06/21/20
On 13-06-23 03:00 PM, Pavel Machek wrote:
>
> Thanks for the hint. (Insert rant about hdparm documentation
> explaining that it is bad idea, but not telling me _why_ is it bad
> idea. Can I expect cache consistency issues after that, or is it just
> simple "you are writing to the disk without any c
On Sunday, June 23, 2013 01:29:19 PM Yinghai Lu wrote:
> On Sun, Jun 23, 2013 at 12:57 PM, Yinghai Lu wrote:
> > On Sun, Jun 23, 2013 at 8:54 AM, Jiang Liu wrote:
> >> On 06/23/2013 05:25 AM, Rafael J. Wysocki wrote:
> >>> From: Rafael J. Wysocki
> >>>
> >>> The interactions between the ACPI doc
Hi Gabriel,
sorry for the late feedback.
Dne 10.6.2013 17:28, Gabriel de Perthuis napsal(a):
> Use RCS_FIND_IGNORE in more places.
Can you split it into two parts - one adding the missing RCS_FIND_IGNORE
to some find invocations, and other adding the -xdev option? While the
first change is obvio
On Mon, Jun 24, 2013 at 6:58 AM, H. Peter Anvin wrote:
> On 06/23/2013 01:54 PM, Dave Airlie wrote:
breaking old boxes just because, is just going to get reverted when I
get the first regression report that you broke old boxes.
>>>
>>> Not "just because", but *if* the choice is betw
Hi Michal,
On 08/06/13 01:58 PM, Graeme Smecher wrote:
Hi all,
On 08/06/13 09:52 AM, Graeme Smecher wrote:
Other architectures don't do it, and it conflicts with the extern'd
definition
in include/linux/kgdb.h.
Signed-off-by: Graeme Smecher
CC: Michal Simek
CC:linux-kernel@vger.kernel.org
--
On Sunday, June 23, 2013 11:50:15 PM Alexander E. Patrakov wrote:
> 2013/6/23 Rafael J. Wysocki :
> > Alexander, I've modified patch [3/3] a bit since you have tested it.
> > The modifications shouldn't affect the behavior, but if you could re-test
> > it,
> > that would be great.
>
> Retested, e
On 06/23/2013 01:54 PM, Dave Airlie wrote:
>>> breaking old boxes just because, is just going to get reverted when I
>>> get the first regression report that you broke old boxes.
>>>
>>
>> Not "just because", but *if* the choice is between breaking old boxes
>> and breaking new boxes I'll take the
>> breaking old boxes just because, is just going to get reverted when I
>> get the first regression report that you broke old boxes.
>>
>
> Not "just because", but *if* the choice is between breaking old boxes
> and breaking new boxes I'll take the latter.
>
But Linus won't so your choice doesn't
On 06/23/2013 01:30 PM, Dave Airlie wrote:
Why do you care about performance when PAT is disabled?
>
> breaking old boxes just because, is just going to get reverted when I
> get the first regression report that you broke old boxes.
>
Not "just because", but *if* the choice is between break
>>> Why do you care about performance when PAT is disabled?
breaking old boxes just because, is just going to get reverted when I
get the first regression report that you broke old boxes.
Andy Lutomirski just submitted a bunch of patches to clean up the DRM
usage of mtrrs, they are in drm-next, a
1 - 100 of 254 matches
Mail list logo