On 15.10.2013 08:40, Ingo Molnar wrote:
* Frederic Weisbecker wrote:
I've been thinking that CONFIG_DEBUG_LIST could help. Unfortunately it's
good to spot list APIs misuse but, if Linus is right, the problem may be
that the list belongs to an object that has been freed, and I believe
that
> I was led to believe this in the busybox list. maybe we are communally
> smoking the same stuff. Linux Kernel Developers would rather go on
> developing better code than waste time on enforcement. Some even think
> it is counter productive to adoption of linux.
>
> Transcend most likely knows
Hi Neil, Andi,
On Mon, 14 Oct 2013 16:25:28 -0400
Neil Horman wrote:
> On Sun, Oct 13, 2013 at 09:38:33PM -0700, Andi Kleen wrote:
> > Neil Horman writes:
> >
> > > Sébastien Dugué reported to me that devices implementing ipoib (which
> > > don't have
> > > checksum offload hardware were
On 15/10/2013 01:58, Soren Brinkmann :
Use the device managed interface to request the IRQ, simplifying error
paths.
Signed-off-by: Soren Brinkmann
Acked-by: Nicolas Ferre
---
drivers/net/ethernet/cadence/macb.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git
On 15/10/2013 01:58, Soren Brinkmann :
Use the device managed version of ioremap to remap IO memory,
simplifying error paths.
Signed-off-by: Soren Brinkmann
Acked-by: Nicolas Ferre
---
drivers/net/ethernet/cadence/macb.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
* Namhyung Kim wrote:
> [SNIP]
> > +/* mmap file big chunks at a time */
> > +#define MMAP_OUTPUT_SIZE (64*1024*1024)
>
> Why did you choose 64MB for the size? Did you also test other sizes?
Btw., should this value go up if the ring buffer (mmap_pages) is larger
than 64MB?
Thanks,
On 15/10/2013 01:58, Soren Brinkmann :
Migrate to using the device managed intreface for clocks and clean up
the associated error paths.
Signed-off-by: Soren Brinkmann
Acked-by: Nicolas Ferre
---
drivers/net/ethernet/cadence/macb.c | 32
1 file changed,
On 15/10/2013 01:58, Soren Brinkmann :
Migrate the suspend/resume functions to use the dev_pm_ops PM interface.
Signed-off-by: Soren Brinkmann
Acked-by: Nicolas Ferre
---
drivers/net/ethernet/cadence/macb.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff
* Joe Perches wrote:
> On Mon, 2013-10-14 at 15:44 -0700, Eric Dumazet wrote:
> > On Mon, 2013-10-14 at 15:37 -0700, Joe Perches wrote:
> > > On Mon, 2013-10-14 at 15:18 -0700, Eric Dumazet wrote:
> > > > attached patch brings much better results
> > > >
> > > > lpq83:~# ./netperf -H 7.7.8.84
> call_timer_fn 0x73/0x160 <--- EIP hits 0
Use after free.. with CONFIG_DEBUG_PAGEALLOC &&
CONFIG_DEBUG_OBJECTS_TIMERS we get :
call_timer_fn 0x73/0x160
destroy_timer_on_stack 0x20/0x20
ftrace_raw_event_hrtimer_expire_entry 0x3b/0xc0
run_timer_softirq 0x1f2/0x230
--
Janne
--
To unsubscribe
Dear Jason Cooper,
On Mon, 14 Oct 2013 15:02:47 -0400, Jason Cooper wrote:
> On Mon, Oct 14, 2013 at 08:43:49PM +0200, Sebastian Hesselbarth wrote:
> ...
> > You know a good way to determine how far it should go back to -stable?
>
> $ git blame -L 338,338 drivers/pinctrl/mvebu/pinctrl-dove.c
>
On 15/10/13 09:49, Ивайло Димитров wrote:
> I am using my n900 as a daily/only device since the beginning of 2010, never
> seen such an
> issue with video playback. And as a maintainer of one of the community
> supported kernels for
> n900 (kernel-power) I've never had such an issue reported.
Before this patch, looking at 'perf bench sched pipe' behavior
over 'top' only told us that something related to perf is
running:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
19934 mingo 20 0 54836 1296 952 R 18.6 0.0 0:00.56 perf
19935 mingo 20
This is a refresh of the perf bench improvement + cleanup patch I posted a
couple
of weeks ago. It can also be found in tip:tmp.perf.
Thanks,
Ingo
==>
Ingo Molnar (1):
tools/perf/bench: Change the procps visible command-name of invididual
benchmark tests plus cleanups
Hi Thomas,
On Tuesday 01 October 2013 08:37 PM, Santosh Shilimkar wrote:
> On Tuesday 01 October 2013 10:53 AM, Rob Herring wrote:
>> On 10/01/2013 08:57 AM, Santosh Shilimkar wrote:
>>> On Tuesday 01 October 2013 09:48 AM, Rob Herring wrote:
On 10/01/2013 06:13 AM, Sricharan R wrote:
>
* Neil Horman wrote:
> On Sat, Oct 12, 2013 at 07:21:24PM +0200, Ingo Molnar wrote:
> >
> > * Neil Horman wrote:
> >
> > > Sébastien Dugué reported to me that devices implementing ipoib (which
> > > don't have checksum offload hardware were spending a significant amount
> > > of time
Hi David,
On Mon, 14 Oct 2013 20:55:31 -0600, David Ahern wrote:
> When recording raw_syscalls for the entire system, e.g.,
> perf record -e raw_syscalls:*,sched:sched_switch -a -- sleep 1
>
> you end up with a negative feedback loop as perf itself calls
> write() fairly often. This patch
On Thu, Sep 26, 2013 at 7:35 PM, Vishal Annapurve wrote:
> Hi,
>
> There was a recent commit in mainline for the scsi devices which do not
> respond properly to medium access command:
>
> commit18a4d0a22ed6c54b67af7718c305cd010f09ddf8
>
> [SCSI] Handle disk devices which can not process
Hi Nishanth,
On 10/10/2013 18:44, Nishanth Menon wrote:
Do not reset GPIO1 at boot-up because GPIO 7 in GPIO1 block is used on
OMAP4460 PandaBoard-ES to select voltage register in TPS62361 which
supplies VDD_MPU.
Without this, OMAP4460 PandaBoard-ES boards fail to boot-up because
MPU voltage
* Namhyung Kim wrote:
> > 3)
> >
> > The rec->bytes_at_mmap_start field feels a bit weird. If I read the code
> > correctly, in every 'perf record' invocation, rec->bytes_written starts at
> > 0 - i.e. we don't have repeat invocations of cmd_record().
>
> rec->bytes_written is updated when
On Tue, 15 Oct 2013 08:50:11 +0200
Geert Uytterhoeven wrote:
> arch/s390/kernel/crash_dump.c: In function 'copy_from_realmem':
> arch/s390/kernel/crash_dump.c:48:6: warning: unused variable 'rc'
> [-Wunused-variable]
>
> Introduced by commit 4d3b0664a0d0c0dc7501cfbd067f74226aeca510 ("s390:
* Ingo Molnar wrote:
>
> * H. Peter Anvin wrote:
>
> > On 10/12/2013 11:05 AM, Linus Torvalds wrote:
> > > On Sat, Oct 12, 2013 at 10:15 AM, Ingo Molnar wrote:
> > >>
> > >> Ville Syrjälä (1):
> > >> x86/reboot: Add reboot quirk for Dell Latitude E5410
> > >
> > > So we have a number
On Mon, 2013-10-14 at 17:59 -0500, Felipe Balbi wrote:
> On Mon, Oct 14, 2013 at 06:24:39PM +0300, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov"
> >
> > IRQ with number 0 is valid case, so check for negative
>
> not entirelly correct... IRQ 0 isn't supposed to be used as a linux IRQ
>
On Tue, 15 Oct 2013 08:08:29 +0200, Ingo Molnar wrote:
> * Namhyung Kim wrote:
>
>> From: Namhyung Kim
>>
>> Linus reported that sometimes 'perf report -s symbol' exits without any
>> message on TUI. David and Jiri found that it's because it failed to add
>> a hist entry due to an invalid
Hi Ingo,
On Tue, 15 Oct 2013 08:02:00 +0200, Ingo Molnar wrote:
> * David Ahern wrote:
>
>> +/* for MMAP based file writes */
>> +void*mmap_addr;
>> +u64 bytes_at_mmap_start; /* bytes in file when mmap
>> use starts */
>> +u64
* Christoph Lameter wrote:
> On Sat, 12 Oct 2013, Ingo Molnar wrote:
>
> > Another problem is that the patch emails are not properly threaded to the
> > 0/6 patch and thus appear out of order and mixed up:
> >
> > 66216 N C Oct 11 Christoph Lamet ( 36) [PATCH 0/6] percpu: Implement
> >
Hi Gao-san,
(2013/10/15 15:30), Gao feng wrote:
> Hi Toshiyuki-san,
> On 10/15/2013 12:43 PM, Toshiyuki Okajima wrote:
>> The backlog cannot be consumed when audit_log_start is running on auditd
>> even if audit_log_start calls wait_for_auditd to consume it.
>> The situation is a deadlock because
Hi Mark,
Fixed all your comments and already sent a V2.
On 10/14/2013 8:03 PM, Mark Rutland wrote:
On Mon, Oct 14, 2013 at 01:43:23PM +0100, George Cherian wrote:
This patch adds a compatible for AM437x "ti,am43xx-usb2" to
reuse the same phy-omap-usb2 driver.
Also updated the documentation
On 10/14/2013 6:49 PM, Roger Quadros wrote:
Hi George,
On 10/14/2013 03:51 PM, George Cherian wrote:
This adds omap control module support for USBSS in AM437x SoC.
Update DT binding information to reflect these changes.
Signed-off-by: George Cherian
---
On Mon, 2013-10-14 at 17:52 -0500, Felipe Balbi wrote:
> Hi,
>
> On Mon, Oct 14, 2013 at 06:24:28PM +0300, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov"
> >
> > This patch fix compilation error and is an intermediate step
> > before the addition of DeviceTree support for newer targets.
> >
On Tue, Oct 15, 2013 at 3:23 PM, Naveen Krishna Chatradhi
wrote:
> For Exynos4 and Exynos5 SoCs from Samsung the i2c clock is based
> on a fixed 66 MHz peripheral clock, and therefore is completely
> independent of the cpu frequency.
> Thus, registering for a CPU freq notifier is very wasteful.
>
This patch arranges the includes in alphabetical order
Signed-off-by: George Cherian
---
drivers/phy/phy-omap-usb2.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/phy/phy-omap-usb2.c b/drivers/phy/phy-omap-usb2.c
index bfc5c33..3e5f08c 100644
---
This patch adds a compatible for AM437x "ti,am43xx-usb2" to
reuse the same phy-omap-usb2 driver.
Also updated the documentation to add the new compatible.
Signed-off-by: George Cherian
---
Documentation/devicetree/bindings/usb/usb-phy.txt | 4 +-
drivers/phy/phy-omap-usb2.c
Hi Roger,
On 14/10/2013 11:20, Roger Quadros wrote:
Hi Benoit,
On 10/10/2013 06:34 PM, Felipe Balbi wrote:
On Mon, Oct 07, 2013 at 04:28:13PM +0300, Roger Quadros wrote:
The generic PHY framewrok expects different properties than the
old USB PHY framework. Supply those properties.
Fixes USB
This series adapts the phy-omap-usb2 generic phy driver for AM437x.
While at that arrange the include files alphabetically (PATCH 1)
V2 of 2nd Patch which fixes the following from v1
- List comaptible entries in Documentaion
- Add usb_phy_data instead of checking compatible each
arch/s390/kernel/crash_dump.c: In function 'copy_from_realmem':
arch/s390/kernel/crash_dump.c:48:6: warning: unused variable 'rc'
[-Wunused-variable]
Introduced by commit 4d3b0664a0d0c0dc7501cfbd067f74226aeca510 ("s390: Allow
vmalloc target buffers for copy_from_oldmem()").
Signed-off-by: Geert
* H. Peter Anvin wrote:
> On 10/14/2013 01:37 PM, Yinghai Lu wrote:
> >>
> >> Optimizing NUMA boot just requires moving the heavy lifting to
> >> appropriate NUMA nodes. It doesn't require that early boot phase
> >> should strictly follow NUMA node boundaries.
> >
> > At end of day, I like to
Hi
> Оригинално писмо
>От: Tomi Valkeinen
>Относно: Re: OMAPFB: CMA allocation failures
>До: Ивайло Димитров
>Изпратено на: Понеделник, 2013, Октомври 14 09:04:35 EEST
>
>
>Hi,
>
>On 12/10/13 17:43, Ивайло Димитров wrote:
>> Hi Tomi,
>>
>> patch
>>
Hi,
On 14/10/13 17:48, Thierry Reding wrote:
> Today's linux-next merge of the omap_dss2 tree got conflicts in
>
> drivers/video/omap2/dss/hdmi4_core.c
> drivers/video/omap2/dss/hdmi4_core.h
>
> caused by commits ef26958 (omapdss: HDMI: Rename hdmi driver files to nicer
> names) and
On Sun, Oct 13, 2013 at 1:02 PM, Pavel Machek wrote:
>>
>> I dont think the majority of linux kernel developers care about
>> enforcement at all. Its virtually public domain as far as i can see,
>> Linus himself will not run after violators.
>>
>> Any company out there is free to do what they
Hi,
Attached config seems to yield following crash ~5 seconds from kernel
init on Lenovo X201. Any pointers? Sorry for horrible output, its
manually copied from console.
call_timer_fn 0x73/0x160 <--- EIP hits 0
usleep_range 0x40/0x40
run_timer_softirq 0x1d5/0x220
..
call_timer_fn:
..
* Frederic Weisbecker wrote:
> I've been thinking that CONFIG_DEBUG_LIST could help. Unfortunately it's
> good to spot list APIs misuse but, if Linus is right, the problem may be
> that the list belongs to an object that has been freed, and I believe
> that won't detect such a thing.
On Tue, Oct 15, 2013 at 8:34 AM, Geert Uytterhoeven
wrote:
> JFYI, when comparing v3.12-rc5 to v3.12-rc4[3], the summaries are:
> - build errors: +13/-6
+ /scratch/kisskb/src/arch/powerpc/kernel/fadump.c: error:
'KEXEC_CORE_NOTE_NAME' undeclared (first use in this function): =>
521:36
+
Below is the list of build error/warning regressions/improvements in
v3.12-rc5[1] compared to v3.11[2].
Summarized:
- build errors: +33/-11
- build warnings: +190/-97
JFYI, when comparing v3.12-rc5 to v3.12-rc4[3], the summaries are:
- build errors: +13/-6
- build warnings: +85/-25
As I
On Sun, Oct 13, 2013 at 08:56:33PM +0530, Vinod Koul wrote:
> On Fri, Oct 11, 2013 at 06:33:43AM -0700, Greg KH wrote:
> > On Fri, Oct 11, 2013 at 05:42:17PM -0400, Youquan Song wrote:
> > > Currently, the DMA channel calculates its data transferred only at network
> > > device driver. When other
Hi Toshiyuki-san,
On 10/15/2013 12:43 PM, Toshiyuki Okajima wrote:
> The backlog cannot be consumed when audit_log_start is running on auditd
> even if audit_log_start calls wait_for_auditd to consume it.
> The situation is a deadlock because only auditd can consume the backlog.
> If the other
On 10/15/2013 05:20 AM, Steven Rostedt wrote:
On Mon, 14 Oct 2013 15:53:27 +0200
Daniel Lezcano wrote:
The Inter Processor Interrupt is used on ARM to tell another processor to do
a specific action. This is mainly used to emulate a timer interrupt on an idle
cpu, force a cpu to reschedule or
Am Montag, 14. Oktober 2013, 11:18:16 schrieb Sandy Harris:
Hi Sandy,
Could you please review the following code to see that the mix is
function right in your eyes?
>
>However, having done that, I see no reason not to add mixing.
>Using bit() for getting one bit of input and rotl(x) for
Hi Eduardo,
> On 14-10-2013 15:13, Eduardo Valentin wrote:
> > On 14-10-2013 01:52, Zhang, Rui wrote:
> >> Eduardo,
> >>
> >> What's your opinion on this patch set?
> >> BTW, please send me all the urgent fixes for thermal soc drivers
> >> that
> > you think should go to 3.12.
> >>
> >
> > I
For Exynos4 and Exynos5 SoCs from Samsung the i2c clock is based
on a fixed 66 MHz peripheral clock, and therefore is completely
independent of the cpu frequency.
Thus, registering for a CPU freq notifier is very wasteful.
This patch modifes the code such that, i2c bus registers to
Hello Naveen,
Am 15.10.2013 07:12, schrieb Naveen Krishna Chatradhi:
The Exynos5 i2c driver does not handle NACKs properly. This change:
- fixes the NACK processing problem (do not continue transaction if
address cycle was NACKed)
- eliminates a fair amount of duplicate code
On 15/10/13 05:09, Arnaldo Carvalho de Melo wrote:
> Hi Adrian,
>
> While testing 'perf top -U' to reply a message in another thread
> I noticed that ksm symbols appeared as '[kernel]', and only when I tried
> 'perf top -U -v' to look at the DSO long name I noticed that it was...
>
Hi Sarah,
On 10/15/2013 03:54 AM, Gerd Hoffmann wrote:
Gerd, Hans, any objections to this updated patch? The warning is fixed
with it.
No objections, looks good to me.
The patch probably still needs to address the case where the ring
expansion fails because we can't insert the new
On 15 October 2013 11:36, Heiko Schocher wrote:
> Hello Naveen,
>
> Am 15.10.2013 07:12, schrieb Naveen Krishna Chatradhi:
>
>> The Exynos5 i2c driver does not handle NACKs properly. This change:
>>
>> - fixes the NACK processing problem (do not continue transaction if
>>address cycle was
* Namhyung Kim wrote:
> From: Namhyung Kim
>
> Linus reported that sometimes 'perf report -s symbol' exits without any
> message on TUI. David and Jiri found that it's because it failed to add
> a hist entry due to an invalid symbol length.
Btw., 'exit without any messages' is something
* Kees Cook wrote:
> On Mon, Oct 14, 2013 at 9:28 AM, H. Peter Anvin wrote:
> > On 10/14/2013 07:19 AM, H. Peter Anvin wrote:
> >> My guess is that the 95 addresses are randomized and the 82 address is an
> >> address which failed to relocate.
> >
> >> 82a04a58 is:
> >>
* David Ahern wrote:
> + /* for MMAP based file writes */
> + void*mmap_addr;
> + u64 bytes_at_mmap_start; /* bytes in file when mmap
> use starts */
> + u64 mmap_offset;/* current location within mmap
> */
> +
From: Kuppuswamy Sathyanarayanan sathyanarayanan.kuppusw...@linux.intel.com
Fixed printk and pr_* related issues in mrst related files.
Signed-off-by: Kuppuswamy Sathyanarayanan
sathyanarayanan.kuppusw...@linux.intel.com
Signed-off-by: David Cohen david.a.co...@linux.intel.com
---
From: Kuppuswamy Sathyanarayanan sathyanarayanan.kuppusw...@linux.intel.com
SFI device_id[] table parsing code is duplicated in every SFI
device handler. This patch removes this code duplication, by
adding a seperate function get_device_id() to parse through the
device table. Also this patch
On Tue, Oct 15, 2013 at 01:41:28PM -0400, Johannes Weiner wrote:
On Tue, Oct 15, 2013 at 12:41:23PM +1100, Dave Chinner wrote:
On Mon, Oct 14, 2013 at 05:42:50PM -0400, Johannes Weiner wrote:
Hi Dave,
On Fri, Oct 11, 2013 at 11:39:30AM +1100, Dave Chinner wrote:
On Thu, Oct 10,
From: Kuppuswamy Sathyanarayanan sathyanarayanan.kuppusw...@linux.intel.com
Following files contains code that is common to all intel mid
soc's. So renamed them as below.
mrst/mrst.c - intel-mid/intel-mid.c
mrst/vrtc.c - intel-mid/intel_mid_vrtc.c
This patch set does initial rework from arch/x86/platform/mrst to
arch/x86/platform/intel-mid.
These changes are necessary to update the obsolete Intel Atom Moorestown code
to support the newer Atom processors of this family (called 'intel-mid').
David Cohen (3):
intel-mid: sfi: allow struct
On 10/15/2013 04:42 PM, David Cohen wrote:
+#define intel_mid_sfi_dev(i) \
+ static const struct devs_id *__intel_mid_sfi_##i##_dev __used \
+ __attribute__((__section__(.x86_intel_mid_dev.init))) = i
+
Any reason to not just call this sfi_device() or something
On 10/15/2013 04:44 PM, H. Peter Anvin wrote:
On 10/15/2013 04:42 PM, David Cohen wrote:
+#define intel_mid_sfi_dev(i) \
+ static const struct devs_id *__intel_mid_sfi_##i##_dev __used \
+ __attribute__((__section__(.x86_intel_mid_dev.init))) = i
+
Any reason to
On 09/09/2013 02:55 PM, Seiji Aguchi wrote:
Change from v2
- Print entry-ip instead of entry-regs-ip to avoid kernel crash.
- Use %pf instead of 0x%lx to print address and ip.
This patch introduces page fault tracepoints to x86 architecture
by switching IDT.
[Use case of page fault
On Mon, 14 Oct 2013, Akira Hayakawa wrote:
Hi, DM Guys
I suppose I have finished the tasks to
answer Mikulas's pointing outs.
So, let me update the progress report.
The code is updated now on my Github repo.
Checkout the develop branch to avail
the latest source code.
Compilation
There is a typo where the checking for priv-ReAssociationRequestRetryCnt must
be, it was checking for priv-AssociationRequestRetryCnt instead.
Signed-off-by: Felipe Pena felipe...@gmail.com
---
drivers/net/wireless/atmel.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Thu, 2013-10-10 at 09:54 +0200, Ingo Molnar wrote:
* Tim Chen tim.c.c...@linux.intel.com wrote:
The throughput of pure mmap with mutex is below vs pure mmap is below:
% change in performance of the mmap with pthread-mutex vs pure mmap
#threadsvanilla all rwsem
On Tue, Oct 15, 2013 at 2:43 PM, Grant Likely grant.lik...@secretlab.ca wrote:
*unless you find the signed tag questionable. You'll notice that I
have a shiny-new gpg key which is currently only signed by my old key.
Yes. Bad. I left it very late to create a new key, the old key is now
On Tue, 2013-10-15 at 18:02 +0200, Andi Kleen wrote:
I get the csum_partial() if disabling prequeue.
At least in the ipoib case i would consider that a misconfiguration.
There is nothing you can do, if application is not blocked on recv(),
but using poll()/epoll()/select(), prequeue is not
In the lpfc_ct_free_iocb function after freeing associated memory to the
ctiocb-context3, the ctiocb-context1 is set to NULL instead of context3.
Signed-off-by: Felipe Pena felipe...@gmail.com
---
drivers/scsi/lpfc/lpfc_ct.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Tue, 2013-10-15 at 09:21 -0700, Joe Perches wrote:
Ingo, Eric _showed_ that the prefetch is good here.
How about looking at a little optimization to the minimal
prefetch that gives that level of performance.
Wait a minute, my point was to remind that main cost is the
memory fetching.
Its
On Wed, Oct 16, 2013 at 4:22 AM, Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 15 Oct 2013, Vishal Annapurve wrote:
Hi Alan,
USB storage maybe just has to say that the abort occurred. By setting the
US_FLIDX_TIMED_OUT bit USB storage is getting signaled that the reason was
time out
On Oct 16, 2013, at 6:21 AM, Marcelo Tosatti mtosa...@redhat.com wrote:
On Tue, Oct 15, 2013 at 06:57:05AM +0300, Gleb Natapov wrote:
Why is it safe to allow access, by the lockless page write protect
side, to spt pointer for shadow page A that can change to a shadow page
pointer of
+ if ((portchange USB_PORT_STAT_C_RESET)) {
Hm, why these double parens?
Oh... good question. I copied the entry below it, remove the and
must have overlooked those. Sorry, v2 incoming...
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
I see a few problems on this patchset:
Em Tue, 15 Oct 2013 23:00:53 +0530
Naveen N. Rao naveen.n@linux.vnet.ibm.com escreveu:
On 10/15/2013 10:30 PM, Borislav Petkov wrote:
On Tue, Oct 15, 2013 at 10:24:35PM +0530, Naveen N. Rao wrote:
On 2013/10/11 02:32AM, Chen Gong wrote:
Use trace
This patch adds the Port Reset Change flag to the set of bits that are
preemptively cleared on init/resume of a hub. In theory this bit should
never be set unexpectedly... in practice it can still happen if BIOS,
SMM or ACPI code plays around with USB devices without cleaning up
correctly. This is
On 10/15/2013 04:53 PM, David Cohen wrote:
On 10/15/2013 04:44 PM, H. Peter Anvin wrote:
On 10/15/2013 04:42 PM, David Cohen wrote:
+#define intel_mid_sfi_dev(i) \
+static const struct devs_id *__intel_mid_sfi_##i##_dev __used \
+
Mikulas,
I/Os shouldn't be returned with -ENOMEM. If they are, you can treat it as
a hard error.
It seems to be blkdev_issue_discard returns -ENOMEM
when bio_alloc fails, for example.
Waiting for a second and we can alloc the memory is my idea
for handling -ENOMEM returned.
Blocking I/O
(2013/10/16 4:12), Vivek Goyal wrote:
On Tue, Oct 15, 2013 at 02:43:22PM +0900, HATAYAMA Daisuke wrote:
Kexec can enter the kdump 2nd kernel on AP if crash happens on AP. To
check if boot cpu is BSP, introduce a helper function
boot_cpu_is_bsp().
Signed-off-by: HATAYAMA Daisuke
Commit 4e7ea81db5(ext4: restructure writeback path) introduces
another performance regression on random write:
- one more page may be added to ext4 extent in mpage_prepare_extent_to_map,
and will be submitted for I/O so nr_to_write will become -1 before 'done'
is set
- the worse thing is
On Tuesday, October 15, 2013 3:40 AM, Thierry Reding wrote:
On Mon, Oct 14, 2013 at 02:57:48PM -0700, H Hartley Sweeten wrote:
Remove the non-standard EP93xx pwm driver in drivers/misc and add
pwm - PWM
OK
a new driver for the PWM chips on the EP93xx platforms based on the
PWM framework.
Hi David,
On Tue, 15 Oct 2013 07:25:04 -0600, David Ahern wrote:
On 10/15/13 1:09 AM, Namhyung Kim wrote:
The stat() seems superfluous, here in __cmd_record() we've just checked
the output_name and made sure it exists. Can that stat() call ever fail?
AFAICS it's needed to check current file
(2013/10/16 4:30), Vivek Goyal wrote:
On Tue, Oct 15, 2013 at 02:43:27PM +0900, HATAYAMA Daisuke wrote:
Currently, on x86 architecture, if crash happens on AP in the kdump
1st kernel, the 2nd kernel fails to wake up multiple CPUs. The typical
behaviour we actually see is immediate system reset
A couple more regressions fixed, please pull.
The following changes since commit 34ec4de42be5006abdd8d0c08b306ffaa64d0d5d:
Merge tag 'devicetree-for-linus' of git://git.secretlab.ca/git/linux
(2013-10-15 17:14:13 -0700)
are available in the git repository at:
sg3_utils is a package of command line utilities for sending
SCSI and some ATA commands to devices. This package targets
the Linux 3, 2.6 and 2.4 kernel series. It also has ports to
FreeBSD, Tru64, Solaris, and Windows (cygwin and MinGW).
This version contains many fixes, some code cleanup and
Remove the non-standard EP93xx PWM driver in drivers/misc and add
a new driver for the PWM controllers on the EP93xx platform based
on the PWM framework.
These PWM controllers each support 1 PWM channel with programmable
duty cycle, frequency, and polarity inversion.
Signed-off-by: H Hartley
On Tue, Oct 15, 2013 at 10:56:25PM +0530, Naveen N. Rao wrote:
Date: Tue, 15 Oct 2013 22:56:25 +0530
From: Naveen N. Rao naveen.n@linux.vnet.ibm.com
To: Chen, Gong gong.c...@linux.intel.com
Cc: tony.l...@intel.com, b...@alien8.de, linux-kernel@vger.kernel.org,
linux-a...@vger.kernel.org
On Tue, 15 Oct 2013 07:35:53 -0600, David Ahern wrote:
On 10/15/13 1:31 AM, Namhyung Kim wrote:
Hi David,
On Mon, 14 Oct 2013 20:55:31 -0600, David Ahern wrote:
When recording raw_syscalls for the entire system, e.g.,
perf record -e raw_syscalls:*,sched:sched_switch -a -- sleep 1
you
On Tue, Oct 15, 2013 at 11:47:23PM +0530, Naveen N. Rao wrote:
Date: Tue, 15 Oct 2013 23:47:23 +0530
From: Naveen N. Rao naveen.n@linux.vnet.ibm.com
To: Chen, Gong gong.c...@linux.intel.com
Cc: tony.l...@intel.com, b...@alien8.de, linux-kernel@vger.kernel.org,
linux-a...@vger.kernel.org
Hello Steven,
-Original Message-
From: Steven Rostedt [mailto:rost...@goodmis.org]
Sent: Wednesday, October 16, 2013 12:40 AM
To: Liu, Chuansheng
Cc: Ingo Molnar (mi...@kernel.org); h...@zytor.com; fweis...@gmail.com;
a...@linux-foundation.org; paul...@linux.vnet.ibm.com; Peter
On Fri, 2013-10-11 at 17:47 +0200, Borislav Petkov wrote:
On Fri, Oct 11, 2013 at 11:06:30AM +0200, Borislav Petkov wrote:
- printk(%sAPEI generic hardware error status\n, pfx);
+ printk(%sGeneric Hardware Error Status\n, pfx);
Btw, what's the story with printk not using KERN_x levels
On 10/15/13 7:52 PM, Namhyung Kim wrote:
Aha, okay. So it mostly matters to syscall tracing, right? For a
normal record session, it seems that the effect is not that large:
Yes, that's in the description When recording raw_syscalls for the
entire system
There is a small benefit to all
On 10/15/2013 09:38 PM, Mark Rutland wrote:
On Tue, Oct 08, 2013 at 04:22:07AM +0100, Hongbo Zhang wrote:
Hi Mark, Stephen and other DT maintainers?
The 1/3 had already been acked by Mark, and please have a further look
at this patch 2/3.
The DMA maintainer Vinod needs ack for the DT related
Hello Jan,
Just wanted to let you know I hit this[1] again on Linus' latest. The
setup/workload is *identical* to the reported one a few months ago.
[1] https://lkml.org/lkml/2013/8/1/532
Here's the complete output, I hope it helps...
[ cut here ]
WARNING: CPU: 42 PID:
On 10/15/2013 07:41 PM, Dave Chinner wrote:
On Tue, Oct 15, 2013 at 01:41:28PM -0400, Johannes Weiner wrote:
I'm not forgetting about them, I just track them very coarsely by
linking up address spaces and then lazily enforce their upper limit
when memory is tight by using the shrinker
Implement instr_is_load_store_2_06() to detect whether a given instruction
is one of the fixed-point or floating-point load/store instructions in the
POWER Instruction Set Architecture v2.06.
This function will be used in a follow-on patch to save memory hierarchy
information of the load/store on
On Power8, the LDST field in SIER identifies the memory hierarchy level
(eg: L1, L2 etc), from which a data-cache miss for a marked instruction
was satisfied.
Use the 'perf_mem_data_src' object to export this hierarchy level to user
space. Fortunately, the memory hierarchy levels in Power8 map
On Wed, 16 Oct 2013 01:54:51 +
Liu, Chuansheng chuansheng@intel.com wrote:
Since the NMI iretq nesting has been fixed, there's no reason that
I think you patch fix the infinite loop, we will have a test soon.
BTW, we are using 3.10, could you help to point out which NMI iretq nesting
The perf event PM_MRK_GRP_CMPL is useful in analyzing memory hierarchy
of applications.
Signed-off-by: Sukadev Bhattiprolu suka...@linux.vnet.ibm.com
---
Changelog[v6]:
- [Michael Ellerman]: Drop redundant PME_ prefix from event name.
arch/powerpc/perf/power8-events-list.h |1 +
1
701 - 800 of 1514 matches
Mail list logo
