mdev_remove_sysfs_files() should follow exact mirror sequence of a
create, similar to what is followed in error unwinding path of
mdev_create_sysfs_files().
Fixes: 6a62c1dfb5c7 ("vfio/mdev: Re-order sysfs attribute creation")
Reviewed-by: Cornelia Huck
Reviewed-by: Maxim Levitsky
Signed-off-by:
The media device is already available via multiple methods, there is no
need to set driver data for v4l2_dev to the media device.
In imx_media_link_notify(), get media device from link->graph_obj.mdev.
In imx_media_capture_device_register(), get media device from
v4l2_dev->mdev.
Signed-off-by:
If device is removal is initiated by two threads as below, mdev core
attempts to create a syfs remove file on stale device.
During this flow, below [1] call trace is observed.
cpu-0cpu-1
--
In following sequences, child devices created while removing mdev parent
device can be left out, or it may lead to race of removing half
initialized child mdev devices.
issue-1:
cpu-0 cpu-1
- -
This patch addresses below two issues and prepares the code to address
3rd issue listed below.
1. mdev device is placed on the mdev bus before it is created in the
vendor driver. Once a device is placed on the mdev bus without creating
its supporting underlying vendor device, mdev driver's
There is no need use 'extern' for exported functions.
Acked-by: Cornelia Huck
Reviewed-by: Maxim Levitsky
Signed-off-by: Parav Pandit
---
include/linux/mdev.h | 21 ++---
1 file changed, 10 insertions(+), 11 deletions(-)
diff --git a/include/linux/mdev.h
As we would like to use mdev subsystem for wider use case as
discussed in [1], [2] apart from an offline discussion.
This use case is also discussed with wider forum in [4] in track
'Lightweight NIC HW functions for container offload use cases'.
This series is prep-work and improves vfio/mdev
On Sun, Apr 21, 2019 at 07:09:30PM +, Han Nandor wrote:
> Add the device tree bindings document for the NVMEM based reboot-mode
> driver.
>
> Signed-off-by: Nandor Han
> ---
> .../power/reset/nvmem-reboot-mode.txt | 32 +++
> 1 file changed, 32 insertions(+)
>
On Tue, Apr 30, 2019 at 12:44:55PM +0200, Miroslav Benes wrote:
> On Tue, 30 Apr 2019, Greg Kroah-Hartman wrote:
>
> > On Tue, Apr 30, 2019 at 10:15:33AM +1000, Tobin C. Harding wrote:
> > > Currently error return from kobject_init_and_add() is not followed by a
> > > call to kobject_put(). This
Similar to commits c68b0274fb3cf ("ARM: reduce "Booted secondary
processor" message to debug level") and 035e787543de7 ("ARM: 8644/1: Reduce
"CPU:
shutdown" message to debug level"), demote the secondary_start_kernel()
and __cpu_die() messages from info, respectively notice to debug. While
we are
On Tue, Apr 30, 2019 at 10:28:15AM +1000, Tobin C. Harding wrote:
[snip]
Please do not consider this series for merge. There is a bit of
confusion here.
There are a few of theses patches live on various LKML lists. Have to
consolidate all the knowledge. When I _actually_ know how to use
On Fri, Apr 19, 2019 at 03:48:07PM +0200, Lukasz Luba wrote:
> Extend the documenation by events description with new 'event-data-type'
> field. Add example how the event might be defined in DT.
Why do we need event types in DT? We don't do this for other h/w such as
ARM PMU.
>
>
On Fri, 19 Apr 2019 15:48:05 +0200, Lukasz Luba wrote:
> This patch add support of a new feature which can be used in DT:
> Performance Monitoring Unit with defined event data type.
> In this patch the event data types are defined for Exynos PPMU.
> The patch also updates the MAINTAINERS file
On 4/30/19 5:37 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.0.11 release.
There are 89 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
On Tue, Apr 30, 2019 at 09:15:42AM -0700, Guenter Roeck wrote:
> On Mon, Apr 29, 2019 at 11:45:57PM -0700, Andrey Smirnov wrote:
> > Add bindings for Microchip UCS1002 Programmable USB Port Power
> > Controller with Charger Emulation.
> >
> > Signed-off-by: Andrey Smirnov
> > Cc: Enric Balletbo
On 4/30/19 5:37 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.38 release.
There are 100 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
On 4/30/19 5:38 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.115 release.
There are 53 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
On Mon, Apr 29, 2019 at 7:10 PM Nathan Chancellor
wrote:
>
> When building with -Wsometimes-uninitialized, Clang warns:
>
> drivers/md/dm-dust.c:216:11: warning: variable 'ret' is used
> uninitialized whenever 'if' condition is false
> [-Wsometimes-uninitialized]
> else if
On Tue, 2019-04-30 at 22:18 +0200, Alexandre Belloni wrote:
> The RTC core already ensures the alarm is set to a time in the future, it
> is not necessary to check again in the driver.
My reading of the rtc core code is that it checks if the alarm is in
the future *twice* before handing off the
On 4/30/19 5:38 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.172 release.
There are 41 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
Bjorn,
Bjorn Helgaas wrote on 4/28/19 7:52 PM:
On Sun, Apr 28, 2019 at 07:02:58PM -0500, Bjorn Helgaas wrote:
On Sat, Apr 27, 2019 at 02:13:01PM -0500, f...@fredlawl.com wrote:
From: Frederick Lawler
Replace remaining instances of dev_*() printk wrappers with pci_*()
printk wrappers. No
stable-rc/linux-4.9.y boot: 99 boots: 0 failed, 96 passed with 3 offline
(v4.9.171-42-ga707069e56d0)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.171-42-ga707069e56d0/
Full Build Summary:
On Tue, 30 Apr 2019 15:42:26 +0530, Lokesh Vutla wrote:
> Add the DT binding documentation for Interrupt Aggregator driver.
>
> Signed-off-by: Lokesh Vutla
> ---
> Changes since v7:
> - None
> .../interrupt-controller/ti,sci-inta.txt | 66 +++
> MAINTAINERS
On Tue, 30 Apr 2019 15:42:24 +0530, Lokesh Vutla wrote:
> Add the DT binding documentation for Interrupt router driver.
>
> Signed-off-by: Lokesh Vutla
> ---
> Changes since v7:
> - Changes interrupt cells to 2.
>
> .../interrupt-controller/ti,sci-intr.txt | 82 +++
>
Andy,
Andy Shevchenko wrote on 4/28/19 10:43 AM:
On Sat, Apr 27, 2019 at 02:13:01PM -0500, f...@fredlawl.com wrote:
From: Frederick Lawler
Replace remaining instances of dev_*() printk wrappers with pci_*()
printk wrappers. No functional change intended.
-
On a s390 z14 LAR with 2 cpus about stalls about 3% of the time while
loading the s390_trng.ko module.
Add a reschedule point to the loop that waits for modules to complete
loading.
v3: cleanup Fixes line.
Reported-by: Heiko Carstens
Fixes: f9a75c1d717f ("modules: Only return -EEXIST for
On 4/30/19 6:18 PM, Prarit Bhargava wrote:
> On a s390 z14 LAR with 2 cpus about stalls about 3% of the time while
> loading the s390_trng.ko module.
>
> Add a reschedule point to the loop that waits for modules to complete
> loading.
>
Sorry, sent in error.
P.
> v2: cleanup Fixes line.
>
On a s390 z14 LAR with 2 cpus about stalls about 3% of the time while
loading the s390_trng.ko module.
Add a reschedule point to the loop that waits for modules to complete
loading.
v2: cleanup Fixes line.
Reported-by: Heiko Carstens
Fixes: commit f9a75c1d717f ("modules: Only return -EEXIST
On 4/30/19 6:10 PM, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 7e470ea99bcd ("kernel/module: Reschedule while waiting for modules to
> finish loading")
>
> Fixes tag
>
> Fixes: linux-next commit f9a75c1d717f ("modules: Only return -EEXIST for
> modules that have finished
Hi all,
In commit
7e470ea99bcd ("kernel/module: Reschedule while waiting for modules to finish
loading")
Fixes tag
Fixes: linux-next commit f9a75c1d717f ("modules: Only return -EEXIST for
modules that have finished loading")
has these problem(s):
- the "linux-next commit" is
On Tue 2019-04-30 17:07:32, Dan Murphy wrote:
>
>
> On 4/30/19 5:05 PM, Pavel Machek wrote:
> > On Tue 2019-04-30 14:17:28, Dan Murphy wrote:
> >> The LM3697 is a single function LED driver. The single function LED
> >> driver needs to reside in the LED directory as a dedicated LED driver
> >>
On 4/30/19 5:05 PM, Pavel Machek wrote:
> On Tue 2019-04-30 14:17:28, Dan Murphy wrote:
>> The LM3697 is a single function LED driver. The single function LED
>> driver needs to reside in the LED directory as a dedicated LED driver
>> and not as a MFD device. The device does have common
Hi Lee,
This patch set has dependency on the previous one for lm3532, which
also touches ti-lmu.txt bindings, and for which I already created
immutable branch. Now if I created another immutable branch for
this patch set we would have to resolve conflicts between the two,
as they would both be
Hi all,
Commit
60ae11086c04 ("unicode: update unicode database unicode version 12.1.0")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpMVRMkvURMn.pgp
Description: OpenPGP digital signature
On Tue 2019-04-30 14:17:28, Dan Murphy wrote:
> The LM3697 is a single function LED driver. The single function LED
> driver needs to reside in the LED directory as a dedicated LED driver
> and not as a MFD device. The device does have common brightness and ramp
> features and those can be
On Tue 2019-04-30 14:17:25, Dan Murphy wrote:
> Document the ramp-up and ramp-down property in the binding.
> Removing the "sec" from the property definition as seconds is
> implied.
>
> Reviewed-by: Rob Herring
> Signed-off-by: Dan Murphy
> ---
>
> v3 - No changes added Reviewed-by Rob -
>
Hi all,
In commit
76d58e0f07ec ("KVM: fix KVM_CLEAR_DIRTY_LOG for memory slots of unaligned
size")
Fixes tag
Fixes: 98938aa8edd6 ("KVM: validate userspace input in
kvm_clear_dirty_log_protect()", 2019-01-02)
has these problem(s):
- The trailing date ine the fixes tag is unexpected
On Tue, Apr 30, 2019 at 2:47 PM Sami Tolvanen wrote:
>
> Casting mapping->a_ops->readpage to filler_t causes an indirect call
> type mismatch with Control-Flow Integrity checking. This change fixes
> the mismatch in read_cache_page_gfp and read_mapping_page by adding a
> stub callback function
From: "Steven Rostedt (VMware)"
Nicolai Stange discovered[1] that if live kernel patching is enabled, and the
function tracer started tracing the same function that was patched, the
conversion of the fentry call site during the translation of going from
calling the live kernel patch trampoline
Casting mapping->a_ops->readpage to filler_t causes an indirect call
type mismatch with Control-Flow Integrity checking. This change fixes
the mismatch in read_cache_page_gfp and read_mapping_page by adding a
stub callback function with the correct type.
As the kernel only has a couple of
Hi Mark/Will,
I would like to understand whether ARM linux community have plans to
support PSCI version 1.1 or not.
PSCI_1_1 specification introduced support for SYSTEM_RESET2 command and
this new command helps mobile devices to SYSTEM_WARM_RESET support.
Rebooting devices with warm reboot
Looks good.
Reviewed-by: Chaitanya Kulkarni
On 4/30/19 11:44 AM, Christoph Hellwig wrote:
> This file has no copyright notice, but was added as part of a commit
> adding another file using the default kernel GPLv2 license. Add
> a matching SPDX tag.
>
> Signed-off-by: Christoph Hellwig
> ---
On Tue, Apr 30, 2019 at 01:00:05PM +0200, Miroslav Benes wrote:
> On Tue, 30 Apr 2019, Tobin C. Harding wrote:
>
> > The correct cleanup function after a call to kobject_init_and_add() has
> > succeeded is kobject_del() _not_ kobject_put(). kobject_del() calls
> > kobject_put().
> >
> > Use
On Tue, Apr 30, 2019 at 05:08:11PM +0200, Petr Mladek wrote:
> On Tue 2019-04-30 10:15:34, Tobin C. Harding wrote:
> > The correct cleanup function after a call to kobject_init_and_add() has
> > succeeded is kobject_del() _not_ kobject_put(). kobject_del() calls
> > kobject_put().
>
> Really? I
Looks good.
Reviewed-by: Chaitanya Kulkarni
On 4/30/19 11:44 AM, Christoph Hellwig wrote:
> All these files have some form of the usual GPLv2 boilerplate. Switch
> them to use SPDX tags instead.
>
> Signed-off-by: Christoph Hellwig
> ---
> block/badblocks.c| 10 +-
>
On Sunday, April 28, 2019 5:08:22 PM CEST Jonathan Neuschäfer wrote:
> The property is spelled 'bias-pull-up', as documented in
> pinctrl-bindings.txt.
>
I also sent out a patch for that... back in 2017:
https://patchwork.ozlabs.org/patch/763151/
It's marked Accepted and Archived.
@rob ?
>
Hi Chanwoo,
On 4/30/19 9:34 AM, Chanwoo Choi wrote:
> Hi Lukasz,
>
> On 19. 4. 19. 오후 10:48, Lukasz Luba wrote:
>> This patch adds posibility to choose what type of data should be counted
>> by the PPMU counter. Now the type comes from DT where the event has been
>> defined. When there is no
> -Original Message-
> From: Asmaa Mnebhi
> Sent: Tuesday, April 30, 2019 8:59 PM
> To: miny...@acm.org; w...@the-dreams.de; Vadim Pasternak
> ; Michael Shych
> Cc: Asmaa Mnebhi ; linux-kernel@vger.kernel.org;
> linux-...@vger.kernel.org
> Subject: [PATCH v4 1/1] Add support for IPMB
On 4/30/19 8:10 AM, Chanwoo Choi wrote:
> Hi,
>
> On 19. 4. 19. 오후 10:48, Lukasz Luba wrote:
>> The patch adds new field in the PPMU event which shows explicitly
>> what kind of data the event is monitoring. It is possible to change it
>> using defined values in exynos_ppmu.h file.
>>
>>
> -Original Message-
> From: Asmaa Mnebhi
> Sent: Tuesday, April 30, 2019 8:59 PM
> To: miny...@acm.org; w...@the-dreams.de; Vadim Pasternak
> ; Michael Shych
> Cc: Asmaa Mnebhi ; linux-kernel@vger.kernel.org;
> linux-...@vger.kernel.org
> Subject: [PATCH v4 0/1] Add support for IPMB
On 4/30/19 8:16 AM, Chanwoo Choi wrote:
> Hi Lukasz,
>
> On 19. 4. 19. 오후 10:48, Lukasz Luba wrote:
>> Extend the documenation by events description with new 'event-data-type'
>> field. Add example how the event might be defined in DT.
>>
>> Signed-off-by: Lukasz Luba
>> ---
>>
On Tue, Apr 30, 2019 at 10:07:45PM +0200, Paolo Bonzini wrote:
> Use specific inline functions for RIP and RSP instead of
> going through kvm_register_read and kvm_register_write,
> which are quite a mouthful. kvm_rsp_read and kvm_rsp_write
> did not exist, so add them.
>
> Signed-off-by: Paolo
On Tue, 30 Apr 2019 11:33:21 -0700
Linus Torvalds wrote:
> > + "ftrace_emulate_call_update_irqoff:\n\t"
> > + "push %gs:ftrace_bp_call_return\n\t"
> > + "sti\n\t"
> > + "jmp *ftrace_update_func_call\n"
>
> .. and this should then use the "push
I was also not able to reproduce this.
Arnd and I were talking about this today morning. Here is something
Arnd noticed:
If there was a signal after do_epoll_wait(), we never were not
entering the if (err = -EINTR) at all before. But, now we do.
We could try with the below patch:
diff --git
Good point Alexey.
Expect v3 shortly.
Best,
Joel Savitz
On Sat, Apr 27, 2019 at 5:45 PM Alexey Dobriyan wrote:
>
> On Fri, Apr 26, 2019 at 03:02:08PM -0400, Joel Savitz wrote:
> > In the mainline kernel, there is no quick mechanism to get the virtual
> > memory size of the current process
151.099635]
==
[ 6151.137893] BUG: KASAN: use-after-free in follow_page_mask+0x32/0x3e0
[ 6151.169683] Read of size 8 at addr 8884ac424048 by task signal06/45144
[ 6151.201832]
[ 6151.208652] CPU: 45 PID: 45144 Comm: signal06 Kdump: loaded Not tainted
5.1.0-rc7-next-20190430+ #8
[ 6
From: Zhang Rui
Syntax only, no functional or semantic change.
Simplify how the code to discover a package is called.
Rename find_package_by_id() to rapl_find_package_domain()
Signed-off-by: Zhang Rui
Signed-off-by: Len Brown
Acked-by: Rafael J. Wysocki
Cc: linux...@vger.kernel.org
---
From: Len Brown
Syntax only, no functional or semantic change.
This routine matches packages, not die, so name it thus.
Signed-off-by: Len Brown
---
arch/x86/kernel/smpboot.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/smpboot.c
From: Len Brown
Define topology_logical_die_id() ala
existing topology_logical_package_id()
Tested-by: Zhang Rui
Signed-off-by: Len Brown
---
arch/x86/include/asm/processor.h | 1 +
arch/x86/include/asm/topology.h | 7 +
arch/x86/kernel/cpu/common.c | 1 +
From: Len Brown
The sysfs cpu/topology/core_siblings (and core_siblings_list)
attributes are documented, implemented, and used by programs to
represent set of logical CPU threads sharing the same package.
This makes sense if the next topology level above a core
is always a package. But on
From: Zhang Rui
On the new dual-die/package systems, the package temperature MSR becomes
die-scope. Thus instead of one thermal zone device per physical package,
now there should be one thermal_zone for each die on these systems.
This patch introduces x86_pkg_temp_thermal support for new
From: Len Brown
Create CPU topology sysfs attributes:
"core_threads" and "core_threads_list"
These attributes represent all of the logical CPU threads that share the
same core.
These attriutes is synonymous with the existing "thread_siblings" and
"thread_siblings_list" attribute, which will be
From: Zhang Rui
The RAPL domain "name" attribute contains "Package-N",
which is ambiguous on multi-die per-package systems.
Update the name to "package-X-die-Y" on those systems.
No change on systems without multi-die.
Driver debug messages are also updated.
Signed-off-by: Zhang Rui
From: Zhang Rui
On the new dual-die/package systems, the RAPL MSR becomes die-scope.
Thus instead of one powercap device per physical package, now there
should be one powercap device for each unique die on these systems.
This patch introduces intel_rapl driver support for new
dual-die/package
From: Len Brown
topology_die_id(cpu) is a simple macro for use inside the kernel
to get the die_id associated with the given cpu.
Signed-off-by: Len Brown
---
arch/x86/include/asm/topology.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/include/asm/topology.h
From: Len Brown
Syntax only, no functional or semantic change.
reflect actual cpuinfo_x86 field name:
s/logical_id/logical_proc_id/
Signed-off-by: Len Brown
Cc: linux-...@vger.kernel.org
---
Documentation/x86/topology.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Zhang Rui
This patch introduces coretemp driver support
for new dual-die/package systems.
On the new dual-die/package systems, the package temperature MSRs becomes
die-scope. Thus instead of one hwmon device per physical package, now
there should be one hwmon device for each die on these
This patch series does 4 things.
1. Parse the new CPUID.1F leaf to discover multi-die/package topology
2. Export multi-die topology inside the kernel
3. Update 4 places (coretemp, pkgtemp, rapl, perf) that that need to know
the difference between die and package-scope MSR.
4. Export
On Tue, Apr 30, 2019 at 11:46:44AM +0200, Arnd Bergmann wrote:
> On Tue, Apr 30, 2019 at 11:33 AM Nathan Chancellor
> wrote:
> > On Tue, Apr 30, 2019 at 09:16:50AM +0200, Arnd Bergmann wrote:
> > > On Tue, Apr 30, 2019 at 3:01 AM Nathan Chancellor
> > > wrote:
> > > >
> > > > This is Clang's
Add common library code for the Analog Bits Wide-Range PLL (WRPLL) IP
block, as implemented in TSMC CLN28HPC.
There is no bus interface or register target associated with this PLL.
This library is intended to be used by drivers for IP blocks that
expose registers connected to the PLL
Add driver code for the SiFive FU540 PRCI IP block. This IP block
handles reset and clock control for the SiFive FU540 device and
implements SoC-level clock tree controls and dividers.
Based on code written by Wesley Terpstra :
On 4/22/2019 6:52 PM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-02-11 10:57:47)
If a parent to a clock comes from outside that clock's provider, the parent
may not be present at the time the clock is registered (ie the parent comes
from another driver that has not yet probed). The clock
clk: add driver for the SiFive FU540 PRCI and PLLs it controls
Add a driver for the SiFive FU540 PRCI IP block, which handles clock and
some device reset control for the SiFive FU540 chip. Also add a driver-
independent library for the Analog Bits Wide-Range PLL (WRPLL), used by
the PRCI driver
of the problem may be somewhere else. *
* Hope this helps! *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
next/master boot bisection: next-20190430 on beagle-xm
Summary:
Start: f43b05fd4c17 Add linux-next specific files for 20190430
On Tue, Apr 30, 2019 at 9:15 AM Fabien DESSENNE wrote:
>
> Hi Rob,
>
>
> On 30/04/2019 2:40 AM, Rob Herring wrote:
> > On Tue, Apr 16, 2019 at 04:58:13PM +0200, Fabien Dessenne wrote:
> >> Add the device tree bindings document for the stm32 remoteproc devices.
> >>
> >> Signed-off-by: Fabien
On 4/30/19 6:56 AM, Chanwoo Choi wrote:
> Hi,
>
> I agree of this patch. But, I add the minor comments.
>
> If you edit them according to my comment, feel free to add my following tag:
> Acked-by: Chanwoo Choi
>
> On 19. 4. 19. 오후 10:48, Lukasz Luba wrote:
>> This patch add support of a new
From: Yazen Ghannam
The struct mce_banks[] array is only used in mce/core.c so move the
definition of struct mce_bank to mce/core.c and make the array static.
Also, change the "init" field to bool type.
Signed-off-by: Yazen Ghannam
---
Link:
From: Yazen Ghannam
The OS is expected to write all bits in MCA_CTL. However, only
implemented bits get set in the hardware.
Read back MCA_CTL so that the value in the hardware is saved and
reported through sysfs.
Signed-off-by: Yazen Ghannam
---
Link:
From: Yazen Ghannam
The OS is expected to write all bits to MCA_CTL for each bank. However,
some banks may be unused in which case the registers for such banks are
Read-as-Zero/Writes-Ignored. Also, the OS may not write any control bits
because of quirks, etc.
A bank can be considered
From: Yazen Ghannam
The focus of this patchset is define and use the MCA bank structures
and bank count per logical CPU.
With the exception of patch 4, this set applies to systems in production
today.
Patch 1:
Moves the declaration of struct mce_banks[] to the only file it's used.
Patch 2:
From: Yazen Ghannam
The number of MCA banks is provided per logical CPU. Historically, this
number has been the same across all CPUs, but this is not an
architectural guarantee. Future AMD systems may have MCA bank counts
that vary between logical CPUs in a system.
This issue was partially
From: Yazen Ghannam
Current AMD systems have unique MCA banks per logical CPU even though
the type of the banks may all align to the same bank number. Each CPU
will have control of a set of MCA banks in the hardware and these are
not shared with other CPUs.
For example, bank 0 may be the
From: Yazen Ghannam
On legacy systems, the addresses of the MCA_MISC* registers need to be
recursively discovered based on a Block Pointer field in the registers.
On Scalable MCA systems, the register space is fixed, and particular
addresses can be derived by regular offsets for bank and
Quoting Roger Lu (2019-04-30 04:20:10)
> Document the binding for enabling mtk svs on MediaTek SoC.
>
> Signed-off-by: Roger Lu
> ---
> .../devicetree/bindings/power/mtk-svs.txt | 70 +++
> 1 file changed, 70 insertions(+)
> create mode 100644
Hi Chanwoo,
On 4/30/19 6:46 AM, Chanwoo Choi wrote:
> On 19. 4. 19. 오후 11:19, Lukasz Luba wrote:
>> The patch adds description for DT binding for a new Exynos5422 Dynamic
>> Memory Controller device.
>>
>> Signed-off-by: Lukasz Luba
>> ---
>> .../bindings/memory-controllers/exynos5422-dmc.txt
On Tue, Apr 30, 2019 at 2:12 AM Dan Carpenter wrote:
> Also it was risky from a process perspective to delete the stray tab
> from the next line because some one could have argued that it was
> unrelated or that the whole line should be removed instead. You would
> have had to redo the patch for
On Tue, 2019-04-30 at 22:02 +0200, Martin Blumenstingl wrote:
> > Thanks for effort but all this just maintain the blur around HS400 on
> > amlogic.
> >
> > Let me rephrase it:
> > Tuning (phase or resampling) is meant to compensate the clock round trip in
> > UHS
> > and HS200 modes. In HS400,
Hi Guillaume,
On Tue, Apr 30, 2019 at 9:20 AM guillaume La Roque
wrote:
>
> Hi Martin,
>
>
> thanks for your feedback.
>
>
> On 4/27/19 9:44 PM, Martin Blumenstingl wrote:
> > Hi Guillaume,
> >
> > On Thu, Apr 18, 2019 at 2:48 PM Guillaume La Roque
> > wrote:
> >> drive-strength-uA is a new
On Wed, Apr 24, 2019 at 11:02 AM Nick Desaulniers
wrote:
>
> Towards the goal of removing cc-ldoption, it seems that --hash-style=
> was added to binutils 2.17.50.0.2 in 2006. The minimal required version
> of binutils for the kernel according to
> Documentation/process/changes.rst is 2.20.
>
>
On Tue, Apr 23, 2019 at 2:01 PM Nick Desaulniers
wrote:
>
> Towards the goal of removing cc-ldoption, it seems that --hash-style=
> was added to binutils 2.17.50.0.2 in 2006. The minimal required version
> of binutils for the kernel according to
> Documentation/process/changes.rst is 2.20.
>
>
On Tue, Apr 23, 2019 at 1:48 PM Nick Desaulniers
wrote:
>
> Towards the goal of removing cc-ldoption, it seems that --hash-style=
> was added to binutils 2.17.50.0.2 in 2006. The minimal required version
> of binutils for the kernel according to
> Documentation/process/changes.rst is 2.20.
>
>
Quoting Paul Walmsley (2019-04-29 18:14:14)
> On Mon, 29 Apr 2019, Stephen Boyd wrote:
> >
> > Nitpick: This might be easier to read with a switch statement:
> >
> > switch (post_divr_freq) {
> > case 0 ... 1100:
> > return 1;
> > case 1101 ... 1800:
>
Sean Christopherson writes:
> On Tue, Apr 30, 2019 at 07:33:26PM +0200, Vitaly Kuznetsov wrote:
>> Commit 47c42e6b4192 ("KVM: x86: fix handling of role.cr4_pae and rename it
>> to 'gpte_size'") introduced a regression: 32-bit PAE guests stopped
>
> "gpte_is_8_bytes" is really confusing in this
On Thu, 25 Apr 2019 11:41:05 +0100
Jean-Philippe Brucker wrote:
> On 25/04/2019 11:17, Auger Eric wrote:
> >> +/**
> >> + * ioasid_alloc - Allocate an IOASID
> >> + * @set: the IOASID set
> >> + * @min: the minimum ID (inclusive)
> >> + * @max: the maximum ID (exclusive)
> >> + * @private: data
The RTC core already ensures the alarm is set to a time in the future, it
is not necessary to check again in the driver.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-st-lpc.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/rtc/rtc-st-lpc.c b/drivers/rtc/rtc-st-lpc.c
index
On 4/29/19 6:43 PM, Rob Herring wrote:
> On Mon, Apr 29, 2019 at 7:14 AM Lukasz Luba
> wrote:
>>
>> Hi Rob,
>>
>> On 4/25/19 9:57 PM, Rob Herring wrote:
>>> On Fri, Apr 19, 2019 at 04:19:24PM +0200, Lukasz Luba wrote:
The patch adds description for DT binding for a new Exynos5422 Dynamic
Use specific inline functions for RIP and RSP instead of
going through kvm_register_read and kvm_register_write,
which are quite a mouthful. kvm_rsp_read and kvm_rsp_write
did not exist, so add them.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/kvm_cache_regs.h | 10 ++
Hi Rob,
On 4/29/19 6:36 PM, Rob Herring wrote:
> On Mon, Apr 29, 2019 at 7:05 AM Lukasz Luba
> wrote:
>>
>> Hi Rob,
>>
>> On 4/25/19 9:51 PM, Rob Herring wrote:
>>> On Fri, Apr 19, 2019 at 04:19:22PM +0200, Lukasz Luba wrote:
The device tree bindings for LPDDR3 SDRAM memories.
Hi Ulf,
On Mon, Apr 29, 2019 at 8:40 PM Martin Blumenstingl
wrote:
>
> Hi Ulf, Hi Kevin,
>
> On Mon, Apr 29, 2019 at 12:45 PM Ulf Hansson wrote:
> >
> > On Tue, 23 Apr 2019 at 11:02, Jerome Brunet wrote:
> > >
> > > The purpose of this series is too improve reliability of the amlogic mmc
> > >
Hi Jerome,
On Mon, Apr 29, 2019 at 8:50 PM Jerome Brunet wrote:
>
> On Mon, 2019-04-29 at 20:31 +0200, Martin Blumenstingl wrote:
> > Hi Jerome,
> >
> > On Mon, Apr 29, 2019 at 10:29 AM Jerome Brunet wrote:
> > > On Sat, 2019-04-27 at 22:02 +0200, Martin Blumenstingl wrote:
> > > > Hi Jerome,
>
101 - 200 of 972 matches
Mail list logo
