> -Original Message-
> From: iommu-boun...@lists.linux-foundation.org [mailto:iommu-
> boun...@lists.linux-foundation.org] On Behalf Of Thierry Reding
> Sent: Friday, June 27, 2014 2:20 AM
> To: Rob Herring; Pawel Moll; Mark Rutland; Ian Campbell; Kumar Gala;
> Stephen Warren; Arnd Bergma
Hi Will,
On Thu, Jul 3, 2014 at 2:14 AM, Will Deacon wrote:
> Hello,
>
> On Wed, Jul 02, 2014 at 06:20:24AM +0100, Zi Shen Lim wrote:
[...]
>
> First off, this is really cool. Thanks for putting in the effort to get this
> supported on arm64! I'm happy to run tests on some real hardware if you te
This bug can be trigger by L1 goes down directly w/ enable_shadow_vmcs.
[ 6413.158950] kvm: vmptrld (null)/7800 failed
[ 6413.158954] vmwrite error: reg 401e value 4 (err 1)
[ 6413.158957] CPU: 0 PID: 4840 Comm: qemu-system-x86 Tainted: G OE
3.16.0kvm+ #2
[ 6413.158958
On 02.07.2014 14:16, Borislav Petkov wrote:
On Tue, Jun 24, 2014 at 01:41:34PM +0200, Tomasz Nowicki wrote:
Currently APEI depends on x86 architecture. It is because of NMI hardware
error notification of GHES which is currently supported by x86 only.
However, many other APEI features can be stil
Hi,
Please drop this patch which generating an another warning.
I will send v2 for this.
Thanks.
On 07/04/2014 12:07 PM, Varka Bhadram wrote:
This patch eliminates the following warning
drivers/gpio/gpio-sch311x.c: In function ‘sch311x_gpio_probe’:
drivers/gpio/gpio-sch311x.c:286:18: warning
* Pavel Machek [140630 13:34]:
> Hi!
>
> > The non-DT support has to be maintained for now to not break
> > OMAP3 legacy boot, and the legacy-style code will be cleaned
> > up once OMAP3 is also converted to DT-boot only.
> > >>>
> > @@ -587,24 +606,157 @@ static int omap_mbox
Hi all,
Changes since 20140703:
My fixes tree contains:
powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64
The net tree gained a build failure for which I reverted a commit.
The usb-gadget tree gained a conflict against the usb.current tree.
The staging tree still had its build
Original 'pci.h' is empty, and some modules in allmodconfig may need
contents which can be found in generic 'pci.h', so use generic one
instead of original.
The related error (allmodconfig under score):
CC [M] drivers/scsi/scsi_lib.o
drivers/scsi/scsi_lib.c: In function 'scsi_calculate_bou
Hi Gleb,
On 07/03/2014 02:04 PM, Gleb Natapov wrote:
On Thu, Jul 03, 2014 at 09:17:59AM +0800, Tang Chen wrote:
Hi Gleb,
On 07/02/2014 05:00 PM, Tang Chen wrote:
Hi Gleb, Marcelo,
Please help to review this patch-set.
NOTE: This patch-set doesn't work properly.
ept identity pagetable and
Hello,
On Thu, Jul 03, 2014 at 06:01:00PM +0200, Martin Schwidefsky wrote:
> On Thu, 3 Jul 2014 17:37:29 +0900
> Minchan Kim wrote:
>
> > Hello,
> >
> > On Thu, Jul 03, 2014 at 10:29:01AM +0200, Martin Schwidefsky wrote:
> > > On Thu, 3 Jul 2014 16:29:54 +0900
> > > Minchan Kim wrote:
> > >
>
This patch eliminates the following warning
drivers/gpio/gpio-sch311x.c: In function ‘sch311x_gpio_probe’:
drivers/gpio/gpio-sch311x.c:286:18: warning: ignoring return value of
‘gpiochip_remove’, declared with attribute warn_unused_result
Signed-off-by: Varka Bhadram
---
drivers/gpio/gpio-sch3
* Felipe Balbi [140703 10:10]:
> On Thu, Jul 03, 2014 at 06:19:47PM +0200, Javier Martinez Canillas wrote:
> > On Thu, Jul 3, 2014 at 6:06 PM, Sebastian Reichel wrote:
> > > Hi,
> > >
> > > On Thu, Jul 03, 2014 at 10:52:40AM -0500, Felipe Balbi wrote:
> > >> > DT is supposed to contain informatio
On 07/03/2014 10:32 PM, Joe Lawrence wrote:
On Thu, Jul 3 2014 Joe Julian wrote:
I have a knox enclosure with an unresponsive drive. When the mpt2sas
module is loaded the module loading process hangs. modprobe/insmod is
stuck and any further attempts to load modules also hang. By
blacklisting
Hi Tejun,
On 2014/6/28 9:03, Tejun Heo wrote:
> Hello, guys.
>
> Currently, the blkio subsystem attributes all of writeback IOs to the
> root. One of the issues is that there's no way to tell who originated
> a writeback IO from block layer. Those IOs are usually issued
> asynchronously from a
The layer which registers with the crypto API should check for the presence of
the CAAM device it is going to use. If the platform's device tree doesn't have
the required CAAM node, the layer should return an error and not register the
algorithms with crypto API layer.
Signed-off-by: Ruchika Gupt
On Fri, Jul 4, 2014 at 6:30 AM, Greg KH wrote:
> The following changes since commit 4c834452aad01531db949414f94f817a86348d59:
>
> Linux 3.16-rc3 (2014-06-29 14:11:36 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/
>
On Fri, 4 Jul 2014, Nick Krause wrote:
> What are these two lines for them another compile issue?
I don't see why those two lines are important.
> >> -/* FIXME - when we get this compiling */
> >> /* erm, now that it's compiling, what do we do with it? */
> >> #define _KERNPG_TABLE 0
Presuma
On 07/03/2014 07:31 PM, Robert Jarzmik wrote:
Daniel Lezcano writes:
-#include
#include
+#include
Now as the driver is in 'drivers', do not reference the headers files in
mach. Moving the driver to the drivers directory implies some cleanup with the
headers dependencies.
I don't see t
On Thu, Jul 03, 2014 at 01:15:26AM -0400, Bandan Das wrote:
>Jan Kiszka writes:
>
>> On 2014-07-02 08:54, Wanpeng Li wrote:
>>> This patch fix bug https://bugzilla.kernel.org/show_bug.cgi?id=72381
>>>
>>> If we didn't inject a still-pending event to L1 since nested_run_pending,
>>> KVM_REQ_EVENT
Hi Bjorn,
On Tue, Jun 17, 2014 at 12:16 AM, Bjorn Andersson
wrote:
> Driver for the Resource Power Manager (RPM) found in Qualcomm 8660, 8960
> and 8064 based devices. The driver exposes resources that child drivers
> can operate on; to implementing regulator, clock and bus frequency
> drivers.
>
On Thu, Jul 03, 2014 at 06:54:50PM -0700, Jason Low wrote:
> On Thu, 2014-07-03 at 18:46 -0700, Jason Low wrote:
> > On Fri, 2014-07-04 at 11:01 +1000, Dave Chinner wrote:
>
> > > FWIW, the rwsems in the struct xfs_inode are often heavily
> > > read/write contended, so there are lots of IO related
>>> On 04.07.14 at 01:11, wrote:
> From: Greg Kroah-Hartman
>
> Jan points out that I forgot to make the needed fixes to the
> lz4_uncompress_unknownoutputsize() function to mirror the changes done
> in lz4_decompress() with regards to potential pointer overflows.
Except that meanwhile Don agre
Hi Bjorn,
-Original Message-
From: "Bjorn Andersson"
Sent: Tuesday, 17 June, 2014 12:16am
To: "Rob Herring" , "Mark Rutland" ,
"Liam Girdwood" , "Mark Brown" ,
"Kumar Gala"
Cc: "Lee Jones" , "Josh Cartwright"
, devicet...@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-ker.
On Jul 3, 2014, at 10:59 PM, Maxime Ripard
wrote:
> On Thu, Jul 03, 2014 at 10:39:08PM +0800, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
>>> +++ b/drivers/power/reset/at91-reset.c
>>> @@ -0,0 +1,202 @@
>>> +/*
>>> + * Atmel AT91 SAM9 SoCs reset code
>>> + *
>>> + * Copyright (C) 2014 Maxime Rip
On Fri, Jul 04, 2014 at 07:43:14AM +0200, Jan Kiszka wrote:
>On 2014-07-04 04:52, Wanpeng Li wrote:
>> On Thu, Jul 03, 2014 at 01:27:05PM -0400, Bandan Das wrote:
>> [...]
>>> # modprobe kvm_intel ept=0 nested=1 enable_shadow_vmcs=0
>>>
>>> The Host CPU - Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
>>>
-/* FIXME - when we get this compiling */
> /* erm, now that it's compiling, what do we do with it? */
What are these two lines for them another compile issue?
Cheers Nick
On Thu, Jul 3, 2014 at 9:28 PM, Finn Thain wrote:
>
> On Wed, 2 Jul 2014, Nicholas Krause wrote:
>
>> Removes a FIXME commen
On Thu, 2014-07-03 at 22:05 -0700, Paul E. McKenney wrote:
> On Fri, Jul 04, 2014 at 05:23:56AM +0200, Mike Galbraith wrote:
> > Turn it on and don't worry about it is exactly what distros want the
> > obscure feature with very few users to be. Last time I did a drive-by,
> > my boxen said I sho
Hi Andrejz,
On Thu, Jul 3, 2014 at 5:23 PM, Andrzej Hajda wrote:
>
> Hi Alexandre,
>
> Thanks for the patch.
>
> On 07/02/2014 02:19 PM, Alexandre Courbot wrote:
>> As per section 5.6.1 of the DSI specification, all DSI transmitters must
>> support continuous clock behavior on the clock lane, whi
At Wed, 2 Jul 2014 09:55:05 -0700,
Luis R. Rodriguez wrote:
>
> From: "Luis R. Rodriguez"
>
> Now that the udev firmware loader is optional request_firmware()
> will not provide any information on the kernel ring buffer if
> direct firmware loading failed and udev firmware loading is disabled.
On Jul 3, 2014, at 10:59 PM, Maxime Ripard
wrote:
> On Thu, Jul 03, 2014 at 10:39:08PM +0800, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
>>> +++ b/drivers/power/reset/at91-reset.c
>>> @@ -0,0 +1,202 @@
>>> +/*
>>> + * Atmel AT91 SAM9 SoCs reset code
>>> + *
>>> + * Copyright (C) 2014 Maxime Rip
On 2014-07-04 05:27, Hu Yaohui wrote:
> Hi All,
> Is direct device assignment in nested VM supported in the latest KVM
> mainline now?
Le Tan is currently working on emulated device assignment (VT-d
emulation in QEMU). This is the necessary first step and could later be
extended to enable assignme
Chen-san,
I would like to recommend that you summarize pros/cons for all ideas so far.
For example,
-
A) make new system call for transrate
A-1) systemcall(ID, NS1, NS2) into (ID).
pros:
- foo
- baa
cons:
- hoge
- hogehogehoge
A-2) pi
On 2014-07-04 04:52, Wanpeng Li wrote:
> On Thu, Jul 03, 2014 at 01:27:05PM -0400, Bandan Das wrote:
> [...]
>> # modprobe kvm_intel ept=0 nested=1 enable_shadow_vmcs=0
>>
>> The Host CPU - Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
>> qemu cmd to run L1 -
>> # qemu-system-x86_64 -drive
>> file=leve
From: Pramod Gurav
Fixes below warning while compiling the kernel.
fs/direct-io.c: In function ‘__blockdev_direct_IO’:
fs/direct-io.c:1011:12: warning: ‘to’ may be used uninitialized in this
function [-Wmaybe-uninitialized]
fs/direct-io.c:913:16: note: ‘to’ was declared here
fs/direct-io.c:1011
At Thu, 3 Jul 2014 13:02:52 +0100,
Mark Brown wrote:
>
> On Thu, Jul 03, 2014 at 03:08:08PM +0530, Vinod Koul wrote:
>
> > Yes makes sense to go thru ASoC tree. Mark can you keep this in immutable
> > branch, which I can merge to my tree for any future fixes...
>
> Fine by me - Takashi?
Sure, p
On Thu, Jul 3 2014 Joe Julian wrote:
> I have a knox enclosure with an unresponsive drive. When the mpt2sas
> module is loaded the module loading process hangs. modprobe/insmod is
> stuck and any further attempts to load modules also hang. By
> blacklisting the module and loading it last, I can
(2014/07/04 2:01), Oleg Nesterov wrote:
> On 07/03, Oleg Nesterov wrote:
>>
>> Hmm. Off-topic, but it seems that instance_rmdir() leaks the memory? Say,
>> file->filter?
>
> Perhaps I am totally confused, but don't we need something like the patch
> below? I'll try to recheck later...
>
> Better
On Wed, Jun 25, 2014 at 10:08 PM, Peter Zijlstra wrote:
> On Wed, Jun 25, 2014 at 10:23:21AM -0600, Stephen Warren wrote:
>> On 06/25/2014 04:19 AM, Peter Zijlstra wrote:
>> > On Wed, Jun 25, 2014 at 03:24:11PM +0530, Srivatsa S. Bhat wrote:
>> >> Wait, that was a stupid idea. hotplug_cfd() alread
On Fri, Jul 04, 2014 at 05:23:56AM +0200, Mike Galbraith wrote:
> On Thu, 2014-07-03 at 09:29 -0700, Paul E. McKenney wrote:
> > On Thu, Jul 03, 2014 at 07:48:40AM +0200, Mike Galbraith wrote:
> > > On Wed, 2014-07-02 at 22:21 -0700, Paul E. McKenney wrote:
> > > > On Thu, Jul 03, 2014 at 05:31:1
Hi Suman,
On Thu, Jul 3, 2014 at 8:28 PM, Suman Anna wrote:
> OK, but we would still require this function to lookup the registered
> device from the controller-phandle to retrieve the base_id.
Can we retrieve the base_id from the parent DT node itself?
Thanks,
Ohad.
--
To unsubscribe from this
Hi Suman,
On Thu, Jul 3, 2014 at 8:35 PM, Suman Anna wrote:
> Not at the moment, with the existing platform implementations. So, if I
> understand you correctly, you are asking to leave out the xlate ops and
> make the of_hwspin_lock_simple_xlate() internal until a need for an
> xlate method aris
Hi Felipe,
Today's linux-next merge of the usb-gadget tree got a conflict in
drivers/usb/musb/musb_cppi41.c between commit c58d80f523ff ("usb: musb:
Ensure that cppi41 timer gets armed on premature DMA TX irq") from the
usb.current tree and commit 50aea6fca771 ("usb: musb: cppi41: fire
hrtimer acc
(2014/07/04 1:22), Oleg Nesterov wrote:
>> One possible scenario is here; someone disables an event and tries to remove
>> it (both will be done by different syscalls). If we don't synchronize
>> the first disabling, the event flag set disabled, but the event itself
>> is not disabled. Thus event
On Thu, 2014-07-03 at 16:08 -0700, Austin Schuh wrote:
> On Tue, Jul 1, 2014 at 12:32 PM, Austin Schuh wrote:
> > On Mon, Jun 30, 2014 at 8:01 PM, Austin Schuh
> > wrote:
> >> On Fri, Jun 27, 2014 at 7:24 AM, Thomas Gleixner
> >> wrote:
> >>> Completely untested patch below.
>
> I've tested
Hi Nick,
On Fri, Jul 4, 2014 at 2:07 AM, Nick Krause wrote:
> Very well then I will read the documentation on Kconfig in order to
> understand that and fix up my patches for that.
> On the other hand I will send a email before the patches to tell in
> what order to apply them.
As already asked b
While searching for FIX ME messages when using cscope on the latest kernels I
get a message on 68 of this file and was wondering what I need to define SMFRAM
as in order for it to point to things needed to support this portion
of the hardware.
Cheers Nick
--
To unsubscribe from this list: send the
On 4 July 2014 03:46, Mike Turquette wrote:
> Sorry for being dense, but I still do not get why trying to dynamically
> discover a shared rate-changeable clock is a better approach than simply
> describing the hardware in DT?
>
> Is adding a property to the CPU binding that describes how the CPUs
From: Viresh Kumar
Currently, the ->set_mode() method of a clockevent device is not
allowed to fail, so it has no return value. In order to add new
clockevent modes, and allow the setting of those modes to fail, we
need the clockevent core to be able to detect when setting a mode
fails.
To allo
Currently, the ->set_mode() method of a clockevent device is not
allowed to fail, so it has no return value. In order to add new
clockevent modes, and allow the setting of those modes to fail, we
need the clockevent core to be able to detect when setting a mode
fails.
Rather than changing the cur
From: Viresh Kumar
Clockevents core now supports ->set_dev_mode() (as a replacement to
->set_mode()), with capability to return error codes.
This patch migrates few clockevent drivers to the new method to demonstrate how
to convert to the new interface.
Drivers are modified to return -ENOSYS wh
From: Steven Rostedt
Date: Thu, 3 Jul 2014 12:41:46 -0400
> Do you have any problem with this patch going through my tree? It
> compiles, but I do not have any hardware to test it. If you can verify
> that this patch works and ack it, it would be much appreciated.
>
> This code is at:
>
> git:
On Fri, 2014-07-04 at 09:15 +0530, Sachin Kamat wrote:
> In any case, if this patch is going to be appled, please fix typo in subject
>
> s/Samsunt/Samsung
I think Sangboem is going to submit something appropriate
instead.
--
To unsubscribe from this list: send the line "unsubscribe linux-kerne
Hi Tejun,
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git review-mq-percpu_ref
commit c924ec35e72ce0d6c289b858d323f7eb3f5076a5 ("block, blk-mq: draining can't
be skipped even if bypass_depth was non-zero")
+-
Hi all,
Sorry please ignore this report: it seems there are no obvious
relationship between the code change and the regression.
Thanks,
Fengguang
On Fri, Jul 04, 2014 at 11:45:31AM +0800, Jet Chen wrote:
> Hi Aaron,
>
> FYI, we noticed the below changes on
>
> commit ed235875e2ca983197831337a9
On Fri, Jul 4, 2014 at 5:23 AM, Sangbeom Kim wrote:
> On Friday, July 04, 2014 7:08 AM, Joe Perches wrote:
>
>> F: drivers/regulator/s2m*.c
>> F: drivers/regulator/s5m*.c
>> -F: drivers/rtc/rtc-sec.c
>> F: include/linux/mfd/samsung/
>>
>
> Yes, You are right.
> There is no rtc-sec.c
> I
Hi Aaron,
FYI, we noticed the below changes on
commit ed235875e2ca983197831337a986f0517074e1a0 ("kernel/watchdog.c: print
traces for all cpus on lockup detection")
test case: lkp-snb01/will-it-scale/signal1
f3aca3d09525f87 ed235875e2ca983197831337a
--- -
Am Freitag, 4. Juli 2014, 11:12:35 schrieb Herbert Xu:
Hi Herbert,
> On Tue, Jul 01, 2014 at 05:08:48PM +0200, Stephan Mueller wrote:
> > For the CTR DRBG, the drbg_state->scratchpad temp buffer (i.e. the
> > memory location immediately before the drbg_state->tfm variable
> > is the buffer that t
Am Freitag, 4. Juli 2014, 11:08:10 schrieb Herbert Xu:
Hi Herbert,
> On Tue, Jul 01, 2014 at 05:08:48PM +0200, Stephan Mueller wrote:
> > For the CTR DRBG, the drbg_state->scratchpad temp buffer (i.e. the
> > memory location immediately before the drbg_state->tfm variable
> > is the buffer that t
Hi All,
Is direct device assignment in nested VM supported in the latest KVM
mainline now?
Thanks,
Yaohui
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.h
This patch fixed spelling typo in various template files
within Documentation/Docbook.
Signed-off-by: Masanari Iida
---
Documentation/DocBook/gadget.tmpl | 2 +-
Documentation/DocBook/genericirq.tmpl | 4 ++--
Documentation/DocBook/kernel-locking.tmpl | 2 +-
On Thu, 2014-07-03 at 09:29 -0700, Paul E. McKenney wrote:
> On Thu, Jul 03, 2014 at 07:48:40AM +0200, Mike Galbraith wrote:
> > On Wed, 2014-07-02 at 22:21 -0700, Paul E. McKenney wrote:
> > > On Thu, Jul 03, 2014 at 05:31:19AM +0200, Mike Galbraith wrote:
> >
> > > > NO_HZ_FULL is a property o
> IF you've turned on debugging options, then you've already lost more
> performance that careful packing of the dentry slab cache gains you.
> There's no point in carefully tuning DNAME_INLINE_LEN for debug
> options - it's just code that will break and annoy people as debug
> implementations chan
On Tue, Jul 01, 2014 at 05:08:48PM +0200, Stephan Mueller wrote:
> For the CTR DRBG, the drbg_state->scratchpad temp buffer (i.e. the
> memory location immediately before the drbg_state->tfm variable
> is the buffer that the BCC function operates on. BCC operates
> blockwise. Making the temp buffer
Please drop this wrong post and see V2.
Thanks,
Ethan
On 2014/7/4 22:48, Ethan Zhao wrote:
netxen driver has implemented netxen_nic_get_ethtool_stats() interface,
but doesn't collect stats.rxdropped in driver, so we will get
different statistic information while using ifconfig and ethtool.
this
On Tue, Jul 01, 2014 at 05:08:48PM +0200, Stephan Mueller wrote:
> For the CTR DRBG, the drbg_state->scratchpad temp buffer (i.e. the
> memory location immediately before the drbg_state->tfm variable
> is the buffer that the BCC function operates on. BCC operates
> blockwise. Making the temp buffer
> -Original Message-
> From: Neil Zhang
> Sent: 2014年5月14日 15:52
> To: Neil Zhang; linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.org
> Cc: rmk+ker...@arm.linux.org.uk
> Subject: RE: [PATCH] ARM: remove redundant code in machine_halt
>
> > -Original Message-
> > F
This commit:
commit 6f6343f53d133bae516caf3d254bce37d8774625
Author: Masami Hiramatsu
Date: Thu Apr 17 17:17:33 2014 +0900
kprobes/x86: Call exception handlers directly from do_int3/do_debug
Trying to dereference addr when addr is user-controlled is
completely bogus.
Sign
On Thu, Jul 03, 2014 at 01:27:05PM -0400, Bandan Das wrote:
[...]
># modprobe kvm_intel ept=0 nested=1 enable_shadow_vmcs=0
>
>The Host CPU - Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
>qemu cmd to run L1 -
># qemu-system-x86_64 -drive
>file=level1.img,if=virtio,id=disk0,format=raw,cache=none,werror
On Thu, Jul 3, 2014 at 4:39 AM, Ian Abbott wrote:
> On 2014-07-03 03:15, Chase Southwood wrote:
>>
>> This patchset moves a misplaced include to the proper file, swaps out an
>> overly
>> aggressive placement of apci1564_reset(), and cleans up
>> apci1564_interrupt().
>>
>> Chase Southwood (3):
>>
On Fri, 2014-07-04 at 09:33 +0800, Barry Song wrote:
> >> -Original Message-
> >> From: Joe Perches [mailto:j...@perches.com]
> >> Sent: Friday, July 04, 2014 6:08 AM
[]
> >> commit 7bf21bc81f28 ("clk: sirf: re-arch to make the codes support both
> >> prima2 and atlas6") moved the files, up
Hi,
just use the MMC_CAP2_SDIO_IRQ_NOTHREAD?
if (!err && host->sdio_irq && !(host->quirks & MMC_CAP2_SDIO_IRQ_NOTHREAD))
wake_up_process(host->sdio_irq_thread);
I didn't test this..but i believe that it will be fixed.
Best Regards,
Jaehoon Chung
On 07/04/2014 12:47 AM, Fu, Zhonghui wro
Hi Gleb,
On 07/03/2014 12:34 AM, Gleb Natapov wrote:
On Wed, Jul 02, 2014 at 05:00:36PM +0800, Tang Chen wrote:
ept identity pagetable is pinned in memory, and as a result it cannot be
migrated/hot-removed.
But actually it doesn't need to be pinned in memory.
This patch introduces a new vcpu
The code has a variable to change the polarity of the PWM backlight control but
it was not being initialized. This patch adds a devicetree entry to set the
variable if required.
Signed-off-by: Michael Welling
---
.../devicetree/bindings/video/atmel,lcdc.txt |1 +
drivers/video/fbdev/at
Hi Gleb,
Thanks for the advices. Please see below.
On 07/03/2014 09:55 PM, Gleb Natapov wrote:
..
@@ -575,6 +575,7 @@ struct kvm_arch {
unsigned int tss_addr;
struct page *apic_access_page;
+ bool apic_access_page_migrated;
Better have two requests KVM_REQ_APIC_PAGE_
Hi Gleb,
Thanks for the advices. Please see below.
On 07/03/2014 09:55 PM, Gleb Natapov wrote:
..
@@ -575,6 +575,7 @@ struct kvm_arch {
unsigned int tss_addr;
struct page *apic_access_page;
+ bool apic_access_page_migrated;
Better have two requests KVM_REQ_APIC_PAGE_
2014-07-03 7:35 GMT+08:00 Colin King :
> From: Colin Ian King
>
> Smatch detected two memory leaks on saved_ec:
>
> drivers/acpi/ec.c:1070 acpi_ec_ecdt_probe() warn: possible
> memory leak of 'saved_ec'
> drivers/acpi/ec.c:1109 acpi_ec_ecdt_probe() warn: possible
> memory leak of 'saved_ec'
>
On Thu, 2014-07-03 at 18:46 -0700, Jason Low wrote:
> On Fri, 2014-07-04 at 11:01 +1000, Dave Chinner wrote:
> > FWIW, the rwsems in the struct xfs_inode are often heavily
> > read/write contended, so there are lots of IO related workloads that
> > are going to regress on XFS without this optimisa
On Fri, 2014-07-04 at 11:01 +1000, Dave Chinner wrote:
> [re-added lkml]
>
> On Thu, Jul 03, 2014 at 11:50:20AM -0700, Jason Low wrote:
> > On Wed, Jul 2, 2014 at 7:32 PM, Dave Chinner wrote:
> > > This is what the kernel profile looks like on the strided run:
> > >
> > > - 83.06% [kernel] [k]
On Fri, Jul 04, 2014 at 11:16:39AM +1000, Dave Chinner wrote:
> On Thu, Jul 03, 2014 at 05:52:12PM -0400, Naoya Horiguchi wrote:
> > We need the pagecache tags to be exported to userspace later in this
> > series for fincore(2), so this patch moves the definition to the new
> > include file for pre
We calculate difference between two readings of a clock to see how
much time has elapsed. Part of the time between rq_clock(rq) -
dl_se->deadline can indeed be accounted for by reading a different
clock
(i.e., rq_clock_task()) if the task was running during the period.
And that is how dl_se->runti
Hi all,
After merging the net tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "phy_resume" [drivers/net/ethernet/stmicro/stmmac/stmmac.ko] undefined!
Caused by commit 0acf16768740 ("net: stmmac: add platform init/exit for
Altera's ARM socfpga").
I reverted that com
>> -Original Message-
>> From: Joe Perches [mailto:j...@perches.com]
>> Sent: Friday, July 04, 2014 6:08 AM
>> To: Andrew Morton
>> Cc: Barry Song; linux-kernel@vger.kernel.org
>> Subject: [PATCH 04/16] MAINTAINERS: Update clk/sirf patterns
>>
>> commit 7bf21bc81f28 ("clk: sirf: re-arch to
On Thu, Jul 03, 2014 at 12:53:01PM -0700, Andi Kleen wrote:
> Rasmus Villemoes writes:
>
> > In dcache.h, DNAME_INLINE_LEN is carefully chosen so that sizeof(struct
> > dentry) is a (specific) multiple of 64 bytes. Obviously this breaks when
> > certain debug options are chosen (DEBUG_LOCK_ALLOC
On Wed, 2 Jul 2014, Nicholas Krause wrote:
> Removes a FIXME comment in this file due to it not compiling as it now
> compiles.
What got fixed?
It doesn't say "FIXME - this doesn't compile".
>
> Signed-off-by: Nicholas Krause
> ---
> arch/m68k/include/asm/sun3_pgalloc.h | 1 -
> 1 file cha
In __rtc_set_alarm(), the error after __rtc_read_time() is not checked.
If rtc device fail to read time, we cannot guarantee the following process.
Add the verification code for returned __rtc_read_time() error.
Signed-off-by: Hyogi Gim
---
drivers/rtc/interface.c | 2 ++
1 file changed, 2 inse
On Thu, Jul 03, 2014 at 05:52:12PM -0400, Naoya Horiguchi wrote:
> We need the pagecache tags to be exported to userspace later in this
> series for fincore(2), so this patch moves the definition to the new
> include file for preparation. We also use the number of pagecache tags,
> so this patch al
The Tegra USB complex has a particularly annoying misdesign: some of the
UTMI pad configuration registers are global for all the 3 USB controllers
on the chip, but those registers are located in the first controller's
register space and will be cleared when the reset to the first
controller is asse
Hi all,
Here's a second version of the probe order issue series. This time I've
added the USB1 resets to the PHYs, thus replacing the really ugly parts
with something slightly better. Old device trees will still probe
successfully, but instead of this bugfix they'll get a dev_warn().
The reset co
tegra_usb_phy_close() is supposed to undo the effects of
tegra_usb_phy_init(). It is also currently added as the USB PHY shutdown
callback, which is wrong, since tegra_usb_phy_init() is only called
during probing wheras the shutdown callback can get called multiple
times. This then leads to warning
When Tegra was converted to use the standard reset bindings, the PHY was
forgotten, probably because all the resetting of the USB blocks were
done in the EHCI driver. What also went unnoticed is that resetting the
1st on-chip USB module also wipes some of the UTMI pad configuration
registers that a
Add new properties to all of the Tegra PHYs that are now required
according to the binding.
In order to stay compatible with old device trees, the USB drivers
will still function without these reset properties but with the old,
potentially buggy behaviour.
Signed-off-by: Tuomas Tynkkynen
---
v2
On Thu, 2014-07-03 at 16:35 -0400, Waiman Long wrote:
> I do see a point in reducing the size of the rwsem structure. However, I
> don't quite understand the point of converting pointers in the
> optimistic_spin_queue structure to atomic_t. The structure is cacheline
> aligned and there is no s
[re-added lkml]
On Thu, Jul 03, 2014 at 11:50:20AM -0700, Jason Low wrote:
> On Wed, Jul 2, 2014 at 7:32 PM, Dave Chinner wrote:
> > This is what the kernel profile looks like on the strided run:
> >
> > - 83.06% [kernel] [k] osq_lock
> >- osq_lock
> > - 100.00% rwsem_down_write_fail
(2014/07/03 16:44), Namhyung Kim wrote:
> Hi Masami,
>
> On Thu, 03 Jul 2014 14:46:09 +0900, Masami Hiramatsu wrote:
>> One possible scenario is here; someone disables an event and tries to remove
>> it (both will be done by different syscalls). If we don't synchronize
>> the first disabling, the
The following changes since commit a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee:
Linux 3.16-rc2 (2014-06-21 19:02:54 -1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/
tags/usb-3.16-rc4
for you to fetch changes up to e4adcff09ca39ecbcc4
The following changes since commit a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee:
Linux 3.16-rc2 (2014-06-21 19:02:54 -1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/
tags/staging-3.16-rc4
for you to fetch changes up to 6b64168de84
The following changes since commit 4c834452aad01531db949414f94f817a86348d59:
Linux 3.16-rc3 (2014-06-29 14:11:36 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/
tags/driver-core-3.16-rc4
for you to fetch changes up to 4a3
(2014/07/03 22:21), Steven Rostedt wrote:
> Fengguang Wu's build bot detected that if moduleloader.h is included in
> a C file (used by ftrace and kprobes to access module_alloc() when
> available), that it can fail to build if CONFIG_MODULES and
> CONFIG_MODULES_USE_ELF_REL is not defined.
>
> Th
Whenever files are added, moved, or deleted, the
MAINTAINERS file patterns can be out of sync or
outdated.
To try to keep MAINTAINERS more up-to-date, add a
one-time warning whenever a patch does any of those.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 13 -
1 file chang
Good day,
We are Christian loan organization, we help people financially for a loan,
if interested, please contact us at marieloanlend...@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo in
1 - 100 of 1003 matches
Mail list logo
