Re: Variant symlink filesystem

Am 11.03.2016 um 21:22 schrieb Cole: > If I remember correctly, when we were testing the fuse version, we hard coded > the path to see if that solved the problem, and the difference between > the env lookup > code and the hard coded path was almost the same, but substantially slower > than > the

Re: [PATCH 1/1] KVM: don't allow irq_fpu_usable when the VCPU's XCR0 is loaded

On Fri, Mar 11, 2016 at 1:14 PM, Andy Lutomirski wrote: > > On Fri, Mar 11, 2016 at 12:47 PM, David Matlack wrote: > > From: Eric Northup > > > > Add a percpu boolean, tracking whether a KVM vCPU is running on the > > host CPU.

Re: [PATCH 2/2 V2] staging: dgnc: use tty_alloc_driver instead of kcalloc

On Mon, Mar 07, 2016 at 04:55:38PM +0900, Daeseok Youn wrote: > the tty_alloc_driver() can allocate memory for ttys and termios. > And also it can release allocated memory easly with using > put_tty_driver(). Also needs to be rebased and resent.

[PATCH V15 1/4] dma: qcom_hidma: implement lower level hardware interface

This patch implements the hardware hooks for the HIDMA channel driver. The main functions of interest are: - hidma_ll_init - hidma_ll_request - hidma_ll_queue_request - hidma_ll_hw_start OS layer calls the hidma_ll_init function during probe to set up the hardware. At this moment, the number of

[PATCH V15 2/4] dma: qcom_hidma: add debugfs hooks

Add debugfs hooks for debugging the execution behavior of the DMA channel. The debugfs hooks get initialized by the probe function and uninitialized by the remove function. A stats file is created in debugfs. The stats file will show the information about each HIDMA channel as well as each

Re: Variant symlink filesystem

On Fri, Mar 11, 2016 at 10:52:52PM +0200, Cole wrote: > The implementation doesn't necessarily have to continue to work with > env variables. On FreeBSD, the variant symlinks function by using > variables stored in kernel memory, and have a hierarchical lookup, > starting with user defined values

[PATCH V15 3/4] dma: qcom_hidma: add support for object hierarchy

In order to create a relationship model between the channels and the management object, we are adding support for object hierarchy to the drivers. This patch simplifies the userspace application development. We will not have to traverse different firmware paths based on device tree or ACPI based

[PATCH 4/4] dma: qcom_hidma: read the channel id from HW

Removing the flexibility to choose the event channel as there is no real use case right now. We have been using the values in ACPI that match the HW defaults. OS is reading the event-channel from the HW register now. Signed-off-by: Sinan Kaya ---

Re: Variant symlink filesystem

On Sat, Mar 12, 2016 at 12:03:11AM +0200, Cole wrote: > This was one of the first solutions we looked at, and using various > namespaces. However we would like to be able to have multiple terminal > sessions open, and be able to have each session using a different > mount point, or be able to use

Re: multipath: I/O hanging forever

On Sat, Mar 05, 2016 at 08:31:03PM -0900, Kent Overstreet wrote: > On Fri, Mar 04, 2016 at 10:30:44AM -0700, Andrea Righi wrote: > > On Sun, Feb 28, 2016 at 08:46:16PM -0700, Andrea Righi wrote: > > > On Sun, Feb 28, 2016 at 06:53:33PM -0700, Andrea Righi wrote: > > > ... > > > > I'm using

Re: Variant symlink filesystem

On 12 March 2016 at 00:48, David Lang wrote: > On Sat, 12 Mar 2016, Cole wrote: > >> On 12 March 2016 at 00:24, Al Viro wrote: >>> >>> On Sat, Mar 12, 2016 at 12:03:11AM +0200, Cole wrote: >>> This was one of the first solutions we looked at, and

Re: [PATCH V6 0/6] Intel memory b/w monitoring support

On Thu, Mar 10, 2016 at 03:32:06PM -0800, Vikas Shivappa wrote: > The patch series has two preparatory patch for cqm and then 4 MBM > patches. Patches are based on tip perf/core. They were not (or at least not a recent copy of it); all the files got moved about by someone.. But a little sed

Re: [PATCH V2] proc-vmcore: wrong data type casting fix

On Fri, 11 Mar 2016 16:42:48 +0800 Dave Young wrote: > On i686 PAE enabled machine the contiguous physical area could be large > and it can cause trimming down variables in below calculation in > read_vmcore() and mmap_vmcore(): > > tsz = min_t(size_t, m->offset +

[PATCH 2/3] pfn_t: Support for huge PFNs

We need to put entries in the radix tree that represent PMDs and PUDs. Use another bit to determine if this PFN entry represents a huge page or not. If it does, we know the bottom few bits of the PFN are zero, so we can reuse them to distinguish between PMDs and PUDs. Thanks to Neil Brown for

[PATCH 3/3] pfn_t: New functions pfn_t_add and pfn_t_cmp

When we find a huge PFN in the radix tree, we need to add the low bits of the index to it in order to find the PFN we are looking for. Since we want the result to stay in pfn_t form, create pfn_t_add(). We also need to compare PFNs, for example to determine if the PFN represents a zero page. At

[PATCH 1/3] pfn_t: Change the encoding

By moving the flag bits to the bottom, we encourage commonality between SGs with pages and those using pfn_t. We can also then insert a pfn_t into a radix tree, as it uses the same two bits for indirect & exceptional indicators. Signed-off-by: Matthew Wilcox ---

[PATCH 0/3] Make pfn_t suitable for placing in the radix tree

I did some experimenting with converting the DAX radix tree from storing sector numbers to storing pfn_t. While we're not ready to do that conversion yet, these pieces make sense to at least get reviewed now, and maybe get upstream. I think the first patch is worthwhile all by itself as a

Re: Overlapping ioremap() calls, set_memory_*() semantics

On Thu, 2016-03-10 at 22:47 -0800, Andy Lutomirski wrote: > On Mon, Mar 7, 2016 at 9:03 AM, Toshi Kani wrote: > > Let me try to summarize... > > > > The original issue Luis brought up was that drivers written to work > > with MTRR may create a single ioremap range covering

Re: [PATCH v12] [PATCH] PCI: Xilinx-NWL-PCIe: Adding support for Xilinx NWL PCIe Host Controller

Hi Bharat, I forgot I still have one question here: On Sun, Mar 06, 2016 at 10:02:14PM +0530, Bharat Kumar Gogada wrote: > Adding PCIe Root Port driver for Xilinx PCIe NWL bridge IP. > +static bool nwl_pcie_valid_device(struct pci_bus *bus, unsigned int devfn) > +{ > + struct nwl_pcie *pcie

[net-next PATCH 3/3] GSO/UDP: Use skb->len instead of udph->len to determine length of original skb

It is possible for tunnels to end up generating IP or IPv6 datagrams that are larger than 64K and expecting to be segmented. As such we need to deal with length values greater than 64K. In order to accommodate this we need to update the code to work with a 32b length value instead of a 16b one.

[net-next PATCH 2/3] ipv6: Pass proto to csum_ipv6_magic as __u8 instead of unsigned short

This patch updates csum_ipv6_magic so that it correctly recognizes that protocol is a unsigned 8 bit value. This will allow us to better understand what limitations may or may not be present in how we handle the data. For example there are a number of places that call htonl on the protocol

[net-next PATCH 0/3] Fix differences between IPv4 and IPv6 TCP/UDP checksum calculation

This patch series is meant to address the differences that exist between IPv4 and IPv6 in terms of checksum calculation. Specifically the IPv6 function csum_ipv6_magic treated length as a value that could be greater than 64K, while csum_tcpudp_magic was truncating the length at 16 bits. After

[net-next PATCH 1/3] ipv4: Update parameters for csum_tcpudp_magic to their original types

This patch updates all instances of csum_tcpudp_magic and csum_tcpudp_nofold to reflect the types that are usually used as the source inputs. For example the protocol field is populated based on nexthdr which is actually an unsigned 8 bit value. The length is usually populated based on skb->len

[PATCH v11 05/13] task_isolation: support CONFIG_TASK_ISOLATION_ALL

This option, similar to NO_HZ_FULL_ALL, simplifies configuring a system to boot by default with all cores except the boot core running in task isolation mode. Signed-off-by: Chris Metcalf --- init/Kconfig | 10 ++ kernel/isolation.c | 6 ++ 2 files

[PATCH v11 06/13] task_isolation: support PR_TASK_ISOLATION_STRICT mode

With task_isolation mode, the task is in principle guaranteed not to be interrupted by the kernel, but only if it behaves. In particular, if it enters the kernel via system call, page fault, or any of a number of other synchronous traps, it may be unexpectedly exposed to long latencies. Add a

[PATCH v11 12/13] arm64: factor work_pending state machine to C

Currently ret_fast_syscall, work_pending, and ret_to_user form an ad-hoc state machine that can be difficult to reason about due to duplicated code and a large number of branch targets. This patch factors the common logic out into the existing do_notify_resume function, converting the code to C

[PATCH v11 09/13] arm, tile: turn off timer tick for oneshot_stopped state

When the schedule tick is disabled in tick_nohz_stop_sched_tick(), we call hrtimer_cancel(), which eventually calls down into __remove_hrtimer() and thus into hrtimer_force_reprogram(). That function's call to tick_program_event() detects that we are trying to set the expiration to KTIME_MAX and

Re: Variant symlink filesystem

On 12 March 2016 at 00:24, Al Viro wrote: > On Sat, Mar 12, 2016 at 12:03:11AM +0200, Cole wrote: > >> This was one of the first solutions we looked at, and using various >> namespaces. However we would like to be able to have multiple terminal >> sessions open, and be

Re: [PATCH 2/2] block: create ioctl to discard-or-zeroout a range of blocks

On Fri, Mar 11, 2016 at 10:25:30AM -0800, Linus Torvalds wrote: > On Fri, Mar 11, 2016 at 9:30 AM, Andy Lutomirski wrote: > > > > What if we had an ioctl to do these data-leaking operations that took, > > as an extra parameter, an fd to the block device node. They allow > >

Re: Variant symlink filesystem

On Sat, 12 Mar 2016, Cole wrote: On 12 March 2016 at 00:24, Al Viro wrote: On Sat, Mar 12, 2016 at 12:03:11AM +0200, Cole wrote: This was one of the first solutions we looked at, and using various namespaces. However we would like to be able to have multiple

Re: [PATCH V6 0/6] Intel memory b/w monitoring support

On Fri, 11 Mar 2016, Peter Zijlstra wrote: On Thu, Mar 10, 2016 at 03:32:06PM -0800, Vikas Shivappa wrote: The patch series has two preparatory patch for cqm and then 4 MBM patches. Patches are based on tip perf/core. They were not (or at least not a recent copy of it); all the files got

RE: [PATCH V6 0/6] Intel memory b/w monitoring support

> Please see if the branch below works for you: > > git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git perf/core tragically no :-( The instant I started perf stat to trace some MBM events, I got a panic. But I think something went awry with the base version you applied these

Re: [PATCH 1/2 V2] staging: dgnc: use pointer type of tty_struct

On Mon, Mar 07, 2016 at 04:52:47PM +0900, Daeseok Youn wrote: > For using tty_alloc_driver, SerialDriver has to be pointer type. > It also has checkpatch.pl warning about Camelcase, so > SerialDriver is changed to serial_driver. Please only fix one thing per patch. This should be two different

Re: [PATCH] x86/FPU: Fix FPU handling on legacy FPU machines

On Fri, Mar 11, 2016 at 02:07:19PM -0800, Dave Hansen wrote: > I've actually got 4.0 running on my Quark board. The FPU rewrite > dropped in just after that iirc. 4.2 or so... Ok, so it looks like we broke it then. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.

Re: [RFC PATCH 1/3] siox: new driver/bus framework for Eckelmann SIOX

On Fri, Mar 11, 2016 at 10:52:12PM +0100, Uwe Kleine-König wrote: > Signed-off-by: Uwe Kleine-König > --- > drivers/Kconfig | 2 + > drivers/Makefile | 1 + > drivers/siox/Kconfig | 2 + > drivers/siox/Makefile| 1 + >

[PATCHv4 01/25] mm: do not pass mm_struct into handle_mm_fault

We always have vma->vm_mm around. Signed-off-by: Kirill A. Shutemov --- arch/alpha/mm/fault.c | 2 +- arch/arc/mm/fault.c | 2 +- arch/arm/mm/fault.c | 2 +- arch/arm64/mm/fault.c | 2 +- arch/avr32/mm/fault.c | 2

[PATCHv4 02/25] mm: introduce fault_env

The idea borrowed from Peter's patch from patchset on speculative page faults[1]: Instead of passing around the endless list of function arguments, replace the lot with a single structure so we can change context without endless function signature changes. The changes are mostly mechanical with

[PATCHv4 16/25] thp, mlock: do not mlock PTE-mapped file huge pages

As with anon THP, we only mlock file huge pages if we can prove that the page is not mapped with PTE. This way we can avoid mlock leak into non-mlocked vma on split. We rely on PageDoubleMap() under lock_page() to check if the the page may be PTE mapped. PG_double_map is set by

Re: [PATCH] usb: gadget: f_midi: Fixed a bug when buflen was smaller than wMaxPacketSize

On Wed, Mar 09 2016, Felipe F. Tonello wrote: > buflen by default (256) is smaller than wMaxPacketSize (512) in high-speed > devices. > > That caused the OUT endpoint to freeze if the host send any data packet of > length greater than 256 bytes. > > This is an example dump of what happended on

Re: runtime regression with "x86/mm/pat: Emulate PAT when it is disabled"

On Fri, 2016-03-11 at 17:28 -0500, Bruce Ashfield wrote: > On 2016-03-11 5:16 PM, Borislav Petkov wrote: > > On Fri, Mar 11, 2016 at 08:18:23PM +0100, Paolo Bonzini wrote: > > > Somebody got it wrong 10-ish years ago, and nobody has ever > > > checked since. > > > > > > But, don't use qemu32 or

Re: Variant symlink filesystem

On 11 March 2016 at 22:24, Richard Weinberger wrote: > Am 11.03.2016 um 21:22 schrieb Cole: >> If I remember correctly, when we were testing the fuse version, we hard coded >> the path to see if that solved the problem, and the difference between >> the env lookup >> code and the

[PATCH 0/1] KVM: x86: using the fpu in interrupt context with a guest's xcr0

We've found that an interrupt handler that uses the fpu can kill a KVM VM, if it runs under the following conditions: - the guest's xcr0 register is loaded on the cpu - the guest's fpu context is not loaded - the host is using eagerfpu Note that the guest's xcr0 register and fpu context are

[PATCH 1/1] KVM: don't allow irq_fpu_usable when the VCPU's XCR0 is loaded

From: Eric Northup Add a percpu boolean, tracking whether a KVM vCPU is running on the host CPU. KVM will set and clear it as it loads/unloads guest XCR0. (Note that the rest of the guest FPU load/restore is safe, because kvm_load_guest_fpu and kvm_put_guest_fpu call

Re: Overlapping ioremap() calls, set_memory_*() semantics

Hi Ingo, My apology for the delay... On Wed, 2016-03-09 at 10:15 +0100, Ingo Molnar wrote: > * Toshi Kani wrote: > > > On Tue, 2016-03-08 at 13:16 +0100, Ingo Molnar wrote: > > > * Toshi Kani wrote: > > > > > > > > So where is the problem? The memtype

Re: [PATCH 2/2] Staging: nvec: fix multiline comment style.

On Thu, Mar 10, 2016 at 12:42:29PM +0530, Neha Rani wrote: > This is a patch in nvec.c file that fixes a multiline comment found by > checkpatch.pl tool > > Signed-off-by: Neha Rani > --- > drivers/staging/nvec/nvec.c | 6 -- > 1 file changed, 4 insertions(+), 2

Re: [PATCH] staging/android: change IOCTLs opcode after ABI change

On Thu, Mar 03, 2016 at 07:42:43PM -0300, Gustavo Padovan wrote: > From: Gustavo Padovan > > Burn the old opcode to avoid any potential old userspace running the old > API to get weird errors. Changing the opcodes will make them fail right > away. > > This is

Re: [PATCH V14 5/9] dma: qcom_hidma: implement lower level hardware interface

Vinod, On 3/11/2016 2:29 PM, Sinan Kaya wrote: > I have done the renaming. This is all left for me to post a follow up. I just posted v15 (forgot to put v15 on 4/4). http://www.spinics.net/lists/arm-kernel/msg490282.html I wanted to get v15 out before the end of the week with the macro

Re: runtime regression with "x86/mm/pat: Emulate PAT when it is disabled"

On 2016-03-11 5:16 PM, Borislav Petkov wrote: On Fri, Mar 11, 2016 at 08:18:23PM +0100, Paolo Bonzini wrote: Somebody got it wrong 10-ish years ago, and nobody has ever checked since. But, don't use qemu32 or qemu64. Use kvm32 and kvm64, or better something like the host you run on ("-cpu

Re: Variant symlink filesystem

On Fri, 11 Mar 2016, Cole wrote: On 11 March 2016 at 22:24, Richard Weinberger wrote: Am 11.03.2016 um 21:22 schrieb Cole: If I remember correctly, when we were testing the fuse version, we hard coded the path to see if that solved the problem, and the difference between the

Re: [v8,07/23] powerpc/8xx: Fix vaddr for IMMR early remap

On Tue, Feb 09, 2016 at 05:08:00PM +0100, Christophe Leroy wrote: > Memory: 124428K/131072K available (3748K kernel code, 188K rwdata, > 648K rodata, 508K init, 290K bss, 6644K reserved) > Kernel virtual memory layout: > * 0xfffdf000..0xf000 : fixmap > * 0xfde0..0xfe00 :

[PATCHv4 08/25] thp: support file pages in zap_huge_pmd()

split_huge_pmd() for file mappings (and DAX too) is implemented by just clearing pmd entry as we can re-fill this area from page cache on pte level later. This means we don't need deposit page tables when file THP is mapped. Therefore we shouldn't try to withdraw a page table on zap_huge_pmd()

[PATCHv4 20/25] filemap: prepare find and delete operations for huge pages

For now, we would have HPAGE_PMD_NR entries in radix tree for every huge page. That's suboptimal and it will be changed to use Matthew's multi-order entries later. 'add' operation is not changed, because we don't need it to implement hugetmpfs: shmem uses its own implementation. Signed-off-by:

[PATCHv4 04/25] rmap: support file thp

Naive approach: on mapping/unmapping the page as compound we update ->_mapcount on each 4k page. That's not efficient, but it's not obvious how we can optimize this. We can look into optimization later. PG_double_map optimization doesn't work for file pages since lifecycle of file pages is

Re: [PATCH v2] tty: amba-pl011: Use 32-bit accesses for SBSA UART

On March 11, 2016 10:02:14 PM GMT+07:00, Peter Hurley wrote: >Hi Christopher, > >On 03/10/2016 10:35 PM, Christopher Covington wrote: >> Version 2 of the Server Base System Architecture (SBSAv2) describes >the >> Generic UART registers as 32 bits wide. At least one

Re: Glibc recvmsg from kernel netlink socket hangs forever

On Fri, Mar 11, 2016 at 11:33:17AM -0800, Jun Wang wrote: > > On 09/25/2015 08:55 AM, Herbert Xu wrote: > >> On Thu, Sep 24, 2015 at 10:34:10PM -0700, Guenter Roeck wrote: > >>> > >>> Any idea what may be needed for 4.1 ? > >>> I am currently trying https://patchwork.ozlabs.org/patch/473041/, > >>

[PATCH] dmaengine: fsl-edma: disable clks in case of failure in probe

fsl_edma_probe() does not disable already enabled clocks in case of failure. The patch fixes that. Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey Khoroshilov --- drivers/dma/fsl-edma.c | 27 +++ 1 file

[PATCH] Driver: Vmxnet3: Fix regression caused by cec0556

don't pass uninitialized flags to spin_unlock_irqrestore. Reported-by: Tetsuo Handa Signed-off-by: Shrikrishna Khare Signed-off-by: Guolin Yang --- drivers/net/vmxnet3/vmxnet3_drv.c | 9 -

[RFC PATCH 2/3] siox: add gpio bus driver

Signed-off-by: Uwe Kleine-König --- drivers/siox/Kconfig | 7 ++ drivers/siox/Makefile| 1 + drivers/siox/siox-bus-gpio.c | 168 +++ 3 files changed, 176 insertions(+) create mode 100644

[RFC PATCH 1/3] siox: new driver/bus framework for Eckelmann SIOX

Signed-off-by: Uwe Kleine-König --- drivers/Kconfig | 2 + drivers/Makefile | 1 + drivers/siox/Kconfig | 2 + drivers/siox/Makefile| 1 + drivers/siox/siox-core.c | 572 +++

Re: [PATCH] staging/android: add flags member to sync ioctl structs

On Fri, Mar 04, 2016 at 05:40:29PM +0100, Daniel Vetter wrote: > On Thu, Mar 03, 2016 at 08:17:14AM -0800, Greg Kroah-Hartman wrote: > > On Thu, Mar 03, 2016 at 11:37:17AM -0300, Gustavo Padovan wrote: > > > From: Gustavo Padovan > > > > > > Play safe and add

Re: [PATCH 1/3] net: thunderx: Cleanup PHY probing code.

On 03/11/2016 01:35 PM, Andrew Lunn wrote: [...] How usable is the hardware without a PHY driver? The hardware has always in the past, still does, and probably always will work fine without a PHY driver. Link up/down are correctly handled. Is a better solution that your write a very

Re: [PATCH 2/2] x86/mtrr: Refactor PAT initialization code

On Fri, Mar 11, 2016 at 11:57:12AM -0700, Toshi Kani wrote: > On Fri, 2016-03-11 at 10:24 +0100, Borislav Petkov wrote: > > On Thu, Mar 10, 2016 at 09:45:46PM -0700, Toshi Kani wrote: > > > MTRR manages PAT initialization as it implements a rendezvous > > > handler that initializes PAT as part of

Re: runtime regression with "x86/mm/pat: Emulate PAT when it is disabled"

On Fri, Mar 11, 2016 at 08:18:23PM +0100, Paolo Bonzini wrote: > Somebody got it wrong 10-ish years ago, and nobody has ever checked since. > > But, don't use qemu32 or qemu64. Use kvm32 and kvm64, or better > something like the host you run on ("-cpu Nehalem", "-cpu SandyBridge", > "-cpu

Re: [PATCH v14] x86, mce: Add memcpy_mcsafe()

On Fri, Mar 11, 2016 at 2:10 PM, Tony Luck wrote: > On Thu, Mar 10, 2016 at 11:37 AM, Luck, Tony wrote: >>> But you return 0 == false for success and 1 == true for failure. >> >> Aaargh! -ETOOMUCHSHELLSCRIPTPROGRAMMING >> >> -Tony > > Options to fix

[PATCH v11 02/13] vmstat: add vmstat_idle function

This function checks to see if a vmstat worker is not running, and the vmstat diffs don't require an update. The function is called from the task-isolation code to see if we need to actually do some work to quiet vmstat. Acked-by: Christoph Lameter Signed-off-by: Chris Metcalf

[PATCH v11 04/13] task_isolation: add initial support

The existing nohz_full mode is designed as a "soft" isolation mode that makes tradeoffs to minimize userspace interruptions while still attempting to avoid overheads in the kernel entry/exit path, to provide 100% kernel semantics, etc. However, some applications require a "hard" commitment from

[PATCH v11 03/13] lru_add_drain_all: factor out lru_add_drain_needed

This per-cpu check was being done in the loop in lru_add_drain_all(), but having it be callable for a particular cpu is helpful for the task-isolation patches. Signed-off-by: Chris Metcalf --- include/linux/swap.h | 1 + mm/swap.c| 15 ++- 2 files

[PATCHv4 24/25] shmem: add huge pages support

Here's basic implementation of huge pages support for shmem/tmpfs. It's all pretty streight-forward: - shmem_getpage() allcoates huge page if it can and try to inserd into radix tree with shmem_add_to_page_cache(); - shmem_add_to_page_cache() puts the page onto radix-tree if there's

[PATCHv4 11/25] thp: handle file pages in mremap()

We need to mirror logic in move_ptes() wrt need_rmap_locks to get proper serialization file THP. Signed-off-by: Kirill A. Shutemov --- mm/mremap.c | 22 -- 1 file changed, 16 insertions(+), 6 deletions(-) diff --git a/mm/mremap.c

[PATCHv4 07/25] thp, vmstats: add counters for huge file pages

THP_FILE_ALLOC: how many times huge page was allocated and put page cache. THP_FILE_MAPPED: how many times file huge page was mapped. Signed-off-by: Kirill A. Shutemov --- include/linux/vm_event_item.h | 7 +++ mm/memory.c | 1 +

[PATCHv4 17/25] vmscan: split file huge pages before paging them out

This is preparation of vmscan for file huge pages. We cannot write out huge pages, so we need to split them on the way out. Signed-off-by: Kirill A. Shutemov --- mm/vmscan.c | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git

[PATCHv4 18/25] page-flags: relax policy for PG_mappedtodisk and PG_reclaim

These flags are in use for file THP. Signed-off-by: Kirill A. Shutemov --- include/linux/page-flags.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/include/linux/page-flags.h b/include/linux/page-flags.h index

Re: [PATCH] x86, pmem: use memcpy_mcsafe() for memcpy_from_pmem()

On Fri, Mar 11, 2016 at 2:50 PM, Ross Zwisler wrote: > On Thu, Mar 10, 2016 at 11:15:53AM -0800, Dan Williams wrote: >> Update the definition of memcpy_from_pmem() to return 0 or -EIO on >> error. Implement x86::arch_memcpy_from_pmem() with memcpy_mcsafe(). >> >>

Re: [PATCH 2/2] x86/mtrr: Refactor PAT initialization code

On Fri, Mar 11, 2016 at 3:56 PM, Toshi Kani wrote: > On Fri, 2016-03-11 at 23:17 +0100, Luis R. Rodriguez wrote: >> On Fri, Mar 11, 2016 at 11:57:12AM -0700, Toshi Kani wrote: >> > On Fri, 2016-03-11 at 10:24 +0100, Borislav Petkov wrote: >> > > On Thu, Mar 10, 2016 at

[PATCH v2] dell-rbtn: Ignore ACPI notifications if device is suspended

Some BIOSes unconditionally send an ACPI notification to RBTN when the system is resuming from suspend. This makes dell-rbtn send an input event to userspace as if a function key was pressed. Prevent this by ignoring all the notifications received while the device is suspended. Link:

Re: [PATCH] epoll: add exclusive wakeups flag

>> By the way, in the code you have >> >> case EPOLL_CTL_MOD: >> if (epi) { >> if (!(epi->event.events & EPOLLEXCLUSIVE)) { >> epds.events |= POLLERR | POLLHUP; >> error = ep_modify(ep,

Re: [PATCH 1/3] net: thunderx: Cleanup PHY probing code.

> For this phy, we have: > > compatible = "cortina,cs4223-slice"; That actually means something else is happening, i think. of_mdiobus_register() looks at the children, and decides if each child is a phy or an mdio device, by calling of_mdiobus_child_is_phy(). Since this compatible string is

[RFC PATCH 3/3] gpio: new driver to work with a 8x12 siox

Signed-off-by: Uwe Kleine-König --- drivers/gpio/Kconfig | 5 + drivers/gpio/Makefile| 1 + drivers/gpio/gpio-siox.c | 280 +++ 3 files changed, 286 insertions(+) create mode 100644 drivers/gpio/gpio-siox.c

[RFC PATCH 0/3] new bus type siox

Hello, this is a patch set for a new bus type called SIOX created by the German company Eckelmann. This is a bus with four data lines. The signales DIN (from devices to master) and DOUT (from master to devices) are daisy chained through all devices. DLD and DCLK are shared. A pulse on DCLK pushs

Re: [PATCH] x86/FPU: Fix FPU handling on legacy FPU machines

On 03/11/2016 02:03 PM, Borislav Petkov wrote: > I'm still wondering, though, why didn't the Quark people scream > earlier... And who knows, it was probably b0rked even before the > FPU rewrite. I've actually got 4.0 running on my Quark board. The FPU rewrite dropped in just after that iirc.

[PATCH v11 07/13] task_isolation: add debug boot flag

The new "task_isolation_debug" flag simplifies debugging of TASK_ISOLATION kernels when processes are running in PR_TASK_ISOLATION_ENABLE mode. Such processes should get no interrupts from the kernel, and if they do, we notify either the process (if STRICT mode is set and the interrupt is not an

[PATCH v11 11/13] arch/tile: enable task isolation functionality

We add the necessary call to task_isolation_enter() in the prepare_exit_to_usermode() routine. We already unconditionally call into this routine if TIF_NOHZ is set, since that's where we do the user_enter() call. We add calls to task_isolation_check_exception() in places where exceptions may not

[PATCH v11 10/13] arch/x86: enable task isolation functionality

In prepare_exit_to_usermode(), call task_isolation_ready() for TIF_TASK_ISOLATION tasks when we are checking the thread-info flags, and after we've handled the other work, call task_isolation_enter() for such tasks. In syscall_trace_enter_phase1(), we add the necessary support for strict-mode

[PATCH v11 08/13] task_isolation: add PR_TASK_ISOLATION_ONE_SHOT flag

When this flag is set by the initial prctl(), the semantics of task isolation change to be "one-shot", i.e. as soon as the kernel is re-entered for any reason, task isolation is turned off. During application development, use of this flag is best coupled with STRICT mode, since otherwise any bug

[PATCH v11 13/13] arch/arm64: enable task isolation functionality

In do_notify_resume(), call task_isolation_ready() for TIF_TASK_ISOLATION tasks when we are checking the thread-info flags; and after we've handled the other work, call task_isolation_enter() for such tasks. To ensure we always call task_isolation_enter() when returning to userspace, add

Re: [PATCH v14] x86, mce: Add memcpy_mcsafe()

On Thu, Mar 10, 2016 at 11:37 AM, Luck, Tony wrote: >> But you return 0 == false for success and 1 == true for failure. > > Aaargh! -ETOOMUCHSHELLSCRIPTPROGRAMMING > > -Tony Options to fix this: 1) Just change the comments in the code. This seems like it would confuse

[PATCH v11 01/13] vmstat: add quiet_vmstat_sync function

In commit f01f17d3705b ("mm, vmstat: make quiet_vmstat lighter") the quiet_vmstat() function became asynchronous, in the sense that the vmstat work was still scheduled to run on the core when the function returned. For task isolation, we need a synchronous version of the function that guarantees

[PATCHv4 03/25] mm: postpone page table allocation until we have page to map

The idea (and most of code) is borrowed again: from Hugh's patchset on huge tmpfs[1]. Instead of allocation pte page table upfront, we postpone this until we have page to map in hands. This approach opens possibility to map the page as huge if filesystem supports this. Comparing to Hugh's patch

[PATCHv4 12/25] thp: skip file huge pmd on copy_huge_pmd()

copy_page_range() has a check for "Don't copy ptes where a page fault will fill them correctly." It works on VMA level. We still copy all page table entries from private mappings, even if they map page cache. We can simplify copy_huge_pmd() a bit by skipping file PMDs. We don't map file private

Re: [v8, 08/23] powerpc/8xx: Map IMMR area with 512k page at a fixed address

On Tue, Feb 09, 2016 at 05:08:02PM +0100, Christophe Leroy wrote: > Once the linear memory space has been mapped with 8Mb pages, as > seen in the related commit, we get 11 millions DTLB missed during > the reference 600s period. 77% of the misses are on user addresses > and 23% are on kernel

Re: [PATCH v1 00/12] PCI: Rework shadow ROM handling

On Fri, Mar 11, 2016 at 01:16:09PM -0800, Andy Lutomirski wrote: > On Tue, Mar 8, 2016 at 9:45 AM, Bjorn Helgaas wrote: > > On Thu, Mar 03, 2016 at 10:53:50AM -0600, Bjorn Helgaas wrote: > >> The purpose of this series is to: > >> > >> - Fix the "BAR 6: [??? 0x flags

Re: [PATCH v2] cpufreq: Make cpufreq_quick_get() safe to call.

On 11-03-16, 09:43, Richard Cochran wrote: > The function, cpufreq_quick_get, accesses the global 'cpufreq_driver' and > its fields without taking the associated lock, cpufreq_driver_lock. > > Without the locking, nothing guarantees that 'cpufreq_driver' remains > consistent during the call.

Re: Variant symlink filesystem

On 2016-03-11 15:24, Richard Weinberger wrote: Am 11.03.2016 um 21:22 schrieb Cole: If I remember correctly, when we were testing the fuse version, we hard coded the path to see if that solved the problem, and the difference between the env lookup code and the hard coded path was almost the

Re: [PATCH 1/3] net: thunderx: Cleanup PHY probing code.

On 03/11/2016 11:37 AM, Florian Fainelli wrote: On 11/03/16 11:06, Andrew Lunn wrote: I don't see why it should wait around forever. I have boards with Marvell PHYs, yet if i don't build the Marvell driver, the Ethernet driver still loads, because the generic PHY driver is used instead. Why

[git pull] drm i915 fixes

Hi Linus, Just two i915 regression fixes, that should be it from me. Dave. The following changes since commit 2a4fb270daa9c1f1d1b86a53d66ed86cc64ad232: Merge tag 'armsoc-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2016-03-11 12:35:54 -0800) are available in the

Re: [PATCH 1/1] KVM: don't allow irq_fpu_usable when the VCPU's XCR0 is loaded

On Fri, Mar 11, 2016 at 12:47 PM, David Matlack wrote: > From: Eric Northup > > Add a percpu boolean, tracking whether a KVM vCPU is running on the > host CPU. KVM will set and clear it as it loads/unloads guest XCR0. > (Note that the rest of the

Re: [PATCH v10 01/59] PCI: Add pci_find_root_bus_resource()

Hi Bjorn, Thanks for taking time to look at those patches! On Wed, Mar 9, 2016 at 7:54 PM, Bjorn Helgaas wrote: > On Wed, Feb 24, 2016 at 06:11:52PM -0800, Yinghai Lu wrote: >> Add pci_find_root_bus_resource() to return root bus resource >> for input resource. >> >> For

Re: [PATCH 1/1] staging: android: Fixed coding style issues reported by checkpatch

On Wed, Mar 09, 2016 at 01:55:01AM +0530, Saiyam Doshi wrote: > On Sun, Mar 06, 2016 at 05:21:08PM -0800, Greg KH wrote: > > You need to do only one thing per patch, please split this up into > > multiple patches. > > Created two separate patches out of it having same logical change in each. You

Re: Variant symlink filesystem

On 11 March 2016 at 23:51, Al Viro wrote: > On Fri, Mar 11, 2016 at 10:52:52PM +0200, Cole wrote: > >> The implementation doesn't necessarily have to continue to work with >> env variables. On FreeBSD, the variant symlinks function by using >> variables stored in kernel

Re: [PATCH] x86/FPU: Fix FPU handling on legacy FPU machines

On Fri, Mar 11, 2016 at 10:32:43AM -0800, Linus Torvalds wrote: > Obvious Ack to the patch, along with a "how did this ever work > before?" comment.. I had a sarcastic sentence in the commit message which I deleted later: "Apparently no one had tried the kernel on a 486er after the FPU rewrite.

  1   2   3   4   5   6   7   8   9   10   >