On Wed, Oct 2, 2013 at 6:37 AM, Peter Zijlstra wrote:
> On Wed, Oct 02, 2013 at 03:13:16PM +0200, Stephane Eranian wrote:
>> On Wed, Oct 2, 2013 at 3:01 PM, Peter Zijlstra wrote:
>> > On Wed, Oct 02, 2013 at 02:59:32PM +0200, Stephane Eranian wrote:
>> >> On Wed, Oct 2, 2013 at 2:46 PM, Peter Zij
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/ntb/ntb_hw.c | 41 +---
On Wed, Oct 02, 2013 at 09:47:18AM -0700, Guenter Roeck wrote:
> On Wed, Oct 02, 2013 at 06:34:18PM +0200, Henrik Rydberg wrote:
> > > >>One thing I have seen in all logs is the earlier "send_byte fail"
> > > >>message, so
> > > >>I think that is a pre-requisite.
> > > >
> > > >Not necessarily - i
On 10/02/13 10:14, Santosh Shilimkar wrote:
> On Wednesday 02 October 2013 01:09 PM, Will Deacon wrote:
>> On Wed, Oct 02, 2013 at 05:55:28PM +0100, Santosh Shilimkar wrote:
>>> The sched_clock code uses 2 levels of function pointers, sched_clock_func()
>>> and read_sched_clock() but the no sched_c
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/ata/ahci.c | 56 --
On Wed, Oct 2, 2013 at 7:14 PM, Kees Cook wrote:
> On Wed, Oct 2, 2013 at 6:37 AM, Peter Zijlstra wrote:
>> On Wed, Oct 02, 2013 at 03:13:16PM +0200, Stephane Eranian wrote:
>>> On Wed, Oct 2, 2013 at 3:01 PM, Peter Zijlstra wrote:
>>> > On Wed, Oct 02, 2013 at 02:59:32PM +0200, Stephane Eranian
Hi Mike,
could you please comment on this/apply it to clk-next?
Thanks,
Sören
On Sat, Sep 21, 2013 at 04:40:39PM -0700, Soren Brinkmann wrote:
> Add a driver for SILabs 570, 571, 598, 599 programmable oscillators.
> The devices generate low-jitter clock signals and are reprogramm
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/net/ethernet/qlogic/qlge/qlge_main.c | 39 +++-
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/scsi/ipr.c | 46 +++---
Hi!
Thanks for looking into this!
On Wed, Oct 02, 2013 at 11:10:18AM -0400, Theodore Ts'o wrote:
> On Wed, Sep 25, 2013 at 11:00:34AM +0200, Hannes Frederic Sowa wrote:
> > [PATCH RFC] random: introduce get_random_bytes_busy_wait_initialized
> >
> > We want to use good entropy for initializing t
On Wednesday 02 October 2013 01:09 PM, Will Deacon wrote:
> On Wed, Oct 02, 2013 at 05:55:28PM +0100, Santosh Shilimkar wrote:
>> The sched_clock code uses 2 levels of function pointers, sched_clock_func()
>> and read_sched_clock() but the no sched_clock check in postinit() just
>> checks read_sche
On Wed, 2 Oct 2013, Catalin Marinas wrote:
> On Wed, Oct 02, 2013 at 06:03:46PM +0100, Stefano Stabellini wrote:
> > On Tue, 1 Oct 2013, Catalin Marinas wrote:
> > > On 30 Sep 2013, at 16:31, Konrad Rzeszutek Wilk
> > > wrote:
> > > > On Fri, Sep 27, 2013 at 05:09:58PM +0100, Stefano Stabellini w
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/net/ethernet/emulex/benet/be_main.c | 38 ++---
The real issue is that some devices (xgmac, I am looking at you), don't
set the dma_mask, even though they are perfectly capable of doing dma.
Maybe I should modify the arm implementation of dma_capable (see
http://marc.info/?l=linux-kernel&m=138029832007821&w=2) to ignore the
dma_mask.
On Mon, 3
On Tue, 2013-10-01 at 06:22 +0200, Manfred Spraul wrote:
> Hi Davidlohr,
>
> On 09/30/2013 07:54 PM, Davidlohr Bueso wrote:
> > Hi Manfred,
> >
> > On Mon, 2013-09-30 at 11:13 +0200, Manfred Spraul wrote:
> >> After acquiring the semlock spinlock, the operations must test that the
> >> array is st
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/net/ethernet/chelsio/cxgb3/cxgb3_main.c | 29 -
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/net/ethernet/brocade/bna/bnad.c | 34 -
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/scsi/hpsa.c | 28 +---
1 files cha
On Wed, Oct 02, 2013 at 05:55:28PM +0100, Santosh Shilimkar wrote:
> The sched_clock code uses 2 levels of function pointers, sched_clock_func()
> and read_sched_clock() but the no sched_clock check in postinit() just
> checks read_sched_clock().
>
> This leads to kernel falling back to jiffy base
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/net/ethernet/neterion/vxge/vxge-main.c | 36 ++
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/scsi/csiostor/csio_isr.c | 18 --
1 files
On Wed, Oct 02, 2013 at 06:03:46PM +0100, Stefano Stabellini wrote:
> On Tue, 1 Oct 2013, Catalin Marinas wrote:
> > On 30 Sep 2013, at 16:31, Konrad Rzeszutek Wilk
> > wrote:
> > > On Fri, Sep 27, 2013 at 05:09:58PM +0100, Stefano Stabellini wrote:
> > >> xen_swiotlb_alloc_coherent needs to allo
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/block/nvme-core.c | 48 +++
On Wed, Oct 02, 2013 at 08:43:52AM -0700, H. Peter Anvin wrote:
> On 10/02/2013 03:04 AM, Borislav Petkov wrote:
> > When we start allocating from -4G, i.e. 0x, I think we
> > want to do it bottom-up so that 0x is the *last*, i.e.
> > lowest address. Because we link
On Tue, Oct 01, 2013 at 09:48:43PM +0100, Stephen Boyd wrote:
> This config item already exists generically in lib/Kconfig.debug.
> Remove the duplicate config in arm64.
>
> Signed-off-by: Stephen Boyd
Thanks. Applied.
--
Catalin
--
To unsubscribe from this list: send the line "unsubscribe lin
On Tue, 1 Oct 2013, Catalin Marinas wrote:
> On 30 Sep 2013, at 16:31, Konrad Rzeszutek Wilk
> wrote:
> > On Fri, Sep 27, 2013 at 05:09:58PM +0100, Stefano Stabellini wrote:
> >> xen_swiotlb_alloc_coherent needs to allocate a coherent buffer for cpu
> >> and devices. On native x86 and ARMv8 is su
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/net/ethernet/broadcom/tg3.c | 24 +---
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/net/ethernet/mellanox/mlx5/core/main.c | 18 +-
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/net/ethernet/sfc/efx.c | 18 +++---
1 files ch
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/rapidio/devices/tsi721.c | 27 +--
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c | 18 +++
Do not trust the hardware and always check if MSI
Revert to Single Message mode was enforced. Fall
back to the single MSI mode in case it did. Not
doing so might screw up the interrupt handling.
Signed-off-by: Alexander Gordeev
---
drivers/ata/ahci.c | 17 +
drivers/ata/ahci.h
The sched_clock code uses 2 levels of function pointers, sched_clock_func()
and read_sched_clock() but the no sched_clock check in postinit() just
checks read_sched_clock().
This leads to kernel falling back to jiffy based sched clock even in
presence of sched_clock_func() which is not desirable.
On 10/2/2013 11:15 AM, Oleg Nesterov wrote:
On 10/02,suravee.suthikulpa...@amd.com wrote:
>
>From: Suravee Suthikulpanit
>
>Frederic, this is the rebase of the V4 patch onto the linux-3.12.0-rc3
(linux.git),
>and retest.
But the code is the same? If yes,
Reviewed-by: Oleg Nesterov
The only
From: James Bates
The dmi_list array is initialized using gnu designated initializers, and
therefore may contain fewer explicitly defined entries as there are
elements in it. This is because the enum above with M_xyz constants
contains more items than the designated initializer. Those elements no
On Wed, Oct 02, 2013 at 12:43:26PM -0400, Steven Rostedt wrote:
> > I keep hititng that other ftrace bug instead:
> >
> > WARNING: CPU: 2 PID: 15596 at kernel/trace/ftrace.c:1701
> > ftrace_bug+0x206/0x270()
> > Modules linked in: snd_seq_dummy(+) rfcomm hidp bnep nfnetlink
> > scsi_tran
02.10.2013 17:34, Takashi Iwai kirjoitti:
> At Tue, 1 Oct 2013 23:30:52 +0300,
> Anssi Hannula wrote:
[...]
>> Anssi Hannula (4):
>> ALSA: hda - hdmi: Add ATI/AMD multi-channel audio support
>> ALSA: hda - hdmi: Add ELD emulation for ATI/AMD codecs
>> ALSA: hda - hdmi: Add HBR bi
On 02/10/2013 17:51, Guenter Roeck wrote:
On Fri, Jun 21, 2013 at 03:23:34PM -, Boris BREZILLON wrote:
Add new at91sam9 watchdog properties to the documentation.
Signed-off-by: Boris BREZILLON
Acked-by: Grant Likely
---
.../devicetree/bindings/watchdog/atmel-wdt.txt | 30 +++
On Wed, Oct 2, 2013 at 3:37 PM, Djalal Harouni wrote:
> On Tue, Oct 01, 2013 at 06:40:41PM -0700, Andy Lutomirski wrote:
>> On 10/01/2013 01:26 PM, Djalal Harouni wrote:
>> > /proc//* entries varies at runtime, appropriate permission checks
>> > need to happen during each system call.
>> >
>> > Cu
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/scsi/pmcraid.c | 23 +++
1 files chang
On 2 October 2013 22:08, Rafael J. Wysocki wrote:
> On Wednesday, October 02, 2013 02:13:36 PM Viresh Kumar wrote:
>> On 30 September 2013 23:58, Rafael J. Wysocki wrote:
>> > On Monday, September 16, 2013 08:40:17 PM Viresh Kumar wrote:
>> >> lock_policy_rwsem_{read|write}() currently has return
On Wed, Oct 02, 2013 at 06:34:18PM +0200, Henrik Rydberg wrote:
> > >>One thing I have seen in all logs is the earlier "send_byte fail"
> > >>message, so
> > >>I think that is a pre-requisite.
> > >
> > >Not necessarily - it could be that the patch actually fixes the root
> > >cause. One possible
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/block/cciss.c | 17 +++--
1 files changed, 7 i
On Wed, Oct 2, 2013 at 4:14 PM, Djalal Harouni wrote:
> On Tue, Oct 01, 2013 at 06:39:00PM -0700, Andy Lutomirski wrote:
>> On 10/01/2013 01:26 PM, Djalal Harouni wrote:
>> > Some fields of the /proc/*/stat are sensitive fields that need
>> > appropriate protection.
>> >
>> > However, /proc file d
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/net/ethernet/mellanox/mlx4/main.c | 17 -
On Wed, Oct 2, 2013 at 3:55 PM, Djalal Harouni wrote:
> On Tue, Oct 01, 2013 at 06:36:34PM -0700, Andy Lutomirski wrote:
>> On 10/01/2013 01:26 PM, Djalal Harouni wrote:
>> > Since /proc entries varies at runtime, permission checks need to happen
>> > during each system call.
>> >
>> > However eve
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Note, in case just one MSI-X vector was available the
error message "0484 PCI enable MSI-X failed 1" is
pre
On Wed, 2 Oct 2013 14:08:44 +0300
Taras Kondratiuk wrote:
> From: Danke Xie
>
> The current TWL 6030 IRQ handler assumes little endianness.
> This change makes it endian-neutral.
>
> Signed-off-by: Danke Xie
> Signed-off-by: Taras Kondratiuk
> ---
this patch causes a new sparse warning:
m
On Wed, 2013-10-02 at 10:16 -0400, Dave Jones wrote:
> On Tue, Oct 01, 2013 at 08:28:51AM -0400, Steven Rostedt wrote:
> > On Tue, 2013-10-01 at 00:20 -0400, Dave Jones wrote:
> >
> > > It seems like trace-cmd needs to be run as root. all hell will break
> loose if trinity gets root privs.
>
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/net/ethernet/broadcom/bnx2.c | 27 ++--
On Wed, Oct 02, 2013 at 06:22:29PM +0200, Daniel Lezcano wrote:
> On 10/02/2013 05:57 PM, Frederic Weisbecker wrote:
> >2013/10/2 Daniel Lezcano :
> >>The sleep_length is computed in the tick_nohz_stop_sched_tick function but
> >>it
> >>is used later in the code with in between the local irq enabl
On 10/02/2013 11:28 PM, Toshi Kani wrote:
> On Wed, 2013-10-02 at 03:10 +, Chen Gang wrote:
>> Hello Maintainers:
>>
>> Under my x86_64 dual core laptop, I build kernel next-20130927 with
>> 'allmodconfig', and install it, the machine can not start. Related
>> information is:
>>
>> after call
The dmi_list array is initialized using gnu designated initializers, and
therefore may contain fewer explicitly defined entries as there are
elements in it. This is because the enum above with M_xyz constants
contains more items than the designated initializer. Those elements not
explicitly initial
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/scsi/megaraid/megaraid_sas_base.c | 20 +--
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/scsi/qla2xxx/qla_isr.c | 18 +++---
1 files ch
(10/2/13 10:27 AM), Jan Kara wrote:
> Signed-off-by: Jan Kara
> ---
> mm/process_vm_access.c | 8 ++--
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/mm/process_vm_access.c b/mm/process_vm_access.c
> index fd26d0433509..c1bc47d8ed90 100644
> --- a/mm/process_vm_access.c
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/misc/vmw_vmci/vmci_guest.c | 22 +++---
1
On 10/02, Peter Zijlstra wrote:
>
> On Wed, Oct 02, 2013 at 04:00:20PM +0200, Oleg Nesterov wrote:
> > And again, even
> >
> > for (;;) {
> > percpu_down_write();
> > percpu_up_write();
> > }
> >
> > should not completely block the readers.
>
> Sure there's a tiny wi
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/infiniband/hw/mthca/mthca_main.c | 16 +++-
1
As result of recent re-design of the MSI/MSI-X interrupts enabling
pattern this driver has to be updated to use the new technique to
obtain a optimal number of MSI/MSI-X interrupts required.
Signed-off-by: Alexander Gordeev
---
drivers/net/ethernet/sun/niu.c | 20 +++-
1 files
> >>One thing I have seen in all logs is the earlier "send_byte fail" message,
> >>so
> >>I think that is a pre-requisite.
> >
> >Not necessarily - it could be that the patch actually fixes the root
> >cause. One possible scenario is that on recent SMCs, some of the
> >commands produce more data t
On Wed, Oct 02, 2013 at 11:56:23AM -0400, Kevin Mulvey wrote:
> replace all kerneli with kernel
kerneli is correct in this case.
--
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://vger.ker
(10/2/13 10:27 AM), Jan Kara wrote:
> Provide a wrapper for get_user_pages() which takes care of acquiring and
> releasing mmap_sem. Using this function reduces amount of places in
> which we deal with mmap_sem.
>
> Signed-off-by: Jan Kara
> ---
> include/linux/mm.h | 14 ++
> 1 fi
On Wed, Oct 02, 2013 at 04:57:12PM +0100, Christoph Lameter wrote:
> On Wed, 2 Oct 2013, Bird, Tim wrote:
>
> > The problem child is actually the unconditional call to kmemleak_alloc()
> > in kmalloc_large_node() (in slub.c). The problem comes because that call
> > is unconditional on CONFIG_SLUB
On Wednesday, October 02, 2013 02:13:36 PM Viresh Kumar wrote:
> On 30 September 2013 23:58, Rafael J. Wysocki wrote:
> > On Monday, September 16, 2013 08:40:17 PM Viresh Kumar wrote:
> >> lock_policy_rwsem_{read|write}() currently has return type of int but it
> >> always
> >> return zero and he
On Wed, Oct 02, 2013 at 04:27:57PM +0200, Jan Kara wrote:
> Provide a wrapper for get_user_pages() which takes care of acquiring and
> releasing mmap_sem. Using this function reduces amount of places in
> which we deal with mmap_sem.
>
> Signed-off-by: Jan Kara
Seem like this should be the defau
On 01/10/13 15:49, Mauro Carvalho Chehab wrote:
>>> > >
>>> > > Btw, we're even thinking on mapping HDMI-CEC remote controller RX/TX via
>>> > > the RC subsystem. So, another L1 protocol would be "hdmi-cec".
>>> > >
>> > Ok.
>>> > > Yet, it seems unlikely that the very same remote controller IP w
On Wed, 2 Oct 2013, Catalin Marinas wrote:
> Kmemleak doesn't depend on SLUB_DEBUG (at least it didn't originally ;),
> so I don't think we should add an artificial dependency (or select). Can
> we have kmemleak_*() calls in both debug and !debug hooks?
Yes if you move the hook calls out from und
Hi
On Wed, Oct 2, 2013 at 6:16 PM, Stephen Warren wrote:
> On 10/02/2013 08:58 AM, David Herrmann wrote:
>> Unfortunately, fbdev does not create its own "struct device" for
>> framebuffers. Instead, it attaches to the device of the parent layer. This
>> has the side-effect that devm_* managed res
On 10/02/2013 05:57 PM, Frederic Weisbecker wrote:
2013/10/2 Daniel Lezcano :
The sleep_length is computed in the tick_nohz_stop_sched_tick function but it
is used later in the code with in between the local irq enabled.
cpu_idle_loop
tick_nohz_idle_enter [ exits with local irq enabl
On 10/02, suravee.suthikulpa...@amd.com wrote:
>
> From: Suravee Suthikulpanit
>
> Frederic, this is the rebase of the V4 patch onto the linux-3.12.0-rc3
> (linux.git),
> and retest.
But the code is the same? If yes,
Reviewed-by: Oleg Nesterov
To remind, a range on executable breakpoint is p
On 10/02/2013 08:58 AM, David Herrmann wrote:
> Unfortunately, fbdev does not create its own "struct device" for
> framebuffers. Instead, it attaches to the device of the parent layer. This
> has the side-effect that devm_* managed resources are not cleaned up on
> framebuffer-destruction but rathe
Em Wed, Oct 02, 2013 at 04:46:59PM +0300, Adrian Hunter escreveu:
> On 02/10/13 16:23, Jiri Olsa wrote:
> > hi,
> > got a segfault in the tsc test on latest acme's tree.
> >
> > I'm dealing with some other issues right now, so just reporting ;-)
>
> The capability bits have changed positions. Yo
From: Jacob Shin
Currently bp_len is given a default value of 4. Allow user to override it:
$ perf stat -e mem:0x1000/8
^
bp_len
If no value is given, it will default to 4 as it did before.
Signed-off-by: Jacob Shin
Signed-off-by: Sura
Em Wed, Oct 02, 2013 at 01:59:36PM +0200, Jiri Olsa escreveu:
> On Wed, Oct 02, 2013 at 05:03:48PM +0530, Ramkumar Ramachandra wrote:
> > Jiri Olsa wrote:
> > > what perf version are you running?
> > I'm running off the one in torvalds/linux.git.
> > $ perf --version
> > perf version 3.12.rc3.g34
On Fri, Jun 21, 2013 at 03:21:28PM -, Boris BREZILLON wrote:
> The at91sam9 watchdog timer can only be configured once, and the current
> implementation tries to configure it in a static way:
> - 2 seconds timeout
> - wdt restart every 500ms
>
> If the timer has already been configured with di
On 10/02/2013 05:37 AM, Laxman Dewangan wrote:
> Palmas devices do not support the default bias configuration
> and hence removing this option from valid pin config parameters.
Acked-by: Stephen Warren
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mes
From: Jacob Shin
Implement hardware breakpoint address mask for AMD Family 16h and
above processors. CPUID feature bit indicates hardware support for
DRn_ADDR_MASK MSRs. These masks further qualify DRn/DR7 hardware
breakpoint addresses to allow matching of larger addresses ranges.
Valuable advic
From: Jacob Shin
Signed-off-by: Jacob Shin
Signed-off-by: Suravee Suthikulpanit
---
tools/perf/tests/parse-events.c | 55 +
1 file changed, 55 insertions(+)
diff --git a/tools/perf/tests/parse-events.c b/tools/perf/tests/parse-events.c
index 48114d1..9b
From: Suravee Suthikulpanit
Frederic, this is the rebase of the V4 patch onto the linux-3.12.0-rc3
(linux.git),
and retest.
The following patchset enables hardware breakpoint bp_len greater than
HW_BREAKPOINT_LEN_8 on AMD Family 16h and later.
$ perf stat -e mem:0x1000/16:w a.out
On 10/02/2013 04:40 AM, Linus Walleij wrote:
> On Fri, Sep 27, 2013 at 6:06 PM, Stephen Warren wrote:
>> [Laxman]
>>> Hmm.. When I added the PIN_DEFAULT, I just though that do not update
>>> anything in the register and implemented like that.
>>> There is nothing "default" option in HW.
>>
>> The
change kerneli to kernel as well as kerneli.org to kernel.org
Signed-off-by: Kevin Mulvey
---
Documentation/crypto/api-intro.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/crypto/api-intro.txt
b/Documentation/crypto/api-intro.txt
index 8b49302..94c2e8c 100
On Wed, 2013-10-02 at 17:35 +0200, Michal Simek wrote:
> This new fpga subsystem core should unify all fpga drivers/managers which
> do the same things. Load configuration data to fpga or another programmable
> logic through common interface. It doesn't matter if it is MMIO device,
> gpio bitbangin
When CR4.PAE is set, the 64b PTE's are used(ARCH_PHYS_ADDR_T_64BIT is set for
X86_64 || X86_PAE). According to [1] Chapter 4 Paging, some higher bits in 64b
PTE are reserved and have to be set to zero. For example, for IA-32e and 4KB
page [1] 4.5 IA-32e Paging: Table 4-19, bits 51-M(MAXPHYADDR) are
On Wed, Oct 02, 2013 at 07:35:49AM -0700, Arjan van de Ven wrote:
> On 10/2/2013 5:45 AM, Frederic Weisbecker wrote:
> >On Tue, Oct 01, 2013 at 06:59:57PM +0200, Peter Zijlstra wrote:
> >>On Tue, Oct 01, 2013 at 06:47:10PM +0200, Frederic Weisbecker wrote:
> >>>Yeah thinking more about it, the pree
On Wed, 2 Oct 2013, Bird, Tim wrote:
> The problem child is actually the unconditional call to kmemleak_alloc()
> in kmalloc_large_node() (in slub.c). The problem comes because that call
> is unconditional on CONFIG_SLUB_DEBUG but the kmemleak
> calls in the hook routines are conditional on CONFI
2013/10/2 Daniel Lezcano :
> The sleep_length is computed in the tick_nohz_stop_sched_tick function but it
> is used later in the code with in between the local irq enabled.
>
> cpu_idle_loop
> tick_nohz_idle_enter [ exits with local irq enabled ]
>__tick_nohz_idle_enter
> tick_n
replace all kerneli with kernel
Signed-off-by: Kevin Mulvey
---
crypto/Kconfig | 2 +-
crypto/serpent_generic.c | 2 +-
crypto/testmgr.h | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/crypto/Kconfig b/crypto/Kconfig
index 69ce573..84698cf 100644
--- a/
On 10/02, Peter Zijlstra wrote:
>
> From: Oleg Nesterov
Thanks! I was writing the patch, and I chose almost the same naming ;)
> Signed-off-by: Peter Zijlstra
Signed-off-by: Oleg Nesterov
In fact I'd like to add my sob to 1/3 and 3/3 as well.
Paul, to remind, this is only the first step. I
On Wed, Oct 02, 2013 at 04:33:47PM +0100, Bird, Tim wrote:
> On Wednesday, October 02, 2013 7:41 AM, Christoph Lameter [c...@linux.com]
> wrote:
> >
> >On Fri, 27 Sep 2013, Frank Rowand wrote:
> >
> >> Move the kmemleak code for small block allocation out from
> >> under CONFIG_SLUB_DEBUG.
> >
> >
On Wed, 02 Oct 2013, Laxman Dewangan wrote:
> The ams AS3722 is a compact system PMU suitable for mobile phones,
> tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
> controller, 11 LDOs, RTC, automatic battery, temperature and
> over-current monitoring, 8 GPIOs, ADC and a watchd
On Fri, Jun 21, 2013 at 03:23:34PM -, Boris BREZILLON wrote:
> Add new at91sam9 watchdog properties to the documentation.
>
> Signed-off-by: Boris BREZILLON
> Acked-by: Grant Likely
>
> ---
> .../devicetree/bindings/watchdog/atmel-wdt.txt | 30 ++--
> 1 file changed, 28
On Wed, 2 Oct 2013, Robert Baldyga wrote:
> This patch fix validation of maxpacket value given in endpoint descriptor.
> Add check of maxpacket for bulk endpoints. If maxpacket is not set in
> descriptor, it's set to maximum value for given type on endpoint in used
> speed.
>
> Correct maxpacket
On 10/02/2013 07:07 PM, Miklos Szeredi wrote:
On Wed, Oct 2, 2013 at 1:17 PM, Maxim Patlasov wrote:
If writeback happens while fuse is in FUSE_NOWRITE condition, the request
will be queued but not processed immediately (see fuse_flush_writepages()).
Until FUSE_NOWRITE becomes relaxed, more writ
On 10/02/2013 03:04 AM, Borislav Petkov wrote:
> When we start allocating from -4G, i.e. 0x, I think we
> want to do it bottom-up so that 0x is the *last*, i.e.
> lowest address. Because we link the kernel text at 0x8100 by
> default, which would mean, if
On Wednesday, October 02, 2013 7:41 AM, Christoph Lameter [c...@linux.com]
wrote:
>
>On Fri, 27 Sep 2013, Frank Rowand wrote:
>
>> Move the kmemleak code for small block allocation out from
>> under CONFIG_SLUB_DEBUG.
>
>Well in that case it may be better to move the hooks as a whole out of
>the C
On Wed, 2013-10-02 at 13:35 +0300, Gleb Natapov wrote:
> On Wed, Oct 02, 2013 at 12:23:26PM +0200, Andre Richter wrote:
> > When KVM (de)assigns PCI(e) devices to VMs, a debug message is printed
> > including the BDF notation of the respective device. Currently, the BDF
> > notation does not have t
On Wed 02-10-13 15:32:47, Marciniszyn, Mike wrote:
> > > The risk of GUP fast is the loss of the "force" arg on GUP fast, which
> > > I don't see as significant give our use case.
> > Yes. I was discussing with Roland some time ago whether the force
> > argument is needed and he said it is. So I
Instead of allowing only a single atomic update (both in memory and on disk
orphan lists) of an ext4's orphan list via the s_orphan_lock mutex, this patch
allows multiple updates of the orphan list, while still maintaing the
integrity of both the in memory and on disk orphan lists of each update.
Adding new members, i_prev_oprhan to help decoupling the ondisk from the
in memory orphan list and i_mutex_orphan_mutex to serialize orphan list
updates on a single inode, to the ext4_inode_info structure.
Adding a new member, s_ondisk_oprhan_lock to protect the ondisk orphan list
and change s_orp
501 - 600 of 909 matches
Mail list logo
