Block ids are just shifted section numbers, so let's also use
"unsigned long" for them, too.
Cc: Greg Kroah-Hartman
Cc: "Rafael J. Wysocki"
Signed-off-by: David Hildenbrand
---
drivers/base/memory.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/dr
Let's move walk_memory_blocks() to the place where memory block logic
resides and simplify it. While at it, add a type for the callback function.
Cc: Greg Kroah-Hartman
Cc: "Rafael J. Wysocki"
Cc: David Hildenbrand
Cc: Andrew Morton
Cc: Stephen Rothwell
Cc: Pavel Tatashin
Cc: Andrew Banman
We are using a mixture of "int" and "unsigned long". Let's make this
consistent by using "unsigned long" everywhere. We'll do the same with
memory block ids next.
While at it, turn the "unsigned long i" in removable_show() into an
int - sections_per_block is an int.
Cc: Greg Kroah-Hartman
Cc: "R
walk_memory_range() was once used to iterate over sections. Now, it
iterates over memory blocks. Rename the function, fixup the
documentation. Also, pass start+size instead of PFNs, which is what most
callers already have at hand. (we'll rework link_mem_sections() most
probably soon)
Follow-up pat
It is only used internally.
Cc: Greg Kroah-Hartman
Cc: "Rafael J. Wysocki"
Cc: Andrew Morton
Cc: Keith Busch
Cc: Oscar Salvador
Signed-off-by: David Hildenbrand
---
drivers/base/node.c | 3 ++-
include/linux/node.h | 7 ---
2 files changed, 2 insertions(+), 8 deletions(-)
diff --git a
On Wed, Jun 19, 2019 at 02:34:04PM -0700, Fenghua Yu wrote:
> diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
> index efb114298cfb..4910cb421b82 100644
> --- a/arch/x86/kernel/cpu/common.c
> +++ b/arch/x86/kernel/cpu/common.c
> @@ -847,6 +847,9 @@ void get_cpu_cap(struct cp
On Thu, 2019-06-20 at 16:46 +0800, Tao Xu wrote:
> UMWAIT and TPAUSE instructions use IA32_UMWAIT_CONTROL at MSR index E1H
> to determines the maximum time in TSC-quanta that the processor can reside
> in either C0.1 or C0.2.
>
> This patch emulates MSR IA32_UMWAIT_CONTROL in guest and differentia
Hi Enric,
For extcon parth,
Acked-by: Chanwoo Choi
Best Regards,
Chanwoo Choi
On 19. 6. 15. 오전 1:36, Enric Balletbo i Serra wrote:
> Now, the ChromeOS EC core driver has nothing related to an MFD device, so
> move that driver from the MFD subsystem to the platform/chrome subsystem.
>
> Signed-
Hi all,
Changes since 20190619:
New trees: keys, afs
The jc_docs tree gained a conflict against the char-misc.current tree.
The fbdev tree gained a build failure so I used the version from
next-20190619.
The rdma tree gained conflicts against Linus' tree.
The net-next tree lost its build
On Thu, Jun 20, 2019 at 6:23 PM Tetsuo Handa
wrote:
>
> On 2019/06/20 19:10, Yafang Shao wrote:
> >>> With this patch, hung task warnings will be reset with
> >>> sys_hung_task_warnings setting in evenry check interval.
> >>
> >> Since it is uncommon that the messages are printed for more than 10
Thanks a lot for reply!!
I just misunderstood how a PPI is registered and thought
I have a chance to eliminate the code.
This patch seems nonsense now, please ignore it.
Sorry to disturb you guys.
Thanks,
Lecopzer
On Thu 20-06-19 19:32:15, Minchan Kim wrote:
[...]
> Then, okay, I will add can_do_mincore similar check for the MADV_PAGEOUT
> syscall
> if others have different ideas.
Great that we are on the same page. We can simply skip over those pages.
--
Michal Hocko
SUSE Labs
On Wed, Jun 12, 2019 at 03:23:35PM +0530, Vidya Sagar wrote:
> Add P2U (PIPE to UPHY) and PCIe controller nodes to device tree.
> The Tegra194 SoC contains six PCIe controllers and twenty P2U instances
> grouped into two different PHY bricks namely High-Speed IO (HSIO-12 P2Us)
> and NVIDIA High Spe
On 2019-06-17 14:37, Stanimir Varbanov wrote:
Hi Aniket,
On 6/11/19 9:05 AM, Aniket Masule wrote:
Present core assignment is static. Introduced load balancing
across the cores. Load on earch core is calculated and core
with minimum load is assigned to given instance.
Signed-off-by: Aniket Masu
Cc'ed more people as the issue is not just with the example but
with the interface itself.
On Thu, Jun 20, 2019 at 12:31:06PM +0200, Christian Brauner wrote:
> On Thu, Jun 20, 2019 at 06:11:44AM +0300, Dmitry V. Levin wrote:
> > Initialize pidfd to an invalid descriptor, to fail gracefully on
> >
On Wed, Jun 12, 2019 at 03:23:36PM +0530, Vidya Sagar wrote:
> Enable PCIe controller nodes to enable respective PCIe slots on
> P2972- board. Following is the ownership of slots by different
> PCIe controllers.
> Controller-0 : M.2 Key-M slot
> Controller-1 : On-board Marvell eSATA controller
Jim rightfully complains that hardcoding instuctions lengths is not always
correct: additional (redundant) prefixes can be used. Luckily, the ugliness
is mostly harmless: modern AMD CPUs support NRIP_SAVE feature but I'd like
to clean things up and sacrifice speed in favor of correctness.
Early RF
When we're unable to skip instruction with kvm_emulate_instruction() we
will not advance RIP and most likely the guest will get stuck as
consequitive attempts to execute the same instruction will likely result
in the same behavior.
As we're not supposed to see these messages under normal condition
To avoid hardcoding xsetbv length to '3' we need to support decoding it in
the emulator.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/include/asm/kvm_emulate.h | 1 +
arch/x86/kvm/emulate.c | 9 -
arch/x86/kvm/svm.c | 1 +
3 files changed, 10 insertions(+), 1
Various intercepts hard-code the respective instruction lengths to optimize
skip_emulated_instruction(): when next_rip is pre-set we skip
kvm_emulate_instruction(vcpu, EMULTYPE_SKIP). The optimization is, however,
incorrect: different (redundant) prefixes could be used to enlarge the
instruction. W
svm->next_rip is only used by skip_emulated_instruction() and in case
kvm_set_msr() fails we rightfully don't do that. Move svm->next_rip
advancement to 'else' branch to avoid creating false impression that
it's always advanced.
By the way, rdmsr_interception() has it right already.
Signed-off-by
On Wed, Jun 12, 2019 at 03:23:39PM +0530, Vidya Sagar wrote:
> Add PCIe host controller driver for DesignWare core based
> PCIe controller IP present in Tegra194.
>
> Signed-off-by: Vidya Sagar
> ---
> Changes since [v9]:
> * None
>
> Changes since [v8]:
> * None
>
> Changes since [v7]:
> * Non
Regardless of the way how we skip instruction, interrupt shadow needs to be
cleared.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/kvm/svm.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index 68f1f0218c95..f980fc43372d 100644
--- a
On Wed 19-06-19 11:21:55, Ross Zwisler wrote:
> Currently both journal_submit_inode_data_buffers() and
> journal_finish_inode_data_buffers() operate on the entire address space
> of each of the inodes associated with a given journal entry. The
> consequence of this is that if we have an inode wher
On 19-Jun 17:19, Douglas Raillard wrote:
> Hi Patrick,
Hi!
> On 5/16/19 1:55 PM, Patrick Bellasi wrote:
> > On 08-May 18:43, douglas.raill...@arm.com wrote:
> > > From: Douglas RAILLARD
> > >
> > > Avoid assuming a CPU is busy when it has begun being idle before
> > > get_next_freq() is called.
Hi all,
In commit
905dade66268 ("pinctrl: mcp23s08: Fix add_data and irqchip_add_nested call
order")
Fixes tag
Fixes: 02e389e63 ("pinctrl: mcp23s08: fix irq setup order")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or mo
On Thu, Jun 20, 2019 at 02:00:37PM +0300, Dmitry V. Levin wrote:
> Cc'ed more people as the issue is not just with the example but
> with the interface itself.
>
> On Thu, Jun 20, 2019 at 12:31:06PM +0200, Christian Brauner wrote:
> > On Thu, Jun 20, 2019 at 06:11:44AM +0300, Dmitry V. Levin wrote
On Thu, Jun 20, 2019 at 10:21:09AM +, Peng Fan wrote:
> Hi Sudeep,
>
> > Subject: Re: [PATCH V2 2/2] mailbox: introduce ARM SMC based mailbox
> >
> > On Mon, Jun 03, 2019 at 04:30:05PM +0800, peng@nxp.com wrote:
> > > From: Peng Fan
> > >
> > > This mailbox driver implements a mailbox whic
On Wed 19-06-19 11:21:56, Ross Zwisler wrote:
> Use the newly introduced jbd2_inode dirty range scoping to prevent us
> from waiting forever when trying to complete a journal transaction.
>
> Signed-off-by: Ross Zwisler
Looks good to me. You can add:
Reviewed-by: Jan Kara
Hi Linus,
Here's a PR with quite a few MMC fixes intended for v5.2-rc6. This time the PR
also contains fixes for a WiFi driver, which device is attached to the SDIO
interface. Patches for the WiFi driver have been acked by the corresponding
maintainers. More details about the highlights are as usu
Hello,
syzbot found the following crash on:
HEAD commit:bed3c0d8 Merge tag 'for-5.2-rc5-tag' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=175d674ea0
kernel config: https://syzkaller.appspot.com/x/.config?x=28ec3437a5394ee0
da
The patch focuses on a new instruction AVX512_BF16 support for kvm guest,
defined
as CPUID.(EAX=7,ECX=1):EAX[bit 5], see spec[1].
The kvm implementation depends on kernel patch[2] which is in lkml discussion.
References:
[1] https://software.intel.com/sites/default/files/managed/c5/15/\
arch
AVX512 BFLOAT16 instructions support 16-bit BFLOAT16 floating-point
format (BF16) for deep learning optimization.
Intel adds AVX512 BFLOAT16 feature in CooperLake, which is CPUID.7.1.EAX[5].
Detailed information of the CPUID bit can be found here,
https://software.intel.com/sites/default/files/ma
On 27/05/19 1:52 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Note: resending rebased on top of v5.2-rc2
>
> ===
>
> This series adds cpufreq-dt operating points for da850 boards supported
> with device tree (da850-lcdk, da850-lego-ev3, da850-evm).
>
> Last patch enables CPUF
provides machine_is_olpc() stub for CONFIG_OLPC=n,
compiler should just optimize the unneeded bits away.
Signed-off-by: Lubomir Rintel
---
drivers/mfd/cs5535-mfd.c | 24 +++-
1 file changed, 7 insertions(+), 17 deletions(-)
diff --git a/drivers/mfd/cs5535-mfd.c b/drivers/mf
Kyle has reported that kernel crashes sometimes when it boots in
5-level paging mode with KASLR enabled:
[0.00] WARNING: CPU: 0 PID: 0 at arch/x86/mm/init_64.c:87
phys_p4d_init+0x1d4/0x1ea
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.2.0-rc5+
Kernel that boots in 5-level paging mode crashes in small percentage of
cases if KASLR is enabled.
This issue was tracked down to the case when the kernel image unpack in
the way it crosses 1G boundary. The crash was due to overrun of PMD page
table in __startup_64() and corruption of P4D page tab
__startup_64() uses fixup_pointer() to access global variables in a
position-independent fashion. Access to next_early_pgt was wrapped into
the helper, but one of the instance in 5-level paging branch was missed.
GCC generates a R_X86_64_PC32 PC-relative relocation for the access
which doesn't tri
On Thu, Jun 20, 2019 at 12:22:13PM +0300, Oded Gabbay wrote:
> Hi Greg,
>
> This is a pull request containing fixes to be merged to 5.2-rc6.
>
> It contains a single minor bug fix. See the tag comment for more details.
>
> Thanks,
> Oded
>
> The following changes since commit 6ad805b82dc5fc0ffd
> > From: linux-hyperv-ow...@vger.kernel.org
> > On Behalf Of Lorenzo Pieralisi
> > Sent: Monday, June 17, 2019 9:15 AM
> > > ...
> > > + some ARM experts who worked on arch/arm/kernel/hibernate.c.
> > >
> > > drivers/acpi/sleep.c is only built if ACPI_SYSTEM_POWER_STATES_SUPPORT
> > > is defined,
On Thu, Jun 20, 2019 at 11:45:34AM +0200, Christian Müller wrote:
> As stated in coding-styles.rst multiline comments should be structured in a
> way,
> that the actual comment starts on the second line of the commented portion.
> E.g:
>
> /*
> * Multiline comments
> * should look like
> * th
Ping?
Lubomir: I'm applying the set now, but please addres Jacopo's comment.
Thanks.
--
Sakari Ailus
From: Wanpeng Li
In real product setup, there will be houseeking cpus in each nodes, it
is prefer to do housekeeping from local node, fallback to global online
cpumask if failed to find houseeking cpu from local node.
Cc: Ingo Molnar
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Signed-off-by
On Thu, 2019-06-20 at 14:35 +0300, Sakari Ailus wrote:
> Ping?
>
> Lubomir: I'm applying the set now, but please addres Jacopo's comment.
> Thanks.
Hi, I'm wondering if you could wait a couple of minutes?
I've tested the patch set on my machine last night and I was about to
submit the updated se
Commit-ID: acec0ce081de0c36459eea91647faf99296445a3
Gitweb: https://git.kernel.org/tip/acec0ce081de0c36459eea91647faf99296445a3
Author: Fenghua Yu
AuthorDate: Wed, 19 Jun 2019 18:51:09 +0200
Committer: Borislav Petkov
CommitDate: Thu, 20 Jun 2019 12:38:44 +0200
x86/cpufeatures: Combine
Commit-ID: b302e4b176d00e1cbc80148c5d0aee36751f7480
Gitweb: https://git.kernel.org/tip/b302e4b176d00e1cbc80148c5d0aee36751f7480
Author: Fenghua Yu
AuthorDate: Mon, 17 Jun 2019 11:00:16 -0700
Committer: Borislav Petkov
CommitDate: Thu, 20 Jun 2019 12:38:49 +0200
x86/cpufeatures: Enumera
On Thu, Jun 20, 2019 at 01:37:53PM +0200, Lubomir Rintel wrote:
> On Thu, 2019-06-20 at 14:35 +0300, Sakari Ailus wrote:
> > Ping?
> >
> > Lubomir: I'm applying the set now, but please addres Jacopo's comment.
> > Thanks.
>
> Hi, I'm wondering if you could wait a couple of minutes?
>
> I've test
On Thu, 2019-06-20 at 13:24 +0300, Andy Shevchenko wrote:
> On Wed, Jun 19, 2019 at 12:45:25PM -0400, Jeff Layton wrote:
> > v2: drop bogus EXPORT_SYMBOL of static function
> >
> > The only real difference between this set and the one I sent originally
> > is the removal of a spurious EXPORT_SYMBO
Hi Lubomir, Sakari,
On Thu, Jun 20, 2019 at 01:37:53PM +0200, Lubomir Rintel wrote:
> On Thu, 2019-06-20 at 14:35 +0300, Sakari Ailus wrote:
> > Ping?
> >
> > Lubomir: I'm applying the set now, but please addres Jacopo's comment.
> > Thanks.
>
> Hi, I'm wondering if you could wait a couple of minu
I just noticed I didn't have Andrew explicitly on the receipents
list, so adding him.
Is everyone happy enough to give this a spin in -mm and linux-next?
This is the PHY chip for USB OTG on PXA platforms.
Signed-off-by: Lubomir Rintel
Acked-by: Pavel Machek
---
This remained unapplied, despite the driver being in already.
Changes since v1:
- Cosmetic and wording fixes
.../devicetree/bindings/phy/phy-pxa-usb.txt| 18 ++
1 f
Marvell MMP/PXA/MMP2 platforms seem to be excluded from the defconfig
for no good reasons. Enable the DT-based boards and the modules for
their peripherals.
Signed-off-by: Lubomir Rintel
---
arch/arm/configs/multi_v7_defconfig | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch
Power and volume button support for 5th and 6th genration Microsoft
Surface devices via soc_button_array.
Note that these devices use the same MSHW0040 device as on the Surface
Pro 4, however the implementation is different (GPIOs vs. ACPI
notifications). Thus some checking is required to ensure w
Do not use the surfacepro3_button driver on newer Microsoft Surface
models, only use it on the Surface Pro 3 and 4. Newer models (5th, 6th
and possibly future generations) use the same device as the Surface Pro
4 to represent their volume and power buttons (MSHW0040), but their
acutal implementatio
This series adds suport for power and volume buttons on 5th and 6th
generation Microsoft Surface devices. Specifically, it adds support for
the power-button on the Surface Laptop 1 and Laptop 2, as well as
support for power- and (on-device) volume-buttons on the Surface Pro 5
(2017), Pro 6, and Boo
On 6/20/19 7:53 AM, Andy Shevchenko wrote:
No top post, please.
Sorry, will do better!
And yes, submit it as a series. Also Cc to Benjamin Tissoires.
Done.
Thank you,
Maximilian
On Wed, Jun 19, 2019 at 11:56:36AM -0700, Jeffrey Hugo wrote:
> Fixes: e92a4047419c ("regulator: Add QCOM SPMI regulator driver")
> Reported-by: Bjorn Andersson
> Reported-by: Jorge Ramirez-Ortiz
> Signed-off-by: Jeffrey Hugo
I remember pointing this out during reviews as well...
signature.a
On 19. 06. 19 18:45, Colin King wrote:
> From: Colin Ian King
>
> A statement is indented one level too deep, fix this.
>
> Signed-off-by: Colin Ian King
> ---
> drivers/net/can/xilinx_can.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/can/xilinx_can.c
On Thu, Jun 20, 2019 at 4:58 PM Herbert Xu wrote:
>
> On Thu, Jun 20, 2019 at 06:54:42AM +, yamada.masah...@socionext.com wrote:
> >
> > I cannot reproduce the build error on the latest Linus tree.
> >
> >
> > $ make O=build allmodconfig fs/cifs/
> >
> > perfectly works for me.
>
> I was tryin
The objective is the same for all the governors: save energy, but at
the end the governors menu, ladder and teo aim to improve the
performances with an acceptable energy drop for some workloads which
are identified for servers and desktops (with the help of a firmware).
The ladder governor is desi
Hi Pavel,
Am 19.06.19 um 18:24 schrieb Pavel Machek:
> Hi!
>
> There's a (small) bias in passkey generation in bluetooth:
>
> get_random_bytes(&passkey, sizeof(passkey));
> passkey %= 100;
> put_unaligned_le32(passkey, smp->tk);
>
> (there are at
On 6/11/19 10:48 AM, Hugues Fruchet wrote:
> Add media controller support to dcmi.
>
> Signed-off-by: Hugues Fruchet
> ---
> drivers/media/platform/Kconfig| 2 +-
> drivers/media/platform/stm32/stm32-dcmi.c | 83
> +++
> 2 files changed, 63 insertions(+)
On 5/15/19 1:55 PM, Konstantin Khlebnikov wrote:
> Socket buffers always were dark-matter that lives by its own rules.
Is the information even exported somewhere e.g. in sysfs or via netlink yet?
> This patch adds line NetBuffers that exposes most common kinds of them.
Did you encounter a situat
On Tue, Jun 18, 2019 at 10:29:58AM +0300, Felipe Balbi wrote:
> Bartlomiej Zolnierkiewicz writes:
>
> > 'default n' is the default value for any bool or tristate Kconfig
> > setting so there is no need to write it explicitly.
> >
> > Also since commit f467c5640c29 ("kconfig: only write '# CONFIG_
Hi,
On 2019-06-17 23:00:27, Thomas Gleixner wrote:
On Sat, 30 Mar 2019, Ferdinand Blomqvist wrote:
The decoder is flawed in the following ways:
...
Aside of the fact that I had to wrap my brain around this crime I committed
more than a decade ago, all of this was really a pleasure to review.
On Fri, Jun 14, 2019 at 04:54:32PM +0800, Yinbo Zhu wrote:
> From: Ramneek Mehresh
>
> USB erratum-A006918 workaround tries to start internal PHY inside
> uboot (when PLL fails to lock). However, if the workaround also
> fails, then USB initialization is also stopped inside Linux.
> Erratum-A0069
On Fri, Jun 14, 2019 at 04:54:29PM +0800, Yinbo Zhu wrote:
> From: Nikhil Badola
>
> Set USB_EN bit to select ULPI phy for USB controller version 2.5
>
> Signed-off-by: Nikhil Badola
> Signed-off-by: Yinbo Zhu
> ---
> drivers/usb/host/ehci-fsl.c | 6 ++
> 1 file changed, 6 insertions(+)
On Wed, Jun 19, 2019 at 11:19:03AM -0700, Paul E. McKenney wrote:
> [ Hearing no objections and given no test failures in multiple weeks of
> rcutorture testing, I intend to submit this to the upcoming merge
> window. Thoughts? ]
I can't remember seeing this before; but then, there's a ton of
On Wed, Jun 19, 2019 at 05:15:32PM -0400, Liang, Kan wrote:
> Here are the patches posted.
> https://lkml.org/lkml/2019/5/28/1022
How many times do I have to tell that lkml.org links are frigging
useless?
Now I have to copy/paste them into a browser, pray the site works today,
and then copy paste
Allow testing code for old processors that lack the next RIP save
feature, by disabling usage of the next_rip field.
Nested hypervisors however get the feature unconditionally.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/svm.c | 15 ---
1 file changed, 12 insertions(+), 3 deletion
On 20/06/19 13:02, Vitaly Kuznetsov wrote:
>
> P.S. If you'd like to test the series you'll have to have a CPU without
> NRIP_SAVE feature or forcefully disable it, something like:
>
> index 8d4e50428b68..93c7eaad7915 100644
> --- a/arch/x86/kernel/cpu/amd.c
> +++ b/arch/x86/kernel/cpu/amd.c
> @@
On 20/06/19 13:21, Jing Liu wrote:
> + for (i = 1; i <= times; i++) {
> + if (*nent >= maxnent)
> + goto out;
> + do_cpuid_1_ent(&entry[i], function, i);
> + entry[i].eax &= F(AVX512_BF16);
> +
Hi Tom,
I'm trying to use histogram on a synthetic event, but faced an odd situation.
There is a synthetic event, which has foo and bar.
/sys/kernel/debug/tracing # cat synthetic_events
testevent int foo; int bar
And when I tried to add hist on trigger, both foo and bar can be used as be
Hello Linus,
The following changes since commit d1fdb6d8f6a4109a4263176c84b899076a5f8008:
Linux 5.2-rc4 (2019-06-08 20:24:46 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-5.2-5
for you to fetch changes up to 11aff18322
On 20/06/19 13:02, Vitaly Kuznetsov wrote:
> To avoid hardcoding xsetbv length to '3' we need to support decoding it in
> the emulator.
>
> Signed-off-by: Vitaly Kuznetsov
Can you also emulate it properly? The code from QEMU's
target/i386/fpu_helper.c can help. :)
Paolo
> ---
> arch/x86/incl
Paolo Bonzini writes:
> Commit 332d079735f5 ("KVM: nVMX: KVM_SET_NESTED_STATE - Tear down old EVMCS
> state before setting new state", 2019-05-02) broke evmcs_test because the
> eVMCS setup must be performed even if there is no VMXON region defined,
> as long as the eVMCS bit is set in the assist
Linus Torvalds's on June 12, 2019 11:09 am:
> On Tue, Jun 11, 2019 at 2:55 PM Nicholas Piggin wrote:
>>
>> What does this do for performance? I've found this pattern can be
>> bad for store aliasing detection.
>
> I wouldn't expect it to be noticeable, and the lack of argument
> reloading etc sho
On Thu, Jun 20, 2019 at 03:51:50PM +0530, Vinod Koul wrote:
> From: Christian Lamparter
>
> This patch adds a firmware loader for the uPD720201K8-711-BAC-A
> and uPD720202K8-711-BAA-A variant. Both of these chips are listed
> in Renesas' R19UH0078EJ0500 Rev.5.00 "User's Manual: Hardware" as
> dev
On Thu, Jun 20, 2019 at 03:51:54PM +0530, Vinod Koul wrote:
> Allow multiple firmware file versions in table and load them in
> increasing order as we find them in the file system.
>
> Signed-off-by: Vinod Koul
> Cc: Yoshihiro Shimoda
> Cc: Christian Lamparter
> ---
> drivers/usb/host/xhci-pci
Hi Jeff,
On Thu, Jun 20, 2019 at 1:41 PM Jeff Layton wrote:
> On Thu, 2019-06-20 at 13:24 +0300, Andy Shevchenko wrote:
> > On Wed, Jun 19, 2019 at 12:45:25PM -0400, Jeff Layton wrote:
> > > v2: drop bogus EXPORT_SYMBOL of static function
> > >
> > > The only real difference between this set and
On Tue, May 28, 2019 at 03:08:30PM -0700, kan.li...@linux.intel.com wrote:
> From: Kan Liang
Ok, have them now.
On 20/06/19 11:00, Wanpeng Li wrote:
> From: Wanpeng Li
>
> Raise #GP when guest read/write forbidden IA32_XSS.
>
> Fixes: 203000993de5 (kvm: vmx: add MSR logic for XSAVES)
> Reported-by: Xiaoyao Li
> Reported-by: Tao Xu
> Cc: Cc: Paolo Bonzini
> Cc: Radim Krčmář
> Cc: sta...@vger.kernel.
Paolo Bonzini writes:
> On 20/06/19 13:02, Vitaly Kuznetsov wrote:
>>
>> P.S. If you'd like to test the series you'll have to have a CPU without
>> NRIP_SAVE feature or forcefully disable it, something like:
>>
>> index 8d4e50428b68..93c7eaad7915 100644
>> --- a/arch/x86/kernel/cpu/amd.c
>> +++
Hi Doug,
Am Donnerstag, 20. Juni 2019, 03:27:55 CEST schrieb Doug Anderson:
> On Wed, Fri, 18 Mar 2016 Heiko Stuebner wrote:
> >
> > The panels need a bit of time to actually turn on. If this isn't
> > observed, this results in problems when trying talk to the panels
> > and thus produces detecti
On Thu, 20 Jun 2019, Steve Twiss wrote:
> (resend because the e-mail client added HTML formatting to my last reply)
>
> Hi Wolfram,
>
> On Wed, 19 Jun 2019 19:18:06, Wolfram Sang wrote:
>
> > Subject: [PATCH] mfd: da9063: occupy second I2C address, too
> >
> > Even though we don't use it yet,
On Tue, Jun 18, 2019 at 10:52:29PM -0700, Dan Williams wrote:
> Explain the general mechanisms of 'ZONE_DEVICE' pages and list the users
> of 'devm_memremap_pages()'.
>
> Cc: Jonathan Corbet
> Reported-by: Mike Rapoport
> Signed-off-by: Dan Williams
With one nit below
Reviewed-by: Mike Rapopo
Dan Williams writes:
> Changes since v9 [1]:
> - Fix multiple issues related to the fact that pfn_valid() has
> traditionally returned true for any pfn in an 'early' (onlined at
> boot) section regardless of whether that pfn represented 'System RAM'.
> Teach pfn_valid() to maintain its trad
On Thu, Jun 20, 2019 at 07:41:06AM -0400, Jeff Layton wrote:
> On Thu, 2019-06-20 at 13:24 +0300, Andy Shevchenko wrote:
> > On Wed, Jun 19, 2019 at 12:45:25PM -0400, Jeff Layton wrote:
> > So, then don't use snprintf() for this, simple memcpy() designed for that
> > kind
> > of things.
> >
>
>
On Thu, Jun 20, 2019 at 01:17:17PM +0300, Sakari Ailus wrote:
> diff --git a/drivers/media/i2c/mt9m111.c b/drivers/media/i2c/mt9m111.c
> index bd3a51c3b081..9761a6105407 100644
> --- a/drivers/media/i2c/mt9m111.c
> +++ b/drivers/media/i2c/mt9m111.c
> @@ -1263,9 +1263,11 @@ static int mt9m111_probe(
On Thu, Jun 20, 2019 at 07:36:54PM +0800, Wanpeng Li wrote:
> From: Wanpeng Li
>
> In real product setup, there will be houseeking cpus in each nodes, it
> is prefer to do housekeeping from local node, fallback to global online
> cpumask if failed to find houseeking cpu from local node.
>
> Cc
On 20.06.2019 15:03, Vlastimil Babka wrote:
On 5/15/19 1:55 PM, Konstantin Khlebnikov wrote:
Socket buffers always were dark-matter that lives by its own rules.
Is the information even exported somewhere e.g. in sysfs or via netlink yet?
in /proc/self/net/protocols
protocol size sockets m
Hi John,
For patches that go to a soc maintainer for merge, we're asking that
people don't cc a...@kernel.org directly.
We prefer to keep that alias mostly for pull requests from other
maintainers and patches we might have a reason to apply directly.
Otherwise we risk essentially getting all of l
On Thu, Jun 20, 2019 at 07:38:07AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
> head: 3ce5aceb5dee298b082adfa2baa0df5a447c1b0b
> commit: 2a538fda82824a7722e296be656bb5d11d91a9cb [23/33] perf/x86/intel: Add
> Icelake desktop CPU
On Wed, Jun 19, 2019 at 11:34:39PM +0530, Hariprasad Kelam wrote:
> This patch fixes below issue reported by checkpatch
>
> CHECK: Using comparison to true is error prone
> CHECK: Using comparison to false is error prone
>
> Signed-off-by: Hariprasad Kelam
> ---
> drivers/staging/rtl8723bs/hal/
On 20 June 2019 13:29, Lee Jones wrote:
> Subject: Re: [PATCH] mfd: da9063: occupy second I2C address, too
>
> Why isn't this reply attached (threaded) to the patch.
My apologies. It wasn't my intention to split Wolfram's original e-mail thread.
I don't usually reply using the mailto: link from
Hello,
syzbot found the following crash on:
HEAD commit:bed3c0d8 Merge tag 'for-5.2-rc5-tag' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=138d485ea0
kernel config: https://syzkaller.appspot.com/x/.config?x=28ec3437a5394ee0
da
On Thu, Jun 20, 2019 at 08:56:10PM +0900, Masahiro Yamada wrote:
>
> The similar question, and the answer is here:
> https://lkml.org/lkml/2019/1/17/584
But it doesn't work with O=:
$ rm -rf build-compile/fs/cifs
$ make O=build-compile fs/cifs
make[1]: Entering directory '/home/herbert/src/build/
The only difference between notifier_chain_cond_register() and
notifier_chain_register() is the lack of warning hints for duplicate
registrations.
Consider using notifier_chain_register() instead of
notifier_chain_cond_register() to avoid duplicate code
Signed-off-by: Xiaoming Ni
---
kernel/noti
blocking_notifier_chain_cond_register() does not consider
system_booting state, which is the only difference between this
function and blocking_notifier_cain_register(). This can be a bug
and is a piece of duplicate code.
Delete blocking_notifier_chain_cond_register()
Signed-off-by: Xiaoming Ni
Registering the same notifier to a hook repeatedly can cause the hook
list to form a ring or lose other members of the list.
case1: An infinite loop in notifier_chain_register() can cause soft lockup
atomic_notifier_chain_register(&test_notifier_list, &test1);
atomic_notifier_chain
201 - 300 of 1283 matches
Mail list logo
