Re: [PATCH v3 1/5] perf tools: Add all matching dynamic sort keys for field name

Hi Arnaldo and Jiri, On Wed, Jan 06, 2016 at 01:29:48PM -0300, Arnaldo Carvalho de Melo wrote: > Em Wed, Jan 06, 2016 at 12:19:39PM +0100, Jiri Olsa escreveu: > > On Wed, Jan 06, 2016 at 09:54:57AM +0900, Namhyung Kim wrote: > > > When a perf.data file has multiple events, it's likely to be

Re: [PATCH] Fix documentation for adp1653 DT

On Sat, Dec 26, 2015 at 12:37:16AM +0100, Pali Rohár wrote: > Property names do not match real names needed by driver itself. > This patch fix this problem. > > Signed-off-by: Pali Rohár Applied, thanks. Rob > --- > .../devicetree/bindings/media/i2c/adp1653.txt |

[PATCH v3] ARM: fix atags_to_fdt with stack-protector-strong

Building with CONFIG_CC_STACKPROTECTOR_STRONG triggers protection code generation under CONFIG_ARM_ATAG_DTB_COMPAT but this is too early for being able to use any of the stack_chk code. Explicitly disable it for only the atags_to_fdt bits. Suggested-by: zhxihu Signed-off-by:

Re: [PATCH] Input: ALPS - Detect trackstick presence for v7 protocol

On Wed, Jan 06, 2016 at 09:12:30AM +0100, Hans de Goede wrote: > Hi, > > On 05-01-16 17:44, Pali Rohár wrote: > >On Sunday 22 March 2015 14:46:11 Pali Rohár wrote: > >>This patch adds detection of trackstick for v7 protocol devices. Code in > >>this > >>patch is used in official Dell touchpad

weird DirectMap2M accounting.

I just spotted this in /proc/meminfo on an old Core2 machine with 4G. DirectMap2M:18446744073709543424 kB Looks like we subtracted 8192 from 0 somewhere. Should split_page_count() be checking that direct_pages_count > 0 ? Dave -- To unsubscribe from this list: send the line

[PATCH 09/31] x86, pkeys: store protection in high VMA flags

From: Dave Hansen vma->vm_flags is an 'unsigned long', so has space for 32 flags on 32-bit architectures. The high 32 bits are unused on 64-bit platforms. We've steered away from using the unused high VMA bits for things because we would have difficulty supporting

[PATCH 12/31] signals, pkeys: notify userspace about protection key faults

From: Dave Hansen A protection key fault is very similar to any other access error. There must be a VMA, etc... We even want to take the same action (SIGSEGV) that we do with a normal access fault. However, we do need to let userspace know that something is

Re: [PATCH] Input: ALPS - Report v3 pinnacle trackstick device only if is present

On Tue, Jan 05, 2016 at 05:54:19PM +0100, Pali Rohár wrote: > On Monday 23 March 2015 12:42:25 Hans de Goede wrote: > > Hi, > > > > On 22-03-15 14:47, Pali Rohár wrote: > > >This patch move v3 pinnacle code for trackstick detection from > > >alps_hw_init_v3() > > >to alps_set_protocol() so

[PATCH 01/31] mm, gup: introduce concept of "foreign" get_user_pages()

From: Dave Hansen For protection keys, we need to understand whether protections should be enforced in software or not. In general, we enforce protections when working on our own task, but not when on others. We call these "current" and "foreign" operations. This

[PATCH 00/31] x86: Memory Protection Keys (v8)

Memory Protection Keys for User pages is a CPU feature which will first appear on Skylake Servers, but will also be supported on future non-server parts (there is also a QEMU implementation). It provides a mechanism for enforcing page-based protections, but without requiring modification of the

[PATCH 04/31] x86, pkeys: cpuid bit definition

From: Dave Hansen There are two CPUID bits for protection keys. One is for whether the CPU contains the feature, and the other will appear set once the OS enables protection keys. Specifically: Bit 04: OSPKE. If 1, OS has set CR4.PKE to enable

Re: [PATCH] PCI: iproc: fix msi driver selection

On Fri, Dec 18, 2015 at 03:57:53PM +0100, Arnd Bergmann wrote: > The newly added MSI support for iproc causes a link error when its > Kconfig option is disabled: > > ERROR: "iproc_msi_exit" [drivers/pci/host/pcie-iproc.ko] undefined! > ERROR: "iproc_msi_init" [drivers/pci/host/pcie-iproc.ko]

[PATCH 05/31] x86, pkeys: define new CR4 bit

From: Dave Hansen There is a new bit in CR4 for enabling protection keys. We will actually enable it later in the series. Signed-off-by: Dave Hansen Reviewed-by: Thomas Gleixner ---

[PATCH 07/31] x86, pkeys: PTE bits for storing protection key

From: Dave Hansen Previous documentation has referred to these 4 bits as "ignored". That means that software could have made use of them. But, as far as I know, the kernel never used them. They are still ignored when protection keys is not enabled, so they could

[PATCH 02/31] x86, fpu: add placeholder for Processor Trace XSAVE state

From: Dave Hansen There is an XSAVE state component for Intel Processor Trace (PT). But, we do not currently use it. We add a placeholder in the code for it so it is not a mystery and also so we do not need an explicit enum initialization for Protection Keys in a

Re: [PATCH v2 31/32] sh: support a 2-byte smp_store_mb

On Wed, Jan 06, 2016 at 01:23:50PM -0500, Rich Felker wrote: > On Wed, Jan 06, 2016 at 03:32:18PM +0100, Peter Zijlstra wrote: > > On Wed, Jan 06, 2016 at 01:52:17PM +0200, Michael S. Tsirkin wrote: > > > > > Peter, what do you think? How about I leave this patch as is for now? > > > > > > > >

blog post: Monitoring real-time latencies

Hi, Here is a blog post related to detecting and understanding high interrupt-processing latencies on real-time systems. It is based on a new project called latency_tracker that hooks on the existing kernel tracepoints and executes actions when high latency events occur.

Re: [PATCH 1/3] jffs2: use to_delayed_work

On Fri, Jan 01, 2016 at 10:06:27PM +0800, Geliang Tang wrote: > Use to_delayed_work() instead of open-coding it. > > Signed-off-by: Geliang Tang Applied to l2-mtd.git -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to

Re: [PATCH 02/35] block: add REQ_OP definitions and bi_op/op fields

> "Mike" == mchristi writes: +enum req_op { + REQ_OP_READ, + REQ_OP_WRITE= REQ_WRITE, + REQ_OP_DISCARD = REQ_DISCARD, + REQ_OP_WRITE_SAME = REQ_WRITE_SAME, +}; + I have been irked by the REQ_ prefix in bios since the

Re: [PATCHv1 6/6] rdmacg: Added documentation for rdma controller.

Hello, On Thu, Jan 07, 2016 at 04:14:26AM +0530, Parav Pandit wrote: > Yes. I read through. I can see two changes to be made in V2 version of > this patch. > 1. rdma.resource.verb.usage and rdma.resource.verb.limit to change > respectively to, > 2. rdma.resource.verb.stat and

Re: [PATCH v3 5/5] perf evlist: Add --trace-fields option to show trace fields

On Wed, Jan 06, 2016 at 08:29:49PM -0300, Arnaldo Carvalho de Melo wrote: > Em Thu, Jan 07, 2016 at 08:21:44AM +0900, Namhyung Kim escreveu: > > On Wed, Jan 06, 2016 at 08:10:51PM -0300, Arnaldo Carvalho de Melo wrote: > > > Em Wed, Jan 06, 2016 at 09:55:01AM +0900, Namhyung Kim escreveu: > > > >

Re: [PATCH v2 31/32] sh: support a 2-byte smp_store_mb

On Wed, Jan 06, 2016 at 10:23:12PM +0200, Michael S. Tsirkin wrote: > On Wed, Jan 06, 2016 at 01:23:50PM -0500, Rich Felker wrote: > > On Wed, Jan 06, 2016 at 03:32:18PM +0100, Peter Zijlstra wrote: > > > On Wed, Jan 06, 2016 at 01:52:17PM +0200, Michael S. Tsirkin wrote: > > > > > > Peter, what

[PATCH 17/31] x86, pkeys: check VMAs and PTEs for protection keys

From: Dave Hansen Today, for normal faults and page table walks, we check the VMA and/or PTE to ensure that it is compatible with the action. For instance, if we get a write fault on a non-writeable VMA, we SIGSEGV. We try to do the same thing for protection keys.

[PATCH 21/31] x86, pkeys: dump PKRU with other kernel registers

From: Dave Hansen Protection Keys never affect kernel mappings. But, they can affect whether the kernel will fault when it touches a user mapping. The kernel doesn't touch user mappings without some careful choreography and these accesses don't generally result in

[PATCH 19/31] x86, pkeys: optimize fault handling in access_error()

From: Dave Hansen We might not strictly have to make modifictions to access_error() to check the VMA here. If we do not, we will do this: 1. app sets VMA pkey to K 2. app touches a !present page 3. do_page_fault(), allocates and maps page, sets pte.pkey=K 4. return

Re: [PATCH 1/3] mtd: nand: pxa3xx_nand: add register access debug

On Sat, Dec 19, 2015 at 01:19:26PM +0100, Robert Jarzmik wrote: > Brian Norris writes: > > > I don't have very strong opinions on this. It's kind of annoying to have > > this sort of stuff duplicated for every driver, if it's really needed. > > But I'll admit this

[PATCH 22/31] x86, pkeys: dump pkey from VMA in /proc/pid/smaps

From: Dave Hansen The protection key can now be just as important as read/write permissions on a VMA. We need some debug mechanism to help figure out if it is in play. smaps seems like a logical place to expose it. arch/x86/kernel/setup.c is a bit of a weirdo

Re: [PATCH] X.509: Partially revert patch to add validation against IMA MOK keyring

> Partially revert commit 41c89b64d7184a780f12f2cccdabe65cb2408893: > > Author: Petko Manolov > Date: Wed Dec 2 17:47:55 2015 +0200 > IMA: create machine owner and blacklist keyrings > If you need this applied to a tree, please state which. -- James

Re: weird DirectMap2M accounting.

On Wed, Jan 06, 2016 at 06:55:27PM -0500, Dave Jones wrote: > I just spotted this in /proc/meminfo on an old Core2 machine with 4G. > > DirectMap2M:18446744073709543424 kB > > Looks like we subtracted 8192 from 0 somewhere. > > Should split_page_count() be checking that

[PATCH -next] serial: 8250: Fix serial port driver for OF platform devices

Commit afd7f88f1577 ("serial: 8250: move of_serial code to 8250 directory") moved the serial port driver for Open Firmware platform devices from one directory to another, but a mixup in Kconfig options resulted in the driver never being built. This results in runtime failures for some xtensa,

Re: linux-next: build failure after merge of the vfs tree

Hi all, On Mon, 21 Dec 2015 11:23:01 +1100 Stephen Rothwell wrote: > > On Thu, 10 Dec 2015 11:18:47 +1100 Stephen Rothwell > wrote: > > > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > >

[PATCH RESEND v4 05/11] staging: fsl-mc: Extended MC bus allocator to include IRQs

From: "J. German Rivera" All the IRQs for DPAA2 objects in the same DPRC must use the ICID of that DPRC, as their device Id in the GIC-ITS. Thus, all these IRQs must share the same ITT table in the GIC. As a result, a pool of IRQs with the same device Id must be

[PATCH RESEND v4 03/11] staging: fsl-mc: Added generic MSI support for FSL-MC devices

From: "J. German Rivera" Created an MSI domain for the fsl-mc bus-- including functions to create a domain, find a domain, alloc/free domain irqs, and bus specific overrides for domain and irq_chip ops. Signed-off-by: J. German Rivera

[PATCH RESEND v4 04/11] staging: fsl-mc: Added GICv3-ITS support for FSL-MC MSIs

From: "J. German Rivera" Added platform-specific MSI support layer for FSL-MC devices. Signed-off-by: J. German Rivera --- CHANGE HISTORY Changes in v4: - Addressed comments from Marc Zyngier: * Moved bus type check earlier in

[PATCH RESEND v4 11/11] staging: fsl-mc: Added MSI support to the MC bus driver

From: "J. German Rivera" Initialize/Cleanup ITS-MSI support for the MC bus driver at driver init/exit time. Associate an MSI domain with each DPAA2 child device. Signed-off-by: J. German Rivera --- CHANGE HISTORY Changes in v4: none

[PATCH 2/4] x86/fpu: Disable XGETBV1 when no XSAVE

When "noxsave" is given as a command-line input, the kernel should disable XGETBV1. This issue currently does not cause any actual problems. XGETBV1 is only useful if we have something using the 'init optimization' (i.e. xsaveopt, xsaves). We already clear both of those in

[PATCH 4/4] x86/fpu: Disable AVX when eagerfpu is off

When "eagerfpu=off" is given as a command-line input, the kernel should disable AVX support. The Task Switched bit used for lazy context switching does not support AVX. If AVX is enabled without eagerfpu context switching, one task's AVX state could become corrupted or leak to other tasks. This

[PATCH 3/4] x86/fpu: Disable MPX when eagerfpu is off

This issue is a fallout from the command-line parsing move. When "eagerfpu=off" is given as a command-line input, the kernel should disable MPX support. The decision for turning off MPX was made in fpu__init_system_ctx_switch(), which is after the selection of the XSAVE format. This patch fixes

Re: [PATCH] input: gpio_keys: Fix check for disabling unsupported key

On Tue, Jan 05, 2016 at 09:24:40AM +0200, Ivaylo Dimitrov wrote: > Hi, > > On 5.01.2016 03:19, Dmitry Torokhov wrote: > >>/* First validate */ > >>- for (i = 0; i < ddata->pdata->nbuttons; i++) { > >>- struct gpio_button_data *bdata = >data[i]; > >>+ for (i = 0; i < n_events;

Re: [PATCH] mtd: tests: consolidate kmalloc/memset 0 call to kzalloc

On Thu, Dec 31, 2015 at 04:21:22PM +0100, Nicholas Mc Guire wrote: > This is an API consolidation only. The use of kmalloc + memset to 0 > is equivalent to kzalloc. > > Signed-off-by: Nicholas Mc Guire Applied to l2-mtd.git -- To unsubscribe from this list: send the line

Re: [PATCH v3 5/5] perf evlist: Add --trace-fields option to show trace fields

Em Thu, Jan 07, 2016 at 08:21:44AM +0900, Namhyung Kim escreveu: > On Wed, Jan 06, 2016 at 08:10:51PM -0300, Arnaldo Carvalho de Melo wrote: > > Em Wed, Jan 06, 2016 at 09:55:01AM +0900, Namhyung Kim escreveu: > > > To use dynamic sort keys, it might be good to add an option to see the > > > list

[PATCH 31/31] x86, pkeys: execute-only support

From: Dave Hansen Protection keys provide new page-based protection in hardware. But, they have an interesting attribute: they only affect data accesses and never affect instruction fetches. That means that if we set up some memory which is set as "access-disabled"

[PATCH 18/31] mm: add gup flag to indicate "foreign" mm access

From: Dave Hansen We try to enforce protection keys in software the same way that we do in hardware. (See long example below). But, we only want to do this when accessing our *own* process's memory. If GDB set PKRU[6].AD=1 (disable access to PKEY 6), then tried

[PATCH 29/31] x86, pkeys: allow kernel to modify user pkey rights register

From: Dave Hansen The Protection Key Rights for User memory (PKRU) is a 32-bit user-accessible register. It contains two bits for each protection key: one to write-disable (WD) access to memory covered by the key and another to access-disable (AD). Userspace can

[PATCH 27/31] x86: separate out LDT init from context init

From: Dave Hansen The arch-specific mm_context_t is a great place to put protection-key allocation state. But, we need to initialize the allocation state because pkey 0 is always "allocated". All of the runtime initialization of mm_context_t is done in *_ldt()

[PATCH 25/31] mm, multi-arch: pass a protection key in to calc_vm_flag_bits()

From: Dave Hansen This plumbs a protection key through calc_vm_flag_bits(). We could have done this in calc_vm_prot_bits(), but I did not feel super strongly which way to go. It was pretty arbitrary which one to use. Signed-off-by: Dave Hansen

[PATCH 26/31] x86, pkeys: add arch_validate_pkey()

From: Dave Hansen The syscall-level code is passed a protection key and need to return an appropriate error code if the protection key is bogus. We will be using this in subsequent patches. Note that this also begins a series of arch-specific calls that we need to

[PATCH v4 5/5] perf evlist: Add --trace-fields option to show trace fields

To use dynamic sort keys, it might be good to add an option to see the list of field names. $ perf evlist -i perf.data.sched sched:sched_switch sched:sched_stat_wait sched:sched_stat_sleep sched:sched_stat_iowait sched:sched_stat_runtime sched:sched_process_fork sched:sched_wakeup

[PATCH v4 3/5] perf tools: Fix dynamic sort keys to sort properly

Currently, the dynamic sort keys compares trace data using memcmp(). But for output sorting, it should check data size and compare by word. Also it sorted strings in reverse order, fix it. Before) $ perf report -F overhead -s prev_pid,next_pid ... # Overheadprev_pidnext_pid #

[PATCH v4 1/5] perf tools: Fix sorting of dynamic sort keys

Currently it sorts entries in reverse (alphabetic) order, fix it. Signed-off-by: Namhyung Kim --- This patch can be folded into the original patch c7c2a5e40f17 ("perf tools: Add dynamic sort key for tracepoint events") tools/perf/util/sort.c | 2 +- 1 file changed, 1

[PATCH v4 2/5] perf tools: Separate hpp->sort callback for dynamic sort keys

The ->sort callback is used for final output sorting. As it's called after processing all hist entries, it doesn't need to update dynamic length anymore. Also it needs additional handling to sort them properly (which is the topic of next patch). Signed-off-by: Namhyung Kim

[PATCH v4 4/5] perf tools: Support dynamic sort keys for -F/--fields

Now dynamic sort keys are supported for tracepoint events, add it to output fields too. Signed-off-by: Namhyung Kim --- tools/perf/util/sort.c | 51 -- 1 file changed, 33 insertions(+), 18 deletions(-) diff --git

[PATCH -next] gpio: xilinx: Do not use gpiochip_get_data() in xgpio_save_regs()

Commit 097d88e94c44 ("gpio: xilinx: use gpiochip data pointer") replaces the use of container_of() with gpiochip_get_data(). Unfortunately, the data pointer is not yet set by the time xgpio_save_regs() is called, causing a system hang. Fixes: 097d88e94c44 ("gpio: xilinx: use gpiochip data

Re: [PATCH v2 10/14] serial: pic32_uart: Add PIC32 UART driver

On 01/05/2016 03:50 PM, One Thousand Gnomes wrote: > >> +#define PIC32_SDEV_NAME "ttyS" >> +#define PIC32_SDEV_MAJORTTY_MAJOR >> +#define PIC32_SDEV_MINOR64 > > No. Same goes for you as every one of the forty other people a year who > try and claim their console is ttyS. If

[PATCH RESEND v4 08/11] staging: fsl-mc: set MSI domain for DPRC objects

From: "J. German Rivera" THE MSI domain associated with a root DPRC object is obtained form the device tree. Child DPRCs inherit the parent DPRC MSI domain. Signed-off-by: J. German Rivera --- CHANGE HISTORY Changes in v4: - Addressed

[PATCH RESEND v4 10/11] staging: fsl-mc: Added DPRC interrupt handler

From: "J. German Rivera" The interrupt handler for DPRC IRQs is added. DPRC IRQs are generated for hot plug events related to DPAA2 objects in a given DPRC. These events include, creating/destroying DPAA2 objects in the DPRC, changing the "plugged" state of DPAA2

Re: [PATCHv1 6/6] rdmacg: Added documentation for rdma controller.

On Wed, Jan 6, 2016 at 3:23 AM, Tejun Heo wrote: > Hello, > > On Wed, Jan 06, 2016 at 12:28:06AM +0530, Parav Pandit wrote: >> +5-4-1. RDMA Interface Files >> + >> + rdma.resource.verb.list >> + rdma.resource.verb.limit >> + rdma.resource.verb.usage >> +

[Patch v6 1/3] media: ti-vpe: Document CAL driver

Device Tree bindings for the Camera Adaptation Layer (CAL) driver Signed-off-by: Benoit Parrot Acked-by: Rob Herring --- Documentation/devicetree/bindings/media/ti-cal.txt | 72 ++ 1 file changed, 72 insertions(+) create mode 100644

[Patch v6 0/3] media: ti-vpe: Add CAL v4l2 camera capture driver

The Camera Adaptation Layer (CAL) is a block which consists of a dual port CSI2/MIPI camera capture engine. This camera engine is currently found on DRA72xx family of devices. Port #0 can handle CSI2 camera connected to up to 4 data lanes. Port #1 can handle CSI2 camera connected to up to 2 data

[Patch v6 2/3] MAINTAINERS: Add ti-vpe maintainer entry

Signed-off-by: Benoit Parrot --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 4635e1d14612..ebbdb410c0f0 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -10631,6 +10631,14 @@ L: linux-o...@vger.kernel.org S:

Re: [PATCH v3 3/5] perf tools: Fix dynamic sort keys to sort properly

Em Wed, Jan 06, 2016 at 08:31:49PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Thu, Jan 07, 2016 at 08:26:45AM +0900, Namhyung Kim escreveu: > > On Wed, Jan 06, 2016 at 08:06:43PM -0300, Arnaldo Carvalho de Melo wrote: > > > Em Wed, Jan 06, 2016 at 09:54:59AM +0900, Namhyung Kim escreveu: > > >

Re: [BUG] skb corruption and kernel panic at forwarding with fragmentation

Florian Westphal wrote: > Thadeu Lima de Souza Cascardo wrote: > > On Wed, Jan 06, 2016 at 11:11:41PM +0300, Konstantin Khlebnikov wrote: [ skb_gso_segment uses skb->cb[], causes oops if ip_fragment is invoked on segmented skbs ] > > I have hit this as

Re: [PATCH v3] PCI: hosts: mark pcie/pci (msi) irq cascade handler as IRQF_NO_THREAD

Hi Grygorii, On Thu, Dec 10, 2015 at 09:18:20PM +0200, Grygorii Strashko wrote: > On -RT and if kernel is booting with "threadirqs" cmd line parameter > pcie/pci (msi) irq cascade handlers (like dra7xx_pcie_msi_irq_handler()) > will be forced threaded and, as result, will generate warnings like:

[PATCH] Input: rohm_bu21023 - fix handling of retrying firmware update

Because of the wrong condition we'd never retry firmware update. Signed-off-by: Dmitry Torokhov --- drivers/input/touchscreen/rohm_bu21023.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/input/touchscreen/rohm_bu21023.c

[PATCH v5 6/6] nvdimm: Add IOCTL pass thru functions

Add ioctl command ND_CMD_CALL_DSM to acpi_nfit_ctl and __nd_ioctl which allow kernel to call a nvdimm's _DSM as a passthru without using the marshaling code of the nd_cmd_desc. Signed-off-by: Jerry Hoemann --- drivers/acpi/nfit.c | 52

[PATCH v5 1/6] ACPI / util: Fix acpi_evaluate_dsm() argument type

The ACPI spec speicifies that arguments "Revision ID" and "Function Index" to a _DSM are type "Integer." Type Integers are 64 bit quantities. The function evaluate_dsm specifies these types as simple "int" which are 32 bits. Correct type passed to acpi_evaluate_dsm and its callers and derived

[PATCH v5 0/6] nvdimm: Add an IOCTL pass thru for DSM calls

The NVDIMM code in the kernel supports an IOCTL interface to user space based upon the Intel Example DSM: http://pmem.io/documents/NVDIMM_DSM_Interface_Example.pdf This interface cannot be used by other NVDIMM DSMs that support incompatible functions. This patch set adds a generic

[PATCH v5 4/6] nvdimm: Fix security issue with DSM IOCTL.

Code attempts to prevent certain IOCTL DSM from being called when device is opened read only. This security feature can be trivially overcome by changing the size portion of the ioctl_command which isn't used. Check only the _IOC_NR (i.e. the command). Signed-off-by: Jerry Hoemann

[PATCH v5 3/6] nvdimm: Add wrapper for IOCTL pass thru

Add struct nd_passthru_pkg which serves as a warapper for the data being passed via a pass thru to a NVDIMM DSM. This wrapper specifies the extra information in a uniform manner allowing the kenrel to call a DSM without knowing specifics of the DSM. Add dsm_call command to nvdimm_bus_cmd_name and

[PATCH v5 5/6] nvdimm: Increase max envelope size for IOCTL

In __nd_ioctl must first read in the fixed sized portion of an ioctl so that it can then determine the size of the variable part. Prepare for ND_CMD_CALL_DSM calls which have larger fixed portion wrapper. Signed-off-by: Jerry Hoemann --- include/linux/libnvdimm.h | 2 +-

Re: [PATCH] scripts: recordmcount: fix incorrect use of sprintf

On Wed, Jan 6, 2016 at 3:28 AM, Fengguang Wu wrote: > Hi Steven, > > On Mon, Jan 04, 2016 at 10:42:46AM -0500, Steven Rostedt wrote: >> On Wed, 30 Dec 2015 23:06:41 + >> Colin King wrote: >> >> > From: Colin Ian King

Re: [PATCH v4 55/58] mtd: nand: add helpers to access ->priv

On Sat, Dec 19, 2015 at 04:01:24AM +0100, Boris Brezillon wrote: > Actually the nand_{get,set}_controller_data() helpers are not about > assigning NAND controller private data (as you pointed those can > already be retrieved thanks to the ->controller field using the > container_of() trick), but

Re: [PATCHv1 0/6] rdma controller support

Hi Tejun, On Wed, Jan 6, 2016 at 3:26 AM, Tejun Heo wrote: > Hello, > > On Wed, Jan 06, 2016 at 12:28:00AM +0530, Parav Pandit wrote: >> Resources are not defined by the RDMA cgroup. Resources are defined >> by RDMA/IB stack & optionally by HCA vendor device drivers. > > As I

Re: [PATCH v3 3/5] perf tools: Fix dynamic sort keys to sort properly

On Wed, Jan 06, 2016 at 08:06:43PM -0300, Arnaldo Carvalho de Melo wrote: > Em Wed, Jan 06, 2016 at 09:54:59AM +0900, Namhyung Kim escreveu: > > Currently, the dynamic sort keys compares trace data using memcmp(). > > But for output sorting, it should check data size and compare by word. > > Also

Re: [PATCH v3 3/5] perf tools: Fix dynamic sort keys to sort properly

Em Thu, Jan 07, 2016 at 08:26:45AM +0900, Namhyung Kim escreveu: > On Wed, Jan 06, 2016 at 08:06:43PM -0300, Arnaldo Carvalho de Melo wrote: > > Em Wed, Jan 06, 2016 at 09:54:59AM +0900, Namhyung Kim escreveu: > > > Currently, the dynamic sort keys compares trace data using memcmp(). > > > But for

Re: [PATCHv1 3/6] rdmacg: implements rdma cgroup

On Wed, Jan 6, 2016 at 3:31 AM, Tejun Heo wrote: > Hello, > > On Wed, Jan 06, 2016 at 12:28:03AM +0530, Parav Pandit wrote: >> +/* hash table to keep map of tgid to owner cgroup */ >> +DEFINE_HASHTABLE(pid_cg_map_tbl, 7); >> +DEFINE_SPINLOCK(pid_cg_map_lock);/* lock to

Re: [PATCH v5 0/6] nvdimm: Add an IOCTL pass thru for DSM calls

On Wed, Jan 6, 2016 at 3:03 PM, Jerry Hoemann wrote: > The NVDIMM code in the kernel supports an IOCTL interface to user > space based upon the Intel Example DSM: > > http://pmem.io/documents/NVDIMM_DSM_Interface_Example.pdf > > This interface cannot be used by

[PATCH 20/31] x86, pkeys: differentiate instruction fetches

From: Dave Hansen As discussed earlier, we attempt to enforce protection keys in software. However, the code checks all faults to ensure that they are not violating protection key permissions. It was assumed that all faults are either write faults where we check

[PATCH 15/31] mm: factor out VMA fault permission checking

From: Dave Hansen This code matches a fault condition up with the VMA and ensures that the VMA allows the fault to be handled instead of just erroring out. We will be extending this in a moment to comprehend protection keys. Signed-off-by: Dave Hansen

[PATCH 16/31] x86, mm: simplify get_user_pages() PTE bit handling

From: Dave Hansen The current get_user_pages() code is a wee bit more complicated than it needs to be for pte bit checking. Currently, it establishes a mask of required pte _PAGE_* bits and ensures that the pte it goes after has all those bits. This consolidates

[PATCH 14/31] x86, pkeys: add functions to fetch PKRU

From: Dave Hansen This adds the raw instruction to access PKRU as well as some accessor functions that correctly handle when the CPU does not support the instruction. We don't use it here, but we will use read_pkru() in the next patch. Signed-off-by: Dave Hansen

[PATCH 13/31] x86, pkeys: fill in pkey field in siginfo

From: Dave Hansen This fills in the new siginfo field: si_pkey to indicate to userspace which protection key was set on the PTE that we faulted on. Note though that *ALL* protection key faults have to be generated by a valid, present PTE at some point. But this

Re: [PATCH 1/3] mtd: nand: pxa3xx_nand: add register access debug

On Tue, Aug 11, 2015 at 09:57:12PM +0200, Robert Jarzmik wrote: > Add verbose debug for register accesses. This enables easier debugging > by following where and how hardware is stimulated, and how it answers. > > Signed-off-by: Robert Jarzmik > --- >

[PATCH 08/31] x86, pkeys: new page fault error code bit: PF_PK

From: Dave Hansen Note: "PK" is how the Intel SDM refers to this bit, so we also use that nomenclature. This only defines the bit, it does not plumb it anywhere to be handled. Signed-off-by: Dave Hansen Reviewed-by: Thomas Gleixner

[PATCH 11/31] x86, pkeys: pass VMA down in to fault signal generation code

From: Dave Hansen During a page fault, we look up the VMA to ensure that the fault is in a region with a valid mapping. But, in the top-level page fault code we don't need the VMA for much else. Once we have decided that an access is bad, we are going to send a

Re: [PATCH v2 15/32] powerpc: define __smp_xxx

On Wed, Jan 06, 2016 at 10:23:51PM +0200, Michael S. Tsirkin wrote: [...] > > > > > > Sorry, I don't understand - why do you have to do anything? > > > I changed all users of smp_lwsync so they > > > use __smp_lwsync on SMP and barrier() on !SMP. > > > > > > This is exactly the current

Re: [linux-sunxi] Re: [PATCH v8 2/2] ASoc: sun4i-codec: Add FM, Line and Mic inputs

On Mon, Dec 28, 2015 at 04:06:49AM +0100, Danny Milosavljevic wrote: > Hi Maxime, > > On Sun, 27 Dec 2015 19:21:57 +0100 > Maxime Ripard wrote: > > > On Mon, Dec 21, 2015 at 12:34:16PM +0100, Danny Milosavljevic wrote: > > > This is the second part, actually

[GIT] Networking

As usual, there are a couple straggler bug fixes: 1) qlcnic_alloc_mbx_args() error returns are not checked in qlcnic driver. Fix from Insu Yun. 2) SKB refcounting bug in connector, from Florian Westphal. 3) vrf_get_saddr() has to propagate fib_lookup() errors to it's callers, from David

[PATCH RESEND v4 02/11] fsl-mc: msi: Added FSL-MC-specific member to the msi_desc's union

From: "J. German Rivera" FSL-MC is a bus type different from PCI and platform, so it needs its own member in the msi_desc's union. Signed-off-by: J. German Rivera --- CHANGE HISTORY Changes in v4: none Changes in v3: none Changes in

[PATCH RESEND v4 07/11] staging: fsl-mc: Populate the IRQ pool for an MC bus instance

From: "J. German Rivera" Scan the corresponding DPRC container to get total count of IRQs needed by all its child DPAA2 objects. Then, preallocate a set of MSI IRQs with the DPRC's ICID (GIT-ITS device Id) to populate the the DPRC's IRQ pool. Each child DPAA2 object

[PATCH RESEND v4 01/11] irqdomain: Added domain bus token DOMAIN_BUS_FSL_MC_MSI

From: "J. German Rivera" Since an FSL-MC bus is a new bus type that is neither PCI nor PLATFORM, we need a new domain bus token to disambiguate the IRQ domain for FSL-MC MSIs. Signed-off-by: J. German Rivera --- CHANGE HISTORY Changes

[PATCH RESEND v4 06/11] staging: fsl-mc: Changed DPRC built-in portal's mc_io to be atomic

From: "J. German Rivera" The DPRC built-in portal's mc_io is used to send commands to the MC to program MSIs for MC objects. This is done by the fsl_mc_msi_write_msg() callback, which is invoked by the generic MSI layer with interrupts disabled. As a result, the

Re: [PATCH for-4.5 v2] mtd: nand: assign reasonable default name for NAND drivers

On Tue, Jan 05, 2016 at 10:39:45AM -0800, Brian Norris wrote: > Commits such as commit 853f1c58c4b2 ("mtd: nand: omap2: show parent > device structure in sysfs") attempt to rely on the core MTD code to set > the MTD name based on the parent device. However, nand_base tries to set > a different

[PATCH v5 2/6] nvdimm: Clean-up access mode check.

Change nd_ioctl and nvdimm_ioctl access mode check to use O_RDONLY. Signed-off-by: Jerry Hoemann --- drivers/nvdimm/bus.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/nvdimm/bus.c b/drivers/nvdimm/bus.c index 7e2c43f..1c81203

Re: [PATCH v3 3/5] perf tools: Fix dynamic sort keys to sort properly

Em Wed, Jan 06, 2016 at 09:54:59AM +0900, Namhyung Kim escreveu: > Currently, the dynamic sort keys compares trace data using memcmp(). > But for output sorting, it should check data size and compare by word. > Also it sorted strings in reverse order, fix it. Can this be broken down in two

Re: [PATCHv1 2/6] IB/core: Added members to support rdma cgroup

On Wed, Jan 6, 2016 at 3:26 AM, Tejun Heo wrote: > On Wed, Jan 06, 2016 at 12:28:02AM +0530, Parav Pandit wrote: >> Added function pointer table to store resource pool specific >> operation for each resource type (verb and hw). >> Added list node to link device to rdma cgroup so

Re: [PATCH] Staging: wlan-ng: p80211conv.c: Coding style fixes General coding style checks have been fixed. Warnings not fixed.

On Thu, Jan 07, 2016 at 12:45:40AM +0530, Pranjal Bhor wrote: > Signed-off-by: Pranjal Bhor Your subject is very "odd", please fix it up and provide a real changelog entry as well. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH v5] mtd: support BB SRAM on ICP DAS LP-8x4x

On Sun, Dec 20, 2015 at 01:43:58PM +0300, Sergei Ianovich wrote: > On Sat, 2015-12-19 at 21:38 -0600, Rob Herring wrote: > > On Tue, Dec 15, 2015 at 09:58:53PM +0300, Sergei Ianovich wrote: > > > +Required properties: > > > +- compatible : should be "icpdas,sram-lp8x4x" > > > > No wildcards

Re: [PATCH v2] of/unittest: Show broken behaviour in the platform bus

On Mon, Jan 4, 2016 at 6:13 AM, Wolfram Sang wrote: > From: Grant Likely > > Add a single resource to the test bus device to exercise the platform > bus code a little more. This isn't strictly a devicetree test, but it is > a corner case that the

[PATCH v2 RESEND] tools/hv: Use include/uapi with __EXPORTED_HEADERS__

Use the local uapi headers to keep in sync with "recently" added #define's (e.g. VSS_OP_REGISTER1). Fixes: 3eb2094c59e8 ("Adding makefile for tools/hv") Cc: Signed-off-by: Kamal Mostafa Signed-off-by: K. Y. Srinivasan ---

<    2   3   4   5   6   7   8   9   10   11   >