On Thu, 2013-01-24 at 16:24 +0100, Gu1 wrote:
> In different places in the Thermal code, the CPU frequency list is iterated
> in an incorrect way, leading to endless loops when the frequency list contains
> a CPUFREQ_TABLE_INVALID entry, which is the case by default in the the Exynos
> 4x12
On 02/01/13 07:13, Tao Ma wrote:
In our product system, we have several sata disks attached to one
machine. So when one of the disk fails, the jbd2(yes, we use ext4) will
hang forever and we will get something in /var/log/messages like below.
It seems to me that the io sent to the scsi
On Fri, Feb 1, 2013 at 6:47 AM, Sasha Levin wrote:
> This patch series adds a userspace lock correctnes validator into
> tools/lib/liblock.
>
> There are no changes to any kernel code whatsoever, lockdep is
> being used as is.
>
> First 6 patches are the liblock implementation, the last one is
>
On Fri, 2013-02-01 at 01:17 +, Russell King - ARM Linux wrote:
>
> > I've tried both gcc 4.6.3 [1] and 4.6.4 [2]. If you can point me to
> > a 4.5.x, I'll try that, too, but as it stands now, if one moves the
> > code added to swab.h below outside of its armv6 protection,
> > gcc adds calls
On Friday 01 February 2013 12:43 PM, Viresh Kumar wrote:
On 1 February 2013 12:17, Santosh Shilimkar wrote:
I haven't looked at the cpufreq code recently but remember
that it was needed to ensure that all the CPU which
share clock/voltage gets updated (affected cpus) on
freq change. The CPUs
On Thu, Jan 31, 2013 at 06:32:18PM -0700, Toshi Kani wrote:
> This is already done for PCI host bridges and platform devices and I don't
> > see why we can't do that for the other types of devices too.
> >
> > The only missing piece I see is a way to handle the "eject" problem, i.e.
> > when we
On Tue, Jan 29, 2013 at 03:40:26PM -0600, Seth Jennings wrote:
> This patchset adds support for flush pages out of the compressed
> pool to the swap device
>
I know you don't have a enough time since you sent previous patch.
Please add lots of words next time.
1. advertise "awesome feature",
On Thu, Jan 31, 2013 at 09:54:51PM +0100, Rafael J. Wysocki wrote:
> > > But, again, I'm going to ask why you aren't using the existing cpu /
> > > memory / bridge / node devices that we have in the kernel. Please use
> > > them, or give me a _really_ good reason why they will not work.
> >
> >
On Fri, Feb 01, 2013 at 12:48:16AM +0200, Stratos Karafotis wrote:
> On 02/01/2013 12:25 AM, Greg Kroah-Hartman wrote:
> >Given that no one is working on it, why does it need to be maintained
> >easier? :)
>
> Thanks for your immediate response.
> I was thinking to work on this driver. Is it
On 2013-01-30 오전 7:55, David Sterba wrote:
On Sat, Jan 26, 2013 at 02:50:43PM +0900, Kyungsik Lee wrote:
This patchset is for supporting LZ4 compressed kernel and initial ramdisk on
the x86 and ARM architectures.
Have you considered the 'high compression' mode of lz4?
On 1 February 2013 12:17, Santosh Shilimkar wrote:
> I haven't looked at the cpufreq code recently but remember
> that it was needed to ensure that all the CPU which
> share clock/voltage gets updated (affected cpus) on
> freq change. The CPUs which needs SW co-ordination, should
> have this flag
Signed-off-by: Wenyou Yang
Cc: li...@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org
---
arch/arm/boot/dts/at91sam9n12.dtsi |6 ++
arch/arm/boot/dts/at91sam9x5.dtsi |6 ++
2 files changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/at91sam9n12.dtsi
Add the function watchdog_is_open to check whether or not
the /dev/watchdog? is opened
Signed-off-by: Wenyou Yang
Cc: w...@iguana.be
Cc: linux-watch...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
include/linux/watchdog.h |8
1 file changed, 8 insertions(+)
diff --git
Signed-off-by: Wenyou Yang
Cc: w...@iguana.be
Cc: linux-watch...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
drivers/watchdog/at91sam9_wdt.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/watchdog/at91sam9_wdt.c b/drivers/watchdog/at91sam9_wdt.c
index c6d9f1f..e60a718
For this variable will be used in the timer handler.
Signed-off-by: Wenyou Yang
Cc: w...@iguana.be
Cc: linux-watch...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
drivers/watchdog/at91sam9_wdt.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Remove the global variable at91wdt_private, add the struct at91wdt_drvdata
as a substitute, and set it as the driver data of the at91wdt_wdd.
Signed-off-by: Wenyou Yang
Cc: w...@iguana.be
Cc: linux-watch...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
drivers/watchdog/at91sam9_wdt.c |
Tested on the at91sam9g25ek and at91sam9m10g45ek boards
Signed-off-by: Wenyou Yang
Cc: li...@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org
---
arch/arm/boot/dts/at91sam9m10g45ek.dts |4
arch/arm/boot/dts/at91sam9x5ek.dtsi|4
2 files changed, 8 insertions(+)
diff --git
According to Documentation/watchdog/convert_drivers_to_kernel_api.txt,
remove the file_operations struct, miscdevice, and obsolete includes
Since the at91sam watchdog inherent characteristics, add the watchdog
operations: at91wdt_start, at91wdt_stop and at91wdt_ping.
Signed-off-by: Wenyou Yang
Since the Watchdog Timer Mode Register can be only written only once,
so the watchdog_info shall not support WDIOF_SETTIMEOUT
and WDIOF_MAGICCLOSE options, remove them.
Signed-off-by: Wenyou Yang
Cc: w...@iguana.be
Cc: linux-watch...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
On 1/29/2013 4:29 PM, Linus Walleij wrote:
> On Tue, Jan 29, 2013 at 8:38 AM, Vishwanathrao Badarkhe, Manish
> wrote:
>
>> Currently, I2C driver gets probed before pinctrl driver.
>> To achieve I2C pin muxing via pinctrl driver before I2C
>> probe get called, register pinctrl driver in
On 2013-01-30 오전 6:09, Rajesh Pawar wrote:
Andrew Morton wrote:
On Sat, 26 Jan 2013 14:50:43 +0900
Kyungsik Lee wrote:
This patchset is for supporting LZ4 compressed kernel and initial ramdisk on
the x86 and ARM architectures.
According to [[http://code.google.com/p/lz4/,]] LZ4 is a very
On Fri, Feb 01, 2013 at 12:48:16AM +0200, Stratos Karafotis wrote:
> I will fix it.
I don't know the status of this driver.
But in general the patch should have been divided up into smaller
changes and sent as a patchset. It creates a bunch of messy new
globals where it would have been cleaner
On Friday 01 February 2013 12:10 PM, Viresh Kumar wrote:
policy->shared_type field was added only for SoCs with ACPI support:
commit 3b2d99429e3386b6e2ac949fc72486509c8bbe36
Author: Venkatesh Pallipadi
Date: Wed Dec 14 15:05:00 2005 -0500
P-state software coordination for ACPI core
On 1 February 2013 09:22, Viresh Kumar wrote:
> On 1 February 2013 00:14, Fabio Baltieri wrote:
>> As a sidenote, I noticed just now that since:
>>
>> bc92bea cpufreq: Notify governors when cpus are hot-[un]plugged
>>
>> governor's sampling_rate gets reset to default every time you hotplug a
>>
On 01/31/2013 06:28 PM, Nicolas Pitre wrote:
>>
>> Well, it is too nasty for public confession, but it's called
>> "paravirtualization".
>
> The fact that you are aware of it means we're not going to break them.
>
> But my point is that we must not be held back just in case someone out
>
On 1 February 2013 12:10, Viresh Kumar wrote:
> policy->shared_type field was added only for SoCs with ACPI support:
>
> commit 3b2d99429e3386b6e2ac949fc72486509c8bbe36
> Author: Venkatesh Pallipadi
> Date: Wed Dec 14 15:05:00 2005 -0500
>
> P-state software coordination for ACPI core
>
>
On 1 February 2013 12:10, Viresh Kumar wrote:
> With following patch, we need to set policy->cpus with mask of all possible
> cpus
> and policy->related_cpus would be filled automatically by the core.
>
> commit 4948b355e90080cd5ec1e91189f65a01e4186ef2
> Author: Viresh Kumar
> Date: Tue Jan
With following patch, we need to set policy->cpus with mask of all possible cpus
and policy->related_cpus would be filled automatically by the core.
commit 4948b355e90080cd5ec1e91189f65a01e4186ef2
Author: Viresh Kumar
Date: Tue Jan 29 14:39:08 2013 +
cpufreq: Simplify cpufreq_add_dev()
On 1 February 2013 12:10, Viresh Kumar wrote:
> For multicore SoC's, with cores sharing clock line, we are required to set
> policy->cpus and policy->related_cpus with mask of cpus.
>
> With following patch, we need to set policy->cpus with mask of all possible
> cpus
> and policy->related_cpus
policy->shared_type field was added only for SoCs with ACPI support:
commit 3b2d99429e3386b6e2ac949fc72486509c8bbe36
Author: Venkatesh Pallipadi
Date: Wed Dec 14 15:05:00 2005 -0500
P-state software coordination for ACPI core
http://bugzilla.kernel.org/show_bug.cgi?id=5737
Many
For multicore SoC's, with cores sharing clock line, we are required to set
policy->cpus and policy->related_cpus with mask of cpus.
With following patch, we need to set policy->cpus with mask of all possible cpus
and policy->related_cpus would be filled automatically by the cpufreq core.
commit
Hi Balbi,
On Fri, Feb 1, 2013 at 11:52 AM, Vivek Gautam wrote:
> Hi Kishon,
>
>
> On Fri, Feb 1, 2013 at 10:51 AM, kishon wrote:
>> Hi,
>>
>>
>> On Thursday 31 January 2013 09:08 PM, Felipe Balbi wrote:
>>>
>>> On Thu, Jan 31, 2013 at 09:00:37PM +0530, Vivek Gautam wrote:
Hi Felipe,
Hi Kishon,
On Fri, Feb 1, 2013 at 10:51 AM, kishon wrote:
> Hi,
>
>
> On Thursday 31 January 2013 09:08 PM, Felipe Balbi wrote:
>>
>> On Thu, Jan 31, 2013 at 09:00:37PM +0530, Vivek Gautam wrote:
>>>
>>> Hi Felipe,
>>>
>>>
>>> On Thu, Jan 31, 2013 at 8:55 PM, Felipe Balbi wrote:
Hi,
Guenter,
Thank you so much for all the comments, will re-send a v2 iteration soon.
On 31 January 2013 02:37, Guenter Roeck wrote:
> On Wed, Jan 30, 2013 at 06:21:28PM +0800, Hongbo Zhang wrote:
>> Each of ST-Ericsson X500 chip set series consists of both ABX500 and DBX500
>> chips. This is
In shmem_find_get_pages_and_swap, use the faster radix tree iterator
construct from 78c1d78 "radix-tree: introduce bit-optimized iterator".
Signed-off-by: Johannes Weiner
---
mm/shmem.c | 25 -
1 file changed, 12 insertions(+), 13 deletions(-)
diff --git a/mm/shmem.c
Hi All,
In our product system, we have several sata disks attached to one
machine. So when one of the disk fails, the jbd2(yes, we use ext4) will
hang forever and we will get something in /var/log/messages like below.
It seems to me that the io sent to the scsi layer is never returned back
An inactive file list is considered low when the its active
counter-part is bigger, regardless of whether it is a global zone LRU
list or a memcg zone LRU list. The only difference is in how the LRU
size is assessed.
get_lru_size() does the right thing for both global and memcg reclaim
On Fri, Feb 01, 2013 at 11:07:27, Philip, Avinash wrote:
> DT field of "interrupts" was mentioned wrongly as "interrupt" in SPI
> node. This went unnoticed as spi-omap2 driver not making use of
> interrupt. Fixes the typo.
>
> Signed-off-by: Philip Avinash
Reported-by: Vaibhav Bedia
Typo
The fact that mlock calls get_user_pages, and get_user_pages might
call mlock when expanding a stack looks like a potential recursion.
However, mlock makes sure the requested range is already contained
within a vma, so no stack expansion will actually happen from mlock.
Should this ever change:
Inodes are added to the head of the superblock LRU list and reclaimed
from the tail. If trylocking an inode during reclaim fails, it has to
be moved to the head of the list, not the tail, to prevent spinning on
it.
Signed-off-by: Johannes Weiner
---
fs/inode.c | 4 ++--
1 file changed, 2
On Thu, 2013-01-31 at 16:42 -0500, Matt Porter wrote:
> On Thu, Jan 31, 2013 at 08:58:39PM +, Arnd Bergmann wrote:
> > On Thursday 31 January 2013, Matt Porter wrote:
> > > On Wed, Jan 30, 2013 at 09:32:58AM +, Arnd Bergmann wrote:
> > > > On Wednesday 30 January 2013, Matt Porter wrote:
>
DT field of "interrupts" was mentioned wrongly as "interrupt" in SPI
node. This went unnoticed as spi-omap2 driver not making use of
interrupt. Fixes the typo.
Signed-off-by: Philip Avinash
---
arch/arm/boot/dts/am33xx.dtsi |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
On Tue, 2013-01-08 at 16:18 -0800, Amit Daniel Kachhap wrote:
> This patch modifies the code to use get_crit_temp instead of
> the normal get_trip_temp when critical threshold point is crossed
> or queried about.
>
is there any problem in the current code?
> Signed-off-by: Amit Daniel Kachhap
On 1 February 2013 11:12, Viresh Kumar wrote:
> Currently, whenever governor->governor() is called for CPUFRREQ_GOV_START
> event
> we reset few tunables of governor. Which isn't correct, as this routine is
> called for every cpu hot-[un]plugging event. We should actually be resetting
> these
Currently, whenever governor->governor() is called for CPUFRREQ_GOV_START event
we reset few tunables of governor. Which isn't correct, as this routine is
called for every cpu hot-[un]plugging event. We should actually be resetting
these only when the governor module is removed and re-installed.
Nicolas Pitre wrote:
On Fri, 1 Feb 2013, Hui Wang wrote:
Cyril Chemparathy wrote:
From: Vitaly Andrianov
This patch fixes the alloc_init_pud() function to use phys_addr_t instead of
unsigned long when passing in the phys argument.
This is an extension to commit
Please pull.
The following changes since commit 88b62b915b0b7e25870eb0604ed9a92ba4bfc9f7:
Linus Torvalds (1):
Linux 3.8-rc6
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
for-linus
YOSHIFUJI Hideaki (1):
Hi,
On Thursday 31 January 2013 09:08 PM, Felipe Balbi wrote:
On Thu, Jan 31, 2013 at 09:00:37PM +0530, Vivek Gautam wrote:
Hi Felipe,
On Thu, Jan 31, 2013 at 8:55 PM, Felipe Balbi wrote:
Hi,
On Thu, Jan 31, 2013 at 08:53:27PM +0530, Vivek Gautam wrote:
Moreover, SoCs having multiple
The min and max values for regulators are getting assigned before actually
the voltage is set. So making sure that min and max values are assigned
only if the voltage is successfully set else keeping the last successfully
set voltage's min and max values.
This is boot tested on OMAP4430 and
On 01/31/2013 10:13 PM, paul.sz...@sydney.edu.au wrote:
> [trim /] Does not that prove that PAE is broken?
Please, Paul, take *yes* for an answer. It is broken. You've received
multiple dissertations on why it is going to stay that way. Unless you
fix it yourself, and everyone seems to be
On Friday 25 January 2013 10:14 AM, Stephen Warren wrote:
On 01/24/2013 04:57 PM, Mike Turquette wrote:
Quoting Stephen Warren (2013-01-24 11:32:37)
On 01/24/2013 11:20 AM, Mike Turquette wrote:
Quoting Prashant Gaikwad (2013-01-04 18:44:48)
On Friday 04 January 2013 10:00 PM, Stephen Warren
A simple test to make sure we handle rwlocks correctly.
Signed-off-by: Sasha Levin
---
tools/lib/liblock/tests/WW.c | 16
1 file changed, 16 insertions(+)
create mode 100644 tools/lib/liblock/tests/WW.c
diff --git a/tools/lib/liblock/tests/WW.c b/tools/lib/liblock/tests/WW.c
This patch series adds a userspace lock correctnes validator into
tools/lib/liblock.
There are no changes to any kernel code whatsoever, lockdep is
being used as is.
First 6 patches are the liblock implementation, the last one is
an example of liblock being used on an existing codebase.
Sasha
This is a rather simple and basic test suite to test common locking
issues.
Beyond tests, it also shows how to use the library.
Signed-off-by: Sasha Levin
---
tools/lib/liblock/run_tests.sh | 16
tools/lib/liblock/tests/AA.c | 16
Both pthreads and lockdep support dealing with rwlocks, so here's the
liblock implementation for those.
Signed-off-by: Sasha Levin
---
tools/lib/liblock/include/liblock/rwlock.h | 78 ++
1 file changed, 78 insertions(+)
create mode 100644
liblock is simply userspace lockdep. We can use that to analyze and
verify the locking in perf.
Usage is simple, to compile perf with liblock all that's needed it:
make LIBLOCK=[path to liblock]
Once liblock support is compiled in, perf will yell if locking goes
wrong for any reason:
kernel/lockdep.c deals with validating locking scenarios for various
architectures supported by the kernel. There isn't anything kernel
specific going on in lockdep, and when we compare userspace to other
architectures that don't have to deal with irqs such as s390, they
become all too similar.
Signed-off-by: Sasha Levin
---
MAINTAINERS | 5 +
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 212c255..f26afae 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4637,6 +4637,11 @@ F: drivers/lguest/
F: include/linux/lguest*.h
F: tools/lguest/
These headers provide the same API as their pthread mutex counterparts.
The design here is to allow to easily switch to liblock lock validation
just by adding a "liblock_" to pthread_mutex_*() calls, which means that
it's easy to integrate liblock into existing codebases.
Signed-off-by: Sasha
On 01/31/2013 09:20 PM, Sachin Kamat wrote:
> On 31 January 2013 22:30, Stephen Warren wrote:
>> On 01/31/2013 03:25 AM, Sachin Kamat wrote:
>>> Use the newly introduced devm_ioremap_resource() instead of
>>> devm_request_and_ioremap() which provides more consistent error handling.
>>
>>
On 31 January 2013 22:30, Stephen Warren wrote:
> On 01/31/2013 03:25 AM, Sachin Kamat wrote:
>> Use the newly introduced devm_ioremap_resource() instead of
>> devm_request_and_ioremap() which provides more consistent error handling.
>
> Presumably though that function isn't yet available in the
On 02/01/2013 01:20 AM, Stephen Warren wrote:
> On 01/30/2013 08:51 PM, Mark Zhang wrote:
>> On 01/31/2013 04:19 AM, Stephen Warren wrote:
>>> On 01/30/2013 12:20 AM, Mark Zhang wrote:
On 01/30/2013 11:02 AM, Alexandre Courbot wrote:
> Add support for the Chunghwa CLAA101WA01A display
From: Len Brown
This patch enables turbostat to run properly on the
next-generation Intel(R) Microarchitecture, code named Haswell (HSW).
HSW supports the BCLK and counters found in SNB.
Signed-off-by: Len Brown
---
tools/power/x86/turbostat/turbostat.c | 11 ++-
1 file changed, 10
From: Len Brown
When verbose is enabled, print the C1E-Enable
bit in MSR_IA32_POWER_CTL.
also delete some redundant tests on the verbose variable.
Signed-off-by: Len Brown
---
arch/x86/include/uapi/asm/msr-index.h | 2 ++
tools/power/x86/turbostat/turbostat.c | 13 +++--
2 files
Here are some pathces I have queued in my tree for
the next release to support Haswell.
Please let me know if you see issues with any of them.
thanks!
-Len
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Thu, 31 Jan 2013, Joonsoo Kim wrote:
> A static mapped area is ARM-specific, so it is better not to use
> generic vmalloc data structure, that is, vmlist and vmlist_lock
> for managing static mapped area. And it causes some needless overhead and
> reducing this overhead is better idea.
>
>
From: Len Brown
This patch enables intel_idle to run on the
next-generation Intel(R) Microarchitecture code named Haswell.
Signed-off-by: Len Brown
---
drivers/idle/intel_idle.c | 39 +++
1 file changed, 39 insertions(+)
diff --git
From: Len Brown
The commit, 4202735e8ab6ecfb0381631a0d0b58fefe0bd4e2
(cpuidle: Split cpuidle_state structure and move per-cpu statistics fields)
observed that the MWAIT flags for Cn on every processor to date were the
same, and created get_driver_data() to supply them.
Unfortunately, that
On Fri, 2013-02-01 at 11:57 +0800, Li Zefan wrote:
> on 2013/2/1 11:48, Steven Rostedt wrote:
> > Li,
> >
> > Can you give an Ack or Nack for this.
> >
>
> I think this patch shouldn't go into upstream without bcache code. We don't
> export symbols for out of tree code.
>
Even for GPL code? I
On Thu, 31 Jan 2013, Cyril Chemparathy wrote:
> This series is a repost of the LPAE related changes in preparation for the
> introduction of the Keystone sub-architecture. The original series has now
> been split, and this particular series excludes the earlier changes to the
> runtime code
on 2013/2/1 11:48, Steven Rostedt wrote:
> Li,
>
> Can you give an Ack or Nack for this.
>
I think this patch shouldn't go into upstream without bcache code. We don't
export symbols for out of tree code.
> Thanks,
>
> -- Steve
>
>
> On Tue, 2013-01-15 at 13:25 -0800, Kent Overstreet wrote:
On 31 January 2013 18:36, Rafael J. Wysocki wrote:
> On Thursday, January 31, 2013 12:06:13 PM Fabio Baltieri wrote:
>> On Thu, Jan 31, 2013 at 04:23:06PM +0530, Viresh Kumar wrote:
>> > As discussed over IRC, you will fix following in few days:
>> > - Code redundancy within governors
>> > -
On 1 February 2013 00:14, Fabio Baltieri wrote:
> Hello Viresh, thanks for getting this done... looks much cleaner now!
>
> I tested both patches on my ux500 setup (dual Cortex-A9) and it seems to
> run correctly on both CPU load changes and CPU hotplug, so:
>
> Tested-by: Fabio Baltieri
On Thu, 31 Jan 2013, Cyril Chemparathy wrote:
> On LPAE machines, PHYS_OFFSET evaluates to a phys_addr_t and this type is
> inherited by the PHYS_PFN_OFFSET definition as well. Consequently, the kernel
> build emits warnings of the form:
>
> init/main.c: In function 'start_kernel':
>
Li,
Can you give an Ack or Nack for this.
Thanks,
-- Steve
On Tue, 2013-01-15 at 13:25 -0800, Kent Overstreet wrote:
> Exported so it can be used by bcache's tracepoints
>
> Signed-off-by: Kent Overstreet
> CC: Steven Rostedt
> CC: Frederic Weisbecker
> CC: Ingo Molnar
> ---
>
On Thu, 31 Jan 2013, Cyril Chemparathy wrote:
> This patch redefines the early boot time use of the R4 register to steal a few
> low order bits (ARCH_PGD_SHIFT bits) on LPAE systems. This allows for up to
> 38-bit physical addresses.
>
> Signed-off-by: Cyril Chemparathy
> Signed-off-by: Vitaly
On Thu, 31 Jan 2013, Cyril Chemparathy wrote:
> This patch adds an architecture defined override for ARCH_LOW_ADDRESS_LIMIT.
> On PAE systems, the absence of this override causes bootmem to incorrectly
> limit itself to 32-bit addressable physical memory.
>
> Signed-off-by: Cyril Chemparathy
>
Hi Simon,
On 02/01/2013 11:06 AM, Simon Jeons wrote:
How can distinguish map and use? I mean how can confirm memory is used
by kernel instead of map?
If the page is free, for example, it is in the buddy system, it is not
in use.
Even if it is direct mapped by kernel, the kernel logic should
On Fri, 1 Feb 2013, Hui Wang wrote:
> Cyril Chemparathy wrote:
> > From: Vitaly Andrianov
> >
> > This patch fixes the alloc_init_pud() function to use phys_addr_t instead of
> > unsigned long when passing in the phys argument.
> >
> > This is an extension to commit
On 01/31/2013 02:11 PM, xtu4 wrote:
[SEQ_FILE] Avoid high order memory allocating with kmalloc
when read large seq file
currently, when dumpstate access /proc/xxx/binder , this binder
include lots of info,
it will use seq_read in kernel, in this function, it will trigger high
order memory
>> +{ 0x8086, 0x8c08, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_2port_sata_snb },
>> /* SATA Controller IDE (Lynx Point) */
>> { 0x8086, 0x8c09, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich8_2port_sata },
>
>Also, are you sure this one and the following Lynx Point controllers are
> not affected?
On 01/31/2013 02:11 PM, xtu4 wrote:
[SEQ_FILE] Avoid high order memory allocating with kmalloc
when read large seq file
currently, when dumpstate access /proc/xxx/binder , this binder
include lots of info,
it will use seq_read in kernel, in this function, it will trigger high
order memory
On Fri, Feb 1, 2013 at 11:20 AM, Joe Perches wrote:
>> @@ -15,13 +15,15 @@ struct parsed_partitions {
>> int flags;
>> bool has_info;
>> struct partition_meta_info info;
>> - } parts[DISK_MAX_PARTS];
>> + } *parts;
>
> This is relatively unusual
On Fri, 2013-02-01 at 11:07 +0800, Ming Lei wrote:
> Currently, sizeof(struct parsed_partitions) may be 64KB in 32bit arch,
> so it is easy to trigger page allocation failure by check_partition,
[]
> This patch does below optimizations on the allocation of struct
> parsed_partitions to try to
On Thu, Jan 31, 2013 at 10:13:05AM -0500, Alan Stern wrote:
> On Thu, 31 Jan 2013, Aaron Lu wrote:
>
> > > > +static int scsi_blk_runtime_suspend(struct device *dev)
> > > > +{
> > > > + struct scsi_device *sdev = to_scsi_device(dev);
> > >
> > > For this routine and the other new ones, it
> On 30-01-2013 21:19, Youquan Song wrote:
>
>> There is a quirk patch 5e5a4f5d5a08c9c504fe956391ac3dae2c66556d
>
> Please also specify the summary of that patch in parens.
>
>> fix the 4 ports
>
>s/fix/fixing/
>
>> IDE controller 32bit PIO mode.
>> Recently, the problem was showed
>
>
Dear Ben,
PAE is broken for any amount of RAM.
>>> No it isn't.
>> Could I please ask you to expand on that?
>
> I already did, a few messages back.
OK, thanks. Noting however that fewer than those back, I said:
... PAE with any RAM fails the "sleep test":
n=0; while [ $n -lt 33000 ];
There is a quirk patch 5e5a4f5d5a08c9c504fe956391ac3dae2c66556d
"ata_piix: make DVD Drive recognisable on systems with Intel Sandybridge
chipsets(v2)
This quirk patch fixes one kind of bug inside some Intel Sandybridge
chipsets, see reports from
Cyril Chemparathy wrote:
From: Vitaly Andrianov
This patch fixes the alloc_init_pud() function to use phys_addr_t instead of
unsigned long when passing in the phys argument.
This is an extension to commit 97092e0c56830457af0639f6bd904537a150ea4a (ARM:
pgtable: use phys_addr_t for physical
Currently, sizeof(struct parsed_partitions) may be 64KB in 32bit arch,
so it is easy to trigger page allocation failure by check_partition,
especially in hotplug block device situation(such as, USB mass storage,
MMC card, ...), and Felipe Balbi has observed the failure.
This patch does below
Hi Tang,
On Fri, 2013-02-01 at 10:42 +0800, Tang Chen wrote:
I confuse!
> Hi Simon,
>
> On 02/01/2013 10:17 AM, Simon Jeons wrote:
> >> For example:
> >>
> >> 64TB, what ever
> >> xxxTB, what ever
> >> logic address space:
> >>
On Thu, 31 Jan 2013, Joonsoo Kim wrote:
> In current implementation, we used ARM-specific flag, that is,
> VM_ARM_STATIC_MAPPING, for distinguishing ARM specific static mapped area.
> The purpose of static mapped area is to re-use static mapped area when
> entire physical address range of the
On 01/14/2013 11:26 AM, Cong Ding wrote:
> the variable backup_current_thread_info isn't freed before existing the
> function.
>
> Signed-off-by: Cong Ding
> ---
> arch/powerpc/kernel/kgdb.c |5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git
On Fri, 2013-02-01 at 13:12 +1100, paul.sz...@sydney.edu.au wrote:
> Dear Ben,
>
> >> PAE is broken for any amount of RAM.
> >
> > No it isn't.
>
> Could I please ask you to expand on that?
I already did, a few messages back.
Ben.
--
Ben Hutchings
Everything should be made as simple as
In ack_apic_level(), when there is pending affinity setting for current irq,
ioapic_irqd_mask()/ioapic_irqd_unmask() will try to mask the irq and do the
irq affinity setting.
But at this time, it is possibility that the irq has been masked, in this case,
we should not unmask it directly in
On Thu, 31 Jan 2013 18:30:15 -0800
Mukesh Rathor wrote:
> This patch fixes a fixme in Linux to use alloc_xenballooned_pages() to
> allocate pfns for grant table pages instead of kmalloc. This also
> simplifies add to physmap on the xen side a bit.
Looking at it again, I realized rc should be
Hi Simon,
On 02/01/2013 10:17 AM, Simon Jeons wrote:
For example:
64TB, what ever
xxxTB, what ever
logic address space: |_kernel___|_user_|
\ \ / /
On 1 February 2013 08:01, Viresh Kumar wrote:
> Really!! I see bleeding edge as df0e3f4 and i don't see the $(subject) patch
> in it :)
Well it might have been dropped by Rafael due to build error, which would
be fixed by:
diff --git a/drivers/cpufreq/cpufreq_governor.c
On Thu, Jan 31, 2013 at 01:06:46PM -0600, Seth Jennings wrote:
> On 01/31/2013 01:07 AM, Minchan Kim wrote:
> > On Tue, Jan 29, 2013 at 03:40:23PM -0600, Seth Jennings wrote:
> >> zswap is a thin compression backend for frontswap. It receives
> >> pages from frontswap and attempts to store them in
On Mon, 2013-01-21 at 22:14 +, Seiji Aguchi wrote:
> +void trace_irq_vector_regfunc(void)
> +{
> + if (!trace_irq_vector_refcount) {
> + smp_call_function(switch_to_trace_idt, NULL, 0);
> + local_irq_disable();
> + switch_to_trace_idt(NULL);
> +
1 - 100 of 1296 matches
Mail list logo
