On Thu, Jun 25, 2015 at 02:24:58PM +0800, Alison Wang wrote:
> @@ -391,6 +394,85 @@
> reg = <0x0 0x2d24000 0x0 0x4000>;
> };
>
> + enet0: ethernet@2d1 {
Most of the vendor specific properties below are undocumented bindings.
Shawn
> +
Hello Jonathan,
On 15-07-11 18:39:10, Jonathan Cameron wrote:
> On 10/07/15 19:06, maitysancha...@gmail.com wrote:
> > Hello Shawn,
> >
> > On 15-07-10 16:53:24, Shawn Guo wrote:
> >> On Wed, Jun 24, 2015 at 02:03:41PM +0530, Sanchayan Maity wrote:
> >>> Add a device tree property which allows to
Linus,
please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
This updates contains:
- The high latency PIT detection fix, which slipped through the
cracks for rc1
- A regression fix for the early pr
On Sat, Jul 11, 2015 at 10:36:42PM +0800, HungNien Chen wrote:
> The original value is 200ms, it includes the loading fw & boot up to
> the main function. After that, the main function will do algorithm
> initialized and touch calibrtion about 1.1 second. The touch
> calibration will change con
Linus,
please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
This update from the timer departement contains:
- A series of patches which address a shortcoming in the tick
broadcast code. If the
Linus,
please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
A single fix for a cpu hotplug race vs. interrupt descriptors:
Prevent irq setup/teardown across the cpu starting/dying parts of
cpu hotplug s
On Sat, Jul 11, 2015 at 02:17:49PM -0400, Rob Clark wrote:
> On Sat, Jul 11, 2015 at 1:24 PM, Sudip Mukherjee
> wrote:
> > We are checking the size of e->event but we were doing it when e is
> > known to be NULL.
>
> nak, this will leak event_space.. since it is a sizeof, it isn't
> actually der
On Sat, 11 Jul 2015, Frederic Weisbecker wrote:
> It makes the registration cheaper and simpler for the smpboot per-cpu
> kthread users that don't need to always update the cpumask after threads
> creation.
Reviewed-by: Thomas Gleixner
--
To unsubscribe from this list: send the line "unsubscribe
On Sat, 11 Jul 2015, Frederic Weisbecker wrote:
> --- a/kernel/smpboot.c
> +++ b/kernel/smpboot.c
> @@ -113,7 +113,8 @@ static int smpboot_thread_fn(void *data)
> if (kthread_should_stop()) {
> __set_current_state(TASK_RUNNING);
> preempt_en
On Sat, 11 Jul 2015, Frederic Weisbecker wrote:
> The cpumask is allocated before threads get created. If the latter step
> fails, we need to free the cpumask.
Reviewed-by: Thomas Gleixner
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo
From: Vivien Didelot
Date: Fri, 10 Jul 2015 19:48:58 -0400
> There is no need to abort attribute setting or object addition, if the
> prepare phase returned operation not supported.
>
> Thus, abort these two transactions only if the error is not -EOPNOTSUPP.
>
> Signed-off-by: Vivien Didelot
The fw_event_work struct is concurrently referenced at shutdown, so
add a refcount to protect it, and refactor the code to use it.
Additionally, refactor _scsih_fw_event_cleanup_queue() such that it
no longer iterates over the list without holding the lock, since
_firmware_event_work() concurrentl
Hello all,
This patchset attempts to address problems we've been having with
panics due to memory corruption from the mpt2sas driver.
Thanks,
Calvin
Patches in this series:
[PATCH 1/2] mpt2sas: Refcount sas_device objects and fix unsafe list usage
[PATCH 2/2] mpt2sas: Refcount fw_events and fix
These objects can be referenced concurrently throughout the driver, we
need a way to make sure threads can't delete them out from under each
other. This patch adds the refcount, and refactors the code to use it.
Additionally, we cannot iterate over the sas_device_list without
holding the lock, or
On Friday 07/03 at 09:02 -0700, Christoph Hellwig wrote:
> On Mon, Jun 08, 2015 at 08:50:56PM -0700, Calvin Owens wrote:
> > Since the fw_event deletes itself from the list, cleanup_queue() can
> > walk onto garbage pointers or walk off into freed memory.
> >
> > This refactors the code in _scsih_
On Friday 07/03 at 08:38 -0700, Christoph Hellwig wrote:
> >
> > +struct _sas_device *
> > +mpt2sas_scsih_sas_device_get_by_sas_address_nolock(struct MPT2SAS_ADAPTER
> > *ioc,
> > +u64 sas_address)
>
> Any chance to use a shorter name for this function? E.g.
> __mpt2sas_get_sdev_by_addr ?
Thanks, that should have been a "an acronym" instead of "a acronym"
Typo in my commit message. :-(
Diego
On Fri, Jul 10, 2015 at 6:17 PM, Jonathan Corbet wrote:
> On Mon, 6 Jul 2015 14:33:21 -0300
> Diego Viola wrote:
>
>> - "make gconfig" X windows (Gtk) based configuration tool.
>>
Thanks for this, I'm sending a v2 shortly.
On Friday 07/03 at 09:00 -0700, Christoph Hellwig wrote:
> On Mon, Jun 08, 2015 at 08:50:55PM -0700, Calvin Owens wrote:
> > This refactors the fw_event code to use the new refcount.
>
> I spent some time looking over this code because it's so convoluted
On 2015/07/12 10:19, Waiman Long wrote:
> Enabling locking-selftest in a VM guest may cause the following
> kernel panic:
>
> kernel BUG at .../kernel/locking/qspinlock_paravirt.h:137!
>
> This is due to the fact that the pvqspinlock unlock function is
> expecting either a _Q_LOCKED_VAL or _Q_SLO
On 07/11/2015 01:05 AM, Masami Hiramatsu wrote:
On 2015/07/11 10:27, Waiman Long wrote:
On 07/10/2015 08:32 PM, Masami Hiramatsu wrote:
On 2015/07/10 23:28, Peter Zijlstra wrote:
On Fri, Jul 10, 2015 at 03:57:46PM +0200, Ingo Molnar wrote:
* Peter Zijlstra wrote:
Do we want to make double
Hello Christoph,
On (07/11/15 03:02), Christoph Hellwig wrote:
> > Shrinker API does not handle nicely unregister_shrinker() on a
> > not-registered
> > ->shrinker. Looking at shrinker users, they all have to
> > (a) carry on some sort of a flag to make sure that "unregister_shrinker()"
> > will
On Sat, Jul 11, 2015 at 7:33 AM, Stephen Boyd wrote:
> Clock provider drivers generally shouldn't include clk.h because
> it's the consumer API. The clk.h include is being included in all
> mxs files because it's part of mxs/clk.h even though nothing
> actually requires it in that file. Move the c
>From 55fae099d46749b73895934aab8c2823c5a23abe Mon Sep 17 00:00:00 2001
From: Mustapha Abiola
Date: Sat, 11 Jul 2015 17:01:04 +
Subject: [PATCH 1/1] Fix redundant check against unsigned int in broken audit
test fix for exec arg len
Quick patch to fix the needless check of `len` being < 0
From: Vivien Didelot
Date: Sat, 11 Jul 2015 14:36:12 -0400 (EDT)
> In the meantime, this is really useful for development. i.e. ensuring a good
> switchdev/DSA interaction without being able to read and write directly the
> hardware VLAN table, is a bit a PITA. A dynamic debugfs looked appropriat
On 06/29/2015 07:59 PM, Patrick Donnelly wrote:
> task_pgrp requires an rcu or tasklist lock to be obtained if the returned pid
> is to be dereferenced, which kill_pgrp does. Obtain an RCU lock for the
> duration of use.
>
> Signed-off-by: Patrick Donnelly
> ---
> drivers/tty/n_tty.c | 12 +
On 07/12/2015 02:14 AM, Jens Axboe wrote:
> On 07/11/2015 07:30 AM, Bob Liu wrote:
>> Note: This patch is based on original work of Arianna's internship for
>> GNOME's Outreach Program for Women.
>
> Great to see this finally get prepped to go in!
>
>> Only one hardware queue is used now, so the
Haben Sie sich für ein Darlehen oder Hypotheken und ständig abgelehnt suchen
die von Finanzinstituten ist Mr.James Rodriguez ein Gläubiger bietet Darlehen
zu einem Zinssatz von 3% Personen / Unternehmensverbände, Unternehmen,
Betrieben, Schulen, Kirchen, usw., die in der sind Bedarf an Geld in e
One more nitpick (should be the last one):
On Fri, Jul 10, 2015 at 10:25:32AM +0200, Andreas Ruprecht wrote:
> In Kconfig, definitions of options take the following form:
> " ...". COMMANDs and PARAMs are treated
> slightly different by the underlying parser.
>
> While commit 2e0d737fc76f ("kco
Enabling locking-selftest in a VM guest may cause the following
kernel panic:
kernel BUG at .../kernel/locking/qspinlock_paravirt.h:137!
This is due to the fact that the pvqspinlock unlock function is
expecting either a _Q_LOCKED_VAL or _Q_SLOW_VAL in the lock byte. This
patch prevents that bug r
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm libnvdimm-fixes
...to receive:
1/ Fixes for a handful of smatch reports (Thanks Dan C.!) and minor
bug fixes (patches 1-6)
2/ Correctness fixes to the BLK-mode nvdimm driver (patches 7-10).
Granted the
On Sat, Jul 11, 2015 at 4:35 PM, Oleg Nesterov wrote:
>
> Linus, I am mostly trying to convince you. Nobody else objected so far.
> Could you please comment?
I don't mind this part of the series.
It's the whole "do we really want to put the effort into percpu-rwsem
I worry about, as there just a
On 07/10, Andrew Morton wrote:
>
> On Fri, 10 Jul 2015 18:51:21 +0200 Oleg Nesterov wrote:
>
> > special_mapping_fault() is absolutely broken. It seems it was always
> > wrong, but this didn't matter until vdso/vvar started to use more than
> > one page.
> >
> > The patches are the same, just 1/3
Currently down_write/up_write calls synchronize_sched_expedited()
twice which is evil. Change this code to rely on rcu-sync primitives.
This avoids the _expedited "big hammer", and this can be faster in
the contended case or even in the case when a single thread does
down_write/up_write in a loop.
Add the new struct rcu_sync_ops which holds sync/call methods, and
turn the function pointers in rcu_sync_struct into an array of struct
rcu_sync_ops.
This simplifies the "init" helpers, and this way it is simpler to add
the new methods we need, especially ifdef'ed.
Reviewed-by: Paul E. McKenney
Stolen from Peter's patch.
Change percpu_down_read() to use __down_read(), this way we can
do rwsem_acquire_read() unconditionally at the start to make this
code more symmetric and clean.
Signed-off-by: Oleg Nesterov
---
kernel/locking/percpu-rwsem.c | 10 +-
1 files changed, 5 insert
Update the comments broken by the previous change.
Signed-off-by: Oleg Nesterov
---
kernel/locking/percpu-rwsem.c | 50 +
1 files changed, 11 insertions(+), 39 deletions(-)
diff --git a/kernel/locking/percpu-rwsem.c b/kernel/locking/percpu-rwsem.c
index
Add the new rcu_sync_ops->wait() method and the new helper,
rcu_sync_dtor().
It is needed if you are going to, say, kfree(rcu_sync_object).
It simply calls ops->wait() to "flush" the potentially pending
rcu callback.
Reviewed-by: Paul E. McKenney
Signed-off-by: Oleg Nesterov
Signed-off-by: Pete
It would be nice to validate that the caller of rcu_sync_is_idle()
holds the corresponding type of RCU read-side lock. Add the new
rcu_sync_ops->held() method and change rcu_sync_is_idle() to
WARN() if it returns false.
This obviously penalizes the readers (fast-path), but only if
CONFIG_PROVE_RCU
It is functionally equivalent to
struct rcu_sync_struct {
atomic_t counter;
};
static inline bool rcu_sync_is_idle(struct rcu_sync_struct *rss)
{
return atomic_read(&rss->counter) == 0;
}
static inline void rcu_sync_
Hello,
Let me make another attempt to push rcu_sync and add a _simple_
improvment into percpu-rwsem. It already has another user (cgroups)
and I think it can have more. Peter has some use-cases. sb->s_writers
(which afaics is buggy btw) can be turned into percpu-rwsem too I think.
Linus, I am mos
Since dm9000 driver added support for a vcc regulator, platform data
based platforms have their ethernet broken, as the regulator claiming
returns -EPROBE_DEFER and prevents dm9000 loading.
This patch fixes this for all pxa boards using dm9000, by using the
specific regulator_has_full_constraints(
Good Day Sir/Madam.
I am Mr John Matthew, A private Money lender. I am Writing you to
introduce a small and large business money lending service to you. I
can service your financial need with less payback problem that is why
we fund you for just 3%. Need business or a personal loan Fill the
Short
Good Day Sir / Fru.
Jeg er John Matthew, En privat Money långiver. Jeg skriver dig til at
introducere en lille og store virksomheder penge udlån service til
dig. Jeg kan servicere dine finansielle behov med mindre
tilbagebetalingstid problem, der er derfor, vi finansierer dig for kun
3%. Brug forr
Hello.
On 07/11/2015 11:25 PM, David Daney wrote:
From: David Daney
Most broadcast TLB invalidations are unnecessary. So when
invalidating for a given mm/vma target the only the needed CPUs via
The only the needed?
and IPI.
For global TLB invalidations, also use IPI.
Tested on
Commit-ID: 5b29264c659c31bada65582005d99adb3bb41fea
Gitweb: http://git.kernel.org/tip/5b29264c659c31bada65582005d99adb3bb41fea
Author: Jiang Liu
AuthorDate: Thu, 4 Jun 2015 12:13:20 +0800
Committer: Thomas Gleixner
CommitDate: Sat, 11 Jul 2015 23:14:27 +0200
irqchip: Use irq_desc_get_x
Commit-ID: a8a98eac7b238beb49b479c164303651d5a37eb6
Gitweb: http://git.kernel.org/tip/a8a98eac7b238beb49b479c164303651d5a37eb6
Author: Jiang Liu
AuthorDate: Thu, 4 Jun 2015 12:13:30 +0800
Committer: Thomas Gleixner
CommitDate: Sat, 11 Jul 2015 23:14:25 +0200
genirq: Remove the irq argu
Commit-ID: 72f86db4dd5eafbadd45c9092df73c49f320f638
Gitweb: http://git.kernel.org/tip/72f86db4dd5eafbadd45c9092df73c49f320f638
Author: Jiang Liu
AuthorDate: Mon, 1 Jun 2015 16:05:38 +0800
Committer: Thomas Gleixner
CommitDate: Sat, 11 Jul 2015 23:14:27 +0200
irqchip/mips-gic: Use acces
Commit-ID: 0798abeb7eec37dcc20f252c2195fc31c41561f9
Gitweb: http://git.kernel.org/tip/0798abeb7eec37dcc20f252c2195fc31c41561f9
Author: Jiang Liu
AuthorDate: Thu, 4 Jun 2015 12:13:27 +0800
Committer: Thomas Gleixner
CommitDate: Sat, 11 Jul 2015 23:14:24 +0200
genirq: Remove the irq argu
Commit-ID: 0dcdbc97557fd8c297c4e38e9f66e304a64bae9d
Gitweb: http://git.kernel.org/tip/0dcdbc97557fd8c297c4e38e9f66e304a64bae9d
Author: Jiang Liu
AuthorDate: Thu, 4 Jun 2015 12:13:28 +0800
Committer: Thomas Gleixner
CommitDate: Sat, 11 Jul 2015 23:14:25 +0200
genirq: Remove the irq argu
Commit-ID: b51bf95c583bba645974348666e9b5a14c7aa3ea
Gitweb: http://git.kernel.org/tip/b51bf95c583bba645974348666e9b5a14c7aa3ea
Author: Jiang Liu
AuthorDate: Thu, 4 Jun 2015 12:13:25 +0800
Committer: Thomas Gleixner
CommitDate: Sat, 11 Jul 2015 23:14:24 +0200
genirq: Remove the paramete
Commit-ID: d452bca82d9ff4f220afa4234418912623db4fe6
Gitweb: http://git.kernel.org/tip/d452bca82d9ff4f220afa4234418912623db4fe6
Author: Thomas Gleixner
AuthorDate: Mon, 6 Jul 2015 10:18:29 +
Committer: Thomas Gleixner
CommitDate: Sat, 11 Jul 2015 23:14:23 +0200
irqchip/sirfsoc: Fix
Commit-ID: 41a83e06e2bb9ac46731681fd44d1e6ab184dac5
Gitweb: http://git.kernel.org/tip/41a83e06e2bb9ac46731681fd44d1e6ab184dac5
Author: Joel Porquet
AuthorDate: Tue, 7 Jul 2015 17:11:46 -0400
Committer: Thomas Gleixner
CommitDate: Sat, 11 Jul 2015 23:14:23 +0200
irqchip: Prepare for loc
Commit-ID: b66231183a8542de1414e42326dd1c6bc4af75f4
Gitweb: http://git.kernel.org/tip/b66231183a8542de1414e42326dd1c6bc4af75f4
Author: Thomas Gleixner
AuthorDate: Mon, 6 Jul 2015 15:32:25 +0200
Committer: Thomas Gleixner
CommitDate: Sat, 11 Jul 2015 23:14:23 +0200
irqchip/dw-apb-ictl:
The subject should say V4.2-RC. Sorry.
Larry
On 07/11/2015 04:27 PM, Larry Finger wrote:
Beginning with the commit in the subject, I get the following build error:
CC [M] drivers/media/v4l2-core/videobuf2-core.o
drivers/media/v4l2-core/videobuf2-core.c: In function ‘vb2_warn_zero_bytesused
Xen has an kernel command line argument "xen_nopvspin" to disable
paravirtual spinlocks. This patch adds a similar "kvm_nopvspin"
argument to disable paravirtual spinlocks for KVM. This can be useful
for testing as well as allowing administrators to choose unfair lock
for their KVM guests if they w
This patchset consists of two parts:
1) Patches 1-5 enhance the performance of PV qspinlock especially for
overcommitted guest. The first patch moves all the CPU kicking to
the unlock code. The 2nd and 3rd patches implement a kick-ahead
and wait-early mechanism that was shown to impro
Frequent CPU halting (vmexit) and CPU kicking (vmenter) lengthens
critical section and block forward progress. This patch implements
a kick-ahead mechanism where the unlocker will kick the queue head
vCPUs as well as up to two additional vCPUs next to the queue head if
they were halted. The kicki
This patch enables the accumulation of kicking and waiting related
PV qspinlock statistics when the new QUEUED_LOCK_STAT configuration
option is selected. It also enables the collection of kicking and
wakeup latencies which have a heavy dependency on the CPUs being used.
The measured latencies for
This patch enables the accumulation of unfair qspinlock statistics
when the CONFIG_QUEUED_LOCK_STAT configuration parameter is set.
The accumulated lock statistics will be reported in debugfs under
the unfair-qspinlock directory.
On a KVM guest with 32 vCPUs, the statistics counts after bootup we
For a virtual guest with the qspinlock patch, a simple unfair byte lock
will be used if PV spinlock is not configured in or the hypervisor
isn't either KVM or Xen. The byte lock works fine with small guest
of just a few vCPUs. On a much larger guest, however, byte lock can
have the following proble
In an overcommitted guest where some vCPUs have to be halted to make
forward progress in other areas, it is highly likely that a vCPU
later in the spinlock queue will be spinning while the ones earlier in
the queue would have been halted already. The spinning in the later
vCPUs is then just a waste
Like the native qspinlock, using the pending bit when it is lightly
loaded to acquire the lock is faster than going through the PV queuing
process which is even slower than the native queuing process. It also
avoids loading two additional cachelines (the MCS and PV nodes).
This patch adds the pend
For an over-committed guest with more vCPUs than physical CPUs
available, it is possible that a vCPU may be kicked twice before
getting the lock - one before it becomes queue head and once before
it gets the lock. All these CPU kicking and halting (VMEXIT) can be
expensive and slow down system perf
On Wed, 8 Jul 2015, Alban Bedel wrote:
> We shouldn't include irqchip.h from outside of the drivers/irqchip
> directory. The irq driver should idealy be there, however this not
> trivial at the moment. We still need to support platforms without DT
> support and the interface to the DDR controller s
From: David Daney
When CONFIG_SMP, we end up calling flush_context() on each CPU
(indirectly) from __new_context(). Because of this, doing a broadcast
TLB invalidate is overkill, as all CPUs will be doing a local
invalidation.
Change the scope of the TLB invalidation operation to be local,
resu
From: David Daney
This patch set (or something like it) is needed for the Cavium
ThunderX, but its performance improvements may make it compelling on
its own merits.
Summery: On ThunerX we cannot use broadcast TLB invalidation, so we
use IPIs where necessary. The funny thing is that it also hap
From: David Daney
To be used in follow-on patch.
Signed-off-by: David Daney
---
arch/arm64/include/asm/tlbflush.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/include/asm/tlbflush.h
b/arch/arm64/include/asm/tlbflush.h
index 934815d..42c09ec 100644
--- a/arch/arm64/inc
From: David Daney
Most broadcast TLB invalidations are unnecessary. So when
invalidating for a given mm/vma target the only the needed CPUs via
and IPI.
For global TLB invalidations, also use IPI.
Tested on Cavium ThunderX.
This change reduces 'time make -j48' on kernel from 139s to 116s (83%
On Fri, Jul 10, 2015 at 10:15 PM, andrew banman wrote:
> I'm seeing a large number of allocation errors originating from the Mellanox
> IB
> driver when booting the 4.2-rc1 kernel on a 4096cpu 32TB memory system:
Just to make sure, mlx4 works fine on this small (...) system with 4.1
and 4.2-rc1
On Fri, 10 Jul 2015, Stephen Smalley wrote:
> commit 66fc13039422ba7df2d01a8ee0873e4ef965b50b ("mm: shmem_zero_setup skip
> security check and lockdep conflict with XFS") caused a regression for
> SELinux by disabling any SELinux checking of mprotect PROT_EXEC on
> shared anonymous mappings. Howe
Hi,
On Sat, Jul 11, 2015 at 05:17:32PM +, Subbaraya Sundeep Bhatta wrote:
> > > >> Hi Felipe,
> > > >>
> > > >> Just an update on this.
> > > >>
> > > >> I'm trying to get this working with our latest IP with dwc3 from
> > > >> your testing/next branch. It fails the usbtest with a problem
> >
Hi Jonathan,
Am Samstag, 11. Juli 2015, 18:32:42 schrieb Jonathan Cameron:
> On 08/07/15 15:17, Heiko Stuebner wrote:
> > The module-data is currently missing. This includes the
> > license-information
> > which makes the driver taint the kernel and miss symbols when compiled as
> > module.
> >
>
0001-Fix-redundant-check-against-unsigned-int-in-broken-a.patch
Description: Binary data
Hi David,
On Jul 11, 2015, at 2:01 AM, David da...@davemloft.net wrote:
> From: Vivien Didelot
> Date: Thu, 9 Jul 2015 17:13:29 -0400
>
>> Allow write access to the regs file in the debugfs interface, with the
>> following parameters:
>>
>> echo> regs
>>
>> Where "name" is the regist
On 7/11/2015 11:26 AM, Porteus Kiosk wrote:
Hello Arjan,
We need it for setting up the time in the hardware clock through the 'hwclock'
command.
Thank you.
hmm thinking about it after coffee... there is an RTC that can be exposed to
userspace.
hrmpf. Wonder why its not there for you
--
On 7/11/2015 11:21 AM, Arjan van de Ven wrote:
On 7/11/2015 10:59 AM, Larry Finger wrote:
On a Winbook TW100 BayTrail tablet, kernel 4.0 and later do not create
/dev/rtc0 when CONFIG_PINCTRL_BAYTRAIL is set in the configuration. Removing
this option from the
config creates a real-time clock; h
On 7/11/2015 10:59 AM, Larry Finger wrote:
On a Winbook TW100 BayTrail tablet, kernel 4.0 and later do not create
/dev/rtc0 when CONFIG_PINCTRL_BAYTRAIL is set in the configuration. Removing
this option from the
config creates a real-time clock; however, it is no longer possible to get the
tab
On Sat, Jul 11, 2015 at 1:24 PM, Sudip Mukherjee
wrote:
> We are checking the size of e->event but we were doing it when e is
> known to be NULL.
nak, this will leak event_space.. since it is a sizeof, it isn't
actually deref'ing e, but rather just using the static type info, so
it's ok (althoug
On 07/11/2015 07:30 AM, Bob Liu wrote:
Note: This patch is based on original work of Arianna's internship for
GNOME's Outreach Program for Women.
Great to see this finally get prepped to go in!
Only one hardware queue is used now, so there is no performance change.
I would hope that the blk
When blkcg_init_queue() fails midway after creating a new blkg, it
performs kfree() directly; however, this doesn't free the policy data
areas. Make it use blkg_free() instead. In turn, blkg_free() is
updated to handle root request_list special case.
While this fixes a possible memory leak, it's
This is v3 of blkcg_policy methods cleanup patchset. Changes from the
last take [L] are
* Rebased on top of block/for-linus.
* 0003-blkcg-remove-unnecessary-blkcg_root-handling-from-cs.patch and
0004-blkcg-restructure-blkg_policy_data-allocation-in-blk.patch
added. These are follow-up clean
When a policy gets activated, it needs to allocate and install its
policy data on all existing blkg's (blkcg_gq's). Because blkg
iteration is protected by a spinlock, it currently counts the total
number of blkg's in the system, allocates the matching number of
policy data on a list and installs t
Because percpu allocator couldn't do non-blocking allocations,
blk-throttle was forced to implement an ad-hoc asynchronous allocation
mechanism for its percpu stats for cases where blkg's (blkcg_gq's) are
allocated from an IO path without sleepable context.
Now that percpu allocator can handle gfp
A blkg (blkcg_gq) represents the relationship between a cgroup and
request_queue. Each active policy has a pd (blkg_policy_data) on each
blkg. The pd's were allocated by blkcg core and each policy could
request to allocate extra space at the end by setting
blkcg_policy->pd_size larger than the si
blkg_create() allows NULL ->pd_init_fn() but blkcg_activate_policy()
doesn't. As both in-kernel policies implement ->pd_init_fn, it
currently doesn't break anything. Update blkcg_activate_policy() so
that its behavior is consistent with blkg_create().
Signed-off-by: Tejun Heo
Cc: Vivek Goyal
-
The newly added ->pd_alloc_fn() and ->pd_free_fn() deal with pd
(blkg_policy_data) while the older ones use blkg (blkcg_gq). As using
blkg doesn't make sense for ->pd_alloc_fn() and after allocation pd
can always be mapped to blkg and given that these are policy-specific
methods, it makes sense to
With the recent addition of alloc and free methods, things became
messier. This patch reorganizes them according to the followings.
* ->pd_alloc_fn()
Responsible for allocation and static initializations - the ones
which can be done independent of where the pd might be attached.
* ->pd_init
Each active policy has a cpd (blkcg_policy_data) on each blkcg. The
cpd's were allocated by blkcg core and each policy could request to
allocate extra space at the end by setting blkcg_policy->cpd_size
larger than the size of cpd.
This is a bit unusual but blkg (blkcg_gq) policy data used to be
h
blkcg_css_alloc() bypasses policy data allocation and blkcg_css_free()
bypasses policy data and blkcg freeing for blkcg_root. There's no
reason to to treat policy data any differently for blkcg_root. If the
root css gets allocated after policies are registered, policy
registration path will add p
* Rename blkcg->pd[] to blkcg->cpd[] so that cpd is consistently used
for blkcg_policy_data.
* Make blkcg_policy->cpd_init_fn() take blkcg_policy_data instead of
blkcg. This makes it consistent with blkg_policy_data methods and
to-be-added cpd alloc/free methods.
* blkcg_policy_data->blkcg
Since ec13b1d6f0a0 ("blkcg: always create the blkcg_gq for the root
blkcg"), a request_list always has its blkg associated. Drop
unnecessary rl->blkg NULL test from blk_put_rl().
Signed-off-by: Tejun Heo
Cc: Vivek Goyal
---
include/linux/blk-cgroup.h | 3 +--
1 file changed, 1 insertion(+), 2
On 10/07/15 06:54, Krzysztof Kozlowski wrote:
> i2c_driver does not need to set an owner because i2c_register_driver()
> will set it.
>
> Signed-off-by: Krzysztof Kozlowski
>
Applied to the togreg branch of iio.git
Thanks,
Jonathan
> ---
>
> The coccinelle script which generated the patch was
On 10/07/15 07:34, Krzysztof Kozlowski wrote:
> i2c_driver does not need to set an owner because i2c_register_driver()
> will set it.
>
> Signed-off-by: Krzysztof Kozlowski
Applied to the togreg branch of iio.git
Thanks,
Jonathan
>
> ---
>
> The coccinelle script which generated the patch was
On 10/07/15 15:10, Cristina Opriceana wrote:
> Multiple blank lines should not be used as indicated by checkpatch.pl.
> Also, a line should be used after a function/structure declaration.
>
> Signed-off-by: Cristina Opriceana
Applied to the togreg branch of iio.git
Thanks,
Jonathan
> ---
> dri
On 10/07/15 18:14, Tirdea, Irina wrote:
>
>
>> -Original Message-
>> From: Jonathan Cameron [mailto:ji...@kernel.org]
>> Sent: 05 July, 2015 14:59
>> To: Tirdea, Irina; Wolfram Sang; linux-...@vger.kernel.org;
>> linux-...@vger.kernel.org
>> Cc: linux-kernel@vger.kernel.org; Pandruvada,
On 10/07/15 19:06, maitysancha...@gmail.com wrote:
> Hello Shawn,
>
> On 15-07-10 16:53:24, Shawn Guo wrote:
>> On Wed, Jun 24, 2015 at 02:03:41PM +0530, Sanchayan Maity wrote:
>>> Add a device tree property which allows to specify the minimum sample
>>> time which can be used to calculate the act
On 08/07/15 15:17, Heiko Stuebner wrote:
> The module-data is currently missing. This includes the license-information
> which makes the driver taint the kernel and miss symbols when compiled as
> module.
>
> Fixes: 44d6f2ef94f9 ("iio: adc: add driver for Rockchip saradc")
> Signed-off-by: Heiko S
On 08/07/15 15:04, Ana Calinov wrote:
> This patch removes an unnecessary blank line
> found by checkpatch.pl --strict:
> Blank lines aren't necessary after an open brace '{'.
>
> Signed-off-by: Ana Calinov
Applied to the togreg branch of iio.git. Initially pushed
out as testing for the autobuild
On 08/07/15 13:56, Daniel Baluta wrote:
> On Wed, Jul 8, 2015 at 3:44 PM, Ana Calinov wrote:
>> This patch fixes the the following errors given by
>> checkpatch.pl with --strict:
>> Please don't use multiple blank lines.
>> Blank lines aren't necessary after an open brace '{'.
>>
>> Signed-off-by:
The following
if (val < 0)
*lvalp = (unsigned long)-val;
is incorrect because the compiler is free to assume -val to be positive
and use a sign-extend instruction for extending the bit pattern. This
is a problem if val == INT_MIN:
# echo -2147483648 >/proc/sys/dev/scsi/logging_l
1 - 100 of 207 matches
Mail list logo
