On Thu, 22 Aug 2019 21:24:46 +0200,
Scott Branden wrote:
>
> 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.
AFAIU, this won't work with
On Mon, Aug 12, 2019 at 6:26 PM Hans de Goede wrote:
>
> Hi,
>
> On 12-08-19 18:08, Benjamin Tissoires wrote:
> > Both the G700 and the G700s are sharing the same receiver.
> > Include support for this receiver in hid-logitech-dj so that userspace
> > can differentiate both.
> >
> >
On Tue, Jul 30, 2019 at 04:46:37PM +0200, Paul Menzel wrote:
> Date: Tue, 30 Jul 2019 10:53:10 +0200
>
> Fix the error below triggered by `-Wimplicit-fallthrough`, by tagging
> it as an expected fall-through.
>
> arch/powerpc/kvm/book3s_32_mmu.c: In function
>
Hi Greg,
More testing on fastprc revealed few memory leaks in driver
and few corner cases.
These patches are the fixes for those cases.
One patch from Jorge is to remove unsed definition.
Thanks,
srini
Bjorn Andersson (2):
misc: fastrpc: Reference count channel context
misc: fastrpc: Don't
From: Bjorn Andersson
The channel context is referenced from the fastrpc user and might as
user space holds the file descriptor open outlive the fastrpc device,
which is removed when the remote processor is shutting down.
Reference count the channel context in order to retain this object until
dma buf refcount has to be done by the driver which is going to use the fd.
This driver already does refcount on the dmabuf fd if its actively using it
but also does an additional refcounting via extra ioctl.
This additional refcount can lead to memory leak in cases where the
applications fail to
From: Jorge Ramirez-Ortiz
Remove unused INIT_MEMLEN_MAX define.
Signed-off-by: Jorge Ramirez-Ortiz
Signed-off-by: Abhinav Asati
Signed-off-by: Vamsi Singamsetty
Signed-off-by: Srinivas Kandagatla
---
drivers/misc/fastrpc.c | 1 -
1 file changed, 1 deletion(-)
diff --git
On Tue, Jul 30, 2019 at 2:26 PM Filipe Laíns wrote:
>
> This patchs adds the new Lightspeed receiver. Currently it seems to only
> be used in the G305.
>
> Signed-off-by: Filipe Laíns
Applied to for-5.4/logitech
Cheers,
Benjamin
> ---
> drivers/hid/hid-ids.h | 3 ++-
>
dma buf scatter list is never freed, free it!
Orignally detected by kmemleak:
backtrace:
[] kmemleak_alloc+0x50/0x84
[] sg_kmalloc+0x38/0x60
[] __sg_alloc_table+0x60/0x110
[] sg_alloc_table+0x28/0x58
[] __sg_alloc_table_from_pages+0xc0/0x1ac
[]
From: Bjorn Andersson
As fastrpc_rpmsg_remove() returns the rpdev of the channel context is no
longer a valid object, so ensure to update the channel context to no
longer reference the old object and guard in the invoke code path
against dereferencing it.
TEST=stop and start remote proc1 using
On Fri, Aug 23, 2019 at 9:58 AM Chunfeng Yun wrote:
> It's used to support dual role switch via GPIO when use Type-B
> receptacle, typically the USB ID pin is connected to an input
> GPIO, and also used to enable/disable device when the USB Vbus
> pin is connected to an input GPIO.
>
>
The patch supports flextimer for lx2160a
Signed-off-by: Biwen Li
---
drivers/rtc/rtc-fsl-ftm-alarm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/rtc/rtc-fsl-ftm-alarm.c b/drivers/rtc/rtc-fsl-ftm-alarm.c
index 4f7259c2d6a3..2b81525f6db8 100644
---
Hi,
On Fri, Aug 23, 2019 at 11:42:28AM +0200, meg...@megous.com wrote:
> From: Ondrej Jirman
>
> Orange Pi 3 has AP6256 WiFi/BT module. WiFi part of the module is called
> bcm43356 and can be used with the brcmfmac driver. The module is powered by
> the two always on regulators (not AXP805).
>
>
Support flextimer for SoC LS1021A (ARM32)
Signed-off-by: Biwen Li
---
drivers/rtc/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
index 319bec4bef05..58d8b5f7cfc5 100644
--- a/drivers/rtc/Kconfig
+++ b/drivers/rtc/Kconfig
@@
The patch adds ftm_alarm0 DT node for Soc LX2160A
FlexTimer1 module is used to wakeup the system in deep sleep
Signed-off-by: Biwen Li
---
arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi | 18 ++
1 file changed, 18 insertions(+)
diff --git
On Thu, Aug 22, 2019 at 11:15:46AM +0200, Stefano Garzarella wrote:
> On Tue, Aug 20, 2019 at 09:28:28AM +0100, Stefan Hajnoczi wrote:
> > On Thu, Aug 01, 2019 at 05:25:41PM +0200, Stefano Garzarella wrote:
> > > +/* Wait for the remote to close the connection */
> > > +void
On Fri, 2019-08-23 at 17:47 +0800, Dilip Kota wrote:
[...]
> Thanks for pointing it out.
> Reset is not supported on LGM platform.
> I will update the reset_device() definition to "return -EOPNOTSUPP"
In that case you can just drop intel_reset_device() completely,
the core checks whether
On Fri, Aug 23, 2019 at 6:08 PM Maxime Ripard wrote:
>
> Hi,
>
> On Fri, Aug 23, 2019 at 11:42:28AM +0200, meg...@megous.com wrote:
> > From: Ondrej Jirman
> >
> > Orange Pi 3 has AP6256 WiFi/BT module. WiFi part of the module is called
> > bcm43356 and can be used with the brcmfmac driver. The
Hi Guido,
On Jo, 2019-08-22 at 19:03 +0200, Guido Günther wrote:
> Hi Robert,
> thanks for your comments! Most of this make sense, i have some
> comments
> inline below (mostly since I only have access to the imx8mq reference
> manual but not to the any NWL IP docs):
>
> On Thu, Aug 22, 2019 at
From: Colin Ian King
There is a spelling mistake in a dev_err error message. Fix it.
Signed-off-by: Colin Ian King
---
drivers/rtc/rtc-fsl-ftm-alarm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rtc/rtc-fsl-ftm-alarm.c b/drivers/rtc/rtc-fsl-ftm-alarm.c
index
Hello Maxime,
On Fri, Aug 23, 2019 at 12:08:07PM +0200, Maxime Ripard wrote:
> Hi,
>
> On Fri, Aug 23, 2019 at 11:42:28AM +0200, meg...@megous.com wrote:
> > From: Ondrej Jirman
> >
> > Orange Pi 3 has AP6256 WiFi/BT module. WiFi part of the module is called
> > bcm43356 and can be used with
On Mon, Aug 19, 2019 at 10:44 PM Xin Long wrote:
>
> On Sun, Aug 18, 2019 at 10:13 PM Dmitry Vyukov wrote:
> >
> > On Sun, Aug 18, 2019 at 7:07 AM Xin Long wrote:
> > >
> > > On Sat, Aug 17, 2019 at 2:38 AM syzbot
> > > wrote:
> > > >
> > > > Hello,
> > > >
> > > > syzbot found the following
Replace pclk/aclk/mclk fixed-clock clock provider with platform clockgen
pre-divider provider, those clocks should be driven by the CGA_PLL2/2.
More details please refer Reference Manual.
Signed-off-by: Wen He
---
arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi | 17 ++---
1 file
On Fri, Aug 23, 2019 at 12:15:11AM +0300, Vladimir Oltean wrote:
> The DSPI interrupt can be shared between two controllers at least on the
> LX2160A. In that case, the driver for one controller might misbehave and
> consume the other's interrupt. Fix this by actually checking if any of
> the bits
On Fri 2019-08-23 14:54:45, Sergey Senozhatsky wrote:
> On (08/21/19 07:46), John Ogness wrote:
> [..]
> > The labels are necessary for the technical documentation of the
> > barriers. And, after spending much time in this, I find them very
> > useful. But I agree that there needs to be a better
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo/Thomas,
>
> Please consider pulling,
>
> Best regards,
>
> - Arnaldo
>
> Test results at the end of this message, as usual.
>
> The following changes since commit 4e92b18e5b0b61211f4511cdbc5803300eeead40:
>
> Merge tag
Hi Mark,
On Fri, 23 Aug 2019 at 13:28, Mark Brown wrote:
>
> On Fri, Aug 23, 2019 at 12:15:11AM +0300, Vladimir Oltean wrote:
> > The DSPI interrupt can be shared between two controllers at least on the
> > LX2160A. In that case, the driver for one controller might misbehave and
> > consume the
From: Ondrej Jirman
Some supported devices need more time to come out of reset (eg.
BCM4345C5 in AP6256).
I don't have/found a datasheet, so the value was arrive at
experimentally with the Oprange Pi 3 board. Without increased delay,
I got intermittent failures during probe. This is a Bluetooth
From: Ondrej Jirman
(Resend to add missing lists, sorry for the noise.)
This series implements bluetooth support for Xunlong Orange Pi 3 board.
The board uses AP6256 WiFi/BT 5.0 chip.
Summary of changes:
- add more delay to let initialize the chip
- let the kernel detect firmware file path
-
On Tue, 20 Aug 2019 03:26:55 +0200,
Luis Chamberlain wrote:
>
> On Mon, Aug 19, 2019 at 09:19:51AM -0700, Scott Branden wrote:
> > To be honest, I find the entire firmware code sloppy.
>
> And that is after years of cleanup on my part. Try going back to v4.1
> for instance, check the code out
From: Ondrej Jirman
The board contains AP6256 WiFi/BT module that has its bluetooth part
connected to SoC's UART1 port. Enable this port, and add node for the
bluetooth device.
Bluetooth part is named bcm4345c5.
You'll need a BCM4345C5.hcd firmware file that can be found in the
Xulongs's
From: Ondrej Jirman
Detect BCM4345C5 and load a corresponding firmware file.
Signed-off-by: Ondrej Jirman
---
Checkpatch reports a spurious error.
drivers/bluetooth/btbcm.c | 3 +++
drivers/bluetooth/hci_bcm.c | 1 +
2 files changed, 4 insertions(+)
diff --git a/drivers/bluetooth/btbcm.c
From: Ondrej Jirman
This is present in the AP6526 WiFi/Bluetooth 5.0 module.
Signed-off-by: Ondrej Jirman
---
Documentation/devicetree/bindings/net/broadcom-bluetooth.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/net/broadcom-bluetooth.txt
From: Ondrej Jirman
Orange Pi 3 uses UART1 for bluetooth. Add pinconfigs so that we can use
them.
Signed-off-by: Ondrej Jirman
---
arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi
Commit d3c61619568c ("ARM: 8788/1: ftrace: remove old mcount support")
removed the old mcount support, but forget to remove these three
declarations. This patch removes them.
Signed-off-by: Jisheng Zhang
---
Changes since v1:
- remove mcount() declaration too
arch/arm/include/asm/ftrace.h |
Commit d3c61619568c ("ARM: 8788/1: ftrace: remove old mcount support")
removed the old mcount support, but forget to remove these three
declarations. This patch removes them.
Signed-off-by: Jisheng Zhang
---
Changes since v2:
- really remove mcount() declaration too. I made a mistake when
On 22/08/2019 17:24, Sean Christopherson wrote:
> On Thu, Aug 22, 2019 at 04:46:10PM +0100, Steven Price wrote:
>> On 22/08/2019 16:28, Sean Christopherson wrote:
>>> On Wed, Aug 21, 2019 at 04:36:50PM +0100, Steven Price wrote:
kvm_put_guest() is analogous to put_user() - it writes a single
On Fri, Aug 23, 2019 at 10:44:25AM +0100, Andrew Murray wrote:
> On Thu, Aug 22, 2019 at 05:48:15PM +0100, Lorenzo Pieralisi wrote:
> > On Tue, Aug 20, 2019 at 07:28:37AM +, Z.q. Hou wrote:
> > > From: Hou Zhiqiang
> > >
> > > On FSL Layerscape SoCs, the number of lanes assigned to PCIe
> >
Hi,
To everyone on the long Cc list...
What's happening with this? I was about to merge the patches for 32-bit
ARM, which I don't want to do if doing so will cause this regression on
32-bit ARM as well.
Thanks.
On Thu, Aug 22, 2019 at 07:57:59AM +0100, Chris Clayton wrote:
> Hi everyone,
>
>
On Fri, Aug 23, 2019 at 11:36:54AM +0100, Russell King - ARM Linux admin wrote:
> To everyone on the long Cc list...
>
> What's happening with this? I was about to merge the patches for 32-bit
> ARM, which I don't want to do if doing so will cause this regression on
> 32-bit ARM as well.
tglx
Hi Andrew,
On Thu, Aug 22, 2019 at 04:48:57PM -0700, Andrew Morton wrote:
> On Mon, 19 Aug 2019 17:14:49 +0100 Mark Rutland wrote:
>
> > In several places we need to be able to operate on pointers which have
> > gone via a roundtrip:
> >
> > virt -> {phys,page} -> virt
> >
> > With
Hi Russell,
On 8/23/19 11:36 AM, Russell King - ARM Linux admin wrote:
> Hi,
>
> To everyone on the long Cc list...
>
> What's happening with this? I was about to merge the patches for 32-bit
> ARM, which I don't want to do if doing so will cause this regression on
> 32-bit ARM as well.
>
On Tuesday, 20 August 2019 18:46:19 BST Ayan Halder wrote:
> The de-init routine should be doing the following in order:-
> 1. Unregister the drm device
> 2. Shut down the crtcs - failing to do this might cause a connector leakage
> See the 'commit 109c4d18e574 ("drm/arm/malidp: Ensure that the
Hi,
On 8/20/19 6:57 PM, Max Staudt wrote:
> Up until now, the pata_buddha driver would only check for cards on
> initcall time. Now, the kernel will call its probe function as soon
> as a compatible card is detected.
>
> v6: Only do the drvdata workaround for X-Surf (remove breaks otherwise)
>
On Thu, Aug 22, 2019 at 03:05:49PM -0500, Bjorn Helgaas wrote:
> From: Bjorn Helgaas
>
> An MMIO read from a PCI device that doesn't exist or doesn't respond causes
> a PCI error. There's no real data to return to satisfy the CPU read, so
> most hardware fabricates ~0 data.
>
> Add a
Hi,
We are seeing regression with our uncore perf driver(Marvell's
ThunderX2, ARM64 server platform) on 5.3-Rc1.
After bisecting, it turned out to be this patch causing the issue.
Test case:
Load module and run perf for more than 4 events( we have 4 counters,
event multiplexing takes place for
The patch
spi: spi-fsl-dspi: Exit the ISR with IRQ_NONE when it's not ours
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
On Fri, Jul 12, 2019 at 03:48:57PM +1200, Chris Packham wrote:
> From: Jan Luebbe
>
> The macro name is too generic, so add a AURORA_ prefix.
>
> Signed-off-by: Jan Luebbe
> Reviewed-by: Gregory CLEMENT
> Signed-off-by: Chris Packham
> ---
> arch/arm/include/asm/hardware/cache-aurora-l2.h |
On Thu 2019-08-22 19:38:01, Andrea Parri wrote:
> On Thu, Aug 22, 2019 at 03:50:52PM +0200, Petr Mladek wrote:
> > On Wed 2019-08-21 07:46:28, John Ogness wrote:
> > > On 2019-08-20, Sergey Senozhatsky
> > > wrote:
> > > > [..]
> > > >> > + *
> > > >> > + * Memory barrier involvement:
>
On 08/23/2019 12:42 PM, Bartlomiej Zolnierkiewicz wrote:
>> +static struct zorro_driver pata_buddha_driver = {
>> +.name = "pata_buddha",
>> +.id_table = pata_buddha_zorro_tbl,
>> +.probe = pata_buddha_probe,
>> +.remove = pata_buddha_remove,
>> +
Up until now, the pata_buddha driver would only check for cards on
initcall time. Now, the kernel will call its probe function as soon
as a compatible card is detected.
v7: Removed suppress_bind_attrs that slipped in
v6: Only do the drvdata workaround for X-Surf (remove breaks otherwise)
On Fri, Aug 23, 2019 at 11:46:21AM +0100, Russell King - ARM Linux admin wrote:
> On Fri, Jul 12, 2019 at 03:48:57PM +1200, Chris Packham wrote:
> > From: Jan Luebbe
> >
> > The macro name is too generic, so add a AURORA_ prefix.
> >
> > Signed-off-by: Jan Luebbe
> > Reviewed-by: Gregory
On Fri, Aug 23, 2019 at 01:30:27PM +0300, Vladimir Oltean wrote:
> On Fri, 23 Aug 2019 at 13:28, Mark Brown wrote:
> > It would be better to have done this as the first patch before
> > the restructuring, that way we could send this as a fix - the
> > refactoring while good doesn't really fit
On Fri, Aug 23, 2019 at 11:43:32AM +0100, Vincenzo Frascino wrote:
> Hi Russell,
>
> On 8/23/19 11:36 AM, Russell King - ARM Linux admin wrote:
> > Hi,
> >
> > To everyone on the long Cc list...
> >
> > What's happening with this? I was about to merge the patches for 32-bit
> > ARM, which I
On 8/11/19 6:11 PM, Dmitry Torokhov wrote:
> Let's switch the driver to using threaded IRQ so that we do not need to
> manage the interrupt and work separately, and we do not acknowledge
> interrupt until we finished handling it completely.
>
> Signed-off-by: Dmitry Torokhov
On ILI2117
On Fri, Aug 23, 2019 at 12:24:49AM +0300, Vladimir Oltean wrote:
> This patch is taken out of the "Poll mode for NXP DSPI driver" series
> and respun against the "for-4.20" branch.
> $(git describe --tags 13aed2392741) shows:
> v4.20-rc1-18-g13aed2392741
Please don't send cover letters for single
On Fri, Aug 23, 2019 at 11:50:44AM +0100, Mark Brown wrote:
> On Fri, Aug 23, 2019 at 01:30:27PM +0300, Vladimir Oltean wrote:
> > Did you see this?
> > https://lkml.org/lkml/2019/8/22/1542
> I'm not online enough to readily follow that link right now, I
> did apply another patch for a similar
The patch
spi: spi-fsl-dspi: Exit the ISR with IRQ_NONE when it's not ours
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.4
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
The patch
spi: spi-fsl-dspi: Remove impossible to reach error check
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.4
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
spi: spi-fsl-dspi: Use poll mode in case the platform IRQ is missing
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.4
All being well this means that it will be integrated into the linux-next
tree (usually sometime in
The patch
spi: spi-fsl-dspi: Reduce indentation level in dspi_interrupt
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.4
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
On Fri, Aug 23, 2019 at 1:23 PM Alexander Graf wrote:
>
> On 22.08.19 10:46, Anup Patel wrote:
> > From: Atish Patra
> >
> > The RISC-V hypervisor specification doesn't have any virtual timer
> > feature.
> >
> > Due to this, the guest VCPU timer will be programmed via SBI calls.
> > The host
On Tue, Aug 20, 2019 at 07:28:37AM +, Z.q. Hou wrote:
> From: Hou Zhiqiang
>
> On FSL Layerscape SoCs, the number of lanes assigned to PCIe
> controller is not fixed, it is determined by the selected
> SerDes protocol. The current num-lanes indicates the max lanes
> PCIe controller can
On 2019-08-22 14:20, Colin King wrote:
> From: Colin Ian King
>
> Currently the for-loop will spin forever if variable supported is
> non-zero because supported is never changed. Fix this by adding in
> the missing right shift of supported.
>
> Addresses-Coverity: ("Infinite loop")
> Fixes:
When building mtk_drm_drv.o the following build error is seen:
../drivers/gpu/drm/mediatek/mtk_drm_drv.c: In function ‘mtk_drm_kms_init’:
../drivers/gpu/drm/mediatek/mtk_drm_drv.c:291:8: error: implicit declaration of
function ‘dma_set_max_seg_size’; did you mean ‘drm_rect_adjust_size’?
On Fri, Aug 23, 2019 at 11:40:50AM +0100, Will Deacon wrote:
> On Fri, Aug 23, 2019 at 11:36:54AM +0100, Russell King - ARM Linux admin
> wrote:
> > To everyone on the long Cc list...
> >
> > What's happening with this? I was about to merge the patches for 32-bit
> > ARM, which I don't want to
On Fri, Aug 23, 2019 at 1:34 PM Alexander Graf wrote:
>
> On 22.08.19 10:46, Anup Patel wrote:
> > From: Atish Patra
> >
> > The KVM host kernel running in HS-mode needs to handle SBI calls coming
> > from guest kernel running in VS-mode.
> >
> > This patch adds SBI v0.1 support in KVM RISC-V.
On 8/23/19 12:49 PM, Max Staudt wrote:
> Up until now, the pata_buddha driver would only check for cards on
> initcall time. Now, the kernel will call its probe function as soon
> as a compatible card is detected.
>
> v7: Removed suppress_bind_attrs that slipped in
>
> v6: Only do the drvdata
On Thu, Aug 22, 2019 at 7:42 PM Alexander Graf wrote:
>
>
>
> On 22.08.19 16:00, Anup Patel wrote:
> > On Thu, Aug 22, 2019 at 5:31 PM Alexander Graf wrote:
> >>
> >> On 22.08.19 10:44, Anup Patel wrote:
> >>> For KVM RISC-V, we use KVM_GET_ONE_REG/KVM_SET_ONE_REG ioctls to access
> >>> VCPU
On Thu, Aug 22, 2019 at 7:39 PM Alexander Graf wrote:
>
>
>
> On 22.08.19 15:58, Anup Patel wrote:
> > On Thu, Aug 22, 2019 at 6:57 PM Alexander Graf wrote:
> >>
> >>
> >>
> >> On 22.08.19 14:38, Anup Patel wrote:
> >>> On Thu, Aug 22, 2019 at 5:58 PM Alexander Graf wrote:
>
> On
On Fri, Aug 23, 2019 at 09:52:30AM +0100, Colin King wrote:
> From: Colin Ian King
>
> The subtraction of the two pointers is automatically scaled by the
> size of the size of the object the pointers point to, so the division
> by sizeof(*i2400m->barker) is incorrect. Fix this by removing the
>
On Fri, Aug 23, 2019 at 1:39 PM Alexander Graf wrote:
>
> On 22.08.19 10:42, Anup Patel wrote:
> > This series adds initial KVM RISC-V support. Currently, we are able to boot
> > RISC-V 64bit Linux Guests with multiple VCPUs.
> >
> > Few key aspects of KVM RISC-V added by this series are:
> > 1.
On Thu, Aug 22, 2019 at 12:00:02AM +, Ghannam, Yazen wrote:
> From: Yazen Ghannam
>
> Future AMD systems will support "Asymmetric" Dual-Rank DIMMs. These are
> DIMMs where the ranks are of different sizes.
>
> The even rank will use the Primary Even Chip Select registers and the
> odd rank
On 23/08/2019 12:23, Dan Carpenter wrote:
> On Fri, Aug 23, 2019 at 09:52:30AM +0100, Colin King wrote:
>> From: Colin Ian King
>>
>> The subtraction of the two pointers is automatically scaled by the
>> size of the size of the object the pointers point to, so the division
>> by
Hi
I tested it and the bug is real - with some table sizes,
dm_table_find_target will access memory out of bounds if the sector
argument is beyond limit.
Your patch fixes some of these cases, but not all of them.
I used this script to test all possible table sizes:
#!/bin/bash -e
sync
dmsetup
On Wed, Aug 21, 2019 at 7:43 PM Dmitry Torokhov
wrote:
> The issue is this:
>
> static void bu21013_disable_chip(void *_ts)
> {
> struct bu21013_ts *ts = ts;
>
> which shuts up gcc about the fact that 'ts' is uninitialized, it should
> have said "ts = _ts". I guess it is a lesson for me
On 20/08/2019 10:49, Bibby Hsieh wrote:
> The interrupt mask and thread number has positive correlation,
> so we move the CMDQ_IRQ_MASK into cmdq driver data and calculate
> it by thread number.
>
> Signed-off-by: Bibby Hsieh
> Reviewed-by: CK Hu
Reviewed-by: Matthias Brugger
> ---
>
> Am 23.08.2019 um 13:05 schrieb Anup Patel :
>
>> On Fri, Aug 23, 2019 at 1:23 PM Alexander Graf wrote:
>>
>>> On 22.08.19 10:46, Anup Patel wrote:
>>> From: Atish Patra
>>>
>>> The RISC-V hypervisor specification doesn't have any virtual timer
>>> feature.
>>>
>>> Due to this, the guest
On 20/08/2019 10:49, Bibby Hsieh wrote:
> GCE hardware stored event information in own internal sysram,
> if the initial value in those sysram is not zero value
> it will cause a situation that gce can wait the event immediately
> after client ask gce to wait event but not really trigger the
>
On Thu, Aug 22, 2019 at 05:33:23PM -0400, Qian Cai wrote:
> https://raw.githubusercontent.com/cailca/linux-mm/master/arm64.config
>
> Booting an arm64 ThunderX2 server with page_alloc.shuffle=1 [1] +
> CONFIG_PROVE_LOCKING=y results in hanging.
Hmm, but the config you link to above has:
#
Add kernel doc annotation for HRTIMER_MODE_HARD.
This should have been part of commit
ae6683d815895 ("hrtimer: Introduce HARD expiry mode")
Signed-off-by: Sebastian Andrzej Siewior
---
include/linux/hrtimer.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/hrtimer.h
I compared my old queue vs tip/master and noticed two missing hunks.
Sebastian
The sched_timer should be initialized with the _HARD suffix. Most of
this already happened in commit
902a9f9c50905 ("tick: Mark tick related hrtimers to expiry in hard
interrupt context")
but this one instance has been missed.
Signed-off-by: Sebastian Andrzej Siewior
---
> Am 23.08.2019 um 13:18 schrieb Anup Patel :
>
>> On Fri, Aug 23, 2019 at 1:34 PM Alexander Graf wrote:
>>
>>> On 22.08.19 10:46, Anup Patel wrote:
>>> From: Atish Patra
>>>
>>> The KVM host kernel running in HS-mode needs to handle SBI calls coming
>>> from guest kernel running in
> Am 23.08.2019 um 13:21 schrieb Anup Patel :
>
>> On Thu, Aug 22, 2019 at 7:42 PM Alexander Graf wrote:
>>
>>
>>
>>> On 22.08.19 16:00, Anup Patel wrote:
On Thu, Aug 22, 2019 at 5:31 PM Alexander Graf wrote:
> On 22.08.19 10:44, Anup Patel wrote:
> For KVM RISC-V, we
On 23/08/2019 13:36, Matthias Brugger wrote:
>
>
> On 20/08/2019 10:49, Bibby Hsieh wrote:
>> GCE hardware stored event information in own internal sysram,
>> if the initial value in those sysram is not zero value
>> it will cause a situation that gce can wait the event immediately
>> after
> Am 23.08.2019 um 13:26 schrieb Anup Patel :
>
>> On Fri, Aug 23, 2019 at 1:39 PM Alexander Graf wrote:
>>
>>> On 22.08.19 10:42, Anup Patel wrote:
>>> This series adds initial KVM RISC-V support. Currently, we are able to boot
>>> RISC-V 64bit Linux Guests with multiple VCPUs.
>>>
>>> Few
On 2019/08/23 7:08, Linus Torvalds wrote:
>> syzbot found that a thread can stall for minutes inside read_mem()
>> after that thread was killed by SIGKILL [1]. Reading 2GB at one read()
>> is legal, but delaying termination of killed thread for minutes is bad.
>
> Side note: we might even just
On Fri, Aug 23, 2019 at 5:03 PM Graf (AWS), Alexander wrote:
>
>
>
> > Am 23.08.2019 um 13:05 schrieb Anup Patel :
> >
> >> On Fri, Aug 23, 2019 at 1:23 PM Alexander Graf wrote:
> >>
> >>> On 22.08.19 10:46, Anup Patel wrote:
> >>> From: Atish Patra
> >>>
> >>> The RISC-V hypervisor
On 23.08.19 13:46, Anup Patel wrote:
On Fri, Aug 23, 2019 at 5:03 PM Graf (AWS), Alexander wrote:
Am 23.08.2019 um 13:05 schrieb Anup Patel :
On Fri, Aug 23, 2019 at 1:23 PM Alexander Graf wrote:
On 22.08.19 10:46, Anup Patel wrote:
From: Atish Patra
The RISC-V hypervisor
Hi Steven,
On 2019/8/21 23:36, Steven Price wrote:
Enable paravirtualization features when running under a hypervisor
supporting the PV_TIME_ST hypercall.
For each (v)CPU, we ask the hypervisor for the location of a shared
page which the hypervisor will use to report stolen time to us. We set
On Fri, Aug 23, 2019 at 06:10:30PM +0800, Chen-Yu Tsai wrote:
> On Fri, Aug 23, 2019 at 6:08 PM Maxime Ripard wrote:
> >
> > Hi,
> >
> > On Fri, Aug 23, 2019 at 11:42:28AM +0200, meg...@megous.com wrote:
> > > From: Ondrej Jirman
> > >
> > > Orange Pi 3 has AP6256 WiFi/BT module. WiFi part of
Sean Christopherson writes:
> The VMware backdoor hooks #GP faults on IN{S}, OUT{S}, and RDPMC, none
> of which generate a non-zero error code for their #GP. Re-injecting #GP
> instead of attempting emulation on a non-zero error code will allow a
> future patch to move #GP injection (for
On Fri, 2019-08-23 at 12:37 +0100, Will Deacon wrote:
> On Thu, Aug 22, 2019 at 05:33:23PM -0400, Qian Cai wrote:
> > https://raw.githubusercontent.com/cailca/linux-mm/master/arm64.config
> >
> > Booting an arm64 ThunderX2 server with page_alloc.shuffle=1 [1] +
> > CONFIG_PROVE_LOCKING=y results
Add an arm64 specific helper which parks the cpu in a more architecture
efficient way.
Signed-off-by: Cristian Marussi
---
arch/arm64/kernel/smp.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/kernel/smp.c b/arch/arm64/kernel/smp.c
index c7497a885cfd..a3fb22b4c870 100644
There was a lot of code duplication across architectures regarding the
SMP stop procedures' logic; moreover some of this duplicated code logic
happened to be similarly faulty across a few architectures: while fixing
such logic, move such generic logic as much as possible inside common
code.
Once a stop request is in progress on one CPU, it must be carefully
evaluated what to do if another stop request is issued concurrently
on another CPU.
Given that panic and crash dump code flows are mutually exclusive,
the only alternative possible scenario which instead could lead to
concurrent
Hi all,
the logic underlying SMP stop and kexec crash procedures, beside containing
some arch-specific bits, is mostly generic and common across all archs:
despite this fact, such logic is now scattered across all architectures and
on some of them is flawed, in such a way that, under some
Make arm64 use the generic SMP-stop logic provided by common code
unified smp_send_stop() function.
arm64 smp_send_stop() logic had a bug in it: it failed to consider the
online status of the calling CPU when evaluating if any stop message
needed to be sent to other CPus at all: this resulted, on
Make arm64 use the SMP common implementation of crash_smp_send_stop() and
its generic logic, by removing the arm64 crash_smp_send_stop() definition
and providing the needed arch specific helpers.
Additionally, simplify the arch-specific stop and crash dump ISRs backends
(which are in charge of
601 - 700 of 850 matches
Mail list logo
