The NVIDIA's Tegra KBC has maximum 24 pins to make matrix keypad.
Any pin can be configured as row or column. The maximum column pin
can be 8 and maximum row pin can be 16.
Remove the assumption that all first 16 pins will be used as row
and remaining as columns and Add the property for
Tegra KBC driver have the default key mapping for 16x8 configuration.
The key mapping can be provided through platform data or through DT
and the mapping varies from platform to platform, hence this default
mapping is not so useful. Remove the default mapping to reduce the code
lines of the
This patch series:
- fix build warning,
- use devm_* for allocation,
- make column/rows configuration through DT and
- remove the rarely used key mapping table.
Changes from V1:
- renames the rows and pins property array.
- nit cleanups.
Laxman Dewangan (4):
input: keyboard: tegra: fix
Use devm_* for memory, clock, input device allocation. This reduces
code for freeing these resources.
Signed-off-by: Laxman Dewangan
---
Changes from V1:
None
drivers/input/keyboard/tegra-kbc.c | 93 +++-
1 files changed, 28 insertions(+), 65 deletions(-)
Fix the following build warning when building driver with CONFIG_PM_SLEEP
not selected.
tegra-kbc.c:360:13: warning: 'tegra_kbc_set_keypress_interrupt' defined but not
used [-Wunused-function]
Signed-off-by: Laxman Dewangan
---
Changes form V1:
- none
drivers/input/keyboard/tegra-kbc.c |
On Fri, Jan 4, 2013 at 10:40 PM, Roman Dubtsov wrote:
> On Fri, 2013-01-04 at 03:57 -0800, Michel Lespinasse wrote:
>> If this doesn't help, could you please send me your test case ? I
>> think you described enough of it that I would be able to reproduce it
>> given some time, but it's just
On Fri, Jan 04, 2013 at 11:26:43PM -0600, Simon Jeons wrote:
> On Sat, 2013-01-05 at 11:26 +0800, Fengguang Wu wrote:
> > > > > Hi Namjae,
> > > > >
> > > > > Why use bdi_stat_error here? What's the meaning of its comment
> > > > > "maximal
> > > > > error of a stat counter"?
> > > > Hi Simon,
>
On Fri, Dec 28, 2012 at 9:04 AM, Kamezawa Hiroyuki
wrote:
> (2012/12/26 2:27), Sha Zhengju wrote:
>> From: Sha Zhengju
>>
>> If memcg is enabled and no non-root memcg exists, all allocated pages
>> belongs to root_mem_cgroup and go through root memcg statistics routines
>> which brings some
ldo->en_pin is set iff the regulator is enabled by external pin.
This patch sets ldo->en_pin to NULL if lp8788_gpio_request_ldo_en() fails, then
we can use it to determinate if the regulator is controlled by external pin or
register.
lp8788_get_ldo_enable_mode(), lp8788_ldo_ctrl_by_extern_pin()
On Saturday 05 January 2013 01:22 AM, Stephen Warren wrote:
On 01/04/2013 04:02 AM, Laxman Dewangan wrote:
Tegra KBC driver have the default key mapping for 16x8 configuration.
The key mapping can be provided through platform data or through DT
and the mapping varies from platform to platform,
On 01/05/2013 06:21 AM, Marcelo Tosatti wrote:
> On Fri, Jan 04, 2013 at 09:55:40PM +0800, Xiao Guangrong wrote:
>> Little cleanup for reexecute_instruction, also use gpa_to_gfn in
>> retry_instruction
>>
>> Signed-off-by: Xiao Guangrong
>> ---
>> arch/x86/kvm/x86.c | 13 ++---
>> 1
On Fri, 2013-01-04 at 03:57 -0800, Michel Lespinasse wrote:
> On Fri, Jan 04, 2013 at 12:09:37AM +0700, Roman Dubtsov wrote:
> > On Wed, 2013-01-02 at 16:09 -0800, Michel Lespinasse wrote:
> > > > Is there an interest in fixing this or concurrent mmaps() from the same
> > > > process are too much
Hi Richard,
On Fri, Jan 4, 2013 at 9:35 PM, Richard Cochran
wrote:
> On Fri, Jan 04, 2013 at 09:31:04PM +0200, Pantelis Antoniou wrote:
>> The following patchset introduces Device Tree overlays, a method
>> of dynamically altering the kernel's live Device Tree.
>
> It would be nice to know the
On 01/04/2013 10:08 PM, Mel Gorman wrote:
Zhouping, please test this patch.
Tested it, the issue is gone with following patch.
Tested-by: Zhouping Liu
Thanks,
Zhouping
Andrea and Hugh, any comments on whether this could be improved?
---8<---
mm: thp: Acquire the anon_vma rwsem for lock
> -Original Message-
> From: Jason Wang [mailto:jasow...@redhat.com]
> Sent: Saturday, January 05, 2013 12:03 AM
> To: gre...@linuxfoundation.org; KY Srinivasan; Haiyang Zhang; linux-
> ker...@vger.kernel.org
> Cc: tho...@redhat.com; Jason Wang
> Subject: [PATCH] tools: fix a typo in
Judging anonymous memory's vm_area_struct,
perf_mmap_event's filename will be set to
"//anon" indicating this vma is belong to
anonymous memory.
Once hugepage is used, vma's vm_file points
to hugetlbfs. In this way, this vma will not
be regarded as anonymous memory by is_anon_memory()
in perf user
On Sat, 2013-01-05 at 11:26 +0800, Fengguang Wu wrote:
> > > > Hi Namjae,
> > > >
> > > > Why use bdi_stat_error here? What's the meaning of its comment "maximal
> > > > error of a stat counter"?
> > > Hi Simon,
> > >
> > > As you know bdi stats (BDI_RECLAIMABLE, BDI_WRITEBACK …) are kept in
> >
On Fri, 2012-12-07 at 10:23 +, Mel Gorman wrote:
> From: Lee Schermerhorn
>
> NOTE: Once again there is a lot of patch stealing and the end result
> is sufficiently different that I had to drop the signed-offs.
> Will re-add if the original authors are ok with that.
>
> This
Signed-off-by: Jason Wang
---
tools/hv/hv_set_ifconfig.sh |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/tools/hv/hv_set_ifconfig.sh b/tools/hv/hv_set_ifconfig.sh
index 3e9427e..daf7ec0 100755
--- a/tools/hv/hv_set_ifconfig.sh
+++ b/tools/hv/hv_set_ifconfig.sh
@@ -65,4
On Wed, Jan 2, 2013 at 6:44 PM, Michal Hocko wrote:
> On Wed 26-12-12 01:26:07, Sha Zhengju wrote:
>> From: Sha Zhengju
>>
>> This patch adds memcg routines to count dirty pages, which allows memory
>> controller
>> to maintain an accurate view of the amount of its dirty memory and can
>>
When I do a grep for K8 in my .config file all I get is the following:
> grep -i k8 /usr/local/hugedisk/src/linux-3.6.11/.config
CONFIG_MK8=y
CONFIG_X86_POWERNOW_K8=y
When I try your grep command I get:
> grep -E "^CONFIG_SENSORS" /usr/local/hugedisk/src/linux-3.6.11/.config|grep K
On Fri, Jan 4, 2013 at 6:02 PM, Shuah Khan wrote:
> I applied your patch to 3.6.11 and changed the panic() to pr_info()
> and also changed enough_mem_for_swiotlb() to always return false to
> simulate not enough memory condition as this system does have enough
> memory.
>
> So at least on this
Dear RT Folks,
I'm pleased to announce the 3.2.36-rt54 stable release.
This release is just an update to the new stable 3.2.36 version
and no RT specific changes have been made.
You can get this release via the git tree at:
On Fri, Jan 04, 2013 at 09:31:04PM +0200, Pantelis Antoniou wrote:
> The following patchset introduces Device Tree overlays, a method
> of dynamically altering the kernel's live Device Tree.
It would be nice to know the motivation for this code.
What is the use case? What problem or issue is
query EFI facilities
Reply-To: <1357219085-4312-2-git-send-email-m...@console-pimps.org>
In-Reply-To: <1357219085-4312-2-git-send-email-m...@console-pimps.org>
> diff --git a/init/main.c b/init/main.c
> index e33e09d..e71d924 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -604,7 +604,7 @@
> > > Hi Namjae,
> > >
> > > Why use bdi_stat_error here? What's the meaning of its comment "maximal
> > > error of a stat counter"?
> > Hi Simon,
> >
> > As you know bdi stats (BDI_RECLAIMABLE, BDI_WRITEBACK …) are kept in
> > percpu counters.
> > When these percpu counters are
Inside bus_add_driver(), one device might be added(device_add()) into
the bus or probed which is triggered by deferred probe
just after completing of driver_attach() and before
'klist_add_tail(>knode_bus, >p->klist_drivers)',
so the device won't be probed by this driver.
This patch moves the
Hi Namjae,
On Sun, Dec 30, 2012 at 02:59:50PM +0900, Namjae Jeon wrote:
> From: Namjae Jeon
>
> Consider Process A: huge I/O on sda
> doing heavy write operation - dirty memory becomes more
> than dirty_background_ratio
> on HDD - flusher thread flush-8:0
>
> Consider
From: fangxiaozhi
1. Optimize the match rules with new macro for Huawei USB storage devices,
to avoid to load USB storage driver for the modem interface
with Huawei devices.
2. Add to support new switch command for new Huawei USB dongles.
Signed-off-by: fangxiaozhi
On Friday 04 January 2013 09:55 PM, Stephen Warren wrote:
On 01/03/2013 10:51 PM, Prashant Gaikwad wrote:
Convert clk out to composite clock type which removes
the mux clock.
Signed-off-by: Prashant Gaikwad
---
This patch is rebased on ccf-rework for Tegra patch series. It is just to show
how
If one storage interface or usb network interface(iSCSI case)
exists in current configuration, memory allocation with
GFP_KERNEL during usb_device_reset() might trigger I/O transfer
on the storage interface itself and cause deadlock because
the 'us->dev_mutex' is held in .pre_reset() and the
From: fangxiaozhi
1. Define a new macro for USB storage match rules:
matching with Vendor ID and interface descriptors.
Signed-off-by: fangxiaozhi
diff -uprN linux-3.8-rc2_orig/drivers/usb/storage/usb.c
On Saturday 05 January 2013 03:48 AM, Stephen Boyd wrote:
On 01/03/13 21:51, Prashant Gaikwad wrote:
diff --git a/drivers/clk/Makefile b/drivers/clk/Makefile
index f0b269a..baf7608 100644
--- a/drivers/clk/Makefile
+++ b/drivers/clk/Makefile
@@ -2,7 +2,8 @@
obj-$(CONFIG_HAVE_CLK)
Hi Michal,
Sorry for my late response, I'm just back from vocation. : )
On Wed, Jan 2, 2013 at 5:08 PM, Michal Hocko wrote:
> On Wed 26-12-12 01:22:36, Sha Zhengju wrote:
>> From: Sha Zhengju
>>
>> Commit a8e7d49a(Fix race in create_empty_buffers() vs
>> __set_page_dirty_buffers())
>>
On Tue, Dec 18, 2012 at 09:42:30AM -0800, Yinghai Lu wrote:
> On Tue, Dec 18, 2012 at 9:33 AM, H. Peter Anvin wrote:
> > On 12/18/2012 09:07 AM, Youquan Song wrote:
> >> Blacklist x2apic when Nivida graphics enabled on Lenovo ThinkPad T420.
> >> Also set blacklist x2apic for Lenovo ThinkPad W520
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
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 |
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 Friday 04 January 2013 10:00 PM, Stephen Warren wrote:
On 01/04/2013 12:00 AM, Prashant Gaikwad wrote:
Use common of_clk_init() function for clocks initialization.
drivers/clk/tegra/clk-tegra20.c |3 ++-
drivers/clk/tegra/clk-tegra30.c |3 ++-
Oh, so this series is written
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
Using module_platform_driver() replaces module_init() and module_exit()
and makes the code simpler.
Remove '__init' annotation from the function 'at91wdt_probe'
since the driver becomes hot-plug aware now.
Signed-off-by: Wenyou Yang
Cc: w...@iguana.be
Cc: linux-watch...@vger.kernel.org
Cc:
Tested on the at91sam9g25ek boards
Signed-off-by: Wenyou Yang
Cc: li...@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org
---
arch/arm/boot/dts/at91sam9x5ek.dtsi |4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/at91sam9x5ek.dtsi
b/arch/arm/boot/dts/at91sam9x5ek.dtsi
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
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 a3d1a09..53ede84
Thanks for your patch, it might be useful as_PR3 off method of I2C hosts and
targets might be different from their _PR0 off method, ACPI BIOS may implement
protection in the _PR3 off method in order not to break the transactions during
the powering off process:
As I2C is wired-AND logic bus, if
Cc: Eric Dumazet
Cc: David Decotigny
Cc: Tom Herbert
Cc: Ingo Molnar
Signed-off-by: Ming Lei
--
v7:
- rebase on v3.8-rc2-next-20130104
v4:
- call pm_runtime_set_memalloc_noio(ddev, true) after
device_add
---
net/core/net-sysfs.c |5 +
1 file changed, 5 insertion
Hi Kame,
Sorry for the late response, I'm just back from vocation. : )
On Fri, Dec 28, 2012 at 8:39 AM, Kamezawa Hiroyuki
wrote:
> (2012/12/26 2:22), Sha Zhengju wrote:
>> From: Sha Zhengju
>>
>> Commit a8e7d49a(Fix race in create_empty_buffers() vs
>> __set_page_dirty_buffers())
>> extracts
On Wed, Jan 02, 2013 at 10:37:26AM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the driver-core.current tree got a conflict
> in drivers/i2c/busses/i2c-au1550.c between commit 0b255e927d47 ("i2c:
> remove __dev* attributes from subsystem") from Linus' tree and commit
This patch applies the introduced memalloc_noio_save() and
memalloc_noio_restore() to force memory allocation with no I/O
during runtime_resume/runtime_suspend callback on device with
the flag of 'memalloc_noio' set.
Cc: Alan Stern
Cc: Oliver Neukum
Cc: Rafael J. Wysocki
Signed-off-by: Ming
This patch applyes the introduced pm_runtime_set_memalloc_noio on
block device so that PM core will teach mm to not allocate memory with
GFP_IOFS when calling the runtime_resume and runtime_suspend callback
for block devices and its ancestors.
Cc: Jens Axboe
Signed-off-by: Ming Lei
--
v5:
The patch introduces the flag of memalloc_noio in 'struct dev_pm_info'
to help PM core to teach mm not allocating memory with GFP_KERNEL
flag for avoiding probable deadlock.
As explained in the comment, any GFP_KERNEL allocation inside
runtime_resume() or runtime_suspend() on any one of device in
in memalloc_noio_save()/memalloc_noio_restore()
- rebase on v3.8-rc2-next-20130104
v6:
- replace GFP_IO with __GFP_IO to fix compile failure
v5:
- use inline instead of macro to define memalloc_noio_*
- replace memalloc_noio() with memalloc_noio_flags() to
make
and looks no one objects these patches?
Change logs:
V7:
- rebase on v3.8-rc2-next-20130104
- move memalloc_noio_save/memalloc_noio_restore into
rpm_callback to avoid code duplication, as suggested
by Rafael
- optimize on pm_runtime_set_memalloc_noio(true
> OK, I see the patch I mentioned to fix the problem was later reverted [1].
> The real fix is "libata: replace sata_settings with devslp_timing" [2].
Yes, please use [2] which can also be found in kernel bugzilla #51881
and is pending on Jeff's acceptance. Sorry for the trouble to you guys.
Would you like to take it? It is needed by Linux OSVs.
Thanks
-Youquan
On Tue, Dec 18, 2012 at 12:20:23PM -0500, Youquan Song wrote:
> Run in perf utility at Ivybridge EP server, encouter "not supported" event
>
> L1-dcache-loads
> L1-dcache-load-misses
>
- Original Message -
> From: "Christoph Lameter"
> To: "CAI Qian"
> Cc: net...@vger.kernel.org, "Dave Miller" ,
> sta...@vger.kernel.org, "linux-kernel"
> , "Pekka Enberg" , "Glauber
> Costa"
> Sent: Friday, January 4, 2013 11:05:35 PM
> Subject: Re: load/unload dccp module caused
On Fri, Jan 4, 2013 at 4:55 PM, Yinghai Lu wrote:
> On Fri, Jan 4, 2013 at 3:21 PM, Shuah Khan wrote:
>
>> Please see attached dmesg for full log. I can do some testing on this
>> system with your patch if you would like.
>
> That would be great.
>
> Please try
>
The text in Documentation said it would be removed in 2.6.41;
the text in the Kconfig said removal in the 3.1 release. Either
way you look at it, we are well past both, so push it off a cliff.
Note that the POWER_CSTATE and the POWER_PSTATE are part of the
legacy tracing API. Remove all
The actual deletion is mind-numbingly simple; and if you go by the
comments in the code, it is well overdue. However, in discussions
with Frederic, he suggested to me that those comments might have
been overly optimistic, and that there may still be people out
there who are still unknowingly
Jiri Olsa [jo...@redhat.com] wrote:
| On Tue, Dec 18, 2012 at 11:28:02PM -0800, Sukadev Bhattiprolu wrote:
| >
| > Rename EVENT_ATTR() and EVENT_PTR() PMU_EVENT_ATTR() and PMU_EVENT_PTR().
| > Make them global so they are available to all architectures.
| >
| > Further to allow architectures
On Fri, Jan 4, 2013 at 6:08 AM, Mel Gorman wrote:
> Despite the reason for these commits, NUMA balancing is not the direct
> source of the problem. split_huge_page() expected the anon_vma lock to be
> exclusive to serialise the whole split operation. Ordinarily it is expected
> that the anon_vma
On 2013/1/5 5:50, Bjorn Helgaas wrote:
> [+to Yijing, +cc Kenji]
>
> On Fri, Jan 4, 2013 at 1:01 PM, Bjorn Helgaas wrote:
>> On Thu, Jan 3, 2013 at 8:41 AM, Jiang Liu wrote:
>>> Hi Daniel,
>>> It seems like an issue caused by recursive PCIe HPC.
>>> Could you please help to try the
This driver was for the 8 bit ISA cards that were installed in
the PC-XT machines of 1980 vintage. They supported the dual
ribbon cable MFM drives of 10-20MB capacity, and ran at a 3:1
interleave, giving performance on the order of 128kB/s.
By the introduction of the PC-AT (286) these
Mel Gorman wrote:
> On Wed, Jan 02, 2013 at 08:08:48PM +, Eric Wong wrote:
> > Instead, I disabled THP+compaction under v3.7.1 and I've been unable to
> > reproduce the issue without THP+compaction.
> >
>
> Implying that it's stuck in compaction somewhere. It could be the case
> that
On Fri, Jan 04, 2013 at 05:16:27PM -0700, David Ahern wrote:
> Known problem. Pick one of: update perf to 3.7, add H to the command
> (-e cycles:ppH) or apply this patch:
> https://lkml.org/lkml/2012/12/28/384
I spoke too soon. This works for cycles, but not for branch-misses:
pannekake:~>
On Friday, January 04, 2013 05:36:55 PM Bjorn Helgaas wrote:
> On Fri, Jan 4, 2013 at 5:19 PM, Yinghai Lu wrote:
> > On Fri, Jan 4, 2013 at 4:14 PM, Rafael J. Wysocki wrote:
> >> On Friday, January 04, 2013 04:03:01 PM Yinghai Lu wrote:
> >>> On Fri, Jan 4, 2013 at 3:38 AM, Rafael J. Wysocki
On Fri, 2013-01-04 at 16:41 +0900, Namjae Jeon wrote:
> 2013/1/4, Simon Jeons :
> > On Thu, 2013-01-03 at 13:35 +0900, Namjae Jeon wrote:
> >> 2013/1/2, Jan Kara :
> >> > On Tue 01-01-13 08:51:04, Wanpeng Li wrote:
> >> >> On Mon, Dec 31, 2012 at 12:30:54PM +0100, Jan Kara wrote:
> >> >> >On Sun
On 01/03/2013 12:17 PM, Rik van Riel wrote:
+ if (!(head % 7) && delay < MAX_SPINLOCK_DELAY)
+ delay++;
+
+ loops = delay * waiters_ahead;
I don't like the head % 7 thing. I think using fixed point arithmetic
would be nicer:
if (delay <
Currently free_all_bootmem_core ignores that node_min_pfn may be not
multiple of BITS_PER_LONG. E.g. commit 6dccdcbe "mm: bootmem: fix
checking the bitmap when finally freeing bootmem" shifts vec by lower
bits of start instead of lower bits of idx. Also
if (IS_ALIGNED(start, BITS_PER_LONG) &&
The mm-of-the-moment snapshot 2013-01-04-15-43 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
On Fri, Jan 4, 2013 at 5:19 PM, Yinghai Lu wrote:
> On Fri, Jan 4, 2013 at 4:14 PM, Rafael J. Wysocki wrote:
>> On Friday, January 04, 2013 04:03:01 PM Yinghai Lu wrote:
>>> On Fri, Jan 4, 2013 at 3:38 AM, Rafael J. Wysocki wrote:
>>> >> --- a/arch/x86/include/asm/pci.h
>>> >> +++
Commit 5a505085f04 ("mm/rmap: Convert the struct anon_vma::mutex to an
rwsem") turned anon_vma mutex to rwsem.
However, the properly annotated nested locking in mm_take_all_locks() has
been converted from
mutex_lock_nest_lock(_vma->root->mutex, >mmap_sem);
to
down_write_nest_lock() provides means to annotate locking scenario where
an outter lock is guaranteed to serialize the order nested locks are being
acquired.
This is an analogy to already existing mutex_lock_nest_lock() and
spin_lock_nest_lock().
Signed-off-by: Jiri Kosina
---
On Fri, 2013-01-04 at 15:03 -0800, Hugh Dickins wrote:
> On Thu, 3 Jan 2013, Simon Jeons wrote:
> > On Wed, 2013-01-02 at 21:10 -0800, Hugh Dickins wrote:
> > >
> > > As you can see, remove_rmap_item_from_tree uses it to decide whether
> > > or not it should rb_erase the rmap_item from the
Currently free_all_bootmem_core ignores that node_min_pfn may be not
multiple of BITS_PER_LONG. E.g. commit 6dccdcbe "mm: bootmem: fix
checking the bitmap when finally freeing bootmem" shifts vec by lower
bits of start instead of lower bits of idx. Also
if (IS_ALIGNED(start, BITS_PER_LONG) &&
On Fri, Jan 04, 2013 at 05:16:27PM -0700, David Ahern wrote:
> Known problem. Pick one of: update perf to 3.7, add H to the command
> (-e cycles:ppH) or apply this patch:
> https://lkml.org/lkml/2012/12/28/384
Oh, thinking of it, I've actually read about this flamew^Wdiscussion :-)
Thanks!
/*
On Fri, Jan 4, 2013 at 4:14 PM, Rafael J. Wysocki wrote:
> On Friday, January 04, 2013 04:03:01 PM Yinghai Lu wrote:
>> On Fri, Jan 4, 2013 at 3:38 AM, Rafael J. Wysocki wrote:
>> >> --- a/arch/x86/include/asm/pci.h
>> >> +++ b/arch/x86/include/asm/pci.h
>> >> @@ -14,6 +14,7 @@
>> >> struct
On 1/4/13 4:47 PM, Steinar H. Gunderson wrote:
[Please Cc me on any replies; I'm not subscribed to lkml]
Hi,
I recently upgraded from 3.6.5 to 3.7.1 to get around some MM issues that
have been bothering me. However, it appears it broke PEBS:
pannekake:/usr/src/linux-3.7.1# perf record -a
[Please Cc me on any replies; I'm not subscribed to lkml]
Hi,
I recently upgraded from 3.6.5 to 3.7.1 to get around some MM issues that
have been bothering me. However, it appears it broke PEBS:
pannekake:/usr/src/linux-3.7.1# perf record -a -e cycles:pp
Error: sys_perf_event_open()
On Friday, January 04, 2013 04:03:01 PM Yinghai Lu wrote:
> On Fri, Jan 4, 2013 at 3:38 AM, Rafael J. Wysocki wrote:
> >> --- a/arch/x86/include/asm/pci.h
> >> +++ b/arch/x86/include/asm/pci.h
> >> @@ -14,6 +14,7 @@
> >> struct pci_sysdata {
> >> int domain; /* PCI
On Fri, Jan 4, 2013 at 3:38 AM, Rafael J. Wysocki wrote:
>> --- a/arch/x86/include/asm/pci.h
>> +++ b/arch/x86/include/asm/pci.h
>> @@ -14,6 +14,7 @@
>> struct pci_sysdata {
>> int domain; /* PCI domain */
>> int node; /* NUMA node */
>> +
Tony,
Can you review this patchset?
Seiji
> -Original Message-
> From: Anton Vorontsov [mailto:cbouatmai...@gmail.com]
> Sent: Friday, December 21, 2012 6:37 PM
> To: Seiji Aguchi
> Cc: Luck, Tony (tony.l...@intel.com); linux-kernel@vger.kernel.org;
> ccr...@android.com;
On Friday, January 04, 2013 07:27:24 AM Daniel Lezcano wrote:
> On 01/02/2013 10:13 PM, Russ Anderson wrote:
> > On Wed, Dec 26, 2012 at 11:01:48AM +0100, Daniel Lezcano wrote:
> >> The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces
> >> a lock in the cpuidle_get_cpu_driver function.
On Fri, Jan 4, 2013 at 3:21 PM, Shuah Khan wrote:
> Please see attached dmesg for full log. I can do some testing on this
> system with your patch if you would like.
That would be great.
Please try
git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
for-x86-boot
or just
On Fri, Jan 04, 2013 at 09:12:46PM +0200, Pantelis Antoniou wrote:
> Device tree can store multiple strings in a single property.
> We didn't handle that case properly.
>
> Signed-off-by: Pantelis Antoniou
Acked-by: David Gibson
--
David Gibson| I'll have my music
2012/12/30 Paul E. McKenney :
> On Mon, Dec 24, 2012 at 12:43:25AM +0100, Frederic Weisbecker wrote:
>> 2012/12/21 Steven Rostedt :
>> > On Thu, 2012-12-20 at 19:32 +0100, Frederic Weisbecker wrote:
>> >> Let's imagine you have 4 CPUs. We keep the CPU 0 to offline RCU callbacks
>> >> there and to
On Fri, Jan 04, 2013 at 09:56:59PM +0800, Xiao Guangrong wrote:
> The current reexecute_instruction can not well detect the failed instruction
> emulation. It allows guest to retry all the instructions except it accesses
> on error pfn
>
> For example, some cases are nested-write-protect - if the
From: Lubomir Rintel
Date: Fri, 4 Jan 2013 15:17:43 +0100
> @@ -943,7 +943,7 @@ static int txq_reclaim(struct tx_queue *txq, int budget,
> int force)
> struct netdev_queue *nq = netdev_get_tx_queue(mp->dev, txq->index);
> int reclaimed;
>
> - __netif_tx_lock(nq,
From: Peter Huewe
Date: Thu, 3 Jan 2013 15:23:50 +0100
> Sparse complains that:
> drivers/net/ethernet/broadcom/tg3.c:5670:55: sparse: constant
> 0x7fff is so big it is long long (on x86/32 bit)
>
> so we suffix the constant with LL in the header file.
>
> Reported-by: Fengguang
On Thu, 3 Jan 2013, Simon Jeons wrote:
> On Wed, 2013-01-02 at 21:10 -0800, Hugh Dickins wrote:
> >
> > As you can see, remove_rmap_item_from_tree uses it to decide whether
> > or not it should rb_erase the rmap_item from the unstable_tree.
> >
> > Every full scan of all the rmap_items, we
On Fri, Jan 4, 2013 at 2:56 PM, Shuah Khan wrote:
>
> AMD IOMMU driver is using this lever to leave swiotlb enabled when it
> detects devices that can't be supported by iommu. My concern is that
> this change for kdump removes that handshake ability between iommu and
> swiolb.
No, it does not
On Fri, Jan 4, 2013 at 2:47 PM, Eric W. Biederman wrote:
> Yinghai Lu it looks like your autodetection of the problem case in this
> patch is problematic and needs a rethink. My quick skim says you are
> trying to detect failure too early in the code. Furthermore having
> kexec on panic sized
On Fri, Jan 4, 2013 at 10:16 AM, Andy Lutomirski wrote:
> I still have quite a few instances of 2-6 ms of latency due to
> "call_rwsem_down_read_failed __do_page_fault do_page_fault
> page_fault". Any idea why? I don't know any great way to figure out
> who is holding mmap_sem at the time.
On Fri, Jan 4, 2013 at 3:47 PM, Eric W. Biederman wrote:
> Shuah Khan writes:
>
>> On Fri, Jan 4, 2013 at 3:10 PM, Yinghai Lu wrote:
>>> On Fri, Jan 4, 2013 at 1:02 PM, Shuah Khan wrote:
Pani'cing the system doesn't sound like a good option to me in this
case. This change to disable
> From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
> Subject: Re: [PATCH 7/8] zswap: add to mm/
>
> On 01/03/2013 04:33 PM, Dan Magenheimer wrote:
> >> From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
> >>
> >> However, once the flushing code was introduced and could free an entry
We shouldn't print the current century every time we read the RTC.
Signed-off-by: Bjorn Helgaas
---
arch/x86/kernel/rtc.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/rtc.c b/arch/x86/kernel/rtc.c
index 801602b..2e8f3d3 100644
---
Shuah Khan writes:
> On Fri, Jan 4, 2013 at 3:10 PM, Yinghai Lu wrote:
>> On Fri, Jan 4, 2013 at 1:02 PM, Shuah Khan wrote:
>>> Pani'cing the system doesn't sound like a good option to me in this
>>> case. This change to disable swiotlb is made for kdump. However, with
>>> this change several
Silicon does not support standard AHCI BAR assignment. Add
vendor/device exception to force BAR 2.
Signed-off-by: Hugh Daschbach
---
v2: Corrected comment in response to Sergei's review. Thanks, Sergei.
drivers/ata/ahci.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff
On Fri, Jan 4, 2013 at 2:26 PM, Shuah Khan wrote:
> However, I think regression on existing behavior with a
> panic is a bit of a big hammer. Thie change causes panic on systems
> even when kdump is not enabled, if I understand it correctly.
I don't think so.
+static bool __init
On Fri, Jan 04, 2013 at 09:55:40PM +0800, Xiao Guangrong wrote:
> Little cleanup for reexecute_instruction, also use gpa_to_gfn in
> retry_instruction
>
> Signed-off-by: Xiao Guangrong
> ---
> arch/x86/kvm/x86.c | 13 ++---
> 1 files changed, 6 insertions(+), 7 deletions(-)
>
> diff
1 - 100 of 798 matches
Mail list logo
