[PATCH v6 3/8] test_firmware: add partial read support for request_firmware_into_buf

Add additional hooks to test_firmware to pass in support for partial file read using request_firmware_into_buf. buf_size: size of buffer to request firmware into partial: indicates that a partial file request is being made file_offset: to indicate offset into file to request Signed-off-by: Scott

[PATCH v6 6/8] misc: bcm-vk: add Broadcom VK driver

Add Broadcom VK driver offload engine. This driver interfaces to the VK PCIe offload engine to perform should offload functions as video transcoding on multiple streams in parallel. VK device is booted from files loaded using request_firmware_into_buf mechanism. After booted card status is

[PATCH v6 1/8] fs: introduce kernel_pread_file* support

Add kernel_pread_file* support to kernel to allow for partial read of files with an offset into the file. Existing kernel_read_file functions call new kernel_pread_file functions with offset=0 and opt=KERNEL_PREAD_WHOLE. Signed-off-by: Scott Branden --- fs/exec.c | 95

[PATCH v6 4/8] firmware: test partial file reads of request_firmware_into_buf

Add firmware tests for partial file reads of request_firmware_into_buf. Signed-off-by: Scott Branden --- .../selftests/firmware/fw_filesystem.sh | 80 +++ 1 file changed, 80 insertions(+) diff --git a/tools/testing/selftests/firmware/fw_filesystem.sh

[PATCH v6 2/8] firmware: add offset to request_firmware_into_buf

Add offset to request_firmware_into_buf to allow for portions of firmware file to be read into a buffer. Necessary where firmware needs to be loaded in portions from file in memory constrained systems. Signed-off-by: Scott Branden --- drivers/base/firmware_loader/firmware.h | 5 +++

[PATCH v6 0/8] firmware: add partial read support in request_firmware_into_buf

This patch series adds partial read support in request_firmware_into_buf. In order to accept the enhanced API it has been requested that kernel selftests and upstreamed driver utilize the API enhancement and so are included in this patch series. Also in this patch series is the addition of a new

[PATCH v6 7/8] MAINTAINERS: bcm-vk: add maintainer for Broadcom VK Driver

Add maintainer entry for new Broadcom VK Driver Signed-off-by: Scott Branden --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index b045b70e54df..9fbf255fe093 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -3656,6 +3656,13 @@ L:

Re: [PATCHSET v5 0/12] Add support for async buffered reads

On 6/5/20 4:54 PM, Andres Freund wrote: > Hi, > > On 2020-06-05 16:49:24 -0600, Jens Axboe wrote: >> Yes that's expected, if we have to fallback to ->readpage(), then it'll >> go to a worker. read-ahead is what drives the async nature of it, as we >> issue the range (plus more, depending on RA

Re: [PATCHSET v5 0/12] Add support for async buffered reads

Hi, On 2020-06-05 16:49:24 -0600, Jens Axboe wrote: > Yes that's expected, if we have to fallback to ->readpage(), then it'll > go to a worker. read-ahead is what drives the async nature of it, as we > issue the range (plus more, depending on RA window) as read-ahead for > the normal read, then

Re: [PATCH] iomap: Handle I/O errors gracefully in page_mkwrite

On Sat, Jun 06, 2020 at 07:48:41AM +1000, Dave Chinner wrote: > On Fri, Jun 05, 2020 at 05:48:26AM -0700, Matthew Wilcox wrote: > > ... I don't think that's the interesting path. I mean, that's > > the submission path, and usually we discover errors in the completion > > path, not the submission

Re: [PATCHSET v5 0/12] Add support for async buffered reads

On 6/5/20 4:36 PM, Andres Freund wrote: > Hi, > > On 2020-06-05 15:30:44 -0700, Andres Freund wrote: >> On 2020-06-05 15:21:34 -0600, Jens Axboe wrote: > I can reproduce this, and I see what it is. I'll send out a patch soonish. Thinko, can you try with this on top? >>> >>> Sorry

Re: [PATCH v1 5/5] kselftests: cgroup: add perpcu memory accounting test

On Fri, Jun 05, 2020 at 08:07:51PM +, Dennis Zhou wrote: > On Thu, May 28, 2020 at 04:25:08PM -0700, Roman Gushchin wrote: > > Add a simple test to check the percpu memory accounting. > > The test creates a cgroup tree with 1000 child cgroups > > and checks values of memory.current and

Re: [PATCH v1 2/5] mm: memcg/percpu: account percpu memory to memory cgroups

On Fri, Jun 05, 2020 at 07:49:53PM +, Dennis Zhou wrote: > On Thu, May 28, 2020 at 04:25:05PM -0700, Roman Gushchin wrote: > > Percpu memory is becoming more and more widely used by various > > subsystems, and the total amount of memory controlled by the percpu > > allocator can make a good

[PATCHv2 2/6] power: supply: gpio-charger: Make gpios optional

While strongly recommended, not all devices have a gpio to detect if the charger is connected. This moves the 'gpios' from required to optional section. This also modifies error handling for the GPIO a bit: We no longer fallback to pdata, if a GPIO is specified using GPIO descriptor tables. This

[PATCHv2 3/6] power: supply: gpio-charger: add charge-current-limit feature

Add new charge-current-limit feature to gpio-charger. Signed-off-by: Sebastian Reichel --- .../bindings/power/supply/gpio-charger.yaml | 31 drivers/power/supply/gpio-charger.c | 140 ++ 2 files changed, 171 insertions(+) diff --git

[PATCHv2 0/6] misc. gpio-charger patches

Hi, This is v2 of a patchset for gpio-charger. The patches are mostly unrelated to each other, but have some dependencies. Merge plan is: Assuming there are no huge blockers, the plan is to merge patches 1-3 through power-supply subsystem for 5.9. The ARM patches can go via ARM subsystem for

[PATCHv2 4/6] ARM: pxa: Use GPIO descriptor for gpio-charger

Provide AC detect GPIO via gpiod table instead of legacy platform data so that legacy GPIO support can be removed from the driver. Also remove useless IRQ resource, which is not used by the driver. Due to lack of hardware this has only been compile tested. Signed-off-by: Sebastian Reichel ---

[PATCHv2 5/6] ARM: sa1100: Use GPIO descriptor for gpio-charger

Provide AC detect GPIO via gpiod table instead of legacy platform data so that legacy GPIO support can be removed from the driver. Due to lack of hardware this has only been compile tested. Signed-off-by: Sebastian Reichel --- arch/arm/mach-sa1100/collie.c | 11 ++- 1 file changed, 10

[PATCHv2 1/6] dt-bindings: power: supply: gpio-charger: convert to yaml

Convert the gpio-charger bindings from text format to new YAML based representation. Signed-off-by: Sebastian Reichel --- .../bindings/power/supply/gpio-charger.txt| 31 -- .../bindings/power/supply/gpio-charger.yaml | 58 +++ 2 files changed, 58 insertions(+), 31

[PATCHv2 6/6] power: supply: gpio-charger: drop legacy GPIO support

All board files have been converted to use boardfile GPIO descriptor tables, so GPIO support can be removed from platform data. Signed-off-by: Sebastian Reichel --- drivers/power/supply/gpio-charger.c | 30 + include/linux/power/gpio-charger.h | 5 - 2 files

Re: [PATCH] x86/umip: Add emulation/spoofing for SLDT and STR instructions

On Fri, Jun 05, 2020 at 11:58:13AM -0700, Brendan Shanks wrote: > > > On Jun 3, 2020, at 9:39 PM, Andy Lutomirski wrote: > > > > On Wed, Jun 3, 2020 at 5:12 PM Ricardo Neri > > > > wrote: > >> > >> On Tue, Jun 02, 2020 at 11:42:12AM -0700, Brendan

Hang on wireless removal..

So I think there's something wrong with wireless networking, and (likely) in particular turning off wireless. And I think the problem came in this merge window, because now my machine hangs on shutdown. My new desktop is otherwise working fine, but it has some unnecessary wireless capability on

Re: [PATCHSET v5 0/12] Add support for async buffered reads

Hi, On 2020-06-05 15:30:44 -0700, Andres Freund wrote: > On 2020-06-05 15:21:34 -0600, Jens Axboe wrote: > > >> I can reproduce this, and I see what it is. I'll send out a patch > > >> soonish. > > > > > > Thinko, can you try with this on top? > > > > Sorry that was incomplete, please use this

Re: [PATCH v2] rtc: fsl-ftm-alarm: fix freeze(s2idle) failed to wake

On Mon, 1 Jun 2020 15:19:14 +0800, Ran Wang wrote: > Use dev_pm_set_wake_irq() instead of flag IRQF_NO_SUSPEND to enable > wakeup system feature for both freeze(s2idle) and mem(deep). Applied, thanks! [1/1] rtc: fsl-ftm-alarm: fix freeze(s2idle) failed to wake commit:

Re: [PATCH v5 5/7] blktrace: fix debugfs use after free

On Thu, Jun 04, 2020 at 09:48:43PM -0700, Bart Van Assche wrote: > On 2020-06-01 10:05, Luis Chamberlain wrote: > > diff --git a/kernel/trace/blktrace.c b/kernel/trace/blktrace.c > > index a55cbfd060f5..5b0310f38e11 100644 > > --- a/kernel/trace/blktrace.c > > +++ b/kernel/trace/blktrace.c > > @@

Re: [PATCHSET v5 0/12] Add support for async buffered reads

Hi, On 2020-06-05 15:21:34 -0600, Jens Axboe wrote: > >> I can reproduce this, and I see what it is. I'll send out a patch soonish. > > > > Thinko, can you try with this on top? > > Sorry that was incomplete, please use this one! That seems to fix it! Yay. Bulk buffered reads somehow don't

Re: [PATCH] leds: mt6360: Add LED driver for MT6360

Hi Gene, Thank you for the patch. Please find my comments in the code below. On 6/4/20 8:26 AM, Gene Chen wrote: From: Gene Chen Add MT6360 LED driver include 2-channel Flash LED with torch/strobe mode, and 3-channel RGB LED support Register/Flash/Breath Mode Signed-off-by: Gene Chen

[rcu:dev.2020.06.02a 85/90] smp.c:undefined reference to `__udivdi3'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2020.06.02a head: 5216948905dd07a84cef8a7dc72c2ec076802efd commit: 92ebbb71443dced2019cd24b737ce60b03a29e10 [85/90] EXP kernel/smp: Provide CSD lock timeout diagnostics config: i386-allyesconfig (attached as

[PATCH v1] arm64/module: Optimize module load time by optimizing PLT counting

When loading a module, module_frob_arch_sections() tries to figure out the number of PLTs that'll be needed to handle all the RELAs. While doing this, it tries to dedupe PLT allocations for multiple R_AARCH64_CALL26 relocations to the same symbol. It does the same for R_AARCH64_JUMP26 relocations

Re: 5.7.0 / BUG: kernel NULL pointer dereference / setup_cpu_watcher

On Fri, 5 Jun 2020, Andrew Cooper wrote: > PVH domains don't have the emulated platform device, so Linux will be > finding ~0 when it goes looking in config space. > > The diagnostic should be skipped in that case, to avoid giving the false > impression that something is wrong. Understood,

Re: [PATCH 4.19 00/28] 4.19.127-rc1 review

On 6/5/20 8:15 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.19.127 release. There are 28 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made

Re: [PATCH 5.4 00/38] 5.4.45-rc1 review

On 6/5/20 8:14 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 5.4.45 release. There are 38 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made

[PATCH 0/2] DRA7 timer/mailbox dts fixes

Hi Tony, The following 2 patches are couple of minor fixes that clean up couple of commits from the "ARM: dts: dra7/am57xx: remoteproc support" series [1]. Please pick these for the 5.8-rc fixes. The issues look to be result of incorrect rebase-conflict resolution of the downstream TI patches

[PATCH 1/2] ARM: dts: dra7: Fix timer nodes properly for timer_sys_ck clocks

The commit 5390130f3b28 ("ARM: dts: dra7: add timer_sys_ck entries for IPU/DSP timers") was added to allow the OMAP clocksource timer driver to use the clock aliases when reconfiguring the parent clock source for the timer functional clocks after the timer_sys_ck clock aliases got cleaned up in

Re: [PATCH 5.6 00/43] 5.6.17-rc1 review

On 6/5/20 8:14 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 5.6.17 release. There are 43 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made

[PATCH 2/2] ARM: dts: dra7-evm-common: Fix duplicate mailbox nodes

The mailbox nodes defined in various dts files have been moved to common dra7-ipu-dsp-common.dtsi and dra74-ipu-dsp-common.dtsi files in commit a11a2f73b32d ("ARM: dts: dra7-ipu-dsp-common: Move mailboxes into common files"), but the nodes were erroneously left out in the dra7-evm-common.dtsi

Re: [rcu:dev.2020.06.02a 85/90] kernel/smp.c:122: undefined reference to `__udivdi3'

P kernel/smp: > Provide CSD lock timeout diagnostics > config: i386-randconfig-c001-20200605 (attached as .config) > compiler: gcc-9 (Debian 9.3.0-13) 9.3.0 > > If you fix the issue, kindly add following tag as appropriate > Reported-by: kernel test robot > > All errors (new on

Re: [PATCH 5.7 00/14] 5.7.1-rc1 review

On 6/5/20 8:14 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 5.7.1 release. There are 14 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by

Re: [PATCH] shmem, memcg: enable memcg aware shrinker

On Thu, Jun 4, 2020 at 1:17 AM Greg Thelen wrote: > > Yang Shi wrote: > > > On Sun, May 31, 2020 at 8:22 PM Greg Thelen wrote: > >> > >> Since v4.19 commit b0dedc49a2da ("mm/vmscan.c: iterate only over charged > >> shrinkers during memcg shrink_slab()") a memcg aware shrinker is only > >>

Re: [PATCH v2] spi: bcm2835: Enable shared interrupt support

On 6/5/2020 7:41 AM, Robin Murphy wrote: > On 2020-06-05 14:46, Robin Murphy wrote: >> On 2020-06-05 14:20, Mark Brown wrote: >>> On Fri, Jun 05, 2020 at 12:34:36PM +0100, Robin Murphy wrote: On 2020-06-04 22:28, Florian Fainelli wrote: >>> > For the BCM2835 case which is deemed

Re: [RFC] perf/core: allow ftrace for functions in kernel/event/core.c

On Fri, 5 Jun 2020 21:58:48 + Song Liu wrote: > > How does this work in your tests? I started it, but got distracted by other work. It did not crash with the little testing I did do. I wanted to also look at my patch that adds tracing to the ftrace directory too. I'll try to remember to

Re: [RFC][PATCH] slimbus: core: Set fwnode for a device when setting of_node

On Fri, Jun 5, 2020 at 2:44 PM Saravana Kannan wrote: > On Fri, Jun 5, 2020 at 2:19 PM John Stultz wrote: > > > > From: Saravana Kannan > > > > When setting the of_node for a newly created device, also set the > > fwnode. This allows fw_devlink to work for slimbus devices. > > > > Cc: Srinivas

Re: [RFC] perf/core: allow ftrace for functions in kernel/event/core.c

Hi Steven, > On May 26, 2020, at 3:04 PM, Steven Rostedt wrote: > > On Tue, 26 May 2020 23:54:15 +0200 > Peter Zijlstra wrote: > >> On Tue, May 26, 2020 at 09:46:29PM +, Song Liu wrote: >>> >>> On May 26, 2020, at 2:39 PM, Peter Zijlstra wrote: On Tue, May 26, 2020 at

Re: [PATCH] iomap: Handle I/O errors gracefully in page_mkwrite

On Fri, Jun 05, 2020 at 05:48:26AM -0700, Matthew Wilcox wrote: > On Fri, Jun 05, 2020 at 01:07:58PM +1000, Dave Chinner wrote: > > On Thu, Jun 04, 2020 at 07:24:51PM -0700, Matthew Wilcox wrote: > > > On Fri, Jun 05, 2020 at 10:31:59AM +1000, Dave Chinner wrote: > > > > On Thu, Jun 04, 2020 at

[PATCH] virtio_net: Unregister and re-register xdp_rxq across freeze/restore

Unregister each queue's xdp_rxq during freeze, and re-register the new instance during restore. All queues are released during free and recreated during restore, i.e. the pre-freeze xdp_rxq will be lost. The bug is detected by WARNs in xdp_rxq_info_unreg() and xdp_rxq_info_unreg_mem_model() that

RE: slub freelist issue / BUG: unable to handle page fault for address: 000000003ffe0018

> -Original Message- > From: Vegard Nossum > Sent: Friday, June 5, 2020 7:45 AM > To: Vlastimil Babka ; Rafael J. Wysocki > ; Moore, Robert ; Kaneda, > Erik > Cc: Kees Cook ; Wysocki, Rafael J > ; Christoph Lameter ; Andrew > Morton ; Marco Elver ; > Waiman Long ; LKML

[PATCH 00/21] KVM: Cleanup and unify kvm_mmu_memory_cache usage

This series resurrects Christoffer Dall's series[1] to provide a common MMU memory cache implementation that can be shared by x86, arm64 and MIPS. It also picks up a suggested change from Ben Gardon[2] to clear shadow page tables during initial allocation so as to avoid clearing entire pages

[PATCH 15/21] KVM: Move x86's MMU memory cache helpers to common KVM code

Move x86's memory cache helpers to common KVM code so that they can be reused by arm64 and MIPS in future patches. Suggested-by: Christoffer Dall Signed-off-by: Sean Christopherson --- arch/x86/kvm/mmu/mmu.c | 53 -- include/linux/kvm_host.h | 7 +

Re: [RFC][PATCH] slimbus: core: Set fwnode for a device when setting of_node

Hi John, On Fri, Jun 5, 2020 at 2:19 PM John Stultz wrote: > > From: Saravana Kannan > > When setting the of_node for a newly created device, also set the > fwnode. This allows fw_devlink to work for slimbus devices. > > Cc: Srinivas Kandagatla > Cc: alsa-de...@alsa-project.org >

[PATCH 01/21] KVM: x86/mmu: Track the associated kmem_cache in the MMU caches

Track the kmem_cache used for non-page KVM MMU memory caches instead of passing in the associated kmem_cache when filling the cache. This will allow consolidating code and other cleanups. No functional change intended. Signed-off-by: Sean Christopherson --- arch/x86/include/asm/kvm_host.h |

[PATCH 10/21] KVM: x86/mmu: Make __GFP_ZERO a property of the memory cache

Add a gfp_zero flag to 'struct kvm_mmu_memory_cache' and use it to control __GFP_ZERO instead of hardcoding a call to kmem_cache_zalloc(). A future patch needs such a flag for the __get_free_page() path, as gfn arrays do not need/want the allocator to zero the memory. Convert the kmem_cache paths

[PATCH 16/21] KVM: arm64: Drop @max param from mmu_topup_memory_cache()

Replace the @max param in mmu_topup_memory_cache() and instead use ARRAY_SIZE() to terminate the loop to fill the cache. This removes a BUG_ON() and sets the stage for moving arm64 to the common memory cache implementation. No functional change intended. Signed-off-by: Sean Christopherson ---

[PATCH 08/21] KVM: x86/mmu: Clean up the gorilla math in mmu_topup_memory_caches()

Clean up the minimums in mmu_topup_memory_caches() to document the driving mechanisms behind the minimums. Now that encountering an empty cache is unlikely to trigger BUG_ON(), it is less dangerous to be more precise when defining the minimums. For rmaps, the logic is 1 parent PTE per level,

[PATCH 17/21] KVM: arm64: Use common code's approach for __GFP_ZERO with memory caches

Add a "gfp_zero" member to arm64's 'struct kvm_mmu_memory_cache' to make the struct and its usage compatible with the common 'struct kvm_mmu_memory_cache' in linux/kvm_host.h. This will minimize code churn when arm64 moves to the common implementation in a future patch, at the cost of temporarily

[PATCH 11/21] KVM: x86/mmu: Zero allocate shadow pages (outside of mmu_lock)

Set __GFP_ZERO for the shadow page memory cache and drop the explicit clear_page() from kvm_mmu_get_page(). This moves the cost of zeroing a page to the allocation time of the physical page, i.e. when topping up the memory caches, and thus avoids having to zero out an entire page while holding

[PATCH 03/21] KVM: x86/mmu: Use consistent "mc" name for kvm_mmu_memory_cache locals

Use "mc" for local variables to shorten line lengths and provide consistent names, which will be especially helpful when some of the helpers are moved to common KVM code in future patches. No functional change intended. Signed-off-by: Sean Christopherson --- arch/x86/kvm/mmu/mmu.c | 24

[PATCH 07/21] KVM: x86/mmu: Topup memory caches after walking GVA->GPA

Topup memory caches after walking the GVA->GPA translation during a shadow page fault, there is no need to ensure the caches are full when walking the GVA. As of commit f5a1e9f89504f ("KVM: MMU: remove call to kvm_mmu_pte_write from walk_addr"), the FNAME(walk_addr) flow no longer add rmaps via

[PATCH v8 16/16] s390/vfio-ap: handle probe/remove not due to host AP config changes

AP queue devices are probed or removed for reasons other than changes to the host AP configuration: * Each queue device associated with a card device will get created and probed when the state of the AP adapter represented by the card device dynamically changes from standby to online. * Each

[PATCH v8 00/16] s390/vfio-ap: dynamic configuration support

Note: Patch 1 - s390/ap: introduce new ap function ap_get_qdev() - is not a part of this series. It is a forthcoming patch that is a prerequisite to this series and is being provided so this series will compile. The current design for AP pass-through does not support making

[PATCH 13/21] KVM: x86/mmu: Prepend "kvm_" to memory cache helpers that will be global

Rename the memory helpers that will soon be moved to common code and be made globaly available via linux/kvm_host.h. "mmu" alone is not a sufficient namespace for globally available KVM symbols. Opportunistically add "nr_" in mmu_memory_cache_free_objects() to make it clear the function returns

[PATCH v8 01/16] s390/ap: introduce new ap function ap_get_qdev()

From: Harald Freudenberger Provide a new interface function to be used by the ap drivers: struct ap_queue *ap_get_qdev(ap_qid_t qid); Returns ptr to the struct ap_queue device or NULL if there was no ap_queue device with this qid found. When something is found, the reference count of the

[PATCH 18/21] KVM: arm64: Use common KVM implementation of MMU memory caches

Move to the common MMU memory cache implementation now that the common code and arm64's existing code are semantically compatible. No functional change intended. Suggested-by: Christoffer Dall Signed-off-by: Sean Christopherson --- arch/arm64/include/asm/kvm_host.h | 12 ---

[PATCH v8 03/16] s390/vfio-ap: manage link between queue struct and matrix mdev

A vfio_ap_queue structure is created for each queue device probed. To ensure that the matrix mdev to which a queue's APQN is assigned is linked to the queue structure as long as the queue device is bound to the vfio_ap device driver, let's go ahead and manage these links when the queue device is

[PATCH v8 06/16] s390/vfio-ap: introduce shadow APCB

The APCB is a field within the CRYCB that provides the AP configuration to a KVM guest. Let's introduce a shadow copy of the KVM guest's APCB and maintain it for the lifespan of the guest. Signed-off-by: Tony Krowiak --- drivers/s390/crypto/vfio_ap_ops.c | 33 +++

Re: [PATCH v4 05/12] PCI: brcmstb: Add suspend and resume pm_ops

On 6/5/2020 2:26 PM, Jim Quinlan wrote: > From: Jim Quinlan > > Broadcom Set-top (BrcmSTB) boards typically support S2, S3, and S5 suspend > and resume. Now the PCIe driver may do so as well. > > Signed-off-by: Jim Quinlan Acked-by: Florian Fainelli -- Florian

[PATCH v8 07/16] s390/vfio-ap: sysfs attribute to display the guest's matrix

The matrix of adapters and domains configured in a guest's CRYCB may differ from the matrix of adapters and domains assigned to the matrix mdev, so this patch introduces a sysfs attribute to display the matrix of a guest using the matrix mdev. For a matrix mdev denoted by $uuid, the crycb for a

Re: [GIT PULL] first round of SCSI updates for the 5.6+ merge window

On Fri, 2020-06-05 at 14:25 -0700, Linus Torvalds wrote: > On Fri, Jun 5, 2020 at 2:18 PM James Bottomley > wrote: > > > > Um, no, shuffles feet ... I actually tagged the wrong branch: > > Ok, now I see the changes, but I see more than you reported. > > These seem to be new compared to your

[PATCH v8 11/16] s390/vfio-ap: allow configuration of matrix mdev in use by a KVM guest

The current support for pass-through crypto adapters does not allow configuration of a matrix mdev when it is in use by a KVM guest. Let's allow AP resources - i.e., adapters, domains and control domains - to be assigned to or unassigned from a matrix mdev while it is in use by a guest. This is in

[PATCH v8 08/16] s390/vfio-ap: filter matrix for unavailable queue devices

Even though APQNs for queues that are not in the host's AP configuration may be assigned to a matrix mdev, we do not want to set bits in the guest's APCB for APQNs that do not reference AP queue devices bound to the vfio_ap device driver. Ideally, it would be great if such APQNs could be filtered

[PATCH v8 15/16] s390/vfio-ap: handle AP bus scan completed notification

Implements the driver callback invoked by the AP bus when the AP bus scan has completed. Since this callback is invoked after binding the newly added devices to their respective device drivers, the vfio_ap driver will attempt to plug the adapters, domains and control domains into each guest using

[PATCH v8 12/16] s390/vfio-ap: allow hot plug/unplug of AP resources using mdev device

Let's hot plug/unplug adapters, domains and control domains assigned to or unassigned from an AP matrix mdev device while it is in use by a guest per the following: * When the APID of an adapter is assigned to a matrix mdev in use by a KVM guest, the adapter will be hot plugged into the KVM

[PATCH v8 10/16] s390/vfio-ap: allow assignment of unavailable AP queues to mdev device

The current implementation does not allow assignment of an AP adapter or domain to an mdev device if the APQNs resulting from the assignment do not reference AP queue devices that are bound to the vfio_ap device driver. This patch allows assignment of AP resources to the matrix mdev as long as the

[PATCH v8 14/16] s390/vfio-ap: handle host AP config change notification

Implements the driver callback invoked by the AP bus when the host AP configuration has changed. Since this callback is invoked prior to unbinding a device from its device driver, the vfio_ap driver will respond by unplugging the AP adapters, domains and control domains removed from the host's AP

[PATCH v8 09/16] s390/vfio_ap: add qlink from ap_matrix_mdev struct to vfio_ap_queue struct

In order to make retrieval of a vfio_ap_queue struct more efficient when we already have a pointer to the ap_matrix_mdev to which the queue's APQN is assigned, let's go ahead and add a link from the ap_matrix_mdev struct to the vfio_ap_queue struct. Signed-off-by: Tony Krowiak ---

Re: [PATCH 03/12] x86/xen: Introduce new function to map HYPERVISOR_shared_info on Resume

On 6/4/20 7:03 PM, Anchal Agarwal wrote: > On Sat, May 30, 2020 at 07:02:01PM -0400, Boris Ostrovsky wrote: >> CAUTION: This email originated from outside of the organization. Do not >> click links or open attachments unless you can confirm the sender and know >> the content is safe. >> >> >> >>

[PATCH v8 02/16] s390/vfio-ap: use new AP bus interface to search for queue devices

This patch refactor's the vfio_ap device driver to use the AP bus's ap_get_qdev() function to retrieve the vfio_ap_queue struct containing information about a queue that is bound to the vfio_ap device driver. The bus's ap_get_qdev() function retrieves the queue device from a hashtable keyed by

[PATCH v8 13/16] s390/zcrypt: Notify driver on config changed and scan complete callbacks

From: Harald Freudenberger This patch intruduces an extension to the ap bus to notify drivers on crypto config changed and bus scan complete events. Two new callbacks are introduced for ap_drivers: void (*on_config_changed)(struct ap_config_info *new_config_info,

[PATCH v8 05/16] s390/vfio-ap: implement in-use callback for vfio_ap driver

Let's implement the callback to indicate when an APQN is in use by the vfio_ap device driver. The callback is invoked whenever a change to the apmask or aqmask would result in one or more queue devices being removed from the driver. The vfio_ap device driver will indicate a resource is in use if

[PATCH v8 04/16] s390/zcrypt: driver callback to indicate resource in use

Introduces a new driver callback to prevent a root user from unbinding an AP queue from its device driver if the queue is in use. The intent of this callback is to provide a driver with the means to prevent a root user from inadvertently taking a queue away from a matrix mdev and giving it to the

[PATCH 14/21] KVM: Move x86's version of struct kvm_mmu_memory_cache to common code

Move x86's 'struct kvm_mmu_memory_cache' to common code in anticipation of moving the entire x86 implementation code to common KVM and reusing it for arm64 and MIPS. Add a new architecture specific asm/kvm_types.h to control the existence and parameters of the struct. The new header is needed to

[PATCH 02/21] KVM: x86/mmu: Consolidate "page" variant of memory cache helpers

Drop the "page" variants of the topup/free memory cache helpers, using the existence of an associated kmem_cache to select the correct alloc or free routine. No functional change intended. Signed-off-by: Sean Christopherson --- arch/x86/kvm/mmu/mmu.c | 37 +++--

[PATCH 04/21] KVM: x86/mmu: Remove superfluous gotos from mmu_topup_memory_caches()

Return errors directly from mmu_topup_memory_caches() instead of branching to a label that does the same. No functional change intended. Signed-off-by: Sean Christopherson --- arch/x86/kvm/mmu/mmu.c | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git

[PATCH 05/21] KVM: x86/mmu: Try to avoid crashing KVM if a MMU memory cache is empty

Attempt to allocate a new object instead of crashing KVM (and likely the kernel) if a memory cache is unexpectedly empty. Use GFP_ATOMIC for the allocation as the caches are used while holding mmu_lock. The immediate BUG_ON() makes the code unnecessarily explosive and led to confusing minimums

[rcu:dev.2020.06.02a 85/90] kernel/smp.c:122: undefined reference to `__udivdi3'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2020.06.02a head: 5216948905dd07a84cef8a7dc72c2ec076802efd commit: 92ebbb71443dced2019cd24b737ce60b03a29e10 [85/90] EXP kernel/smp: Provide CSD lock timeout diagnostics config: i386-randconfig-c001-20200605

[PATCH 06/21] KVM: x86/mmu: Move fast_page_fault() call above mmu_topup_memory_caches()

Avoid refilling the memory caches and potentially slow reclaim/swap when handling a fast page fault, which does not need to allocate any new objects. Signed-off-by: Sean Christopherson --- arch/x86/kvm/mmu/mmu.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH 20/21] KVM: MIPS: Account pages used for GPA page tables

Use GFP_KERNEL_ACCOUNT instead of GFP_KERNEL when allocating pages for the the GPA page tables. The primary motivation for accounting the allocations is to align with the common KVM memory cache helpers in preparation for moving to the common implementation in a future patch. The actual

[PATCH 12/21] KVM: x86/mmu: Skip filling the gfn cache for guaranteed direct MMU topups

Don't bother filling the gfn array cache when the caller is a fully direct MMU, i.e. won't need a gfn array for shadow pages. Signed-off-by: Sean Christopherson --- arch/x86/kvm/mmu/mmu.c | 18 ++ arch/x86/kvm/mmu/paging_tmpl.h | 4 ++-- 2 files changed, 12

[PATCH 21/21] KVM: MIPS: Use common KVM implementation of MMU memory caches

Move to the common MMU memory cache implementation now that the common code and MIPS's existing code are semantically compatible. No functional change intended. Suggested-by: Christoffer Dall Signed-off-by: Sean Christopherson --- arch/mips/include/asm/kvm_host.h | 11 -

[PATCH 19/21] KVM: MIPS: Drop @max param from mmu_topup_memory_cache()

Replace the @max param in mmu_topup_memory_cache() and instead use ARRAY_SIZE() to terminate the loop to fill the cache. This removes a BUG_ON() and sets the stage for moving MIPS to the common memory cache implementation. No functional change intended. Signed-off-by: Sean Christopherson ---

[PATCH 09/21] KVM: x86/mmu: Separate the memory caches for shadow pages and gfn arrays

Use separate caches for allocating shadow pages versus gfn arrays. This sets the stage for specifying __GFP_ZERO when allocating shadow pages without incurring extra cost for gfn arrays. No functional change intended. Signed-off-by: Sean Christopherson --- arch/x86/include/asm/kvm_host.h | 3

Re: [PATCH] IMA: Add log statements for failure conditions

On 6/5/20 2:34 PM, Mimi Zohar wrote: Maybe I can use the audit_msgno "AUDIT_INTEGRITY_PCR" with appropriate strings for "op" and "cause". Mimi - please let me know if you think this audit_msgno would be ok to use. I see this code used, for instance, for boot aggregate measurement.

Re: [PATCH] IMA: Add log statements for failure conditions

On Fri, 2020-06-05 at 14:09 -0700, Lakshmi Ramasubramanian wrote: > On 6/5/20 1:49 PM, Paul Moore wrote: > > > > >> Since a pr_xyz() call was already present, I just wanted to change the > >> log level to keep the code change to the minimum. But if audit log is > >> the right approach for this

[PATCH v6 5/5] cpufreq: qcom: Disable fast switch when scaling DDR/L3

Disable fast switch when the opp-tables required for scaling DDR/L3 are populated. Signed-off-by: Sibi Sankar --- v6: * No change v5: * Drop dev_pm_opp_get_path_count [Saravana] drivers/cpufreq/qcom-cpufreq-hw.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH v6 1/5] cpufreq: blacklist SDM845 in cpufreq-dt-platdev

Add SDM845 to cpufreq-dt-platdev blacklist since the actual scaling is handled by the 'qcom-cpufreq-hw' driver. Reviewed-by: Amit Kucheria Reviewed-by: Matthias Kaehlcke Signed-off-by: Sibi Sankar --- v6: * No change v5: * Picked up R-b from Amit v4: * Updated commit message [Matthias]

[PATCH v6 4/5] cpufreq: qcom: Update the bandwidth levels on frequency change

Add support to parse optional OPP table attached to the cpu node when the OPP bandwidth values are populated. This allows for scaling of DDR/L3 bandwidth levels with frequency change. Signed-off-by: Sibi Sankar --- v6: * Add global flag to distinguish between voltage update and opp add. Use

[PATCH v6 3/5] OPP: Add and export helper to set bandwidth

Add and export 'dev_pm_opp_set_bw' to set the bandwidth levels associated with an OPP. Signed-off-by: Sibi Sankar --- v6: * Pass NULL to _set_opp_bw v5: https://lkml.org/lkml/2020/5/27/7 * Rework the patch based on ^^ v4: https://patchwork.kernel.org/patch/11019737/ * Pass device opp to

[PATCH v6 0/5] DDR/L3 Scaling support on SDM845 and SC7180 SoCs

This patch series aims to extend cpu based scaling support to L3/DDR on SDM845 and SC7180 SoCs. Patches [1-2] - Blacklist SDM845 and SC7180 in cpufreq-dt-platdev Patches [3-5] - Update bw levels based on cpu frequency change Based on Viresh's opp-next:

[PATCH v6 2/5] cpufreq: blacklist SC7180 in cpufreq-dt-platdev

Add SC7180 to cpufreq-dt-platdev blacklist since the actual scaling is handled by the 'qcom-cpufreq-hw' driver. Reviewed-by: Amit Kucheria Reviewed-by: Matthias Kaehlcke Signed-off-by: Sibi Sankar --- v6: * No change v5: * Picked up R-b from Amit v4: * Updated commit message [Matthias]

Re: [PATCH v2] docs: deprecated.rst: Add zero-length and one-element arrays

On 6/5/20 14:30, Kees Cook wrote: > On Fri, Jun 05, 2020 at 11:21:42AM -0500, Gustavo A. R. Silva wrote: >> Add zero-length and one-element arrays to the list. >> >> While I continue replacing zero-length and one-element arrays with >> flexible-array members, I need a reference to point people

[PATCH v4 01/12] PCI: brcmstb: PCIE_BRCMSTB depends on ARCH_BRCMSTB

From: Jim Quinlan Have PCIE_BRCMSTB depend on ARCH_BRCMSTB. Also set the default value to ARCH_BRCMSTB. Signed-off-by: Jim Quinlan Acked-by: Florian Fainelli Reviewed-by: Rob Herring --- drivers/pci/controller/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

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