On Thu, Feb 08, 2018 at 12:32:56PM +, Robin Murphy wrote:
> On 08/02/18 12:01, Dave Martin wrote:
> >On Thu, Feb 08, 2018 at 10:53:52AM +, Suzuki K Poulose wrote:
> >>On 07/02/18 10:39, Dave Martin wrote:
> >>>On Wed, Jan 31, 2018 at 06:28:03PM +, Suzuki K Poulose wrote:
> Some
On Thu, Feb 08, 2018 at 11:33:44AM +0800, linxiu...@gmail.com wrote:
> From: "leilei.lin"
>
> Do not install cgroup event into the CPU context and schedule it
> if the cgroup is not running on this CPU
>
> While there is no task of cgroup running specified CPU,
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-part2-4.16-rc1
with top-most commit 616f16093d852215f6a1188de1bafdc1f8892924
Merge branches 'pm-cpufreq', 'pm-cpuidle' and 'pm-domains'
on top of commit
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
acpi-part2-4.16-rc1
with top-most commit d4abd46b7e7279a61a1aa76d1d1b16a990178e75
Merge branches 'acpi-video', 'acpi-battery' and 'acpi-cppc'
on top of commit
On Thu, Feb 08, 2018 at 11:17:33AM -0800, Randy Dunlap wrote:
> On 02/08/2018 11:09 AM, Mike Rapoport wrote:
> > Signed-off-by: Mike Rapoport
> > ---
> > mm/zpool.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/mm/zpool.c b/mm/zpool.c
>
On Fri, Feb 9, 2018 at 11:54 AM, Aishwarya Pant wrote:
> On Fri, Feb 09, 2018 at 11:31:35AM +0100, Rafael J. Wysocki wrote:
>> On Wed, Feb 7, 2018 at 2:18 PM, Aishwarya Pant wrote:
>> > The descriptions have been collected from git commit logs and reading
On Fri, Feb 9, 2018 at 11:53 AM, Juri Lelli wrote:
> Hi,
>
> On 09/02/18 11:36, Rafael J. Wysocki wrote:
>> On Friday, February 9, 2018 9:02:34 AM CET Claudio Scordino wrote:
>> > Hi Viresh,
>> >
>> > Il 09/02/2018 04:51, Viresh Kumar ha scritto:
>> > > On 08-02-18, 18:01,
On Thu, Feb 08, 2018 at 05:19:22PM +, Suzuki K Poulose wrote:
> On 08/02/18 11:00, Christoffer Dall wrote:
> >On Tue, Jan 09, 2018 at 07:04:03PM +, Suzuki K Poulose wrote:
> >>On arm/arm64 we pre-allocate the entry level page tables when
> >>a VM is created and is free'd when either all
On Thu, Feb 08, 2018 at 05:22:29PM +, Suzuki K Poulose wrote:
> On 08/02/18 11:00, Christoffer Dall wrote:
> >On Tue, Jan 09, 2018 at 07:04:09PM +, Suzuki K Poulose wrote:
> >>Now that we can manage the stage2 page table per VM, switch the
> >>configuration details to per VM instance. We
On Thu, Feb 08, 2018 at 05:53:17PM +, Suzuki K Poulose wrote:
> On 08/02/18 11:14, Christoffer Dall wrote:
> >On Tue, Jan 09, 2018 at 07:04:10PM +, Suzuki K Poulose wrote:
> >>Allow the guests to choose a larger physical address space size.
> >>The default and minimum size is 40bits. A
The PAGE_POISON macro is used in page_poison.c only, so avoid exporting
it. Also remove the "mm/debug-pagealloc.c" related comment, which is
obsolete.
Signed-off-by: Wei Wang
Cc: Andrew Morton
Cc: Michal Hocko
Cc: Michael S.
On 02/09/18 at 05:16pm, Sergey Senozhatsky wrote:
> Hi,
>
> On (02/09/18 16:06), Dave Young wrote:
> [..]
> > +void __init dump_stack_set_arch_desc(const char *fmt, ...)
> ..
> > +void dump_stack_print_info(const char *log_lvl)
> ..
> > +void show_regs_print_info(const char *log_lvl)
> ..
>
>
On (02/09/18 16:27), Dave Young wrote:
> > Seems that those functions are still defined in printk header.
> > Did you test !CONFIG_PRINTK build?
Apparently dump_stack(void) is also in printk.h
extern asmlinkage void dump_stack(void) __cold;
so it's "OK" to keep those functions in printk.h, I
On Thu, Feb 08, 2018 at 03:25:30PM +, John Garry wrote:
> On 08/02/2018 13:55, Jiri Olsa wrote:
> > On Wed, Feb 07, 2018 at 01:45:00AM +0800, John Garry wrote:
> >
> > SNIP
> >
> > >
> > > +static int is_json_file(const char *name)
> > > +{
> > > + const char *suffix;
> > > +
> > > + if
The "cooling-min-level" and "cooling-max-level" properties are not
parsed by any part of the kernel currently and the max cooling state of
a CPU cooling device is found by referring to the cpufreq table instead.
Remove the unused properties from the CPU nodes.
Signed-off-by: Viresh Kumar
The "cooling-min-level" and "cooling-max-level" properties are not
parsed by any part of the kernel currently and the max cooling state of
a CPU cooling device is found by referring to the cpufreq table instead.
Remove the unused properties from the CPU nodes.
Signed-off-by: Viresh Kumar
The "cooling-min-level" and "cooling-max-level" properties are not
parsed by any part of the kernel currently and the max cooling state of
gpio-fan cooling device is found by referring to the
"gpio-fan,speed-map" instead.
Remove the unused properties from the gpio-fan node.
Signed-off-by: Viresh
On 02/09/18 at 04:51pm, Dave Young wrote:
> On 02/09/18 at 05:42pm, Sergey Senozhatsky wrote:
> > On (02/09/18 16:27), Dave Young wrote:
> > > > Seems that those functions are still defined in printk header.
> > > > Did you test !CONFIG_PRINTK build?
> >
> > Apparently dump_stack(void) is also in
On 09/02/2018 09:58, Viresh Kumar wrote:
> The "cooling-min-level" and "cooling-max-level" properties are not
> parsed by any part of the kernel currently and the max cooling state of
> a CPU cooling device is found by referring to the cpufreq table instead.
>
> Remove the unused properties from
On 09/02/2018 09:58, Viresh Kumar wrote:
> The "cooling-min-level" and "cooling-max-level" properties are not
> parsed by any part of the kernel currently and the max cooling state of
> gpio-fan cooling device is found by referring to the
> "gpio-fan,speed-map" instead.
>
> Remove the unused
On Wed, 07 Feb 2018, Jonathan Corbet wrote:
> XML escaping is a worry that came with DocBook, which we no longer have any
> dealings with. So get rid of the useless xml_escape()/xml_unescape()
> functions. No change to the generated output.
I think this will break at least the
Greetings,
Today's mainline kernel Oops when running stack_grow_into_huge
Machine: Power 8 bare-metal
Kernel: 4.15.0
Config: attached
gcc: 4.8.5
Test: libhugetlbfs
stack_grow_into_huge (16M: 64) resulted in kernel Oops message and the
bad address maps to:
# gdb -batch vmlinux -ex 'list
Commit 3c47d19ff4dc ("drivers: base: add coredump driver ops") added
a new callback in struct device_driver, but not a kerneldoc description
so here it is.
Fixes: 3c47d19ff4dc ("drivers: base: add coredump driver ops")
Signed-off-by: Arend van Spriel
---
On 9 February 2018 at 14:39, Dmitry Torokhov wrote:
> On Thu, Feb 8, 2018 at 10:08 PM, Baolin Wang wrote:
>> On some platforms (such as Spreadtrum platform), the GPIO keys can only
>> be triggered by level type.
>
> How do you stop the interrupt
On Wed, 07 Feb 2018, Jonathan Corbet wrote:
> Begin the process of splitting up the nearly 500-line process_file()
> function by moving STATE_NORMAL processing to a separate function.
>
> Signed-off-by: Jonathan Corbet
> ---
> scripts/kernel-doc | 21
From: Joerg Roedel
Use the entry-stack as a trampoline to enter the kernel. The
entry-stack is already in the cpu_entry_area and will be
mapped to userspace when PTI is enabled.
Signed-off-by: Joerg Roedel
---
arch/x86/entry/entry_32.S| 135
From: Joerg Roedel
Add unconditional cr3 switches between user and kernel cr3
to all non-NMI entry and exit points.
Signed-off-by: Joerg Roedel
---
arch/x86/entry/entry_32.S | 59 ++-
1 file changed, 58
From: Joerg Roedel
Restoring the segments can cause exceptions that need to be
handled. With PTI enabled, we still need to be on kernel cr3
when the exception happens. For the cr3-switch we need
at least one integer scratch register, so we can't switch
with the user integer
From: Joerg Roedel
Make them available on 32 bit and clone_pgd_range() happy.
Signed-off-by: Joerg Roedel
---
arch/x86/include/asm/pgtable.h| 49 +++
arch/x86/include/asm/pgtable_64.h | 49
From: Joerg Roedel
Generic page-table code populates all non-leaf entries with
_KERNPG_TABLE bits set. This is fine for all paging modes
except PAE.
In PAE mode only a subset of the bits is allowed to be set.
Make sure we only set allowed bits by masking out the
reserved bits.
From: Joerg Roedel
These two functions are required for PTI on 32 bit:
* pgdp_maps_userspace()
* pgd_large()
Also re-implement pgdp_maps_userspace() so that it will work
on 64 and 32 bit kernels.
Signed-off-by: Joerg Roedel
---
On Wed, 07 Feb 2018, Jonathan Corbet wrote:
> Move the top-level prototype-processing code out of process_file().
>
> Signed-off-by: Jonathan Corbet
Reviewed-by: Jani Nikula
> ---
> scripts/kernel-doc | 46
On Thu, 08 Feb 2018, Jonathan Corbet wrote:
> On Thu, 8 Feb 2018 13:29:53 +1100
> "Tobin C. Harding" wrote:
>
>> It doesn't appear to be introduced by you but the brace positions are
>> non-uniform in this patch.
>>
>> if
>> {
>> ...
>> }
>> else
>> {
>> ...
From: Joerg Roedel
Switch back to the trampoline stack before returning to
userspace.
Signed-off-by: Joerg Roedel
---
arch/x86/entry/entry_32.S | 55 +++
1 file changed, 55 insertions(+)
diff --git
From: Joerg Roedel
This makes it easier to split up the shared iret code path.
Signed-off-by: Joerg Roedel
---
arch/x86/entry/entry_32.S | 97 ---
1 file changed, 49 insertions(+), 48 deletions(-)
diff --git
On 02-02-18, 15:30, Daniel Lezcano wrote:
> Agree the cpufreq driver can be unloaded and this part needs some
> adjustments.
Also note that the cpufreq cooling device has two separate set of
callbacks, one for the power-specific callbacks. You haven't taken
care of them in the combo thing.
--
On 07/02/18 21:03, Kim Phillips wrote:
Commit 1c8859848dbb ("coresight replicator: Cleanup programmable
replicator naming") changed the Kconfig symbol name from
QCOM_REPLICATOR, which, whilst not in the single arm64 defconfig,
was being set in my juno build script, which left the new symbol
On Thu, Feb 08, 2018 at 04:03:41PM +, Will Deacon wrote:
> On Thu, Feb 08, 2018 at 04:46:43PM +0100, Peter Zijlstra wrote:
> > On Thu, Feb 08, 2018 at 03:30:31PM +, Will Deacon wrote:
> > > On Thu, Feb 08, 2018 at 03:00:05PM +0100, Peter Zijlstra wrote:
> >
> > > > Without this ordering I
On Tue, 6 Feb 2018, Petr Mladek wrote:
> From: Jason Baron
>
> We are going to add a feature called atomic replace. It will allow to
> create a patch that would replace all already registered patches.
> For this, we will need to dynamically create funcs and objects
> for
On Tue, 6 Feb 2018, Petr Mladek wrote:
> We are going to add a feature called atomic replace. It will allow to
> create a patch that would replace all already registered patches.
> For this, we will need to dynamically create funcs and objects
> for functions that are not longer patched.
s/not
On Tue, 6 Feb 2018, Petr Mladek wrote:
> From: Jason Baron
>
> Currently klp_patch contains a pointer to a statically allocated array of
> struct klp_object and struct klp_objects contains a pointer to a statically
> allocated array of klp_func. In order to allow for the
On Fri, Feb 9, 2018 at 4:40 AM, Maxime Ripard wrote:
> On Wed, Feb 07, 2018 at 01:49:59PM +0100, Giulio Benetti wrote:
>> Hi,
>>
>> Il 07/02/2018 11:39, Maxime Ripard ha scritto:
>> > On Wed, Jan 24, 2018 at 08:37:28PM +0100, Giulio Benetti wrote:
>> > Also, how was
Hi Mark,
> > +static const struct soc_enum ak4458_dac_enum[] = {
> > +/*0*/ SOC_ENUM_SINGLE(AK4458_01_CONTROL2, 1,
> > + ARRAY_SIZE(ak4458_dem_select_texts),
> > + ak4458_dem_select_texts),
> > +/*1*/ SOC_ENUM_SINGLE(AK4458_0A_CONTROL6, 0,
> The fact
On Wed, Feb 7, 2018 at 2:18 PM, Aishwarya Pant wrote:
> Description has been collected from git commit history and reading
> through code.
>
> Signed-off-by: Aishwarya Pant
> ---
> .../ABI/testing/sysfs-devices-platform-dock| 38
>
The registration code first registers the mdev device, and then
proceeds to populate sysfs. An userspace application that listens
for the ADD uevent is therefore likely to look for sysfs entries
that have not yet been created.
The canonical way to fix this is to use attribute groups that are
On Wed, Feb 7, 2018 at 2:18 PM, Aishwarya Pant wrote:
> The descriptions have been collected from git commit logs and reading
> through code.
>
> Signed-off-by: Aishwarya Pant
> ---
> Documentation/ABI/testing/sysfs-platform-dptf | 30
>
On Friday, February 9, 2018 9:02:34 AM CET Claudio Scordino wrote:
> Hi Viresh,
>
> Il 09/02/2018 04:51, Viresh Kumar ha scritto:
> > On 08-02-18, 18:01, Claudio Scordino wrote:
> >> When the SCHED_DEADLINE scheduling class increases the CPU utilization,
> >> we should not wait for the rate
On Fri 2018-02-09 12:28:30, Sergey Senozhatsky wrote:
> On (02/08/18 17:48), Petr Mladek wrote:
> By postponing klogd wakeup we don't really address logbuf_lock
> contention. We have no guarantees that no new printk will come
> while klogd is active. Besides, consoles don't really delay
> klogd -
From: Nitesh Shetty
This removes the dependency on interrupts to wake up task. Set task
state as TASK_RUNNING, if need_resched() returns true,
while polling for IO completion.
Earlier, polling task used to sleep, relying on interrupt to wake it up.
This made some IO take
On Thu, Feb 08, 2018 at 02:46:32PM +0100, Marek Szyprowski wrote:
> Hi Krzysztof,
>
> On 2018-01-30 22:18, Krzysztof Kozlowski wrote:
> > Hi,
> >
> > Changes since v1:
> > 1. New patch (1/4) calling devm_of_platform_populate() in PMU driver,
> > following Rob's advice.
> > 2. The DTS patches
On Fri 2018-02-09 12:28:30, Sergey Senozhatsky wrote:
> On (02/08/18 17:48), Petr Mladek wrote:
> > Note that we need Tejun's patch for-4.16 because it fixes a potential
> > race introduced by the console waiter logic.
>
> I understand it. I think I put my Reviewed-by on v1, maybe not...
> Here
Hi,
On 09/02/18 11:36, Rafael J. Wysocki wrote:
> On Friday, February 9, 2018 9:02:34 AM CET Claudio Scordino wrote:
> > Hi Viresh,
> >
> > Il 09/02/2018 04:51, Viresh Kumar ha scritto:
> > > On 08-02-18, 18:01, Claudio Scordino wrote:
> > >> When the SCHED_DEADLINE scheduling class increases
On Fri, Feb 09, 2018 at 11:31:35AM +0100, Rafael J. Wysocki wrote:
> On Wed, Feb 7, 2018 at 2:18 PM, Aishwarya Pant wrote:
> > The descriptions have been collected from git commit logs and reading
> > through code.
> >
> > Signed-off-by: Aishwarya Pant
> >
qcom,smmu-v2 is an arm,smmu-v2 implementation with specific
clock and power requirements. This smmu core is used with
multiple masters on msm8996, viz. mdss, video, etc.
Add bindings for the same.
Signed-off-by: Vivek Gautam
Reviewed-by: Rob Herring
Hi Viresh,
Il 09/02/2018 04:51, Viresh Kumar ha scritto:
On 08-02-18, 18:01, Claudio Scordino wrote:
When the SCHED_DEADLINE scheduling class increases the CPU utilization,
we should not wait for the rate limit, otherwise we may miss some deadline.
Tests using rt-app on Exynos5422 have shown
On Thu, Feb 08, 2018 at 04:50:40PM -0700, Long Li wrote:
> From: Long Li
No, Dan wrote the first patch here, don't change the authorship of a
patch :(
Now fixed up by hand...
Hi Ulf,
On Thu, Feb 08, 2018 at 10:31:39PM +0100, Ulf Hansson wrote:
> On 8 February 2018 at 15:59, Quentin Schulz
> wrote:
> > Hi Ulf,
> >
> > On Wed, Aug 30, 2017 at 03:43:49PM +0200, Ulf Hansson wrote:
> >> On 30 August 2017 at 14:44, Hans de Goede
On Fri, Feb 09, 2018 at 07:36:49AM -0600, Gustavo A. R. Silva wrote:
> Hi Leon,
>
> Quoting Leon Romanovsky :
>
> > On Fri, Feb 09, 2018 at 12:37:02AM -0600, Gustavo A. R. Silva wrote:
> > > In case the message header and payload cannot be stored, function
> > > nlmsg_put returns
On Fri, Feb 9, 2018 at 10:52 PM, Andy Shevchenko
wrote:
> On Fri, Feb 9, 2018 at 4:43 PM, Donglin Peng wrote:
>> There is some duplicate code in soc-core.c, and the kernel provides
>> DEFINE_SHOW_ATTRIBUTE() helper macro to decrease it in
On Fri, Feb 09, 2018 at 01:51:31PM +, Will Deacon wrote:
> On Fri, Feb 09, 2018 at 02:49:57PM +0100, Greg KH wrote:
> > On Fri, Feb 09, 2018 at 01:48:11PM +, Will Deacon wrote:
> > > Hi Greg,
> > >
> > > I've put together a tag which includes all of the upstream arm64 spectre
> > > and
>
On Fri, Feb 09, 2018 at 05:45:49PM +0800, Jason Wang wrote:
> To avoid slab to warn about exceeded size, fail early if queue
> occupies more than KMALLOC_MAX_SIZE.
>
> Reported-by: syzbot+e4d4f9ddd42955397...@syzkaller.appspotmail.com
> Fixes: 2e0ab8ca83c12 ("ptr_ring: array based FIFO for
Hi Kieran,
Thanks for your patch.
On 2018-02-07 17:34:45 +, Kieran Bingham wrote:
> From: Kieran Bingham
>
> The ADV748x has identical map configurations for each register map. The
> duplication of each map can be simplified using a helper macro
On 09/02/18 15:54, Florian Fainelli wrote:
> On February 9, 2018 12:51:33 AM PST, Marc Zyngier
> wrote:
>> On 09/02/18 02:10, Jaedon Shin wrote:
>>> Since commit ad67b74d2469 ("printk: hash addresses printed with %p")
>>> pointers printed with %p are hashed. Use %px instead
On 2/8/2018 10:54 PM, Mike Galbraith wrote:
> On Thu, 2018-02-08 at 14:19 -0800, Rohit Jain wrote:
>> This patch introduces the sysctl for sched_domain based migration costs.
>> These in turn can be used for performance tuning of workloads.
>
> With this patch, we trade 1 completely bogus
If a device is runtime PM suspended when we enter suspend and has
a dedicated wake irq, we can get the following warning:
WARNING: CPU: 0 PID: 108 at kernel/irq/manage.c:526 enable_irq+0x40/0x94
[ 102.087860] Unbalanced enable for IRQ 147
...
(enable_irq) from [] (dev_pm_arm_wake_irq+0x4c/0x60)
Neither clang nor GCC like this very much with -m32:
long long ret;
asm ("movb $5, %0" : "=q" (ret));
However, GCC can tolerate this variant:
long long ret;
switch (sizeof(ret)) {
case 1:
asm ("movb $5, %0" : "=q" (ret));
case 8:
Nikita Leshenko writes:
> The patch looks correct, however I’m confused about why you consider
> this to be a bug in the guest rather than a bug in KVM.
>
> The spec for x2APIC states:
> "The support for Directed EOI capability can be detected by means of
> bit 24
On 04/02/18 23:37, Randy Dunlap wrote:
[...]
>> +reason, could neither be declared as constant, nor it could take advantage
>
> nor could it
ok
[...]
>> +Ex: A policy that is loaded from userspace.
>
> Either
>Example:
> or
>E.g.:
>
On Fri, Feb 9, 2018 at 4:23 PM, Carlo Caione wrote:
> From: Carlo Caione
>
> On at least one notebook (ECS EF20EA) the 'hp-detect' GPIO is defined in
> the DSDT table by the ACPI GpioIo resources in _CRS. Add this mapping to
> the rt5645 driver to enable the
From: Kieran Bingham
To allow dual pipelines utilising two WPF entities when available, the
VSP was updated to support header-mode display list in continuous
pipelines.
A small bug in the status check of the command register causes the
second pipeline to
From: Wanpeng Li
vCPUs are very unlikely to get preempted when they are the only task
running on a CPU. PV TLB flush is slower that the native flush in that
case. In addition, avoid traversing all the cpus for pv tlb flush when
steal time is disabled since pv tlb flush
On Thu, 8 Feb 2018 12:20:31 +0100
Jiri Olsa wrote:
> On Wed, Feb 07, 2018 at 03:24:13PM -0500, Steven Rostedt wrote:
> > From: "Steven Rostedt (VMware)"
> >
> > Add a special type "symbol" that will use %pS to display the field of a
> > function based
Hi Kieran,
Thanks for your patch,
On 2018-02-07 17:34:46 +, Kieran Bingham wrote:
> From: Kieran Bingham
>
> The ADV748x has 12 pages mapped onto I2C addresses.
>
> In the existing implementation only 11 are mapped correctly in the page
>
On 2018/02/09 23:18, Paul E. McKenney wrote:
> Hello!
>
> This RFC series adds some miscellaneous updates to the Linux kernel
> memory model:
>
> 1.Clarify the origin and scope of the tool name to avoid confusion
> between "memory model" and "memory management", courtesy of
>
Commit 3ca0ff571b09 ("locking/mutex: Rework mutex::owner") reworked the
basic mutex implementation to deal with several problems. Documentation
was however left unchanged and became stale.
Update mutex-design.txt to reflect changes introduced by the above commit.
Signed-off-by: Juri Lelli
Change log:
v2 - v3
Andrew Morton's comments:
- Moved read of pgdat->first_deferred_pfn into
deferred_zone_grow_lock, thus got rid of READ_ONCE()/WRITE_ONCE()
- Replaced spin_lock() with spin_lock_irqsave() in
deferred_grow_zone
- Updated
Hi gengdongjiu,
On 05/02/18 06:19, gengdongjiu wrote:
> On 2018/1/31 3:21, James Morse wrote:
>> On 24/01/18 20:06, gengdongjiu wrote:
On 06/01/18 16:02, Dongjiu Geng wrote:
> The ARM64 RAS SError Interrupt(SEI) syndrome value is specific to the
> guest and user space needs a way to
We enable hardware DBM bit in a capable CPU, very early in the
boot via __cpu_setup. This doesn't give us a flexibility of
optionally disable the feature, as the clearing the bit
is a bit costly as the TLB can cache the settings. Instead,
we delay enabling the feature until the CPU is brought up
Some variants of the Arm Cortex-55 cores (r0p0, r0p1, r1p0) suffer
from an erratum 1024718, which causes incorrect updates when DBM/AP
bits in a page table entry is modified without a break-before-make
sequence. The work around is to skip enabling the hardware DBM feature
on the affected cores.
Some capabilities have different criteria for detection and associated
actions based on the matching criteria, even though they all share the
same capability bit. So far we have used multiple entries with the same
capability bit to handle this. This is prone to errors, as the
cpu_enable is invoked
Update the MIDR encodings for the Cortex-A55 and Cortex-A35
Cc: Mark Rutland
Reviewed-by: Dave Martin
Signed-off-by: Suzuki K Poulose
---
arch/arm64/include/asm/cputype.h | 4
1 file changed, 4 insertions(+)
diff --git
We enable hardware DBM bit in a capable CPU, very early in the
boot via __cpu_setup. This doesn't give us a flexibility of
optionally disable the feature, as the clearing the bit
is a bit costly as the TLB can cache the settings. Instead,
we delay enabling the feature until the CPU is brought up
Some variants of the Arm Cortex-55 cores (r0p0, r0p1, r1p0) suffer
from an erratum 1024718, which causes incorrect updates when DBM/AP
bits in a page table entry is modified without a break-before-make
sequence. The work around is to skip enabling the hardware DBM feature
on the affected cores.
When a CPU is brought up, it is checked against the caps that are
known to be enabled on the system (via verify_local_cpu_capabilities()).
Based on the state of the capability on the CPU vs. that of System we
could have the following combinations of conflict.
On 09/02/18 17:54, Suzuki K Poulose wrote:
This series reworks the arm64 CPU capabilities handling (which
manages the system features and errata). The current infrastructure
doesn't allow fine control for handling different features or errata.
There is one rule for features and another rule for
While processing the list of capabilities, it is useful to
filter out some of the entries based on the given mask for the
scope of the capabilities to allow better control. This can be
used later for handling LOCAL vs SYSTEM wide capabilities and more.
All capabilities should have their scope set
On Fri, Feb 09, 2018 at 12:01:45PM -0600, Timur Tabi wrote:
> On Fri, Feb 9, 2018 at 7:39 AM, Greg Kroah-Hartman
> wrote:
> > This is the start of the stable review cycle for the 4.14.19 release.
> > There are 22 patches in this series, all will be posted as a response
On Fri, Feb 09, 2018 at 05:54:48PM +, Suzuki K Poulose wrote:
> Right now we run through the errata workarounds check on all boot
> active CPUs, with SCOPE_ALL. This doesn't help with detecting the
> errata's with a SYSTEM_SCOPE. While nobody uses it, let us clean
> this up in preparation for
On Fri, 9 Feb 2018, Paul E. McKenney wrote:
> This commit adds comments to the litmus tests summarizing what these
> tests are intended to demonstrate.
>
> Suggested-by: Ingo Molnar
> Signed-off-by: Paul E. McKenney
> [ paulmck: Apply Andrea's and
Hi Klaus,
Am Samstag, 3. Februar 2018, 16:50:16 CET schrieb Klaus Goger:
> Enable the NXP SGTL5000 audio codec on the RK3399-Q7 EVK baseboard
> Haikou.
>
> The i2s0_2ch_bus definition is only done in the SoM dtsi as it is
> missing the LRCK_RX pin (that is used otherwise) and therefore not
>
On 09/02/18 19:48, Linus Torvalds wrote:
> On Fri, Feb 9, 2018 at 6:28 AM, Juergen Gross wrote:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
>> for-linus-4.16-rc1-tag
>
> So I've pulled this, but the back-merges *really* annoy me.
>
> Seriously, DON'T DO
On Fri, Feb 09, 2018 at 05:43:55PM +, Andy Lutomirski wrote:
> The 64-bit code mostly uses a bunch of push instructions for this.
I had it implemented with tons of push instructions first, but that
doesn't work in cases where the stack switch needs to happen only after
everything is copied
watchdog_init_timeout() will allways pick timeout_param since it
defaults to a valid timeout.
Following best practice described in
Documentation/watchdog/watchdog-kernel-api.txt to make use of
the parameter logic.
Signed-off-by: Marcus Folkesson
---
watchdog_init_timeout() will allways pick timeout_param since it
defaults to a valid timeout.
By following best practice described in
Documentation/watchdog/watchdog-kernel-api.txt, it also
let us to set timout-sec property in devicetree.
Signed-off-by: Marcus Folkesson
watchdog_init_timeout() will allways pick timeout_param since it
defaults to a valid timeout.
By following best practice described in
Documentation/watchdog/watchdog-kernel-api.txt, it also
let us to set timout-sec property in devicetree.
Signed-off-by: Marcus Folkesson
watchdog_init_timeout() will allways pick timeout_param since it
defaults to a valid timeout.
By following best practice described in
Documentation/watchdog/watchdog-kernel-api.txt, it also
let us to set timout-sec property in devicetree.
Signed-off-by: Marcus Folkesson
On Fri, Feb 9, 2018 at 3:03 PM, Sebastian Reichel
wrote:
> Add secure-reg-access on PPD device tree to enable PMU and
> hardware counters for perf.
>
> Signed-off-by: Sebastian Reichel
Reviewed-by: Fabio Estevam
On Fri, Feb 9, 2018 at 3:03 PM, Sebastian Reichel
wrote:
> + gpc_reg = ioremap(MXC_CORTEXA8_PLAT_GPC, 4);
> + if (!gpc_reg) {
> + pr_warning("unable to map GPC to enable perf\n");
> + return;
> + }
> +
> + gpc
This patchseries fixes the bananapi m1 devicetree, to be able to boot again.
The first two patches update/improve the devicetree and the last patch adds
all missing regulators.
Regards,
Philipp
Philipp Rossak (3):
arm: dts: sun6i: a31s: bpi-m2: update mmc supply nodes
arm: dts: sun6i: a31s:
This patch fixes a bootproblem with the Bananapi M2 board. Since there
are some regulators missing we add them right now. Those values come
from the schematic, below you can find a small overview:
* reg_aldo1: 3,3V, powers the wifi
* reg_aldo2: 2,5V, powers the IO of the RTL8211E
* reg_aldo3:
1 - 100 of 1658 matches
Mail list logo