Re: [PATCH] KVM: x86: restore IP after all far jump failures

I admit my wrongdoings, but I still think the fix should have been to remove the entire recovery logic and just return X86EMUL_UNHANDLEABLE if something goes wrong (exception). This will kill the misbehaving process but keep the VM running. Otherwise, a malicious VM process, which can somehow

Re: [PATCH] mtd: bcm47xxpart: fix parsing first block after aligned TRX

On Sun, Nov 20, 2016 at 04:09:30PM +0100, Rafał Miłecki wrote: > From: Rafał Miłecki > > After parsing TRX we should skip to the first block placed behind it. > Our code was working only with TRX with length not aligned to the > blocksize. In other cases (length aligned) it was

Re: [PATCH -tip v3 3/9] selftests: ftrace: Add --quiet option not to show error logs on screen

On Wed, 16 Nov 2016 17:13:17 +0900 Masami Hiramatsu wrote: > Since the verbose error logs scrolls out previous test results > --quiet option suppress to show such message. I wonder if -q should be default, and -v be what we have, and -vv be verbose? -- Steve > > e.g. >

Re: BUG at drivers/iommu/amd_iommu.c:1436!

On 11/22/2016 03:45 AM, Joerg Roedel wrote: On Mon, Nov 21, 2016 at 04:47:59PM -0500, Mark Hounschell wrote: OK, I did get this message before the reported BUG message. gpiohsd gpiohsd: DMA-API: device driver tries to free DMA memory it has not allocated [device address=0xffee8000]

Re: [PATCH V4 02/15] blk-throttle: add .high interface

Hello, Shaohua. Sorry about the delay. On Mon, Nov 14, 2016 at 02:22:09PM -0800, Shaohua Li wrote: > @@ -1376,11 +1414,37 @@ static ssize_t tg_set_max(struct kernfs_open_file *of, > goto out_finish; > } > > - tg->bps[READ][LIMIT_MAX] = v[0]; > -

Re: [PATCH] KVM: x86: restore IP after all far jump failures

Should the subject read: "KVM: x86: restore CS after all far jump failures"? On Tue, Nov 22, 2016 at 11:21 AM, Radim Krčmář wrote: > em_jmp_far and em_ret_far assumed that setting IP can only fail in 64 > bit mode, but syzkaller proved otherwise (and SDM agrees). > Code

Re: Enabling peer to peer device transactions for PCIe devices

On Tue, Nov 22, 2016 at 12:10 PM, Daniel Vetter wrote: > On Tue, Nov 22, 2016 at 9:01 PM, Dan Williams > wrote: >> On Tue, Nov 22, 2016 at 10:59 AM, Serguei Sagalovitch >> wrote: >>> I personally like "device-DAX" idea but

[PATCH v8 3/8] x86: Enable Intel Turbo Boost Max Technology 3.0

On platforms supporting Intel Turbo Boost Max Technology 3.0, the maximum turbo frequencies of some cores in a CPU package may be higher than for the other cores in the same package. In that case, better performance (and possibly lower energy consumption as well) can be achieved by making the

[PATCH v8 7/8] acpi: bus: Set _OSC for diverse core support

From: Srinivas Pandruvada Set the OSC_SB_CPC_DIVERSE_HIGH_SUPPORT (bit 12) to enable diverse core support. This is required to inform BIOS the support of Intel Turbo Boost Max Technology 3.0 feature. Signed-off-by: Srinivas Pandruvada

[PATCH v8 4/8] x86/sysctl: Add sysctl for ITMT scheduling feature

Intel Turbo Boost Max Technology 3.0 (ITMT) feature allows some cores to be boosted to higher turbo frequency than others. Add /proc/sys/kernel/sched_itmt_enabled so operator can enable/disable scheduling of tasks that favor cores with higher turbo boost frequency potential. By default, system

[PATCH v8 8/8] cpufreq: intel_pstate: Use CPPC to get max performance

From: "Rafael J. Wysocki" This change uses acpi cppc_lib interface to get CPPC performance limits and calls scheduler interface to update per cpu highest priority. If there is a difference in highest performance of each CPUs, call scheduler interface to enable ITMT

[PATCH v8 5/8] x86/sched: Add SD_ASYM_PACKING flags to x86 ITMT CPU

Some Intel cores in a package can be boosted to a higher turbo frequency with ITMT 3.0 technology. The scheduler can use the asymmetric packing feature to move tasks to the more capable cores. If ITMT is enabled, add SD_ASYM_PACKING flag to the thread and core sched domains to enable asymmetric

Re: [PATCH 4/6] efi: Get the secure boot status

On Tue, Nov 22, 2016 at 02:47:27PM +, David Howells wrote: > Lukas Wunner wrote: > > The "out_efi_err" portion differs from the previous version of this > > patch. Setting a __u8 to a negative value, is this really what you > > want? > > Eh? efi_get_secureboot() returns an

Re: 4.8.8 kernel trigger OOM killer repeatedly when I have lots of RAM that should be free

On Tue, Nov 22, 2016 at 8:14 AM, Vlastimil Babka wrote: > > Thanks a lot for the testing. So what do we do now about 4.8? (4.7 is > already EOL AFAICS). > > - send the patch [1] as 4.8-only stable. I think that's the right thing to do. It's pretty small, and the argument that it

Re: Kernel BUG_ON in stable 4.8

This patch fixes our issue on v4.8.10. Thank you! 2016-11-22 14:22 GMT-05:00 Eric Dumazet : > On Tue, Nov 22, 2016 at 9:57 AM, Eric Dumazet wrote: >> On Tue, Nov 22, 2016 at 9:44 AM, Mathieu Desnoyers >> wrote: >>> -

Re: [PATCH V4 03/15] blk-throttle: configure bps/iops limit for cgroup in high limit

On Mon, Nov 14, 2016 at 02:22:10PM -0800, Shaohua Li wrote: > each queue will have a state machine. Initially queue is in LIMIT_HIGH > state, which means all cgroups will be throttled according to their high > limit. After all cgroups with high limit cross the limit, the queue state > gets

Re: Enabling peer to peer device transactions for PCIe devices

On Tue, Nov 22, 2016 at 9:01 PM, Dan Williams wrote: > On Tue, Nov 22, 2016 at 10:59 AM, Serguei Sagalovitch > wrote: >> I personally like "device-DAX" idea but my concerns are: >> >> - How well it will co-exists with the DRM

Re: Enabling peer to peer device transactions for PCIe devices

On 2016-11-22 03:10 PM, Daniel Vetter wrote: On Tue, Nov 22, 2016 at 9:01 PM, Dan Williams wrote: On Tue, Nov 22, 2016 at 10:59 AM, Serguei Sagalovitch wrote: I personally like "device-DAX" idea but my concerns are: - How well it

Re: [PATCH 0/9] AC97 device/driver model revamp

On Wed, Oct 26, 2016 at 09:41:38PM +0200, Robert Jarzmik wrote: > The driving ideas are still the same, and I put them in [1] for memory. This > is > the first post RFC submission. In order to make a full demonstration of the > framework, wm97xx was converted to an MFD, see [2] for the "why".

Re: [RFC PATCH v3 15/20] x86: Check for memory encryption on the APs

On Wed, Nov 09, 2016 at 06:37:40PM -0600, Tom Lendacky wrote: > Add support to check if memory encryption is active in the kernel and that > it has been enabled on the AP. If memory encryption is active in the kernel > but has not been enabled on the AP then do not allow the AP to continue > start

Re: Kernel BUG_ON in stable 4.8

On Tue, Nov 22, 2016 at 9:57 AM, Eric Dumazet wrote: > On Tue, Nov 22, 2016 at 9:44 AM, Mathieu Desnoyers > wrote: >> - On Nov 22, 2016, at 12:01 PM, Francis Deslauriers >> francis.deslauri...@efficios.com wrote: >> >>> Hi Mathieu, >>>

Re: [PATCH] KVM: x86: fix out-of-bounds access in lapic

On 22/11/2016 20:20, Radim Krčmář wrote: > Cluster xAPIC delivery incorrectly assumed that dest_id <= 0xff. > With enabled KVM_X2APIC_API_USE_32BIT_IDS in KVM_CAP_X2APIC_API, a > userspace can send an interrupt with dest_id that results in > out-of-bounds access. > > Found by syzkaller: > >

Re: [PATCH] KVM: x86: restore IP after all far jump failures

On 22/11/2016 20:21, Radim Krčmář wrote: > em_jmp_far and em_ret_far assumed that setting IP can only fail in 64 > bit mode, but syzkaller proved otherwise (and SDM agrees). > Code segment was restored upon failure, but it was left uninitialized > outside of long mode, which could lead to a leak

Re: [PATCH v6 3/9] tpm: replace dynamically allocated bios_dir with a static array

On 11/22/2016 04:53 PM, Jarkko Sakkinen wrote: On Mon, Nov 14, 2016 at 05:00:50AM -0500, Nayna Jain wrote: This commit is based on a commit by Nayna Jain. Replaced dynamically allocated bios_dir with a static array as the size is always constant. Suggested-by: Jason Gunthorpe

[PATCH 1/2] trace-cmd record: refactor set_mask()

This commit makes set_mask() more specialized: all it does now is to write the cpumask to tracing_cpumask. The handling of "-M -1" is now done by the newly added alloc_mask_from_hex(). Also, uneeded checks are dropped and buffer_instance->cpumask points to dynamic memory. This work is a

[PATCH 2/2] trace-cmd record: add --cpu-list option

With --cpu-list you can do: # trace-cmd record --cpu-list 1,4,10-15 [...] Which is much more human friendly than -M. Support for --cpu-list is implemented by dynamically allocating a cpu_set_t object and setting the parsed CPUs. Using the CPU_SET API allows for more robost error detection.

Re: [PATCH 4/6] efi: Get the secure boot status

On Tue, Nov 22, 2016 at 02:52:01PM +, David Howells wrote: > Lukas Wunner wrote: > > You dropped the efi_system_table_t *sys_table_arg argument but this > > isn't defined anywhere as a static global. > > It seems to me that passing this value in on x86 is probably a bad idea

Re: [PATCH net] flow_dissect: call init_default_flow_dissectors() earlier

On Tue, Nov 22, 11:17, Eric Dumazet wrote > -late_initcall_sync(init_default_flow_dissectors); > +core_initcall(init_default_flow_dissectors); Indeed, that fixed it. Feel free to add Tested-by: Andre Noll Thanks a lot Andre -- Max Planck Institute for Developmental

Re: [RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally

On Tue, Nov 22, 2016 at 9:38 AM, Laurent Pinchart wrote: > Hi John, > > On Tuesday 22 Nov 2016 09:25:22 John Stultz wrote: >> On Tue, Nov 22, 2016 at 12:14 AM, Laurent Pinchart wrote: >> > On Monday 21 Nov 2016 16:37:30 John Stultz wrote: >> @@ -545,24 +554,13

Applied "ASoC: sunxi: Add support for A23/A33/H3 codec's analog path controls" to the asoc tree

The patch ASoC: sunxi: Add support for A23/A33/H3 codec's analog path controls has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Re: [patch V2 00/12] thermal/x86_pkg_temp: Sanitize hotplug and locking

On Tue, 2016-11-22 at 17:57 +, Thomas Gleixner wrote: > Changes vs. V1: Fix the package removal wreckage reported by Srinivas > I haven't looked at individual patch but tested the series as a whole.  So Rui, you can add Tested-by: Srinivas Pandruvada

Re: [PATCH] mtd: mtdswap: fix spelling mistake "erassure" -> "erasure"

On Fri, Oct 28, 2016 at 11:51:47AM -0700, Joe Perches wrote: > I'd suggest as well fixing all the dev_ uses > to be a consistent form: (this also fixes the typo) > and a few other bits > > o Coalesce formats > o Realign arguments > o Add missing newlines Yeah, Colin missed this on the line he

2 Millionen Euro

Ich war ein normaler Bürger genauso wie Sie, bis ich auf dem Gehen Spende einen Artikel corncerning abot ein lesen, die das Leben verändert, ich mit ihnen Kontakt auf und es war leicht, sie gaben mir guidline und am nächsten Tag bekam ich eine Spende von 2 Millionen Euro. Es ist einfach nur

Re: [PATCH 1/5] mm: migrate: Add mode parameter to support additional page copy routines.

Hi Zi, [auto build test WARNING on linus/master] [also build test WARNING on v4.9-rc6 next-20161122] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Zi-Yan/Parallel-hugepage-migration

Re: [PATCH v7 1/8] sched: Extend scheduler's asym packing

On Tue, 2016-11-22 at 11:09 +0100, Peter Zijlstra wrote: >  > > Not a big fan of that part.. would not something like the below cure > that? > > It would be slightly less optimal for Power7 but would actually be > faster (on average) for the ITMT case, but most importantly, it does > away with

[PATCH v2 0/2] trace-cmd record: add --cpu-list option

This series adds support for a --cpu-list option, which is much more human friendly than -M: # trace-cmd record --cpu-list 1,4,10-15 [...] The first patch is a small refectoring needed to make --cpu-list support fit nicely. The second patch adds the new option. v2 -- - Use the CPU_SET() API

[PATCH v8 6/8] acpi: bus: Enable HWP CPPC objects

From: Srinivas Pandruvada Need to set platform wide _OSC bits to enable CPPC and CPPC version 2. If platform supports CPPC, then BIOS exposes CPPC tables. The primary reason to enable CPPC support is to get the maximum performance of each CPU to check and

[PATCH v8 2/8] x86/topology: Define x86's arch_update_cpu_topology

The scheduler calls arch_update_cpu_topology() to check whether the scheduler domains have to be rebuilt. So far x86 has no requirement for this, but the upcoming ITMT support makes this necessary. Request the rebuild when the x86 internal update flag is set. Suggested-by: Morten Rasmussen

[PATCH v8 0/8] Support Intel Turbo Boost Max Technology 3.0

With Intel Turbo Boost Max Technology 3.0 (ITMT), single-threaded performance is optimized by identifying processor's fastest core and running critical workloads on it. Refer to: http://www.intel.com/content/www/us/en/architecture-and-technology/turbo-boost/turbo-boost-max-technology.html This

[PATCH v8 1/8] sched: Extend scheduler's asym packing

We generalize the scheduler's asym packing to provide an ordering of the cpu beyond just the cpu number. This allows the use of the ASYM_PACKING scheduler machinery to move loads to preferred CPU in a sched domain. The preference is defined with the cpu priority given by

[PATCH v8 0/8] drivers: touchscreen: tsc2007 and ads7846/tsc2046 improvements (use common touchscreen bindings, pre-calibration, spi fix and provide iio raw values)

Changes V8: * fix compilation for CONFIG_IIO=m (reported by Jonathan Cameron ) * add some more Reviewed-by: and Acked-by: * mutiple improvements suggested by Dmitry Torokhov : ** drop patch "send pendown and penup only once" (input core does take care

[PATCH v8 8/8] DT:omap3+ads7846: use new common touchscreen bindings

The standard touch screen bindings [1] replace the private ti,swap-xy with touchscreen-swaped-x-y. And for the Openpandora we use touchscreen-size etc. to match the LCD screen size. [1]: Documentation/devicetree/bindings/input/touchscreen/touchscreen.txt Tested with OpenPandora. Signed-off-by:

[PATCH v8 4/8] DT:omap3+tsc2007: use new common touchscreen bindings

While we fix the GTA04 we add proper pinmux for the penirq gpio. Tested on: GTA04A4 and Pyra-Handheld Signed-off-by: H. Nikolaus Schaller Acked-by: Tony Lindgren --- arch/arm/boot/dts/omap3-gta04.dtsi | 25 +++-- 1 file changed, 23

[PATCH v8 6/8] dt-bindings: input: move ads7846 bindings to touchscreen subdirectory

Signed-off-by: H. Nikolaus Schaller Acked-by: Rob Herring --- Documentation/devicetree/bindings/input/{ => touchscreen}/ads7846.txt | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename Documentation/devicetree/bindings/input/{ =>

[PATCH v8 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

commit b98abe52fa8e ("Input: add common DT binding for touchscreens") introduced common DT bindings for touchscreens [1] and a helper function to parse the DT. commit ed7c9870c9bc ("Input: of_touchscreen - add support for inverted / swapped axes") added another helper for parsing axis inversion

[PATCH v8 3/8] drivers:input:tsc2007: add iio interface to read external ADC input and temperature

The tsc2007 chip not only has a resistive touch screen controller but also an external AUX adc imput which can be used for an ambient light sensor, battery voltage monitoring or any general purpose. Additionally it can measure the chip temperature. This extension provides an iio interface for

[PATCH v8 5/8] drivers:input:ads7846(+tsc2046): add new common binding names, pre-calibration and flipping

commit b98abe52fa8e ("Input: add common DT binding for touchscreens") introduced common DT bindings for touchscreens [1] and a helper function to parse the DT. commit ed7c9870c9bc ("Input: of_touchscreen - add support for inverted / swapped axes") added another helper for parsing axis inversion

[RFC 1/4] mm: Define coherent device memory node

There are certain devices like specialized accelerator, GPU cards, network cards, FPGA cards etc which might contain onboard memory which is coherent along with the existing system RAM while being accessed either from the CPU or from the device. They share some similar properties with that of

[DEBUG 06/12] powerpc/mm: Create numa nodes for hotplug memory

From: Reza Arbab When scanning the device tree to initialize the system NUMA topology, process dt elements with compatible id "ibm,hotplug-aperture" to create memoryless numa nodes. These nodes will be filled when hotplug occurs within the associated address range.

[PATCH net-next] marvell: mark mvneta and mvpp2 32-bit only

Both of these drivers won't work on 64-bit architectures unless they are redesigned, since they store a virtual address pointer in a 32-bit field of the descriptors: drivers/net/ethernet/marvell/mvneta_bm.c: In function 'mvneta_bm_construct': drivers/net/ethernet/marvell/mvneta_bm.c:103:16:

[RFC 4/4] mm: Ignore cpuset enforcement when allocation flag has __GFP_THISNODE

__GFP_THISNODE specifically asks the memory to be allocated from the given node. Not all the requests that end up in __alloc_pages_nodemask() are originated from the process context where cpuset makes more sense. The current condition enforces cpuset limitation on every allocation whether

Re: [PATCH 4/6] efi: Get the secure boot status

Lukas Wunner wrote: > You dropped the efi_system_table_t *sys_table_arg argument but this > isn't defined anywhere as a static global. It seems to me that passing this value in on x86 is probably a bad idea as it's not mixed-mode safe. Should I just pass NULL there in that

Re: [PATCH] ipv6:ipv6_pinfo dereferenced after NULL check

From: Hannes Frederic Sowa Date: Tue, 22 Nov 2016 13:26:45 +0100 > On 22.11.2016 07:27, Manjeet Pawar wrote: >> From: Rohit Thapliyal >> >> np checked for NULL and then dereferenced. It should be modified >> for NULL case. >> >>

RE: [PATCH V6 2/2] PCI/ACPI: hisi: Add ACPI support for HiSilicon SoCs Host Controllers

Hi Tomasz > -Original Message- > From: Tomasz Nowicki [mailto:t...@semihalf.com] > Sent: 22 November 2016 13:58 > To: liudongdong (C); helg...@kernel.org; a...@arndb.de; > raf...@kernel.org; lorenzo.pieral...@arm.com; Wangzhou (B); > pratyush.an...@gmail.com > Cc:

Re: [PATCH net-next] marvell: mark mvneta and mvpp2 32-bit only

Hi Arnd, On mar., nov. 22 2016, Arnd Bergmann wrote: > Both of these drivers won't work on 64-bit architectures unless they > are redesigned, since they store a virtual address pointer in a 32-bit > field of the descriptors: > > drivers/net/ethernet/marvell/mvneta_bm.c: In

Re: [PATCH v1 2/3] kvm: svm: Add kvm_fast_pio_in support

- Original Message - > From: "Tom Lendacky" > To: "Paolo Bonzini" , "Brijesh Singh" > , k...@vger.kernel.org > Cc: rkrc...@redhat.com, j...@8bytes.org, x...@kernel.org, > linux-kernel@vger.kernel.org,

Re: [PATCH 1/2] power: supply: sbs-battery: use fixed device name

Hi, On Mon, Nov 21, 2016 at 07:04:50PM +0100, Nicola Saenz Julienne wrote: > The current device name for sbs-battery is derived from it's i2c address. > This is not acceptable if we want to be able to trigger the > "external_power_changed()" routine from a charger driver. > > Signed-off-by:

[PATCH 1/2] mfd: arizona: Add defines for IRQs on the main Arizona IRQ domain

Signed-off-by: Charles Keepax --- drivers/mfd/arizona-irq.c | 21 +++-- 1 file changed, 15 insertions(+), 6 deletions(-) diff --git a/drivers/mfd/arizona-irq.c b/drivers/mfd/arizona-irq.c index 724fa54..88729cf 100644 ---

Re: [PATCH] ARM: davinci_all_defconfig: Enable OHCI as module

On Monday 21 November 2016 10:31 PM, Axel Haslam wrote: > Enable the davinci ohci driver as a module for usb > tested with the omap138-lcdk hawk board. > > Signed-off-by: Axel Haslam Applied to v4.10/defconfg after dropping "hawk" from commit description. Thanks, Sekhar

[PATCHv12 2/3] usb: USB Type-C connector class

The purpose of USB Type-C connector class is to provide unified interface for the user space to get the status and basic information about USB Type-C connectors on a system, control over data role swapping, and when the port supports USB Power Delivery, also control over power role swapping and

[PATCHv12 3/3] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY

This adds driver for the USB Type-C PHY on Intel WhiskeyCove PMIC which is available on some of the Intel Broxton SoC based platforms. Signed-off-by: Heikki Krogerus --- drivers/usb/typec/Kconfig | 14 ++ drivers/usb/typec/Makefile | 1 +

[PATCHv12 0/3] USB Type-C Connector class

The USB Type-C class is meant to provide unified interface to the userspace to present the USB Type-C ports in a system. Changes since v11: - The port drivers are responsible of removing the alternate modes (just like the documentation already said). Changes since v10: - Using ATTRIBUTE_GROUPS

Re: Synopsys Ethernet QoS Driver

Hi Lars and Peppe, On 21-11-2016 16:11, Joao Pinto wrote: > On 21-11-2016 15:43, Lars Persson wrote: >> >> >>> 21 nov. 2016 kl. 16:06 skrev Joao Pinto : >>> On 21-11-2016 14:25, Giuseppe CAVALLARO wrote: > On 11/21/2016 2:28 PM, Lars Persson wrote: > >

Re: [PATCH 1/6] x86/efi: Allow invocation of arbitrary runtime services

Lukas Wunner wrote: > Small nit, checkpatch usually complains that this should be written as > 12-character SHA-1 followed by the commit subject, i.e. > > 0a637ee61247 ("x86/efi: Allow invocation of arbitrary boot services") In this case, checkpatch is wrong. David

[PATCHv12 1/3] lib/string: add sysfs_match_string helper

Make a simple helper for matching strings with sysfs attribute files. In most parts the same as match_string(), except sysfs_match_string() uses sysfs_streq() instead of strcmp() for matching. This is more convenient when used with sysfs attributes. Signed-off-by: Heikki Krogerus

[RFC 0/4] Define coherent device memory node

There are certain devices like accelerators, GPU cards, network cards, FPGA cards, PLD cards etc which might contain on board memory. This on board memory can be coherent along with system RAM and may be accessible from either the CPU or from the device. The coherency is usually achieved

[PATCH 1/2] PCI: iproc: fix 32-bit build

The newly added code to setup the inbound ranges causes a link error on 32-bit machines from a 32-bit division: drivers/pci/host/pcie-iproc.o: In function `iproc_pcie_setup_ib': pcie-iproc.c:(.text.iproc_pcie_setup_ib+0x14c): undefined reference to `__aeabi_uldivmod' As both sides of the

[PATCH 2/2] PCI: iproc: avoid maybe-uninitialized warning

gcc notices that calling iproc_pcie_setup_ib with ib->nr_regions==0 would result in an uninitialized return value: drivers/pci/host/pcie-iproc.c: In function 'iproc_pcie_setup_ib': drivers/pci/host/pcie-iproc.c:894:6: error: 'ret' may be used uninitialized in this function

Re: [PATCH v1 2/3] kvm: svm: Add kvm_fast_pio_in support

On 11/21/2016 8:50 AM, Paolo Bonzini wrote: > > > On 14/11/2016 23:15, Brijesh Singh wrote: >> +/* For size less than 4 we merge, else we zero extend */ >> +val = (size < 4) ? kvm_register_read(vcpu, VCPU_REGS_RAX) : 0; > > Are you sure it shouldn't always zero extend the high 32-bits?

Re: [PATCH] scsi: hpsa: fix uninitialized variable access

On Tuesday, November 22, 2016 3:47:09 PM CET Hannes Reinecke wrote: > index 05f7782..ee6f852 100644 > --- a/drivers/scsi/hpsa.c > +++ b/drivers/scsi/hpsa.c > @@ -2031,7 +2031,7 @@ static struct hpsa_scsi_dev_t > *lookup_hpsa_scsi_dev(struct ctlr_info *h, > > static int hpsa_slave_alloc(struct

Re: [PATCH] binder: replace kzalloc with kmem_cache

-replace-kzalloc-with-kmem_cache/20161122-213614 coccinelle warnings: (new ones prefixed by >>) >> drivers/android/binder.c:3705:2-20: WARNING: NULL check before freeing >> functions like kfree, debugfs_remove, debugfs_remove_recursive or >> usb_free_urb is not needed. May

IS ABOUT YOUR FUND

Dear one. This is to officially inform you about your $8.7m with the United Nations Assisted Program and for your information you will receive your fund through (ATM CARD, CASHIER CHECK OR wire transfer) please choose payment method. Therefore you are advised to contact US with your personal

Re: [PATCH 2/4] arm64: dts: rockchip: Arch counter doesn't tick in system suspend

Am Dienstag, 22. November 2016, 10:44:22 schrieb Daniel Lezcano: > From: Brian Norris > > The "arm,no-tick-in-suspend" property was introduced to note > implementations where the system counter does not quite follow the ARM > specification that it "must be implemented

Re: [PATCH 1/3] of: base: add support to get machine compatible string

Hi Sudeep, On Tuesday 22 November 2016 04:23 PM, Sudeep Holla wrote: > > > On 22/11/16 10:41, Bartosz Golaszewski wrote: >> Add a function allowing to retrieve the compatible string of the root >> node of the device tree. >> > > Rob has queued [1] and it's in -next today. You can reuse that if

Re: [PATCH 5/5] usb: dwc2: fix kernel-doc for dwc2_set_param

Hi, Stefan Wahren writes: > Hi Felipe, > > Am 22.11.2016 um 13:23 schrieb Felipe Balbi: >> Hi, >> >> Stefan Wahren writes: >>> Since there is no parameter @value replace it with @legacy. >>> >>> Fixes: 05ee799f202 ("usb: dwc2: Move gadget

[PATCH v8 2/8] drivers:input:tsc2007: check for presence and power down tsc2007 during probe

1. check if chip is really present and don't succeed if it isn't. 2. if it succeeds, power down the chip until accessed Signed-off-by: H. Nikolaus Schaller --- drivers/input/touchscreen/tsc2007.c | 8 1 file changed, 8 insertions(+) diff --git

[PATCH v8 7/8] drivers:input:ads7846(+tsc2046): fix spi module table

Fix module table so that the driver is loaded if compiled as module and requested by DT. Signed-off-by: H. Nikolaus Schaller --- drivers/input/touchscreen/ads7846.c | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git

[GIT PULL] arm/hdlcd fixes for v4.9-rc7

Hi David, A late issue discovered by Russell King while testing his setup on Juno. I would be really happy if it goes into v4.9-rc7 as it fixes a reference counting problem with the pixelclock clock, but if it is too late for that then I guess it can go into drm-next. The following changes since

[RFC 3/4] mm/hugetlb: Restrict HugeTLB page allocations only to system ram nodemask

HugeTLB allocation/release/accounting currently spans across all the nodes under N_MEMORY node mask. Coherent memory nodes should not be part of these allocations. So use system_ram() call to fetch system RAM only nodes on the platform which can then be used for HugeTLB allocation purpose instead

[RFC 2/4] mm/cpuset: Exclude coherent device memory nodes from mems_allowed

Task's mems_allowed decides the final node mask of nodes from which memory can be allocated irrespective of the process or VMA based memory policy. Coherent device memory nodes should not be used for any user space memory allocation, hence they should not be part of any mems_allowed mask in user

Re: [v5,3/5] USB: ohci: da8xx: Allow a regulator to handle VBUS

On Mon, Nov 21, 2016 at 5:29 PM, David Lechner wrote: > On 11/21/2016 04:22 AM, Axel Haslam wrote: >> >> Hi David, >> >> Thanks for the review, >> > > You're welcome. > @@ -160,15 +212,41 @@ static void ohci_da8xx_ocic_handler(struct da8xx_ohci_root_hub *hub,

[DEBUG 10/12] mm: Add a new migration function migrate_virtual_range()

This adds a new virtual address range based migration interface which can migrate all the mapped pages from a virtual range of a process to a destination node. This also exports this new function symbol. Signed-off-by: Anshuman Khandual --- include/linux/mempolicy.h

[DEBUG 11/12] drivers: Add two drivers for coherent device memory tests

This adds two different drivers inside drivers/char/ directory under two new kernel config options COHERENT_HOTPLUG_DEMO and COHERENT_MEMORY_DEMO. 1) coherent_hotplug_demo: Detects, hoptlugs the coherent device memory 2) coherent_memory_demo: Exports debugfs interface for VMA migrations

[DEBUG 12/12] test: Add a script to perform random VMA migrations across nodes

This is a test script which creates a workload (e.g ebizzy) and go through it's VMAs (/proc/pid/maps) and initiate migration to random nodes which can be either system memory node or coherent memory node. Signed-off-by: Anshuman Khandual ---

[PATCH] f2fs: fix 32-bit build

The addition of multiple-device support broke CONFIG_BLK_DEV_ZONED on 32-bit machines because of a 64-bit division: fs/f2fs/f2fs.o: In function `__issue_discard_async': extent_cache.c:(.text.__issue_discard_async+0xd4): undefined reference to `__aeabi_uldivmod' Unfortunately, the sector number

[DEBUG 09/12] powerpc: Enable CONFIG_MOVABLE_NODE for PPC64 platform

Just enable MOVABLE_NODE config option for PPC64 platform by default. This prevents accidentally building the kernel without the required config option. Signed-off-by: Anshuman Khandual --- arch/powerpc/Kconfig | 4 1 file changed, 4 insertions(+) diff --git

[DEBUG 07/12] powerpc/mm: Allow memory hotplug into a memory less node

From: Reza Arbab Remove the check which prevents us from hotplugging into an empty node. Signed-off-by: Reza Arbab Signed-off-by: Anshuman Khandual --- arch/powerpc/mm/numa.c | 13 + 1 file changed,

Re: [PATCH] f2fs: fix 32-bit build

Arnd, > Unfortunately, the sector number is usually a 64-bit number, and > we probably can't guarantee that bdev_zone_size() returns a > power-of-two number, so we actually have to do the expensive 64-bit > operation to get the remainder. No, the zone size is guaranteed to be a power of 2. See

[PATCH] misc: sram: remove useless #ifdef

A recent patch added a new function that is now unused whenever CONFIG_OF is disabled: drivers/misc/sram.c:342:12: error: 'atmel_securam_wait' defined but not used [-Werror=unused-function] There is actually no reason for the #ifdef, because the driver currently cannot be used in a meaningful

Re: [PATCH] scsi: hpsa: fix uninitialized variable access

On 11/22/2016 03:32 PM, Arnd Bergmann wrote: > A bugfix has left the 'sd' variable uninitialized: > > drivers/scsi/hpsa.c: In function 'hpsa_slave_alloc': > drivers/scsi/hpsa.c:2033:5: error: 'sd' may be used uninitialized in this > function [-Werror=maybe-uninitialized] > > This reverts back

[PATCH] spi: use sg_next for walking through the allocated scatterlist table

A null dereference or Oops exception might occurs when reading at once the whole content of an spi-nor of big enough size that requires an scatterlist table that does not fit into one single page. The spi_map_buf function is ignoring the chained sg case by dereferenceing the scatterlist elements

Re: [PATCH 4/6] efi: Get the secure boot status

Lukas Wunner wrote: > > +int efi_get_secureboot(void) > > It looks like you didn't compile-test this on ARM. Yes. What arm config would you suggest? > > +#define f_getvar(...) efi_call_runtime(get_variable, __VA_ARGS__) > > + > > + status = f_getvar((efi_char16_t

Re: [PATCH 4/6] efi: Get the secure boot status

David Howells wrote: > That makes it less clear. I think something like this makes it much more > obvious: > > static efi_status_t get_efi_var(const efi_char16_t *name, > const efi_guid_t *vendor, > u32 *attr,

Re: [PATCH 2/2] virtio_ring: fix complaint by sparse

On Tue, Nov 22, 2016 at 01:51:50PM +0800, Gonglei wrote: > # make C=2 CF="-D__CHECK_ENDIAN__" ./drivers/virtio/ > > drivers/virtio/virtio_ring.c:423:19: warning: incorrect type in assignment > (different base types) > drivers/virtio/virtio_ring.c:423:19:expected unsigned int [unsigned] >

[PATCH v3 2/2] mfd: arizona: Correctly clean up after IRQs

Currently we leak a lot of things when tearing down the IRQs this patch fixes this cleaning up both the IRQ mappings and the IRQ domain itself. Signed-off-by: Charles Keepax --- Changes since v2: - Updated to use the defines added in the previous patch

Re: Regression: Failed boots bisected to 4cd13c21b207 "softirq: Let ksoftirqd do its job"

Hi Eric, On Tue, Nov 22, 2016 at 06:29:33AM -0800, Eric Dumazet wrote: On Tue, Nov 22, 2016 at 2:33 AM, Brian Starkey wrote: Hi, On Fri, Nov 18, 2016 at 01:40:43AM +0100, Thomas Gleixner wrote: Brian, On Thu, 17 Nov 2016, Brian Starkey wrote: No joy with this

Re: [PATCH 1/2] power: supply: sbs-battery: use fixed device name

Hi Sebastian, sorry I wasn't aware of that feature, I'll have a look at the whole thing and rework the patch. Regards, Nicolas On 22/11/16 16:23, Sebastian Reichel wrote: > Hi, > > On Mon, Nov 21, 2016 at 07:04:50PM +0100, Nicola Saenz Julienne wrote: >> The current device name for sbs-battery

Re: wl1251 & mac address & calibration data

On Tuesday 22 November 2016 16:22:57 Michal Kazior wrote: > On 21 November 2016 at 16:51, Pali Rohár wrote: > > On Friday 11 November 2016 18:20:50 Pali Rohár wrote: > >> Hi! I will open discussion about mac address and calibration data for > >> wl1251 wireless chip again...

Re: [HMM v13 01/18] mm/memory/hotplug: convert device parameter bool to set of flags

On Tue, Nov 22, 2016 at 11:05:30AM +0530, Anshuman Khandual wrote: > On 11/21/2016 05:57 PM, Jerome Glisse wrote: > > On Mon, Nov 21, 2016 at 12:11:50PM +0530, Anshuman Khandual wrote: > >> On 11/18/2016 11:48 PM, Jérôme Glisse wrote: > > > > [...] > > > >>> @@ -956,7 +963,7 @@

Re: [PATCH v1 3/3] kvm: svm: Use the hardware provided GPA instead of page walk

On 11/21/2016 9:07 AM, Paolo Bonzini wrote: > > > On 14/11/2016 23:16, Brijesh Singh wrote: >> From: Tom Lendacky >> >> When a guest causes a NPF which requires emulation, KVM sometimes walks >> the guest page tables to translate the GVA to a GPA. This is unnecessary >>

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