Re: [PATCH] PCI: hisi: Fix Section mismatch compilation warning for probe()

On Thu, 12 Nov 2015 13:21:02 +0100 Arnd Bergmann wrote: > On Thursday 12 November 2015 20:02:08 Jisheng Zhang wrote: > > Following compilation warning occurs when compiled with: > > CONFIG_DEBUG_SECTION_MISMATCH=y > > > > WARNING: drivers/pci/host/built-in.o(.data+0x308): Section mismatch in >

Re: Shut up unhandled MSR warnings

On 12/11/2015 13:16, Borislav Petkov wrote: >>> > > Yes, see guest_cpuid_has_* for an example of reading the CPUID values. >>> > > >>> > > But if it's defined for _all_ models starting at family 21, we can just >>> > > do it unconditionally. >> > >> > The thing is, those bits are Reserved

Re: drm: Bogus WARN() in drm_atomic_helper_update_legacy_modeset_state() ?

On Thu, Nov 12, 2015 at 02:27:29PM +0800, Mark yao wrote: > On 2015年11月11日 00:56, Thierry Reding wrote: > >On Tue, Nov 10, 2015 at 03:01:03PM +, Liviu Dudau wrote: > >>Hello, > >> > >>When booting my Juno board with the HDLCD driver that I have converted to > >>atomic operations I'm getting

Re: [PATCH 0/2] Introduce the request handling for dm-crypt

On Thu 12-11-15 19:46:26, Baolin Wang wrote: > On 12 November 2015 at 19:06, Jan Kara wrote: > > On Thu 12-11-15 17:40:59, Baolin Wang wrote: > >> On 12 November 2015 at 17:17, Jan Kara wrote: > >> > On Thu 12-11-15 10:15:32, Baolin Wang wrote: > >> >> On 11 November 2015 at 17:48, Christoph

[PATCH] PCI: hisi: fix deferred probing

The hisi_pcie_probe function is incorrectly marked as __init, as Kconfig tells us: WARNING: drivers/pci/host/built-in.o(.data+0x7780): Section mismatch in reference from the variable hisi_pcie_driver to the function .init.text:hisi_pcie_probe() If the probe for this device gets deferred past

Re: [PATCH v2 2/3] efi-pstore: implement efivars_pstore_exit()

On Wed, 11 Nov, at 11:23:15PM, Luck, Tony wrote: > >>> module_init(efivars_pstore_init); > >> > >> Looks OK to me. Kees, are you picking this up? > > > > I can, though usually it goes through Tony. > > Can I count that as "Acked-by" from both of you? Yep, Acked-by: Matt Fleming -- To

Re: [PATCH] PCI: hisi: Fix Section mismatch compilation warning for probe()

On Thursday 12 November 2015 20:02:08 Jisheng Zhang wrote: > Following compilation warning occurs when compiled with: > CONFIG_DEBUG_SECTION_MISMATCH=y > > WARNING: drivers/pci/host/built-in.o(.data+0x308): Section mismatch in > reference from the variable hisi_pcie_driver to the function >

Re: [PATCH v3 0/3] virtio DMA API core stuff

On Thu, 2015-11-12 at 13:09 +0200, Michael S. Tsirkin wrote: > On Wed, Nov 11, 2015 at 11:30:27PM +0100, David Woodhouse wrote: > > > > If the IOMMU is exposed, and enabled, and telling the guest kernel that > > it *does* cover the virtio devices, then those virtio devices will > > *not* be in

Re: [PATCH] ARM: xip: Use correct symbol for end of ROM marker

On 11/11/2015 09:17 AM, Chris Brandt wrote: > For an XIP build, _edata_loc, not _etext, represents the end of the > binary image that will be programmed into ROM and mapped into the > MODULES_VADDR area. > With an XIP kernel, nothing is loaded into RAM before boot, meaning > you have to take into

Re: drm: Bogus WARN() in drm_atomic_helper_update_legacy_modeset_state() ?

On Wed, Nov 11, 2015 at 04:09:42PM +, Liviu Dudau wrote: > On Tue, Nov 10, 2015 at 05:56:15PM +0100, Thierry Reding wrote: > > On Tue, Nov 10, 2015 at 03:01:03PM +, Liviu Dudau wrote: > > > Hello, > > > > > > When booting my Juno board with the HDLCD driver that I have converted to > > >

Re: Shut up unhandled MSR warnings

On Thu, Nov 12, 2015 at 11:59:58AM +0100, Borislav Petkov wrote: > On Thu, Nov 12, 2015 at 11:33:33AM +0100, Paolo Bonzini wrote: > > Yes, see guest_cpuid_has_* for an example of reading the CPUID values. > > > > But if it's defined for _all_ models starting at family 21, we can just > > do it

[PATCH 0/3] arm64: make some functions static

These functions are only called within the its own file, so they could be declared static. Jisheng Zhang (3): arm64: smp: make of_parse_and_init_cpus static arm64: mmu: make split_pud and fixup_executable static arm64: suspend: make hw_breakpoint_restore static arch/arm64/kernel/smp.c

[PATCH 1/3] arm64: smp: make of_parse_and_init_cpus static

of_parse_and_init_cpus is only called from within smp.c, so it can be declared static. Signed-off-by: Jisheng Zhang --- arch/arm64/kernel/smp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/kernel/smp.c b/arch/arm64/kernel/smp.c index 2bbdc0e..b1adc51 100644 ---

[PATCH 3/3] arm64: suspend: make hw_breakpoint_restore static

hw_breakpoint_restore is only used within suspend.c, so it can be declared static. Signed-off-by: Jisheng Zhang --- arch/arm64/kernel/suspend.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/kernel/suspend.c b/arch/arm64/kernel/suspend.c index 40f7b33..fce95e1

[PATCH 2/3] arm64: mmu: make split_pud and fixup_executable static

split_pud and fixup_executable are only called from within mmu.c, so they can be declared static. Signed-off-by: Jisheng Zhang --- arch/arm64/mm/mmu.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/arm64/mm/mmu.c b/arch/arm64/mm/mmu.c index c2fa6b5..02306c3 100644

Re: [PATCH 00/10 V2] KVM: x86: MMU: Clean up x86's mmu code for future work

On 12/11/2015 12:48, Takuya Yoshikawa wrote: > v1->v2: > Patch 5 and 7 are added based on Paolo's suggestions. > Patch 8-10 are new. > > Patch 1/2/3/4: no change. > Patch 5: Needed a bit more work than I had expected. > Patch 6: Removed extra comment of v1 (patch 5 made it inappropriate). >

Re: [Patch v7 4/7] PCI/ACPI: Add interface acpi_pci_root_create()

On Wed, Nov 11, 2015 at 09:55:37PM +0100, Arnd Bergmann wrote: > On Wednesday 11 November 2015 17:46:47 Lorenzo Pieralisi wrote: > > On Tue, Nov 10, 2015 at 01:50:46PM +0800, Jiang Liu wrote: > > If we go with this approach though, you are not adding the offset to > > the resource when parsing the

[PATCH] PCI: hisi: Fix Section mismatch compilation warning for probe()

Following compilation warning occurs when compiled with: CONFIG_DEBUG_SECTION_MISMATCH=y WARNING: drivers/pci/host/built-in.o(.data+0x308): Section mismatch in reference from the variable hisi_pcie_driver to the function .init.text:hisi_pcie_probe() Fix it by dropping __init from

Re: [PATCH v2 0/2] Stop Intel Processor Trace logging on panic

Ping, any comments on these patches? Thanks, Takao Indoh On 2015/11/04 14:22, Takao Indoh wrote: > Hi all, > > These patch series provide a feature to stop Intel Processor Trace > (Intel PT) logging and save its registers in the memory on panic. > > Intel PT is a new feature of Intel CPU

[PATCH] drivers: firmware: psci: drop duplicate const from psci_of_match

This is to fix below sparse warning: drivers/firmware/psci.c:427:40: warning: duplicate const Signed-off-by: Jisheng Zhang --- drivers/firmware/psci.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/firmware/psci.c b/drivers/firmware/psci.c index d24f35d..ae70d24

Re: [PATCH net-next RFC V3 0/3] basic busy polling support for vhost_net

Hi Jason, I understand your busy loop timeout is quite conservative at 50us. Did you try any other values? Also, did you measure how polling affects many VMs talking to each other (e.g. 20 VMs on each host, perhaps with several vNICs each, transmitting to a corresponding VM/vNIC pair on

[PATCH] KVM: arm/arm64: vgic: make vgic_io_ops static

vgic_io_ops is only referenced within vgic.c, so it can be declared static. Signed-off-by: Jisheng Zhang --- virt/kvm/arm/vgic.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/virt/kvm/arm/vgic.c b/virt/kvm/arm/vgic.c index 5335383..8ef7279 100644 --- a/virt/kvm/arm/vgic.c

Re: [PATCHv2 2/2] arm64: Allow changing of attributes outside of modules

On 2015/11/11 9:57, Laura Abbott wrote: > Currently, the set_memory_* functions that are implemented for arm64 > are restricted to module addresses only. This was mostly done > because arm64 maps normal zone memory with larger page sizes to > improve TLB performance. This has the side effect

[PATCH 1/2] FS-Cache: Add missing initialization of ret in cachefiles_write_page()

From: Geert Uytterhoeven fs/cachefiles/rdwr.c: In function ‘cachefiles_write_page’: fs/cachefiles/rdwr.c:882: warning: ‘ret’ may be used uninitialized in this function If the jump to label "error" is taken, "ret" will indeed be uninitialized, and random stack data may be printed by the debug

[PATCH 2/2] MAINTAINERS: linux-cach...@redhat.com is moderated for non-subscribers

From: Geert Uytterhoeven Signed-off-by: Geert Uytterhoeven Signed-off-by: David Howells --- MAINTAINERS |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index 35fe7ae0492e..470605885f01 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -2545,7

Re: [PATCH 0/2] Introduce the request handling for dm-crypt

On 12 November 2015 at 19:06, Jan Kara wrote: > On Thu 12-11-15 17:40:59, Baolin Wang wrote: >> On 12 November 2015 at 17:17, Jan Kara wrote: >> > On Thu 12-11-15 10:15:32, Baolin Wang wrote: >> >> On 11 November 2015 at 17:48, Christoph Hellwig >> >> wrote: >> >> > On Wed, Nov 11, 2015 at

[PATCH 0/2] FS-Cache: More miscellany

Attached are another couple of miscellaneous bits in FS-Cache and CacheFiles: (1) Fix an uninitialised error value. (2) In MAINTAINERS, mark the mailing list as being moderated for non-subscribers. These can also be found here:

Re: [PATCH 0/2] FS-Cache: More miscellany

Let me resend this with the correct cc list. -- 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.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH 10/10] KVM: x86: MMU: Remove unused parameter parent_pte from kvm_mmu_get_page()

Signed-off-by: Takuya Yoshikawa --- arch/x86/kvm/mmu.c | 20 +++- arch/x86/kvm/paging_tmpl.h | 4 ++-- 2 files changed, 9 insertions(+), 15 deletions(-) diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c index 33fe720..101e77d 100644 --- a/arch/x86/kvm/mmu.c +++

[PATCH 1/2] FS-Cache: Add missing initialization of ret in cachefiles_write_page()

From: Geert Uytterhoeven fs/cachefiles/rdwr.c: In function ‘cachefiles_write_page’: fs/cachefiles/rdwr.c:882: warning: ‘ret’ may be used uninitialized in this function If the jump to label "error" is taken, "ret" will indeed be uninitialized, and random stack data may be printed by the debug

[PATCH 09/10 RFC] KVM: x86: MMU: Move parent_pte handling from kvm_mmu_get_page() to link_shadow_page()

Every time kvm_mmu_get_page() is called with a non-NULL parent_pte argument, link_shadow_page() follows that to set the parent entry so that the new mapping will point to the returned page table. Moving parent_pte handling there allows to clean up the code because parent_pte is passed to

[PATCH 2/2] MAINTAINERS: linux-cach...@redhat.com is moderated for non-subscribers

From: Geert Uytterhoeven Signed-off-by: Geert Uytterhoeven Signed-off-by: David Howells --- MAINTAINERS |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index 35fe7ae0492e..470605885f01 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -2545,7

[PATCH 08/10] KVM: x86: MMU: Move initialization of parent_ptes out from kvm_mmu_alloc_page()

Make kvm_mmu_alloc_page() do just what its name tells to do, and remove the extra error check at its call site since the allocation cannot fail. Signed-off-by: Takuya Yoshikawa --- arch/x86/kvm/mmu.c | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git

[PATCH 0/2] FS-Cache: More miscellany

Attached are another couple of miscellaneous bits in FS-Cache and CacheFiles: (1) Fix an uninitialised error value. (2) In MAINTAINERS, mark the mailing list as being moderated for non-subscribers. These can also be found here:

[PATCH 07/10] KVM: x86: MMU: Encapsulate the type of rmap-chain head in a new struct

New struct kvm_rmap_head makes the code type-safe to some extent. Signed-off-by: Takuya Yoshikawa --- arch/x86/include/asm/kvm_host.h | 8 +- arch/x86/kvm/mmu.c | 169 +--- arch/x86/kvm/mmu_audit.c| 13 ++-- 3 files changed, 100

[PATCH 06/10] KVM: x86: MMU: Consolidate WARN_ON/BUG_ON checks for reverse-mapped sptes

At some call sites of rmap_get_first() and rmap_get_next(), BUG_ON is placed right after the call to detect unrelated sptes which must not be found in the reverse-mapping list. Move this check in rmap_get_first/next() so that all call sites, not just the users of the for_each_rmap_spte() macro,

Re: [PATCH 15/20] staging/wilc1000: pass hif operations through initialization

On Thursday 12 November 2015 19:05:41 glen lee wrote: > Hi arnd, > > I appreciate the patches. > I did test this patch series on h/w which is arm based MCU. > From this patch wilc is not working properly. After downloading firmware, > the firmware cannot start and it fails. > I double check

[PATCH 05/10] KVM: x86: MMU: Use for_each_rmap_spte macro instead of pte_list_walk()

kvm_mmu_mark_parents_unsync() alone uses pte_list_walk(), witch does nearly the same as the for_each_rmap_spte macro. The only difference is that is_shadow_present_pte() checks cannot be placed there because kvm_mmu_mark_parents_unsync() can be called with a new parent pointer whose entry is not

[PATCH] X.509: Fix the time validation [ver #3]

This fixes CVE-2015-5327. It affects kernels from 4.3-rc1 onwards. Fix the X.509 time validation to use month number-1 when looking up the number of days in that month. Also put the month number validation before doing the lookup so as not to risk overrunning the array. This can be tested by

[PATCH 04/10] KVM: x86: MMU: Remove is_rmap_spte() and use is_shadow_present_pte()

is_rmap_spte(), originally named is_rmap_pte(), was introduced when the simple reverse mapping was implemented by commit cd4a4e5374110444 ("[PATCH] KVM: MMU: Implement simple reverse mapping"). At that point, its role was clear and only rmap_add() and rmap_remove() were using it to select sptes

[PATCH 02/10] KVM: x86: MMU: Add helper function to clear a bit in unsync child bitmap

Both __mmu_unsync_walk() and mmu_pages_clear_parents() have three line code which clears a bit in the unsync child bitmap; the former places it inside a loop block and uses a few goto statements to jump to it. A new helper function, clear_unsync_child_bit(), makes the code cleaner.

[PATCH 03/10] KVM: x86: MMU: Make mmu_set_spte() return emulate value

mmu_set_spte()'s code is based on the assumption that the emulate parameter has a valid pointer value if set_spte() returns true and write_fault is not zero. In other cases, emulate may be NULL, so a NULL-check is needed. Stop passing emulate pointer and make mmu_set_spte() return the emulate

[PATCH 01/10] KVM: x86: MMU: Remove unused parameter of __direct_map()

Signed-off-by: Takuya Yoshikawa --- arch/x86/kvm/mmu.c | 12 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c index e7c2c14..c3bbc82 100644 --- a/arch/x86/kvm/mmu.c +++ b/arch/x86/kvm/mmu.c @@ -2708,9 +2708,8 @@ static void

[PATCH 00/10 V2] KVM: x86: MMU: Clean up x86's mmu code for future work

v1->v2: Patch 5 and 7 are added based on Paolo's suggestions. Patch 8-10 are new. Patch 1/2/3/4: no change. Patch 5: Needed a bit more work than I had expected. Patch 6: Removed extra comment of v1 (patch 5 made it inappropriate). Patch 7: As expected, many places needed to be converted.

[PATCH 1/4] Drivers: hv: utils: fix memory leak on on_msg() failure

inmsg should be freed in case of on_msg() failure to avoid memory leak. Signed-off-by: Vitaly Kuznetsov --- drivers/hv/hv_utils_transport.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/hv/hv_utils_transport.c b/drivers/hv/hv_utils_transport.c index

[PATCH 0/4] Drivers: hv: utils: prevent crash when a utility driver is disabled host side

I'm observing a crash when a utility driver is disabled host side (e.g. 'Guest services' is disabled live) when we have userspace daemon connected: [ 90.244859] general protection fault: [#1] SMP ... [ 90.800082] CPU: 3 PID: 473 Comm: hypervfcopyd Not tainted 4.3.0-rc7_netvsc_noalloc+

[PATCH 2/4] Drivers: hv: utils: rename outmsg_lock

As a preparation to reusing outmsg_lock to protect test-and-set openrations on 'mode' rename it the more general 'lock'. Signed-off-by: Vitaly Kuznetsov --- drivers/hv/hv_utils_transport.c | 14 +++--- drivers/hv/hv_utils_transport.h | 2 +- 2 files changed, 8 insertions(+), 8

[PATCH 3/4] Drivers: hv: utils: introduce HVUTIL_TRANSPORT_DESTROY mode

When Hyper-V host asks us to remove some util driver by closing the appropriate channel there is no easy way to force the current file descriptor holder to hang up but we can start to respond -EBADF to all operations asking it to exit gracefully. As we're setting hvt->mode from two separate

[PATCH 4/4] Drivers: hv: utils: fix crash when device is removed from host side

The crash is observed when a service is being disabled host side while userspace daemon is connected to the device: [ 90.244859] general protection fault: [#1] SMP ... [ 90.800082] Call Trace: [ 90.800082] [] __fput+0xc8/0x1f0 [ 90.800082] [] fput+0xe/0x10 ... [ 90.800082]

Re: [PATCH] null_blk: Register as a LightNVM device

On 11/11/2015 11:11 PM, Jens Axboe wrote: On 11/11/2015 02:27 PM, Jens Axboe wrote: On 11/11/2015 03:06 AM, Matias Bjørling wrote: Add support for registering as a LightNVM device. This allows us to evaluate the performance of the LightNVM library. In /drivers/Makefile, LightNVM is moved

Re: [PATCH v3 5/6] xen/arm: introduce xen_read_wallclock

On Wed, 11 Nov 2015, Arnd Bergmann wrote: > On Wednesday 11 November 2015 16:51:35 Stefano Stabellini wrote: > > +static void xen_read_wallclock(struct timespec64 *ts) > > +{ > > + u32 version; > > + u64 delta; > > + struct timespec64 now; > > + struct shared_info *s =

Re: [PATCH v3 03/17] arch: uapi: asm: mman.h: Let MADV_FREE have same value for all architectures

On Thu, Nov 12, 2015 at 01:32:59PM +0900, Minchan Kim wrote: > From: Chen Gang > > For uapi, need try to let all macros have same value, and MADV_FREE is > added into main branch recently, so need redefine MADV_FREE for it. > > At present, '8' can be shared with all architectures, so redefine

[PATCH V2] mmc: change to use kmalloc

Use kmalloc instead of kzalloc, zero the memory is not needed. Signed-off-by: yalin wang --- drivers/mmc/card/block.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/mmc/card/block.c b/drivers/mmc/card/block.c index c742cfd..c3fd4c8 100644 ---

Re: [PATCH] mmc: change to use kmalloc

> On Nov 12, 2015, at 05:57, Andy Shevchenko wrote: > > On Wed, Nov 11, 2015 at 11:17 PM, Peter Hurley > wrote: >> On 11/11/2015 12:02 PM, Alim Akhtar wrote: >>> Hi Yalin, >>> >>> On Wed, Nov 11, 2015 at 9:53 AM, yalin wang >>> wrote: Use kmalloc instead of kzalloc, zero the memory is

Re: [PATCH v3 01/17] mm: support madvise(MADV_FREE)

On Thu, Nov 12, 2015 at 01:32:57PM +0900, Minchan Kim wrote: > @@ -256,6 +260,125 @@ static long madvise_willneed(struct vm_area_struct *vma, > return 0; > } > > +static int madvise_free_pte_range(pmd_t *pmd, unsigned long addr, > + unsigned long end, struct

RE: [PATCH v2 1/3] dma: Add Freescale qDMA engine driver support

On Wed, Nov 11, 2015 4:14 PM, Vinod Koul wrote: > On Fri, Oct 23, 2015 at 09:59:11AM +0800, Yuan Yao wrote: > > > +config FSL_QDMA > > + tristate "Freescale qDMA engine support" > > + depends on SOC_LS1021A || ARCH_LAYERSCAPE > > Where is this ARCH defined, quick grep revealed none > This

Re: [PATCH v3 0/3] virtio DMA API core stuff

On Wed, Nov 11, 2015 at 11:30:27PM +0100, David Woodhouse wrote: > On Wed, 2015-11-11 at 07:56 -0800, Andy Lutomirski wrote: > > > > Can you flesh out this trick? > > > > On x86 IIUC the IOMMU more-or-less defaults to passthrough. If the > > kernel wants, it can switch it to a non-passthrough

Re: [PATCH v2 1/4] drm: arm: Add DT bindings documentation for HDLCD driver.

On Thu, Nov 12, 2015 at 10:52:25AM +, Jon Medhurst (Tixy) wrote: > On Thu, 2015-11-12 at 10:42 +, Liviu Dudau wrote: > > > This is on-chip RAM or nornal system RAM? We already have bindings > > for > > > both. > > > > Juno has a set of TLX (ThinLinks) connectors on the board where an > >

Re: [PATCH] perf/x86/intel/pt: Test CPU vendor before loading

On Thu, Nov 12, 2015 at 11:56:12AM +0100, Borislav Petkov wrote: > diff --git a/arch/x86/kernel/cpu/perf_event_intel_pt.c > b/arch/x86/kernel/cpu/perf_event_intel_pt.c > index 42169283448b..fa1262b025e7 100644 > --- a/arch/x86/kernel/cpu/perf_event_intel_pt.c > +++

Re: [PATCH 0/2] Introduce the request handling for dm-crypt

On Thu 12-11-15 17:40:59, Baolin Wang wrote: > On 12 November 2015 at 17:17, Jan Kara wrote: > > On Thu 12-11-15 10:15:32, Baolin Wang wrote: > >> On 11 November 2015 at 17:48, Christoph Hellwig wrote: > >> > On Wed, Nov 11, 2015 at 05:31:43PM +0800, Baolin Wang wrote: > >> >> Now the dm-crypt

Re: Shut up unhandled MSR warnings

On Thu, Nov 12, 2015 at 11:33:33AM +0100, Paolo Bonzini wrote: > Yes, see guest_cpuid_has_* for an example of reading the CPUID values. > > But if it's defined for _all_ models starting at family 21, we can just > do it unconditionally. The thing is, those bits are Reserved again on the next

Re: [RFC PATCH 1/2] genirq: Add runtime resume/suspend support for IRQ chips

On 11/11/15 15:41, Grygorii Strashko wrote: > On 11/11/2015 12:13 PM, Jon Hunter wrote: >> >> On 10/11/15 18:07, Lars-Peter Clausen wrote: >>> On 11/10/2015 05:47 PM, Grygorii Strashko wrote: >>> [...] > I was trying to simplify matters by placing the resume call in > __setup_irq() as

[PATCH] perf/x86/intel/pt: Test CPU vendor before loading

From: Borislav Petkov This keeps poking at MSR 0x570 when loading, i.e. MSR_IA32_RTIT_CTL, which is most likely not present on other vendors. It is using the _safe variant but there's no need to try it at all, really. Besides, it causes unhandled rdmsr warnings when booting in a guest: kvm

Re: [PATCH V3 00/26] Coresight integration with perf

Mathieu Poirier writes: Hi Mathieu, > Changes since V2: > * Rebased to v4.3. Just tried, does not apply onto v4.3. I also tried Greg's char-misc-next and TIP perf/core. Regards, -- Alex -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to

Re: drm: Bogus WARN() in drm_atomic_helper_update_legacy_modeset_state() ?

On 2015年11月12日 18:34, Liviu Dudau wrote: Can you switch your email client to text mode and make it do proper reply quoting? It is rather difficult to follow where your reply comes when you don't use HTML MUAs. Best regards, Liviu Hi Liviu I'm sorry about that, now I switch my email into

Re: [PATCH v2 1/4] drm: arm: Add DT bindings documentation for HDLCD driver.

On Thu, 2015-11-12 at 10:42 +, Liviu Dudau wrote: > > This is on-chip RAM or nornal system RAM? We already have bindings > for > > both. > > Juno has a set of TLX (ThinLinks) connectors on the board where an > FPGA can be attached. On r1 > the code running on FPGA can even participate as an

Re: Issue on regmap-mmio

On Thu, Nov 12, 2015 at 08:57:34AM +, Lu Y.B. wrote: > Hi Mark, Please fix your mail client to word wrap within paragraphs at something substantially less than 80 columns. Doing this makes your messages much easier to read and reply to. > May I know whether the regmap APIs support

Re: drm: Bogus WARN() in drm_atomic_helper_update_legacy_modeset_state() ?

On 2015年11月12日 18:36, Liviu Dudau wrote: On Thu, Nov 12, 2015 at 04:32:33PM +0800, Mark yao wrote: On 2015年11月10日 23:01, Liviu Dudau wrote: Hello, When booting my Juno board with the HDLCD driver that I have converted to atomic operations I'm getting the following warning:

Re: samples: livepatch: init reloc list and mark as klp module

On Thu, 12 Nov 2015, Jessica Yu wrote: > +++ Petr Mladek [11/11/15 16:42 +0100]: > > On Mon 2015-11-09 23:45:54, Jessica Yu wrote: > > > Intialize the list of relocation sections in the sample > > > klp_object (even if the list will be empty in this case). > > > Also mark module as a livepatch

Re: linux-next: Tree for Nov 10 (8250_mid.c)

On Tue, Nov 10, 2015 at 10:12:26AM -0800, Randy Dunlap wrote: > On 11/09/15 18:19, Stephen Rothwell wrote: > > Hi all, > > > > Please do *not* add any material intended for v4.5 to your linux-next > > included branches until after v4.4-rc1 has been released. > > > > Changes since 20151109: > >

Re: [PATCH] FS-Cache: Add missing initialization of ret in cachefiles_write_page()

On Thu, Nov 12, 2015 at 11:42 AM, David Howells wrote: > Geert Uytterhoeven wrote: > >> > This isn't quite the right solution. The uninitialised error path needs to >> > set -ENOBUFS. >> >> That's what your commit 102f4d900c9c8f5e ("FS-Cache: Handle a write to the >> page immediately beyond the

Re: [PATCH] FS-Cache: Add missing initialization of ret in cachefiles_write_page()

Geert Uytterhoeven wrote: > > This isn't quite the right solution. The uninitialised error path needs to > > set -ENOBUFS. > > That's what your commit 102f4d900c9c8f5e ("FS-Cache: Handle a write to the > page immediately beyond the EOF marker") does, and is also in its commit > description: >

Re: [PATCH v2 1/4] drm: arm: Add DT bindings documentation for HDLCD driver.

On Wed, Nov 11, 2015 at 12:48:50PM -0600, Rob Herring wrote: > On Wed, Nov 11, 2015 at 04:06:47PM +, Liviu Dudau wrote: > > Cc: Rob Herring > > Cc: Pawel Moll > > Cc: Mark Rutland > > Cc: Ian Campbell > > Cc: Kumar Gala > > > > Signed-off-by: Liviu Dudau > > Looks pretty good, but a

Re: [PATCH V2 10/12] Drivers: hv: vmbus: channge vmbus_connection.channel_lock to mutex

"K. Y. Srinivasan" writes: > From: Dexuan Cui > > spinlock is unnecessary here. > mutex is enough. Hm, mutex is usually required when we need to sleep and a spinlock is enough otherwise :-) Or are you trying to say we don't need to disable interrupts here? In that can maybe we can just switch

Re: [PATCH v2 3/4] KVM: X86: Migration is supported

On 2015/11/12 17:00, Paolo Bonzini wrote: On 12/11/2015 08:06, Jian Zhou wrote: I think you can just do this in kvm_x86_ops->set_msr. The old implementation for DEBUGCTL MSR can be moved to svm.c. I think you mean "moved to vmx.c"? No, the old implementation is moved from x86.c to

Re: [PATCH v4 2/3] mtd: nand: Add support for Arasan Nand Flash Controller

On Thu, Nov 12, 2015 at 11:32 AM, Andy Shevchenko wrote: > On Thu, 2015-11-12 at 10:18 +0530, punnaiah choudary kalluri wrote: >> On Mon, Nov 9, 2015 at 7:20 PM, Andy Shevchenko >> wrote: >> > On Thu, 2015-11-05 at 08:19 +0530, Punnaiah Choudary Kalluri wrote: >> > > Added the basic driver for

Re: [PATCH] X.509: Fix the time validation [ver #2]

On Thu, 2015-11-12 at 09:36 +, David Howells wrote: > If it works, it emit a key ID; if it fails, it should give a bad > message error. In this sentence, failure is good, yes? This is a malformed key so we *expect* the failure? -- David WoodhouseOpen Source

RE: [f2fs-dev] [PATCH] f2fs: optimize __find_rev_next_bit

Hi Fan, > -Original Message- > From: Fan Li [mailto:fanofcode...@samsung.com] > Sent: Thursday, November 12, 2015 8:43 AM > To: 'Jaegeuk Kim' > Cc: linux-kernel@vger.kernel.org; linux-f2fs-de...@lists.sourceforge.net > Subject: [f2fs-dev] [PATCH] f2fs: optimize __find_rev_next_bit > > 1.

Re: MIPS: BMIPS: Enable GZIP ramdisk and timed printks

On Thu, Nov 12, 2015 at 11:18:30AM +0100, Andreas Ziegler wrote: > Hi Florian, > > your patch "MIPS: BMIPS: Enable GZIP ramdisk and timed printks" > showed up as commit fb9e5642aa9e in linux-next today (that is, > next-20151112). I noticed it because we (a researc

Re: drm: Bogus WARN() in drm_atomic_helper_update_legacy_modeset_state() ?

On Thu, Nov 12, 2015 at 04:32:33PM +0800, Mark yao wrote: >On 2015年11月10日 23:01, Liviu Dudau wrote: > > Hello, > > When booting my Juno board with the HDLCD driver that I have converted to > atomic operations I'm getting the following warning: > > [ cut here ] >

Re: drm: Bogus WARN() in drm_atomic_helper_update_legacy_modeset_state() ?

On Thu, Nov 12, 2015 at 02:34:57PM +0800, Mark yao wrote: Mark, >On 2015年11月12日 14:27, Mark yao wrote: > > On 2015年11月11日 00:56, Thierry Reding wrote: > > On Tue, Nov 10, 2015 at 03:01:03PM +, Liviu Dudau wrote: > > Hello, > > When booting my Juno board with the HDLCD driver

Re: Shut up unhandled MSR warnings

On 12/11/2015 11:13, Borislav Petkov wrote: > Hey Paolo, > > do we apply stuff like that below? If we really need to, we do. > When booting guests all the time here, dmesg gets filled up with those > "unhandled rdmsr" useless warnings. The patch below shuts them up. > > The only problem is

Re: [PATCH v3 0/2] perf/core: rcu fixes

On Thu, Nov 12, 2015 at 11:00:02AM +0100, Stephane Eranian wrote: > > This short patch series fixes some issues with RCU locking in the generic > perf layer. > > Patch 1 fixes cgroup switching rcu issues related to the fact that > perf_cgroup_sched_out() and perf_cgroup_sched_in() were missing

Re: [PATCH v4 2/3] mtd: nand: Add support for Arasan Nand Flash Controller

On Thu, 2015-11-12 at 10:18 +0530, punnaiah choudary kalluri wrote: > On Mon, Nov 9, 2015 at 7:20 PM, Andy Shevchenko > wrote: > > On Thu, 2015-11-05 at 08:19 +0530, Punnaiah Choudary Kalluri wrote: > > > Added the basic driver for Arasan Nand Flash Controller used in > > > Zynq UltraScale+

Re: PCIe host controller behind IOMMU on ARM

On Thu, Nov 12, 2015 at 09:26:33AM +, Phil Edworthy wrote: > Hi Liviu, Arnd, > > On 11 November 2015 18:25, LIviu wrote: > > On Mon, Nov 09, 2015 at 12:32:13PM +, Phil Edworthy wrote: > > > Hi Liviu, Will, > > > > > > On 04 November 2015 15:19, Phil wrote: > > > > On 04 November 2015

Re: [PATCH 0/4] dm verity: add support for error correction

On 11/09/2015 08:19 PM, Sami Tolvanen wrote: ... > We don't see actual I/O errors very often. Most corruption we've seen > is caused by flaky hardware that doesn't return errors. However, I can > certainly change to code to attempt recovery in this case too. So if I understand it correctly, there

Re: [PATCH 4/4] locking: Introduce smp_cond_acquire()

On Thu, Nov 12, 2015 at 03:14:51PM +0800, Boqun Feng wrote: > Hmm.. probably incorrect.. because the ACQUIRE semantics of spin_lock() > only guarantees that the memory operations following spin_lock() can't > be reorder before the *LOAD* part of spin_lock() not the *STORE* part, > i.e. the case

Re: module: save load_info for livepatch modules

On Thu 2015-11-12 00:33:12, Jessica Yu wrote: > +++ Miroslav Benes [11/11/15 15:17 +0100]: > >On Mon, 9 Nov 2015, Jessica Yu wrote: > > > >>diff --git a/include/linux/module.h b/include/linux/module.h > >>index 3a19c79..c8680b1 100644 > >>--- a/include/linux/module.h > >>+++

Re: [PATCH 2/3 v4] livepatch: add old_sympos as disambiguator field to klp_reloc

On Wed, 11 Nov 2015, Chris J Arges wrote: > In cases of duplicate symbols, sympos will be used to disambiguate instead > of val. By default old_sympos will be 0, and patching will only succeed if > the symbol is unique. Specifying a positive value will ensure that > occurrence of the symbol will

Re: [PATCH] FS-Cache: Add missing initialization of ret in cachefiles_write_page()

Hi David, On Thu, Nov 12, 2015 at 11:15 AM, David Howells wrote: > Geert Uytterhoeven wrote: > >> - int ret; >> + int ret = 0; > > This isn't quite the right solution. The uninitialised error path needs to > set -ENOBUFS. That's what your commit 102f4d900c9c8f5e ("FS-Cache: Handle a

Re: [PATCH 1/3 v4] livepatch: add old_sympos as disambiguator field to klp_func

Next to Josh's remarks I have some more (mainly nitpicks, so it is often up to you). On Wed, 11 Nov 2015, Chris J Arges wrote: > In cases of duplicate symbols, old_sympos will be used to disambiguate > instead of old_addr. By default old_sympos will be 0, and patching will > only succeed if

Re: [RFC 4/4] iio: ina2xx: add SOFTWARE buffer mode using an iio kfifo.

On 11/12/2015 11:18 AM, Marc Titinger wrote: [...] >> Slightly OT, but do you already have some Sigrok IIO support? I have this >> scheduled for end of the month, maybe we can align our strategies here and >> avoid duplicated work. > > How fortunate! I've started some preliminary work like

Re: [PATCH net-next RFC V3 0/3] basic busy polling support for vhost_net

On 11/12/2015 06:16 PM, Jason Wang wrote: > Hi all: > > This series tries to add basic busy polling for vhost net. The idea is > simple: at the end of tx/rx processing, busy polling for new tx added > descriptor and rx receive socket for a while. The maximum number of > time (in us) could be

Re: MIPS: BMIPS: Enable GZIP ramdisk and timed printks

Hi Florian, your patch "MIPS: BMIPS: Enable GZIP ramdisk and timed printks" showed up as commit fb9e5642aa9e in linux-next today (that is, next-20151112). I noticed it because we (a research group from Erlangen[0]) are running daily checks on linux-next. Your commit adds two entries to

Re: [RFC 4/4] iio: ina2xx: add SOFTWARE buffer mode using an iio kfifo.

On 10/11/2015 19:23, Lars-Peter Clausen wrote: On 11/10/2015 05:07 PM, Marc Titinger wrote: Capture the active scan_elements into a kfifo. The capture thread will compute the remaining time until the next capture tick, and do an active wait (udelay). This will produce a stream of up to fours

[PATCH net-next RFC V3 2/3] vhost: introduce vhost_vq_more_avail()

Signed-off-by: Jason Wang --- drivers/vhost/vhost.c | 26 +- drivers/vhost/vhost.h | 1 + 2 files changed, 18 insertions(+), 9 deletions(-) diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index 163b365..b86c5aa 100644 --- a/drivers/vhost/vhost.c +++

[PATCH net-next RFC V3 3/3] vhost_net: basic polling support

This patch tries to poll for new added tx buffer or socket receive queue for a while at the end of tx/rx processing. The maximum time spent on polling were specified through a new kind of vring ioctl. Signed-off-by: Jason Wang --- drivers/vhost/net.c| 77

[PATCH net-next RFC V3 1/3] vhost: introduce vhost_has_work()

This path introduces a helper which can give a hint for whether or not there's a work queued in the work list. Signed-off-by: Jason Wang --- drivers/vhost/vhost.c | 7 +++ drivers/vhost/vhost.h | 1 + 2 files changed, 8 insertions(+) diff --git a/drivers/vhost/vhost.c

[PATCH net-next RFC V3 0/3] basic busy polling support for vhost_net

Hi all: This series tries to add basic busy polling for vhost net. The idea is simple: at the end of tx/rx processing, busy polling for new tx added descriptor and rx receive socket for a while. The maximum number of time (in us) could be spent on busy polling was specified ioctl. Test were done

Re: [PATCH] FS-Cache: Add missing initialization of ret in cachefiles_write_page()

Geert Uytterhoeven wrote: > - int ret; > + int ret = 0; This isn't quite the right solution. The uninitialised error path needs to set -ENOBUFS. Unfortunately, my compiler doesn't show a warning:-/ David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

<    4   5   6   7   8   9   10   11   12   13   >