Currently, kdump just makes all the logical processors leave VMX operation by
executing VMXOFF instruction, so any VMCSs active on the logical processors may
be corrupted. But, sometimes, we need the VMCSs to debug guest images contained
in the host vmcore. To prevent the corruption, we should VMCL
This patch adds an atomic notifier list named vmclear_notifier_list.
When loading kvm-intel module, a notifier will be registered in
the list to enable vmcss loaded on all cpus to be VMCLEAR'd if
needed.
Signed-off-by: Zhang Yanfei
---
arch/x86/include/asm/kexec.h |2 ++
arch/x86/kernel/cras
> From: Konrad Rzeszutek Wilk
> Sent: Tuesday, November 20, 2012 7:48 PM
> To: Dan Magenheimer
> Cc: linux-kernel@vger.kernel.org; xen-de...@lists.xen.org
> Subject: Re: [PATCH] xen: tmem: selfballooning should be enabled when xen
> tmem is enabled
>
> On Tue, Nov 20, 2012 at 02:42:18PM -0800, Da
The notifier will be registered in vmclear_notifier_list when loading
kvm-intel module. And the bitmap indicates whether we should do
VMCLEAR operation in kdump. The bits in the bitmap are set/unset
according to different conditions.
Signed-off-by: Zhang Yanfei
---
arch/x86/kvm/vmx.c | 77
On Mon 19-11-12 21:15:50, Ronny Meeus wrote:
> Hello
Hi,
> I have an created an application that measures the cpuload consumed by
> the tasks within a process.
> For this I use the file /proc/stat and /proc//tasks//stat
>
> The cpuload monitor is a very simple application that just executes in
>
Hi Linus,
Here a final (hopefully) oneliner for the pinctrl subsystem targeted at v3.7.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit 77b67063bb6bce6d475e910d3b886a606d0d91f7:
Linux 3.7-rc5 (2012-11-11 13:44:33 +0100)
are available in the git repository at:
g
On 21 November 2012 20:46, Greg KH wrote:
> On Wed, Nov 21, 2012 at 08:21:40PM +0530, Sachin Kamat wrote:
>> On 21 November 2012 20:16, Greg KH wrote:
>> > On Wed, Nov 21, 2012 at 10:49:07AM +0530, Sachin Kamat wrote:
>> >> kfree on a NULL pointer is a no-op.
>> >>
>> >> Signed-off-by: Sachin Kam
Signed-off-by: David Howells
Acked-by: Arnd Bergmann
Acked-by: Thomas Gleixner
Acked-by: Michael Kerrisk
Acked-by: Paul E. McKenney
Acked-by: Dave Jones
---
include/scsi/Kbuild |3 ---
include/uapi/scsi/Kbuild|3 +++
include/uapi/scsi/scsi_bsg_fc.h |
On Fri, 16 Nov 2012 11:32:46 -0500, Murali Karicheri
wrote:
> On 11/15/2012 11:20 AM, Grant Likely wrote:
> > On Mon, 12 Nov 2012 16:28:22 -0500, Murali Karicheri
> > wrote:
> >> This adds OF support to DaVinci SPI controller to configure platform
> >> data through device bindings.
> >>
> >> Si
commit 5515061d22f0 ("mm: throttle direct reclaimers if PF_MEMALLOC reserves
are low and swap is backed by network storage") introduced a check for
fatal signals after a process gets throttled for network storage. The
intention was that if a process was throttled and got killed that it
should not t
Signed-off-by: David Howells
Acked-by: Arnd Bergmann
Acked-by: Thomas Gleixner
Acked-by: Michael Kerrisk
Acked-by: Paul E. McKenney
Acked-by: Dave Jones
---
include/scsi/fc/Kbuild|4
include/uapi/scsi/fc/Kbuild |4
include/uapi/scsi/fc/fc_els.h |0
include/u
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Wednesday, November 21, 2012 1:21 AM
> To: Dan Magenheimer
> Cc: xen-de...@lists.xen.org; Konrad Wilk; linux-kernel@vger.kernel.org
> Subject: Re: [Xen-devel] [PATCH] xen: tmem: selfballooning should be enabled
> when xen tmem is enabled
>
>
On 11/21/12 14:02, Cho KyongHo wrote:
This removes System MMU initialization from arch/arm/mach-exynos/
Basically, looks OK to me, but I think, this removing change should be
done after 03/12 patch :-)
to move them to DT and the exynos-iommu driver except gating clock
definitions.
Change-I
On Wed, Nov 21, 2012 at 2:09 AM, Jan Kara wrote:
> I haven't heard about such problem so far. What filesystem are you using?
I've tried ext2/ext3/ext4/reiserfs/btrfs ... all seems to be slower
than before. Seems to be fs independent.
> Can you quantify 'is slower'? Bisecting would be welcome o
On Wed, 2012-11-21 at 07:01 -0800, Joe Perches wrote:
> checkpatch isn't a perfect tool. Given how it's constructed,
> I doubt it ever could be.
Joe - I completely agree, this is why I'm not to concern about the
potential miss in the version I suggested.
Thanks,
Eilon
--
To unsubscribe from t
Signed-off-by: David Howells
Acked-by: Arnd Bergmann
Acked-by: Thomas Gleixner
Acked-by: Michael Kerrisk
Acked-by: Paul E. McKenney
Acked-by: Dave Jones
---
include/rdma/Kbuild |6 --
include/rdma/rdma_netlink.h | 36 +---
includ
On Tue, 20 Nov 2012 15:48:24 -0800, Simon Glass wrote:
> Hi Grant,
>
> On Tue, Nov 20, 2012 at 2:32 PM, Grant Likely
> wrote:
> > On Tue, Nov 20, 2012 at 10:23 PM, Simon Glass wrote:
> >> Hi,
> >>
> >> I hope this is a stupid question with an easy answer, but I cannot find it.
> >>
> >> I have
On 11/21/12 14:03, Cho KyongHo wrote:
Touching some System MMU needs its master devices' clock to be enabled
before. This commit adds clk_ops.set_parent of gating clocks of System
MMU to ensure gating clocks of System MMU's mater devices are enabled
when enabling gating clocks of System MMU.
Cha
Hello,
On 11/21/2012 2:05 AM, Minchan Kim wrote:
On Tue, Nov 20, 2012 at 03:49:35PM +0100, Marek Szyprowski wrote:
> Hello,
>
> On 11/20/2012 1:01 AM, Minchan Kim wrote:
> >Hi Marek,
> >
> >On Mon, Nov 12, 2012 at 09:59:42AM +0100, Marek Szyprowski wrote:
> >> It has been observed that system te
On Wed, 21 Nov 2012 00:24:48 -0700, Jason Gunthorpe
wrote:
> This allows platform_device_add a chance to call insert_resource
> on all of the resources from OF. At a minimum this fills in proc/iomem
> and presumably makes resource tracking and conflict detection work
> better.
>
> Signed-off-by:
Hi Olof and Arnd,
based on my chat with Olof today I have created new branch
with 4 patches which move zynq to multiplatform.
This branch depends on arm-soc devel/debug_ll_init branch because
we needed Rob's "ARM: implement debug_ll_io_init()"
(sha1: afaee03511ba8002b26a9c6b1fe7d6baf33eac86)
patc
Linus,
On Wed, Nov 21, 2012 at 03:45:42PM +0100, Linus Walleij wrote:
> On Wed, Nov 21, 2012 at 11:20 AM, Sebastian Hesselbarth
> wrote:
> > On 11/21/2012 10:59 AM, Linus Walleij wrote:
> >> On Mon, Nov 19, 2012 at 10:39 AM, Sebastian Hesselbarth
> >> wrote:
> >>> This patch relies on a patch
>>> On 21.11.12 at 16:42, Dan Magenheimer wrote:
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Wednesday, November 21, 2012 1:21 AM
>> To: Dan Magenheimer
>> Cc: xen-de...@lists.xen.org; Konrad Wilk; linux-kernel@vger.kernel.org
>> Subject: Re: [Xen-devel] [PATCH] xen: tmem: selfballo
The following adds a helper for matching the linux,stdout-path property
in the chosen node and makes use of it in the i.MX serial and Atmel serial
driver.
changes since v4:
- add option support and check stdout-path too
changes since v3:
- move code from separate files to drivers/of/base.c an
On Wed, Nov 21, 2012 at 3:51 PM, Grant Likely wrote:
> On Wed, 21 Nov 2012 00:24:48 -0700, Jason Gunthorpe
> wrote:
>> This allows platform_device_add a chance to call insert_resource
>> on all of the resources from OF. At a minimum this fills in proc/iomem
>> and presumably makes resource track
Hello,
Am 09.11.2012 15:27, schrieb Alexander Holler:
> Am 09.11.2012 15:21, schrieb richard -rw- weinberger:
>> On Fri, Nov 9, 2012 at 2:12 PM, Alexander Holler
>> wrote:
>>> While implementing the same functionality for arm, I've noticed that
>>> memtest does an unnecessary round to zero the m
When someone sends a patch there are a several possible responses:
1) Ack the patch.
2) Request that the submitter redo it. The downside is that no one
likes redoing patches.
3) Reject the patch.
4) Redo it yourself and say "Based on a patch from Sachin Kamat".
This isn't nice because everyo
By just reversing the order memtest is using the test patterns, an
additional round to zero the memory is not necessary.
This makes it a bit faster.
Signed-off-by: Alexander Holler
---
arch/x86/mm/memtest.c | 11 ++-
1 files changed, 2 insertions(+), 9 deletions(-)
diff --git a/arch/
I've used the source of memtest.c for a 32bit version (to use with ARM)
and checkpatch had some warnings. This patch removes them.
It also changes the message if bad memory was found from warning
to emergency.
Signed-off-by: Alexander Holler
---
arch/x86/mm/memtest.c | 10 ++
1 files
commit 57a0c44fca179c27808a5f2fae718e7eab9d6243
Dave,
This is a batch of fixes intended for 3.7...
Included are two pulls. Regarding the mac80211 tree, Johannes says:
"Please pull my mac80211.git tree (see below) to get two more fixes for
3.7. Both fix regressions introduced *before* this cycl
On Wed, 21 Nov 2012 13:10:44 +0530, "Philip, Avinash"
wrote:
> Add support for encoding PWM properties in bit encoded form with
> of_pwm_xlate_with_flags() function support. Platforms require platform
> specific PWM properties has to populate in 3rd cell of the pwm-specifier
> and PWM driver shou
Hi Peter,
On Mon, Nov 19, 2012 at 01:28:53PM -0500, Peter Hurley wrote:
> On Mon, 2012-11-19 at 18:46 +0100, Samuel Ortiz wrote:
> > Hi Peter,
> >
> > On Fri, Nov 09, 2012 at 06:55:29AM -0500, Peter Hurley wrote:
> > > The older southbridges supported by the lpc_ich driver do not
> > > provide me
Hi Paul,
On Mon, Nov 19, 2012 at 09:04:11PM +0100, Paul Bolle wrote:
> At every boot of an (outdated) laptop lpc_ich prints an error:
> lpc_ich :00:1f.0: I/O space for GPIO uninitialized
>
> But if one looks at lpc_ich's probe function one notices that the code
> only cares if both lpc_ic
Hi Joe
On Wed, Nov 14, 2012 at 4:31 PM, Joe Perches wrote:
> On Tue, 2012-11-13 at 14:50 +0800, Andrew Cooks wrote:
>> The boot_delay parameter affects all printk(), even if the log level
>> prevents visible output from the call. It results in delays greater
>> than the user intended without pu
Hi Alan,
> There is an Intel driver with open kernel code and proprietary userspace for
> the Imagination 3D engine (EMGD) although only for an out of maintenance
> Fedora and for Meego and in both cases for ancient kernels.
I knew about EMGD, but not that there's code available for parts of it.
On Wed, 21 Nov 2012 10:31:34 +0900, Mark Brown
wrote:
> On Tue, Nov 20, 2012 at 09:54:29PM +, Grant Likely wrote:
> > On Sat, 17 Nov 2012 19:55:45 +0900, Alexandre Courbot
> > wrote:
>
> > > With the advent of the device tree and of ARM kernels that are not
> > > board-tied, we cannot rely
Devices making use of PM reset are getting incorrectly identified as
not supporting reset because pci_pm_reset() fails unless the device is
in D0 power state. When first attached to vfio_pci devices are
typically in an unknown power state. We can fix this by explicitly
setting the power state or
From: "John W. Linville"
Date: Wed, 21 Nov 2012 11:24:06 -0500
> Included are two pulls. Regarding the mac80211 tree, Johannes says:
>
> "Please pull my mac80211.git tree (see below) to get two more fixes for
> 3.7. Both fix regressions introduced *before* this cycle that weren't
> noticed unti
Hi Inderpal,
On Wed, Oct 17, 2012 at 11:48:55AM +0530, Inderpal Singh wrote:
> reg_offset is offset of the status/mask registers. Now, since status_base
> and mask_base are pointing to corresponding first registers, reg_offset
> should start from 0 otheriwse regmap_add_irq_chip will fail during pr
On Wed, Nov 21, 2012 at 10:21:06AM +, Mel Gorman wrote:
>
> I am not including a benchmark report in this but will be posting one
> shortly in the "Latest numa/core release, v16" thread along with the latest
> schednuma figures I have available.
>
Report is linked here https://lkml.org/lkml/
On Wed, Nov 21, 2012 at 08:59:08PM +0530, Sachin Kamat wrote:
> On 21 November 2012 20:46, Greg KH wrote:
> > On Wed, Nov 21, 2012 at 08:21:40PM +0530, Sachin Kamat wrote:
> >> On 21 November 2012 20:16, Greg KH wrote:
> >> > On Wed, Nov 21, 2012 at 10:49:07AM +0530, Sachin Kamat wrote:
> >> >> k
On Wed 21-11-12 09:09:41, Jeff Moyer wrote:
> Jan Kara writes:
>
> >> Just to be clear, are you saying you would like me to remove the
> >> mutex_lock/unlock pair from ext4_sync_file? (I had already factored out
> >> the common code between this new code path and the fsync path in my tree.)
> >
Christoph Hellwig writes:
> On Mon, Nov 19, 2012 at 11:41:23PM -0800, Darrick J. Wong wrote:
>> Provide VFS helpers for handling O_SYNC AIO DIO writes. Filesystems wanting
>> to
>> use the helpers have to pass DIO_SYNC_WRITES to __blockdev_direct_IO. If the
>> filesystem doesn't provide its ow
On Tue, Nov 20, 2012 at 11:29 PM, Olof Johansson wrote:
>
> On Tue, Nov 20, 2012 at 02:48:58PM -0800, Doug Anderson wrote:
> > From: Olof Johansson
> >
> > UART3 is used for debugging on exynos5250-snow.
> >
> > [dianders: cleaned commit message.]
> >
> > Signed-off-by: Olof Johansson
> > Signed
From: Olof Johansson
Add support for using UART3 for DEBUG_LL on exynos.
[dianders: added depend on ARCH_EXYNOS.]
Signed-off-by: Olof Johansson
Signed-off-by: Doug Anderson
---
Changes in v2:
- Matched Olof's commit message.
- Added ARCH_EXYNOS to depend list.
arch/arm/Kconfig.debug
Hi Rachna,
On Fri, Nov 16, 2012 at 10:33:00AM +, Patil, Rachna wrote:
> Hi,
>
> This is just a gentle reminder of the patch set I had posted earlier viz.
> "[PATCH RESEND 0/7] MFD: ti_am335x_tscadc: DT support and TSC features
> addition"
> Can this patch set be pulled in if there are no rev
On Mon, Nov 19, 2012 at 11:06 PM, Ingo Molnar wrote:
>
> Oh, finally a clue: you seem to have vsyscall emulation
> overhead!
Ingo, stop it already!
This is *exactly* the kind of "blame everybody else than yourself"
behavior that I was talking about earlier.
There have been an absolute *shitload
On 11/17/2012 05:03 PM, Marcin Slusarz wrote:
On Sat, Nov 17, 2012 at 08:35:18PM +0100, Mikael Pettersson wrote:
mplayer worked fine on my Dell Latitude E6510 (nVidia GT218 [NVS 3100M]
graphics)
up to and including kernel 3.7-rc4. However, with 3.7-rc5 or -rc6, any attempt
to
run mplayer just
* Mel Gorman wrote:
> On Wed, Nov 21, 2012 at 10:21:06AM +, Mel Gorman wrote:
> >
> > I am not including a benchmark report in this but will be posting one
> > shortly in the "Latest numa/core release, v16" thread along with the latest
> > schednuma figures I have available.
> >
>
> Repor
From: Paolo Valente
Date: Wed, 21 Nov 2012 10:45:14 +0100
> Got it. Actually, if the first qfq_peek_skb returns NULL, then the
> example version that you are proposing apparently may behave in a
> different way than the original one: in your proposal the scheduler
> tries to switch to a new aggre
On Wed 21-11-12 13:44:05, Dave Chinner wrote:
> On Wed, Nov 21, 2012 at 02:48:51AM +0100, Jan Kara wrote:
> >
> > diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> > index 51ea267..3e3422f 100644
> > --- a/fs/fs-writeback.c
> > +++ b/fs/fs-writeback.c
> > @@ -228,6 +228,8 @@ static void requeue
* Linus Torvalds wrote:
> On Mon, Nov 19, 2012 at 11:06 PM, Ingo Molnar wrote:
> >
> > Oh, finally a clue: you seem to have vsyscall emulation
> > overhead!
>
> Ingo, stop it already!
>
> This is *exactly* the kind of "blame everybody else than
> yourself" behavior that I was talking about e
On 11/20/2012 11:16 PM, Yinghai Lu wrote:
diff --git a/Documentation/x86/boot.txt b/Documentation/x86/boot.txt
index 9efceff..a8263f7 100644
--- a/Documentation/x86/boot.txt
+++ b/Documentation/x86/boot.txt
@@ -57,6 +57,9 @@ Protocol 2.10:(Kernel 2.6.31) Added a protocol for
relaxed ali
On Wed, Nov 21, 2012 at 06:03:06PM +0100, Ingo Molnar wrote:
>
> * Mel Gorman wrote:
>
> > On Wed, Nov 21, 2012 at 10:21:06AM +, Mel Gorman wrote:
> > >
> > > I am not including a benchmark report in this but will be posting one
> > > shortly in the "Latest numa/core release, v16" thread al
* Ingo Molnar wrote:
> This is an entirely valid line of inquiry IMO.
Btw., what I did was to simply look at David's profile on the
regressing system and I compared it to the profile I got on a
pretty similar (but unfortunately not identical and not
regressing) system. I saw 3 differences:
On 11/20/2012 11:16 PM, Yinghai Lu wrote:
At that stage, it is already in 32bit protected mode or 64bit mode.
so we do not need to check if ptr less 1M.
When go from other boot loader (kexec) instead of boot/ code path.
Move out accessible checking out __cmdline_find_option
So misc.c will
On 11/20/2012 11:15 PM, Yinghai Lu wrote:
We are short of space before 0x200 that is entry for startup_64.
And we can not change startup_64 to other value --- ABI ?
Here you are saying "I don't understand how this works." It is YOUR
responsibility to find out and write a definite statement r
On 21/11/12 16:19, Dan Carpenter wrote:
When someone sends a patch there are a several possible responses:
1) Ack the patch.
2) Request that the submitter redo it. The downside is that no one
likes redoing patches.
3) Reject the patch.
4) Redo it yourself and say "Based on a patch from Sachi
* Sasha Levin [2012-11-13 11:18:47 -0500]:
> Hi all,
>
> While fuzzing with trinity on a KVM tools (lkvm) guest running latest -next
> kernel I've
> stumbled on the following:
>
> [ 1434.201149] [ cut here ]
> [ 1434.204998] WARNING: at lib/debugobjects.c:261
> debug_p
On Wed, Nov 21, 2012 at 08:59:24AM +, peter.hu...@infineon.com wrote:
> I just gave the new version a run on my beagleboard with our Infineon SLB9635
> TT 1.2 Soft I2C TPM
> and it seems to work as expected. (Tested with and without previous startup).
>
> Tested-by: Peter Huewe
Great, I'll
Hi Oleg,
Yes, I can see that "arch/x86/kernel/vsyscall_64.c"
has changed dramatically since I last looked at it.
Since this is the case, I no longer need to trap the vsyscall page.
Now however, that "vsyscall" was effectively replaced by vdso, it
creates a new problem for me and probably for any
* Mel Gorman wrote:
> On Wed, Nov 21, 2012 at 06:03:06PM +0100, Ingo Molnar wrote:
> >
> > * Mel Gorman wrote:
> >
> > > On Wed, Nov 21, 2012 at 10:21:06AM +, Mel Gorman wrote:
> > > >
> > > > I am not including a benchmark report in this but will be posting one
> > > > shortly in the "L
1) inet6_csk_update_pmtu() must return NULL or non-NULL, so translate
ERR_PTR to NULL, as needed. Fix from Eric Dumazet.
2) Fix copy&paste error in IRDA sir_dev ->set_speed method invocation,
it was testing the NULL'ness of a different method to guard the call.
Fix from Alexander Shiyan
Hi Jason,
>Great, I'll send an updated version, thanks!
;) You're welcome.
>> >+struct tpm_startup_in {
>> >+ __be16 startup_type;
>> >+} __packed;
>>
>>
>> All the other user
>> __attribute__((packed));
>> Care to change to be consistent?
> I used to __packed to avoid a checkpatch warning,
On 11/20/2012 04:30 PM, Darren Hart wrote:
>
>
> On 11/20/2012 03:10 PM, Darren Hart wrote:
>>
>>
>> On 11/20/2012 08:46 AM, Dave Jones wrote:
>>> On Wed, Oct 24, 2012 at 09:44:07PM -0700, Darren Hart wrote:
>>>
>>> > > I've been able to trigger this for the last week or so.
>>> > > Unclear
* Ingo Molnar wrote:
> So because I did not have an old-glibc system like David's, I
> did not know the actual page fault rate. If it is high enough
> then nonlinear effects might cause such effects.
>
> This is an entirely valid line of inquiry IMO.
Btw., when comparing against 'mainline' I
Hello,
I have a question regarding tagging of patches targetted in -stable
kernels. We have this 'CC: sta...@vger.kernel.org # something' tag. Now
inconvenient thing is that when I create a patch and have such tag in it,
then git-send-email will mangle the address because of the #. Now even if
On Wed, Nov 21, 2012 at 03:51:04PM +, Grant Likely wrote:
> On Wed, 21 Nov 2012 00:24:48 -0700, Jason Gunthorpe
> wrote:
> > This allows platform_device_add a chance to call insert_resource
> > on all of the resources from OF. At a minimum this fills in proc/iomem
> > and presumably makes res
On 11/21/2012 12:02 PM, Linus Torvalds wrote:
The same is true of all your arguments about Mel's numbers wrt THP
etc. Your arguments are misleading - either intentionally, of because
you yourself didn't think things through. For schednuma, it's not
enough to be par with mainline with THP off - t
On Wed, Nov 21, 2012 at 09:37:40AM -0800, Darren Hart wrote:
> I've sent a patch to address this. It has now been running "trinity -c
> futex" for about 12 hours. I haven't seen any more futex failures
Looks good here too.
> but I
> have seen a few OOMs. Is that expected from trinity?
Yeah,
Hi,
On Wed, Nov 21, 2012 at 06:44:45PM +0100, Jan Kara wrote:
> Hello,
>
> I have a question regarding tagging of patches targetted in -stable
> kernels. We have this 'CC: sta...@vger.kernel.org # something' tag. Now
> inconvenient thing is that when I create a patch and have such tag in it,
Hi Daniel,
> > As advertised, this patch breaks the Macbook Pro Retina, which seems
> > unfair. The patch below is certainly not the best remedy, but it does
> > work. Tested on a MacbookPro10,1.
>
> My apologies for the long delay in answering, I've somehow mixed up
> different bugreports and th
On Tue, 2012-11-20 at 20:10 -0800, Hugh Dickins wrote:
> On Tue, 20 Nov 2012, Rik van Riel wrote:
> > On 11/20/2012 08:54 PM, Andrew Theurer wrote:
> >
> > > I can confirm single JVM JBB is working well for me. I see a 30%
> > > improvement over autoNUMA. What I can't make sense of is some perf
On Wed, Nov 21, 2012 at 06:33:16PM +0100, Ingo Molnar wrote:
>
> * Mel Gorman wrote:
>
> > On Wed, Nov 21, 2012 at 06:03:06PM +0100, Ingo Molnar wrote:
> > >
> > > * Mel Gorman wrote:
> > >
> > > > On Wed, Nov 21, 2012 at 10:21:06AM +, Mel Gorman wrote:
> > > > >
> > > > > I am not inclu
* Linus Torvalds wrote:
> [...] And not look at vsyscalls or anything, but look at what
> schednuma does wrong!
I have started 4 independent lines of inquiry to figure out
what's wrong on David's system, and all four are in the category
of 'what does our tree do to cause a regression':
-
On 11/21/2012 12:37 AM, Minchan Kim wrote:
Hi alls,
Today, I saw below complain of lockdep.
As a matter of fact, I knew it long time ago but forgot that.
The reason lockdep complains is that now zram uses GFP_KERNEL
in reclaim path(ex, __zram_make_request) :(
I can fix it via replacing GFP_KERNE
On Wed, Nov 21, 2012 at 5:44 PM, Jason Gunthorpe
wrote:
> On Wed, Nov 21, 2012 at 03:51:04PM +, Grant Likely wrote:
>> On Wed, 21 Nov 2012 00:24:48 -0700, Jason Gunthorpe
>> wrote:
>> > This allows platform_device_add a chance to call insert_resource
>> > on all of the resources from OF. At
On Wed, Nov 21, 2012 at 06:07:46PM +, Grant Likely wrote:
> > Which is nesting the generic gpio driver under a larger region..
>
> Try two sibling nodes with overlapping addresses. There are powerpc
> device trees doing that even though it isn't legal by the ofw and
> epapr specs.
Both my ex
Adding __printf helps spot format and argument mismatches.
Signed-off-by: Joe Perches
---
drivers/net/wireless/brcm80211/brcmsmac/debug.h | 10 --
1 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/brcm80211/brcmsmac/debug.h
b/drivers/net/wireless/brcm
AS3711 is a PMIC with multiple DCDC and LDO power supplies, GPIOs, an RTC,
a battery charger and a general purpose ADC. This patch adds support for
the MFD with support for a regulator driver and a backlight driver.
Signed-off-by: Guennadi Liakhovetski
---
An as3711 backlight driver is still und
This driver supports the 4 DCDC and 8 LDO regulators on the AS3711 PMIC.
Signed-off-by: Guennadi Liakhovetski
---
drivers/regulator/as3711-regulator.c | 381 ++
1 files changed, 381 insertions(+), 0 deletions(-)
create mode 100644 drivers/regulator/as3711-regula
* Mel Gorman wrote:
> On Wed, Nov 21, 2012 at 06:33:16PM +0100, Ingo Molnar wrote:
> >
> > * Mel Gorman wrote:
> >
> > > On Wed, Nov 21, 2012 at 06:03:06PM +0100, Ingo Molnar wrote:
> > > >
> > > > * Mel Gorman wrote:
> > > >
> > > > > On Wed, Nov 21, 2012 at 10:21:06AM +, Mel Gorman w
So far CPU hotplug was ignored for mptable implementations which support it by
having the hotpluggable CPUs marked as disabled during boot.
The current kernel code detects that behaviour and actually deals with it
properly:
[0.00] Intel MultiProcessor Specification v1.4
[
This allows platform_device_add a chance to call insert_resource on all
of the resources from OF. At a minimum this fills in proc/iomem and
presumably makes resource tracking and conflict detection work better.
However, it has the side effect of moving all OF generated platform
devices from /sys/de
* Mel Gorman wrote:
> While it is desirable that all threads in a process run on its home
> node, this is not always possible or necessary. There may be more
> threads than exist within the node or the node might over-subscribed
> with unrelated processes.
>
> This can cause a situation whereby
On 11/21/2012 10:22 AM, Sasha Levin wrote:
> So far CPU hotplug was ignored for mptable implementations which support it by
> having the hotpluggable CPUs marked as disabled during boot.
>
> The current kernel code detects that behaviour and actually deals with it
> properly:
>
> [0.000
This allows you to get the equivalent functionality of
i2c_add_numbered_adapter() with all data in the device tree and no
special case code in your driver. This is a common device tree
technique.
For quick reference, the FDT syntax for using an alias to provide an
ID looks like:
aliases {
i
The commit: "i2c-core: dt: Pick i2c bus number from i2c alias if
present" adds support for automatically picking the bus number based
on the alias ID. Remove the now unnecessary code from i2c-pxa that
did the same thing.
Signed-off-by: Doug Anderson
---
drivers/i2c/busses/i2c-pxa.c |8 +
On Wed, Nov 21, 2012 at 11:58:05AM -0500, Jeff Moyer wrote:
> > I'd like to use this as a vehicle to revisit how dio completions work.
>
> I don't like the sound of that. ;-) It sounds like this bugfix may get
> further delayed by the desire for unrelated code cleanup.
I've got a prototype that
Hi Rachna,
On Wed, Nov 07, 2012 at 12:22:03PM +0530, Patil, Rachna wrote:
> Add DT support for client touchscreen driver
>
> Signed-off-by: Patil, Rachna
> ---
> drivers/input/touchscreen/ti_am335x_tsc.c | 60
> -
> 1 files changed, 50 insertions(+), 10 deletions(
On Tue, Nov 20, 2012 at 8:09 PM, Mark Brown
wrote:
> On Tue, Nov 20, 2012 at 02:27:04PM -0800, Doug Anderson wrote:
>> From: Padmavathi Venna
>>
>> Get the i2c bus number that the device is connected to using the alias
>> id. This makes debugging / grokking of kernel messages much easier.
>
> Th
Hi Rachna,
On Wed, Nov 07, 2012 at 12:22:00PM +0530, Patil, Rachna wrote:
> Only fine tuning variance parameter present in tslib
> utility does not help in removing all the ADC noise.
> This logic of filtering is necessary to get this
> touchscreen to work finely.
No, if filtering in tslib is not
On Wed, Nov 21, 2012 at 06:15:59PM +, Grant Likely wrote:
> This allows platform_device_add a chance to call insert_resource on all
> of the resources from OF. At a minimum this fills in proc/iomem and
> presumably makes resource tracking and conflict detection work better.
> However, it has th
On 11/21/2012 01:25 PM, H. Peter Anvin wrote:
> On 11/21/2012 10:22 AM, Sasha Levin wrote:
>> So far CPU hotplug was ignored for mptable implementations which support it
>> by
>> having the hotpluggable CPUs marked as disabled during boot.
>>
>> The current kernel code detects that behaviour and a
The TPM will respond to TPM_GET_CAP with TPM_ERR_INVALID_POSTINIT if
TPM_STARTUP has not been issued. Detect this and automatically
issue TPM_STARTUP.
This is for embedded applications where the kernel is the first thing
to touch the TPM.
Signed-off-by: Jason Gunthorpe
Tested-by: Peter Huewe
Re
On 11/21/2012 10:35 AM, Sasha Levin wrote:
>>
>> Reading between the lines, this sounds like would cause a user-visible
>> difference between mptable platforms and ACPI platforms? If so, that is
>> totally unacceptable. If not, the description is confusing.
>
> With ACPI platforms you don't need
dabusb was removed with commit dae86ccbc3c185aebfc396e8e668aa3d73d748d8
'[media] dabusb: remove obsolete driver', so remove the last vestiges of
firmware and documentation.
Cc: Rob Landley
Cc: Paul Gortmaker
Cc: Andrew Morton
Cc: Ben Hutchings
Cc: Greg Kroah-Hartman
Cc: linux-...@vger.kernel.
Christoph Hellwig writes:
> On Wed, Nov 21, 2012 at 11:58:05AM -0500, Jeff Moyer wrote:
>> > I'd like to use this as a vehicle to revisit how dio completions work.
>>
>> I don't like the sound of that. ;-) It sounds like this bugfix may get
>> further delayed by the desire for unrelated code c
Andrew Morton writes:
>
> On Tue, 20 Nov 2012 10:46:11 + Grant Likely
> wrote:
>
> > On Sat, Nov 17, 2012 at 12:19 AM, Bill Pemberton wrote:
> > > CONFIG_HOTPLUG is no longer an optional setting. In order to remove
> > > it as on option code paths that check CONFIG_HOTPLUG will removed
>
Hi Lee,
On Wed, Nov 14, 2012 at 01:47:14PM +, Lee Jones wrote:
> @@ -272,6 +276,60 @@ static irqreturn_t bu21013_gpio_irq(int irq, void
> *device_data)
> }
>
> /**
> + * bu21013_gpio_board_init() - configures the touch panel
> + * @reset_pin: reset pin number
> + *
> + * This function is
301 - 400 of 473 matches
Mail list logo
