On Mon, Apr 16, 2018 at 09:44:51AM +0200, Daniel Lezcano wrote:
> On 16/04/2018 09:37, Viresh Kumar wrote:
> > On 13-04-18, 13:47, Daniel Lezcano wrote:
> >> Ok, noted. At the first glance, it should not be a problem.
> >
> > Why do you think it wouldn't be a problem ?
>
> Because we rely on the
The use of GPIO descriptors takes care of inversion flags declared in
the device tree. The conversion of the Atmel USBA UDC driver introduced
in 4.17-rc1 missed it, and as a result the inversion will not work.
In addition, cleanup the code to remove an include left behind after
the suppression of
When converting to GPIO descriptors, gpiod_get_value automatically
handles the line inversion flags from the device tree.
Do not invert the line twice.
Fixes: 3df034081021fa4b6967ce3364bc7d867ec1c870
Signed-off-by: Romain Izard
---
drivers/usb/gadget/udc/atmel_usba_udc.c | 3 +--
drivers/usb/g
The include defines the private platform_data structure used with AVR
platforms. It has no user since 7c55984e191f. Remove it.
Signed-off-by: Romain Izard
---
drivers/usb/gadget/udc/atmel_usba_udc.c | 1 -
include/linux/usb/atmel_usba_udc.h | 24
2 files changed, 2
Fix the fallout of the conversion to GPIO descriptors in 3df034081021.
Signed-off-by: Romain Izard
---
drivers/usb/gadget/udc/atmel_usba_udc.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/usb/gadget/udc/atmel_usba_udc.c
b/drivers/usb/gadget/udc/
On Mon, 16 Apr 2018 10:13:12 +0800
Dong Jia Shi wrote:
> * Cornelia Huck [2018-04-13 16:05:09 +0200]:
>
> > When we call ssch, an interrupt might already be pending once we
> > return from the START SUBCHANNEL instruction. Therefore we need to
> > make sure interrupts are disabled until after w
On Thu, 29 Mar 2018, Chen-Yu Tsai wrote:
> The axp20x driver has lots of mfd_cell and resource structs.
> These can all be const-ified.
>
> Signed-off-by: Chen-Yu Tsai
> ---
> drivers/mfd/axp20x.c | 44 ++--
> include/linux/mfd/axp20x.h | 2 +-
> 2
On Thu, 29 Mar 2018, Chen-Yu Tsai wrote:
> Previously we were open coding the interrupts for the various mfd
> cells. This made the code somewhat long due to pretty-formatting.
>
> This patch convert those into one-line declarations with DEFINE_RES_IRQ,
> making the code shorter and easier to rea
On Mon, Apr 16, 2018 at 06:17:48PM +0900, Minchan Kim wrote:
> Hi Ganesh,
>
> On Tue, Apr 10, 2018 at 04:52:58PM +0800, Ganesh Mahendran wrote:
>
> < snip >
> > >> basepatch_v1 patch_v5
> > >> ---
> > >>
On Thu, 29 Mar 2018, Chen-Yu Tsai wrote:
> When AXP806 support was added, POK was incorrectly expanded to PWROK.
> However, the datasheet lists them as POK[LSNP], which is the same as
> on the AXP288. Furthermore, the registers associated with POK functions
> are the same as the PEK on the other A
On Thu, 29 Mar 2018, Daniel Schultz wrote:
> When using Rockchip SoCs with rk805/808/818 PMICs, restarts are realized by
> setting the reset registers in the "Clock and Reset Unit".
>
> Now, the driver can trigger a restart in the PMIC. Like the
> shutdown function, the restart is bound to an ind
On Thu, 29 Mar 2018, Daniel Schultz wrote:
> Since all three shutdown functions have almost the same code, all logic
> from the shutdown functions can be refactored to a new function
> "rk808_update_bits", which can update a register by a given address and
> bitmask.
>
> Signed-off-by: Daniel Sch
On 16-04-18, 09:44, Daniel Lezcano wrote:
> Because we rely on the number to identify the cluster and flag it
> 'processed'. The number itself is not important.
It is, because you are creating multiple groups (like cpufreq
policies) right now based on cluster id. Which will be zero for all
the CPU
*Warning -- this requires the base RZ/N1 support patches already posted *
This is a tentative patch series for enabling the second CA7 of the RZ/N1D.
It's based on a spin_table method, and it reuses the same binding property
as that driver.
One question is: Do i have to document it separately, or
This enables starting the second CA7 core. Also handles the case the
bootloader has had to change the second CPU parking address to allow
booting in NONSEC/HYP.
Signed-off-by: Michel Pollet
---
arch/arm/mach-shmobile/Makefile | 1 +
arch/arm/mach-shmobile/r9a06g032.h | 7 +++
ar
The Renesas RZ/N1D second CA7 is parked in a ROM pen at boot time, it
requires a special enable method to get it started at boot time.
Signed-off-by: Michel Pollet
---
arch/arm/mach-shmobile/Makefile| 1 +
arch/arm/mach-shmobile/smp-r9a06g032.c | 87 ++
2
* Laura Abbott wrote:
> There's an ongoing effort to remove VLAs[1] from the kernel to eventually
> turn on -Wvla. The few VLAs in use have an upper bound based on a size
> of 64K. This doesn't produce an excessively large stack so just switch
> the upper bound.
>
> [1] https://lkml.org/lkml/20
Add a special enable method for second CA8 of the Renesas RZ/N1D
(R9A06G032).
Signed-off-by: Michel Pollet
---
Documentation/devicetree/bindings/arm/cpus.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/cpus.txt
b/Documentation/devicetree/bindings/ar
Add a special enable method for the second CA7 of the Renesas RZ/N1D
(R9A06G032), as well as the default value for the "cpu-release-addr"
property.
Signed-off-by: Michel Pollet
---
arch/arm/boot/dts/r9a06g032.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/r9a06g032.
On Mon, Apr 16, 2018 at 11:37:27AM +0200, Greg Kroah-Hartman wrote:
> On Mon, Apr 16, 2018 at 06:17:48PM +0900, Minchan Kim wrote:
> > Hi Ganesh,
> >
> > On Tue, Apr 10, 2018 at 04:52:58PM +0800, Ganesh Mahendran wrote:
> >
> > < snip >
> > > >> basepatch_v1 patch_
Hi Masami,
On 04/16/2018 02:57 PM, Masami Hiramatsu wrote:
> On Mon, 9 Apr 2018 16:36:33 +0530
> Ravi Bangoria wrote:
>
>> User can remove files from cache using --remove/--purge options
>> but both needs list of files as an argument. It's not convenient
>> when you want to flush out entire cach
On Thu, 12 Apr 2018, Kirill A. Shutemov wrote:
> > Commits 9b46a051e4 ("x86/mm: Initialize vmemmap_base at boot-time") and
> > a7412546d8 ("x86/mm: Adjust vmalloc base and size at boot-time") lost the
> > type information for __VMALLOC_BASE_L4, __VMALLOC_BASE_L5,
> > __VMEMMAP_BASE_L4 and __VME
From: Joerg Roedel
The |= operator will let us end up with an invalid PTE. Use
the correct &= instead.
Fixes: fb43d6cb91ef ('x86/mm: Do not auto-massage page protections')
Cc: Dave Hansen
Signed-off-by: Joerg Roedel
---
arch/x86/kernel/ldt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(
On 16 April 2018 at 17:15, Daniel Vetter wrote:
> On Thu, Apr 12, 2018 at 07:54:10AM +0200, Julia Lawall wrote:
>> From: Fengguang Wu
>>
>> Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference() and
>> drm_*_unreference() helpers.
>>
>> Generated by: scripts/coccinelle/api/drm-get
Please ignore this one... it's rebase junk 😊
Michel
>
> This enables starting the second CA7 core. Also handles the case the
> bootloader has had to change the second CPU parking address to allow
> booting in NONSEC/HYP.
>
> Signed-off-by: Michel Pollet
> ---
> arch/arm/mach-shmobile/Makefile
On 16/04/2018 11:37, Viresh Kumar wrote:
> On 16-04-18, 09:44, Daniel Lezcano wrote:
>> Because we rely on the number to identify the cluster and flag it
>> 'processed'. The number itself is not important.
>
> It is, because you are creating multiple groups (like cpufreq
> policies) right now base
On Fri, Apr 13, 2018 at 04:29:48PM +0100, Ayan Kumar Halder wrote:
> One needs to ensure that the crtcs are shutdown so that the
> drm_crtc_state->connector_mask reflects that no connectors
> are currently active. Further, it reduces the reference
> count for each connector. This ensures that the c
On Mon, Apr 16, 2018 at 09:43:02AM +, Jiri Kosina wrote:
> On Thu, 12 Apr 2018, Kirill A. Shutemov wrote:
>
> > > Commits 9b46a051e4 ("x86/mm: Initialize vmemmap_base at boot-time") and
> > > a7412546d8 ("x86/mm: Adjust vmalloc base and size at boot-time") lost the
> > > type information for
This patch is used to tell kernel that new VIA HDAC controller also
support no-snoop path.
Signed-off-by: David Wang
---
sound/pci/hda/hda_intel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
index 96143df..439e8e9 1006
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus
Late pull request, sorry. I just totally forgot about it, probably because fuse
updates are so rare these days (hoping to get back to regular fuse updates once
overlayfs is "finished").
This
On Wed, 11 Apr 2018, Robert Munteanu wrote:
> Changelog:
>
> - v2: modifier keys work, some combinations are still troublesome
> - v3: style cleanup, rebase on top of 4.14
> - v4: remove most debugging calls, make init info useful for user,
> rebased on top of 4.15
> - v5: fix the HID descripto
On 16-04-18, 11:45, Daniel Lezcano wrote:
> Can you elaborate a bit ? I'm not sure to get the point.
Sure. With your current code on Hikey960 (big/LITTLE), you end up
creating two cooling devices, one for the big cluster and one for
small cluster. Which is the right thing to do, as we also have tw
On 28/03/18 10:00, Lee Jones wrote:
On Tue, 13 Mar 2018, Richard Fitzgerald wrote:
This adds the generic core support for Cirrus Logic "Madera" class codecs.
These are complex audio codec SoCs with a variety of digital and analogue
I/O, onboard audio processing and DSPs, and other features.
Th
On 05.04.2018 11:49, Enric Balletbo i Serra wrote:
> From: Tomasz Figa
>
> Currently PSR flush is triggered from CRTC's .atomic_begin() callback,
> which is executed after modeset disables and enables and before plane
> updates are committed. Since PSR flush and re-enable can be triggered
> asynch
When run the following test case,
/*
* This expects the new RTC class driver framework, working with
* clocks that will often not be clones of what the PC-AT had.
* Use the command line to specify another RTC if you need one.
*/
static const char default_rtc[] = "/dev/rtc0";
int main(int argc,
On 05.04.2018 11:50, Enric Balletbo i Serra wrote:
> From: Tomasz Figa
>
> It is not used anymore after last changes and it was not even correct to
> begin with as it assumed a 1:1 relation between a CRTC and encoder,
> while in fact a CRTC can be attached to multiple encoders.
>
> Signed-off-by:
On Mon, Apr 16, 2018 at 11:49 AM, Jiri Kosina wrote:
> On Wed, 11 Apr 2018, Robert Munteanu wrote:
>
>> Changelog:
>>
>> - v2: modifier keys work, some combinations are still troublesome
>> - v3: style cleanup, rebase on top of 4.14
>> - v4: remove most debugging calls, make init info useful for u
On 05.04.2018 11:49, Enric Balletbo i Serra wrote:
> From: Tomasz Figa
>
> It looks like the driver subsystem detaches devices from power domains
> at shutdown without consent of the drivers.
It looks bit strange. Could you elaborate more on it. Could you show the
code performing the detach?
Re
Hi Greg,
This release has build failure on file tools/perf/tests/code-reading.c:
tests/code-reading.c: In function ‘read_object_code’:
tests/code-reading.c:186:19: error: ‘KMOD_DECOMP_LEN’ undeclared
(first use in this function)
char decomp_name[KMOD_DECOMP_LEN];
^
Thanks,
Le
On Mon, 2018-04-09 at 22:37 +0800, Yixun Lan wrote:
> Add dt-bindings headers for the Meson-AXG's AO clock and
> reset controller.
>
> Reviewed-by: Rob Herring
> Signed-off-by: Yixun Lan
> ---
> include/dt-bindings/clock/axg-aoclkc.h | 26 ++
> include/dt-bindings/reset/
Hi Robert,
On Wed, Apr 11, 2018 at 11:49 AM, Robert Munteanu wrote:
> Changelog:
>
> - v2: modifier keys work, some combinations are still troublesome
> - v3: style cleanup, rebase on top of 4.14
> - v4: remove most debugging calls, make init info useful for user,
> rebased on top of 4.15
> - v
Hi,
On 16-04-18 10:40, Tobias Regnery wrote:
With CONFIG_AXP288=y and CONFIG_USB_COMMON=n there is the following link
error:
drivers/extcon/extcon-axp288.o: In function `axp288_put_role_sw':
extcon-axp288.c:(.text+0xa0): undefined reference to `usb_role_switch_put'
drivers/extcon/extcon-axp288.
On Mon, Apr 16, 2018 at 11:37:27AM +0200, Greg Kroah-Hartman wrote:
> On Mon, Apr 16, 2018 at 06:17:48PM +0900, Minchan Kim wrote:
> > Hi Ganesh,
> >
> > On Tue, Apr 10, 2018 at 04:52:58PM +0800, Ganesh Mahendran wrote:
> >
> > < snip >
> > > >> basepatch_v1 patch_
On 16/04/2018 11:50, Viresh Kumar wrote:
> On 16-04-18, 11:45, Daniel Lezcano wrote:
>> Can you elaborate a bit ? I'm not sure to get the point.
>
> Sure. With your current code on Hikey960 (big/LITTLE), you end up
> creating two cooling devices, one for the big cluster and one for
> small cluster
Hi Todor,
On Mon, Apr 16, 2018 at 11:48:59AM +0300, Todor Tomov wrote:
> Hi Mani,
>
> Thank you for the patch.
>
> On 14.04.2018 06:18, Manivannan Sadhasivam wrote:
> > Add gpio-line-names property for Dragonboard820c based on APQ8096 SoC.
> > There are 4 gpio-controllers present on this board,
On Fri 13-04-18 18:17:36, Jann Horn wrote:
> On Fri, Apr 13, 2018 at 6:05 PM, Jann Horn wrote:
> > On Fri, Apr 13, 2018 at 6:04 PM, Michal Hocko wrote:
> >> On Fri 13-04-18 17:04:09, Jann Horn wrote:
> >>> On Fri, Apr 13, 2018 at 8:49 AM, Michal Hocko wrote:
> >>> > On Fri 13-04-18 08:43:27, Mic
Hi Jerome,
On Mon, 2018-04-16 at 11:59 +0200, Jerome Brunet wrote:
> On Mon, 2018-04-09 at 22:37 +0800, Yixun Lan wrote:
> > Add dt-bindings headers for the Meson-AXG's AO clock and
> > reset controller.
> >
> > Reviewed-by: Rob Herring
> > Signed-off-by: Yixun Lan
> > ---
> > include/dt-bindi
On 16-04-18, 12:03, Daniel Lezcano wrote:
> On 16/04/2018 11:50, Viresh Kumar wrote:
> > On 16-04-18, 11:45, Daniel Lezcano wrote:
> >> Can you elaborate a bit ? I'm not sure to get the point.
> >
> > Sure. With your current code on Hikey960 (big/LITTLE), you end up
> > creating two cooling device
On Mon, Apr 16, 2018 at 05:58:26PM +0800, Lei Chen wrote:
> Hi Greg,
> This release has build failure on file tools/perf/tests/code-reading.c:
>
> tests/code-reading.c: In function ‘read_object_code’:
> tests/code-reading.c:186:19: error: ‘KMOD_DECOMP_LEN’ undeclared
> (first use in this function)
Hi Eduardo,
Per your request (https://marc.info/?l=linux-pm&m=152378232213070&w=2)
this patchset contains pending Exynos thermal driver fixes and cleanups.
It is based on:
- "[PATCH v3] thermal: exynos: Reading temperature makes sense only
when TMU is turned on" from Marek Szyprowski
(https:/
From: Marek Szyprowski
tmu_read() in case of Exynos4210 might return error for out of bound
values. Current code ignores such value, what leads to reporting critical
temperature value. Add proper error code propagation to exynos_get_temp()
function.
Signed-off-by: Marek Szyprowski
CC: sta...@vg
From: Marek Szyprowski
When thermal sensor is not yet enabled, reading temperature might return
random value. This might even result in stopping system booting when such
temperature is higher than the critical value. Fix this by checking if TMU
has been actually enabled before reading the tempera
Remove unused "type" field from struct exynos_tmu_platform_data.
There should be no functional changes caused by this patch.
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/thermal/samsung/exynos_tmu.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/thermal/samsung/exynos_tmu.
Since pdata efuse values are SoC (not platform) specific just move
them from platform data to struct exynos_tmu_data instance. Then
remove parsing of samsung,tmu[_,min_,max]_efuse_value properties.
There should be no functional changes caused by this patch.
Signed-off-by: Bartlomiej Zolnierkiewic
Remove no longer needed samsung thermal properties.
There should be no functional changes caused by this patch.
Signed-off-by: Bartlomiej Zolnierkiewicz
---
.../dts/exynos/exynos5433-tmu-g3d-sensor-conf.dtsi | 20
.../boot/dts/exynos/exynos5433-tmu-sensor-conf.dtsi | 19 --
All SoCs use the same values (25, 85) for trim points (except
Exynos5440 which currently specifices value 70 for the second trim
point -> it seems to be a mistake because documentation uses value
85 and two points based trimming has never been used by the driver
for this SoC anyway) so just make it
Remove no longer needed samsung thermal properties.
There should be no functional changes caused by this patch.
Signed-off-by: Bartlomiej Zolnierkiewicz
---
arch/arm/boot/dts/exynos3250.dtsi | 2 +-
arch/arm/boot/dts/exynos4.dtsi| 2 +-
arch/arm/boot/dts/ex
exynos_tmu.h is used only by exynos_tmu.c so there is no need
for a separate include file.
There should be no functional changes caused by this patch.
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/thermal/samsung/exynos_tmu.c | 18 +++-
drivers/thermal/samsung/exynos_tmu.h |
Since pdata gain values are SoC (not platform) specific just move
it from platform data to struct exynos_tmu_data instance. Then
remove parsing of samsung,tmu_gain property.
There should be no functional changes caused by this patch.
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/thermal/
Hi Benjamin and Jiri,
On Mon, 2018-04-16 at 12:02 +0200, Benjamin Tissoires wrote:
> Hi Robert,
>
> On Wed, Apr 11, 2018 at 11:49 AM, Robert Munteanu > wrote:
> > Changelog:
> >
> > - v2: modifier keys work, some combinations are still troublesome
> > - v3: style cleanup, rebase on top of 4.14
On 04/16/2018 12:32 PM, Daniel Vetter wrote:
On Mon, Apr 16, 2018 at 10:22 AM, Oleksandr Andrushchenko
wrote:
On 04/16/2018 10:43 AM, Daniel Vetter wrote:
On Mon, Apr 16, 2018 at 10:16:31AM +0300, Oleksandr Andrushchenko wrote:
On 04/13/2018 06:37 PM, Daniel Vetter wrote:
On Wed, Apr 11, 201
Since pdata reference_voltage values are SoC (not platform) specific
just move it from platform data to struct exynos_tmu_data instance.
Then remove parsing of samsung,tmu_reference_voltage property.
There should be no functional changes caused by this patch.
Signed-off-by: Bartlomiej Zolnierkiew
Since calibration type for temperature is SoC (not platform) specific
just move it from platform data to struct exynos_tmu_data instance.
Then remove parsing of samsung,tmu_cal_type property. Also remove no
longer needed platform data structure.
There should be no functional changes caused by this
All SoCs use the same value (4) for the noise cancel mode so just
make it explicit and remove parsing of samsung,tmu_noise_cancel_mode
property.
There should be no functional changes caused by this patch.
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/thermal/samsung/exynos_tmu.c | 10 +++
Trimming (one point based or two points based) is always used for
the temperature calibration and the default non-trimming code is
never reached. Remove it and then remove no longer needed parsing
of samsung,tmu_default_temp_offset property.
There should be no functional changes caused by this pat
From: Maciej Purski
Device context's field data->soc is currently obtained by comparing
of_compatible's. Provide soc_type as .data field in device's match
table, as it is done in most drivers.
Signed-off-by: Maciej Purski
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/thermal/samsung/ex
This patch is just wrong, sorry. I was trying to fix a static checker
warning and misread the code. The reference taken in macsec_newlink()
is released in macsec_free_netdev() when the netdevice is destroyed.
This reverts commit 5dcd8400884cc4a043a6d4617e042489e5d566a9.
Reported-by: Laura Abbot
Allocate line bitmaps outside of the line lock on line preparation.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-core.c | 96 +---
1 file changed, 55 insertions(+), 41 deletions(-)
diff --git a/drivers/lightnvm/pblk-core.c b/drivers/lightnvm/p
In the read path, pblk gets a reference to the incoming bio and puts it
after ending the bio. Though this behavior is correct, it is unnecessary
since pblk is the one putting the bio, therefore, it cannot disappear
underneath it.
Removing this reference, allows to clean up rqd->bio and avoid point
On 13/04/18 14:21, Peter Maydell wrote:
On 27 March 2018 at 14:15, Suzuki K Poulose wrote:
Expose the maximum physical address size supported by the host
for a VM. This could be later used by the userspace to choose the
appropriate size for a given VM. The limit is determined as the
minimum of
Bad blocks can grow at runtime. Check that the number of valid blocks in
a line are within the sanity threshold before allocating the line for
new writes.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-core.c | 38 --
drivers/lightnvm/pblk-init.c | 1
On 13/04/18 17:27, Punit Agrawal wrote:
Hi Suzuki,
I haven't had a chance to look at the code but noticed one issue below.
Suzuki K Poulose writes:
Now that we can manage the stage2 page table per VM, switch the
configuration details to per VM instance. We keep track of the
IPA bits, number
Remove unnecessary indirection on the read path.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-read.c | 12 +---
1 file changed, 1 insertion(+), 11 deletions(-)
diff --git a/drivers/lightnvm/pblk-read.c b/drivers/lightnvm/pblk-read.c
index 89aed634333a..2f8224354c62 100644
--
Return a meaningful error when the sanity vector I/O check fails.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-core.c | 22 --
1 file changed, 8 insertions(+), 14 deletions(-)
diff --git a/drivers/lightnvm/pblk-core.c b/drivers/lightnvm/pblk-core.c
index 128101f9
Remove dead function for manual sync. I/O
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-core.c | 7 ---
drivers/lightnvm/pblk.h | 1 -
2 files changed, 8 deletions(-)
diff --git a/drivers/lightnvm/pblk-core.c b/drivers/lightnvm/pblk-core.c
index cc34d5d9652d..5f960a6609c8 10
If the namespace is unregistered before the LightNVM target is removed
(e.g., on hot unplug) it is too late for the target to store any metadata
on the device - any attempt to write to the device will fail. In this
case, pass on a "gracefull teardown" flag to the target to let it know
when this hap
Remove unnecessary argument on pblk_line_free()
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-core.c | 6 +++---
drivers/lightnvm/pblk-init.c | 2 +-
drivers/lightnvm/pblk.h | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/lightnvm/pblk-core.c b/driv
When cleaning up buffer entries as we wrap up, their state should be
"completed". If any of the entries is in "submitted" state, it means
that something bad has happened. Trigger a warning immediately instead of
waiting for the state flag to eventually be updated, thus hiding the
issue.
Signed-off
Do the check for the chunk state after making sure that the chunk type
is supported.
Fixes: 32ef9412c114 ("lightnvm: pblk: implement get log report chunk")
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-init.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/dr
In the event of a mismatch between the read LBA and the metadata pointer
reported by the device, improve the error message to be able to detect
the offending physical address (PPA) mapped to the corrupted LBA.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-read.c | 42 +
Check that the lba stored in the LBA metadata is correct in the GC path
too. This requires a new helper function to check random reads in the
vector read.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-read.c | 39 +--
1 file changed, 33 insertions(+
A bunch of small fixes and extra checks for pblk. Non is critical, though
("lightnvm: pblk: check for chunk size before allocating it") might be nice to
get into 4.17 as it is a fix for the 2.0 pblk patches.
Javier
Javier González (11):
lightnvm: pblk: fail gracefully on line alloc. failure
l
In the event of a line failing to allocate, fail gracefully and stop the
pipeline to avoid more write failing in the same place.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-init.c | 5 +
drivers/lightnvm/pblk-map.c | 33 -
2 files changed, 29 in
On Thursday 12 April 2018 10:14 PM, santosh.shilim...@oracle.com wrote:
> On 4/11/18 9:53 PM, Keerthy wrote:
>> From: Dave Gerlach
>>
>> After an RTC+DDR cycle we lose sram context so emif pm functions present
>> in sram are lost. We can check if the first byte of the original
>> code in DDR con
On Mon, Apr 16, 2018 at 03:10:40PM +0530, Ravi Bangoria wrote:
> Hi Masami,
>
> On 04/16/2018 02:57 PM, Masami Hiramatsu wrote:
> > On Mon, 9 Apr 2018 16:36:33 +0530
> > Ravi Bangoria wrote:
> >
> >> User can remove files from cache using --remove/--purge options
> >> but both needs list of file
Hi Linus,
Enjoy!
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git
tags/mfd-next-4.17
for you to fetch changes up
On Mon, 2018-04-09 at 22:37 +0800, Yixun Lan wrote:
> We try to refactor the common code into one dedicated file,
> while preparing to add new Meson-AXG aoclk driver, this would
> help us to better share the code by all aoclk drivers.
>
> Suggested-by: Jerome Brunet
> Signed-off-by: Yixun Lan
>
Hi Linus,
Enjoy!
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git mfd-next-4.17-1
for you to fetch changes up to b45bf45
Enlightened MSR-Bitmap is a natural extension of Enlightened VMCS:
Hyper-V Top Level Functional Specification states:
"The L1 hypervisor may collaborate with the L0 hypervisor to make MSR
accesses more efficient. It can enable enlightened MSR bitmaps by setting
the corresponding field in the enlig
On 16/04/18 09:50, Christoph Hellwig wrote:
We can rely on the dma-mapping code to handle any DMA limits that is
bigger than the ISA DMA mask for us (either using an iommu or swiotlb),
so remove setting the block layer bounce limit for anything but bouncing
for highmem pages.
Signed-off-by: Chri
On 15/04/2018 23:22, Tony Krowiak wrote:
The VFIO AP device model exploits interpretive execution of AP
instructions (APIE) to provide guests passthrough access to AP
devices. This patch introduces a new interface to enable and
disable APIE.
Signed-off-by: Tony Krowiak
---
arch/s390/include/a
Can this be related to
commit ef0010a30935de4e0211cbc7bdffc30446cdee9b
vsprintf: don't use 'restricted_pointer()' when not restricting
and related commits?
To me it looks like %pk is always printing the hash, but never the real pointer
-
no matter what kernel.kptr_restrict says.
On 04/1
vunmap does page table clear operations twice in the
case when DEBUG_PAGEALLOC_ENABLE_DEFAULT is enabled.
So, clean up the code as that is unintended.
As a perf gain, we save few us. Below ftrace data was
obtained while doing 1 MB of vmalloc/vfree on ARM64
based SoC *without* this patch applied.
The test checks the behavior of setting MSR_IA32_TSC in a nested guest,
and the TSC_OFFSET VMCS field in general. It also introduces the testing
infrastructure for Intel nested virtualization.
Signed-off-by: Paolo Bonzini
---
tools/testing/selftests/kvm/Makefile | 3 +-
tools/tes
On 14/04/2018 05:10, KarimAllah Ahmed wrote:
> Update 'tsc_offset' on vmentry/vmexit of L2 guests to ensure that it always
> captures the TSC_OFFSET of the running guest whether it is the L1 or L2
> guest.
>
> Cc: Jim Mattson
> Cc: Paolo Bonzini
> Cc: Radim Krčmář
> Cc: k...@vger.kernel.org
> C
any suggestions？
On 2018/4/10 上午10:59, zou...@linux.alibaba.com wrote:
From: zoucao
Normally every BIOS reserved memory is used for some features, we can't
use them, but in some conditions, users can ensure some BIOS memories
are not used and reserved memory is well to free, they have not a g
Greg and Jiri, are you OK with this patch?
Alan Cox wrote:
> > syzbot is reporting crashes [1] triggered by memory allocation failure at
> > tty_ldisc_get() from tty_ldisc_restore(). While syzbot stops at WARN_ON()
> > due to panic_on_warn == true, panic_on_warn == false will after all trigger
> >
Implement HvFlushVirtualAddress{List,Space}Ex hypercalls in a simplistic
way: do full TLB flush with KVM_REQ_TLB_FLUSH and kick vCPUs which are
currently IN_GUEST_MODE.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/kvm/hyperv.c | 116 ++
arch/x86/kv
We need a new capability to indicate support for the newly added
HvFlushVirtualAddress{List,Space}{,Ex} hypercalls. Upon seeing this
capability, userspace is supposed to announce PV TLB flush features
by setting the appropriate CPUID bits (if needed).
Signed-off-by: Vitaly Kuznetsov
---
Document
Prepare to support TLB flush hypercalls, some of which are REP hypercalls.
Also, return HV_STATUS_INVALID_HYPERCALL_INPUT as it seems more
appropriate.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/kvm/hyperv.c | 21 -
1 file changed, 12 insertions(+), 9 deletions(-)
diff --g
101 - 200 of 1099 matches
Mail list logo
