Hi Neil,
On Mon, Mar 11, 2019 at 10:57 AM Neil Armstrong wrote:
>
> Enable the Bluetooth Module on the X96 Max Set-Top-Box.
>
> Signed-off-by: Neil Armstrong
I didn't have time to test this yet but it looks sane to me, so:
Reviewed-by: Martin Blumenstingl
> ---
>
The pull request you sent on Fri, 15 Mar 2019 16:26:09 -0400:
> git://github.com/jonmason/ntb tags/ntb-5.1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e8a71a38668919c53e6ca9dd1bfa977e5690523f
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 15 Mar 2019 12:00:14 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git
> i2c/for-current-fixed
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/51b1ac0fa2403d1db009189122c17b7c1ea37b33
Thank you!
--
Deet-doot-dot,
The pull request you sent on Fri, 15 Mar 2019 10:35:19 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-next-2019-03-15
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8264fd046a0884d6bf475a784412978dbbd93175
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 15 Mar 2019 09:07:06 -0700:
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.1-merge-5
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/de578188ed0161713c9515eeafa394296516ff27
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 15 Mar 2019 11:26:08 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
> tags/sound-fix-5.1-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2dbb0e6c1961d823354c12bc1b66b005d1c78092
Thank you!
--
On Mon, Mar 11, 2019 at 10:57 AM Neil Armstrong wrote:
>
> Add pinctrl on the always-enabled debug UART AO.
>
> Signed-off-by: Neil Armstrong
Reviewed-by: Martin Blumenstingl
On Mon, Mar 11, 2019 at 10:56 AM Neil Armstrong wrote:
>
> Add pinctrl on the always-enabled debug UART AO.
>
> Signed-off-by: Neil Armstrong
Reviewed-by: Martin Blumenstingl
On Mon, Mar 11, 2019 at 10:56 AM Neil Armstrong wrote:
>
> Add pinctrl on the always-enabled debug UART AO.
>
> Signed-off-by: Neil Armstrong
Reviewed-by: Martin Blumenstingl
On Thu, Mar 7, 2019 at 4:15 PM Neil Armstrong wrote:
>
> This patch adds the nodes for the USB Complex found in the Amlogic
> G12A SoC.
>
> It includes the :
> - 2 USB2 PHYs
> - 1 USB3 + PCIE Combo PHY
> - the USB Glue with it's DWC2 and DWC3 sub-nodes
>
> Signed-off-by: Neil Armstrong
On Fri, Mar 08, 2019 at 03:10:08PM +0800, zhong jiang wrote:
> I can reproduce the issue in arm64 qemu machine. The issue will leave after
> applying the
> patch.
>
> Tested-by: zhong jiang
Thanks a lot for the quick testing!
> Meanwhile, I just has a little doubt whether it is necessary to
Hi Neil and Jerome,
On Thu, Mar 7, 2019 at 4:14 PM Neil Armstrong wrote:
>
> From: Jerome Brunet
>
> Add the reset controller device of g12a SoC family
>
> Signed-off-by: Jerome Brunet
> Signed-off-by: Neil Armstrong
> ---
> arch/arm64/boot/dts/amlogic/meson-g12a.dtsi | 7 +++
> 1 file
On Fri, Mar 15, 2019 at 12:54 PM Matthias Kaehlcke wrote:
>
> Building the 32-bit vDSO with a recent clang version fails due
> to undefined symbols:
>
> arch/x86/entry/vdso/vdso32.so.dbg: undefined symbols found
>
> The undefined symbol in this case is __lshrdi3, which is part of
> the compiler
> Basically I cheat Kconfig, so if one driver is built-in and
> the other is a loadable module, we compile both as built-in.
My mail client may have munged that path. Both "git am" and "patch -p1"
barf when I try to apply it. Since it was small I tried to replicate manually,
but I must have
Hi Neil,
On Thu, Mar 7, 2019 at 4:15 PM Neil Armstrong wrote:
>
> This patch adds the 2 UART nodes in the EE power domain with the corresponding
> pinctrl nodes.
there are 3 UART controllers in the EE power domain
> Signed-off-by: Neil Armstrong
> ---
>
Hi Stephen,
On Fri, Mar 15, 2019 at 11:51:12AM -0700, Stephen Boyd wrote:
> If we encounter a failure during suspend where this RTC was programmed
> to wakeup the system from suspend, but that wakeup couldn't be
> configured because the system didn't support wakeup interrupts, we'll
> run into
On Thu, Mar 7, 2019 at 4:14 PM Neil Armstrong wrote:
>
> This patch adds the SAR ADC controller node.
>
> Signed-off-by: Neil Armstrong
Reviewed-by: Martin Blumenstingl
On Thu, Mar 7, 2019 at 4:14 PM Neil Armstrong wrote:
>
> This adds the Always-On ao-secure system control registers node,
> which is used by the meson-gx-socinfo driver to detect the SoC IDs.
>
> Signed-off-by: Neil Armstrong
Reviewed-by: Martin Blumenstingl
Linus,
The following changes since commit c3c7470c75566a077c8dc71dcf8f1948b8ddfab4:
powerpc/kvm: Save and restore host AMR/IAMR/UAMOR (2019-02-22 13:41:13 +1100)
are available in the git repository at:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes
Hi Neil,
On Thu, Mar 7, 2019 at 4:14 PM Neil Armstrong wrote:
>
> Add nodes and properties for the AO Clocks and Resets.
>
> Signed-off-by: Neil Armstrong
> Signed-off-by: Jerome Brunet
> ---
> arch/arm64/boot/dts/amlogic/meson-g12a.dtsi | 17 +
> 1 file changed, 17
On Fri, Mar 15, 2019 at 7:11 PM Luck, Tony wrote:
>
> On Fri, Mar 15, 2019 at 07:02:06PM +0100, Borislav Petkov wrote:
> > On Fri, Mar 15, 2019 at 10:49:56AM -0700, Luck, Tony wrote:
> > > Yes - Qiuxu did that already ... patch reposted below.
> >
> > ... to which Arnd said that it were fragile
securityfs_create_file may fail. The fix checks its status and
returns the error code upstream if it fails.
Signed-off-by: Kangjie Lu
---
Return the exact error code upstream.
---
security/inode.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/security/inode.c b/security/inode.c
The compiler may emit calls to __lshrti3 from the compiler runtime
library, which results in undefined references:
arch/x86/kvm/x86.o: In function `mul_u64_u64_shr':
include/linux/math64.h:186: undefined reference to `__lshrti3'
Add a copy of the __lshrti3 libgcc routine (from gcc v4.9.2).
Jerome Brunet writes:
> This patchset adds the secure monitor and efuse to the g12a SoC family.
> These are sent together because the secure monitor is required for the
> efuse driver to work properly. This is probably something the bindings
> should show but it was not designed that way when
Neil Armstrong writes:
> Enable USB on the Nexbox A1 STB
>
> Signed-off-by: Neil Armstrong
Queued for v5.2 (branch; v5.2/dt64)
Thanks,
Kevin
On AMD processors, the detection of an overflowed PMC counter in the NMI
handler relies on the current value of the PMC. So, for example, to check
for overflow on a 48-bit counter, bit 47 is checked to see if it is 1 (not
overflowed) or 0 (overflowed).
When the perf NMI handler executes it does
On AMD processors, the detection of an overflowed counter in the NMI
handler relies on the current value of the counter. So, for example, to
check for overflow on a 48 bit counter, bit 47 is checked to see if it
is 1 (not overflowed) or 0 (overflowed).
There is currently a race condition present
This patch series addresses issues with increased NMI latency in newer
AMD processors that can result in unknown NMI messages when PMC counters
are active.
The following fixes are included in this series:
- Resolve a race condition when disabling an overflowed PMC counter,
specifically when
Hello Linus,
Here are a few NTB fixes for v5.1. While the tag is new, the patches
have been in my tree (and thus linux-next) for weeks now. Please
consider pulling them.
Thanks,
Jon
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06
Hi,
Am 15.03.19 um 13:15 schrieb Peter Zijlstra:
> On Fri, Mar 15, 2019 at 12:41:00PM +0100, Thomas Müller wrote:
>
>>> What .config do you have?
>> The one packaged by Fedora. I've attached the one for 4.20.15 as reference.
>
> Thanks, I'll have a poke, see what, if anything, is different from
This function returns an error if a child interrupt controller calls
irq_chip_set_wake_parent() but that parent interrupt controller has the
IRQCHIP_SKIP_SET_WAKE flag. Let's return 0 for success instead because
there isn't anything to do.
There's also the possibility that a parent indicates that
The helper functions will switch on faster accesses to FSBASE and GSBASE
when the FSGSBASE feature is enabled.
Accessing user GSBASE needs a couple of SWAPGS operations. It is avoidable
if the user GSBASE is saved at kernel entry, being updated as changes, and
restored back at kernel exit.
From: Andy Lutomirski
This is temporary. It will allow the next few patches to be tested
incrementally.
Setting unsafe_fsgsbase is a root hole. Don't do it.
Signed-off-by: Andy Lutomirski
Signed-off-by: Chang S. Bae
Reviewed-by: Andi Kleen
Reviewed-by: Andy Lutomirski
Cc: Thomas Gleixner
From: Andi Kleen
Add C intrinsics and assembler macros for the new FSBASE and GSBASE
instructions.
Very straight forward. Used in followon patches.
[ luto: Rename the variables from FS and GS to FSBASE and GSBASE and
make safe to include on 32-bit kernels. ]
Signed-off-by: Andi Kleen
On 3/6/19 9:01 AM, John Stultz wrote:
On Wed, Mar 6, 2019 at 8:14 AM Benjamin Gaignard
wrote:
Le mar. 5 mars 2019 à 21:54, John Stultz a écrit :
+
+ printf("Allocating 1 MEG\n");
+ ret = dmabuf_heap_alloc(heap_fd, ONE_MEG, 0, _fd);
+ if (ret)
+ goto out;
+
+
Copy real FS/GSBASE values instead of approximation when FSGSBASE is
enabled.
Suggested-by: Andy Lutomirski
Signed-off-by: Chang S. Bae
Cc: Andy Lutomirski
Cc: H. Peter Anvin
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Andi Kleen
---
arch/x86/kernel/process_64.c | 15 +--
1 file
From: Andy Lutomirski
Now that FSGSBASE is fully supported, remove unsafe_fsgsbase, enable
FSGSBASE by default, and add nofsgsbase to disable it.
Signed-off-by: Andy Lutomirski
Signed-off-by: Chang S. Bae
Reviewed-by: Andi Kleen
Cc: H. Peter Anvin
Cc: Thomas Gleixner
Cc: Ingo Molnar
---
From: Andi Kleen
v2: Minor updates to documentation requested in review.
v3: Update for new gcc and various improvements.
Signed-off-by: Andi Kleen
Signed-off-by: Chang S. Bae
Cc: Andy Lutomirski
Cc: H. Peter Anvin
Cc: Thomas Gleixner
Cc: Ingo Molnar
---
Documentation/x86/fsgs.txt | 104
From: Andi Kleen
The kernel needs to explicitly enable FSGSBASE. So, the application needs
to know if it can safely use these instructions. Just looking at the CPUID
bit is not enough because it may be running in a kernel that does not
enable the instructions.
One way for the application would
The FSGSBASE instructions allow fast accesses on GSBASE. Now, at the
paranoid_entry, the per-CPU base value can be always copied to GSBASE.
And the original GSBASE value will be restored at the exit.
So far, GSBASE modification has not been directly allowed from userspace.
So, swapping GSBASE
From: Andy Lutomirski
With the new FSGSBASE instructions, we can efficiently read and write
the FSBASE and GSBASE in __switch_to(). Use that capability to preserve
the full state.
This will enable user code to do whatever it wants with the new
instructions without any kernel-induced gotchas.
GSBASE is used to find per-CPU data in the kernel. But when it is unknown,
the per-CPU base can be found from the per_cpu_offset table with a CPU NR.
The CPU NR is extracted from the limit field of the CPUNODE entry in GDT,
or by the RDPID instruction.
Also, add the GAS-compatible RDPID macro.
It helps to use some new instructions directly in assembly code.
Suggested-by: Andi Kleen
Signed-off-by: Chang S. Bae
Reviewed-by: Andi Kleen
Acked-by: Andrew Morton
Cc: Andy Lutomirski
Cc: Linux Torvalds
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: H. Peter Anvin
---
Updates from v5 [5]:
* Drop the new tain flag (TAINT_INSECURE)
* Cleanup copy_thread_tls(), some changelog, and unnecessary comments on
assembly macros
* Rearrange some helper updates appropriately (from patch 4 to 6)
Updates from v4 [4]:
* Remove the FSGSBASE assembly macros
Updates from v3
From: Andy Lutomirski
This validates that GS and GSBASE are independently preserved across
context switches.
[ chang: Use FSGSBASE instructions directly instead of .byte ]
Signed-off-by: Andy Lutomirski
Reviewed-by: Andi Kleen
Signed-off-by: Chang S. Bae
Cc: H. Peter Anvin
Cc: Thomas
On Fri, Mar 15, 2019 at 10:23:53PM +0300, Andrey Abramov wrote:
> 15.03.2019, 22:06, "Andy Shevchenko" :
> > It makes harder to read and understand the code. One needs spend
> > deciseconds /
> > seconds to catch instead of santiseconds of time.
>
> If it is true for someone (for example, for me
I am pleased with this patch. Yes there is still a couple of controversial
issues but in my opinion, it is mostly "matter of taste", and whatever solutions
could be made, the patch is great.
So you may add me to the "Acked-by" section.
(And I mean the whole patch from 1 to 5)
With Best Regards,
Building the 32-bit vDSO with a recent clang version fails due
to undefined symbols:
arch/x86/entry/vdso/vdso32.so.dbg: undefined symbols found
The undefined symbol in this case is __lshrdi3, which is part of
the compiler runtime library, however the vDSO isn't linked against
this library.
_OSC now has a way to inform firmware that OS has the capability to
interpret HPX type 3 tables. Since ACPI 6.3 deprecated _OSC specifics,
these are now part of the PCI Firmware Specification.
The following is the document describing the changes:
ECN:_HPX and PCIe Completion Timeout related
15.03.2019, 22:06, "Andy Shevchenko" :
> It makes harder to read and understand the code. One needs spend deciseconds /
> seconds to catch instead of santiseconds of time.
If it is true for someone (for example, for me it is almost as readable
as a simple size_t), then I agree with Geert who
Dear Sir, I Know That This Mail Will Come To You As A Surprise As We
Never Met Before. I Need Your Urgent Assistance in Transferring the
Sum Of ($15.5m) to your account for safe keeping and investment this
is not a spam, its a real business that will benefit both of us. upon
receipt of your reply
When using this driver with the wireless dongle and some usermode
program that monitors every input device (acpid, for example), while
another usermode client opens and closes the low-level device
repeadedly, the system eventually deadlocks.
The reason is that steam_input_register_device() must
On Thu, 14 Mar 2019, Kangjie Lu wrote:
> securityfs_create_file may fail. The fix checks its status and
> returns EFAULT upstream if it fails.
>
> Signed-off-by: Kangjie Lu
> ---
> security/inode.c | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/security/inode.c
On Fri, Mar 15, 2019 at 09:53:07PM +0300, Andrey Abramov wrote:
> > I'm trying to present the case to spur discussion, but it realy is
> > a *question* I'm asking about whether to do that, not a suggestion
> > phrased as a question.
>
> > If it's just x86_64, use size_t everywhere, and let them
On 3/13/19 2:30 PM, Georgi Djakov wrote:
Here is a proposal to extend the OPP bindings with bandwidth based on
a previous discussion [1].
Every functional block on a SoC can contribute to the system power
efficiency by expressing its own bandwidth needs (to memory or other SoC
modules). This
Hi Matthew,
On Thu, Mar 14, 2019 at 9:30 PM Matthew Wilcox wrote:
>
> On Thu, Mar 14, 2019 at 03:10:19PM +0530, Souptick Joarder wrote:
> > > >> mm/memory.c:3968:21: sparse: incorrect type in assignment (different
> > > >> base types) @@expected restricted vm_fault_t [usertype] ret @@
>
> I'm trying to present the case to spur discussion, but it realy is
> a *question* I'm asking about whether to do that, not a suggestion
> phrased as a question.
> If it's just x86_64, use size_t everywhere, and let them suffer, for not
> being real 64-bit ;-)
But what is the problem of local
If we encounter a failure during suspend where this RTC was programmed
to wakeup the system from suspend, but that wakeup couldn't be
configured because the system didn't support wakeup interrupts, we'll
run into the following warning:
Unbalanced IRQ 166 wake disable
WARNING: CPU:
On Fri, Mar 15, 2019 at 07:24:28PM +0100, Christian Brauner wrote:
[..]
> > why do we want to add a new syscall (pidfd_wait) though? Why not just use
> > standard poll/epoll interface on the proc fd like Daniel was suggesting.
> > AFAIK, once the proc file is opened, the struct pid is essentially
From: =?UTF-8?q?Valdis=20Kl=C4=93tnieks?=
CC kernel/trace/trace_kprobe.o
kernel/trace/trace_kprobe.c:41: warning: cannot understand function prototype:
'struct trace_kprobe '
The real problem is that a comment looked like kerneldoc when it shouldn't be...
Link:
From: Masami Hiramatsu
Check the size of argument name and expression is not 0
and smaller than maximum length.
Link:
http://lkml.kernel.org/r/155253783029.14922.12650939303827581096.stgit@devnote2
Signed-off-by: Masami Hiramatsu
Signed-off-by: Steven Rostedt (VMware)
---
Linus,
This contains a series of last minute clean ups, small fixes and
error checks.
Please pull the latest trace-v5.1-2 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v5.1-2
Tag SHA1: de3d34862ab43473fb0ce9d774c09241b85c7c9c
Head
From: Douglas Anderson
As reported back in 2016-11 [1], the "ftdump" kdb command triggers a
BUG for "sleeping function called from invalid context".
kdb's "ftdump" command wants to call ring_buffer_read_prepare() in
atomic context. A very simple solution for this is to add allocation
flags to
From: Masami Hiramatsu
Check maxactive on kprobe error case, because maxactive
is only for kretprobe, not for kprobe. Also, maxactive
should not be 0, it should be at least 1.
Link:
http://lkml.kernel.org/r/155253780952.14922.15784129810238750331.stgit@devnote2
Signed-off-by: Masami Hiramatsu
On Fri, Mar 15, 2019 at 8:44 PM Enrico Weigelt, metux IT consult
wrote:
> On 15.03.19 19:11, Andy Shevchenko wrote:
> OTOH, the name, IMHO, is a bit misleading. Any chance of ever changing
> it to a more clear name (eg. devm_request_and_ioremap_resource()) ?
Compare iomap vs. ioREmap.
--
From: Masami Hiramatsu
Ensure given name of event is not too long when parsing it,
and fix to update event name offset correctly when the group
name is given. For example, this makes probe event to check
the "p:foo/" error case correctly.
Link:
From: Masami Hiramatsu
Check event and group naming rule at parsing it instead
of allocating probes.
Link:
http://lkml.kernel.org/r/155253784064.14922.2336893061156236237.stgit@devnote2
Signed-off-by: Masami Hiramatsu
Signed-off-by: Steven Rostedt (VMware)
---
kernel/trace/trace_kprobe.c |
From: =?UTF-8?q?Valdis=20Kl=C4=93tnieks?=
sparse complains:
CHECK kernel/trace/trace_probe.c
kernel/trace/trace_probe.c:16:12: warning: symbol 'reserved_field_names' was
not declared. Should it be static?
Yes, it should be static.
Link:
From: Masami Hiramatsu
Since alloc_trace_*probe() returns -EINVAL only if !event && !group,
it should not happen in trace_*probe_create(). If we catch that case
there is a bug. So use WARN_ON_ONCE() instead of pr_info().
Link:
On Fri, Mar 15, 2019 at 7:47 PM Hans de Goede wrote:
>
> Hi,
>
> On 3/15/19 2:31 PM, Gabriel Lazar wrote:
> > Add touchscreen platform data for the Myrya MY8307 2-in-1 laptop.
> >
> > Signed-off-by: Gabriel Lazar
>
> Patch looks good to me:
>
> Reviewed-by: Hans de Goede
>
OK, thanks for
On Fri, Mar 15, 2019 at 07:07:45PM +0100, Paolo Bonzini wrote:
> On 13/03/19 21:16, Sean Christopherson wrote:
> > Gah, this also needs: tools/testing/selftests/kvm/*/
> >
>
> No, it doesn't.
>
> $ scripts/get_maintainer.pl tools/testing/selftests/kvm/x86_64/state_test.c
> Paolo Bonzini
On Fri, Mar 15, 2019 at 02:13:24PM -0400, Joel Fernandes wrote:
> On Fri, Mar 15, 2019 at 07:03:07PM +0100, Christian Brauner wrote:
> > On Thu, Mar 14, 2019 at 09:36:43PM -0700, Daniel Colascione wrote:
> > > On Thu, Mar 14, 2019 at 8:16 PM Steven Rostedt
> > > wrote:
> > > >
> > > > On Thu, 14
Hi,
I'm working on organizing a microconference for Linux Plumbers 2019
focused on distribution kernels. The focus is on collaboration on
common problems for maintaining and distributing a kernel for any
kind of distribution (embedded, enterprise, community, internal, extrnal).
Ideally, this
I don't know if fix is functional correct, but at least it compiles now.
It failed before with a config for an AMD CPU.
Bug was introduced with commit d01b1f96a82e5dd7841a1d39db3abfdaf95f70ab
"perf/x86/intel: Make cpuc allocations consistent" which was merged
with
On Wed, 13 Mar 2019 17:05:01 +0100
Pierre Morel wrote:
> When the mediated device is open we setup the relation with KVM unset it
> when the mediated device is released.
>
> We ensure KVM is present on opening of the mediated device.
>
> We ensure that KVM survives the mediated device, and
On Fri, Mar 15, 2019 at 07:03:07PM +0100, Christian Brauner wrote:
> On Thu, Mar 14, 2019 at 09:36:43PM -0700, Daniel Colascione wrote:
> > On Thu, Mar 14, 2019 at 8:16 PM Steven Rostedt wrote:
> > >
> > > On Thu, 14 Mar 2019 13:49:11 -0700
> > > Sultan Alsawaf wrote:
> > >
> > > > Perhaps I'm
On Fri, Mar 15, 2019 at 07:02:06PM +0100, Borislav Petkov wrote:
> On Fri, Mar 15, 2019 at 10:49:56AM -0700, Luck, Tony wrote:
> > Yes - Qiuxu did that already ... patch reposted below.
>
> ... to which Arnd said that it were fragile because it might break if it
> includes a THIS_MODULE
On 13/03/19 21:16, Sean Christopherson wrote:
> Gah, this also needs: tools/testing/selftests/kvm/*/
>
No, it doesn't.
$ scripts/get_maintainer.pl tools/testing/selftests/kvm/x86_64/state_test.c
Paolo Bonzini (supporter:KERNEL VIRTUAL MACHINE
(KVM),commit_signer:8/9=89%,authored:3/9=33%)
On 13/03/19 18:13, Vitaly Kuznetsov wrote:
> When userspace initializes guest vCPUs it may want to zero all supported
> MSRs including Hyper-V related ones including HV_X64_MSR_STIMERn_CONFIG/
> HV_X64_MSR_STIMERn_COUNT. With commit f3b138c5d89a ("kvm/x86: Update SynIC
> timers on guest entry
On Thu, Mar 14, 2019 at 09:36:43PM -0700, Daniel Colascione wrote:
> On Thu, Mar 14, 2019 at 8:16 PM Steven Rostedt wrote:
> >
> > On Thu, 14 Mar 2019 13:49:11 -0700
> > Sultan Alsawaf wrote:
> >
> > > Perhaps I'm missing something, but if you want to know when a process has
> > > died
> > >
On 3/10/19 11:21 AM, Jonathan Cameron wrote:
> On Wed, 6 Mar 2019 09:55:23 +0100
> Fabrice Gasnier wrote:
>
>> DFSDM can operate using these buffer modes:
>> - INDIO_BUFFER_SOFTWARE: regular continuous conversions (no trigger)
>> but limited to 1 channel. User can set sampling frequency in
On Fri, Mar 15, 2019 at 10:49:56AM -0700, Luck, Tony wrote:
> Yes - Qiuxu did that already ... patch reposted below.
... to which Arnd said that it were fragile because it might break if it
includes a THIS_MODULE reference. So I'd say we won't do that then. And
keep it strictly a library.
Right?
From: Kan Liang
Perf fails to parse uncore event alias, for example:
#perf stat -e unc_m_clockticks -a --no-merge sleep 1
event syntax error: 'unc_m_clockticks'
\___ parser error
Current code assumes that the event alias is from one specific PMU.
To find the PMU,
On Fri, Mar 15, 2019 at 06:37:20PM +0100, Borislav Petkov wrote:
> I think the shared code should not have any reference to modules because
> it is supposed to be a library. Can you move the THIS_MODULE out of the
> common file and into the actual module?
Yes - Qiuxu did that already ... patch
Hi Greg,
Just wanted to check with you on how we may proceed with this series.
The main feature is exporting new sysfs attributes through driver core,
so I think it makes most sense to go through you unless you'd prefer
this go through a different route.
The proposed interface has been pretty
Hi George,
On Fri, Mar 15, 2019 at 5:59 PM George Spelvin wrote:
> On Fri, 15 Mar 2019 at 13:57:05 +0100, Geert Uytterhoeven wrote:
> > On Fri, Mar 15, 2019 at 11:23 AM George Spelvin wrote:
> >> On Fri, 15 Mar 2019 at 09:20:58 +0100, Geert Uytterhoeven wrote:
> >>> On Fri, Mar 15, 2019 at 5:33
Hi,
On 3/15/19 2:31 PM, Gabriel Lazar wrote:
Add touchscreen platform data for the Myrya MY8307 2-in-1 laptop.
Signed-off-by: Gabriel Lazar
Patch looks good to me:
Reviewed-by: Hans de Goede
Regards,
Hans
---
drivers/platform/x86/touchscreen_dmi.c | 25 +
On 3/15/19 10:49 AM, Tom Lendacky wrote:
> On 3/15/19 10:11 AM, Peter Zijlstra wrote:
>> On Fri, Mar 15, 2019 at 02:44:32PM +, Lendacky, Thomas wrote:
>>
> @@ -689,6 +731,7 @@ static __initconst const struct x86_pmu amd_pmu = {
> .amd_nb_constraints = 1,
>
On 22/02/19 11:48, lantianyu1...@gmail.com wrote:
> From: Lan Tianyu
>
> The max flush rep count of HvFlushGuestPhysicalAddressList hypercall
> is equal with how many entries of union hv_gpa_page_range can be populated
> into the input parameter page. The origin code lacks parenthesis around
>
On 06/02/19 06:53, Masahiro Yamada wrote:
> I do not see any consistency about headers_install of
> and .
>
> According to my analysis of Linux 5.0-rc5, there are 3 groups:
>
> [1] Both and are exported
>
> alpha, arm, hexagon, mips, powerpc, s390, sparc, x86
>
> [2] is exported, but
On Fri, 15 Mar 2019 15:10:25 +0100
Pierre Morel wrote:
> Sorry, wrong conclusion, handling this in userland will bring us much
> too far if we want to answer correctly for the case the hook is not
> there but QEMU accepted the facility for AQIC.
>
> The alternative is easier, we just continue
Hi,
On 3/15/19 6:33 PM, Andy Shevchenko wrote:
On Fri, Mar 15, 2019 at 3:31 PM Gabriel Lazar
wrote:
Add touchscreen platform data for the Myrya MY8307 2-in-1 laptop.
You sent one patch twice or two patches?
Please, clarify this by sending v2 with correct subject line(s) and
amount of
On Fri, Mar 15, 2019 at 08:57:18AM -0700, Luck, Tony wrote:
> fsl_ddr_edac.c looks to be doing exactly what we are doing with
> skx_common.c. They just get away with it for now because they don't
> have a reference to THIS_MODULE since they don't set up anything
> in sysfs.
>
> If this is your
On 31/01/19 17:09, Yu Zhang wrote:
> Previously, 'commit 372fddf70904 ("x86/mm: Introduce the 'no5lvl' kernel
> parameter")' cleared X86_FEATURE_LA57 in boot_cpu_data, if Linux chooses
> to not run in 5-level paging mode. Yet boot_cpu_data is queried by
> do_cpuid_ent() as the host capability
On Fri, Mar 15, 2019 at 3:31 PM Gabriel Lazar
wrote:
>
> Add touchscreen platform data for the Myrya MY8307 2-in-1 laptop.
You sent one patch twice or two patches?
Please, clarify this by sending v2 with correct subject line(s) and
amount of patches.
>
> Signed-off-by: Gabriel Lazar
> ---
>
On Fri, 15 Mar 2019 14:26:34 +0100
Pierre Morel wrote:
> On 15/03/2019 11:20, Cornelia Huck wrote:
> > On Wed, 13 Mar 2019 17:04:58 +0100
> > Pierre Morel wrote:
> >
> >> +/*
> >> + * handle_pqap: Handling pqap interception
> >> + * @vcpu: the vcpu having issue the pqap instruction
> >> + *
>
On 3/15/19 1:43 PM, André Almeida wrote:
Hello,
This series implements support for multiplane pixel formats at vimc.
A lot of changes were required since vimc support for singleplane
was "hardcoded". The code has been adapted in order to support both
formats. When was possible, the functions
On Fri, 15 Mar 2019, Oscar Salvador wrote:
> On Fri, Mar 15, 2019 at 01:47:33PM +0100, Michal Hocko wrote:
> > diff --git a/mm/debug.c b/mm/debug.c
> > index 1611cf00a137..499c26d5ebe5 100644
> > --- a/mm/debug.c
> > +++ b/mm/debug.c
> > @@ -78,6 +78,9 @@ void __dump_page(struct page *page, const
The patch
spi: spi-mem: stm32-qspi: avoid memory corruption at low frequency
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
spi: spi-mem: stm32-qspi: add suspend/resume support
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
101 - 200 of 443 matches
Mail list logo
