Hi all,
This is version four of the patches I previously posted here:
v1:
http://lkml.kernel.org/r/1536747974-25875-1-git-send-email-will.dea...@arm.com
v2:
http://lkml.kernel.org/r/1538478363-16255-1-git-send-email-will.dea...@arm.com
v3:
http://lkml.kernel.org/r/1539188584-15819-1-git-
On 26/11/18 17:08, Colin King wrote:
> From: Colin Ian King
>
> The text in a TEST_ASSERT message contains a spelling mistake, fix it.
>
> Signed-off-by: Colin Ian King
> ---
> tools/testing/selftests/kvm/lib/elf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools
The current ioremap() code uses a phys_addr variable at each level of
page table, which is confusingly offset by subtracting the base virtual
address being mapped so that adding the current virtual address back on
when iterating through the page table entries gives back the corresponding
physical a
The core code already has a check for pXd_none(), so remove it from the
architecture implementation.
Cc: Chintan Pandya
Cc: Toshi Kani
Cc: Michal Hocko
Cc: Andrew Morton
Acked-by: Thomas Gleixner
Reviewed-by: Toshi Kani
Signed-off-by: Will Deacon
---
arch/x86/mm/pgtable.c | 6 --
1 fil
The core code already has a check for pXd_none(), so remove it from the
architecture implementation.
Cc: Chintan Pandya
Cc: Toshi Kani
Cc: Thomas Gleixner
Cc: Michal Hocko
Cc: Andrew Morton
Signed-off-by: Will Deacon
---
arch/arm64/mm/mmu.c | 8 ++--
1 file changed, 2 insertions(+), 6 d
Whilst no architectures actually enable support for huge p4d mappings
in the vmap area, the code that is implemented should be using
break-before-make, as we do for pud and pmd huge entries.
Cc: Chintan Pandya
Cc: Toshi Kani
Cc: Thomas Gleixner
Cc: Michal Hocko
Cc: Andrew Morton
Reviewed-by:
From: Vitaly Kuznetsov Sent: Monday, November 26, 2018
7:47 AM
>
> We implement Hyper-V SynIC and synthetic timers in KVM too so there's some
> room for code sharing.
>
> Signed-off-by: Vitaly Kuznetsov
> ---
> arch/x86/include/asm/hyperv-tlfs.h | 69 ++
> drivers
Commit 75045f77f7a7 ("x86/extable: Introduce _ASM_EXTABLE_UA for uaccess
fixups") made copy_user_to_xregs() -> XSTATE_OP() use _ASM_EXTABLE_UA.
Commit 9da3f2b74054 ("x86/fault: BUG() when uaccess helpers fault on
kernel addresses") then decided that a #GP is not good and has to be
reported loudly.
Hi Parthiban,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/irq/core]
[also build test ERROR on v4.20-rc4 next-20181126]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Hi Vinod,
Thanks for the review.
On 2018-11-26 20:14, Vinod Koul wrote:
Hi Govind,
On 26-11-18, 19:51, Govind Singh wrote:
Add device node for the ath10k SNOC platform driver probe
and add resources required for WCN3990 on qcs404 soc.
Optional clock and regulator controls are not yet availabl
On Mon, Nov 26, 2018 at 05:27:48PM +0200, Priit Laes wrote:
> +- regulator-soft-start: enable the output at the lowest possible
> voltage and
> + only then set the desired voltage
> + AXP20x/LDO3
This is a generic property, there is no need to documen
On 2018/11/25 17:59, Wei Yang wrote:
On Tue, Nov 20, 2018 at 10:58 AM zhong jiang wrote:
On 2018/11/17 9:33, Wengang Wang wrote:
The this_cpu_cmpxchg makes the do-while loop pass as long as the
s->cpu_slab->partial as the same value. It doesn't care what happened to
that slab. Interrupt is
On Mon, Nov 26, 2018 at 05:27:50PM +0200, Priit Laes wrote:
> In the defense of LDO3, LDO3 is the regulator that feeds port bank E,
> which has no other purpose then a CSI/TS interface, however the case
> may still be, that the connected IO may be just as well be 3.3 volts.
> The big misnomer is h
status = "disabled";
+
+ pruss: pruss@4a30 {
+
elm: elm@4808 {
compatible = "ti,am3352-elm";
reg = <0x4808 0x2000>;
This doesn't apply cleanly to next-2018112
On Mon, 2018-11-26 at 16:26 +0300, Dan Carpenter wrote:
> On Mon, Nov 26, 2018 at 02:10:09PM +0100, Nicholas Mc Guire wrote:
> > On Mon, Nov 26, 2018 at 04:00:32PM +0300, Dan Carpenter wrote:
> > > On Mon, Nov 26, 2018 at 10:39:04AM +0100, Nicholas Mc Guire wrote:
> > > > devm_kasprintf() may retur
This patch was initially posted by Kelley(kelley...@gmail.com).
Reposting the patch with all review comments addressed and with minor
modifications and optimizations. Tests were rerun and commit message
updated with new results.
The function try_to_unuse() is of quadratic complexity, with a lot of
On Mon, Nov 26, 2018 at 11:07:24AM -0500, Johannes Weiner wrote:
> Hi Mel,
>
> On Mon, Nov 26, 2018 at 01:34:20PM +, Mel Gorman wrote:
> > Hi Johannes,
> >
> > PSI is a great idea but it does have overhead and if enabled by Kconfig
> > then it incurs a hit whether the user is aware of the fea
When manual dirty log reprotect will be enabled, kvm_get_dirty_log_protect's
pointer argument will always be false on exit, because no TLB flush is needed
until the manual re-protection operation. Rename it from "is_dirty" to "flush",
which more accurately tells the caller what they have to do wit
CONFIG_DEBUG_OBJECTS_RCU_HEAD does not play well with kmemleak due to
recursive calls.
fill_pool
kmemleak_ignore
make_black_object
put_object
__call_rcu (kernel/rcu/tree.c)
debug_rcu_head_queue
debug_object_activate
debug_object_init
There are two problems with KVM_GET_DIRTY_LOG. First, and less important,
it can take kvm->mmu_lock for an extended period of time. Second, its user
can actually see many false positives in some cases. The latter is due
to a benign race like this:
1. KVM_GET_DIRTY_LOG returns a set of dirty p
The first such capability to be handled in virt/kvm/ will be manual
dirty page reprotection.
Signed-off-by: Paolo Bonzini
---
Documentation/virtual/kvm/api.txt | 13 +
arch/powerpc/kvm/powerpc.c| 14 ++
arch/s390/kvm/kvm-s390.c | 11 +--
arch/x86/
There are two problems with KVM_GET_DIRTY_LOG. First, and less important,
it can take kvm->mmu_lock for an extended period of time. Second, its user
can actually see many false positives in some cases. The latter is due
to a benign race like this:
1. KVM_GET_DIRTY_LOG returns a set of dirty p
On Mon, Nov 26, 2018 at 02:54:28PM +, Mark Brown wrote:
> On Mon, Nov 26, 2018 at 02:30:28PM +, Charles Keepax wrote:
>
> > Would there perhaps be milage in looking at just making
> > the regulator core request the GPIO, rather than the end
> > drivers? Gives us a single request/free point
On Wed, 21 Nov 2018 16:28:11 PST (-0800), rost...@goodmis.org wrote:
From: "Steven Rostedt (VMware)"
The function_graph_entry() function does the work of calling the function
graph hook function and the management of the shadow stack, simplifying the
work done in the architecture dependent prep
On 26/11/18 16:47, Vitaly Kuznetsov wrote:
> stimers_pending optimization only helps us to avoid multiple
> kvm_make_request() calls. This doesn't happen very often and these
> calls are very cheap in the first place, remove open-coded version of
> stimer_mark_pending() from kvm_hv_notify_acked_sin
On 26/11/18 16:47, Vitaly Kuznetsov wrote:
> Changes since v1:
> - avoid open-coding stimer_mark_pending() in kvm_hv_notify_acked_sint() and
> kvm_hv_synic_send_eoi [Paolo Bonzini]
>
> Turns out Hyper-V on KVM (as of 2016) will only use synthetic timers
> if direct mode is available. With direct
Quadros
---
This does not apply cleanly to next-20181126. It looks like you
could be missing "ARM: dts: am33xx: convert to use new clkctrl
layout" from your development branch.
On 26/11/18 16:47, Vitaly Kuznetsov wrote:
> Turns out Hyper-V on KVM (as of 2016) will only use synthetic timers
> if direct mode is available. With direct mode we notify the guest by
> asserting APIC irq instead of sending a SynIC message.
>
> The implementation uses existing vec_bitmap for lett
On Mon, Nov 26, 2018 at 05:39:23PM +0100, Peter Zijlstra wrote:
> On Mon, Nov 26, 2018 at 05:11:05PM +0100, Ard Biesheuvel wrote:
> > On Mon, 26 Nov 2018 at 17:08, Peter Zijlstra wrote:
> > >
> > > On Mon, Nov 26, 2018 at 07:55:00AM -0600, Josh Poimboeuf wrote:
> > > > +#ifdef CONFIG_HAVE_STATIC_C
As the comments for wake_up_bit() and waitqueue_active() point out,
the barriers are needed to order the clearing of the _FL_NOT_READY
bit and the waitqueue_active() load; match the implicit barrier in
prepare_to_wait().
Signed-off-by: Andrea Parri
---
fs/afs/cell.c | 2 ++
1 file changed, 2 ins
On 11/23/18 1:13 PM, Dan Williams wrote:
>> A new system call makes total sense to me. I have the same concern
>> about the completeness of what's exposed in sysfs, I just don't see a
>> _route_ to completeness with sysfs itself. Thus, the minimalist
>> approach as a first step.
> Outside of plat
On 14/11/18 19:15, Borislav Petkov wrote:
> From: Borislav Petkov
>
> Hi all,
>
> here's a rediff ontop of -rc2. No changes, only added Yazen's Tested-by.
>
> Please queue,
> thx.
>
> Changelog:
> ==
>
> v2:
>
> here's v2, dropping patch 3 and incorporating hopefully all of Radim's
>
On Mon, Nov 26, 2018 at 05:11:05PM +0100, Ard Biesheuvel wrote:
> On Mon, 26 Nov 2018 at 17:08, Peter Zijlstra wrote:
> >
> > On Mon, Nov 26, 2018 at 07:55:00AM -0600, Josh Poimboeuf wrote:
> > > +#ifdef CONFIG_HAVE_STATIC_CALL_INLINE
> > > +void arch_static_call_defuse_tramp(void *site, void *tra
On Mon, 26 Nov 2018 at 15:16, Sasha Levin wrote:
>
> >>
> >> /drivers/mtd/nand/atmel/nand-controller.c: In function
> >> 'atmel_hsmc_nand_controller_legacy_init':
> >> /drivers/mtd/nand/atmel/nand-controller.c:2080:11: error: implicit
> >> declaration of function 'of_get_compatible_child'; did y
On Mon, 2018-11-26 at 10:16 +, Leonard Crestez wrote:
> On Tue, 2018-11-20 at 21:42 +0100, Stefan Agner wrote:
> > On 20.11.2018 20:13, Trent Piepho wrote:
> > > On Tue, 2018-11-20 at 18:19 +, Leonard Crestez wrote:
> > > > On Tue, 2018-11-20 at 17:56 +0100, Stefan Agner wrote:
> > > > > De
On 11/26/2018 4:56 AM, Roberto Sassu wrote:
> On 11/23/2018 9:21 PM, Rob Landley wrote:
>> On 11/22/18 9:49 AM, Roberto Sassu wrote:
>>> Although rootfs (tmpfs) supports xattrs, they are not set due to the
>>> limitation of the cpio format. A new format called 'newcx' was proposed to
>>> overcome t
On Mon, Nov 26, 2018 at 8:11 AM Ard Biesheuvel
wrote:
>
> On Mon, 26 Nov 2018 at 17:08, Peter Zijlstra wrote:
> >
> > On Mon, Nov 26, 2018 at 07:55:00AM -0600, Josh Poimboeuf wrote:
> > > +#ifdef CONFIG_HAVE_STATIC_CALL_INLINE
> > > +void arch_static_call_defuse_tramp(void *site, void *tramp)
> >
On Mon, 26 Nov 2018 18:21:12 +0900
Masami Hiramatsu wrote:
> > Note, if another fgraph_ops is registered in the same location, its
> > retfunc may be called that was set by a previous fgraph_ops. This
> > is not a regression because that's what can happen today if you unregister
> > a callback f
- On Nov 26, 2018, at 10:51 AM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Nov 26, 2018, at 3:28 AM, Florian Weimer fwei...@redhat.com wrote:
>
>> * Mathieu Desnoyers:
>>
>>> Using a "weak" symbol in early adopter libraries is important, so they
>>> can be loaded tog
stable-rc/linux-4.4.y boot: 47 boots: 1 failed, 46 passed
(v4.4.164-71-g2646be341868)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.164-71-g2646be341868/
Full Build Summary:
https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.164-7
stable-rc/linux-3.18.y boot: 48 boots: 3 failed, 45 passed
(v3.18.126-25-g370f85bf6ea2)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18.126-25-g370f85bf6ea2/
Full Build Summary:
https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18
stable-rc/linux-4.9.y boot: 53 boots: 0 failed, 53 passed
(v4.9.140-47-gc5b0719ca177)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.140-47-gc5b0719ca177/
Full Build Summary:
https://kernelci.org/build/stable-rc/branch/linux-4.9.y/kernel/v4.9.140-4
stable-rc/linux-4.19.y boot: 99 boots: 0 failed, 96 passed with 3 offline
(v4.19.4-118-gba8189574643)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.4-118-gba8189574643/
Full Build Summary:
https://kernelci.org/build/stable-rc/branch/linux-4.19.y
On Tue, 27 Nov 2018 01:07:55 +0900
Masami Hiramatsu wrote:
> > > --- a/include/linux/sched.h
> > > +++ b/include/linux/sched.h
> > > @@ -1119,7 +1119,7 @@ struct task_struct {
> > > int curr_ret_depth;
> > >
> > > /* Stack of return addresses for return function
From: Colin Ian King
There is a spelling mistake in the module description text, fix it.
Signed-off-by: Colin Ian King
---
drivers/infiniband/hw/qib/qib_pcie.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/infiniband/hw/qib/qib_pcie.c
b/drivers/infiniband/hw/qib/
On Mon, 26 Nov 2018 16:43:56 +0100
Peter Zijlstra wrote:
> > + /* Patch the call site: */
> > + text_poke_bp((void *)insn, opcodes, CALL_INSN_SIZE,
> > +static_call_bp_handler);
>
> I'm confused by the whole static_call_bp_handler thing; why not jump
> straight to @func ?
On 11/26/2018 4:51 AM, Mimi Zohar wrote:
> On Fri, 2018-11-23 at 18:07 -0800, Casey Schaufler wrote:
>> On 11/23/2018 11:30 AM, Mimi Zohar wrote:
>>> On Fri, 2018-11-23 at 11:03 -0800, Casey Schaufler wrote:
On 11/22/2018 7:49 AM, Roberto Sassu wrote:
> Although rootfs (tmpfs) supports xat
On Wed, Nov 21 2018 at 14:36 -0700, Stephen Boyd wrote:
Quoting Lina Iyer (2018-11-20 16:06:47)
SDM845 SoC has an always-on interrupt controller (PDC) with select GPIO
routed to the PDC as interrupts that can be used to wake the system up
from deep low power modes and suspend.
Signed-off-by: Li
On Mon, 19 Nov 2018 12:59:10 +0100,
Takashi Iwai wrote:
>
> CONFIG_GENERIC_PCI_IOMAP is supposed to be set no matter whether
> CONFIG_PCI is present or not. Otherwise the generic header
> (asm-generic/pci_iomap.h) won't create dummy functions, and the code
> using pci_iomap() and pci_iounmap() wi
On Mon, 26 Nov 2018 at 17:08, Peter Zijlstra wrote:
>
> On Mon, Nov 26, 2018 at 07:55:00AM -0600, Josh Poimboeuf wrote:
> > +#ifdef CONFIG_HAVE_STATIC_CALL_INLINE
> > +void arch_static_call_defuse_tramp(void *site, void *tramp)
> > +{
> > + unsigned short opcode = INSN_UD2;
> > +
> > + mut
On Tue, Nov 20, 2018 at 04:31:47PM +0100, Andrea Merello wrote:
> The width of the "length register" cannot be autodetected, and it is now
> specified with a DT property. Add documentation for it.
>
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: devicet...@vger.kernel.org
> Cc: Radhey Shyam Pandey
On Mon, Nov 26, 2018 at 04:53:54PM +0100, Frederic Weisbecker wrote:
> > > + irq_work_queue_on(&per_cpu(vtime_set_nice_work, cpu), cpu);
> >
> > What happens if you already had one pending? Do we loose updates?
>
> No, if irq_work is already pending, it doesn't requeue iff the work hasn't
> been
From: Colin Ian King
The text in a TEST_ASSERT message contains a spelling mistake, fix it.
Signed-off-by: Colin Ian King
---
tools/testing/selftests/kvm/lib/elf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/kvm/lib/elf.c
b/tools/testing/selftes
On Fri, 23 Nov 2018 21:31:38 -0800
Joel Fernandes wrote:
> On Wed, Nov 21, 2018 at 08:27:19PM -0500, Steven Rostedt wrote:
> > From: "Steven Rostedt (VMware)"
> >
> > In order to make it possible to have multiple callbacks registered with the
> > function_graph tracer, the retstack needs to be
On Mon, Nov 26, 2018 at 07:55:00AM -0600, Josh Poimboeuf wrote:
> +#ifdef CONFIG_HAVE_STATIC_CALL_INLINE
> +void arch_static_call_defuse_tramp(void *site, void *tramp)
> +{
> + unsigned short opcode = INSN_UD2;
> +
> + mutex_lock(&text_mutex);
> + text_poke((void *)tramp, &opcode, 2);
>
On Sun, Nov 18, 2018 at 02:53:10PM +0100, Neil Armstrong wrote:
> The Amlogic Meson SoCs embeds a clock measurer IP to measure the internal
> clock paths frequencies.
>
> Acked-by: Martin Blumenstingl
> Signed-off-by: Neil Armstrong
> ---
> Rob,
>
> I didn't take your v2 Reviewed-by since I cha
On Tue, Nov 27, 2018 at 1:00 AM Hans Verkuil wrote:
>
> On 11/26/2018 04:44 PM, Tomasz Figa wrote:
> > Hi Hans,
> >
> > On Tue, Nov 27, 2018 at 12:24 AM Hans Verkuil wrote:
> >>
> >> On 11/26/2018 03:57 PM, Stanimir Varbanov wrote:
> >>> Hi Hans,
> >>>
> >>> On 11/26/18 3:37 PM, Hans Verkuil wrot
Hi Mel,
On Mon, Nov 26, 2018 at 01:34:20PM +, Mel Gorman wrote:
> Hi Johannes,
>
> PSI is a great idea but it does have overhead and if enabled by Kconfig
> then it incurs a hit whether the user is aware of the feature or not. I
> think enabling by default is unnecessary as it should only be
On 11/26/2018 02:11 AM, Dan Carpenter wrote:
The platform_device_register_full() function doesn't return NULL, it
returns error pointers.
Fixes: 4e01f5644463 ("fsi: Add On-Chip Controller (OCC) driver")
Signed-off-by: Dan Carpenter
Thanks.
Reviewed-by: Eddie James
---
drivers/fsi/fsi
On Mon, Nov 26, 2018 at 07:55:00AM -0600, Josh Poimboeuf wrote:
> diff --git a/arch/x86/kernel/static_call.c b/arch/x86/kernel/static_call.c
> index 8026d176f25c..d3869295b88d 100644
> --- a/arch/x86/kernel/static_call.c
> +++ b/arch/x86/kernel/static_call.c
> @@ -9,13 +9,21 @@
>
> void static_c
* Mathieu Desnoyers:
> So let's make __rseq_abi and __rseq_refcount strong symbols then ?
Yes, please. (But I'm still not sure we need the reference counter.)
Thanks,
Florian
On Mon, Nov 19, 2018 at 6:32 AM Philipp Zabel wrote:
>
> Hi Andrey,
>
> thank you for the patch.
>
> In general, sharing the lookup table with i.MX7 is fine iff it is a
> strict superset. But I don't think that is the case (see below).
> Even so, this will change if there ever is another i.MX7 or
On Tue, Nov 20, 2018 at 03:17:54PM +0100, Peter Zijlstra wrote:
> On Wed, Nov 14, 2018 at 03:46:03AM +0100, Frederic Weisbecker wrote:
> > On the vtime level, nice updates are currently handled on context
> > switches. When a task's nice value gets updated while it is sleeping,
> > the context swit
On 11/24/2018 02:43 AM, Dan Williams wrote:
> On Fri, Nov 23, 2018 at 11:21 AM Dave Hansen wrote:
>>
>> On 11/22/18 10:42 PM, Anshuman Khandual wrote:
>>> Are we willing to go in the direction for inclusion of a new system
>>> call, subset of it appears on sysfs etc ? My primary concern is not
- On Nov 26, 2018, at 3:28 AM, Florian Weimer fwei...@redhat.com wrote:
> * Mathieu Desnoyers:
>
>> Using a "weak" symbol in early adopter libraries is important, so they
>> can be loaded together into the same process without causing loader
>> errors due to many definitions of the same stron
On Fri, Oct 19, 2018 at 7:32 PM Masahiro Yamada
wrote:
>
> Document the list of SoCs and boards of UniPhier platform.
>
> Signed-off-by: Masahiro Yamada
> Reviewed-by: Rob Herring
> ---
Applied to linux-uniphier.
> Changes in v3:
> - Capitalize 'Board' consistently
> - Add Rob's Reviewed-
On Fri, Oct 19, 2018 at 7:33 PM Masahiro Yamada
wrote:
>
> Now, the Socionext vendor directory is available at
> Documentation/devicetree/bindings/arm/socionext/
>
> Move cache-uniphier.txt over to it.
>
> Signed-off-by: Masahiro Yamada
> Reviewed-by: Rob Herring
> ---
Applied to linux-uniphier
On 26.11.2018 14:34, Thierry Reding wrote:
> On Mon, Nov 26, 2018 at 01:23:16PM +0100, Lothar Waßmann wrote:
>> Thierry Reding wrote:
>>
>>> On Fri, Nov 23, 2018 at 03:15:11PM +, Vokáč Michal wrote:
On 22.11.2018 20:03, Uwe Kleine-König wrote:
> On Thu, Nov 22, 2018 at 04:46:39PM +000
On Fri, Nov 16, 2018 at 7:02 PM Viresh Kumar wrote:
>
> Each CPU can (and does) participate in cooling down the system but the
> DT only captures a handful of them, normally CPU0, in the cooling maps.
> Things work by chance currently as under normal circumstances its the
> first CPU of each clust
On Fri, Nov 16, 2018 at 7:06 PM Viresh Kumar wrote:
>
> Each CPU can (and does) participate in cooling down the system but the
> DT only captures a handful of them, normally CPU0, in the cooling maps.
> Things work by chance currently as under normal circumstances its the
> first CPU of each clust
On Mon, Nov 26, 2018 at 04:14:18PM +0100, Greg Kroah-Hartman wrote:
> On Mon, Nov 26, 2018 at 04:08:40PM +0100, Boris Brezillon wrote:
> > On Mon, 26 Nov 2018 19:46:15 +0530
> > Naresh Kamboju wrote:
> >
> > > Do you see build failure arm x15 beagleboard on 4.14 due to this patch ?
> > >
> > > O
We implement Hyper-V SynIC and synthetic timers in KVM too so there's some
room for code sharing.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/include/asm/hyperv-tlfs.h | 69 ++
drivers/hv/hv.c| 2 +-
drivers/hv/hyperv_vmbus.h | 68 --
Turns out Hyper-V on KVM (as of 2016) will only use synthetic timers
if direct mode is available. With direct mode we notify the guest by
asserting APIC irq instead of sending a SynIC message.
The implementation uses existing vec_bitmap for letting lapic code
know that we're interested in the part
stimers_pending optimization only helps us to avoid multiple
kvm_make_request() calls. This doesn't happen very often and these
calls are very cheap in the first place, remove open-coded version of
stimer_mark_pending() from kvm_hv_notify_acked_sint().
Suggested-by: Paolo Bonzini
Signed-off-by: V
Changes since v1:
- avoid open-coding stimer_mark_pending() in kvm_hv_notify_acked_sint() and
kvm_hv_synic_send_eoi [Paolo Bonzini]
Turns out Hyper-V on KVM (as of 2016) will only use synthetic timers
if direct mode is available. With direct mode we notify the guest by
asserting APIC irq instead
As a preparation to implementing Direct Mode for Hyper-V synthetic
timers switch to using stimer config definition from hyperv-tlfs.h.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/include/asm/hyperv-tlfs.h | 6 --
arch/x86/include/asm/kvm_host.h| 2 +-
arch/x86/kvm/hyperv.c
On Sun, Nov 25, 2018 at 07:33:35PM +0100, Thomas Gleixner wrote:
> The logic to detect whether there's a change in the previous and next
> task's flag relevant to update speculation control MSRs are spread out
s/are/is/
> across multiple functions.
>
> Consolidate all checks needed for updating
On Mon, Nov 26, 2018 at 07:54:59AM -0600, Josh Poimboeuf wrote:
> +void static_call_bp_handler(void);
> +void *bp_handler_dest;
> +
> +asm(".pushsection .text, \"ax\"
> \n"
> +".globl static_call_bp_handler \n"
> +
On 11/24/2018 12:51 AM, Dave Hansen wrote:
> On 11/22/18 10:42 PM, Anshuman Khandual wrote:
>> Are we willing to go in the direction for inclusion of a new system
>> call, subset of it appears on sysfs etc ? My primary concern is not
>> how the attribute information appears on the sysfs but lack
+++ Rick Edgecombe [20/11/18 15:23 -0800]:
Resending this because I missed Jessica in the "to" list. Also removing the part
of this coverletter that talked about KPTI helping with some local kernel text
de-randomizing methods, because I'm not sure I fully understand this.
---
On 14.11.18 19:15, Borislav Petkov wrote:
> From: Borislav Petkov
>
> This is an AMD-specific MSR. Put it where it belongs.
>
> Signed-off-by: Borislav Petkov
> Tested-by: Yazen Ghannam
> ---
> arch/x86/kvm/svm.c | 14 ++
> arch/x86/kvm/x86.c | 12
> 2 files changed,
From: Olliver Schinagl
The AXP209 supports ramping up voltages on several regulators such as
DCDC2 and LDO3.
This patch adds preliminary support for the regulator-ramp-delay property
for these 2 regulators. Note that the voltage ramp only works when
regulator is already enabled. E.g. when going
From: Olliver Schinagl
The current axp20x names the ramping register 'scal' which probably
means scaling. Since the register really has nothing to do with
scaling, but really is the voltage ramp we rename it appropriately.
Signed-off-by: Olliver Schinagl
Signed-off-by: Priit Laes
---
include/
From: Olliver Schinagl
When a regulator is marked as always on, it is enabled early on, when
checking and setting up constraints. It makes the assumption that the
bootloader properly initialized the regulator, and just in case enables
the regulator anyway.
Some constraints however currently get
From: Olliver Schinagl
In the past, there have been words on various lists that if LDO3 is
disabled in u-boot, but enabled in the DTS, the axp209 driver would
fail to continue/hang. Several enable/disable patches have been
issues to devicetree's in both the kernel and u-boot to address
this issue
From: Olliver Schinagl
The AXP20X driver currently has several masks defined throughout the
code. Use nice defines to make them clean and more descriptive.
Additionally include bitops.h, which was missing before, and sort
headers.
Signed-off-by: Olliver Schinagl
Signed-off-by: Priit Laes
---
From: Colin Ian King
The error message text contains a trivial spelling mistake, fix it.
Signed-off-by: Colin Ian King
---
drivers/net/wimax/i2400m/control.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wimax/i2400m/control.c
b/drivers/net/wimax/i2400m/contr
From: Olliver Schinagl
The AXP20X_OFF define is an actual specific bit, define it as such.
Signed-off-by: Olliver Schinagl
Signed-off-by: Priit Laes
---
drivers/mfd/axp20x.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c
index d
From: Olliver Schinagl
The axp20x_usb_power driver uses BIT() operations but lacks the include
for it. Include the bitops.h header file.
Signed-off-by: Olliver Schinagl
Signed-off-by: Priit Laes
---
drivers/power/supply/axp20x_usb_power.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/dr
From: Olliver Schinagl
The lradc's analog reference voltage is set to 3.0 volt in the
hardware. This is more or less set in copper for at least lradc0. Set the
property in the dts to ensure the lradc is referenced properly.
Signed-off-by: Olliver Schinagl
Signed-off-by: Priit Laes
---
arch/ar
From: Olliver Schinagl
The OLinuXino Lime2 has a big capacitor on its LDO3 output. It is
actually too large, causing the PMIC to shutdown when toggling the LDO3.
By enabling soft-start and ramp delay we increase the time for the
capacitor to charge lowering the current drain on the power regulat
This series implements voltage ramping for AXP209 DCDC2 and LDO3
regulators and software based soft-start for AXP209 LDO3 regulator.
Both features are needed to work around a PMIC shutdown when
toggling LDO3 on certain boards with high capacitance on the
LDO3 output.
Similar features (or workarou
From: Olliver Schinagl
With commit b43776d65a33b46092 ("ARM: dts: sunxi: Use axp209.dtsi for
Olinuxino Lime2") we force them an arbitrary 2.8 volts. Granted, for
LDO3 this may be less arbitrary, but for LDO4 this is just wrong.
In the defense of LDO3, LDO3 is the regulator that feeds port bank E
From: Olliver Schinagl
Add the bitops.h header as we need it, alphabetize header order.
Signed-off-by: Olliver Schinagl
Signed-off-by: Priit Laes
---
drivers/mfd/axp20x.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.
From: Olliver Schinagl
The AXP209 supports ramping up voltages on several regulators such as
DCDC2 and LDO3, therefore we can use the standard 'regulator-ramp-delay'
property for those 2 regulators.
Note that the voltage ramp only works when the regulator is already
enabled. E.g. when going from
From: Olliver Schinagl
In the past, there have been words on various lists that if LDO3 is
disabled in u-boot, but enabled in the DTS, the axp209 driver would
fail to continue/hang. Several enable/disable patches have been
issues to devicetree's in both the kernel and u-boot to address
this issue
From: Olliver Schinagl
Make use of the recommended BIT() macro for bit defines.
Signed-off-by: Olliver Schinagl
Signed-off-by: Priit Laes
---
drivers/power/supply/axp288_charger.c | 35 ++--
1 file changed, 18 insertions(+), 17 deletions(-)
diff --git a/drivers/power/
On Sun, Nov 25, 2018 at 07:33:34PM +0100, Thomas Gleixner wrote:
> During context switch, the SSBD bit in SPEC_CTRL MSR is updated according
> to changes of the TIF_SSBD flag in the current and next running task.
>
> Currently, only the bit controlling speculative store bypass disable in
> SPEC_CT
Hi,
> On 2018년 11월 21일 21:05, Kamil Konieczny wrote:
>> Add imem clock for exynos5433.
>
> It is diffcult to understand the meaning of 'imem' without the description.
> Please add more detailed description as the patch2 description.
> [...]
Thank you for review, will this be enough for descripti
On Thu, Nov 22, 2018 at 06:59:21PM +0530, Anshuman Khandual wrote:
>
>
> On 11/20/2018 04:36 AM, Keith Busch wrote:
> > On Mon, Nov 19, 2018 at 09:44:00AM +0530, Anshuman Khandual wrote:
> >> On 11/15/2018 04:19 AM, Keith Busch wrote:
> >>> System memory may have side caches to help improve acces
401 - 500 of 1098 matches
Mail list logo
