On Thu, Apr 18, 2019 at 5:07 PM Luck, Tony wrote:
>
> On Fri, Apr 19, 2019 at 01:29:10AM +0200, Borislav Petkov wrote:
> > Which reminds me, Tony, I think all those debugging files "pfn"
> > and "array" and the one you add now, should all be under a
> > CONFIG_RAS_CEC_DEBUG which is default off
On Thu, Apr 18, 2019 at 5:26 PM Borislav Petkov wrote:
>
> Now, if any of that above still doesn't make it clear, please state what
> you're trying to achieve and I'll try to help.
Sorry that I misled you to believe we don't even enable
CONFIG_X86_MCELOG_LEGACY. Here is what we have and
what we
On Fri, 19 Apr 2019, Jethro Beekman wrote:
> On 2019-04-19 14:34, Thomas Gleixner wrote:
> > And how so? You create writeable AND executable memory. That's a nono and
> > you can argue in circles, that's not going to change with any of your
> > proposed changes.
>
> On 2019-04-19 14:38, Thomas
On Mon, Apr 15, 2019 at 03:35:33PM +0200, Paolo Bonzini wrote:
> As mentioned in the comment, there are some special cases where we can simply
> clear the TPR shadow bit from the CPU-based execution controls in the vmcs02.
> Handle them so that we can remove some XFAILs from vmx.flat.
>
>
On Thu, 18 Apr 2019 at 23:29, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.36 release.
> There are 110 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
On Thu, 18 Apr 2019 at 23:40, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.0.9 release.
> There are 93 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
On 4/19/19 2:53 PM, a...@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2019-04-19-14-53 has been uploaded to
>
>http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my
From: kbuild test robot
drivers/power/supply/wilco-charger.c:173:1-3: WARNING: PTR_ERR_OR_ZERO can be
used
Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
Generated by: scripts/coccinelle/api/ptr_ret.cocci
Fixes: 2600e89ec94e ("power_supply: platform/chrome: wilco_ec: Add
Replace pci_printk with pci_*, dev_*() and pr_*() to avoid checkpatch
warnings.
Signed-off-by: Mohan Kumar
---
drivers/pci/bus.c | 3 +--
drivers/pci/pci.c | 14 +++---
drivers/pci/probe.c| 21 +
drivers/pci/setup-bus.c| 15
Define a pr_fmt() macro that convert all of the explicit printk() calls
into corresponding pr_*().
Signed-off-by: Mohan Kumar
---
drivers/pci/bus.c | 5 -
drivers/pci/pci-stub.c | 11 +--
drivers/pci/pci-sysfs.c | 3 ++-
drivers/pci/pci.c | 5 +++--
Replace printk with pr_* to avoid checkpatch warnings.
Signed-off-by: Mohan Kumar
---
drivers/pci/pci-acpi.c | 11 ---
drivers/pci/quirks.c | 2 +-
2 files changed, 5 insertions(+), 8 deletions(-)
diff --git a/drivers/pci/pci-acpi.c b/drivers/pci/pci-acpi.c
index e1949f7..3ada026
On Tue, Mar 26, 2019 at 04:26:54AM +, George Spelvin wrote:
> Explain what these functions are for and when they offer
> an advantage over get_random_bytes().
>
> (We still need documentation on rng_is_initialized(), the
> random_ready_callback system, and early boot in general.)
>
>
On 2019/4/19 18:43, Robert Jarzmik wrote:
> Zhou Wang writes:
>
>> In function sg_split, the second sg_calculate_split will return -EINVAL
>> when in_mapped_nents is 0.
>>
>> Indeed there is no need to do second sg_calculate_split and sg_split_mapped
>> when in_mapped_nents is 0, as
Pls ignore this.
On 2019/3/22 22:30, Yue Haibing wrote:
> From: YueHaibing
>
> Fix sparse warnings:
>
> kernel/sched/fair.c:2596:6: warning: symbol 'task_tick_numa' was not
> declared. Should it be static?
> kernel/sched/fair.c:3570:6: warning: symbol 'sync_entity_load_avg' was not
>
On Tue, Mar 19, 2019 at 01:28:47PM -0400, Jon DeVree wrote:
> When the system boots with random.trust_cpu=1 it doesn't initialize the
> per-NUMA CRNGs because it skips the rest of the CRNG startup code. This
> means that the code from 1e7f583af67b ("random: make /dev/urandom scalable
> for silly
On 2019/4/20 0:12, Mark Brown wrote:
> On Tue, Apr 16, 2019 at 10:41:09PM +0800, Yue Haibing wrote:
>> From: YueHaibing
>>
>> Fix sparse warnings:
>>
>> drivers/regulator/stm32-pwr.c:35:5: warning:
>> symbol 'ready_mask_table' was not declared. Should it be static?
>>
On 04/19 :49, Stefan Wahren wrote:
> Hi Madhumitha,
>
> Am 19.04.19 um 23:23 schrieb Madhumitha Prabakaran:
> > Remove unnecessary variable and replace return type.
> >
> > Issue suggested by Coccinelle.
> >
> > Signed-off-by: Madhumitha Prabakaran
> > ---
> >
On Fri, Apr 19, 2019 at 9:37 PM Steven Rostedt wrote:
>
> On Fri, 19 Apr 2019 21:22:59 -0500
> Wenwen Wang wrote:
>
> > In trace_pid_write(), the buffer for trace parser is allocated through
> > kmalloc() in trace_parser_get_init(). Later on, after the buffer is used,
> > it is then freed
All the fields in struct sy8106a are only used in sy8106a_i2c_probe(), so
use local variables instead.
Signed-off-by: Axel Lin
---
drivers/regulator/sy8106a-regulator.c | 40 +--
1 file changed, 13 insertions(+), 27 deletions(-)
diff --git
On 2019/4/17 1:52, Al Viro wrote:
> From: Al Viro
>
> Signed-off-by: Al Viro
Acked-by: Chao Yu
Thanks,
On Fri, 19 Apr 2019 21:22:59 -0500
Wenwen Wang wrote:
> In trace_pid_write(), the buffer for trace parser is allocated through
> kmalloc() in trace_parser_get_init(). Later on, after the buffer is used,
> it is then freed through kfree() in trace_parser_put(). However, it is
> possible that
Hi Arnd,
On 16/4/19 6:24 am, Arnd Bergmann wrote:
drivers should not rely on machine specific headers but
get their information from the platform device.
Signed-off-by: Arnd Bergmann
I like the whole series, thanks for doing this.
I haven't looked at the KS8695 in a long time now. I am not
- On Apr 19, 2019, at 5:13 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Apr 19, 2019, at 2:53 PM, Linus Torvalds
> torva...@linux-foundation.org
> wrote:
>
>> On Fri, Apr 19, 2019 at 11:46 AM tip-bot for Mathieu Desnoyers
>> wrote:
>>>
>>> rseq/selftests/x86:
In trace_pid_write(), the buffer for trace parser is allocated through
kmalloc() in trace_parser_get_init(). Later on, after the buffer is used,
it is then freed through kfree() in trace_parser_put(). However, it is
possible that trace_pid_write() is terminated due to unexpected errors,
e.g.,
Hi Arnd,
On 16/4/19 6:24 am, Arnd Bergmann wrote:
The TX interrupt is marked as edge triggered, so it will
already be acked by the top-level irq code, and does not
need the ack in the driver.
Removing this avoids a nasty dependency on the regs-irq.h
file that is otherwise reserved for the
Added Comet Lake PCI device ID to the supported device list.
Signed-off-by: Srinivas Pandruvada
---
drivers/hid/intel-ish-hid/ipc/hw-ish.h | 1 +
drivers/hid/intel-ish-hid/ipc/pci-ish.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/hid/intel-ish-hid/ipc/hw-ish.h
On Fri, Apr 19, 2019 at 03:20:42PM -0700, Stephen Boyd wrote:
> Quoting Leo Yan (2019-03-20 03:05:08)
> > clk_gate_ufs_subsys is a system bus clock, turning off it will
> > introduce lockup issue during system suspend flow. Let's mark
> > clk_gate_ufs_subsys as critical clock, thus keeps it on
On Fri, Apr 19, 2019 at 01:16:37PM -0700, Guenter Roeck wrote:
On Fri, Apr 19, 2019 at 12:39:26PM -0700, Guenter Roeck wrote:
On Thu, Apr 18, 2019 at 07:57:11PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.170 release.
> There are 50 patches in
The pull request you sent on Fri, 19 Apr 2019 17:28:34 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-5.1-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/371dd432ab39f7bc55d6ec77d63b430285627e04
Thank you!
--
Deet-doot-dot, I am a
On Fri, Apr 19, 2019 at 04:11:37PM -0700, Linus Torvalds wrote:
> On Fri, Apr 19, 2019 at 2:20 PM Joel Fernandes wrote:
> >
> > According to Linus, POLLHUP usually indicates that something is readable:
>
> Note that if you use the legacy interfaces (ie "select()"), then even
> just a plain
15.04.2019 в 00:08:38 +0200 Lukasz Majewski написал:
> +# if defined __NR_clock_settime64
> + /* Make sure that passed __timespec64 struct pad is 0. */
> + struct __timespec64 ts = *tp;
> + ts.tv_pad = 0;
> + return INLINE_SYSCALL_CALL (clock_settime64, clock_id, );
Isn't kernel supposed to
Currently for soft reboot(kexec_file_load) the kernel file and
signature is measured by IMA. The cmdline args used to load the kernel
is not measured.
The boot aggregate that gets calculated will have no change since the
EFI loader has not been triggered.
Adding the kexec cmdline args measure and
After extending the size of dentry from 192-bytes to 208-bytes
under aarch64, we got oops during the running of xfstests generic/429:
Unable to handle kernel NULL pointer dereference at virtual address
0002
CPU: 3 PID: 2725 Comm: t_encrypted_d_r Tainted: G D
Dear friend,
I am the Head of file Department in Africa Develop bank Burkina Faso.
I need your sincere cooperation to transfer the sum of $15 million
U.S.A dollars to your bank account.
I want you stand as next of kin to the deceased. I agree 40% for you
and 60% for me. Upon receipt of your
Hello, Linus.
A patch to fix a RCU imbalance error in the devices cgroup
configuration error path.
Thanks.
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.x86/alternatives
head: 1f30946b1a01baf22df6faf74c0a1e602bb6cac7
commit: 41bef31d0abe29b5888b33b526cacc8a30795318 [2/9] jump_label: Add the
jump_label_can_update_check() helper
If you fix the issue, kindly add following
Paul E. McKenney's on April 20, 2019 4:26 am:
> On Fri, Apr 19, 2019 at 08:00:17PM +0200, Peter Zijlstra wrote:
>> On Fri, Apr 19, 2019 at 01:21:45PM -0400, Alan Stern wrote:
>> > Index: usb-devel/Documentation/atomic_t.txt
>> > ===
On Sat, Apr 20, 2019 at 1:47 AM Daniel Colascione wrote:
>
> On Fri, Apr 19, 2019 at 4:12 PM Christian Brauner
> wrote:
> >
> > On Sat, Apr 20, 2019 at 12:46 AM Daniel Colascione
> > wrote:
> > >
> > > On Fri, Apr 19, 2019 at 3:02 PM Christian Brauner
> > > wrote:
> > > >
> > > > On Fri,
From: Prakhar Srivastava
Signed-off-by: Prakhar Srivastava
---
Currently for soft reboot(kexec_file_load) the kernel file and
signature is measured by IMA. The cmdline args used to load the kernel
is not measured.
The boot aggregate that gets calculated will have no change since the
EFI loader
From: Prakhar Srivastava
Signed-off-by: Prakhar Srivastava
---
Currently for soft reboot(kexec_file_load) the kernel file and
signature is measured by IMA. The cmdline args used to load the kernel
is not measured.
The boot aggregate that gets calculated will have no change since the
EFI loader
From: Prakhar Srivastava
Signed-off-by: Prakhar Srivastava
---
Currently for soft reboot(kexec_file_load) the kernel file and
signature is measured by IMA. The cmdline args used to load the kernel
is not measured.
The boot aggregate that gets calculated will have no change since the
EFI loader
On Sat, Apr 20, 2019 at 1:30 AM Daniel Colascione wrote:
>
> On Fri, Apr 19, 2019 at 4:02 PM Christian Brauner
> wrote:
> >
> > On Sat, Apr 20, 2019 at 12:35 AM Daniel Colascione
> > wrote:
> > >
> > > On Fri, Apr 19, 2019 at 2:48 PM Christian Brauner
> > > wrote:
> > > >
> > > > On Fri,
From: Prakhar Srivastava
Signed-off-by: Prakhar Srivastava
---
remove enaums to control type of buffers entries, instead pass the event name
to be used.
include/linux/ima.h | 10 ++
kernel/kexec_file.c | 3 +++
security/integrity/ima/ima.h | 2 +-
From: Prakhar Srivastava
Signed-off-by: Prakhar Srivastava
---
This adds a new ima hook ima_buffer_check and a policy entry BUFFER_CHECK.
This enables buffer has measurements into ima log
Documentation/ABI/testing/ima_policy | 1 +
include/linux/ima.h | 13 +++-
From: Prakhar Srivastava
Signed-off-by: Prakhar Srivastava
---
since cmdline args can be same for multiple kexec, log entry
hash will collide. Prepend the kernel file name to the cmdline args to
distinguish between cmdline args passed to subsequent kexec calls
kernel/kexec_core.c | 57
On Fri, Apr 19, 2019 at 4:12 PM Christian Brauner wrote:
>
> On Sat, Apr 20, 2019 at 12:46 AM Daniel Colascione wrote:
> >
> > On Fri, Apr 19, 2019 at 3:02 PM Christian Brauner
> > wrote:
> > >
> > > On Fri, Apr 19, 2019 at 11:48 PM Christian Brauner
> > > wrote:
> > > >
> > > > On Fri, Apr
The pull request you sent on Fri, 19 Apr 2019 17:29:18 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/dennis/percpu.git for-5.1-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4c3f49ae1306c05e91211c06feddfd0a4a57fabd
Thank you!
--
Deet-doot-dot, I am a
On Fri, Apr 19, 2019 at 4:20 PM Christian Brauner wrote:
>
> On Sat, Apr 20, 2019 at 1:11 AM Linus Torvalds
> wrote:
> >
> > It's also worth noting that POLLERR/POLLHUP/POLLNVAL cannot be masked
> > for "poll()". Even if you only ask for POLLIN/POLLOUT, you will always
> > get POLLERR/POLLHUP
On Fri, Apr 19, 2019 at 4:33 PM Linus Torvalds
wrote:
>
> On Fri, Apr 19, 2019 at 4:20 PM Christian Brauner
> wrote:
> >
> > On Sat, Apr 20, 2019 at 1:11 AM Linus Torvalds
> > wrote:
> > >
> > > It's also worth noting that POLLERR/POLLHUP/POLLNVAL cannot be masked
> > > for "poll()". Even if
From: Ralph Campbell
The mmotm patch [1] adds hugetlbfs support for HMM but the initial
PFN used to fill the HMM range->pfns[] array doesn't properly
compute the starting PFN offset.
This can be tested by running test-hugetlbfs-read from [2].
Fix the PFN offset by adjusting the page offset by
On Fri, Apr 19, 2019 at 4:02 PM Christian Brauner wrote:
>
> On Sat, Apr 20, 2019 at 12:35 AM Daniel Colascione wrote:
> >
> > On Fri, Apr 19, 2019 at 2:48 PM Christian Brauner
> > wrote:
> > >
> > > On Fri, Apr 19, 2019 at 11:21 PM Daniel Colascione
> > > wrote:
> > > >
> > > > On Fri, Apr
One of the use-cases is building kselftest and then installing.
Adding a target to just build the tests from the main Makefile
will help users and makes it easier.
Signed-off-by: Shuah Khan
---
Makefile | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Makefile b/Makefile
index
Build and run gpio when output directory is the src dir. gpio has
dependency on tools/gpio and builds tools/gpio objects in the src
directory in all cases making the src repo dirty even when object
relocation is specified.
This fixes the following commands from generating gpio objects in
the
On 4/19/19 1:40 AM, Ingo Molnar wrote:
* Subhra Mazumdar wrote:
I see similar improvement with this patch as removing the condition I
earlier mentioned. So that's not needed. I also included the patch for the
priority fix. For 2 DB instances, HT disabling stands at -22% for 32 users
(from
On Sat, Apr 20, 2019 at 1:11 AM Linus Torvalds
wrote:
>
> On Fri, Apr 19, 2019 at 2:20 PM Joel Fernandes wrote:
> >
> > According to Linus, POLLHUP usually indicates that something is readable:
>
> Note that if you use the legacy interfaces (ie "select()"), then even
> just a plain POLLHUP will
On Sat, Apr 20, 2019 at 12:46 AM Daniel Colascione wrote:
>
> On Fri, Apr 19, 2019 at 3:02 PM Christian Brauner
> wrote:
> >
> > On Fri, Apr 19, 2019 at 11:48 PM Christian Brauner
> > wrote:
> > >
> > > On Fri, Apr 19, 2019 at 11:21 PM Daniel Colascione
> > > wrote:
> > > >
> > > > On Fri,
On Fri, Apr 19, 2019 at 2:20 PM Joel Fernandes wrote:
>
> According to Linus, POLLHUP usually indicates that something is readable:
Note that if you use the legacy interfaces (ie "select()"), then even
just a plain POLLHUP will always just show as "readable".
So for a lot of applications, it
On Sat, Apr 20, 2019 at 4:03 AM Ludovic Desroches
wrote:
>
> On Mon, Apr 15, 2019 at 05:14:50PM +0200, Alexandre Belloni wrote:
> > External E-Mail
> >
> >
> > On 08/04/2019 16:54:26+0900, Masahiro Yamada wrote:
> > > is only generated and included
> > > by arch/arm/mach-at91/, so it does not
On Fri, 19 Apr 2019 22:52:01 +0200 (CEST)
Thomas Gleixner wrote:
> On Fri, 19 Apr 2019, Jacob Pan wrote:
> > On Fri, 19 Apr 2019 10:57:10 +0200 (CEST)
> > Thomas Gleixner wrote:
> > > On Fri, 19 Apr 2019, Daniel Drake wrote:
> > > > 0x7F vs 0x7FFF, is that intentional?
> > >
>
Hi Nick,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.1-rc5 next-20190418]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Sat, Apr 20, 2019 at 12:35 AM Daniel Colascione wrote:
>
> On Fri, Apr 19, 2019 at 2:48 PM Christian Brauner
> wrote:
> >
> > On Fri, Apr 19, 2019 at 11:21 PM Daniel Colascione
> > wrote:
> > >
> > > On Fri, Apr 19, 2019 at 1:57 PM Christian Brauner
> > > wrote:
> > > >
> > > > On Fri,
On Fri, Apr 19, 2019 at 10:43:35AM +0100, Mel Gorman wrote:
> DISCONTIG is essentially deprecated and even parisc plans to move to
> SPARSEMEM so there is no need to be fancy, this patch simply disables
> watermark boosting by default on DISCONTIGMEM.
I don't think parisc is the only arch which
On Fri, Apr 19, 2019 at 02:02:07PM +0200, Peter Zijlstra wrote:
> On Fri, Apr 19, 2019 at 12:26:47PM +0200, Peter Zijlstra wrote:
> > I thought of a horrible horrible alternative:
>
> Hurm, that's broken as heck. Let me try again.
So I can't make that scheme work, it all ends up wanting to have
On almost all places, we're including ReST files without the
extension.
Let's remove the extension here as well, in order to use just
one standard.
Suggested-by: Jani Nikula
---
Documentation/hwmon/index.rst | 316 +-
1 file changed, 158 insertions(+), 158
On Thu, Apr 18, 2019 at 05:42:55PM +0200, Thomas Gleixner wrote:
> On Thu, 18 Apr 2019, Josh Poimboeuf wrote:
> > Another idea I had (but never got a chance to work on) was to extend the
> > x86 unwind interface to all arches. So instead of the callbacks, each
> > arch would implement something
On Fri, Apr 19, 2019 at 12:26:47PM +0200, Peter Zijlstra wrote:
> I thought of a horrible horrible alternative:
Hurm, that's broken as heck. Let me try again.
On Fri, Apr 19, 2019 at 3:02 PM Christian Brauner wrote:
>
> On Fri, Apr 19, 2019 at 11:48 PM Christian Brauner
> wrote:
> >
> > On Fri, Apr 19, 2019 at 11:21 PM Daniel Colascione
> > wrote:
> > >
> > > On Fri, Apr 19, 2019 at 1:57 PM Christian Brauner
> > > wrote:
> > > >
> > > > On Fri,
Hello,
Commit f8a0590f fix some part of this issue.
I will send out V3 base on this commit in linux-kselftest next branch.
Thank you.
On Fri, Apr 19, 2019 at 9:20 PM shuah wrote:
>
> On 4/19/19 7:12 AM, Po-Hsu Lin wrote:
> > Test files created by test_create*() tests will stay in the
> >
Test files created by test_create*() tests will stay in the
$efivarfs_mount directory unless the system was rebooted.
When the tester tries to run this efivarfs test again on the same
system, the immutable characteristics in that directory will cause some
"Operation not permitted" noises and a
Test files created by test_create() and test_create_empty() tests will
stay in the $efivarfs_mount directory until the system was rebooted.
When the tester tries to run this efivarfs test again on the same
system, the immutable characteristics in that directory will cause some
"Operation not
On 4/18/19 5:42 AM, Hans de Goede wrote:
>> On 4/8/19 2:16 AM, Hans de Goede wrote:>
>>>
>>> Hmm, interesting so you have hibernation working on a T100TA
>>> (with 5.0 + 02e45646d53b reverted), right ?
>>>
> Still since my patch is regressing things for you I will try to
> take a look at this
From: Ralph Campbell
The mmotm patch [1] adds hugetlbfs support for HMM but the initial
PFN used to fill the HMM range->pfns[] array doesn't properly
compute the starting PFN offset.
This can be tested by running test-hugetlbfs-read from [2].
Fix the PFN offset by adjusting the page offset by
On Fri, Apr 19, 2019 at 3:18 PM Christian Brauner wrote:
>
> On Sat, Apr 20, 2019 at 12:08 AM Daniel Colascione wrote:
> >
> > On Fri, Apr 19, 2019 at 2:45 PM Joel Fernandes
> > wrote:
> > >
> > > On Fri, Apr 19, 2019 at 02:24:09PM -0700, Daniel Colascione wrote:
> > > > On Fri, Apr 19, 2019
On Fri, Apr 19, 2019 at 2:48 PM Christian Brauner wrote:
>
> On Fri, Apr 19, 2019 at 11:21 PM Daniel Colascione wrote:
> >
> > On Fri, Apr 19, 2019 at 1:57 PM Christian Brauner
> > wrote:
> > >
> > > On Fri, Apr 19, 2019 at 10:34 PM Daniel Colascione
> > > wrote:
> > > >
> > > > On Fri, Apr
On 04/15/2019 06:35 AM, Paolo Bonzini wrote:
As mentioned in the comment, there are some special cases where we can simply
clear the TPR shadow bit from the CPU-based execution controls in the vmcs02.
Handle them so that we can remove some XFAILs from vmx.flat.
Signed-off-by: Paolo Bonzini
Quoting Leo Yan (2019-03-20 03:05:08)
> clk_gate_ufs_subsys is a system bus clock, turning off it will
> introduce lockup issue during system suspend flow. Let's mark
> clk_gate_ufs_subsys as critical clock, thus keeps it on during
> system suspend and resume.
>
> Fixes: d374e6fd5088 ("clk:
Quoting Dmitry Osipenko (2019-04-19 04:42:26)
> Initially Common Clock Framework isn't aware of the clock-enable status,
> this results in enabling of clocks that were enabled by bootloader. This
> is not a big deal for a regular clock-gates, but for PLL's it may have
> some unpleasant
On Sat, Apr 20, 2019 at 12:08 AM Daniel Colascione wrote:
>
> On Fri, Apr 19, 2019 at 2:45 PM Joel Fernandes wrote:
> >
> > On Fri, Apr 19, 2019 at 02:24:09PM -0700, Daniel Colascione wrote:
> > > On Fri, Apr 19, 2019 at 2:20 PM Joel Fernandes
> > > wrote:
> > > >
> > > > On Fri, Apr 19, 2019
This adds a code for turning on chicken bit 11, which appears to avoid
a potential CPU deadlock that could occur. The exact set of
instruction needed to trigger this errata is not totaly known but we
have a high level of confidence that the problem is fixed by setting
chicken bit 11.
All details
From: Sonny Rao
This adds support for working around errata A12 857271 / A17 857272.
These errata were causing hangs on rk3288-based Chromebooks and it was
confirmed that this workaround fixed the problems. In the Chrome OS
3.14 kernel [1] this erratum was known as ERRATA_FOOBAR due to lack of
Quoting Stephen Boyd (2019-04-12 11:31:49)
> Some clk providers are simple DT nodes that only have a 'clocks'
> property without having an associated 'clock-names' property. In these
> cases, we want to let these clk providers point to their parent clks
> without having to dereference the 'clocks'
Quoting Stephen Boyd (2019-04-12 11:31:45)
> We'd like to chain this in places where the 'dev' argument might be
> NULL. Let this function take a NULL 'dev' so this can work.
>
> Cc: Miquel Raynal
> Cc: Jerome Brunet
> Cc: Russell King
> Cc: Michael Turquette
> Cc: Jeffrey Hugo
> Cc: Chen-Yu
Quoting Stephen Boyd (2019-04-12 11:31:48)
> In addition to looking for DT based parents, support clkdev based
> clk_lookups. This should allow non-DT based clk drivers to participate
> in the parent lookup process.
>
> Cc: Miquel Raynal
> Cc: Jerome Brunet
> Cc: Russell King
> Cc: Michael
Quoting Stephen Boyd (2019-04-12 11:31:50)
> Convert this driver to a more modern way of specifying parents now that
> we have a way to specify clk parents by DT index. This lets us nicely
> avoid a problem where a parent clk name isn't know because the parent
> clk hasn't been registered yet.
>
Quoting Stephen Boyd (2019-04-12 11:31:46)
> In some circumstances drivers register clks early and don't have access
> to a struct device because the device model isn't initialized yet. Add
> an API to let drivers register clks associated with a struct device_node
> so that these drivers can
Quoting Stephen Boyd (2019-04-12 11:31:47)
> The common clk framework is lacking in ability to describe the clk
> topology without specifying strings for every possible parent-child
> link. There are a few drawbacks to the current approach:
>
> 1) String comparisons are used for everything,
Quoting Stephen Boyd (2019-04-12 11:31:44)
> Split out the body of the clk_register() function so it can be shared
> between the different types of registration APIs (DT, device).
>
> Cc: Miquel Raynal
> Cc: Jerome Brunet
> Cc: Russell King
> Cc: Michael Turquette
> Cc: Jeffrey Hugo
> Cc:
Quoting Stephen Boyd (2019-04-12 11:31:43)
> We don't need to hold the 'clocks_mutex' here when we're creating a clk
> pointer from a clk_lookup structure. Instead, we just need to make sure
> that the lookup doesn't go away while we dereference the lookup pointer
> to extract the clk_hw pointer
On Fri, Apr 19, 2019 at 2:45 PM Joel Fernandes wrote:
>
> On Fri, Apr 19, 2019 at 02:24:09PM -0700, Daniel Colascione wrote:
> > On Fri, Apr 19, 2019 at 2:20 PM Joel Fernandes
> > wrote:
> > >
> > > On Fri, Apr 19, 2019 at 10:57:11PM +0200, Christian Brauner wrote:
> > > > On Fri, Apr 19, 2019
On Fri, Apr 19, 2019 at 11:48 PM Christian Brauner wrote:
>
> On Fri, Apr 19, 2019 at 11:21 PM Daniel Colascione wrote:
> >
> > On Fri, Apr 19, 2019 at 1:57 PM Christian Brauner
> > wrote:
> > >
> > > On Fri, Apr 19, 2019 at 10:34 PM Daniel Colascione
> > > wrote:
> > > >
> > > > On Fri, Apr
On Fri, Apr 19, 2019 at 03:07:45PM -0500, Bjorn Helgaas wrote:
> On Fri, Feb 08, 2019 at 10:24:12AM -0600, Alexandru Gagniuc wrote:
> > We used to first parse all the _HPP and _HPX tables before using the
> > information to program registers of PCIe devices. Up until HPX type 2,
> > there was only
On Fri, Apr 19, 2019 at 11:20 PM Joel Fernandes wrote:
>
> On Fri, Apr 19, 2019 at 10:57:11PM +0200, Christian Brauner wrote:
> > On Fri, Apr 19, 2019 at 10:34 PM Daniel Colascione
> > wrote:
> > >
> > > On Fri, Apr 19, 2019 at 12:49 PM Joel Fernandes
> > > wrote:
> > > >
> > > > On Fri, Apr
On 2019-04-19 14:34, Thomas Gleixner wrote:
> And how so? You create writeable AND executable memory. That's a nono and
> you can argue in circles, that's not going to change with any of your
> proposed changes.
On 2019-04-19 14:38, Thomas Gleixner wrote:
> You are working around LSM nothing else
The mm-of-the-moment snapshot 2019-04-19-14-53 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
Hi Madhumitha,
Am 19.04.19 um 23:23 schrieb Madhumitha Prabakaran:
> Remove unnecessary variable and replace return type.
>
> Issue suggested by Coccinelle.
>
> Signed-off-by: Madhumitha Prabakaran
> ---
> drivers/staging/vc04_services/bcm2835-camera/controls.c | 7 +--
> 1 file changed, 1
On Fri, Apr 19, 2019 at 11:21 PM Daniel Colascione wrote:
>
> On Fri, Apr 19, 2019 at 1:57 PM Christian Brauner
> wrote:
> >
> > On Fri, Apr 19, 2019 at 10:34 PM Daniel Colascione
> > wrote:
> > >
> > > On Fri, Apr 19, 2019 at 12:49 PM Joel Fernandes
> > > wrote:
> > > >
> > > > On Fri, Apr
On Fri, Apr 19, 2019 at 02:24:09PM -0700, Daniel Colascione wrote:
> On Fri, Apr 19, 2019 at 2:20 PM Joel Fernandes wrote:
> >
> > On Fri, Apr 19, 2019 at 10:57:11PM +0200, Christian Brauner wrote:
> > > On Fri, Apr 19, 2019 at 10:34 PM Daniel Colascione
> > > wrote:
> > > >
> > > > On Fri, Apr
On Fri, 19 Apr 2019, Jethro Beekman wrote:
> On 2019-04-19 14:31, Andy Lutomirski wrote:
> > I do think we need to follow LSM rules. But my bigger point is that
> > there are policies that don’t allow JIT at all. I think we should
> > arrange the SGX API so it’s still usable when such a policy is
On 2019-04-19 14:31, Andy Lutomirski wrote:
> I do think we need to follow LSM rules. But my bigger point is that there
> are policies that don’t allow JIT at all. I think we should arrange the SGX
> API so it’s still usable when such a policy is in effect.
I don't think we need to arrange
On Fri, 19 Apr 2019, Jethro Beekman wrote:
> On 2019-04-19 14:15, Andy Lutomirski wrote:
> > With plain mmap() + mprotect(), the LSM will prevent you from making
> > memory that *was* writable executable. This is by design and SELinux
> > supports it. I don’t remember the name of the associated
1 - 100 of 522 matches
Mail list logo
