Commit-ID: 24613a04ad1c0588c10f4b5403ca60a73d164051
Gitweb: https://git.kernel.org/tip/24613a04ad1c0588c10f4b5403ca60a73d164051
Author: Borislav Petkov
AuthorDate: Thu, 4 Apr 2019 22:14:07 +0200
Committer: Borislav Petkov
CommitDate: Wed, 10 Apr 2019 22:41:24 +0200
x86/microcode: Fix t
Commit-ID: c02f48e070bde326f55bd94544ca82291f7396e3
Gitweb: https://git.kernel.org/tip/c02f48e070bde326f55bd94544ca82291f7396e3
Author: Borislav Petkov
AuthorDate: Fri, 5 Apr 2019 06:28:11 +0200
Committer: Borislav Petkov
CommitDate: Wed, 10 Apr 2019 22:43:24 +0200
x86/microcode: Depre
This is a standard BCD RTC that will fail in 2100.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf85363.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/rtc/rtc-pcf85363.c b/drivers/rtc/rtc-pcf85363.c
index 3905c0ad9d83..8d538a253d72 100644
--- a/drivers/rtc/rtc-pcf85363.
regmap is abstracting the i2c functionalities the best it can, there is no
need to check.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf85363.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/rtc/rtc-pcf85363.c b/drivers/rtc/rtc-pcf85363.c
index 8d538a253d72..5e369846795e
pcf85363->dev is unused, remove it.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf85363.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/rtc/rtc-pcf85363.c b/drivers/rtc/rtc-pcf85363.c
index a3988079f60a..3905c0ad9d83 100644
--- a/drivers/rtc/rtc-pcf8
It is not necessary to forward declare pcf85363_driver as it is not used
before being declared.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf85363.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/rtc/rtc-pcf85363.c b/drivers/rtc/rtc-pcf85363.c
index 5e369846795e..afb1baa
Use SPDX-License-Identifier instead of a verbose license text.
The original text refers to version 2 so also update MODULE_LICENSE() to
"GPL v2" instead of "GPL".
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-pcf85363.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --
Hi,
On Tue, Apr 9, 2019 at 4:14 PM Matthias Kaehlcke wrote:
>
> Add GPIO D5 (BT_ENABLE_L) as reset-GPIO to the power sequence for the
> Bluetooth/WiFi module. On devices with a Broadcom module the signal
> needs to be asserted to use Bluetooth.
>
> Note that BT_ENABLE_L is a misnomer in the schem
Hi all,
In commit
70802487bb91 ("ASoC: pcm: fix error handling when try_module_get() fails.")
Fixes tag
Fixes: 52034add7 (ASoC: pcm: update module refcount if
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more) or (for g
Hi Mike,
Commit
a9781aff5d95 ("orangefs: add orangefs_revalidate_mapping")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpXAWgmSQoku.pgp
Description: OpenPGP digital signature
Hi Bjorn
This is v2 of my patch to fix the disable_acs_redir paramater.
Per our discussion I've found a much better way which can be
applied to the resource_alignment paramater. Thus, I've included
a second patch that removes the static buffer used there.
I'd appreciate it if the first patch can
In most cases, kmalloc will not be available early in boot when
pci_setup() is called. Thus, the kstrdup call that was added to fix the
__initdata bug with the disable_acs_redir parameter usually returns
NULL. Thus the parameter is discarded and it does not take into effect.
To fix this, we store
Clean up the 'resource_alignment' parameter code to use kstrdup
in the initcall routine instead of a static buffer that wastes memory
regardless of whether the feature is used. This allows us to drop
'COMMAND_LINE_SIZE' bytes (typically 256-4096 depending on architecture)
of static data.
This is s
--
Greetings From Mrs,Elodie Antoine
May be this letter will definitely come to you as a huge surprise, but
I implore you to take the time to go through it carefully as the
decision you make will go off a long way to determine my future and
continued existence. I am Mrs.Elodie Antoine aging
On 4/10/19 3:35 PM, Guenter Roeck wrote:
> On Wed, Apr 10, 2019 at 01:49:05PM -0500, Gustavo A. R. Silva wrote:
>> In preparation to enabling -Wimplicit-fallthrough, mark switch
>> cases where we are expecting to fall through.
>>
>> This patch fixes the following warnings:
>>
>> drivers/watchdog
Hi all,
If no one cares I'll add this to my tree for 5.2.
Thanks
--
Gustavo
On 3/20/19 3:16 PM, Gustavo A. R. Silva wrote:
> Hi all,
>
> Friendly ping:
>
> Who can take this?
>
> Thanks
> --
> Gustavo
>
> On 2/9/19 2:29 AM, Tokunori Ikegami wrote:
>> Reviewed-by: Tokunori Ikegami
>>
>>> ---
Hi all,
If no one cares I'll add this to my tree for 5.2.
Thanks
--
Gustavo
On 3/20/19 3:17 PM, Gustavo A. R. Silva wrote:
> Hi all,
>
> Friendly ping:
>
> Who can take this?
>
> Thanks
> --
> Gustavo
>
> On 2/8/19 12:12 PM, Gustavo A. R. Silva wrote:
>> In preparation to enabling -Wimplicit
Hi all,
If no one cares I'll add this to my tree for 5.2.
Thanks
--
Gustavo
On 3/20/19 3:19 PM, Gustavo A. R. Silva wrote:
> Hi all,
>
> Friendly ping:
>
> Who can take this?
>
> Thanks
> --
> Gustavo
>
> On 2/8/19 12:09 PM, Gustavo A. R. Silva wrote:
>> In preparation to enabling -Wimplicit
Hi all,
If no one cares I'll add this to my tree for 5.2.
Thanks
--
Gustavo
On 3/20/19 3:20 PM, Gustavo A. R. Silva wrote:
> Hi all,
>
> Friendly ping:
>
> Who can take this?
>
> Thanks
> --
> Gustavo
>
> On 2/8/19 12:02 PM, Gustavo A. R. Silva wrote:
>> In preparation to enabling -Wimplicit
The ror32 implementation (word >> shift) | (word << (32 - shift) has
undefined behaviour if shift is outside the [1, 31] range. Similarly
for the 64 bit variants. Most callers pass a compile-time
constant (naturally in that range), but there's an UBSAN report that
these may actually be called with
On 2019-04-10 18:52:41 [+0200], Borislav Petkov wrote:
> On Wed, Apr 10, 2019 at 06:36:15PM +0200, Borislav Petkov wrote:
> > Well, this is going in the wrong direction. The proper thing to do would
> > be to have:
> >
> > rdpkru()
> > wrpkru()
> >
> > which only do the inline asm with the respec
We can't seem to have a kernel with CONFIG_EXPERT set but
CONFIG_DEBUG_KERNEL unset these days.
While some of the features under the CONFIG_EXPERT require
CONFIG_DEBUG_KERNEL, it doesn't apply for all features.
The meaning of CONFIG_EXPERT and CONFIG_DEBUG_KERNEL has been
mixed here.
It looks li
On Wed, Apr 10, 2019 at 11:03:20AM +0300, Nikolai Kostrigin wrote:
> 10.04.2019 10:26, Nikolai Kostrigin пишет:
> > Hello!
> >
> > 10.04.2019 00:59, Bjorn Helgaas пишет:
> >> [+cc Alex]
> >>
> >> This claims to be a resend, but I don't see a previous posting.
> > For some reason, unknown to me, my
Hi Rob,
In commit
7800990023f4 ("of: use correct function prototype for of_overlay_fdt_apply()")
Fixes tag
Fixes: commit 39a751a4cb7e ("of: change overlay apply input data from
unflattened to FDT")
has these problem(s):
- leading word 'commit' unexpected
--
Cheers,
Stephen Rothwell
On 4/10/19 2:25 PM, Sebastian Andrzej Siewior wrote:
>> static inline void write_pkru(u32 pkru)
>> {
>> if (boot_cpu_has(X86_FEATURE_OSPKE))
>> -__write_pkru(pkru);
>> +wrpkru(pkru);
> I think if this is a simple
>
>'s@__write_pkru_ins@wrpkru@g'
>'s@__read_pk
On Wed, Apr 10, 2019 at 4:28 PM Stephen Rothwell wrote:
>
> Hi Rob,
>
> In commit
>
> 7800990023f4 ("of: use correct function prototype for
> of_overlay_fdt_apply()")
>
> Fixes tag
>
> Fixes: commit 39a751a4cb7e ("of: change overlay apply input data from
> unflattened to FDT")
>
> has these
[+cc Keith, Jonathan (VMD guys)]
I'm OK with this from a PCI perspective. It would be nice if
dma_domain_list
dma_domain_list_lock
add_dma_domain()
del_dma_domain()
set_dma_domain_ops()
could all be moved to vmd.c, since they're really only used there.
But we don't really have a good
On Wed, Apr 10, 2019 at 2:26 PM Sinan Kaya wrote:
>
> We can't seem to have a kernel with CONFIG_EXPERT set but
> CONFIG_DEBUG_KERNEL unset these days.
>
> While some of the features under the CONFIG_EXPERT require
> CONFIG_DEBUG_KERNEL, it doesn't apply for all features.
>
> The meaning of CONFIG
Quoting Jeffrey Hugo (2019-04-10 12:39:16)
> On 4/10/2019 10:53 AM, Stephen Boyd wrote:
> > Quoting Jeffrey Hugo (2019-04-08 14:46:11)
> >> On 4/4/2019 3:53 PM, Stephen Boyd wrote:
> >>> In some circumstances drivers register clks early and don't have access
> >>> to a struct device because the dev
On Fri, Feb 8, 2019 at 10:02 AM Gustavo A. R. Silva
wrote:
>
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warnings:
>
> drivers/mtd/chips/cfi_util.c: In function ‘cfi_build_cmd’:
> drivers/mtd/ch
On Fri, Feb 8, 2019 at 10:17 AM Gustavo A. R. Silva
wrote:
>
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warnings:
>
> drivers/mtd/devices/phram.c: In function ‘parse_num64’:
> drivers/mtd/devic
On Fri, Feb 8, 2019 at 10:12 AM Gustavo A. R. Silva
wrote:
>
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warnings:
>
> drivers/mtd/lpddr/lpddr_cmds.c: In function ‘chip_ready’:
> drivers/mtd/lpd
As part of Chrome OS's FAFT (Fully Automated Firmware Testing)
tests, we need to ensure that the H1 chip is properly setting
some GPIO lines. The h1_gpio attribute exposes the state
of the lines:
- ENTRY_TO_FACT_MODE in BIT(0)
- SPI_CHROME_SEL in BIT(1)
There are two reasons that I am exposing thi
On Wed, Apr 10, 2019 at 12:24 PM Matteo Croce wrote:
>
> On Wed, Apr 10, 2019 at 8:46 PM Kees Cook wrote:
> >
> > On Mon, Apr 8, 2019 at 3:09 PM Matteo Croce wrote:
> > >
> > > Use the shared variables for range check, instead of declaring a local one
> > > in every source file.
> >
> > I was ex
dma_mapping_error() was being called on a different device struct than
what was passed to map/unmap. Besides rendering the error checking
ineffective, it caused a debug splat with CONFIG_DMA_API_DEBUG.
Signed-off-by: Scott Wood
---
drivers/fpga/dfl-afu-dma-region.c | 2 +-
1 file changed, 1 ins
struct dfl_feature_platform_data (and it's mutex) is used
by both fme and port devices, and when lockdep is enabled it
complains about nesting between these locks. Tell lockdep about
the difference so it can track each class separately.
Here's the lockdep complaint:
[ 409.680668] WARNING: possib
On Wed, 10 Apr 2019, Vlastimil Babka wrote:
> On 4/10/19 4:47 AM, Tobin C. Harding wrote:
> > Recently a 2 year old bug was found in the SLAB allocator that crashes
> > the kernel. This seems to imply that not that many people are using the
> > SLAB allocator.
>
> AFAIK that bug required CONFIG_
On 4/10/2019 5:45 PM, Kees Cook wrote:
On Wed, Apr 10, 2019 at 2:26 PM Sinan Kaya wrote:
We can't seem to have a kernel with CONFIG_EXPERT set but
CONFIG_DEBUG_KERNEL unset these days.
While some of the features under the CONFIG_EXPERT require
CONFIG_DEBUG_KERNEL, it doesn't apply for all fea
Quoting Fabio Estevam (2019-03-22 09:24:54)
> Hi Abel,
>
> On Fri, Mar 22, 2019 at 12:37 PM Abel Vesa wrote:
> >
> > This work is part of the effort of switching the entire imx clock drivers
> > towards clk_hw based API. In order to do that, we have to keep the old
>
> Maybe I missed some earlie
On Wed, 10 Apr 2019, Al Viro wrote:
> Rather bad way to do it - generally, register_filesystem() should be
> the last thing done by initialization. Any modular code that
> does unregister_filesystem() on failure exit is flat-out broken;
> here it's not instantly FUBAR, but it's a bloody bad examp
On Wed, 2019-04-10 at 16:45 -0500, Bjorn Helgaas wrote:
> [+cc Keith, Jonathan (VMD guys)]
>
> I'm OK with this from a PCI perspective. It would be nice if
>
> dma_domain_list
> dma_domain_list_lock
> add_dma_domain()
> del_dma_domain()
> set_dma_domain_ops()
>
> could all be moved to
- On Apr 10, 2019, at 5:53 PM, Sinan Kaya ok...@kernel.org wrote:
> On 4/10/2019 5:45 PM, Kees Cook wrote:
>> On Wed, Apr 10, 2019 at 2:26 PM Sinan Kaya wrote:
>>>
>>> We can't seem to have a kernel with CONFIG_EXPERT set but
>>> CONFIG_DEBUG_KERNEL unset these days.
>>>
>>> While some of the
When compiling with -Wformat, clang warns:
fs/afs/flock.c:632:29: warning: format specifies type 'short' but the argument
has type
'unsigned char' [-Wformat]
_leave(" = %d [%hd]", ret, fl->fl_type);
~~~ ^~~
fl_type is declared as an unsigned c
On Wed, Apr 10, 2019 at 2:54 PM Sinan Kaya wrote:
>
> On 4/10/2019 5:45 PM, Kees Cook wrote:
> > On Wed, Apr 10, 2019 at 2:26 PM Sinan Kaya wrote:
> >>
> >> We can't seem to have a kernel with CONFIG_EXPERT set but
> >> CONFIG_DEBUG_KERNEL unset these days.
> >>
> >> While some of the features un
Hi Nicholas,
On Mon, Mar 11, 2019 at 04:23:23PM +, Nicholas Johnson wrote:
> Change block comments to accepted style with asterisks on each line.
>
> Justify block comments to 80-character limit to reduce the number of
> lines where possible.
Thanks for doing this; I do accept cleanup patche
As part of Chrome OS's FAFT (Fully Automated Firmware Testing)
tests, we need to ensure that the H1 chip is properly setting
some GPIO lines. The h1_gpio attribute exposes the state
of the lines:
- ENTRY_TO_FACT_MODE in BIT(0)
- SPI_CHROME_SEL in BIT(1)
There are two reasons that I am exposing thi
On Wed, Apr 10, 2019 at 3:04 PM Mathieu Desnoyers
wrote:
>
> - On Apr 10, 2019, at 5:53 PM, Sinan Kaya ok...@kernel.org wrote:
>
> > On 4/10/2019 5:45 PM, Kees Cook wrote:
> >> On Wed, Apr 10, 2019 at 2:26 PM Sinan Kaya wrote:
> >>>
> >>> We can't seem to have a kernel with CONFIG_EXPERT set
On Wed, 2019-04-10 at 12:54 -0700, Guenter Roeck wrote:
> A checkpatch rule suggesting that multiple extension lines can be merged
> might be useful to help finding such situations. Just a thought.
You are welcome to try to write that one.
It's likely not a trivial task to make it sensible.
cheer
Zdravstvujte Vas interesuyut klientskie bazy dannyh?
Hi ,
On 4/10/19 11:41 AM, Bjorn Helgaas wrote:
On Tue, Mar 19, 2019 at 01:47:29PM -0700,
sathyanarayanan.kuppusw...@linux.intel.com wrote:
From: Kuppuswamy Sathyanarayanan
As per PCI firmware specification v3.2 ECN
(https://members.pcisig.com/wg/PCI-SIG/document/12614), when firmware
owns Do
On Wed, Apr 10, 2019 at 1:13 PM Arnd Bergmann wrote:
>
> The purgatory and boot Makefiles do not inherit the original cflags,
> so clang falls back to the default target architecture when building it,
> typically this would be x86 when cross-compiling.
>
> Add $(CLANG_FLAGS) everywhere so we pass
Hi Joe,
On Wed, Apr 10, 2019 at 03:10:09PM -0700, Joe Perches wrote:
> On Wed, 2019-04-10 at 12:54 -0700, Guenter Roeck wrote:
> > A checkpatch rule suggesting that multiple extension lines can be merged
> > might be useful to help finding such situations. Just a thought.
>
> You are welcome to t
Stop enabling the oscillator and removing the oscillator failure flags in
probe. Instead, return -EINVAL in .read_time when the oscillaotr is not
start or when it failed at some point. The oscillator gets enabled on the
first .set_time after failure and the failure flags are cleared.
This also rem
On 4/10/2019 6:04 PM, Kees Cook wrote:
I don't want any of the debug features in my kernel but still
need all the expert features. My kernel is considered a production
kernel. I don't really want to ship all the good debug enables.
Production kernels enable it. e.g. Ubuntu:
$ grep '\bCONFIG_DE
On 4/10/2019 3:45 PM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-04-10 12:39:16)
On 4/10/2019 10:53 AM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-04-08 14:46:11)
On 4/4/2019 3:53 PM, Stephen Boyd wrote:
In some circumstances drivers register clks early and don't have access
to a stru
On Mon, Apr 8, 2019 at 3:09 PM Matteo Croce wrote:
>
> In the sysctl code the proc_dointvec_minmax() function is often used to
> validate the user supplied value between an allowed range. This function
> uses the extra1 and extra2 members from struct ctl_table as minimum and
> maximum allowed valu
On Wed, Apr 10, 2019 at 1:13 PM Arnd Bergmann wrote:
>
> llvm does does not understand -march=z9-109 and older target
Please file bugs for these in LLVM's issue tracker. It might be
possible to enable these additional architecture variants if they're
similar to existing ones and simply unrecogni
It has been observed, that highly-threaded, non-cpu-bound applications
running under cpu.cfs_quota_us constraints can hit a high percentage of
periods throttled while simultaneously not consuming the allocated
amount of quota. This use case is typical of user-interactive non-cpu
bound web services
The following patch is an implementation of option 2 from my earlier e-mail.
Option #2 was the removal of all runtime_expires and related slice expiration
logic.
This is a very early iteration of this patch, and testing/comments are very
appreciated.
Thanks,
Dave.
On Wed, Apr 10, 2019 at 3:18 PM Sinan Kaya wrote:
>
> On 4/10/2019 6:04 PM, Kees Cook wrote:
>
> >> I don't want any of the debug features in my kernel but still
> >> need all the expert features. My kernel is considered a production
> >> kernel. I don't really want to ship all the good debug enab
On Wed, Apr 10, 2019 at 12:14:55PM +0200, David Hildenbrand wrote:
>While current node handling is probably terribly broken for memory block
>devices that span several nodes (only possible when added during boot,
>and something like that should be blocked completely), properly put the
>device refer
On 4/10/2019 6:21 PM, Kees Cook wrote:
I can go after individual enables if you agree assuming Mathieu will
go after the changes in the other email. Let me know otherwise.
How about you split it, but make DEBUG_KERNEL be "default EXPERT" that
way enabling EXPERT will enable DEBUG_KERNEL still in
On Wed, Apr 10, 2019 at 3:03 PM Louis Taylor wrote:
>
> When compiling with -Wformat, clang warns:
>
> fs/afs/flock.c:632:29: warning: format specifies type 'short' but the
> argument has type
> 'unsigned char' [-Wformat]
> _leave(" = %d [%hd]", ret, fl->fl_type);
>
On Wed, Apr 10, 2019 at 3:25 PM Sinan Kaya wrote:
>
> On 4/10/2019 6:21 PM, Kees Cook wrote:
> >> I can go after individual enables if you agree assuming Mathieu will
> >> go after the changes in the other email. Let me know otherwise.
> > How about you split it, but make DEBUG_KERNEL be "default
On 4/10/2019 6:28 PM, Kees Cook wrote:
diff --git a/init/Kconfig b/init/Kconfig
index c9386a365eea..7ce4a60ab3e9 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -1188,8 +1188,6 @@ config BPF
menuconfig EXPERT
bool "Configure standard kernel features (expert users)"
- # Unhide de
On Wed, Apr 10, 2019 at 11:51 PM Kees Cook wrote:
>
> On Wed, Apr 10, 2019 at 12:24 PM Matteo Croce wrote:
> >
> > On Wed, Apr 10, 2019 at 8:46 PM Kees Cook wrote:
> > >
> > > On Mon, Apr 8, 2019 at 3:09 PM Matteo Croce wrote:
> > > >
> > > > Use the shared variables for range check, instead of
On Wed, Apr 10, 2019 at 3:30 PM Matteo Croce wrote:
>
> On Wed, Apr 10, 2019 at 11:51 PM Kees Cook wrote:
> >
> > On Wed, Apr 10, 2019 at 12:24 PM Matteo Croce wrote:
> > >
> > > On Wed, Apr 10, 2019 at 8:46 PM Kees Cook wrote:
> > > >
> > > > On Mon, Apr 8, 2019 at 3:09 PM Matteo Croce wrote:
When compiling with -Wformat, clang warns:
fs/afs/flock.c:632:29: warning: format specifies type 'short' but the argument
has type
'unsigned char' [-Wformat]
_leave(" = %d [%hd]", ret, fl->fl_type);
~~~ ^~~
fs/afs/dir.c:138:11: warning: format
We can't seem to have a kernel with CONFIG_EXPERT set but
CONFIG_DEBUG_KERNEL unset these days.
While some of the features under the CONFIG_EXPERT require
CONFIG_DEBUG_KERNEL, it doesn't apply for all features.
It looks like CONFIG_KALLSYMS_ALL is the only feature that
requires CONFIG_DEBUG_KERNE
The TLB flush counters under vmstat seems to be very helpful while
debugging TLB flush performance in RISC-V.
Update the counters in every TLB flush methods respectively.
Signed-off-by: Atish Patra
---
arch/riscv/include/asm/tlbflush.h | 5 +
arch/riscv/mm/tlbflush.c | 12
The TLB flush counters under vmstat seems to be very helpful while
debugging TLB flush performance in RISC-V.
Add the Kconfig option only for debug kernels.
Signed-off-by: Atish Patra
---
arch/riscv/Kconfig.debug | 12
1 file changed, 12 insertions(+)
diff --git a/arch/riscv/Kconf
CONFIG_DEBUG_TLBFLUSH was added in 'commit 3df3212f9722 ("x86/tlb: add
tlb_flushall_shift knob into debugfs")' to support tlb_flushall_shift
knob. The knob was removed in 'commit e9f4e0a9fe27 ("x86/mm: Rip out
complicated, out-of-date, buggy TLB flushing")'. However, the debug
option was never rem
The RISC-V patch (2/3) is based on Gary's TLB flush patch series
https://patchwork.kernel.org/project/linux-riscv/list/?series=97315
The x86 kconfig fix patch(1/3) can be applied separately.
Atish Patra (3):
x86: Update DEBUG_TLBFLUSH options description.
RISC-V: Update tlb flush counters
RISC-V
On 3/20/19 4:48 PM, Atish Patra wrote:
The cpu-map DT entry in ARM can describe the CPU topology in much better
way compared to other existing approaches. RISC-V can easily adopt this
binding to represent its own CPU topology. Thus, both cpu-map DT
binding and topology parsing code can be moved t
Boot on AC is a policy which makes the device boot from S5 when AC
power is connected. This is useful for users who want to run their
device headless or with a dock.
v2 changes:
- Move documentation to Documentation/ABI/testing/sysfs-platform-wilco-ec
Signed-off-by: Nick Crews
---
.../ABI/testi
On Mon, Mar 11, 2019 at 04:23:55PM +, Nicholas Johnson wrote:
> Add new kernel parameters:
> - hp_io_size=nn
> - hp_mmio_size=nnM
> - hp_mmio_pref_size=nnM
>
> Depreciate old kernel parameters and print warning when used:
> - hpiosize=nn
> - hpmemsize=nn
On Wed, Apr 10, 2019 at 3:41 PM Louis Taylor wrote:
>
> When compiling with -Wformat, clang warns:
>
> fs/afs/flock.c:632:29: warning: format specifies type 'short' but the
> argument has type
> 'unsigned char' [-Wformat]
> _leave(" = %d [%hd]", ret, fl->fl_type);
>
USB PowerShare is a policy which affects charging via the special
USB PowerShare port (marked with a small lightning bolt or battery icon)
when in low power states:
- In S0, the port will always provide power.
- In S0ix, if power_share is enabled, then power will be supplied to
the port when on A
Quoting Nicholas Mc Guire (2019-04-06 20:13:24)
> Providing a range for usleep_range() allows the hrtimer subsystem to
> coalesce timers - the delay is runtime configurable so a factor 2
> is taken to provide the range.
>
> Signed-off-by: Nicholas Mc Guire
> ---
I think this driver is in mainten
On Thu, Apr 11, 2019 at 12:34 AM Kees Cook wrote:
>
> On Wed, Apr 10, 2019 at 3:30 PM Matteo Croce wrote:
> >
> > FYI, this are the stats from my local repo, just to let you the size
> > of a series with all the changes in it:
> >
> > $ git --no-pager log --stat --oneline linus/master
> > 2 file
On Thu, Mar 14, 2019 at 04:04:52PM -0400, Kimberly Brown wrote:
This patchset fixes a race condition in the "_show" functions that
access the channel ring buffers.
Changes in v3:
Patch 1: Drivers: hv: vmbus: Refactor chan->state if statement
- Added the “reviewed-by” line from v2.
Patch 2: Driv
On Wed, Apr 10, 2019 at 3:54 PM Matteo Croce wrote:
>
> On Thu, Apr 11, 2019 at 12:34 AM Kees Cook wrote:
> >
> > On Wed, Apr 10, 2019 at 3:30 PM Matteo Croce wrote:
> > >
> > > FYI, this are the stats from my local repo, just to let you the size
> > > of a series with all the changes in it:
> >
On Thu, Mar 7, 2019 at 7:43 AM Dan Williams wrote:
>
> On Thu, Mar 7, 2019 at 1:17 AM Guillaume Tucker
> wrote:
> >
> > On 06/03/2019 14:05, Mike Rapoport wrote:
> > > On Wed, Mar 06, 2019 at 10:14:47AM +, Guillaume Tucker wrote:
> > >> On 01/03/2019 23:23, Dan Williams wrote:
> > >>> On Fri,
LKML
http://chanathleticassociationbaseball.assn.la/Goto.asp?URL=https://bit.ly/2KAzcan&AssocID=12781
Mark Underwood
--
Importance is one of the most important of our illusions. - Herbert Salzer
On Wed, 2019-04-10 at 23:03 +0100, Louis Taylor wrote:
> When compiling with -Wformat, clang warns:
>
> fs/afs/flock.c:632:29: warning: format specifies type 'short' but the
> argument has type
> 'unsigned char' [-Wformat]
> _leave(" = %d [%hd]", ret, fl->fl_type);
I really think t
If nr_cpus command line option is set, maximum possible cpu should be
set to that value.
Signed-off-by: Atish Patra
---
arch/riscv/kernel/smpboot. | 0
arch/riscv/kernel/smpboot.c | 10 +-
2 files changed, 9 insertions(+), 1 deletion(-)
create mode 100644 arch/riscv/kernel/smpboot.
d
OF/DT core has a hook for architecture specific logical cpuid to hartid
mapping. By implementing this, we can pass the logical cpu id to cpu
node parsing functions.
Signed-off-by: Atish Patra
---
arch/riscv/kernel/smp.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/riscv/kernel/s
nosmp command line option sets max_cpus to zero. No secondary harts
will boot if this is enabled. But present cpu mask will still point to
all possible masks.
Fix present cpu mask for nosmp usecase.
Signed-off-by: Atish Patra
---
arch/riscv/kernel/smpboot.c | 12 +++-
1 file changed, 11
Assorted command line option fixes for RISC-V.
Changes from v1->v2.
1. Update pr_err string in patch (4/4) as per review.
Atish Patra (4):
RISC-V: Add RISC-V specific arch_match_cpu_phys_id
RISC-V: Fix of_get_cpu_node usage
RISC-V: Implement nosmp commandline option.
RISC-V: Support nr_cpus comma
of_get_cpu_node expects a logical cpu id not a hartid.
Signed-off-by: Atish Patra
---
arch/riscv/kernel/cpu.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/riscv/kernel/cpu.c b/arch/riscv/kernel/cpu.c
index cf2fca12414a..c8d2a3223099 100644
--- a/arch/riscv/kernel/cp
On Wed, Apr 10, 2019 at 3:42 PM Sinan Kaya wrote:
>
> We can't seem to have a kernel with CONFIG_EXPERT set but
> CONFIG_DEBUG_KERNEL unset these days.
>
> While some of the features under the CONFIG_EXPERT require
> CONFIG_DEBUG_KERNEL, it doesn't apply for all features.
>
> It looks like CONFIG_
On Wed, Apr 10, 2019 at 03:12:05PM -0700, sathyanarayanan kuppuswamy wrote:
> On 4/10/19 11:41 AM, Bjorn Helgaas wrote:
> > On Tue, Mar 19, 2019 at 01:47:29PM -0700,
> > sathyanarayanan.kuppusw...@linux.intel.com wrote:
> > > From: Kuppuswamy Sathyanarayanan
> > >
> > >
> > > As per PCI firmwar
From: Mian Yousaf Kaukab
Enable CPU vulnerabilty show functions for spectre_v1, spectre_v2,
meltdown and store-bypass.
Signed-off-by: Mian Yousaf Kaukab
Signed-off-by: Jeremy Linton
Reviewed-by: Andre Przywara
Reviewed-by: Catalin Marinas
Tested-by: Stefan Wahren
---
arch/arm64/Kconfig | 1
Return status based on ssbd_state and the arm64 SSBS feature. If
the mitigation is disabled, or the firmware isn't responding then
return the expected machine state based on a whitelist of known
good cores.
Given a heterogeneous machine, the overall machine vulnerability
must be a tristate to assu
From: Marc Zyngier
The SMCCC ARCH_WORKAROUND_1 service can indicate that although the
firmware knows about the Spectre-v2 mitigation, this particular
CPU is not vulnerable, and it is thus not necessary to call
the firmware on this CPU.
Let's use this information to our benefit.
Signed-off-by: M
There are various reasons, including bencmarking, to disable spectrev2
mitigation on a machine. Provide a command-line to do so.
Signed-off-by: Jeremy Linton
Reviewed-by: Suzuki K Poulose
Reviewed-by: Andre Przywara
Reviewed-by: Catalin Marinas
Tested-by: Stefan Wahren
Cc: Jonathan Corbet
Cc
Add code to track whether all the cores in the machine are
vulnerable, and whether all the vulnerable cores have been
mitigated.
Once we have that information we can add the sysfs stub and
provide an accurate view of what is known about the machine.
Signed-off-by: Jeremy Linton
Reviewed-by: Andr
The common ARM architecture code provides a generic function to exit
coherency called v7_exit_coherency_flush(). Replace the machine
specific implementation using the generic function.
Tested on a i.MX 6Dual by hotplugging the secondary CPU under load
through sysfs several 1000 times.
Tested-by:
From: Marc Zyngier
We currently have a list of CPUs affected by Spectre-v2, for which
we check that the firmware implements ARCH_WORKAROUND_1. It turns
out that not all firmwares do implement the required mitigation,
and that we fail to let the user know about it.
Instead, let's slightly revamp
The ssb detection logic is necessary regardless of whether
the vulnerability mitigation code is built into the kernel.
Break it out so that the CONFIG option only controls the
mitigation logic and not the vulnerability detection.
Signed-off-by: Jeremy Linton
Reviewed-by: Andre Przywara
Reviewed-
601 - 700 of 869 matches
Mail list logo
