On Tue, Jul 10, 2012 at 9:54 AM, Jiang Liu wrote:
> From: Jiang Liu
>
> Use PCIe cap access functions to simplify pcihp_slot.c
>
> Signed-off-by: Jiang Liu
> ---
> drivers/pci/hotplug/pcihp_slot.c | 17 +
> 1 file changed, 9 insertions(+), 8 deletions(-)
>
> diff --git a/drive
On Tue, Jul 10, 2012 at 10:12:17AM -0700, Tony Luck wrote:
> On Tue, Jul 10, 2012 at 8:44 AM, Borislav Petkov wrote:
> > Acked-by: Borislav Petkov
>
> Thanks for the Ack.
>
> + doit = !!PageDirty(ppage) || !!(flags & MF_MUST_KILL);
>
> Thinking about this some more, the "!!" are redundan
I sent a patch yesterday (or was it friday) to fix the issue. Sorry @airport
right now.
On Jul 10, 2012, at 6:17, w...@linux.intel.com wrote:
> Hi Christoph,
>
> This commit crashes the kernel w/o any dmesg output (the attached one
> is created by the script as a summary for that run). This
On Tue, Jul 10, 2012 at 08:09:53PM +0200, Olaf Hering wrote:
> On Tue, Jul 10, Konrad Rzeszutek Wilk wrote:
>
> > On Tue, Jul 10, 2012 at 05:23:08PM +0200, Olaf Hering wrote:
> > > I was not thinking of statically allocated pages but some new concept of
> > > allocating such shared pages. Shouldnt
On Tue, Jul 10, 2012 at 9:54 AM, Jiang Liu wrote:
> From: Jiang Liu
>
> As suggested by Bjorn Helgaas and Don Dutile in threads
> http://www.spinics.net/lists/linux-pci/msg15663.html, we could improve access
> to PCIe capabilities register in to way:
> 1) cache content of PCIe Capabilities Regist
On Tue, Jul 10, 2012 at 9:54 AM, Jiang Liu wrote:
> From: Jiang Liu
>
> Move pcie_cap_has_*() macros to include/linux/pci.h, so they can be shared.
> Since pcie_flags was introduced, rework these macros to take a struct pci_dev
> *
> and use pcie_flags insead of type and flags.
>
> Signed-off-by
Hi,
On Sun, Jul 08, 2012 at 10:51:12PM +0400, K900 wrote:
> This adds support for Razer Onza Tournament Edition (
> http://store.razerzone.com/store/razerusa/en_US/pd/productID.218524000/categoryId.54297600
> ) controller to the xpad module. It's very simple, I just added
> another entry to the de
>-Original Message-
>From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org]
>On Behalf Of Joe Jin
>Sent: Tuesday, July 10, 2012 12:40 AM
>To: Joe Jin
>Cc: e1000-de...@lists.sf.net; net...@vger.kernel.org; linux-
>ker...@vger.kernel.org
>Subject: Re: 82571EB: Detected Hardw
From: Manoj Iyer
Patch adds support for BCM20702A0 device id (0a5c:21f4).
usb-devices after patch was applied:
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a5c ProdID=21f4 Rev=01.12
S: Manufacturer=Broadcom C
On 10/07/2012 19:09, "Olaf Hering" wrote:
>>> Are there more shared areas or is it just the shared info page?
>>>
And I am kind of worried that moving it to the .data section won't
be completly safe - as the decompressor might blow away that part too.
>>>
>>> The decompressor may just
On Tuesday, July 10, 2012 4:27 AM, Mike Wrote:
>As it happens, v2's changes to blk_limits_max_hw_sectors and
>blk_queue_max_hw_sectors are not strictly required in order for existing
>stacking drivers to have have an unconstrained max_sectors. Dropping
>those changes also allows for consistency ac
>-Original Message-
>From: Dave, Tushar N
>Sent: Tuesday, July 10, 2012 12:02 PM
>To: Joe Jin
>Cc: e1000-de...@lists.sf.net; net...@vger.kernel.org; linux-
>ker...@vger.kernel.org; Dave, Tushar N
>Subject: RE: 82571EB: Detected Hardware Unit Hang
>
>>-Original Message-
>>From: netd
On Tue, Jul 10 2012 at 3:10pm -0400,
Chauhan, Vijay wrote:
> On Tuesday, July 10, 2012 4:27 AM, Mike Wrote:
> >As it happens, v2's changes to blk_limits_max_hw_sectors and
> >blk_queue_max_hw_sectors are not strictly required in order for existing
> >stacking drivers to have have an unconstraine
Hi Tejun,
On Mon, Jul 09, 2012 at 10:28:31AM -0700, Tejun Heo wrote:
> On Mon, Jul 09, 2012 at 10:22:20AM -0700, Tejun Heo wrote:
> > > Changing subsys_bits via remount is being deprecated. No need to
> > > worry about this.
> >
> > Also, why does this matter? The xattrs are kept in cgrp anyway.
Hi Federico,
On Tue, Jul 10, 2012 at 7:43 PM, Federico Fuga wrote:
> omaprpc is out of the official mainline code, it's inside the official
> ti/omap branch/project.
Ok, thanks for the explanation. In general, we don't change the
mainline kernel to solve issues with out-of-tree code.
> I guess
Currently Pause Looop Exit (PLE) handler is doing directed yield to a
random VCPU on PL exit. Though we already have filtering while choosing
the candidate to yield_to, we can do better.
Problem is, for large vcpu guests, we have more probability of yielding
to a bad vcpu. We are not able to prev
From: Raghavendra K T
Noting pause loop exited vcpu helps in filtering right candidate to yield.
Yielding to same vcpu may result in more wastage of cpu.
Signed-off-by: Raghavendra K T
---
arch/x86/include/asm/kvm_host.h | 11 +++
arch/x86/kvm/svm.c |1 +
arch/x86/k
From: Raghavendra K T
Currently PLE handler can repeatedly do a directed yield to same vcpu
that has recently done PL exit. This can degrade the performance.
Try to yield to most eligible guy instead by alternate yielding.
Precisely, give chance to a VCPU which has:
(a) Not done PLE exit at all
Hi Dmitry,
On 10/07/12 18:41, Dmitry Torokhov wrote:
> Ah, right, I meant to change that too ;)
>
> Could you please try this one for me (instead of the previous one)?
Same problem (you actually sent the same patch).
I'm posting an updated version considering all your suggestions from
your last
This patch adds a driver for the key scan interface of the LPC32xx SoC
Signed-off-by: Roland Stigge
---
Applies to v3.5-rc6
Changes since v8:
* Optimized lpc32xx_mod_states() to shift "changed" word and break on 0
* lpc32xx_parse_dt(): Return -EINVAL instead of -ENXIO
* kfree() of keymap _after
On 07/10/2012 03:31 PM, Raghavendra K T wrote:
From: Raghavendra K T
Noting pause loop exited vcpu helps in filtering right candidate to yield.
Yielding to same vcpu may result in more wastage of cpu.
Signed-off-by: Raghavendra K T
Reviewed-by: Rik van Riel
--
All rights reversed
--
To unsu
On 07/10/2012 03:31 PM, Raghavendra K T wrote:
From: Raghavendra K T
Currently PLE handler can repeatedly do a directed yield to same vcpu
that has recently done PL exit. This can degrade the performance.
Try to yield to most eligible guy instead by alternate yielding.
Precisely, give chance to
Hi Manoj,
* manoj.i...@canonical.com [2012-07-10 14:07:38
-0500]:
> From: Manoj Iyer
>
> Patch adds support for BCM20702A0 device id (0a5c:21f4).
>
> usb-devices after patch was applied:
> T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
> D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot
On Mon, 9 Jul 2012, David Rientjes wrote:
> kmemcheck_alloc_shadow() requires irqs to be enabled, so wait to disable
> them until after its called for __GFP_WAIT allocations.
>
> This fixes a warning for such allocations:
>
> WARNING: at kernel/lockdep.c:2739 lockdep_trace_alloc+0x14e/0x1c0
On Jul 10, 2012, at 6:17, w...@linux.intel.com wrote:
>> This commit crashes the kernel w/o any dmesg output (the attached one
>> is created by the script as a summary for that run). This is very
>> reproducible in kvm for the attached config.
>>
>>commit 3b0efdfa1e719303536c04d9abca43abeb4
Hello Peter,
2012/7/10 Peter Zijlstra :
> On Wed, 2012-07-04 at 13:08 +0400, Andrew Vagin wrote:
>> From: Peter Zijlstra
>>
>> A few events are interesting not only for a current task.
>> For example, sched_stat_* are interesting to a task, which
>> wake up. For this reason, it will be good, if s
On Wed, 11 Jul 2012, Yuri Khan wrote:
> * Add this device to usbhid ignore list
> ---
> drivers/hid/hid-core.c|1 +
> drivers/hid/hid-ids.h |3 +++
Acked-by: Jiri Kosina
> drivers/input/joystick/xpad.c |1 +
> 3 files changed, 5 insertions(+)
>
> diff --git a/drive
On Wed, 04 Jul 2012 16:34:51 +0100
Alan Cox wrote:
> From: Alan Cox
>
> Coverity 703573
>
> Signed-off-by: Alan Cox
It would be nice to have a Reported-by here, but we were only given
"Scan Subscription ".
Is there some human behind these reports? If so, can that person's
details please be
Hi Linus,
yes, this is a *LATE* GPIO pull request with fixes for v3.5.
Grant moved across the planet and accidentally fell off the grid, so he asked
me to take over the GPIO merges for a while 10 days ago, refer to:
https://lkml.org/lkml/2012/7/1/220
Since then I went over the archives and colle
Am 10.07.2012 19:14, schrieb Joe Perches:
On Tue, 2012-07-10 at 11:10 +0100, Catalin Marinas wrote:
On Tue, Jul 10, 2012 at 08:10:23AM +0100, Ingo Molnar wrote:
* Arnd Bergmann wrote:
On Saturday 07 July 2012, Olof Johansson wrote:
ARM introduced AArch64 as part of the ARMv8 architecture
W
On Mon, Jul 9, 2012 at 4:45 PM, Anton Vorontsov
wrote:
> Just a few patches left from the series that used to add configurable
> ECC size for pstore/ram backend. Most patches were merged into -next,
> and this is just a resend of the leftovers.
Feel free to add my:
Acked-by: Kees Cook
to this
* Arnd Bergmann wrote:
> > What plans to other maintainers and board vendors have ? Any
> > design choice has to cope with these happening if a third
> > party goes and does it.
>
> It is slightly worrying to have multiple SoC vendors working
> on their own platform support. There are a few
Hi Yuri,
On Wed, Jul 11, 2012 at 12:33:22AM +0700, Yuri Khan wrote:
> * Add this device to usbhid ignore list
Please do not forget your "Signed-off-by: " so that I can apply the
patch.
Thanks.
> ---
> drivers/hid/hid-core.c|1 +
> drivers/hid/hid-ids.h |3 +++
> drivers
* Raghavendra K T wrote:
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -1595,6 +1595,9 @@ void kvm_vcpu_on_spin(struct kvm_vcpu *me)
> continue;
> if (waitqueue_active(&vcpu->wq))
> continue;
> +
Hi,
On 10.07.2012 03:01, Joseph Salisbury wrote:
> Some users are hitting a bug reported in bugzilla[0] and launchpad[1].
> The bug was introduced in v3.5-rc1, which is preventing some Logitech
> webcams from working. I bisected down to the following commit as the
> cause of the regression:
>
>
Hi Roland,
On Tue, Jul 10, 2012 at 09:35:10PM +0200, Roland Stigge wrote:
> This patch adds a driver for the key scan interface of the LPC32xx SoC
>
Could of more things that I had in my patch but forgot to specifically
call out:
> +
> + /* Configure the key scanner */
> + clk_prepare_e
The types for ARCH_KMALLOC_MINALIGN and ARCH_SLAB_MINALIGN are not always
the same, as seen by building ARM collie_defconfig:
mm/slob.c: In function 'kfree':
mm/slob.c:482:153: warning: comparison of distinct pointer types lacks a cast
mm/slob.c: In function 'ksize':
mm/slob.c:501:153: warning: co
On Tue, Jul 10, 2012 at 10:16 PM, Linus Walleij
wrote:
> yes, this is a *LATE* GPIO pull request with fixes for v3.5.
Grr! So typically -next washed out a bug in the bug fixes. This v2 of the
pull request fixes another OF/DT related issue caused by fixing another
OF/DT related issue, courtesy of
On Mon, Jul 9, 2012 at 11:21 PM, Lee Jones wrote:
> On 09/07/12 23:03, Linus Walleij wrote:
>> Now since I was fooled by the last patch, thinking you had tested it
>> before
>> submitting (obviously not) - please send a test log of some
>> cat /dev/input/event* for this one before I ACK it this t
On Tue, Jul 10, 2012 at 1:14 PM, Stephen Rothwell wrote:
> Linus (Walleij), Stephen, Grant, can someone please send this patch to
> Linus (Torvalds)?
I sent it by pill request a few minutes ago.
Ironically my pull request was postponed two days for the sole reason of
getting some rotation of th
On Tuesday 10 July 2012, Ingo Molnar wrote:
> So are you really convinced that the colorful ARM SoC world is
> not going to go 64-bit and will all unify behind a platform, and
> that we can actually force this process by not accepting
> non-generic patches? Is such a platform design being enforc
On Sat, 30 Jun 2012 15:00:57 +0300
Octavian Purdila wrote:
> When the requested and root ranges do not intersect the logic in
> __reserve_region_with_split will cause an infinite recursion which
> will overflow the stack as seen in the warning bellow.
>
> This particular stack overflow was cause
On Thursday 14 June 2012, Roland Stigge wrote:
> --- linux-2.6.orig/arch/arm/mach-lpc32xx/phy3250.c
> +++ linux-2.6/arch/arm/mach-lpc32xx/phy3250.c
> @@ -226,7 +226,38 @@ static int __init phy3250_spi_board_regi
> }
> arch_initcall(phy3250_spi_board_register);
>
> +static struct pl08x_channel_d
Hi Andew,
The two reports that were sent on 6/28 and 7/6, were sent manually by us,
Coverit Scan Admin, project dedicated for Open Source Community.
But going forward (next week), it will be completely automated.
Based on the suggestions we got from some of the lead Linux Developer, weekly
repo
(just replying to a couple of points now, I'll follow up tomorrow)
On Tue, Jul 10, 2012 at 09:35:27PM +0100, Ingo Molnar wrote:
> Do you *really* think that all of the 32-bit ARM code should
> essentially be thrown away when going to 64-bit ARM, that
> patches can only touch arch/arm64/ + driver
Ingo:
Please consider applying the following patches while Arnaldo is on
vacaction. They apply to tip/perf/urgent. Arguably on the 3rd one really
should go into 3.5. The first, second and fourth patches should cleanly
to tip/perf/core. Hopefully the fourth patch walks an rbtree correctly.
David A
COMM events are generated in the context of a guest machine, so the thread
name is never set for the VMM process. For example, the qemu-kvm name
applies to the process in the host machine. Samples for guest mode are
currently displayed as:
99.67% :5671 [unknown] [g] 0x8136
e.g., perf kvm --host --guest report -i perf.data --stdio -D
shows:
1 599127912065356 0x143b8 [0x48]: PERF_RECORD_SAMPLE(IP, 5): 5671/5676:
0x7fdf95a061c0 period: 1 addr: 0
... chain: nr:2
. 0: ff80
. 1: fe00
... thread: qemu-kvm:5671
.. dso:
(IP, 5) mea
After 7ed97ad use of the guestmount option without a subdir for each
VM generates an error message for *each* sample related to that VM. Once
is enough.
Signed-off-by: David Ahern
---
tools/perf/util/map.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/perf/util/m
Guest kernel symbols are not resolved despite passing the information
needed to resolve them. e.g.,
perf kvm --guest --guestmount=/tmp/guest-mount record -a -- sleep 1
perf kvm --guest --guestmount=/tmp/guest-mount report --stdio
36.55% [guest/11399] [unknown] [g] 0x81600bc8
On Tue, Jul 10, 2012 at 10:19:38PM +0100, Arnd Bergmann wrote:
> On Tuesday 10 July 2012, Ingo Molnar wrote:
> > Do you really think that all of the 32-bit ARM code should
> > essentially be thrown away when going to 64-bit ARM, that
> > patches can only touch arch/arm64/ + drivers/ or the highwa
From: Gustavo Padovan
A lot of Broadcom Bluetooth devices provides vendor specific interface
class and we are getting flooded by patches adding new device support.
This change will help us enable support for any other Broadcom with vendor
specific device that arrives in the future.
Only the prod
On Tue, Jul 10, 2012 at 06:51:03PM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> A lot of Broadcom Bluetooth devices provides vendor specific interface
> class and we are getting flooded by patches adding new device support.
> This change will help us enable support for any other Broa
Hi Gustavo,
> A lot of Broadcom Bluetooth devices provides vendor specific interface
> class and we are getting flooded by patches adding new device support.
> This change will help us enable support for any other Broadcom with vendor
> specific device that arrives in the future.
>
> Only the pro
From: Gustavo Padovan
A lot of Broadcom Bluetooth devices provides vendor specific interface
class and we are getting flooded by patches adding new device support.
This change will help us enable support for any other Broadcom with vendor
specific device that arrives in the future.
Only the prod
Once upon a time, Catalin Marinas said:
>Changing the arch/ dir name is easy at this point. My preference is for
>consistency with the official name (that cannot be changed) and the gcc
>triplet.
What ARM Ltd. says is the "official" name isn't necessarily what the
rest of the world will call it.
I run a number of Linux servers and I noticed an interesting bug, possibly
related to a recent change in fs/proc/array.c
After upgrading from Ubuntu 2.6.24-26 to 2.6.32-40 (and higher) in Ubuntu, I
noticed that about once per month, suddenly, a user process causing the main
load on a given machine
From: Yinghai Lu
238305b "mm: remove sparsemem allocation details from the bootmem
allocator" introduced a bug in the allocation goal calculation that
put section usemaps not in the same section as the node descriptors,
creating unnecessary hotplug dependencies between them:
[0.00] node
From: Yinghai Lu
After f5bf18f "bootmem/sparsemem: remove limit constraint in
alloc_bootmem_section", usemap allocations may easily be placed
outside the optimal section that holds the node descriptor, even if
there is space available in that section. This results in unnecessary
hotplug dependen
This patch introduces a driver for Cypress All Points Addressable
I2C Trackpad, including the one in the Samsung Series 5 550 Chromebook.
This device is compatible with MT protocol type B, providing identifiable
contacts.
This driver also implements firmware updating capability via
request_firmwa
Use PCI_VENDOR_ID_* from pci_ids.h instead of creating #define locally.
Signed-off-by: Jon Mason
Cc: Jeff Kirsher
Cc: Jesse Brandeburg
Cc: Bruce Allan
Cc: Carolyn Wyborny
Cc: Don Skidmore
Cc: Greg Rose
Cc: Peter P Waskiewicz Jr
Cc: Alex Duyck
Cc: John Ronciak
---
drivers/net/ethernet/in
Remove unused IXGBE_INTEL_VENDOR_ID #define
Signed-off-by: Jon Mason
Cc: Jeff Kirsher
Cc: Jesse Brandeburg
Cc: Bruce Allan
Cc: Carolyn Wyborny
Cc: Don Skidmore
Cc: Greg Rose
Cc: Peter P Waskiewicz Jr
Cc: Alex Duyck
Cc: John Ronciak
---
drivers/net/ethernet/intel/ixgbe/ixgbe_type.h |
Remove PCI vendor IDs, as they are already defined in pci_ids.h.
Signed-off-by: Jon Mason
Cc: Achim Leubner
---
drivers/scsi/gdth.h |9 -
1 file changed, 9 deletions(-)
diff --git a/drivers/scsi/gdth.h b/drivers/scsi/gdth.h
index d3e4d7c..fbf6f0f 100644
--- a/drivers/scsi/gdth.h
++
HPET_ID_VENDOR_8086 is defined but never used. It would be a redefine
of PCI_VENDOR_ID_INTEL if it was ever used.
Signed-off-by: Jon Mason
---
arch/x86/include/asm/hpet.h |2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x86/include/asm/hpet.h b/arch/x86/include/asm/hpet.h
index 2c39
IOAT has a redefine of PCI Vendor, PCI Subvendor, etc for
PCI_VENDOR_ID_INTEL but they are never used. Remove them.
Signed-off-by: Jon Mason
Cc: Dan Williams
---
drivers/dma/ioat/hw.h |4
1 file changed, 4 deletions(-)
diff --git a/drivers/dma/ioat/hw.h b/drivers/dma/ioat/hw.h
index
Remove PCI vendor and subvendor IDs, as they are already defined in
pci_ids.h.
Signed-off-by: Jon Mason
---
drivers/scsi/megaraid.c |5 ++---
drivers/scsi/megaraid.h | 35 ---
2 files changed, 2 insertions(+), 38 deletions(-)
diff --git a/drivers/scsi/megar
On Mon, 09 Jul 2012 14:30:40 +0300, Meelis Roos said:
> It's actually more complicated than that. Old kernel images started
> misbehaving from around 2.6.35-rc5 and any kernel older than that was
> OK. When I recompiled the older kernels with squeeze gcc (migh have been
> lenny gcc before, or diff
Use PCI_VENDOR_ID_INTEL instead of creating its own vendor ID #define.
Signed-off-by: Jon Mason
Cc: Greg Kroah-Hartman
---
drivers/staging/media/dt3155v4l/dt3155v4l.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/media/dt3155v4l/dt3155v4l.c
b/drivers/
On Tue, 2012-07-10 at 15:31 -0700, Jon Mason wrote:
> Use PCI_VENDOR_ID_* from pci_ids.h instead of creating #define locally.
>
> Signed-off-by: Jon Mason
> Cc: Jeff Kirsher
> Cc: Jesse Brandeburg
> Cc: Bruce Allan
> Cc: Carolyn Wyborny
> Cc: Don Skidmore
> Cc: Greg Rose
> Cc: Peter P Waski
On Tue, 2012-07-10 at 15:31 -0700, Jon Mason wrote:
> Remove unused IXGBE_INTEL_VENDOR_ID #define
>
> Signed-off-by: Jon Mason
> Cc: Jeff Kirsher
> Cc: Jesse Brandeburg
> Cc: Bruce Allan
> Cc: Carolyn Wyborny
> Cc: Don Skidmore
> Cc: Greg Rose
> Cc: Peter P Waskiewicz Jr
> Cc: Alex Duyck
The timekeeping code misses an update of the hrtimer subsystem after a
leap second happened. Due to that timers based on CLOCK_REALTIME are
either expiring a second early or late depending on whether a leap
second has been inserted or deleted until an operation is initiated
which causes that update
From: Thomas Gleixner
We need to update the hrtimer clock offsets from the hrtimer interrupt
context. To avoid conversions from timespec to ktime_t maintain a
ktime_t based representation of those offsets in the timekeeper. This
puts the conversion overhead into the code which updates the
underly
From: Thomas Gleixner
We need to update the base offsets from this code and we need to do
that under base->lock. Move the lock held region around the
ktime_get() calls. The ktime_get() calls are going to be replaced with
a function which gets the time and the offsets atomically.
CC: Ingo Molnar
clock_was_set() cannot be called from hard interrupt context because
it calls on_each_cpu(). For fixing the widely reported leap seconds
issue it's necessary to call it from the timer interrupt context.
Provide a new function which denotes it in the hrtimer cpu base
structure of the cpu on which i
Over the weekend, Thomas got a chance to review the leap second fix
in more detail and had a few additional changes he wanted to make
to improve performance as well as style.
So this iteration includes his modifications.
Once merged, I'll be working to get the backports finished as quickly
as I c
From: Thomas Gleixner
We need to update the base offsets from this code and we need to do
that under base->lock. Move the lock held region around the
ktime_get() calls. The ktime_get() calls are going to be replaced with
a function which gets the time and the offsets atomically.
CC: Ingo Molnar
The update of the hrtimer base offsets on all cpus cannot be made
atomically from the timekeeper.lock held and interrupt disabled region
as smp function calls are not allowed there.
clock_was_set(), which enforces the update on all cpus, is called
either from preemptible process context in case of
From: Thomas Gleixner
To finally fix the infamous leap second issue and other race windows
caused by functions which change the offsets between the various time
bases (CLOCK_MONOTONIC, CLOCK_REALTIME and CLOCK_BOOTTIME) we need a
function which atomically gets the current monotonic time and updat
On 07/10/2012 03:43 PM, John Stultz wrote:
Over the weekend, Thomas got a chance to review the leap second fix
in more detail and had a few additional changes he wanted to make
to improve performance as well as style.
So this iteration includes his modifications.
Once merged, I'll be working to
On Fri, 2012-07-06 at 15:00 -0600, Toshi Kani wrote:
> Yes, offlining and eject are similar operations to a core as it alone
> cannot be removed physically. Ejecting a core is a logical eject
> operation, which updates the status (_STA) of the object in ACPI after
> offlining. The difference from
On 07/10/2012 03:43 PM, John Stultz wrote:
Over the weekend, Thomas got a chance to review the leap second fix
in more detail and had a few additional changes he wanted to make
to improve performance as well as style.
So this iteration includes his modifications.
Once merged, I'll be working to
This adds the chromeos_laptop driver. It supports
the Cypress APA SMBUS touchpad as well as the isl29018 i2c ambient
light sensor on the Samsung Series 5 550 Chromebook.
Signed-off-by: Benson Leung
---
drivers/platform/x86/Kconfig | 11 ++
drivers/platform/x86/Makefile |
On Tue, 2012-07-10 at 13:32 -0400, Konrad Rzeszutek Wilk wrote:
> On Tue, Jul 10, 2012 at 10:55:07AM -0600, Shuah Khan wrote:
> > On Mon, 2012-07-09 at 16:25 -0400, Konrad Rzeszutek Wilk wrote:
> > > On Fri, Jul 06, 2012 at 05:06:12PM -0600, Shuah Khan wrote:
> > > > Remove SWIOTLB overflow buffer
On Tue, Jul 10, 2012 at 5:19 AM, Michal Nazarewicz wrote:
> On Tue, 10 Jul 2012 01:35:14 +0200, Michel Lespinasse
> wrote:
>> +#defineRB_RED 0
>> +#defineRB_BLACK1
>
> Interestingly, those are almost never used. RB_BLACK is used only once.
> Should we get rid of
On Tue, 2012-07-10 at 17:06 -0600, Shuah Khan wrote:
> On Tue, 2012-07-10 at 13:32 -0400, Konrad Rzeszutek Wilk wrote:
> > On Tue, Jul 10, 2012 at 10:55:07AM -0600, Shuah Khan wrote:
> > > On Mon, 2012-07-09 at 16:25 -0400, Konrad Rzeszutek Wilk wrote:
> > > > On Fri, Jul 06, 2012 at 05:06:12PM -06
On Tue, Jul 10, 2012 at 3:59 AM, Daniel Santos wrote:
>> One final rb_init_node() caller was recently added in sysctl code
>> to implement faster sysctl name lookups. This code doesn't make use
>> of RB_EMPTY_NODE at all, and from what I could see it only called
>> rb_init_node() under the mistake
On Tue, Jul 10, 2012 at 5:27 AM, Michal Nazarewicz wrote:
> On Tue, 10 Jul 2012 01:35:15 +0200, Michel Lespinasse
> wrote:
>> + for (i = 0; i < CHECK_LOOPS; i++) {
>> + init();
>
> Is this init() needed?
So, the reasoning here is that we first have timed loops, where we
don'
p;
> -atomic_read(get_gcwq_nr_running(gcwq->cpu)));
> +atomic_read(get_pool_nr_running(pool)));
> }
Just had this WARN_ON_ONCE trigger on ia64 booting next-20120710. I
haven't bisected ... just noticed that two patches in this series
Here is the patch:
Subject: slob: Undo slob hunk
Commit fd3142a59af2012a7c5dc72ec97a4935ff1c5fc6 broke
slob since a piece of a change for a later patch slipped into
it.
Signed-off-by: Christoph Lameter
---
mm/slob.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6/mm
On Tue, 2012-07-10 at 16:56 -0600, Khalid Aziz wrote:
> On Fri, 2012-07-06 at 15:00 -0600, Toshi Kani wrote:
> > Yes, offlining and eject are similar operations to a core as it alone
> > cannot be removed physically. Ejecting a core is a logical eject
> > operation, which updates the status (_STA)
The 'devpriv' macro usage in this driver is holding up other cleanup
of the comedi drivers.
This patch series removes all the macros used to read/write the
hardware registers. All of them are simple wrappers around standard
{read,write}[rwl] calls with some of them caching the write value
in a sha
On 7/9/12 8:59 AM, Peter Zijlstra wrote:
On Mon, 2012-07-09 at 17:51 +0300, Avi Kivity wrote:
On 07/09/2012 05:49 PM, Peter Zijlstra wrote:
On Mon, 2012-07-09 at 08:47 -0600, David Ahern wrote:
I found this testing changes to perf-kvm, but found the problem extends
to just perf-record. With p
This macro uses the 'devpriv' macro which relies on a local variable
having a specific name. Plus it's just a wrapper around a simple
'writel'. Remove the macro.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/rtd520.c | 8 ++--
1 f
This macro uses the 'devpriv' macro which relies on a local variable
having a specific name. It's also not used. Remove it.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/rtd520.c | 4
1 file changed, 4 deletions(-)
diff --git a/
This macro uses the 'devpriv' macro which relies on a local variable
having a specific name. Plus it's just a wrapper around a simple
'writel'. Remove the macro.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/rtd520.c | 9 +++--
1
If platform_get_resource_by_name() fails, driver probe is aborted an
should return an error so the driver is not bound to the device.
However, in the current error path of platform_get_resource_by_name(),
probe returns zero since the return value (ret) is not properly set.
With a zero return value
This macro uses the 'devpriv' macro which relies on a local variable
having a specific name. Plus it's just a wrapper around a simple
'writel'. Remove the macro.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/rtd520.c | 8 ++--
1 f
This macro uses the 'devpriv' macro which relies on a local variable
having a specific name. Plus it's just a wrapper around a simple
'writel'. Remove the macro.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/rtd520.c | 8 ++--
1 f
This macro uses the 'devpriv' macro which relies on a local variable
having a specific name. Plus it's just a wrapper around a simple
'writel'. Remove the macro.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/rtd520.c | 7 ++-
1 fi
This macro uses the 'devpriv' macro which relies on a local variable
having a specific name. Plus it's just a wrapper around a simple
'writel'. Remove the macro.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/rtd520.c | 16 ++--
301 - 400 of 581 matches
Mail list logo
