Hi,
On Wed, Apr 30, 2014 at 12:43:49PM +0800, Xiubo Li wrote:
[...]
> diff --git a/drivers/base/regmap/regmap.c b/drivers/base/regmap/regmap.c
> index 8e8cea1..946e901 100644
> --- a/drivers/base/regmap/regmap.c
> +++ b/drivers/base/regmap/regmap.c
> @@ -15,6 +15,7 @@
> #include
> #include
>
Hello,
Found these in dmesg:
[344307.090007] r8169 :01:00.0 eth0: Rx ERROR. status = 342ac0ea
[344630.822919] r8169 :01:00.0 eth0: Rx ERROR. status = 342ac09d
[345763.949918] r8169 :01:00.0 eth0: Rx ERROR. status = 342cc16e
[347773.266930] r8169 :01:00.0 eth0: Rx ERROR. status = 3
On 18.04.14 20:53:23, Myron Stowe wrote:
> From: Suravee Suthikulpanit
> - start = reg & 0xff00; /* 39:16 on 31:8*/
> - start <<= 8;
> - reg = read_pci_config(bus, slot, 1, 0x84 + (i << 3));
> + start = (reg & 0xff00UL) << 8; /* 39:16 o
At Tue, 29 Apr 2014 14:04:15 -0400,
Bryan Quigley wrote:
>
> I pastebined the full boots syslog here: http://pastebin.ubuntu.com/7360925/
>
> The only kernel error I get is that pulseaudio hangs.. Nothing more
> specific as to why.
> I can also get a hang if I just run: sudo lsusb -v. It display
On Tuesday, April 29, 2014 11:48 PM, Catalin Marinas wrote:
> On Tue, Apr 29, 2014 at 05:59:27AM +0100, Jungseok Lee wrote:
> > --- a/Documentation/arm64/memory.txt
> > +++ b/Documentation/arm64/memory.txt
> > @@ -8,10 +8,11 @@ This document describes the virtual memory layout
> > used by the AArch
On Tue, Apr 29, 2014 at 12:06:03PM -0700, Brian Norris wrote:
> OK, I'll try to split it up. Is ARM unique in tracking defconfigs in
> separate trees? I assume MIPS, PowerPC, and Blackfin won't require the
> same splitting? I'd like to avoid 31 patches when <20 could suffice.
>
> I'll also rebase
Hi Tomasz,
I have tested your patches for exynos5250 and 5420. Works fine. Are
you planning to post v3? If you want I can share hand with you for v3.
Regards,
Rahul Sharma
On 9 April 2014 17:17, Andreas Oberritter wrote:
> Hello Andrzej,
>
> On 09.04.2014 10:37, Andrzej Hajda wrote:
>>> +static
On 2014年04月30日 13:16, Jiang Liu wrote:
> Hi Tianyu,
> Found another issue at the second glance.
> In case of x2apic, "if (apic_id < 0)" should be replaced
> by "if (apic_id == -1)" for safety.
Hi Jiang:
Thanks for suggestion. I will update soon.
> Best Regards!
> Gerry
>
>
In the frequency table dts file, the frequencies are arranged in
descending order which maps 1 to 1 with other frequency parameter to
be calculated and programmed in some registers.
But the OPP library works by generating the frequencies in ascending
order which breaks the above logic.
So added OPP
Hi all,
This tree still fails (more than usual) the powerpc allyesconfig build.
Changes since 20140429:
The powerpc tree still had its build failure.
The drm-intel tree gained a conflict against the drm-intel-fixes tree.
The mfd-lj tree still had its build failure so I used the version from
If the inode page is clean during its inode eviction, it'd better drop the page
to reduce further memory pressure.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/inode.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c
index f7a6553..adc622c 100644
--- a/fs/f2fs/inod
Dear Peter
If we wait the end of loop as loops_per_jiffy.
It may last more than 130s and local IRQ disabled at interval
which may cause Hard LOCKUP. We break out in 1 second and
dump the stack for debug.
> -Original Message-
> From: Peter Zijlstra [mailto:pet...@infradead.org]
>
On Wed, Apr 30, 2014 at 01:04:31PM -0400, Wang, Xiaoming wrote:
> loops_per_jiffy is larger than expectation that possible
> causes one thread can not obtain the spin lock for a long time.
> So use cpu_clock() to reach timeout in one second which can
> avoid HARD LOCKUP.
This is just not making se
Hi Pankaj,
On Wed, Apr 30, 2014 at 10:47 AM, Pankaj Dubey wrote:
> This patch modifies Exynos Power Management Unit (PMU) initialization
> implementation in following way:
>
> - Added platform_device support by registering static platform device.
> - Added platform struct exynos_pmu_data to hold
Hi Rafael,
Thanks for previous review for v1. Later on I thought acpi_lapic is
more suitable for checking whether LAPIC in MADT is available, and it can
hanlde both the UP system running SMP kernel with no LAPIC in MADT and kdump
kernel after multiple CPUs system crashed on non-1st CPU.
I tested
From: Rob Herring
The call to early_init_fdt_scan_reserved_mem will be skipped if
reserved-ranges is not found. Move the call earlier so that it is called
unconditionally.
Signed-off-by: Rob Herring
Cc: Marek Szyprowski
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: linuxppc-...@lists.ozl
Hi Pankaj,
On 30 April 2014 10:47, Pankaj Dubey wrote:
> As machine function ops are used only in this file let's make
> them static.
>
> Signed-off-by: Pankaj Dubey
> ---
> arch/arm/mach-exynos/exynos.c |6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/
In acpi_processor_get_info(), acpi processor info is initialized including
id, namely cpu index. Currently, if on UP system running SMP kerenl with
no LAPIC in MADT, cpu0_initialized is checked if acpi processor id is
initialized.
However this check maybe is not correct for kdump kernel. Most of t
On Tue, Apr 29, 2014 at 03:45:08PM -0400, David Miller wrote:
> From: Darek Marcinkiewicz
> Date: Mon, 28 Apr 2014 07:36:58 +0200
>
> > +void *ec_bh_alloc_dma_mem(struct bh_priv *priv,
> > +int channel,
> > +u8 **buf,
> > +dm
On Wed, Apr 23, 2014 at 08:23:25PM +0530, Srikanth Thokala wrote:
> Device-tree binding documentation of Xilinx Video DMA Engine
>
> Signed-off-by: Srikanth Thokala
> Acked-by: Rob Herring
Applied, both
Thanks
--
~Vinod
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel
> -Original Message-
> From: David E. Box [mailto:david.e@linux.intel.com]
> Sent: Wednesday, April 30, 2014 4:03 AM
> To: david.e@linux.intel.com; jacob.jun@linux.intel.com; linux-
> p...@vger.kernel.org; Wysocki, Rafael J; linux-kernel@vger.kernel.org;
> h...@linux.intel.com
Signed-off-by: Xiubo Li
---
.../devicetree/bindings/endianness/endianness.txt | 47 ++
1 file changed, 47 insertions(+)
create mode 100644 Documentation/devicetree/bindings/endianness/endianness.txt
diff --git a/Documentation/devicetree/bindings/endianness/endianness.txt
b
For many drivers which will support rich endianness of CPU<-->Dev
need define DT properties by itself without the binding support.
The endianness using regmap:
IndexCPU Device Endianess flag for DT bool property
1LE
Changes in V3:
- Follow Mark Rutland's advice.
- Document common case of the endianess usage.
Changes in V2:
- Namespace the properties using the prefix sring.
- Add one binding ducomentation off regmap.
Xiubo Li (2):
dt/bindings: Add the DT binding documentation for endianness
regmap: add DT
Change to use struct device instead of struct platform_device
for some static functions.
Signed-off-by: Vivek Gautam
Cc: Alan Stern
Acked-by: Jingoo Han
---
Changes from v1:
- none
drivers/usb/host/ehci-exynos.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/dri
Change to use struct device instead of struct platform_device
for some static functions.
Signed-off-by: Vivek Gautam
Cc: Alan Stern
Acked-by: Jingoo Han
---
Changes from v1:
- none
drivers/usb/host/ohci-exynos.c | 20 +---
1 file changed, 9 insertions(+), 11 deletions(-)
From: Kamil Debski
Add the phy provider, supplied by new Exynos-usb2phy using
Generic phy framework.
Keeping the support for older USB phy intact right now, in order
to prevent any functionality break in absence of relevant
device tree side change for ehci-exynos.
Once we move to new phy in the d
Add support to consume phy provided by Generic phy framework.
Keeping the support for older usb-phy intact right now, in order
to prevent any functionality break in absence of relevant
device tree side change for ohci-exynos.
Once we move to new phy in the device nodes for ohci, we can
remove the s
On 04/29/2014 06:13 PM, H. Peter Anvin wrote:
> I suspect this will generate FP instructions on x86 which will corrupt user
> space state. This is thus a critical bug!!
It looks like at least x86-64 gcc does the evaluation at compile time
and there aren't any fp instructions left in the code. Ho
On Mon, 2014-04-07 at 09:31 +0200, Christophe Leroy wrote:
> This patch provides VIRT_CPU_ACCOUTING to PPC32 architecture.
> Unlike PPC64, PPC32 doesn't use the PACA convention. Therefore the
> implementation is taken from the IA64 architecture.
> It is based on additional information added to the
Hi Tianyu,
Found another issue at the second glance.
In case of x2apic, "if (apic_id < 0)" should be replaced
by "if (apic_id == -1)" for safety.
Best Regards!
Gerry
On 2014/4/30 13:08, Jiang Liu wrote:
> Hi Tianyu,
> With the suggested fix, we still need to protect
> acpi_processor_
On 04/29/2014 10:08 PM, Andrew Pinski wrote:
>
> restoring the values is hard since even the ptrace interface does not
> allow for that.
>
So that begs the ultimate question, which is: given the fact that there
is *state missing* from the state vector (this is the core of the
problem), is there
On Tue, 29 Apr 2014 15:30:22 -0700
Andrew Morton wrote:
> On Tue, 29 Apr 2014 21:35:12 +0200 Fabian Frederick wrote:
>
> > This reverts commit 842a859db26b70 due to permanent crash issues.
> >
> > Sample scenario:
> >
> > dd if=/dev/zero of=f1 bs=1M count=1
> > losetup -f f1
> > mount -t affs
> > diff --git a/Documentation/devicetree/bindings/endianness/endianness.txt
> b/Documentation/devicetree/bindings/endianness/endianness.txt
> > new file mode 100644
> > index 000..64f1d5e
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/endianness/endianness.txt
> > @@ -0,0 +1,55
Hi Tianyu,
With the suggested fix, we still need to protect
acpi_processor_hotadd_init() when pr->apic_id is -1,
otherwise it may cause invalid memory access.
Best Regards!
Gerry
diff --git a/drivers/acpi/acpi_processor.c b/drivers/acpi/acpi_processor.c
index c29c2c3ec0ad..e17befc54c34 10
On Tue, Apr 29, 2014 at 9:50 PM, H. Peter Anvin wrote:
> On 04/29/2014 08:44 PM, Hui Zhu wrote:
>>
>> I am sorry that the root cause of issue has something wrong.
>> The right root cause is:
>> When inferior call 32 bits syscall "read", Linux kernel function
>> "ia32_cstar_target" will set TS_COMP
Under "arm/mach-exynos" many files are using PMU register offsets.
Since we have added support for accessing PMU base address via DT,
now we can remove PMU mapping from exynosX_iodesc. Let's convert
all these access using either of iomapped address or regmap handle.
This will help us in removing st
From: Young-Gun Jang
Current "pm_domain.c" file uses "S5P_INT_LOCAL_PWR_EN" definition from
"regs-pmu.h" and hence needs to include this header file. As there is
no other user of "S5P_INT_LOCAL_PWR_EN" definition other than pm_domain,
to remove "regs-pmu.h" header file dependency from "pm_domain.
From: Young-Gun Jang
Add support for mapping Samsung Power Management Unit (PMU)
base address from device tree. This patch also adds helper
function as "get_exynos_pmuregmap". This function can be used
by other machine files such as "pm.c", "hotplug.c" for accessing
PMU regmap handle.
Signed-off
As we have removed static mappings from "regs-pmu.h" it does not
need map.h anymore. But "platsmp.c" needed this and till now it
got included indirectly. So lets move header inclusion of
"mach/map.h" from "regs-pmu.h" to "platsmp.c".
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/platsmp.c
This patch series, does some minor cleanup of exynos machine files.
It also modifies Exynos Power Management Unit (PMU) related code for
converting it into a platform_driver.
This is also preparation for moving PMU related code out of machine
folder into a either "drivers/mfd", or "drivers/power" o
Many files under "arm/mach-exynos" are having file path in file
comment section which is invalid now.
So for better code maintainability let's remove them.
Signed-off-by: Pankaj Dubey
Reviewed-by: Tomasz Figa
---
arch/arm/mach-exynos/headsmp.S |2 --
arch/arm/mach-exynos/hotplug
As exynos_cpuidle_init and exynos_cpufreq_init function have just one lines
of code for registering platform devices. We can move these lines to
exynos_dt_machine_init and delete exynos_cpuidle_init and exynos_cpufreq_init
function. This will help in reducing lines of code in exynos.c, making it
mo
This patch modifies Exynos Power Management Unit (PMU) initialization
implementation in following way:
- Added platform_device support by registering static platform device.
- Added platform struct exynos_pmu_data to hold platform specific data.
- For each SoC's PMU support now we can add platform
Remove unused and unwanted declarations from "mach-exynos/common.h"
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/common.h |9 -
1 file changed, 9 deletions(-)
diff --git a/arch/arm/mach-exynos/common.h b/arch/arm/mach-exynos/common.h
index 30123a0..8a4aa0b 100644
--- a/arch/
This patch removes unnecessary header file inclusion from pmu.c.
Signed-off-by: Young-Gun Jang
Reviewed-by: Tomasz Figa
---
arch/arm/mach-exynos/pmu.c |1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-exynos/pmu.c b/arch/arm/mach-exynos/pmu.c
index 05c7ce1..4c3453a 100644
---
From: Young-Gun Jang
This patch moves PMU specific definitions into a new file
as exynos-pmu.h. This will help in making PMU implementation
independent of common.h header.
Signed-off-by: Young-Gun Jang
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/common.h | 17 -
From: Young-Gun Jang
While making PMU implementation to be device tree based, there are
few register offsets related with SYSREG present in regs-pmu.h, so
let's make a new header file "regs-sys.h" to keep all such SYSREG
related register offsets and remove them from "regs-pmu.h"
Signed-off-by: Y
As machine function ops are used only in this file let's make
them static.
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/exynos.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos/exynos.c
index 3d69e8d..06dcc
On 04/28/2014 03:12 PM, Andi Kleen wrote:
> From: Andi Kleen
>
> Every gs selector/index reload always paid an extra MFENCE
> between the two SWAPGS. This was to work around an old
> bug in early K8 steppings. All other CPUs don't need the extra
> mfence. Patch the extra MFENCE only in for K8.
>
On 04/29/2014 09:52 PM, H. Peter Anvin wrote:
>
> It matters -- greatly -- if (and only if) we can enter the kernel with
> usergs == kernelgs and then want to change usergs inside a paranoid
> routine. At that point we risk being upside down, which basically means
> we're rooted.
>
> However, I
On Wed, 2014-03-19 at 17:05 -0500, Scott Wood wrote:
> On Wed, 2014-03-19 at 22:52 +0100, Christophe Leroy wrote:
> > This patch provides VIRT_CPU_ACCOUTING to PPC32 architecture.
> > Unlike PPC64, PPC32 doesn't provide the PACA register. Therefore the
> > implementation is similar to the one done
On 04/29/2014 04:39 PM, Andi Kleen wrote:
>> Case 3 is annoying. If nothing tries to change the user gs base, then
>> everything is okay because the user gs base and the kernel gs bases are
>> equal. But if something does try to change the user gs base, then it
>> will accidentally change the ker
On 04/29/2014 08:44 PM, Hui Zhu wrote:
>
> I am sorry that the root cause of issue has something wrong.
> The right root cause is:
> When inferior call 32 bits syscall "read", Linux kernel function
> "ia32_cstar_target" will set TS_COMPAT to current_thread_info->status.
>
> syscall read is interr
On Mon, Apr 28, 2014 at 2:04 PM, Arnd Bergmann wrote:
> On Sunday 27 April 2014 13:07:32 Shaik Ameer Basha wrote:
>> The current exynos-iommu(System MMU) driver does not work autonomously
>> since it is lack of support for power management of peripheral blocks.
>> For example, MFC device driver mu
Thanks Peter, I will try to find other solutions.
On 2014/4/28 15:09, Peter Zijlstra wrote:
> On Mon, Apr 28, 2014 at 10:48:13AM +0800, Jiang Liu wrote:
>> Intel platforms with Nehalem/Westmere/IvyBridge CPUs may support socket
>> hotplug/online at runtime. The CPU hot-addition flow is:
>> 1) hand
Hi,
On Mon, Apr 28, 2014 at 9:11 PM, Alan Stern wrote:
> On Mon, 28 Apr 2014, Vivek Gautam wrote:
>
>> Add support to consume phy provided by Generic phy framework.
>> Keeping the support for older usb-phy intact right now, in order
>> to prevent any functionality break in absence of relevant
>>
On 29 April 2014 23:23, Stratos Karafotis wrote:
> Since commit d37e2b7644 ("intel_pstate: remove unneeded sample buffers")
> we use only one sample. So, there is no need to pass the sample
> pointer to intel_pstate_calc_busy. Instead, get the pointer from
> cpudata. Also, remove the unused SAMPLE
On 30 April 2014 04:09, Rafael J. Wysocki wrote:
> It should be cleaned up generally, so if you have the time and you're willing
> to do such things, please do them.
>
> That said things like lines in excess of 80 characters may stay as they are.
I have tried this sort of stuff earlier, but there
On Tue, Apr 29, 2014 at 07:56:13PM -0700, Linus Torvalds wrote:
> On Tue, Apr 29, 2014 at 7:31 PM, Al Viro wrote:
> >
> > OK, aggregate diff follows, more readable splitup (3 commits) attached.
> > It seems to survive beating here; testing, review and comments are
> > welcome.
>
> Miklos, did you
Resend to kernel-development list.
The original email wasn't plaintext mode and was rejected by
kernel-development list.
On Tue, Apr 29, 2014 at 11:31 PM, Jidong Xiao wrote:
> Hi,
>
> I noticed this variable, defined in mm/nommu.c,
>
> mm/nommu.c:int heap_stack_gap = 0;
>
> This variable only sh
On 04/29/2014 04:48 PM, Xia Kaixu wrote:
> From: Arnd Bergmann
>
> dma_addr_t may be 64 bit wide, which causes a build failure
> when doing a division on it. Here it is safe to cast to an
> u32 type, which avoids the problem.
>
> Signed-off-by: Arnd Bergmann
> Signed-off-by: Xia Kaixu
> Cc: Ma
On Tue, Apr 29, 2014 at 07:24:30PM -0700, Davidlohr Bueso wrote:
> > futex(uaddr=0x7f55ff8c4000, op=0x6, val=0x20006223800b,
> > utime=0x7f55ff8c4000, uaddr2=0x7f55ff8c4000, val3=-123)
>
> Perhaps because of chance. Even for pi futexes, if the lock is
> uncontended, the kernel will neve
On Tue, Apr 22, 2014 at 12:33 AM, H. Peter Anvin wrote:
> On 04/21/2014 09:19 AM, Hui Zhu wrote:
>> }
>> Now ax is in 32 bits now, need sign-extend to 64 bits. But
>> current_thread_info()->status TS_COMPAT is cleared when GDB call "call
>> func1()".
>> Linux kernel don't know this is a 32 bits
On 04/29/2014 08:46 PM, Arnd Bergmann wrote:
On Tuesday 29 April 2014 13:05:15 Ulf Hansson wrote:
On 29 April 2014 11:45, Arnd Bergmann wrote:
drivers/built-in.o: In function `rtsx_usb_sdmmc_drv_remove':
:(.text+0x806480): undefined reference to `led_classdev_unregister'
drivers/built-in.o: I
On Apr 29, 2014, at 5:08 AM, Dan Carpenter wrote:
> On Sun, Apr 27, 2014 at 01:06:42PM -0400, Oleg Drokin wrote:
>> diff --git a/drivers/staging/lustre/lustre/llite/dir.c
>> b/drivers/staging/lustre/lustre/llite/dir.c
>> index 7fbc18e..c391b60 100644
>> --- a/drivers/staging/lustre/lustre/llite/d
Hi Kishon, Tomasz,
On Mon, Apr 28, 2014 at 11:47 AM, Vivek Gautam wrote:
> Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs.
> The new driver uses the generic PHY framework and will interact
> with DWC3 controller present on Exynos5 series of SoCs.
> Thereby, removing old phy-samsu
Hello!
On Apr 29, 2014, at 5:46 AM, Dan Carpenter wrote:
>>
>> +/* Fall through */
>> case 7:
>> sptlrpc_fini();
>> -case 5:
>> +/* Fall through */
>> +case 6:
>> ldlm_exit();
>> -case 4:
>> +/* Fall through */
>> +
Hello!
On Apr 29, 2014, at 7:02 AM, Dan Carpenter wrote:
>> diff --git a/drivers/staging/lustre/lustre/llite/statahead.c
>> b/drivers/staging/lustre/lustre/llite/statahead.c
>> index 51c5327..1b47774 100644
>> --- a/drivers/staging/lustre/lustre/llite/statahead.c
>> +++ b/drivers/staging/lustre/
According commit d640113fe(ACPI: processor: fix acpi_get_cpuid for UP
processor), Bios may not provide _MAT or MADT tables and acpi_get_apicid()
always returns -1. For these cases, original code will pass apic_id with
vaule of -1 to acpi_map_cpuid() and it will check the acpi_id. If acpi_id
is equ
On Tue, 29 Apr 2014, Xia Kaixu wrote:
From: Arnd Bergmann
Building ARM randconfig got into a situation where CONFIG_INPUT
is turned off and SND_SOC_ALL_CODECS is turned on, which failed
for two codecs trying to use the input subsystem. Some other
drivers also select one of these codecs and c
loops_per_jiffy is larger than expectation that possible
causes one thread can not obtain the spin lock for a long time.
So use cpu_clock() to reach timeout in one second which can
avoid HARD LOCKUP.
Signed-off-by: Chuansheng Liu
Signed-off-by: xiaoming wang
---
kernel/locking/spinlock_debug.c
On 04/29/2014 01:31 PM, Dave Martin wrote:
> On Tue, Apr 29, 2014 at 05:36:30PM +0100, Joel Fernandes wrote:
>
> [...]
>
Sorry what I meant is, say its of Type function. What tells the firmware
to switch to THUMB?
What's typically done is a boot address register is written by
On Tue, Apr 29, 2014 at 7:31 PM, Al Viro wrote:
>
> OK, aggregate diff follows, more readable splitup (3 commits) attached.
> It seems to survive beating here; testing, review and comments are
> welcome.
Miklos, did you have some particular load that triggered this, or was
it just some reports? I
Here's a redo of the patch [1] that effectively does the same
thing but is the right way to do things by using ENDPROC instead.
The firmware correctly switches to THUMB before entry.
The patch applies ontop of the earlier patch [1].
[1] https://lkml.org/lkml/2014/4/22/1044
Suggested-by: Dave Mar
On Tuesday, April 29, 2014 11:41 PM, Catalin Marinas wrote:
> Jungseok,
Hi, Catalin
> On Tue, Apr 29, 2014 at 05:59:20AM +0100, Jungseok Lee wrote:
> > +choice
> > + prompt "Level of translation tables"
> > + default ARM64_3_LEVELS if ARM64_4K_PAGES
> > + default ARM64_2_LEVELS if ARM64_64K
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/i915_gem_gtt.c between commitcfa7c862982b
("drm/i915: Sanitize the enable_ppgtt module option once") from the
drm-intel-fixes tree tree and commit 5db6c735ead5 ("drm/i915: dmesg
output for VT-d testing")
We don't need to wait on page writeback for these cases.
Signed-off-by: Chao Yu
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c | 4 ++--
fs/f2fs/inline.c | 3 ++-
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index 273fe16..91ff104 100644
--- a/
This patch removes grab_cache_page_write_begin for meta pages.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
index 1346ce9..b6f6ead 100644
--- a/fs/f2fs/checkpoint.c
+++ b/fs
This patch splits grab_cache_page_write_begin into grab_cache_page and
wait_on_page_writeback for node pages.
This patch intends to enhance the latency to get node pages by alleviating
unnecessary wait_on_page_writeback.
Signed-off-by: Chao Yu
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/dir.c|
This patch reduces the lock granularity during write_begin.
When the system is under memory pressure, it would be better to reduce
the locking time for the data pages.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a
On Wednesday, April 30, 2014 5:35 AM, Mitchel Humpherys wrote:
> On Mon, Apr 28 2014 at 09:59:14 PM, Jungseok Lee wrote:
> > This patch fixed the following checkpatch complaint as using pr_*
> > instead of printk.
> >
> > WARNING: printk() should include KERN_ facility level
> >
> > Cc: Catalin Ma
On Wed, Apr 30, 2014 at 12:20:13AM +0100, Al Viro wrote:
> On Tue, Apr 29, 2014 at 04:04:11PM -0700, Linus Torvalds wrote:
> > But at a minimum, we have "d_op->d_prune()" that would now be possibly
> > be called for the old dentry *after* a new dentry has been allocated.
> > Not to mention the inod
On Tue, 29 Apr 2014 12:32:17 +0200 Peter Zijlstra
wrote:
> So I'm sure I'm not getting it; but why is all the wait_bit crap so
> entirely different from the normal wait stuff?
>
> Surely something like:
>
> wait_event_timeout(&wq, test_bit(bit, word), timeout);
>
> Is pretty much the sam
On Wednesday, April 30, 2014 2:04 AM, Catalin Marinas wrote:
> On Tue, Apr 29, 2014 at 05:59:33AM +0100, Jungseok Lee wrote:
> > diff --git a/arch/arm64/kernel/head.S b/arch/arm64/kernel/head.S index
> > 0fd5650..03ec424 100644
> > --- a/arch/arm64/kernel/head.S
> > +++ b/arch/arm64/kernel/head.S
>
On Tue, 2014-04-29 at 20:14 -0400, Dave Jones wrote:
> On Tue, Apr 29, 2014 at 11:16:55AM -0400, Dave Jones wrote:
> > Just hit this while fuzzing the futex() syscall.
> >
> >
> > WARNING: CPU: 2 PID: 6202 at kernel/locking/rtmutex-debug.c:151
> debug_rt_mutex_proxy_unlock+0x4e/0x60()
> > D
> -Original Message-
> From: Will Deacon [mailto:will.dea...@arm.com]
> Sent: 2014年4月24日 1:08
> To: Neil Zhang
> Cc: li...@arm.linux.org.uk; linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.org; Sudeep Holla; devicet...@vger.kernel.org
> Subject: Re: [PATCH v4] ARM: perf: s
On Tuesday, April 29, 2014 11:45 PM, Catalin Marinas wrote:
> On Tue, Apr 29, 2014 at 05:59:23AM +0100, Jungseok Lee wrote:
> > +config ARM64_VA_BITS
> > + int "Virtual address space size"
> > + range 39 39 if ARM64_4K_PAGES && ARM64_3_LEVELS
> > + range 42 42 if ARM64_64K_PAGES && ARM64_2_LE
earlyprintk=efi,keep will cause kernel hangs while freeing initmem like below:
[2.826089] VFS: Mounted root (ext4 filesystem) readonly on device 254:2.
[2.846592] devtmpfs: mounted
[2.856974] Freeing unused kernel memory: 880K (817d4000 -
818b)
It is caused by efi
ACPICA 20140424 Release Notes for kernel-resident subsystem:
Implemented support to skip/ignore NULL address entries in the RSDT/XSDT.
Some of these tables are known to contain a trailing NULL entry. Lv Zheng.
Removed an extraneous error message for the case where there are a large
number of syst
Move all of the public globals to acpixf.h for the convenience
of users. Also:
Adds #ifndef/#endif conditions arround ACPI_GLOBAL and
ACPI_INIT_GLOBAL definition so that OSPMs might be able to:
1. Redefine ACPI_GLOBAL/ACPI_INIT_GLOBAL into no-op, and
2. Redefine external global variables into imme
The commit of back porting Linux XSDT validation mechanism has introduced
a regreession:
Commit: 671cc68dc61f029d44b43a681356078e02d8dab8
Subject: ACPICA: Back port and refine validation of the XSDT root table.
There is a pointer still accessed after unmapping.
This patch fixes this issue. Lv
From: Bob Moore
Add some additional commenting the the public acpixf.h file.
Signed-off-by: Bob Moore
Signed-off-by: Lv Zheng
---
include/acpi/acpixf.h | 73 -
1 file changed, 54 insertions(+), 19 deletions(-)
diff --git a/include/acpi/acpixf
From: Bob Moore
Change all instances of "sub-table" to "subtable" for
consistency.
Signed-off-by: Bob Moore
Signed-off-by: Lv Zheng
---
include/acpi/actbl1.h |4 ++--
include/acpi/actbl2.h |6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/include/acpi/actbl1.h
This patch enforces a rule to always use ACPI_VALIDATE_RSDP_SIG for RSDP
signatures passed from table header or ACPI_SIG_RSDP so that truncated
string comparison can be avoided. This could help to fix the issue that
"RSD " matches but "RSD PTR " doesn't match. Lv Zheng.
Signed-off-by: Lv Zheng
From: Bob Moore
Version 20140424.
Signed-off-by: Bob Moore
Signed-off-by: Lv Zheng
---
include/acpi/acpixf.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/acpi/acpixf.h b/include/acpi/acpixf.h
index b3b2108..4e3044c 100644
--- a/include/acpi/acpixf.h
+++ b/inc
This patch adds "-x" and "-x -x" options to disable XSDT for acpidump.
The single "-x" can be used to stop using XSDT, RSDT will be forced to find
static tables, note that XSDT will still be dumped. The double "-x" can
stop dumping XSDT, which is useful when the XSDT address reported by RSDP
is po
From: Bob Moore
1) Eliminate most use of GAS structs, since they are not needed
for GPEs.
2) Allow raw GPE numbers > 255.
Signed-off-by: Bob Moore
Signed-off-by: Lv Zheng
---
drivers/acpi/acpica/acevents.h |5 +++--
drivers/acpi/acpica/aclocal.h |9 +
drivers/acpi/acpica/ev
With the NULL entry sanity check implemented, the XSDT validation is
useless because:
1. If XSDT contains NULL entries, it can be bypassed by the new sanity
check mechanism;
2. If RSDP contains a bad XSDT address, invoking XSDT validation will still
lead to a kernel crash.
This patch deletes
This patch re-orders the interface prototypes defined in acpixf.h, moving
those having not back ported to ACPICA into a seperate section to reduce
the source code differences between Linux and ACPICA.
This can help to reduce the cost of linuxizing the follow up commits.
Signed-off-by: Lv Zheng
--
1 - 100 of 724 matches
Mail list logo