On Wed, Mar 20, 2013 at 12:55 PM, Rik van Riel wrote:
>
> This series makes the sysv semaphore code more scalable,
> by reducing the time the semaphore lock is held, and making
> the locking more scalable for semaphore arrays with multiple
> semaphores.
The series looks sane to me, and I like
On 03/20/2013 07:44 AM, Laxman Dewangan wrote:
> NVIDIA's Tegra114 platform, Dalmore, uses the TPS65090 as
> secondary PMICs which mainly act as voltage switch controlled
> by I2C communication.
> diff --git a/arch/arm/boot/dts/tegra114-dalmore.dts
> b/arch/arm/boot/dts/tegra114-dalmore.dts
>
Vivek Goyal writes:
> On Tue, Mar 19, 2013 at 03:12:10PM -0700, Eric W. Biederman wrote:
>> HATAYAMA Daisuke writes:
>>
>> > To satisfy mmap()'s page-size boundary requirement, allocate per-cpu
>> > crash_notes objects on page-size boundary.
>> >
>> > /proc/vmcore on the 2nd kernel checks if
On Tue, 2013-03-19 at 18:08 +1100, Alexey Kardashevskiy wrote:
> VFIO implements platform independent stuff such as
> a PCI driver, BAR access (via read/write on a file descriptor
> or direct mapping when possible) and IRQ signaling.
>
> The platform dependent part includes IOMMU initialization
>
Am 20.03.2013 20:02, schrieb Sebastian Gottschall (DD-WRT):
Hello
The patch for sa_restorer will break mips builds, since sa_restorer
isnt defined as field within the struct, but the MACRO is.
so use the __ARCH_HAS_SA_RESTORER way which is implemented in that way
in linux 3.9 or simply revert
Hello folks,
I was looking at why I can't load the Intel RNG driver (or why it doesn't load
automatically) and
it just so happens I have both the mobile and non-mobile ICH9 chipset. Looking
at the driver I noticed:
/* BAM, CAM, DBM, FBM, GxM
{ PCI_DEVICE(0x8086, 0x2448) }, */
/*
On Wed, 20 Mar 2013, Greg Kroah-Hartman wrote:
> > > Ok, I'll postpone this patch for the next stable release, in time for
> > > the fix to be put in at the same time.
> >
> > I think patch 13/75 ("USB: EHCI: dont check DMA values in QH overlays")
> > should also be postponed then, at least Alan
On Wed, 2013-03-20 at 15:16 -0400, Mimi Zohar wrote:
> On Wed, 2013-03-20 at 18:12 +, Matthew Garrett wrote:
> > Well, in the absence of hardcoded in-kernel policy, there needs to be
> > some mechanism for ensuring the integrity of a policy. Shipping a signed
> > policy initramfs fragment and
Benoit Lourdelet writes:
> Hello,
>
> The measurement has been done with kernel 3.8.2.
>
> Linux ieng-serv06 3.7.9 #3 SMP Wed Feb 27 02:38:58 PST 2013 x86_64 x86_64
> x86_64 GNU/Linux
Two different kernel versions?
> What information would you like to see on the kernel ?
The question is where
On Wed, Mar 20, 2013 at 09:14:38PM +0100, Sven Joachim wrote:
> On 2013-03-20 21:08 +0100, Greg Kroah-Hartman wrote:
>
> > On Tue, Mar 19, 2013 at 10:44:30PM +0100, Sven Joachim wrote:
> >> On 2013-03-19 22:00 +0100, Alan Stern wrote:
> >>
> >> > On Tue, 19 Mar 2013, Sven Joachim wrote:
> >> >
>
Hello,
The measurement has been done with kernel 3.8.2.
Linux ieng-serv06 3.7.9 #3 SMP Wed Feb 27 02:38:58 PST 2013 x86_64 x86_64
x86_64 GNU/Linux
What information would you like to see on the kernel ?
Regards
Benoit
On 20/03/2013 01:29, "Eric W. Biederman" wrote:
>Serge Hallyn writes:
>
On Sun, Mar 17, 2013 at 03:08:11PM -0700, Christopher Li wrote:
> On Sun, Mar 17, 2013 at 2:58 PM, Sam Ravnborg wrote:
> >
> > We got no patch - just some git help stuff.
> > Seems you mistyped somthing..
> >
>
> Oops, sorry about that. I reattach the patch here.
I looked at the attached patch:
On Tue, Mar 19, 2013 at 05:07:21PM +0900, Joonsoo Kim wrote:
> On Tue, Mar 19, 2013 at 12:35:45AM -0700, Yinghai Lu wrote:
> > Can you check why sparc do not need to change interface during converting
> > to use memblock to replace bootmem?
>
> Sure.
> According to my understanding to sparc32
From: Davidlohr Bueso
Various forms of ipc use the ipcctl_pre_down() function to
retrieve an ipc object and check permissions, mostly for IPC_RMID
and IPC_SET commands.
Introduce ipcctl_pre_down_nolock(), a lockless version of this function.
The locking version is maintained, yet modified to
Rename sem_lock to sem_obtain_lock, so we can introduce a sem_lock
function later that only locks the sem_array and does nothing else.
Open code the locking from ipc_lock in sem_obtain_lock, so we can
introduce finer grained locking for the sem_array in the next patch.
Signed-off-by: Rik van
From: Davidlohr Bueso
Through ipc_lock() and therefore ipc_lock_check() we currently
return the locked ipc object. This is not necessary for all situations
an can, therefore, incur in unnecessary ipc lock contention.
Introduce, analogous, ipc_obtain_object() and ipc_obtain_object_check()
From: Davidlohr Bueso
There is no reason to be holding the ipc lock while
reading ipcp->seq, hence remove misleading comment.
Also simplify the return value for the function.
Signed-off-by: Rik van Riel
Signed-off-by: Davidlohr Bueso
---
ipc/util.h |7 +--
1 files changed, 1
Having only one list in struct sem_queue, and only queueing simple
semaphore operations on the list for the semaphore involved, allows
us to introduce finer grained locking for semtimedop.
Signed-off-by: Rik van Riel
---
ipc/sem.c | 65
Include lkml in the CC: this time... *sigh*
---8<---
This series makes the sysv semaphore code more scalable,
by reducing the time the semaphore lock is held, and making
the locking more scalable for semaphore arrays with multiple
semaphores.
The first four patches were written by Davidlohr
From: Davidlohr Bueso
I have corrected the two locking bugs in this patch, but
left it otherwise untouched - Rik.
---8<---
Instead of holding the ipc lock for permissions and security
checks, among others, only acquire it when necessary.
Some numbers
1) With Rik's semop-multi.c
Introduce finer grained locking for semtimedop, to handle the
common case of a program wanting to manipulate one semaphore
from an array with multiple semaphores.
If the call is a semop manipulating just one semaphore in
an array with multiple semaphores, only take the lock for
that semaphore
On 2013-03-20 21:08 +0100, Greg Kroah-Hartman wrote:
> On Tue, Mar 19, 2013 at 10:44:30PM +0100, Sven Joachim wrote:
>> On 2013-03-19 22:00 +0100, Alan Stern wrote:
>>
>> > On Tue, 19 Mar 2013, Sven Joachim wrote:
>> >
>> >> On 2013-03-19 21:10 +0100, Alan Stern wrote:
>> >>
>> >> > On Tue, 19
I'm announcing the release of the 3.8.4 kernel.
All users of the 3.8 kernel series must upgrade.
The updated 3.8.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.8.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 2659987..a9e4d61 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 4
-SUBLEVEL = 36
+SUBLEVEL = 37
EXTRAVERSION =
NAME = Saber-toothed Squirrel
diff --git a/arch/powerpc/kernel/cputable.c b/arch/powerpc/kernel/cputable.c
I'm announcing the release of the 3.4.37 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 534f7de..6754172 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 0
-SUBLEVEL = 69
+SUBLEVEL = 70
EXTRAVERSION =
NAME = Sneaky Weasel
diff --git a/arch/powerpc/kernel/cputable.c b/arch/powerpc/kernel/cputable.c
index
I'm announcing the release of the 3.0.70 kernel.
All users of the 3.0 kernel series must upgrade.
The updated 3.0.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.0.y
and can be browsed at the normal kernel.org git web browser:
On Tue, Mar 19, 2013 at 10:44:30PM +0100, Sven Joachim wrote:
> On 2013-03-19 22:00 +0100, Alan Stern wrote:
>
> > On Tue, 19 Mar 2013, Sven Joachim wrote:
> >
> >> On 2013-03-19 21:10 +0100, Alan Stern wrote:
> >>
> >> > On Tue, 19 Mar 2013, Sven Joachim wrote:
> >> >
> >> >> > In what way is
Hello,
What is the status of the below patch? Both Marvell PCIe driver and
Tegra PCIe driver need a way to parse the ranges = <...> property of
the PCI DT node.
Would it be possible to get this patch merged for 3.10, or get some
review comments that would allow us to rework it in time for 3.10 ?
I'm announcing the release of the 3.2.41 kernel.
All users of the 3.2 kernel series should upgrade.
The updated 3.2.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.2.y
and can be browsed at the normal kernel.org git web browser:
On Wed 20-03-13 12:07:29, David Rientjes wrote:
> mm, hugetlb: include hugepages in meminfo
>
> Particularly in oom conditions, it's troublesome that hugetlb memory is
> not displayed. All other meminfo that is emitted will not add up to what
> is expected, and there is no artifact left in the
On Wed 20-03-13 02:33:08, Al Viro wrote:
> On Tue, Mar 19, 2013 at 10:10:32PM +, Al Viro wrote:
>
> > OK, it's going to be an interesting series - aforementioned tentative patch
> > was badly incomplete ;-/
>
> The interesting question is how far do we want to lift that. ->aio_write()
>
Sorry for being so very late to the party, but rather than messing
with xattrs, why not just have a specific file (say, default /.whiteout,
but selectable via a mount option) and links to it are counted as
whiteout entries?
All you need to do is resolve the link (it's probably a good idea
to
Hi all
On Sat, 2 Mar 2013, Mark Brown wrote:
> On Mon, Feb 18, 2013 at 10:57:44AM +0100, Guennadi Liakhovetski wrote:
> > Add device-tree bindings to the AS3711 regulator and backlight drivers.
>
> Reviwed-by: Mark Brown
This patch has been submitted more than a month ago and only has got one
audit rule additions containing "-F auid!=4294967295" were failing with EINVAL.
UID_INVALID (and GID_INVALID) is actually a valid uid (gid) for setting and
testing against audit rules. Remove the check for invalid uid and gid when
parsing rules and data for logging.
Revert part of
On Wed, Mar 20, 2013 at 08:23:39PM +0100, Takashi Iwai wrote:
> At Wed, 20 Mar 2013 19:12:50 +,
> Matthew Garrett wrote:
> > On Wed, Mar 20, 2013 at 08:11:15PM +0100, Takashi Iwai wrote:
> > > I'm afraid that it's too radical to enable always.
> >
> > Why?
>
> Because I'm conservative :)
>
On 20.03.2013 21:49, Peter Hurley wrote:
> The motivation for changing the workqueue api to allow parallel work
> items on SMP was to fix a class of deadlocks where forward progress
> could not be made due to subtle dependencies between work items
> (actually that potential still exists with
At Wed, 20 Mar 2013 19:12:50 +,
Matthew Garrett wrote:
>
> On Wed, Mar 20, 2013 at 08:11:15PM +0100, Takashi Iwai wrote:
> > At Wed, 20 Mar 2013 17:52:34 +,
> > Matthew Garrett wrote:
> > > Well that just sounds like a bug. What's the downside to just ignoring
> > > that capability bit?
We can extend kexec-tools to support multiple "Crash kernel" in /proc/iomem
instead.
So we can use "Crash kernel" instead of "Crash kernel low" in /proc/iomem.
Suggested-by: Vivek Goyal
Signed-off-by: Yinghai Lu
---
kernel/kexec.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Wed, Mar 20, 2013 at 06:28:21PM +, Jonathan Cameron wrote:
> On 03/20/2013 03:52 PM, Guenter Roeck wrote:
> > So far, all instances of iio_hwmon set their hwmon name attribute
> > to "iio_hwmon", which is not very descriptive. Set it to the device tree
> > node name if available, and only
On Wed 20-03-13 11:58:20, David Rientjes wrote:
> On Wed, 20 Mar 2013, Michal Hocko wrote:
>
> > > I didn't do this because it isn't already exported in /proc/meminfo and
> > > since we've made an effort to reduce the amount of information emitted by
> > > the oom killer at oom kill time to
From: "John W. Linville"
Date: Wed, 20 Mar 2013 15:11:08 -0400
> I present to you another batch of fixes intended for the 3.9 stream...
>
> On the bluetooth bits, Gustavo says:
>
> "I put together 3 fixes intended for 3.9, there are support for two
> new devices and a NULL dereference fix in
At Wed, 20 Mar 2013 19:41:38 +0100,
Martin Mokrejs wrote:
>
> Hi Takashi,
> would you please describe your test system in more detail? How
> about 'lspci -tv'? And 'lsusb -v' of the broken device?
I left the machine in my office, so I'll give details tomorrow.
It's a Realtek 5249 PCI-e card
On Wed, 2013-03-20 at 18:12 +, Matthew Garrett wrote:
> On Wed, 2013-03-20 at 14:01 -0400, Mimi Zohar wrote:
>
> > Sorry, I'm not sure to which work you're referring. If you're referring
> > to Dmitry's "initramfs with digital signature protection" patches, then
> > we're speaking about
On Mon, 2013-03-18 at 17:34 +0100, Oleg Nesterov wrote:
> syscall_regfunc() and syscall_unregfunc() should set/clear
> TIF_SYSCALL_TRACEPOINT system-wide, but do_each_thread() can race
> with copy_process() and miss the new child which was not added to
> init_task.tasks list yet.
>
> Change
Dave,
I present to you another batch of fixes intended for the 3.9 stream...
On the bluetooth bits, Gustavo says:
"I put together 3 fixes intended for 3.9, there are support for two
new devices and a NULL dereference fix in the SCO code."
Amitkumar Karwar fixes a command queueing race in
On Wed, Mar 20, 2013 at 08:11:15PM +0100, Takashi Iwai wrote:
> At Wed, 20 Mar 2013 17:52:34 +,
> Matthew Garrett wrote:
> > Well that just sounds like a bug. What's the downside to just ignoring
> > that capability bit?
>
> I'm afraid that it's too radical to enable always.
Why?
> Or,
At Wed, 20 Mar 2013 17:52:34 +,
Matthew Garrett wrote:
>
> On Wed, Mar 20, 2013 at 03:02:01PM +0100, Takashi Iwai wrote:
> > We encountered a problem that on some HP machines the Realtek PCI-e
> > card reader device appears only when you inserted a card before the
> > cold boot. While
At Wed, 20 Mar 2013 12:09:13 -0600,
Alex Williamson wrote:
>
> On Wed, 2013-03-20 at 15:02 +0100, Takashi Iwai wrote:
> > We encountered a problem that on some HP machines the Realtek PCI-e
> > card reader device appears only when you inserted a card before the
> > cold boot. While debugging, it
mm, hugetlb: include hugepages in meminfo
Particularly in oom conditions, it's troublesome that hugetlb memory is
not displayed. All other meminfo that is emitted will not add up to what
is expected, and there is no artifact left in the kernel log to show that
a potentially significant amount
From: Jiri Slaby
Date: Thu, 14 Mar 2013 00:30:34 +0100
> The following commits:
> * 6732c8bb8671acbdac6cdc93dd72ddd581dd5e25 (TTY: switch
> tty_schedule_flip)
> * 2e124b4a390ca85325fae75764bef92f0547fa25 (TTY: switch
> tty_flip_buffer_push)
> * 05c7cd39907184328f48d3e7899f9cdd653ad336 (TTY:
On Wed, 20 Mar 2013, Michal Hocko wrote:
> > I didn't do this because it isn't already exported in /proc/meminfo and
> > since we've made an effort to reduce the amount of information emitted by
> > the oom killer at oom kill time to avoid spamming the kernel log, I only
> > print the default
On 03/20/13 11:56, David Rientjes wrote:
> On Wed, 20 Mar 2013, Randy Dunlap wrote:
>
>> on x86_64:
>>
>> fs/proc/vmcore.c: In function 'merge_note_headers_elf64':
>> fs/proc/vmcore.c:349:22: error: 'VMCOREINFO_NOTE_NAME' undeclared (first use
>> in this function)
>> fs/proc/vmcore.c:349:22:
On Tue, Mar 19, 2013 at 05:00:19PM -0700, Tejun Heo wrote:
> and also available in the following git branch.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git review-numa
Branch rebased on top of the current wq/for-3.10 with updated patches.
The new comit ID is
On Wed 20-03-13 11:46:12, David Rientjes wrote:
> On Wed, 20 Mar 2013, Michal Hocko wrote:
>
> > On Tue 19-03-13 17:18:12, David Rientjes wrote:
> > > Particularly in oom conditions, it's troublesome that hugetlb memory is
> > > not displayed. All other meminfo that is emitted will not add up
Martin Mokrejs wrote:
> Hi Takashi,
> would you please describe your test system in more detail? How
> about 'lspci -tv'? And 'lsusb -v' of the broken device?
>
> 1. For me on Dell Vostro 3550 with a SandyBridge chip doing all
> SATA+USB2+ExpressCardSlot:
>
> 00:00.0 Host bridge: Intel
On Wed, 20 Mar 2013, Randy Dunlap wrote:
> on x86_64:
>
> fs/proc/vmcore.c: In function 'merge_note_headers_elf64':
> fs/proc/vmcore.c:349:22: error: 'VMCOREINFO_NOTE_NAME' undeclared (first use
> in this function)
> fs/proc/vmcore.c:349:22: note: each undeclared identifier is reported only
>
Currently, an unbound workqueue has single current, or first, pwq
(pool_workqueue) to which all new work items are queued. This often
isn't optimal on NUMA machines as workers may jump around across node
boundaries and work items get assigned to workers without any regard
to NUMA affinity.
This
On 03/20/2013 11:36 AM, Stephen Warren wrote:
> On 03/20/2013 06:12 AM, Venu Byravarasu wrote:
>> Venu Byravarasu wrote at Wednesday, March 20, 2013 11:30 AM:
>>> Stephen Warren wrote at Wednesday, March 20, 2013 1:22 AM:
On 03/18/2013 06:29 AM, Venu Byravarasu wrote:
> As part of this
On Wed, Mar 20, 2013 at 09:32:51AM -0700, Sören Brinkmann wrote:
> Hi Mike,
>
> On Tue, Mar 19, 2013 at 05:16:09PM -0700, Mike Turquette wrote:
> > Quoting Soren Brinkmann (2013-01-29 17:25:44)
> > > Use the DIV_ROUND_CLOSEST macro to calculate divider values and minimize
> > > rounding errors.
>
On Wed, 20 Mar 2013, Michal Hocko wrote:
> On Tue 19-03-13 17:18:12, David Rientjes wrote:
> > Particularly in oom conditions, it's troublesome that hugetlb memory is
> > not displayed. All other meminfo that is emitted will not add up to what
> > is expected, and there is no artifact left in
On Wed 20-03-13 18:19:57, Mel Gorman wrote:
> The following problem was reported against a distribution kernel when
> zone_reclaim was enabled but the same problem applies to the mainline
> kernel. The reproduction case was as follows
>
> 1. Run numactl -m +0 dd if=largefile of=/dev/null
>
On Mon, Mar 18, 2013 at 08:42:09PM +0800, Xiao Guangrong wrote:
> On 03/18/2013 07:19 PM, Paolo Bonzini wrote:
> > Il 15/03/2013 16:29, Xiao Guangrong ha scritto:
> >> +/*
> >> + * spte bits of bit 3 ~ bit 11 are used as low 9 bits of
> >> + * generation, the bits of bits 52 ~ bit 61 are used as
>
From: Johannes Weiner
Date: Wed, 20 Mar 2013 14:03:29 -0400
> The sparse code, when asking the architecture to populate the vmemmap,
> specifies the section range as a starting page and a number of pages.
>
> This is an awkward interface, because none of the arch-specific code
> actually thinks
On Wed, Mar 20, 2013 at 11:35 AM, Oleg Nesterov wrote:
> then we need "do not abuse ->cred_guard_mutex in threadgroup_lock()"
> acked by you and Li. Please let me know if I should resend it.
Yeah, we want that one regardless of this one. Please feel free to add
my Acked-by (if I hadn't acked
Hi Takashi,
would you please describe your test system in more detail? How
about 'lspci -tv'? And 'lsusb -v' of the broken device?
1. For me on Dell Vostro 3550 with a SandyBridge chip doing all
SATA+USB2+ExpressCardSlot:
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor
On Wed, Mar 20, 2013 at 01:41:30PM -0400, Mimi Zohar wrote:
[..]
> Defining another Kconfig option will either memlock all signed
> executables or none. If a distro ships with this new Kconfig enabled,
> then the 'ima_appraise_tcb' boot command line option would result in all
> executables,
On 03/20, Tejun Heo wrote:
>
> So, let's leave the locking in cgroup alone. I like
> cgroup_mutex to be the outer one.
OK... but sorry, I am a bit confused.
then we need "do not abuse ->cred_guard_mutex in threadgroup_lock()"
acked by you and Li. Please let me know if I should resend it.
Oleg.
On 03/20/2013 11:28 AM, Rafael J. Wysocki wrote:
On Wednesday, March 20, 2013 09:17:24 AM dirk.brande...@gmail.com wrote:
From: Dirk Brandewie
Some VMs seem to try to implement some MSRs but not all the registers
the driver needs. Check to make sure all the MSR that we need are
available. If
On Wed, Mar 20, 2013 at 7:43 PM, David Miller wrote:
>
> Please, in the future, post networking patches to net...@vger.kernel.org
> rather than lkml.
Sure, I was convinced that I did that. get_maintainer.pl is playing
tricks on me :)
$ ./scripts/get_maintainer.pl
So, overall,
On Wed, Mar 20, 2013 at 03:28:00AM +0800, Lai Jiangshan wrote:
...
> In this list, we can find that:
> 1) wq_mutex protects too much different kind of things.
I don't agree with this and unless you can come up with a much better
reason, won't be splitting wq_mutex further. Also,
On 03/12/2013 06:05 AM, Russell King - ARM Linux wrote:
> On Tue, Mar 12, 2013 at 09:58:29AM +0200, Silviu-Mihai Popescu wrote:
>> This uses PTR_RET instead of IS_ERR and PTR_ERR in order to increase
>> readability.
>>
>> Signed-off-by: Silviu-Mihai Popescu
>> ---
>>
On 03/20/2013 03:52 PM, Guenter Roeck wrote:
> So far, all instances of iio_hwmon set their hwmon name attribute
> to "iio_hwmon", which is not very descriptive. Set it to the device tree
> node name if available, and only revert to iio_hwmon otherwise.
>
> Signed-off-by: Guenter Roeck
> ---
>
On Wed, Mar 20, 2013 at 03:28:21AM +0800, Lai Jiangshan wrote:
> If lockdep complains something for other subsystem, lockdep_is_held() can be
> false negative. so we need to also test debug_locks before do assert.
>
> Signed-off-by: Lai Jiangshan
Applied to wq/for-3.10.
Thanks.
--
tejun
--
On Wednesday, March 20, 2013 09:17:24 AM dirk.brande...@gmail.com wrote:
> From: Dirk Brandewie
>
> Some VMs seem to try to implement some MSRs but not all the registers
> the driver needs. Check to make sure all the MSR that we need are
> available. If any of the required MSRs are not
The following problem was reported against a distribution kernel when
zone_reclaim was enabled but the same problem applies to the mainline
kernel. The reproduction case was as follows
1. Run numactl -m +0 dd if=largefile of=/dev/null
This allocates a large number of clean pages in node 0
2.
On Wed, Mar 20, 2013 at 03:28:18AM +0800, Lai Jiangshan wrote:
> Simply move it to pool->lock C.S.
Patch description should explain *why* in addition to what. Also,
please don't use abbreviations like C.S. Yeah, I know it's critical
section but it might as well be counter strike or context
On Wed, Mar 20, 2013 at 03:28:17AM +0800, Lai Jiangshan wrote:
> If we have 4096 CPUs, workqueue_cpu_up_callback() will travel too much CPUs,
> to avoid it, we use for_each_cpu_worker_pool for the cpu pools and
> use unbound_pool_hash for unbound pools.
>
> After it, for_each_pool() becomes
On Wed, 2013-03-20 at 14:01 -0400, Mimi Zohar wrote:
> Sorry, I'm not sure to which work you're referring. If you're referring
> to Dmitry's "initramfs with digital signature protection" patches, then
> we're speaking about enforcing integrity, not MAC security.
Well, in the absence of
On Wed, Mar 20, 2013 at 03:28:15AM +0800, Lai Jiangshan wrote:
> static struct worker *alloc_worker(void)
> {
> struct worker *worker;
> @@ -2326,7 +2262,8 @@ repeat:
> spin_unlock_irq(_mayday_lock);
>
> /* migrate to the target cpu if possible */
> -
On Wed, 2013-03-20 at 15:02 +0100, Takashi Iwai wrote:
> We encountered a problem that on some HP machines the Realtek PCI-e
> card reader device appears only when you inserted a card before the
> cold boot. While debugging, it turned out that the device is actually
> handled via PCI-e hotplug in
On Wednesday, March 20, 2013 09:54:01 AM Mike Turquette wrote:
> Quoting Rafael J. Wysocki (2013-03-02 14:27:52)
> > From: Rafael J. Wysocki
> >
> > Devices on the Intel Lynxpoint Low Power Subsystem (LPSS) have some
> > common features that aren't shared with any other platform devices,
> >
On Wednesday 20 March 2013 10:27 PM, Rhyland Klein wrote:
On 3/20/2013 9:44 AM, Laxman Dewangan wrote:
+ regulators {
+ dcdc1 {
+ regulator-name = "vdd-sys-5v0";
+
On 03/20/2013 01:02 PM, Jon Hunter wrote:
>
> On 03/20/2013 11:59 AM, Tomi Valkeinen wrote:
>> On 2013-03-20 17:44, Jon Hunter wrote:
>>>
>>> On 03/20/2013 06:56 AM, Tomi Valkeinen wrote:
On 2013-03-19 10:03, Alexandru Gheorghiu wrote:
> Use PTR_RET function instead of IS_ERR and
On Wed, 2013-03-20 at 16:49 +, Matthew Garrett wrote:
> On Wed, 2013-03-20 at 12:41 -0400, Mimi Zohar wrote:
>
> > Matthrew, perhaps you could clarify whether this will be tied to MAC
> > security. Based on the kexec thread, I'm under the impression that is
> > not the intention, or at least
Hotplug can happen at times when the memory situation is less than
perfect to allocate huge pages for the vmemmap. This series makes the
allocation try harder in patch #1. The remaining patches allow x86-64
to fall back to regular pages as a last resort before the hotplug
event fails completely.
No need to maintain addr_end and p_end when they are never actually
read anywhere on !pse setups. Remove the dead code.
Signed-off-by: Johannes Weiner
---
arch/x86/mm/init_64.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
index
We already have generic code to allocate vmemmap with regular pages,
use it.
Signed-off-by: Johannes Weiner
---
arch/x86/mm/init_64.c | 81 ---
1 file changed, 38 insertions(+), 43 deletions(-)
diff --git a/arch/x86/mm/init_64.c
Memory hotplug can happen on a machine under load, memory shortness
and fragmentation, so huge page allocations for the vmemmap are not
guaranteed to succeed.
Try to fall back to regular pages before failing the hotplug event
completely.
Signed-off-by: Johannes Weiner
---
arch/x86/mm/init_64.c
The sparse code, when asking the architecture to populate the vmemmap,
specifies the section range as a starting page and a number of pages.
This is an awkward interface, because none of the arch-specific code
actually thinks of the range in terms of 'struct page' units and
always translates it
From: Ben Hutchings
Hot-adding memory on x86_64 normally requires huge page allocation.
When this is done to a VM guest, it's usually because the system is
already tight on memory, so the request tends to fail. Try to avoid
this by adding __GFP_REPEAT to the allocation flags.
On 03/20/2013 11:59 AM, Tomi Valkeinen wrote:
> On 2013-03-20 17:44, Jon Hunter wrote:
>>
>> On 03/20/2013 06:56 AM, Tomi Valkeinen wrote:
>>> On 2013-03-19 10:03, Alexandru Gheorghiu wrote:
Use PTR_RET function instead of IS_ERR and PTR_ERR.
Patch found using coccinelle.
On Wed, Mar 20, 2013 at 03:28:10AM +0800, Lai Jiangshan wrote:
> rcu_read_lock_sched() is better than preempt_disable() if the code is
> protected by RCU_SCHED.
>
> Signed-off-by: Lai Jiangshan
Applied to wq/for-3.10.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line
* Steven Rostedt (rost...@goodmis.org) wrote:
> On Wed, 2013-03-20 at 12:18 +0900, kpark3...@gmail.com wrote:
> > From: Sahara
> >
> > Somehow tracepoint_entry_add/remove_probe functions allow a null probe
> > function.
>
> You actually hit this in practice, or is this just something that you
>
On 03/20/13 10:44, Gregory CLEMENT wrote:
> On 03/20/2013 06:26 PM, Gregory CLEMENT wrote:
>> On 03/20/2013 06:20 PM, Stephen Boyd wrote:
>>> On 03/20/13 10:09, Gregory CLEMENT wrote:
On 03/13/2013 07:17 PM, Stephen Boyd wrote:
> Separate the armada 370xp local timers from the local timer
On Wed, Mar 20, 2013 at 03:28:06AM +0800, Lai Jiangshan wrote:
> currently wq_mutext protects:
>
> * worker_pool_idr and unbound_pool_hash
> * pool->refcnt
> * workqueues list
> * workqueue->flags, ->nr_drainers
> * workqueue_freezing
>
> We can see that it protects very different things.
> So
On 20.03.2013 21:20, Peter Hurley wrote:
> As Ilya Zykov identified in his patch 'PROBLEM: Race condition in
> tty buffer's function flush_to_ldisc()', a race condition exists
> which allows a parallel flush_to_ldisc() to flush and free the tty
> flip buffers while those buffers are in-use. For
>From 951a078a5285ad31bc22e190616ad54b78fac992 Mon Sep 17 00:00:00 2001
From: Lai Jiangshan
Date: Wed, 20 Mar 2013 10:52:30 -0700
If pwq_adjust_max_active() changes max_active from 0 to
saved_max_active, it needs to wakeup worker. This is already done by
thaw_workqueues().
If
On Wed, Mar 20, 2013 at 03:02:01PM +0100, Takashi Iwai wrote:
> We encountered a problem that on some HP machines the Realtek PCI-e
> card reader device appears only when you inserted a card before the
> cold boot. While debugging, it turned out that the device is actually
> handled via PCI-e
On 03/20/2013 06:43 AM, Venu Byravarasu wrote:
> Stephen Warren wrote at Wednesday, March 20, 2013 1:51 AM:
>> On 03/18/2013 06:29 AM, Venu Byravarasu wrote:
>>> Registered tegra USB PHY as a separate platform driver.
>>> diff --git a/drivers/usb/phy/tegra_usb_phy.c
>>>
201 - 300 of 1483 matches
Mail list logo
