Re: [PATCH V2 1/3] kvm: use kmalloc() instead of kzalloc() during iodev register/unregister

On 08/26/2015 01:45 PM, Joe Perches wrote: > On Wed, 2015-08-26 at 13:39 +0800, Jason Wang wrote: >> > >> > On 08/25/2015 11:29 PM, Joe Perches wrote: >>> > > On Tue, 2015-08-25 at 15:47 +0800, Jason Wang wrote: > > >> > All fields of kvm_io_range were initialized or copied explicitly >

Re: [PATCH V2 1/3] kvm: use kmalloc() instead of kzalloc() during iodev register/unregister

On Wed, 2015-08-26 at 13:39 +0800, Jason Wang wrote: > > On 08/25/2015 11:29 PM, Joe Perches wrote: > > On Tue, 2015-08-25 at 15:47 +0800, Jason Wang wrote: > >> > All fields of kvm_io_range were initialized or copied explicitly > >> > afterwards. So switch to use kmalloc(). > > Is there any

Re: [PATCH net-next] macvtap/macvlan: use IFF_NO_QUEUE

On 08/26/2015 12:32 AM, Vlad Yasevich wrote: > On 08/25/2015 07:30 AM, Jason Wang wrote: >> >> On 08/25/2015 06:17 PM, Michael S. Tsirkin wrote: >>> On Mon, Aug 24, 2015 at 04:33:12PM +0800, Jason Wang wrote: > For macvlan, switch to use IFF_NO_QUEUE instead of tx_queue_len = 0. > >

Re: [PATCH v4 4/4] Use 2GB memory block size on large-memory x86-64 systems

On Tue, Aug 25, 2015 at 9:17 PM, Ingo Molnar wrote: > NAK due to lack of cleanliness: the two loops look almost identical - this > sure > can be factored out... Please check complete version at https://patchwork.kernel.org/patch/7074341/ Andrew, Ingo NAKed raw version of this patch, so you

Re: [PATCH v3] qcom: ipq40xx: Add basic board/dts support for IPQ40XX SoC

On Tue, Aug 25, 2015 at 02:14:05PM -0700, Stephen Boyd wrote: > On 08/25, Varadarajan Narayanan wrote: > > On Mon, Aug 24, 2015 at 03:49:28PM -0700, Stephen Boyd wrote: > > > On 08/24, Varadarajan Narayanan wrote: > > > > > > + compatible = "qcom,ipq40xx-r3pc", "qcom,ipq40xx"; > > > > + > >

Re: [PATCH V2 1/3] kvm: use kmalloc() instead of kzalloc() during iodev register/unregister

On 08/25/2015 11:29 PM, Joe Perches wrote: > On Tue, 2015-08-25 at 15:47 +0800, Jason Wang wrote: >> > All fields of kvm_io_range were initialized or copied explicitly >> > afterwards. So switch to use kmalloc(). > Is there any compiler added alignment padding > in either structure? If so,

Re: Problems loading firmware using built-in drivers with kernels that use initramfs.

On Wed, 26 Aug 2015 07:12:46 +0200, Jie, Yang wrote: > > > -Original Message- > > From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com] > > Sent: Wednesday, August 26, 2015 3:58 AM > > To: Takashi Iwai > > Cc: Luis R. Rodriguez; Girdwood, Liam R; Jie, Yang; > >

Re: Problems loading firmware using built-in drivers with kernels that use initramfs.

> On Aug 26, 2015, at 04:26, Linus Torvalds > wrote: > > On Tue, Aug 25, 2015 at 12:58 PM, Dmitry Torokhov > wrote: >> >> Either build firmware in the kernel or ramdisk (so it is always >> available), or make sure request_firmware() calls are not in driver's >> probe() paths. > > The

Re: [PATCH v9 0/3] Enable PPI sysfs interface for TPM 2.0

On Tue, Aug 25, 2015 at 07:20:24PM +0200, Peter Huewe wrote: > Will look at it as soon as possible - relocating to the us is quite > stressful.sorry about that. > > But since we are already at v9 i think it is in a good shape. > Peter Alright, thanks for informing about this! /Jarkko > Am

Re: Proposal for finishing the 64-bit x86 syscall cleanup

>>> Thing 2: vdso compilation with binutils that doesn't support .cfi directives >>> >>> Userspace debuggers really like having the vdso properly >>> CFI-annotated, and the 32-bit fast syscall entries are annotatied >>> manually in hexidecimal. AFAIK Jan Beulich is the only person who >>>

RE: Problems loading firmware using built-in drivers with kernels that use initramfs.

> -Original Message- > From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com] > Sent: Wednesday, August 26, 2015 3:58 AM > To: Takashi Iwai > Cc: Luis R. Rodriguez; Girdwood, Liam R; Jie, Yang; > joonas.lahti...@linux.intel.com; Tom Gundersen; Ming Lei; Al Viro; Greg > Kroah-Hartman; Kay

[PATCH v2] mm: Check if section present during memory block (un)registering

Tony found on his setup, if memory block size 512M will cause crash during booting. BUG: unable to handle kernel paging request at ea007420 IP: [] get_nid_for_pfn+0x17/0x40 PGD 128ffcb067 PUD 128ffc9067 PMD 0 Oops: [#1] SMP Modules linked in: CPU: 0 PID: 1 Comm: swapper/0 Not

Re: [PATCH V3 2/3] kvm: don't register wildcard MMIO EVENTFD on two buses

On 08/25/2015 07:51 PM, Michael S. Tsirkin wrote: > On Tue, Aug 25, 2015 at 05:05:47PM +0800, Jason Wang wrote: >> > We register wildcard mmio eventfd on two buses, one for KVM_MMIO_BUS >> > and another is KVM_FAST_MMIO_BUS. This leads to issue: >> > >> > - kvm_io_bus_destroy() knows nothing

Re: [PATCH V2 3/3] kvm: add tracepoint for fast mmio

On 08/25/2015 07:34 PM, Michael S. Tsirkin wrote: > On Tue, Aug 25, 2015 at 03:47:15PM +0800, Jason Wang wrote: >> > Cc: Gleb Natapov >> > Cc: Paolo Bonzini >> > Cc: Michael S. Tsirkin >> > Signed-off-by: Jason Wang >> > --- >> > arch/x86/kvm/trace.h | 17 + >> >

Re: [PATCH V2 2/3] kvm: don't register wildcard MMIO EVENTFD on two buses

On 08/25/2015 07:33 PM, Michael S. Tsirkin wrote: > On Tue, Aug 25, 2015 at 03:47:14PM +0800, Jason Wang wrote: >> > We register wildcard mmio eventfd on two buses, one for KVM_MMIO_BUS >> > and another is KVM_FAST_MMIO_BUS. This leads to issue: >> > >> > - kvm_io_bus_destroy() knows nothing

[PATCH v2 RESEND] irqchip, gicv3-its, numa: Workaround for Cavium ThunderX erratum 23144

This implements a workaround for gicv3-its erratum 23144 on Cavium's ThunderX dual-socket platforms, where LPI cannot be routed to a redistributors present on a foreign node. Signed-off-by: Ganapatrao Kulkarni Signed-off-by: Robert Richter --- The patch below is on top of Robert's recent gicv3

Re: [PATCH v2 0/6] perf: Introduce extended syscall error reporting

* Johannes Berg wrote: > On Tue, 2015-08-25 at 12:07 +0200, Ingo Molnar wrote: > > Having a separate syscall has two (big!) appeals: > > > > - we wouldn't have to touch existing system calls at all. > > > > - extended error reporting would be available for any system call that > > opts to

Re: [PATCH v5 0/8] Add generic support for relaxed atomics

Hi Will, On Thu, Aug 06, 2015 at 05:54:36PM +0100, Will Deacon wrote: > > Will Deacon (8): > atomics: add acquire/release/relaxed variants of some atomic > operations > asm-generic: rework atomic-long.h to avoid bulk code duplication > asm-generic: add relaxed/acquire/release variants

Re: [PATCH v4 10/11] dma: rename dma_*_writecombine() to dma_*_wc()

* Andrew Morton wrote: > > There's a catch-22 issue here either way, for instance this rename patch > > has > > been being baked for probably 2 releases already but the difficulty has > > been > > trying to find the appropriate time to merge it without conflict. > > > > If you do it in the

Re: [PATCH v4 4/4] Use 2GB memory block size on large-memory x86-64 systems

* Yinghai Lu wrote: > --- a/drivers/base/node.c > +++ b/drivers/base/node.c > @@ -390,8 +390,14 @@ int register_mem_sect_under_node(struct memory_block > *mem_blk, int nid) > sect_end_pfn = section_nr_to_pfn(mem_blk->end_section_nr); > sect_end_pfn += PAGES_PER_SECTION - 1; >

[PATCH 1/2] mpt3sas: Refcount sas_device objects and fix unsafe list usage

From: Nicholas Bellinger These objects can be referenced concurrently throughout the driver, we need a way to make sure threads can't delete them out from under each other. This patch adds the refcount, and refactors the code to use it. Additionally, we cannot iterate over the sas_device_list

[PATCH 2/2] mpt3sas: Refcount fw_events and fix unsafe list usage

From: Nicholas Bellinger The fw_event_work struct is concurrently referenced at shutdown, so add a refcount to protect it, and refactor the code to use it. Additionally, refactor _scsih_fw_event_cleanup_queue() such that it no longer iterates over the list without holding the lock, since

[PATCH 0/2] mpt3sas: Reference counting fixes from in-flight mpt2sas

From: Nicholas Bellinger Hi James & Co, This series is a mpt3sas forward port of Calvin Owens' in-flight reference counting bugfixes for mpt2sas LLD code here: [PATCH v4 0/2] Fixes for memory corruption in mpt2sas http://marc.info/?l=linux-scsi=143951695904115=2 The differences between

Re: [PATCH] kernel: make module.c itself more explicitly non-modular

Paul Gortmaker writes: > The Kconfig currently controlling compilation of this code is: > > menuconfig MODULES >bool "Enable loadable module support" > > ...meaning that it currently is not being built as a module by anyone. > No surprise here, since modular support being a module would be an

Re: [RFC PATCH v2] memory-barriers: remove smp_mb__after_unlock_lock()

On Tue, 2015-08-25 at 17:27 -0700, Paul E. McKenney wrote: > On Thu, Aug 20, 2015 at 04:56:04PM +0100, Will Deacon wrote: > > On Thu, Aug 20, 2015 at 10:45:05AM +0100, Michael Ellerman wrote: > > > On Tue, 2015-08-18 at 09:37 +0100, Will Deacon wrote: > > > > > > > > Thanks, that sounds great.

Re: [PATCH] mm: Check if section present during memory block (un)registering

On Tue, Aug 25, 2015 at 4:08 PM, Andrew Morton wrote: > On Tue, 25 Aug 2015 15:41:16 -0700 Yinghai Lu wrote: > >> Tony found on his setup, if memory block size 512M will cause crash >> during booting. >> >> BUG: unable to handle kernel paging request at ea007420 >> IP: []

Re: linux: sata_nv: adma support

On Tue, Aug 25, 2015 at 6:58 AM, Pali Rohár wrote: > On Tuesday 25 August 2015 07:20:05 Mark Lord wrote: >> On 15-08-01 09:45 PM, Robert Hancock wrote: >> >On Sat, Aug 1, 2015 at 2:09 PM, Pali Rohár wrote: >> >>On Thursday 25 December 2014 07:22:13 Robert Hancock wrote: >> >>>On Tue, Dec 23,

[PATCH v2] ARM: OMAP: Change all cpu_is_* occurences to soc_is_*

Currently apart from dra7, omap5 and amx3 all the other SoCs are identified using cpu_is_* functions which is not right since they are all SoCs(System on Chips). Hence changing the SoC identification code to use soc_is instead of cpu_is and keeping defines for cpu_is where needed. This allows us

[PATCH 6/8] fix staging:android style issue:Comparison to NULL could be written

Signed-off-by: Peng Sun --- drivers/staging/android/sw_sync.c | 6 +++--- drivers/staging/android/sync.c| 18 +- 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/drivers/staging/android/sw_sync.c b/drivers/staging/android/sw_sync.c index c90838d..29b5c35

[PATCH 3/8] fix staging:android style issue:Alignment should match open parenthesis

Signed-off-by: Peng Sun --- drivers/staging/android/ashmem.c | 8 drivers/staging/android/lowmemorykiller.c | 4 ++-- drivers/staging/android/sync.c| 4 ++-- drivers/staging/android/sync.h| 2 +- drivers/staging/android/timed_gpio.c | 12

[PATCH 2/8] fix staging:android style issue:No space is necessary after a cast

Signed-off-by: Peng Sun --- drivers/staging/android/ashmem.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/android/ashmem.c b/drivers/staging/android/ashmem.c index b340ddc..1312600 100644 --- a/drivers/staging/android/ashmem.c +++

[PATCH 4/8] fix staging:android style issue:Prefer kernel type 'u32' over 'uint32_t'

Signed-off-by: Peng Sun --- drivers/staging/android/lowmemorykiller.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/android/lowmemorykiller.c b/drivers/staging/android/lowmemorykiller.c index 61937ab..78e1281 100644 ---

[PATCH 7/8] fix staging:android style issue:definition without comment

Signed-off-by: Peng Sun --- drivers/staging/android/sync.h | 2 +- drivers/staging/android/timed_gpio.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/android/sync.h b/drivers/staging/android/sync.h index 18a94ed..bb42923 100644 ---

[PATCH 8/8] fix staging:android style issue:Please don't use multiple blank lines

Signed-off-by: Peng Sun --- drivers/staging/android/timed_gpio.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/android/timed_gpio.c b/drivers/staging/android/timed_gpio.c index 5c55463..33acbbe 100644 --- a/drivers/staging/android/timed_gpio.c +++

[PATCH 5/8] fix staging:android style issue:Please use a blank line after function/struct/union/enum declarations

Signed-off-by: Peng Sun --- drivers/staging/android/lowmemorykiller.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/staging/android/lowmemorykiller.c b/drivers/staging/android/lowmemorykiller.c index 78e1281..3f1311f 100644 ---

[PATCH 1/8] fix staging:android style issue:spaces preferred around that '-'

Signed-off-by: Peng Sun --- drivers/staging/android/ashmem.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/staging/android/ashmem.c b/drivers/staging/android/ashmem.c index 60200a3..b340ddc 100644 --- a/drivers/staging/android/ashmem.c +++

[PATCH 0/8] fix drivers/staging/android several coding style issues

patches based on linux-next next-20150825 Corrections based on checkpatch.pl with --strict Peng Sun (8): fix staging:android style issue:spaces preferred around that '-' fix staging:android style issue:No space is necessary after a cast fix staging:android style issue:Alignment should match

Re: [PATCH] soc: qcom: smd: Use correct remote processor ID

On Tue 25 Aug 13:36 PDT 2015, Andy Gross wrote: > This patch fixes SMEM addressing issues when remote processors need to use > secure SMEM partitions. > Right, sorry for missing that remote_pid and edge_pid isn't in sync... > Signed-off-by: Andy Gross > --- >

Re: [PATCH 0/3] timer: Improve itimers scalability

On Tue, 25 Aug 2015 20:17:45 -0700 Jason Low wrote: > When running a database workload on a 16 socket machine, there were > scalability issues related to itimers. > > Commit 1018016c706f addressed the issue with the thread_group_cputimer > spinlock taking up a significant portion of total run

[PATCH v2] ASoC: rockchip: fix a misjudgement by return

Being careless, judge the return value of snd_soc_card_jack_new is opposite, so it should be fixed. --- Changes in v2: Signed-off-by: Xing Zheng Reviewed-by: Dylan Reid sound/soc/rockchip/rockchip_rt5645.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 3/3] timer: Reduce unnecessary sighand lock contention

It was found while running a database workload on large systems that significant time was spent trying to acquire the sighand lock. The issue was that whenever an itimer expired, many threads ended up simultaneously trying to send the signal. Most of the time, nothing happened after acquiring the

[PATCH 0/3] timer: Improve itimers scalability

When running a database workload on a 16 socket machine, there were scalability issues related to itimers. Commit 1018016c706f addressed the issue with the thread_group_cputimer spinlock taking up a significant portion of total run time. This patch series address the other issue where a lot of

[PATCH 2/3] timer: Check thread timers only when there are active thread timers

The fastpath_timer_check() contains logic to check for if any timers are set by checking if !task_cputime_zero(). Similarly, we can do this before calling check_thread_timers(). In the case where there are only process-wide timers, this will skip all the computations for the per-thread timers when

[PATCH 1/3] timer: Optimize fastpath_timer_check()

In fastpath_timer_check(), the task_cputime() function is always called to compute the utime and stime values. However, this is not necessary if there are no per-thread timers to check for. This patch modifies the code such that we compute the task_cputime values only when there are per-thread

RE: [V3 PATCH 3/4] kexec: Fix race between panic() and crash_kexec() called directly

Hi, > From: Peter Zijlstra [mailto:pet...@infradead.org] > > On Sat, Aug 22, 2015 at 02:35:24AM +, 河合英宏 / KAWAI，HIDEHIRO wrote: > > > From: Peter Zijlstra [mailto:pet...@infradead.org] > > > > > > On Thu, Aug 06, 2015 at 02:45:43PM +0900, Hidehiro Kawai wrote: > > > > void

Re: [PATCH V2 0/4] PCI: ACPI: Setting up DMA coherency for PCI device from _CCA attribute

Hi Arnd, On 8/26/15 01:48, Arnd Bergmann wrote: On Wednesday 26 August 2015 00:33:25 Suravee Suthikulpanit wrote: This patch adds support to setup DMA coherency for PCI device using the ACPI _CCA attribute. According to the ACPI spec, the _CCA attribute is required for ARM64. Therefore, this

Re: [PATCH 2/2] usbnet: Fix a race between usbnet_stop() and the BH

From: Eugene Shatokhin Date: Mon, 24 Aug 2015 23:13:43 +0300 > The race may happen when a device (e.g. YOTA 4G LTE Modem) is > unplugged while the system is downloading a large file from the Net. > > Hardware breakpoints and Kprobes with delays were used to confirm that > the race does actually

[PATCH] arm64: fix bug for reloading FPSIMD state after execve on cpu 0.

From: Janet Liu If process A is running on CPU 0 and do execve syscall and after sched_exec, dest_cpu is 0, fpsimd_state.cpu is 0. If at the time Process A get scheduled out and after some kernel threads running on CPU 0, process A is back in CPU 0, A's fpsimd_state.cpu is current cpu id "0",

Re: [PATCH 1/2] usbnet: Get EVENT_NO_RUNTIME_PM bit before it is cleared

From: Eugene Shatokhin Date: Mon, 24 Aug 2015 23:13:42 +0300 > It is needed to check EVENT_NO_RUNTIME_PM bit of dev->flags in > usbnet_stop(), but its value should be read before it is cleared > when dev->flags is set to 0. > > The problem was spotted and the fix was provided by > Oliver Neukum

Re: [PATCH v1 3/3] arm64: dts: add Hi6220 mailbox node

On Tue, 2015-08-25 at 16:37 +0100, Leif Lindholm wrote: > On Tue, Aug 25, 2015 at 04:51:22PM +0200, Ard Biesheuvel wrote: > > >>Arm kernel should either fetch memory information from > > >>efi or DT. > > > > > > Absolutely. > > > > > >>Currently arm kernel fetch both efi memory

Re: [Patch v3] ACPI, PCI: Penalize legacy IRQ used by ACPI SCI

On 08/25/2015 04:01 PM, Thomas Gleixner wrote: > On Fri, 21 Aug 2015, Jiang Liu wrote: >> --- >> Hi Nick, >> Rafael and Thomas have concerns about the way to solve the >> regression by quirk, so could you please help to test this patch? > > Nick, can you please confirm that this works? I

Re: [PATCH 2/2] perf probe: Support probing at absolute address

On 2015/8/26 8:02, 平松雅巳 / HIRAMATU，MASAMI wrote: From: Wang Nan [mailto:wangn...@huawei.com] It should be useful to allow 'perf probe' probe at absolute offset of a target. For example, when (u)probing at a instruction of a shared object in a embedded system where debuginfo is not avaliable

Re: [PATCH V1 0/3] fix clock issue for fsl,spdif

On Tue, Aug 25, 2015 at 11:45:27AM -0700, Michael Turquette wrote: > Quoting Shengjiu Wang (2015-08-11 02:26:51) > > fix clock issue for fsl,spdif > > > > Shengjiu Wang (3): > > ARM: imx6q: Add SPDIF_GCLK clock in clock tree > > ARM: imx6sl: Add SPDIF_GCLK clock in clock tree > > ARM:

Re: [RESEND PATCH 0/3 v6] Add Mediatek MT8173 cpufreq driver

On 26-08-15, 09:25, Pi-Cheng Chen wrote: > The [3/3] is based on Mediatek SoC maintainer tree[1] and the patch which > introduce a new clock type[2] consumed by MT8173 cpufreq driver. So it will > cause some conflicts if it goes through your tree. I am not sure how this > should be handled, but

Re: [PATCH] fs/binfmt_elf_fdpic.c: fix brk area overlap with stack on NOMMU

On Wed, Aug 26, 2015 at 11:26:02AM +1000, Greg Ungerer wrote: > Hi Rich, > > On 21/08/15 05:11, Rich Felker wrote: > > From: Rich Felker > > > > On NOMMU archs, the FDPIC ELF loader sets up the usable brk range to > > overlap with all but the last PAGE_SIZE bytes of the stack. This leads > > to

Re: [PATCH V2 2/4] ACPI/scan: Clean up acpi_check_dma

On Wednesday, August 26, 2015 09:00:23 AM Suravee Suthikulpanit wrote: > Hi Rafael, > > On 8/26/15 06:48, Rafael J. Wysocki wrote: > > >[...] > > On Wednesday, August 26, 2015 12:33:27 AM Suravee Suthikulpanit wrote: > >> diff --git a/drivers/acpi/glue.c b/drivers/acpi/glue.c > >> index

[PATCH] kernel: make module.c itself more explicitly non-modular

The Kconfig currently controlling compilation of this code is: menuconfig MODULES bool "Enable loadable module support" ...meaning that it currently is not being built as a module by anyone. No surprise here, since modular support being a module would be an interesting chicken before the egg

Re: [PATCH 1/1] usb: dwc2: gadget: parity fix in isochronous mode

On 8/25/2015 3:00 PM, Roman Bacik wrote: >> -Original Message- >> From: John Youn [mailto:john.y...@synopsys.com] >> Sent: August-25-15 2:52 PM >> To: Scott Branden; John Youn; Greg Kroah-Hartman; linux- >> u...@vger.kernel.org >> Cc: linux-kernel@vger.kernel.org; bcm-kernel-feedback-list;

Re: [PATCH v2 7/7] ARM: bcm2835: Add VC4 to the device tree.

On 08/18/2015 03:54 PM, Eric Anholt wrote: > VC4 is the GPU (display and 3D) present on the 2835. This patch and patch 1 seem OK to me, although I'll withhold any ack until the DT binding design discussion with Rob has been resolved. I haven't looked at the OF graph bindings he mentioned so have

linux-next: build failure after merge of the mmc-uh tree

used te mmc-uh tree from next-20150825 for today. -- Cheers, Stephen Rothwells...@canb.auug.org.au -- 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.

Re: [PATCH v2 6/7] ARM: bcm2835: Add the DDC I2C controller to the device tree.

On 08/18/2015 03:54 PM, Eric Anholt wrote: > We need to use it for getting video modes over HDMI. This patch, Acked-by: Stephen Warren -- 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

Re: [PATCH V2 4/4] PCI: ACPI: Add support for PCI device DMA coherency

Hi Rafael, On 8/26/15 06:48, Rafael J. Wysocki wrote: On Wednesday, August 26, 2015 12:33:29 AM Suravee Suthikulpanit wrote: This patch adds support for setting up PCI device DMA coherency from ACPI _CCA object that should normally be specified in the DSDT node of its PCI host bridge.

Re: [PATCH V2 2/4] ACPI/scan: Clean up acpi_check_dma

Hi Rafael, On 8/26/15 06:48, Rafael J. Wysocki wrote: [...] On Wednesday, August 26, 2015 12:33:27 AM Suravee Suthikulpanit wrote: diff --git a/drivers/acpi/glue.c b/drivers/acpi/glue.c index b9657af..55cf916 100644 --- a/drivers/acpi/glue.c +++ b/drivers/acpi/glue.c @@ -168,7 +168,7 @@ int

Re: [PATCH v4 4/5] spi: bcm2835: new driver implementing auxiliar spi1/spi2 on the bcm2835 soc

On 08/24/2015 02:40 AM, ker...@martin.sperl.org wrote: > From: Martin Sperl Patch description? > arch/arm/configs/bcm2835_defconfig |1 + > drivers/spi/Kconfig| 12 + > drivers/spi/Makefile |1 + > drivers/spi/spi-bcm2835aux.c | 506 >

Re: [PATCH v6 3/3] qe_common: add qe_muram_ functions to manage muram

On Tue, 2015-08-25 at 20:49 -0500, Zhao Qiang-B45475 wrote: > > -Original Message- > > From: Wood Scott-B07421 > > Sent: Wednesday, August 26, 2015 12:23 AM > > To: Zhao Qiang-B45475 > > Cc: Laura Abbott; linux-kernel@vger.kernel.org; linuxppc- > > d...@lists.ozlabs.org;

Re: [PATCH v4 1/5] soc: bcm2835: auxiliar devices enable infrastructure

On 08/24/2015 02:40 AM, ker...@martin.sperl.org wrote: > From: Martin Sperl > > The bcm2835 SOC contains 3 auxiliar devices (spi1, spi2 and uart1) > that all are enabled via a shared register. > > To serialize access to this shared register this soc-driver > is created that implements: >

RE: [PATCH v6 3/3] qe_common: add qe_muram_ functions to manage muram

> -Original Message- > From: Wood Scott-B07421 > Sent: Wednesday, August 26, 2015 12:23 AM > To: Zhao Qiang-B45475 > Cc: Laura Abbott; linux-kernel@vger.kernel.org; linuxppc- > d...@lists.ozlabs.org; lau...@codeaurora.org; Xie Xiaobo-R63061; > b...@kernel.crashing.org; Li Yang-Leo-R58472;

Re: [PATCH v4 5/5] dt/bindings: bcm2835: Add binding documentation for auxiliar spi devices

On 08/24/2015 02:40 AM, ker...@martin.sperl.org wrote: > From: Martin Sperl Patch description? > diff --git a/Documentation/devicetree/bindings/spi/brcm,bcm2835-aux-spi.txt > b/Documentation/devicetree/bindings/spi/brcm,bcm2835-aux-spi.txt > +Required properties: > +- compatible: Should be

Re: [PATCH v4 3/5] dt/bindings: bcm2835: add binding documentation for bcm2835-aux

On 08/24/2015 02:40 AM, ker...@martin.sperl.org wrote: > From: Martin Sperl Patch description? > diff --git a/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-aux.txt > b/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-aux.txt > +Required properties: > +- compatible: Should be

Re: [PATCH 1/3] ARM: uniphier: add outer cache support

Hi Arnd, 2015-08-25 4:59 GMT+09:00 Arnd Bergmann : > On Monday 24 August 2015 11:18:10 Masahiro Yamada wrote: >> diff --git >> a/Documentation/devicetree/bindings/arm/uniphier/cache-uniphier.txt >> b/Documentation/devicetree/bindings/arm/uniphier/cache-uniphier.txt >> new file mode 100644 >>

Re: [PATCH] irqdomain: remove the confused log

On Tue, Aug 25, 2015 at 09:34:00PM +0200, Thomas Gleixner wrote: > On Tue, 25 Aug 2015, Huang Shijie wrote: > > > When the dynamic debug is enabled for irq domain, the kernel will print out: > > -- > > irqdomain:__irq_domain_add: irq:

Re: [PATCH net] net: dsa: fix EDSA frame from hwaccel frame

On Tue, Aug 25, 2015 at 06:28:34PM -0700, Florian Fainelli wrote: > Le 08/03/15 23:35, Vivien Didelot a écrit : > > If the underlying network device features NETIF_F_HW_VLAN_CTAG_TX, > > an EDSA frame is prepended with a 802.1q header once queued. > > > > To fix this, push the VLAN tag to the

Re: [PATCH] kernel: make rcu/tree_trace.c explicitly non-modular

[Re: [PATCH] kernel: make rcu/tree_trace.c explicitly non-modular] On 25/08/2015 (Tue 15:37) Paul E. McKenney wrote: > On Tue, Aug 25, 2015 at 02:11:09PM -0400, Paul Gortmaker wrote: > > [Re: [PATCH] kernel: make rcu/tree_trace.c explicitly non-modular] On > > 25/08/2015 (Tue 09:29) Josh

[PATCH v2 2/9] mm: move __phys_to_pfn and __pfn_to_phys to asm/generic/memory_model.h

From: Christoph Hellwig Three architectures already define these, and we'll need them genericly soon. Signed-off-by: Christoph Hellwig Signed-off-by: Dan Williams --- arch/arm/include/asm/memory.h |6 -- arch/arm64/include/asm/memory.h |6 --

[PATCH v2 3/9] mm: ZONE_DEVICE for "device memory"

While pmem is usable as a block device or via DAX mappings to userspace there are several usage scenarios that can not target pmem due to its lack of struct page coverage. In preparation for "hot plugging" pmem into the vmemmap add ZONE_DEVICE as a new zone to tag these pages separately from the

[PATCH v2 9/9] devm_memremap_pages: protect against pmem device unbind

Given that: 1/ device ->remove() can not be failed 2/ a pmem device may be unbound at any time 3/ we do not know what other parts of the kernel are actively using a 'struct page' from devm_memremap_pages() ...provide a facility for active usages of device memory to block pmem device unbind.

[PATCH v2 6/9] libnvdimm, pfn: 'struct page' provider infrastructure

Implement the base infrastructure for libnvdimm PFN devices. Similar to BTT devices they take a namespace as a backing device and layer functionality on top. In this case the functionality is reserving space for an array of 'struct page' entries to be handed out through pfn_to_page(). For now this

[PATCH v2 1/9] dax: drop size parameter to ->direct_access()

None of the implementations currently use it. The common bdev_direct_access() entry point handles all the size checks before calling ->direct_access(). Signed-off-by: Christoph Hellwig Signed-off-by: Dan Williams --- arch/powerpc/sysdev/axonram.c |2 +- drivers/block/brd.c |

[PATCH v2 7/9] libnvdimm, pmem: 'struct page' for pmem

Enable the pmem driver to handle PFN device instances. Attaching a pmem namespace to a pfn device triggers the driver to allocate and initialize struct page entries for pmem. Memory capacity for this allocation comes exclusively from RAM for now which is suitable for low PMEM to RAM ratios.

[PATCH v2 4/9] add devm_memremap_pages

From: Christoph Hellwig This behaves like devm_memremap except that it ensures we have page structures available that can back the region. Signed-off-by: Christoph Hellwig [djbw: catch attempts to remap RAM, drop flags] Signed-off-by: Dan Williams --- include/linux/io.h | 20

[PATCH v2 0/9] initial struct page support for pmem

Changes since v1 [1]: 1/ Several simplifications from Christoph including dropping the __pfn_t dependency, and merging ZONE_DEVICE into the base arch_add_memory() implementation. 2/ Drop the deeper changes to the memory hotplug code that enabled allocating the backing 'struct page'

[PATCH v2 8/9] libnvdimm, pmem: direct map legacy pmem by default

The expectation is that the legacy / non-standard pmem discovery method (e820 type-12) will only ever be used to describe small quantities of persistent memory. Larger capacities will be described via the ACPI NFIT. When "allocate struct page from pmem" support is added this default policy can

[PATCH v2 5/9] x86, pmem: push fallback handling to arch code

The decision of when to fallback to the default pmem apis is currently done at too high of a level. In particular the test for arch_has_pmem_api() in memcpy_to_pmem() really wants to decide whether the arch_memcpy_to_pmem() implementation is placing data in a location that a subsequent wmb_pmem()

Re: [PATCH net] net: dsa: fix EDSA frame from hwaccel frame

Le 08/03/15 23:35, Vivien Didelot a écrit : > If the underlying network device features NETIF_F_HW_VLAN_CTAG_TX, > an EDSA frame is prepended with a 802.1q header once queued. > > To fix this, push the VLAN tag to the payload if present, before > checking the frame protocol. Makes sense, but you

Re: [PATCH v1 3/3] arm64: dts: add Hi6220 mailbox node

On Wed, 2015-08-26 at 00:00 +0800, Leo Yan wrote: > On Tue, Aug 25, 2015 at 09:43:14PM +0800, Haojian Zhuang wrote: > > On Tue, 2015-08-25 at 11:42 +0100, Mark Rutland wrote: > > > > > Are you then going to hack GRUB, release a special HiKey version of > > > > > GRUB, not support any other

Re: [RESEND PATCH 0/3 v6] Add Mediatek MT8173 cpufreq driver

Hi Rafael, On Wed, Aug 26, 2015 at 7:01 AM, Rafael J. Wysocki wrote: > On Tuesday, August 25, 2015 10:10:44 AM Pi-Cheng Chen wrote: >> On Mon, Aug 17, 2015 at 5:24 PM, Pi-Cheng Chen >> wrote: >> > MT8173 is a ARMv8 based SoC with 2 clusters. All CPUs in a single cluster >> > share the same

[PATCH] arm: insn: use set_fixmap_offset to make it more clear

A little change to patch_map() function, use set_fixmap_offset() to make code more clear. Signed-off-by: yalin wang --- arch/arm/kernel/patch.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/arch/arm/kernel/patch.c b/arch/arm/kernel/patch.c index 69bda1a..5779105

Re: [PATCH] fs/binfmt_elf_fdpic.c: fix brk area overlap with stack on NOMMU

Hi Rich, On 21/08/15 05:11, Rich Felker wrote: > From: Rich Felker > > On NOMMU archs, the FDPIC ELF loader sets up the usable brk range to > overlap with all but the last PAGE_SIZE bytes of the stack. This leads > to catastrophic memory reuse/corruption if brk is used. Fix by setting > the brk

Re: [PATCH 1/1] params: don't ignore the rest of cmdline if parse_one() fails

Oleg Nesterov writes: > parse_args() just aborts after it hits an error, so other args > at the same initcall level are simply ignored. This can lead to > other hard-to-understand problems, for example my testing machine > panics during the boot if I pass "locktorture.verbose=true". > > Change

Re: ask for help about BUG: soft lockup - CPU#13 stuck for 22s! [trinity-c13:6691]

Looks like the none-preempt kernel will not schedule from trinity and the program run into D states? Ding On 2015/8/25 22:06, Kefeng Wang wrote: > Hi all, > > We got issues about rcu/ soft lockup in trinity test on our arm64 board, > and have no idea to fix this, any advice will be

Re: [PATCH V2] mm:memory hot-add: memory can not been added to movable zone

First, thanks very much for your review, I will update codes according to your suggestion On 2015/8/25 21:12, Yasuaki Ishimatsu wrote: On Thu, 20 Aug 2015 03:28:05 -0400 Changsheng Liu wrote: From: Changsheng Liu When memory is hot added, should_add_memory_movable() always returns 0

Re: [PATCH] Memory hot added,The memory can not been added to movable zone

在 2015/8/25 19:13, Vlastimil Babka 写道: On 08/25/2015 12:25 PM, Changsheng Liu wrote: Thanks very much for your review, I can move the memory from normal zone to movable zone succesfully. And thank you for let me understand the memory mechanism better. 在 2015/8/25 3:15, Yasuaki Ishimatsu 写道:

Re: [PATCH] gpio: rcar: GPIO_RCAR doesn't relate to ARM

On Tue, Aug 25, 2015 at 11:15:18AM +0200, Geert Uytterhoeven wrote: > On Tue, Aug 25, 2015 at 11:12 AM, Kuninori Morimoto > wrote: > > From: Kuninori Morimoto > > > > 8cd1470("gpio: rcar: Add r8a7795 (R-Car H3) support") added > > GPIO support for r8a7795. r8a7795 based on CONFIG_ARM64. > >

RE: [PATCH v7 10/17] KVM: x86: Update IRTE for posted-interrupts

> -Original Message- > From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Wednesday, August 26, 2015 3:58 AM > To: Wu, Feng > Cc: pbonz...@redhat.com; j...@8bytes.org; mtosa...@redhat.com; > eric.au...@linaro.org; k...@vger.kernel.org; > io...@lists.linux-foundation.org;

[PATCH v4] pinctrl: mediatek: Fix multiple registration issue.

Since our common driver need support main chip and PMU at the same time, that means it will register two pinctrl device, and the pinctrl_desc structure should be used two times. But pinctrl_desc use global static definition, then the latest registered pinctrl device will overwrite the old one's,

Re: [PATCH] arm: kgdb: Don't try to stop the machine when setting breakpoints

On Tue, Aug 25, 2015 at 3:02 PM, Douglas Anderson wrote: > In (23a4e40 arm: kgdb: Handle read-only text / modules) we moved to > using patch_text() to set breakpoints so that we could handle the case > when we had CONFIG_DEBUG_RODATA. That patch used patch_text(). > Unfortunately, patch_text()

Re: [PATCH v4] pinctrl: mediatek: Fix multiple registration issue.

On Tue, 2015-08-25 at 17:16 -0700, Hongzhou Yang wrote: > Since our common driver need support main chip and PMU > at the same time, that means it will register two > pinctrl device, and the pinctrl_desc structure should > be used two times. > > But pinctrl_desc use global static definition, then

Re: [RFC PATCH v2] memory-barriers: remove smp_mb__after_unlock_lock()

On Thu, Aug 20, 2015 at 04:56:04PM +0100, Will Deacon wrote: > On Thu, Aug 20, 2015 at 10:45:05AM +0100, Michael Ellerman wrote: > > On Tue, 2015-08-18 at 09:37 +0100, Will Deacon wrote: > > > On Tue, Aug 18, 2015 at 02:50:55AM +0100, Michael Ellerman wrote: > > > > On Mon, 2015-08-17 at 09:57

[PATCH] PCI: create builtin_pci_driver to avoid registration boilerplate

In commit f309d4443130bf814e991f836e919dca22df37ae ("platform_device: better support builtin boilerplate avoidance") we introduced the builtin_driver macro. Here we use that support and extend it to PCI driver registration, so where a driver is clearly non-modular and builtin-only, we can

Re: [PATCH] of/irq: export of_get_irq_byname()

Hi Dmitry, On Tue, 25 Aug 2015 17:04:02 -0700 Dmitry Torokhov wrote: > > Similarly to of_get_irq(), let's export of_irq_get_byname(), so if a bus core > can be compiled as a module (such as I2C) it can have access to the symbol. > > Reported-by: Stephen Rothwell > Reported-by: kbuild test

  1   2   3   4   5   6   7   8   9   10   >