KASAN uses compiler instrumentation to intercept all memory accesses. But it
does
not see memory accesses done in assembly code. One notable user of assembly code
is atomic operations. Frequently, for example, an atomic reference decrement is
the last access to an object and a good candidate for a
On Mon, Jan 29, 2018 at 08:46:03AM +, David Woodhouse wrote:
> On Sun, 2018-01-28 at 16:39 -0800, Liran Alon wrote:
> >
> > Windows use IBRS and Microsoft don't have any plans to switch to retpoline.
> > Running a Windows guest should be a pretty common use-case no?
> >
> > In addition, your
KASAN uses compiler instrumentation to intercept all memory accesses.
But it does not see memory accesses done in assembly code.
One notable user of assembly code is atomic operations. Frequently,
for example, an atomic reference decrement is the last access to an
object and a good candidate for a
Replace my codeaurora.org address with my kernel.org address so
that emails don't bounce.
Signed-off-by: Stephen Boyd
---
MAINTAINERS | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index c90687ec8fc6..35b26c121bc2 100644
--- a/MAINTAINERS
++
The following changes since commit b2cd1df66037e7c4697c7e40496bf7e4a5e16a2d:
Linux 4.15-rc7 (2018-01-07 14:22:41 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
tags/regmap-v4.16
for you to fetch changes up to a75de77211842a
From: Jason Wang
Date: Thu, 25 Jan 2018 22:03:52 +0800
> We don't stop device before reset owner, this means we could try to
> serve any virtqueue kick before reset dev->worker. This will result a
> warn since the work was pending at llist during owner resetting. Fix
> this by stopping device dur
On 27.01.2018 at 09:37, Peter Rosin wrote:
> On 2018-01-26 17:33, Adrian Fiergolski wrote:
>> Hi Peter,
>>
>> Sorry for the late reply.
> No problem.
>
>> Yes, it's true I have one of the chip. However, my yocto based build system
>> depends on https://github.com/Xilinx/linux-xlnx and it's in versi
Ingo/Peter/Thomas,
can you comment on this? I'd like to get this moving one way or
another, rather than just hold it back forever.
I _think_ all the concerns were resolved, no?
Linus
On Tue, Jan 23, 2018 at 7:57 AM, Mathieu Desnoyers
wrote:
> Hi Ingo, Peter, Thomas,
>
> Here is t
Hi Mimi,
On Mon, Jan 29, 2018 at 5:33 PM, Mimi Zohar wrote:
> Hi Alban,
>
> On Thu, 2018-01-25 at 06:56 -0500, Mimi Zohar wrote:
>> > > @@ -228,9 +229,28 @@ static int process_measurement(struct file *file,
>> > > char *buf, loff_t size,
>> > >IMA_APPRAISE_SUBMASK | I
On Fri, Jan 26, 2018 at 10:19:47AM +, David Woodhouse wrote:
> On Tue, 2018-01-23 at 16:25 +0100, Peter Zijlstra wrote:
> > Annotate the indirect calls/jumps in the CALL_NOSPEC/JUMP_NOSPEC
> > alternatives.
> >
> >
> > Signed-off-by: Peter Zijlstra (Intel)
>
> Reviewed-by: David Woodhouse
ARM has recently published a SMC Calling Convention (SMCCC)
specification update[1] that provides an optimised calling convention
and optional, discoverable support for mitigating CVE-2017-5715. ARM
Trusted Firmware (ATF) has already gained such an implementation[2].
This series addresses a few th
Instead of open coding the accesses to the various registers,
let's add explicit SMCCC accessors.
Signed-off-by: Marc Zyngier
---
virt/kvm/arm/psci.c | 52 ++--
1 file changed, 42 insertions(+), 10 deletions(-)
diff --git a/virt/kvm/arm/psci.c b/v
As we're about to update the PSCI support, and because I'm lazy,
let's move the PSCI include file to include/kvm so that both
ARM architectures can find it.
Signed-off-by: Marc Zyngier
---
arch/arm/include/asm/kvm_psci.h| 27 --
arch/arm/kvm/handle_exit.c
The new SMC Calling Convention (v1.1) allows for a reduced overhead
when calling into the firmware, and provides a new feature discovery
mechanism.
Make it visible to KVM guests.
Signed-off-by: Marc Zyngier
---
Documentation/virtual/kvm/arm/psci.txt | 12 +++-
arch/arm/kvm/handle_exit.c
PSCI 1.0 can be trivially implemented by having PSCI 0.2 and
the FEATURES call. Of, and returning 1.0 as the PSCI version.
We happily ignore everything else, as it is optional.
Signed-off-by: Marc Zyngier
---
include/kvm/arm_psci.h | 1 +
virt/kvm/arm/psci.c| 43 +++
As we're about to trigger a PSCI version explosion, it doesn't
hurt to introduce a PSCI_VERSION helper that is going to be
used everywhere.
Signed-off-by: Marc Zyngier
---
include/kvm/arm_psci.h | 5 +++--
virt/kvm/arm/psci.c| 2 +-
2 files changed, 4 insertions(+), 3 deletions(-)
diff --gi
A new feature of SMCCC 1.1 is that it offers firmware-based CPU
workarounds. In particular, SMCCC_ARCH_WORKAROUND_1 provides
BP hardening for CVE-2017-5715.
If the host has some mitigation for this issue, report that
we deal with it using SMCCC_ARCH_WORKAROUND_1, as we apply the
host workaround on
We're about to need kvm_psci_version in HYP too. So let's turn it
into a static inline, and pass the kvm structure as a second
parameter (so that HYP can do a kern_hyp_va on it).
Signed-off-by: Marc Zyngier
---
arch/arm64/kvm/hyp/switch.c | 20
include/kvm/arm_psci.h |
Although we've implemented PSCI 1.0 and 1.1, nothing can select them
Since all the new PSCI versions are backward compatible, we decide to
default to the latest version of the PSCI implementation. This is no
different from doing a firmware upgrade on KVM.
But in order to give a chance to hypotheti
KVM doesn't follow the SMCCC when it comes to unimplemented calls,
and inject an UNDEF instead of returning an error. Since firmware
calls are now used for security mitigation, they are becoming more
common, and the undef is counter productive.
Instead, let's follow the SMCCC which states that -1
KVM doesn't follow the SMCCC when it comes to unimplemented calls,
and inject an UNDEF instead of returning an error. Since firmware
calls are now used for security mitigation, they are becoming more
common, and the undef is counter productive.
Instead, let's follow the SMCCC which states that -1
The following changes since commit
50c4c4e268a2d7a3e58ebb698ac74da0de40ae36:
Linux 4.15-rc3 (2017-12-10 17:56:26 -0800)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-4.16
for you to fetch changes up to ae17a87dd7c79fa742ef5dcf06d1095eec4e1925:
linux-next:
On Fri, Jan 26, 2018 at 10:37:30AM +, David Woodhouse wrote:
> On Tue, 2018-01-23 at 16:25 +0100, Peter Zijlstra wrote:
> > This is boot code, we run this _way_ before userspace comes along to
> > poison our branch predictor.
>
> Hm, objtool knows about sections, doesn't it? Why it is whining
On Mon, Jan 29, 2018 at 06:49:52PM +0100, Peter Zijlstra wrote:
> On Fri, Jan 26, 2018 at 10:37:30AM +, David Woodhouse wrote:
> > On Tue, 2018-01-23 at 16:25 +0100, Peter Zijlstra wrote:
> > > This is boot code, we run this _way_ before userspace comes along to
> > > poison our branch predicto
From: Michael Kelley
The 2016 version of Hyper-V offers the option to operate the guest VM
per-vcpu stimer's in Direct Mode, which means the timer interupts on its
own vector rather than queueing a VMbus message. Direct Mode reduces
timer processing overhead in both the hypervisor and the guest,
Function identifiers are a 32bit, unsigned quantity. But we never
tell so to the compiler, resulting in the following:
4ac: b26187e0mov x0, #0x8001
We thus rely on the firmware narrowing it for us, which is not
always a reasonable expectation.
Cc: sta...@vger.kernel.or
On Mon, Jan 29, 2018 at 05:45:55PM +, Marc Zyngier wrote:
> In order to call into the firmware to apply workarounds, it is
> useful to find out whether we're using HVC or SMC. Let's expose
> this through the psci_ops.
>
> Signed-off-by: Marc Zyngier
> ---
> drivers/firmware/psci.c | 28 +
We want SMCCC_ARCH_WORKAROUND_1 to be fast. As fast as possible.
So let's intercept it as early as we can by testing for the
function call number as soon as we've identified a HVC call
coming from the guest.
Signed-off-by: Marc Zyngier
---
arch/arm64/kvm/hyp/hyp-entry.S | 20 ++--
Since PSCI 1.0 allows the SMCCC version to be (indirectly) probed,
let's do that at boot time, and expose the version of the calling
convention as part of the psci_ops structure.
Signed-off-by: Marc Zyngier
---
drivers/firmware/psci.c | 21 +
include/linux/psci.h| 6
Add the detection and runtime code for ARM_SMCCC_ARCH_WORKAROUND_1.
It is lovely. Really.
Signed-off-by: Marc Zyngier
---
arch/arm64/include/asm/kvm_psci.h | 63
arch/arm64/kernel/bpi.S | 20
arch/arm64/kernel/cpu_errata.c| 68 +
In order to call into the firmware to apply workarounds, it is
useful to find out whether we're using HVC or SMC. Let's expose
this through the psci_ops.
Signed-off-by: Marc Zyngier
---
drivers/firmware/psci.c | 28 +++-
include/linux/psci.h| 7 +++
2 files chang
One of the major improvement of SMCCC v1.1 is that it only clobbers
the first 4 registers, both on 32 and 64bit. This means that it
becomes very easy to provide an inline version of the SMC call
primitive, and avoid performing a function call to stash the
registers that would otherwise be clobbered
On Sun, Jan 28, 2018 at 09:17:53PM +, Winkler, Tomas wrote:
> > I think if a driver can fail reliquish then it needs some kind of strategy
> > to
> > recover.
> Maybe some driver can and some not, but if it doesn't succeed it
> should return an error.
But you can't just leave the driver in
On Tue, Jan 23, 2018 at 04:25:42PM +0100, Peter Zijlstra wrote:
> Paravirt emits indirect calls which get flagged by objtool retpoline
> checks, annotate it away because all these indirect calls will be
> patched out before we start userspace.
>
> Signed-off-by: Peter Zijlstra (Intel)
> ---
> ar
On Fri, Jan 19, 2018 at 05:42:29PM +0100, Peter Zijlstra wrote:
> Josh, how would you feel about adding the bits required to make objtool
> a full disassembler? That would make it far easier to visualse the state
> and I don't think its _that_ much more, all the difficult bits are
> already done af
On Tue, Jan 23, 2018 at 10:57:30AM -0500, Mathieu Desnoyers wrote:
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index f38c4c7e256a..041893128f51 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -2662,9 +2662,13 @@ static struct rq *finish_task_switch(struct
> task_
On Wed, Jan 17, 2018 at 09:14:15PM +0100, Jernej Skrabec wrote:
> This commit adds all necessary compatibles and descriptions needed to
> implement A83T HDMI pipeline.
>
> Mixer is already properly described, so only compatible is added.
>
> However, A83T TV TCON, which is connected to HDMI, does
On 01/29/2018 01:54 AM, Michal Hocko wrote:
> On Mon 29-01-18 06:30:55, Naoya Horiguchi wrote:
>> My apology, I forgot to CC to the mailing lists.
>>
>> On Mon, Jan 29, 2018 at 03:28:03PM +0900, Naoya Horiguchi wrote:
>>> Recently the following BUG was reported:
>>>
>>> Injecting memory failure
于 2018年1月30日 GMT+08:00 上午2:05:26, Rob Herring 写到:
>On Wed, Jan 17, 2018 at 09:14:15PM +0100, Jernej Skrabec wrote:
>> This commit adds all necessary compatibles and descriptions needed to
>> implement A83T HDMI pipeline.
>>
>> Mixer is already properly described, so only compatible is added.
>>
On Mon, 2018-01-29 at 11:58 -0600, Josh Poimboeuf wrote:
> On Tue, Jan 23, 2018 at 04:25:42PM +0100, Peter Zijlstra wrote:
> >
> > Paravirt emits indirect calls which get flagged by objtool
> > retpoline
> > checks, annotate it away because all these indirect calls will be
> > patched out before w
On Mon, Jan 29, 2018 at 07:04:14PM +0100, Peter Zijlstra wrote:
> On Tue, Jan 23, 2018 at 10:57:30AM -0500, Mathieu Desnoyers wrote:
> > diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> > index f38c4c7e256a..041893128f51 100644
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> >
On 01/29/18 08:37, Andy Lutomirski wrote:
>
> That's what I thought, too, and the SDM does say that, but the SDM
> says all kinds of not-quite-correct things about segmentation.
>
>> It is pretty much scratch space (I have
>> suggested using it for the gsbase once all those issues get sorted out,
On Mon, Jan 29, 2018 at 11:58:58AM -0600, Josh Poimboeuf wrote:
> On Tue, Jan 23, 2018 at 04:25:42PM +0100, Peter Zijlstra wrote:
> > Paravirt emits indirect calls which get flagged by objtool retpoline
> > checks, annotate it away because all these indirect calls will be
> > patched out before we
Scenarios:
[1] Cache size 1024 + early cache build up [Small change in your cache
patch,
see the patch below]
[2] Hash 64 approach[my original v2 patch]
[3] Cache size 64
[4] Cache size 128
[5] Cache size 256
[6] Base build
Result (boot to shell in sec):
[1] 14.292498 14.370994 14.313537 -
On Thu, Jan 25, 2018 at 04:37:48PM -0800, Eric Biggers wrote:
> On Thu, Jan 18, 2018 at 01:13:59PM +, André Draszik wrote:
> > -static int validate_user_key(struct fscrypt_info *crypt_info,
> > +static inline struct key *fscrypt_get_encrypted_key(const char
> > *description)
> > +{
> > + if
Signed-off-by: Ildar Ismagilov
---
kernel/rcu/srcutree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c
index 6d5880089ff6..1798d1aa60fa 100644
--- a/kernel/rcu/srcutree.c
+++ b/kernel/rcu/srcutree.c
@@ -599,7 +599,7 @@ static voi
On Mon, Jan 29, 2018 at 12:01:05PM -0600, Josh Poimboeuf wrote:
> On Fri, Jan 19, 2018 at 05:42:29PM +0100, Peter Zijlstra wrote:
> > Josh, how would you feel about adding the bits required to make objtool
> > a full disassembler? That would make it far easier to visualse the state
> > and I don't
On Mon 29-01-18 17:57:22, Florian Westphal wrote:
> Kirill A. Shutemov wrote:
> > On Mon, Jan 29, 2018 at 08:23:57AM +0100, Florian Westphal wrote:
> > > > vmalloc() once became killable by commit 5d17a73a2ebeb8d1 ("vmalloc:
> > > > back
> > > > off when the current task is killed") but then beca
> On Jan 29, 2018, at 10:12 AM, H. Peter Anvin wrote:
>
>> On 01/29/18 08:37, Andy Lutomirski wrote:
>>
>> That's what I thought, too, and the SDM does say that, but the SDM
>> says all kinds of not-quite-correct things about segmentation.
>>
>>> It is pretty much scratch space (I have
>>> su
On Mon, Jan 29, 2018 at 05:57:22PM +0100, Florian Westphal wrote:
> Kirill A. Shutemov wrote:
> > On Mon, Jan 29, 2018 at 08:23:57AM +0100, Florian Westphal wrote:
> > > > vmalloc() once became killable by commit 5d17a73a2ebeb8d1 ("vmalloc:
> > > > back
> > > > off when the current task is killed
On Monday 2018-01-29 17:57, Florian Westphal wrote:
>> > > vmalloc() once became killable by commit 5d17a73a2ebeb8d1 ("vmalloc: back
>> > > off when the current task is killed") but then became unkillable by
>> > > commit
>> > > b8c8a338f75e052d ("Revert "vmalloc: back off when the current task i
On 01/29/18 10:26, Andy Lutomirski wrote:
>>>
>>> That will utterly suck on non-UMIP machines that have
>>> hypervisor-provided UMIP emulation.
>>
>> Is that a valid thing to optimize for, especially given that paranoid
>> entries aren't the most common anyway?
>
> A bunch of people seem to care a
- On Jan 29, 2018, at 1:15 PM, Peter Zijlstra pet...@infradead.org wrote:
> On Mon, Jan 29, 2018 at 07:04:14PM +0100, Peter Zijlstra wrote:
>> On Tue, Jan 23, 2018 at 10:57:30AM -0500, Mathieu Desnoyers wrote:
>> > diff --git a/kernel/sched/core.c b/kernel/sched/core.c
>> > index f38c4c7e256a.
-0800)
are available in the git repository at:
git://github.com/jcmvbkbc/linux-xtensa.git tags/xtensa-20180129
for you to fetch changes up to ca47480921587ae30417dd234a9f79af188e3666:
xtensa: fix futex_atomic_cmpxchg_inatomic (2018-01-05 15:55:59
On Tue, Jan 23, 2018 at 04:25:42PM +0100, Peter Zijlstra wrote:
> Paravirt emits indirect calls which get flagged by objtool retpoline
> checks, annotate it away because all these indirect calls will be
> patched out before we start userspace.
There's one condition where this isn't true: the 'nore
On Mon, Jan 29, 2018 at 05:45:56PM +, Marc Zyngier wrote:
> Since PSCI 1.0 allows the SMCCC version to be (indirectly) probed,
> let's do that at boot time, and expose the version of the calling
> convention as part of the psci_ops structure.
>
> Signed-off-by: Marc Zyngier
> ---
> drivers/f
On Mon, Jan 29, 2018 at 08:33:19PM +0900, Andi Shyti wrote:
> '__packed' is not used anywhere, remove it.
Umm, this is not a variable, this is type annotation meaning that the
structure is packed. Still not needed, as we are not using anything but
u8 data elements, but justification is completely
On Mon, Jan 29, 2018 at 02:50:10AM +0800, kbuild test robot wrote:
> From: Fengguang Wu
>
> fs/btrfs/volumes.c:742:10-17: WARNING: ERR_CAST can be used with fs_devices
>
>
> Use ERR_CAST inlined function instead of ERR_PTR(PTR_ERR(...))
>
> Generated by: scripts/coccinelle/api/err_cast.cocci
On Sun, Jan 28, 2018 at 11:29 AM, KarimAllah Ahmed wrote:
> Add direct access to MSR_IA32_SPEC_CTRL for guests. This is needed for guests
> that will only mitigate Spectre V2 through IBRS+IBPB and will not be using a
> retpoline+IBPB based approach.
>
> To avoid the overhead of atomically saving a
On 01/24/2018 09:25 AM, Vincent Guittot wrote:
Hi,
Le Thursday 18 Jan 2018 à 10:38:07 (+), Morten Rasmussen a écrit :
On Mon, Jan 15, 2018 at 09:26:09AM +0100, Vincent Guittot wrote:
Le Wednesday 03 Jan 2018 à 10:16:00 (+0100), Vincent Guittot a écrit :
[...]
Hi Peter,
With the patch
On Sun, Jan 28, 2018 at 05:56:29AM -0800, Joe Perches wrote:
commit 321737416c72d ("tty: serial: msm: Move header file into driver")
removed the .h file, update the patterns.
Signed-off-by: Joe Perches
cc: Stephen Boyd
cc: Andy Gross
cc: David Brown
---
MAINTAINERS | 1 -
1 file changed, 1 de
On Wed 24-01-18 15:35:45, Eugeniu Rosca wrote:
[...]
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 76c9688b6a0a..4a3d5936a9a0 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -5344,14 +5344,12 @@ void __meminit memmap_init_zone(unsigned long size,
> int nid, unsigned long zon
On Thu, Jan 18, 2018 at 03:49:39PM +0100, gabriel.fernan...@st.com wrote:
> From: Gabriel Fernandez
>
> Update of END_PRIMARY_CLK was missed, it should be after CLK_SYSCLK
> hsi and sysclk are overwritten by gpioa and gpiob.
>
> Signed-off-by: Gabriel Fernandez
> ---
> include/dt-bindings/cloc
Why should this MSR be pass-through? I doubt that it would be accessed
frequently.
On Sun, Jan 28, 2018 at 4:58 PM, KarimAllah Ahmed wrote:
> Add direct access to MSR_IA32_SPEC_CTRL for guests. Future intel processors
> will use this MSR to indicate RDCL_NO (bit 0) and IBRS_ALL (bit 1).
>
> Cc: A
On Thu, Jan 18, 2018 at 03:49:40PM +0100, gabriel.fernan...@st.com wrote:
> From: Gabriel Fernandez
>
> This patch adds DSI clock for STM32F469 board
>
> Signed-off-by: Gabriel Fernandez
> ---
> drivers/clk/clk-stm32f4.c | 11 ++-
> include/dt-bindings/clock/stm32fx-clo
On Mon, Jan 29, 2018 at 08:33:20PM +0900, Andi Shyti wrote:
> Signed-off-by: Andi Shyti
But why?
> ---
> drivers/input/touchscreen/mms114.c | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/input/touchscreen/mms114.c
> b/drivers/input/touchscreen/mms1
On Sat, Jan 27, 2018 at 6:35 PM, Marco Martin wrote:
> Some laptops such as Dell Inspiron 7000 series have the
> tablet mode switch implemented in Intel ACPI,
> the events to enter and exit the tablet mode are 0xCC and 0xCD
>
It doesn't apply :-(
> CC: platform-driver-...@vger.kernel.org
> CC: M
On 01/29/2018 07:55 PM, Jim Mattson wrote:
Why should this MSR be pass-through? I doubt that it would be accessed
frequently.
True. Will update it to be emulated and allow user-space to set the
value exposed.
On Sun, Jan 28, 2018 at 4:58 PM, KarimAllah Ahmed wrote:
Add direct access to M
On Sun, Jan 28, 2018 at 4:58 PM, KarimAllah Ahmed wrote:
> Cc: Paolo Bonzini
> Cc: Radim Krčmář
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: H. Peter Anvin
> Cc: x...@kernel.org
> Cc: k...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: KarimAllah Ahmed
> ---
> arch/x86
On Mon, Jan 29, 2018 at 08:33:17PM +0900, Andi Shyti wrote:
> The 'mms114_read_reg' and 'mms114_write_reg' are used when
> reading or writing to the 'MMS114_MODE_CONTROL' register for
> updating the 'cache_mode_control' variable.
>
> Update the 'cache_mode_control' variable in the calling
> mms114
(Top-posting; sorry.)
Much of that is already fixed during our day, in
http://git.infradead.org/linux-retpoline.git/shortlog/refs/heads/ibpb
I forgot to fix up the wrong-MSR typo though, and we do still need to address
reset.
On Mon, 2018-01-29 at 10:43 -0800, Jim Mattson wrote:
> On Sun, Jan
On Mon, Jan 22, 2018 at 09:37:38AM +0100, Linus Walleij wrote:
> On Thu, Jan 18, 2018 at 5:02 PM, Ludovic Desroches
> wrote:
>
> > Add support for the drive-strength property. Usually its value is
> > expressed in mA. Since the numeric value depends on VDDIOP voltage,
> > the controller uses low,
Rafael,
On 1/16/2018 4:49 PM, Bjorn Helgaas wrote:
> On Tue, Jan 16, 2018 at 01:53:00PM -0500, Sinan Kaya wrote:
>> Correcting linux-pci email.
>>
>> On 1/16/2018 1:51 PM, Sinan Kaya wrote:
>>> When ACPI Link object is enabled, the message is printed with a warning
>>> prefix. Some test tools are
On Sun, Jan 28, 2018 at 4:58 PM, KarimAllah Ahmed wrote:
> Add direct access to MSR_IA32_SPEC_CTRL for guests. This is needed for
> guests that will only mitigate Spectre V2 through IBRS+IBPB and will not
> be using a retpoline+IBPB based approach.
>
> To avoid the overhead of atomically saving an
Can I assume you'll send out a new version with the fixes?
On Mon, Jan 29, 2018 at 11:01 AM, David Woodhouse wrote:
>
> (Top-posting; sorry.)
>
> Much of that is already fixed during our day, in
> http://git.infradead.org/linux-retpoline.git/shortlog/refs/heads/ibpb
>
> I forgot to fix up the wro
On 01/26/2018 06:00 PM, Borislav Petkov wrote:
On Fri, Jan 26, 2018 at 05:52:15PM -0600, Gary R Hook wrote:
--- a/drivers/iommu/Kconfig
+++ b/drivers/iommu/Kconfig
@@ -135,6 +135,15 @@ config AMD_IOMMU_V2
hardware. Select this option if you want to use devices that support
th
On 29/01/18 17:45, Marc Zyngier wrote:
One of the major improvement of SMCCC v1.1 is that it only clobbers
the first 4 registers, both on 32 and 64bit. This means that it
becomes very easy to provide an inline version of the SMC call
primitive, and avoid performing a function call to stash the
re
On Mon, Jan 29, 2018 at 06:36:05PM +, Mathieu Desnoyers wrote:
> - On Jan 29, 2018, at 1:15 PM, Peter Zijlstra pet...@infradead.org wrote:
> > Aaah, its the case where we do not pass through switch_mm(), the partial
> > comment got to me. I only realized after reading the next patch.
>
>
On 01/29/2018 08:04 PM, Jim Mattson wrote:
Can I assume you'll send out a new version with the fixes?
Yes, I am currently doing some tests and once I am done I will send a
new round.
... and the typo is already fixed in 'ibpb-wip' :)
On Mon, Jan 29, 2018 at 11:01 AM, David Woodhouse wrot
Hello, Michal.
On Mon, Jan 29, 2018 at 11:46:57AM +0100, Michal Hocko wrote:
> @@ -1292,7 +1292,11 @@ the memory controller considers only cgroups belonging
> to the sub-tree
> of the OOM'ing cgroup.
>
> The root cgroup is treated as a leaf memory cgroup, so it's compared
> -with other leaf m
On Fri, Jan 26, 2018 at 02:47:20PM -0800, Cong Wang wrote:
> Similar to commit df206988e03e
> ("fs: fuse: account fuse_inode slab memory as reclaimable"), these
> kernfs nodes are currently included in the unreclaimable slab counts -
> SUnreclaim in /proc/meminfo. And they are reclaimable too and c
On Tue, Jan 23, 2018 at 10:57:22AM -0500, Mathieu Desnoyers wrote:
> Hi Ingo, Peter, Thomas,
>
> Here is the updated membarrier patch series
Aside from the horribly long symbols and the comment bike-shedding, I
think its ok.
Acked-by: Peter Zijlstra (Intel)
Hello,
On Mon, Jan 22, 2018 at 11:26:18AM -0800, Tejun Heo wrote:
> While adding cgroup2 interface for the cpu controller, 0d5936344f30
> ("sched: Implement interface for cgroup unified hierarchy") forgot to
> update input validation and left it to reject cpu.max config if any
> descendant has set
On Sun, Jan 28, 2018 at 4:58 PM, KarimAllah Ahmed wrote:
> From: Ashok Raj
>
> Add MSR passthrough for MSR_IA32_PRED_CMD and place branch predictor
> barriers on switching between VMs to avoid inter VM Spectre-v2 attacks.
>
> [peterz: rebase and changelog rewrite]
> [karahmed: - rebase
>
On Mon, Jan 29, 2018 at 10:43:22AM -0800, Jim Mattson wrote:
> On Sun, Jan 28, 2018 at 11:29 AM, KarimAllah Ahmed wrote:
> > Add direct access to MSR_IA32_SPEC_CTRL for guests. This is needed for
> > guests
> > that will only mitigate Spectre V2 through IBRS+IBPB and will not be using a
> > retpo
- On Jan 29, 2018, at 2:09 PM, Peter Zijlstra pet...@infradead.org wrote:
> On Mon, Jan 29, 2018 at 06:36:05PM +, Mathieu Desnoyers wrote:
>> - On Jan 29, 2018, at 1:15 PM, Peter Zijlstra pet...@infradead.org wrote:
>
>> > Aaah, its the case where we do not pass through switch_mm(), t
On Mon, Jan 29, 2018 at 12:38:50PM -0600, Josh Poimboeuf wrote:
> On Tue, Jan 23, 2018 at 04:25:42PM +0100, Peter Zijlstra wrote:
> > Paravirt emits indirect calls which get flagged by objtool retpoline
> > checks, annotate it away because all these indirect calls will be
> > patched out before we
From:
Date: Sat, 27 Jan 2018 12:09:01 +0530
> From: Harini Katakam
>
> Handle HRESP error by doing a SW reset of RX and TX and
> re-initializing the descriptors, RX and TX queue pointers.
>
> Signed-off-by: Harini Katakam
> Signed-off-by: Michal Simek
Applied, thanks.
On Mon, Jan 29, 2018 at 11:16 AM, Konrad Rzeszutek Wilk
wrote:
> On Mon, Jan 29, 2018 at 10:43:22AM -0800, Jim Mattson wrote:
>> On Sun, Jan 28, 2018 at 11:29 AM, KarimAllah Ahmed
>> wrote:
>> > Add direct access to MSR_IA32_SPEC_CTRL for guests. This is needed for
>> > guests
>> > that will on
Hi Vincent, Peter,
I've been running some tests on your patches (Peter's base + the 2 from
Vincent). The results themselves are hosted at [1].
The base of those tests is the same: a task ("accumulator") is ran for 5
seconds (arbitrary value) to accumulate some load, then goes to sleep
for .5 s
In kernel 4.15, the modprobe step on my PowerBook G5 started complaining that
there was no module license for ans-lcd.
Signed-off-by: Larry Finger
---
drivers/macintosh/ans-lcd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/macintosh/ans-lcd.c b/drivers/macintosh/ans-lcd.c
index 1
> -Original Message-
> From: Andy Shevchenko [mailto:andy.shevche...@gmail.com]
> Sent: Monday, January 29, 2018 12:57 PM
> To: Marco Martin
> Cc: Platform Driver ; Limonciello, Mario
> ; Andy Shevchenko ; Pali
> Rohár ; Darren Hart ; Matthew
> Garrett ; Linux Kernel Mailing List ker...@v
From: Colin King
Date: Tue, 16 Jan 2018 17:54:22 +
> From: Colin Ian King
>
> Pointer cursg is initialized to cmd->cursg and again re-assigned the
> same value a few lines later, hence the second assignment is redundant
> and can be removed.
>
> Cleans up clang warning:
> drivers/ide/ide-t
> On Sun, Jan 28, 2018 at 09:17:53PM +, Winkler, Tomas wrote:
>
> > > I think if a driver can fail reliquish then it needs some kind of
> > > strategy to recover.
>
> > Maybe some driver can and some not, but if it doesn't succeed it
> > should return an error.
>
> But you can't just leave
On 29 January 2018 at 17:45, Marc Zyngier wrote:
> Add the detection and runtime code for ARM_SMCCC_ARCH_WORKAROUND_1.
> It is lovely. Really.
>
> Signed-off-by: Marc Zyngier
> ---
> arch/arm64/include/asm/kvm_psci.h | 63
> arch/arm64/kernel/bpi.S
On Fri, Jan 19, 2018 at 05:13:42PM +0530, Vivek Gautam wrote:
> 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
On Mon, Jan 29, 2018 at 08:33:18PM +0900, Andi Shyti wrote:
> 200ms seconds is a very long time to keep the CPU busy looping.
> Use msleep instead.
>
> Signed-off-by: Andi Shyti
Applied, thank you.
> ---
> drivers/input/touchscreen/mms114.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(
On Mon, Jan 29, 2018 at 08:33:21PM +0900, Andi Shyti wrote:
> Signed-off-by: Andi Shyti
Applied, thank you.
> ---
> drivers/input/touchscreen/mms114.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/input/touchscreen/mms114.c
> b/drivers/input/touchscreen/mms1
On Mon, Jan 29, 2018 at 08:33:23PM +0900, Andi Shyti wrote:
> It's 'MMS114_INFORMATION', not 'MMS114_INFOMATION'
>
> Signed-off-by: Andi Shyti
Applied, thank you.
> ---
> drivers/input/touchscreen/mms114.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/in
On Mon, Jan 29, 2018 at 08:33:22PM +0900, Andi Shyti wrote:
> Replace the original license statement with the SPDX identifier.
>
> Signed-off-by: Andi Shyti
Applied, thank you.
> ---
> drivers/input/touchscreen/mms114.c | 13 +
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
>
401 - 500 of 1013 matches
Mail list logo
