A bunch of fixes for a moderately common class of bugs: file with
single_open() done by its ->open() and seq_release as its ->release().
That leaks; fortunately, it's not _too_ common (either people manage to
RTFM that says "When using single_open(), the programmer should use
From: Wei Yongjun
We have registered platform device when module init, and
need unregister it when module exit.
Signed-off-by: Wei Yongjun
---
drivers/rtc/rtc-tile.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/rtc/rtc-tile.c b/drivers/rtc/rtc-tile.c
index 249b653..fc3dee9
On Mon, 2013-04-22 at 11:41 +0100, Andrew Murray wrote:
> The pci_process_bridge_OF_ranges function, used to parse the "ranges"
> property of a PCI host device, is found in both Microblaze and PowerPC
> architectures. These implementations are nearly identical. This patch
> moves this common code
1) Several routines do not use netdev_features_t to hold such bitmasks,
fixes from Patrick McHardy and Bjørn Mork.
2) Update cpsw IRQ software state and the actual HW irq enabling in
the correct order. From Mugunthan V N.
3) When sending tipc packets to multiple bearers, we have to make
1) Hibernation support, as well as removal of excess interrupt
twiddling in MMU context allocation on sparc64 from Kirill Tkhai.
2) Kill references to __ARCH_WANT_UNLOCKED_CTXSW.
3) Sparc32 LEON bug fixes from Daniel Hellstrom and Andreas Larsson.
4) Provide cmpxchg64(), from Geert
From: Federico Vaga
Date: Mon, 15 Apr 2013 16:42:52 +0200
> The vio_remove() function uses device_find_child() but it does not drop
> the reference of the retrieved child.
>
> Signed-off-by: Federico Vaga
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Sat 2013-05-04 17:23:01, Colin Cross wrote:
> On Sat, May 4, 2013 at 5:05 PM, Pavel Machek wrote:
> > Hi!
> >
> >> >> >> --- a/kernel/exit.c
> >> >> >> +++ b/kernel/exit.c
> >> >> >> @@ -835,7 +835,7 @@ void do_exit(long code)
> >> >> >> /*
> >> >> >>* Make sure we are holding no
On Sat, May 4, 2013 at 5:30 PM, Craig Small wrote:
>
> I saw someone wants the 10 second resolution, can I get it confirmed
> that the kernel will only be updating at minute intervals (so the .1
> second stuff is completely useless) or 10 second (so the .1 second
> stuff is just confusing for
On Fri, Apr 26, 2013 at 10:02:12AM -0700, Linus Torvalds wrote:
> Craig, background: the current git kernel (so 3.9, and these commits
> will presumably be back-ported) does not update tty timestamps very
> often, because you can use the timestamps to look at peoples typing
> behavior. Initially
On Sat, May 4, 2013 at 5:05 PM, Pavel Machek wrote:
> Hi!
>
>> >> >> --- a/kernel/exit.c
>> >> >> +++ b/kernel/exit.c
>> >> >> @@ -835,7 +835,7 @@ void do_exit(long code)
>> >> >> /*
>> >> >>* Make sure we are holding no locks:
>> >> >>*/
>> >> >> -
Hi!
> >> >> --- a/kernel/exit.c
> >> >> +++ b/kernel/exit.c
> >> >> @@ -835,7 +835,7 @@ void do_exit(long code)
> >> >> /*
> >> >>* Make sure we are holding no locks:
> >> >>*/
> >> >> - debug_check_no_locks_held(tsk);
> >> >> + debug_check_no_locks_held();
> >> >
>
On Fri, 2013-05-03 at 17:08 +0200, Lennart Poettering wrote:
> It sounds really wrong to first merge this into one string and then
> split it up again. It sounds much more sensible to instead just pass the
> string array around all the time. What's the reason to make this one
> string first?
I'm
On Sat, May 4, 2013 at 3:57 PM, Pavel Machek wrote:
> On Sat 2013-05-04 13:27:23, Colin Cross wrote:
>> On Sat, May 4, 2013 at 6:04 AM, Pavel Machek wrote:
>> > On Fri 2013-05-03 14:04:10, Colin Cross wrote:
>> >> From: Mandeep Singh Baines
>> >>
>> >> We shouldn't try_to_freeze if locks are
On Sat 2013-05-04 13:27:23, Colin Cross wrote:
> On Sat, May 4, 2013 at 6:04 AM, Pavel Machek wrote:
> > On Fri 2013-05-03 14:04:10, Colin Cross wrote:
> >> From: Mandeep Singh Baines
> >>
> >> We shouldn't try_to_freeze if locks are held. Holding a lock can cause a
> >> deadlock if the lock is
Hi!
> >> NFS calls the freezable helpers with locks held, which is unsafe
> >> and caused lockdep warnings when 6aa9707 "lockdep: check that no
> >> locks held at freeze time" was applied (reverted in dbf520a).
> >> Add new *_unsafe versions of the helpers that will not run the
> >> lockdep test
On Sat, May 4, 2013 at 1:39 PM, Tejun Heo wrote:
> Hello, Rafael.
>
> On Sat, May 4, 2013 at 12:19 PM, Rafael J. Wysocki wrote:
>>> Heh, so you are aware of the deadlock possibilities. Good selection
>>> of spots. For all the conversion patches.
>>>
>>> Acked-by: Tejun Heo
>>
>> I wonder if
After upgrading to the official Arch Linux 3.9-2 kernel package, dmesg reports
that my NIC is hanging:
[ 5.955720] e1000e :00:19.0 eno1: changing MTU from 1500 to 4000
[ 8.464507] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
TDH <0>
TDT
Hello, Rafael.
On Sat, May 4, 2013 at 12:19 PM, Rafael J. Wysocki wrote:
>> Heh, so you are aware of the deadlock possibilities. Good selection
>> of spots. For all the conversion patches.
>>
>> Acked-by: Tejun Heo
>
> I wonder if that includes [3/10] (just to get the record straight)?
I
On Sat, May 4, 2013 at 6:04 AM, Pavel Machek wrote:
> On Fri 2013-05-03 14:04:10, Colin Cross wrote:
>> From: Mandeep Singh Baines
>>
>> We shouldn't try_to_freeze if locks are held. Holding a lock can cause a
>> deadlock if the lock is later acquired in the suspend or hibernate path
>> (e.g.
Assorted fixes, etc. Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Al Viro (6):
do_mount(): fix a leak introduced in 3.9 ("mount: consolidate permission
checks")
do_coredump(): don't wait for thaw if coredump has already been
On Sat, May 4, 2013 at 6:00 AM, Pavel Machek wrote:
> Hi!
>
>> NFS calls the freezable helpers with locks held, which is unsafe
>> and caused lockdep warnings when 6aa9707 "lockdep: check that no
>> locks held at freeze time" was applied (reverted in dbf520a).
>> Add new *_unsafe versions of the
Ezequiel, All,
On Sat, May 04, 2013 at 02:21:44PM -0300, Ezequiel Garcia wrote:
> I'm trying to split the ac97 support into a separate module.
> So far I've managed to do this with two different approaches,
> but both of them are broken in some way :-(
>
> Couple questions:
>
> 1. Is it
On Thursday, May 02, 2013 05:08:12 PM Tejun Heo wrote:
> On Wed, May 01, 2013 at 06:35:08PM -0700, Colin Cross wrote:
> > Avoid waking up every thread sleeping in read call on an AF_UNIX
> > socket during suspend and resume by calling a freezable blocking
> > call. Previous patches modified the
Hi Suman,
On 4 May 2013 07:50, Suman Anna wrote:
> Hi Jassi,
>
> On 04/27/2013 01:14 PM, jassisinghb...@gmail.com wrote:
>> From: Jassi Brar
>>
>> Introduce common framework for client/protocol drivers and
>> controller drivers of Inter-Processor-Communication (IPC).
>>
>> Client driver
On Sat, May 04, 2013 at 12:11:23AM +0200, Jan Kara wrote:
> When BSD process accounting is enabled and logs information to a
> filesystem which gets frozen, system easily becomes unusable because
> each attempt to account process information blocks. Thus e.g. every task
> gets blocked in exit.
>
On Fri, May 03, 2013 at 10:03:43PM +0200, Geert Uytterhoeven wrote:
> Ping?
>
> Now the build failure is also in Linus' tree:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/8674437/
>
> BTW, this patch depends on "[PATCH 1/2] sun3_scsi: Fill in missing
> scsi_host_template.proc_info
On Sat, May 04, 2013 at 08:02:40PM +0200, Michael Leun wrote:
> On Sat, 4 May 2013 16:52:14 +0100
> Al Viro wrote:
>
> > On Sat, May 04, 2013 at 12:45:19PM +0200, Michael Leun wrote:
> >
> > > After reverting 57eccb830f1cc93d4b506ba306d8dfa685e0c88f from 3.9
> > > that umount above works (not
On Thu, May 02, 2013 at 08:25:39PM +0200, Sebastian Hesselbarth wrote:
> To allow to move to orion irqchip driver, existing legacy devices
> have to map their irqs. This patch adds a node for orion timer and
> some init code to map the corresponding irqs. While the device tree
> node can stay, the
On Thu, May 02, 2013 at 08:25:38PM +0200, Sebastian Hesselbarth wrote:
> To allow to move to orion irqchip driver, existing legacy devices
> have to map their irqs. This patch adds a node for mv643xx_eth and
> some init code to map the corresponding irqs. While the device tree
> node can stay, the
On Fri, May 03, 2013 at 07:06:32AM +0200, Andrew Lunn wrote:
> Jason: what is the status of the ethernet driver conversion to DT?
> Will it get merged this week, or is it material for the next merge
> window?
You'd have to ask Florian/David Miller. I'm not sure wether David was
able to pull that
Add support for chip id detection of AM335x PG2.1 Silicon.
Currently omap3xxx_check_revision() detects PG1.0 and PG2.0 only,
this patch extends it by adding PG2.1 Si support.
Signed-off-by: Vaibhav Hiremath
---
arch/arm/mach-omap2/id.c |8 ++--
arch/arm/mach-omap2/soc.h |1 +
2
On Fri, May 03, 2013 at 12:37:20AM +0200, Sebastian Hesselbarth wrote:
> (@Jason C: Are you sure that I should merge dove and orion
> irqchip patches? I doubt that anything touching generic irq
> will not go through irq tree.)
Putting them in the same patch series does not imply they have to go
On Sat, May 04, 2013 at 11:55:58AM -0400, Jörn Engel wrote:
> Blockconsole currently lives here:
> https://git.kernel.org/cgit/linux/kernel/git/joern/bcon2.git/
Tja, if only that were upstream...
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To
On Sat, 4 May 2013 16:52:14 +0100
Al Viro wrote:
> On Sat, May 04, 2013 at 12:45:19PM +0200, Michael Leun wrote:
>
> > After reverting 57eccb830f1cc93d4b506ba306d8dfa685e0c88f from 3.9
> > that umount above works (not busy).
>
> Sigh... Check if the following fix works for your testcase:
>
On Sat, May 04, 2013 at 10:23:31AM +0300, Julian Anastasov wrote:
>
> Hello,
>
> On Fri, 3 May 2013, Paul E. McKenney wrote:
>
> > static inline int cond_resched_rcu(void)
> > {
> > #if defined(CONFIG_DEBUG_ATOMIC_SLEEP) || !defined(CONFIG_PREEMPT_RCU)
> > rcu_read_unlock();
> >
On Thu, May 02, 2013 at 09:48:50PM +0200, Sebastian Hesselbarth wrote:
> On 05/02/2013 09:35 PM, Jason Gunthorpe wrote:
> >I have kirkwood HW but I haven't had time to make newer kernels run on
> >it, otherwise I'd test it too :(
>
> I also have kirkwood HW but that will cut me from email as I
>From 37830ddd9548d298c0c846cd36181cdb97ceebd7 Mon Sep 17 00:00:00 2001
From: Jake Champlin
Date: Sat, 4 May 2013 12:50:27 -0400
Subject: [PATCH] Staging: Goldfish: goldfish_nand: Fixed all checkpatch errors
Fixed all checkpatch errors included inside goldfish_nand.c.
Checkpatch is now clean for
On Sat, May 4, 2013 at 10:45 AM, Daniel Vetter wrote:
> On Fri, May 03, 2013 at 04:00:30PM -0700, Andy Lutomirski wrote:
>> This replaces drm_mtrr_{add,del} with drm_mtrr_{add,del}_wc. The
>> interface is simplified (because the base and size parameters to
>> drm_mtrr_del never did anything) and
On Fri, May 03, 2013 at 04:00:30PM -0700, Andy Lutomirski wrote:
> This replaces drm_mtrr_{add,del} with drm_mtrr_{add,del}_wc. The
> interface is simplified (because the base and size parameters to
> drm_mtrr_del never did anything) and it uses
> mtrr_{add,del}_wc_if_needed to avoid allocating
On Sat, 23 March 2013 10:19:16 +0700, Emmanuel Benisty wrote:
>
> I could reproduce it but could you please let me know what would be
> the right tools I should use to catch the original oops?
> This is what I got but I doubt it will be helpful:
> http://i.imgur.com/Mewi1hC.jpg
You could use
Hi Mauro,
On Thu, May 02, 2013 at 11:52:33AM -0300, Mauro Carvalho Chehab wrote:
> >
> > is unreliable (doesn't do what some people expect) when SND=m and
> > SND_AC97_CODEC=m,
> > since VIDEO_STK1160_AC97 is a bool.
>
> Using select is always tricky.
>
> I can see a few possible fixes for it:
On Sat, May 04, 2013 at 11:21:17AM -0400, Jake Champlin wrote:
> Fixed 4 cases of line length issues with checkpatch. Checkpatch is now clean
> for panel.c.
OK that's clean, thanks!
> Signed-off-by: 'Jake Champlin '
Acked-by: Willy Tarreau
Willy
--
To unsubscribe from this list: send the
Fixed 4 cases of line length issues with checkpatch. Checkpatch is now clean
for panel.c.
Signed-off-by: 'Jake Champlin '
---
drivers/staging/panel/panel.c | 25 ++---
1 file changed, 14 insertions(+), 11 deletions(-)
diff --git a/drivers/staging/panel/panel.c
Am 03.05.2013 17:24, schrieb Jonathan Austin:
> Hi Russell,
>
> Thanks for the comments - you're right about the 'switch_tls'
> being more appropriate - needed to take a step back to see that.
>
> I've got a few questions, added inline.
>
> André, Assuming I've understood things okay, there's a
On Sat, May 04, 2013 at 12:45:19PM +0200, Michael Leun wrote:
> After reverting 57eccb830f1cc93d4b506ba306d8dfa685e0c88f from 3.9 that
> umount above works (not busy).
Sigh... Check if the following fix works for your testcase:
diff --git a/fs/namespace.c b/fs/namespace.c
index
Change in Liam's email ID.
On 22:02-20130504, Axel Lin wrote:
> abb->current_info_idx is used as array subscript to access volt_table,
> thus the valid value range should be 0 ... desc->n_voltages - 1.
>
> Signed-off-by: Axel Lin
> ---
> drivers/regulator/ti-abb-regula
Make sure devicetable-offsets.h is cleaned in the scripts/mod directory
Signed-off-by: Andreas Schwab
---
scripts/mod/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/scripts/mod/Makefile b/scripts/mod/Makefile
index 9415b56..75d59fc 100644
--- a/scripts/mod/Makefile
+++
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc.git
tags/mmc-updates-for-3.10-rc1
to receive the MMC merge for 3.10. There are currently no conflicts,
and these patches have been tested in linux-next. Thanks.
The following changes since commit
abb->current_info_idx is used as array subscript to access volt_table,
thus the valid value range should be 0 ... desc->n_voltages - 1.
Signed-off-by: Axel Lin
---
drivers/regulator/ti-abb-regulator.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Fri 2013-05-03 14:04:10, Colin Cross wrote:
> From: Mandeep Singh Baines
>
> We shouldn't try_to_freeze if locks are held. Holding a lock can cause a
> deadlock if the lock is later acquired in the suspend or hibernate path
> (e.g. by dpm). Holding a lock can also cause a deadlock in the
Hi!
> NFS calls the freezable helpers with locks held, which is unsafe
> and caused lockdep warnings when 6aa9707 "lockdep: check that no
> locks held at freeze time" was applied (reverted in dbf520a).
> Add new *_unsafe versions of the helpers that will not run the
> lockdep test when 6aa9707 is
Hi!
> dev_pm_put_subsys_data() calls kfree() while holding device power lock, when
> the reference count is 0. Fix it to call kfree() after releasing the lock.
>
> Signed-off-by: Shuah Khan
> ---
> drivers/base/power/common.c |6 +-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
On Fri, May 03, 2013 at 05:21:37PM +0200, Arnd Bergmann wrote:
> On Friday 03 May 2013, Shawn Guo wrote:
> > On Thu, May 02, 2013 at 05:16:08PM +0200, Arnd Bergmann wrote:
> > > The imx DRM driver needs a couple of extra Kconfig dependencies
> > > to avoid random build failures:
> > >
> > >
04.05.2013 15:15, Johan Hovold пишет:
The query takes longer than the transmit at decent baudrates (>=38k)
and under the assumption that flow control isn't causing any delays.
But you do have a point, and I have been meaning to look into whether
the added overhead of checking the hardware
On 05/04/2013 07:15 AM, Johan Hovold wrote:
On Sat, May 04, 2013 at 01:50:42AM +0400, Stas Sergeev wrote:
04.05.2013 00:34, Greg KH пишет:
On Fri, May 03, 2013 at 10:27:18PM +0400, Stas Sergeev wrote:
03.05.2013 21:16, Greg KH пишет:
[...]
There's no guarantee as to how long select or an
On Sat, May 04, 2013 at 01:50:42AM +0400, Stas Sergeev wrote:
> 04.05.2013 00:34, Greg KH пишет:
> > On Fri, May 03, 2013 at 10:27:18PM +0400, Stas Sergeev wrote:
> >> 03.05.2013 21:16, Greg KH пишет:
[...]
> >>> There's no guarantee as to how long select or an ioctl will take, and
> >>> now
From: Rafael J. Wysocki
During ACPI memory hotplug configuration bind memory blocks residing
in modules removable through the standard ACPI mechanism to struct
acpi_device objects associated with ACPI namespace objects
representing those modules. Accordingly, unbind those memory blocks
from the
Hi,
On Saturday, May 04, 2013 03:01:23 AM Rafael J. Wysocki wrote:
> Hi,
>
> This is a continuation of this patchset: https://lkml.org/lkml/2013/5/2/214
> and it applies on top of it or rather on top of the rebased version (with
> build problems fixed) in the bleeding-edge branch of the
From: Rafael J. Wysocki
Introduce .offline() and .online() callbacks for memory_subsys
that will allow the generic device_offline() and device_online()
to be used with device objects representing memory blocks. That,
in turn, allows the ACPI subsystem to use device_offline() to put
removable
On Sat, May 04, 2013 at 01:22:57AM -0700, tip-bot for Peter Zijlstra wrote:
> Commit-ID: 0f5c78b5f33ce940034743e5f9485fc81ad75b0f
> Gitweb: http://git.kernel.org/tip/0f5c78b5f33ce940034743e5f9485fc81ad75b0f
> Author: Peter Zijlstra
> AuthorDate: Fri, 3 May 2013 14:11:25 +0200
>
Add device tree based support for TI's tps6507x touchscreen.
Tested on da850-evm.
Signed-off-by: Vishwanathrao Badarkhe, Manish
---
Changes since V1:
- Updated documetation to specify tps6507x as multifunctional
device.
- return proper error value in absence of
Add tps6507x touchscreen DT node to da850-evm.
Touchscreen DT data is added as per da850 board file.
Tested on da850-evm.
Signed-off-by: Vishwanathrao Badarkhe, Manish
---
Changes since V1:
- Updated commit message.
:100644 100644 c914357... 9c136d1... M
Patch set adds DT support for tps6507x based touchscreen
Also, add DT data for tps6507x touchscreen in da850-evm by
providing touchscreen node inside tps6507x mfd device.
This patch series applies on top of linux-next tree
and depends on [1].
[1]tps6507x-ts: update to devm_* API
Mount some filesystem, below that mountpoint as user mount some fuse fs
(tried that with sshfs and fuseiso, both same error), fusermount -u the
fuse fs, try to unmount the filesystem -> busy.
ml@lara:~> id -u
500
ml@lara:~> grep test /etc/fstab
/dev/vg1/test /mnt2 ext4acl,user_xattr,user,noauto
This driver is a i2c driver, use "i2c" rather than "platform" prefix for module
alias.
Signed-off-by: Axel Lin
---
drivers/power/pm2301_charger.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/power/pm2301_charger.c b/drivers/power/pm2301_charger.c
index
On 05/04/2013 12:11 PM, zhou jencce wrote:
> 2013/5/3 Lars-Peter Clausen :
>> On 05/03/2013 11:56 AM, Xiong Zhou wrote:
>>> From: Xiong Zhou
>>>
>>> This patch fixes build failure(randconfig) of next-20130501.
>>> When config I2C as m, BATTERY_BQ27x00 as y, here comes the failure.
>>>
2013/5/3 Lars-Peter Clausen :
> On 05/03/2013 11:56 AM, Xiong Zhou wrote:
>> From: Xiong Zhou
>>
>> This patch fixes build failure(randconfig) of next-20130501.
>> When config I2C as m, BATTERY_BQ27x00 as y, here comes the failure.
>> BATTERY_BQ27x00 depends on I2C according to the code.
>>
>
>>
On 05/02/2013 09:08 PM, Matt Helsley wrote:
> On Thu, Apr 11, 2013 at 03:29:41PM +0400, Pavel Emelyanov wrote:
>> This file is the same as the pagemap one, but shows entries with bits
>> 55-60 being zero (reserved for future use). Next patch will occupy one
>> of them.
>
> This approach doesn't
Dear Boss:
Nice day!
It is my big pleasure to hear you need chain hoist
we have chain hoist. electric hoist and so on
If you still need it pls inform me
Pls reply me let us contact details
Best wishes
Ida
Sales manager
EAST SIWEITE INDUSTRY CO., LIMITED
www.dfswt.com
Skype: siweite
>> I running a VM(RHEL-5.5) on KVM hypervisor(linux-3.8 + QEMU-1.4.1),
>> and direct-assign intel 82576 VF to the VM. When TX/RX packets on VM to the
>> other host via iperf tool, top tool result on VM shown that the %si is too
>> high, approximately 95% ~ 100%, but from the view of host, the
On 3 May 2013 at 15:03, Jani Nikula wrote:
> >> This fixes a compilation issue with clang. An initial version of this patch
> >> was developed by PaX Team .
> >> This is respin of this patch.
> >>
> >> Signed-off-by: Jan-Simon Möller
> >> CC: pagee...@freemail.hu
> >> CC: daniel.vet...@ffwll.ch
04.05.2013 00:34, Greg KH пишет:
Don't call select for every character :)
OK, let me draw an approximate workflow of the
setup in question.
Lets say we have 3 tty devices, A, B and C.
A and B are blazingly fast, while C is a casual usb-serial
chip.
The app must establish a bidirectional relay
Commit-ID: 0f5c78b5f33ce940034743e5f9485fc81ad75b0f
Gitweb: http://git.kernel.org/tip/0f5c78b5f33ce940034743e5f9485fc81ad75b0f
Author: Peter Zijlstra
AuthorDate: Fri, 3 May 2013 14:11:25 +0200
Committer: Ingo Molnar
CommitDate: Sat, 4 May 2013 08:37:48 +0200
perf/x86/intel/lbr: Demand
Commit-ID: 6e15eb3ba6c0249c9e8c783517d131b47db995ca
Gitweb: http://git.kernel.org/tip/6e15eb3ba6c0249c9e8c783517d131b47db995ca
Author: Peter Zijlstra
AuthorDate: Fri, 3 May 2013 14:11:24 +0200
Committer: Ingo Molnar
CommitDate: Sat, 4 May 2013 08:37:47 +0200
perf/x86/intel/lbr: Fix
Commit-ID: 741a698f420c34c458294a6accecfbad702a7c52
Gitweb: http://git.kernel.org/tip/741a698f420c34c458294a6accecfbad702a7c52
Author: Peter Zijlstra
AuthorDate: Fri, 3 May 2013 14:11:23 +0200
Committer: Ingo Molnar
CommitDate: Sat, 4 May 2013 08:37:46 +0200
perf/x86: Blacklist all
* Peter Zijlstra wrote:
> > I meant to add that I think it would be more productive if we (you and I)
> > were
> > to work on the library to extend it with external text-based event tables
> > that
> > could be used by perf either directly or thru the libpfm4 interface.
>
> That would be
On Sat, May 4, 2013 at 3:18 AM, Josh Boyer wrote:
> On Fri, May 03, 2013 at 10:40:17PM +0200, Daniel Vetter wrote:
>>On Fri, May 3, 2013 at 10:31 PM, Josh Boyer wrote:
>>> OK. Git bisect tells me this:
>>>
>>> 57c219633275c7e7413f8bc7be250dc092887458 is the first bad commit
>>> commit
On Sat, 4 May 2013, Sebastian Hesselbarth wrote:
> On 05/03/2013 11:50 PM, Thomas Gleixner wrote:
> > Provide infrastructure for irq chip implementations which work on
> > linear irq domains.
>
> Thomas,
>
> I am happy that I put you into rant mode. It took me little more
> than an hour to read
On 05/03/2013 11:43 PM, Dirk Brandewie wrote:
> On 05/03/2013 02:26 PM, Toralf Förster wrote:
>> On 05/03/2013 11:10 PM, Dirk Brandewie wrote:
>>>
>>> ignore_nice_load is a feature of the ondemand governor.
>>> The intel_pstate driver is seeing the load presented by the BOINC client
>>> and is
Give the OID registry file module information so that it doesn't taint the
kernel when compiled as a module and loaded.
Reported-by: Dros Adamson
Signed-off-by: David Howells
cc: Trond Myklebust
cc: sta...@vger.kernel.org
cc: linux-...@vger.kernel.org
---
lib/oid_registry.c |5 +
1
Give the OID registry file module information so that it doesn't taint the
kernel when compiled as a module and loaded.
Reported-by: Dros Adamson
Signed-off-by: David Howells
cc: Trond Myklebust
cc: sta...@vger.kernel.org
cc: linux-...@vger.kernel.org
---
lib/oid_registry.c |5 +
1
Il 03/05/2013 06:05, Zhanghaoyu (A) ha scritto:
> I running a VM(RHEL-5.5) on KVM hypervisor(linux-3.8 + QEMU-1.4.1), and
> direct-assign intel 82576 VF to the VM. When TX/RX packets on VM to the other
> host via iperf tool, top tool result on VM shown that the %si is too high,
> approximately
These changes are all for board specific files. These used to make up a
large portion of the ARM changes in the past, but as we are generalizing
the support and moving to device tree probing, this has gotten
significantly smaller. The only platform actually adding new code here
at the moment is
Two platforms, bcm and exynos have their own firmware interfaces using
the "secure monitor call", this adds support for those.
We had originally planned to have a third set of patches in here, which
would extend support for the existing generic "psci" call that is used
on multiple platforms as
This is a rather large set of patches for device drivers that for one
reason or another the subsystem maintainer preferred to get merged
through the arm-soc tree. There are both new drivers as well as
existing drivers that are getting converted from platform-specific
code into standalone drivers
This is yet another driver change, which is split out just because
of its size. As already in 3.9, a lot of changes are going on here,
as the shmobile platform gets converted from its own pin control
API to the generic drivers/pinctrl subsystem.
Based on agreements with Paul Mundt, we are merging
Hi Linus,
Here is the second batch of branches from arm-soc for 3.10, descriptions
in each pull request including conflict resolutions.
As before, a combined resolved branch has been pushed to our repo for
comparison. Branch name this time is 'second-batch-resolved'.
Thanks,
-Olof
--
To
Hello Sander,
Monday, April 29, 2013, 6:05:20 PM, you wrote:
> Monday, April 29, 2013, 5:46:23 PM, you wrote:
>> On Wed, Apr 24, 2013 at 08:16:37PM +0200, Sander Eikelenboom wrote:
>>> Friday, April 19, 2013, 4:44:01 PM, you wrote:
>>>
>>> > Hey Jens,
>>>
>>> > Please in your spare time (if
Hello,
On Fri, 3 May 2013, Paul E. McKenney wrote:
> static inline int cond_resched_rcu(void)
> {
> #if defined(CONFIG_DEBUG_ATOMIC_SLEEP) || !defined(CONFIG_PREEMPT_RCU)
> rcu_read_unlock();
> cond_resched();
> rcu_read_lock();
> #endif
> }
>
> This adds absolutely
Replaced sb_start_write with sb_start_write_killable inside
mnt_want_write and mnt_want_write_file.
Signed-off-by: Marco Stornelli
Reviewed-by: Jan Kara
---
fs/namei.c |6 ++
fs/namespace.c |8 ++--
ipc/mqueue.c |6 +-
3 files changed, 17 insertions(+), 3
Replace sb_start_write with sb_start_write_killable where
possible.
Signed-off-by: Marco Stornelli
Reviewed-by: Jan Kara
---
fs/open.c |8 ++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/fs/open.c b/fs/open.c
index 8c74100..d621d76 100644
--- a/fs/open.c
+++
Replace file_start_write with file_start_write_killable where
possible.
Signed-off-by: Marco Stornelli
Reviewed-by: Jan Kara
---
drivers/block/loop.c |4 +++-
fs/aio.c |7 +--
fs/coda/file.c |4 +++-
fs/read_write.c | 38
Added a new enum to decide if we want to sleep in uninterruptible or
killable state or we want simply to return immediately.
Signed-off-by: Marco Stornelli
Reviewed-by: Jan Kara
---
fs/super.c | 24 ++--
include/linux/fs.h | 19 +--
2 files
* Frederic Weisbecker wrote:
> Ingo,
>
> Please pull the timers/nohz-hz1 branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> timers/nohz-hz1
>
> HEAD: a7f4d69bb1d5e1f573b680355a2ad51566338887
>
> It fixes a Kconfig dependency
On 2 May 2013 20:46, Arnd Bergmann wrote:
> The big.LITTLE cpufreq driver uses the CPU topology API, which
> needs to be reflected in Kconfig to prevent broken configurations.
>
> warning: (ARM_DT_BL_CPUFREQ) selects ARM_BIG_LITTLE_CPUFREQ which
> has unmet direct dependencies (ARCH_HAS_CPUFREQ
2013/5/3 Paul E. McKenney :
> On Fri, May 03, 2013 at 06:47:55PM +0200, Frederic Weisbecker wrote:
>> Commit 0637e029392386e6996f5d6574aadccee8315efa
>> ("nohz: Select wide RCU nocb for full dynticks") intended
>> to force CONFIG_RCU_NOCB_CPU_ALL=y when full dynticks is
>> enabled.
>>
>> However
* Andi Kleen wrote:
> > + } else {
> > + /*
> > +* The LBR logs any address in the IP, even if the IP just
> > +* faulted. This means userspace can control the from address.
> > +* Ensure we don't blindy read any address by validating it is
> > +
On Fri, May 3, 2013 at 12:06 PM, Jingoo Han wrote:
> The driver core clears the driver data to NULL after device_release
> or on probe failure, since commit 0998d0631001288a5974afc0b2a5f568bcdecb4d
> (device-core: Ensure drvdata = NULL when no driver is bound).
> Thus, it is not needed to
On Fri, May 3, 2013 at 12:06 PM, Jingoo Han jg1@samsung.com wrote:
The driver core clears the driver data to NULL after device_release
or on probe failure, since commit 0998d0631001288a5974afc0b2a5f568bcdecb4d
(device-core: Ensure drvdata = NULL when no driver is bound).
Thus, it is not
* Andi Kleen a...@linux.intel.com wrote:
+ } else {
+ /*
+* The LBR logs any address in the IP, even if the IP just
+* faulted. This means userspace can control the from address.
+* Ensure we don't blindy read any address by validating it
1 - 100 of 196 matches
Mail list logo
