On 09/14/2016 08:36 PM, Stephen Boyd wrote:
> On 08/29, gabriel.fernan...@st.com wrote:
>> From: Gabriel Fernandez
>>
>> v3:
>> - Rebase to v4.8-rc1
>> - Tipo fix in st,clkgen-pll.txt
>> - Add Ack of Peter for the series
>> - Add missed patch: "ARM: DT: STiH4xx: Simplify clock binding of
In the debate about how to support persistent memory applications that
want to use hardware-platform memory-media persistence
rules/cpu-instructions rather than filesystem data intergrity system
calls [1], one of the consistent requests is to move these applications
to use a device file rather than
There are cases, particularly for testing and validating a configuration
to know the hardware mapping geometry of the pages in a given process
address range. Consider filesystem-dax where a configuration needs to
take care to align partitions and block allocations before huge page
mappings might b
Introduce a new vma flag to indicate the property of device-dax VMAs
that, while file-backed, do not require notification to a filesystem
agent to sync metadata after a fault. In particular this enables
persistent memory applications to know if they can commit transactions
to media via cpu instruc
The DAX property, page cache bypass, of a VMA is only detectable via the
vma_is_dax() helper to check the S_DAX inode flag. However, this is
only available internal to the kernel and is a property that userspace
applications would like to interrogate.
Yes, this new VM_DAX flag is only available o
Hi all,
Changes since 20160914:
The kbuild tree still had its build warnings for PowerPC, for which I
applied a supplied patch. It also gained a build failure for which I
applied a patch.
The amlogic tree gained a conflict against the pinctrl tree.
The pm tree lost its build failure.
Non
2016-09-15 14:29 GMT+08:00 Paolo Bonzini :
>
>
> On 15/09/2016 03:19, Wanpeng Li wrote:
>> 2016-09-14 20:03 GMT+08:00 Radim Krčmář :
>>> 2016-09-14 11:40+0200, Paolo Bonzini:
On 14/09/2016 09:58, Wanpeng Li wrote:
> From: Wanpeng Li
>
> I observed that kvmvapic(to optimize flexpri
* Andy Lutomirski wrote:
> This will prevent a crash if the target task dies before or while
> dumping its stack once we start freeing task stacks early.
>
> Signed-off-by: Andy Lutomirski
> ---
> arch/x86/kernel/stacktrace.c | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch
On 15/09/2016 06:08, Mika Penttilä wrote:
> On 09/14/2016 10:58 AM, Wanpeng Li wrote:
>> From: Wanpeng Li
>>
>> I observed that kvmvapic(to optimize flexpriority=N or AMD) is used
>> to boost TPR access when testing kvm-unit-test/eventinj.flat tpr case
>> on my haswell desktop (w/ flexpriority,
On 15/09/2016 03:19, Wanpeng Li wrote:
> 2016-09-14 20:03 GMT+08:00 Radim Krčmář :
>> 2016-09-14 11:40+0200, Paolo Bonzini:
>>> On 14/09/2016 09:58, Wanpeng Li wrote:
From: Wanpeng Li
I observed that kvmvapic(to optimize flexpriority=N or AMD) is used
to boost TPR access when
> Subject: Re: [PATCH v3 1/4] tpm/tpm_crb: implement tpm crb idle state
>
> On Mon, Sep 12, 2016 at 04:04:18PM +0300, Tomas Winkler wrote:
> > The register TPM_CRB_CTRL_REQ_x contains bits goIdle and cmdReady for
> > SW to indicate that the device can enter or should exit the idle state.
> >
> > T
On Wed, Sep 14, 2016 at 10:55:03PM -0700, Darrick J. Wong wrote:
> On Mon, Sep 12, 2016 at 11:40:35AM +1000, Dave Chinner wrote:
> > On Thu, Sep 08, 2016 at 04:56:36PM -0600, Ross Zwisler wrote:
> > > On Wed, Sep 07, 2016 at 09:32:36PM -0700, Dan Williams wrote:
> > > > My understanding is that it
On Mon, Sep 12, 2016 at 04:04:20PM +0300, Tomas Winkler wrote:
> This is preparation step for implementing tpm crb
> runtime pm. We need to have tpm chip allocated
> and populated before we access the runtime handlers.
>
> Signed-off-by: Tomas Winkler
Use pm_runtime_put().
Tested-by: Jarkko Sak
On Wed, 2016-09-14 at 23:02 -0500, NTU wrote:
> [ 26.542980] Call Trace:
> [ 26.542983] [] ? 0xa7fbd7c1
> [ 26.542985] [] ? 0xa7f17d35
> [ 26.542986] [] ? 0xa796c115
> [ 26.542988] [] ? 0xa7633d86
> [ 26.542989] [] ? 0xa796c0a6
...
The stack
On Mon, Sep 12, 2016 at 04:04:19PM +0300, Tomas Winkler wrote:
> There is a HW bug in Skylake, and Broxton PCH Intel PTT device, where
> most of the registers in the control area except START, REQUEST, CANCEL,
> and LOC_CTRL lost retention when the device is in the idle state. Hence
> we need to br
On 15/09/2016 07:54, Raslan, KarimAllah wrote:
>
>> On Jun 22, 2016, at 3:41 PM, Paolo Bonzini wrote:
>>
>>
>>
>> On 22/06/2016 04:34, KarimAllah Ahmed wrote:
>>> pfn_valid check is not sufficient because it only checks if a page has a
>>> struct
>>> page or not, if for example "mem=" was pass
From: Wanpeng Li
===
[ INFO: suspicious RCU usage. ]
4.8.0-rc6+ #5 Not tainted
---
./arch/x86/include/asm/msr-trace.h:47 suspicious rcu_dereference_check() usage!
other info that might help us debug this:
RCU used illegally from idle CPU!
* Andy Lutomirski wrote:
> From: Linus Torvalds
>
> thread_info may move in the future, so use the accessors.
>
> Andy Lutomirski wrote this changelog message and changed
> "task_thread_info(child)->cpu" to "task_cpu(child)".
>
> Message-Id:
>
> Signed-off-by: Andy Lutomirski
Like the pr
On Mon, Sep 12, 2016 at 04:04:18PM +0300, Tomas Winkler wrote:
> The register TPM_CRB_CTRL_REQ_x contains bits goIdle and cmdReady for
> SW to indicate that the device can enter or should exit the idle state.
>
> The legacy ACPI-start (SMI + DMA) based devices do not support these
> bits and the i
* Andy Lutomirski wrote:
> From: Linus Torvalds
>
> It was a nice optimization while it lasted, but thread_info is moving
> and this optimization will no longer work.
>
> Quoting Linus:
>
> Oh Gods, Andy. That pt_regs_to_thread_info() thing made me want
> to do unspeakable acts on a
On Tue, Sep 13, 2016 at 12:32:29PM -0600, Shuah Khan wrote:
> On 09/12/2016 09:29 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.7.4 release.
> > There are 59 patches in this series, all will be posted as a response
> > to this one. If anyone has any issue
On Wed, Sep 14, 2016 at 11:20:54PM +0100, Ben Hutchings wrote:
> On Mon, 2016-09-12 at 18:58 +0200, Greg Kroah-Hartman wrote:
> > Many thanks for the majority of these patches to Sasha Levin, who dug
> > them out of Canonical's 4.4 kernel tree. I have no idea why they never
> > sent them in for in
Hi all,
After merging the dax-misc tree, today's linux-next build (powerpc
ppc44x_defconfig) failed like this:
arch/powerpc/kernel/built-in.o: In function `__ksymtab_clear_pages':
(___ksymtab+clear_pages+0x0): undefined reference to `clear_pages'
Caused by commit
9445aa1a3062 ("ppc: move expo
On Thu, Sep 15, 2016 at 11:12:08AM +0800, bobcao3 wrote:
> Signed-off-by: bobcao3
> ---
> drivers/gpu/drm/i915/i915_gem_gtt.c | 6
> drivers/gpu/drm/i915/i915_gem_stolen.c | 61
> -
> drivers/gpu/drm/i915/i915_reg.h | 6
> drivers/gpu/drm/
On Thu, Sep 15, 2016 at 12:03:48AM +0100, Aidan Thornton wrote:
> On 24 Jun 2016 16:10, "Greg KH" wrote:
> >
> > On Fri, Jun 24, 2016 at 01:42:24PM +0800, WCH Tech Group wrote:
> > > There are several reasons why we decided to revoke the old one after
> > > communicating with the author of
>
On Mon, Sep 12, 2016 at 11:40:35AM +1000, Dave Chinner wrote:
> On Thu, Sep 08, 2016 at 04:56:36PM -0600, Ross Zwisler wrote:
> > On Wed, Sep 07, 2016 at 09:32:36PM -0700, Dan Williams wrote:
> > > My understanding is that it is looking for the VM_MIXEDMAP flag which
> > > is already ambiguous for
> On Jun 22, 2016, at 3:41 PM, Paolo Bonzini wrote:
>
>
>
> On 22/06/2016 04:34, KarimAllah Ahmed wrote:
>> pfn_valid check is not sufficient because it only checks if a page has a
>> struct
>> page or not, if for example "mem=" was passed to the kernel some valid pages
>> won't have a struct
On Wed, Sep 14, 2016 at 7:43 PM, Vince Weaver wrote:
>
> so the skylake that was fuzzing finally is mostly locked up.
>
> Really hard to tell what's going, especially as KASLR made looking up the
> addresses a big pain.
>
I would think there is a way to disable KASLR for this kind of testing!
Whi
On 09/14/2016 03:39 AM, John Crispin wrote:
> Add support for the 2-bytes Qualcomm tag that gigabit switches such as
> the QCA8337/N might insert when receiving packets, or that we need
> to insert while targeting specific switch ports. The tag is inserted
> directly behind the ethernet header.
>
On Wed, Sep 14, 2016 at 10:42:50AM -0700, Stephen Boyd wrote:
> > >
> > > Hmm.. maybe the confusion is in which registers we should be able to
> > > access? Are we talking about the ULPI viewport MMIO register space or
> > > the ULPI registers that we access through the viewport? I have a
> > > hw
On Thu, Sep 15, 2016 at 10:15 AM, wrote:
> From: Vivek Gautam
a stale "--from " flag in my command added this line.
Will take care of it from next time.
>
> Adding missing reset lines for USB 3.0 PHY.
>
> Signed-off-by: Vivek Gautam
> ---
[snip]
--
Qualcomm Innovation Center, Inc. is a mem
On Wed, Sep 14, 2016 at 03:32:44PM +, Bharat Kumar Gogada wrote:
> On Thu, Sep 01, 2016 at 03:44:41PM +0530, Bharat Kumar Gogada wrote:
> > When built with MSI support the legacy domain reference is being
> > overwritten with MSI.
> > Instead creating two separate domains for MSI and legacy in
On Wed, Sep 14, 2016 at 09:38:16PM -0700, Andy Lutomirski wrote:
> On Wed, Sep 14, 2016 at 9:31 PM, Alexei Starovoitov
> wrote:
> > On Wed, Sep 14, 2016 at 09:08:57PM -0700, Andy Lutomirski wrote:
> >> On Wed, Sep 14, 2016 at 9:00 PM, Alexei Starovoitov
> >> wrote:
> >> > On Wed, Sep 14, 2016 at
From: Vivek Gautam
Adding missing reset lines for USB 3.0 PHY.
Signed-off-by: Vivek Gautam
---
- Build tested on clk-next branch.
- Tested with my wip branch for usbphy that is available @[1].
[1]https://github.com/vivekgautam1/linux/tree/linaro/integration-linux-qcomlt-usbphy-wip
drivers
On Wed, Sep 14, 2016 at 9:31 PM, Alexei Starovoitov
wrote:
> On Wed, Sep 14, 2016 at 09:08:57PM -0700, Andy Lutomirski wrote:
>> On Wed, Sep 14, 2016 at 9:00 PM, Alexei Starovoitov
>> wrote:
>> > On Wed, Sep 14, 2016 at 07:27:08PM -0700, Andy Lutomirski wrote:
>> >> >> >
>> >> >> > This RFC handl
On Mon, 12 Sep 2016 21:07:40 -0400
David Long wrote:
>
> After the patch the function reads as follows:
>
> > enum kprobe_insn __kprobes
> > arm_kprobe_decode_insn(kprobe_opcode_t *addr, struct arch_specific_insn
> > *asi)
> > {
> > enum kprobe_insn decoded;
> > kprobe_opcode_t insn = l
On Wed, Sep 14, 2016 at 09:08:57PM -0700, Andy Lutomirski wrote:
> On Wed, Sep 14, 2016 at 9:00 PM, Alexei Starovoitov
> wrote:
> > On Wed, Sep 14, 2016 at 07:27:08PM -0700, Andy Lutomirski wrote:
> >> >> >
> >> >> > This RFC handle both cgroup and seccomp approaches in a similar way. I
> >> >> >
2016-09-15 12:08 GMT+08:00 Mika Penttilä :
> On 09/14/2016 10:58 AM, Wanpeng Li wrote:
>> From: Wanpeng Li
>>
>> I observed that kvmvapic(to optimize flexpriority=N or AMD) is used
>> to boost TPR access when testing kvm-unit-test/eventinj.flat tpr case
>> on my haswell desktop (w/ flexpriority, w
On 09/14/2016 10:58 AM, Wanpeng Li wrote:
> From: Wanpeng Li
>
> I observed that kvmvapic(to optimize flexpriority=N or AMD) is used
> to boost TPR access when testing kvm-unit-test/eventinj.flat tpr case
> on my haswell desktop (w/ flexpriority, w/o APICv). Commit (8d14695f9542
> x86, apicv: a
On Wed, 2016-09-14 at 21:08 -0500, Eric W. Biederman wrote:
> Ian Kent writes:
>
> > On Wed, 2016-09-14 at 12:28 -0500, Eric W. Biederman wrote:
> > > Ian Kent writes:
> > >
> > > > If an automount mount is clone(2)ed into a file system that is
> > > > propagation private, when it later expires
On Wed, Sep 14, 2016 at 9:00 PM, Alexei Starovoitov
wrote:
> On Wed, Sep 14, 2016 at 07:27:08PM -0700, Andy Lutomirski wrote:
>> >> >
>> >> > This RFC handle both cgroup and seccomp approaches in a similar way. I
>> >> > don't see why building on top of cgroup v2 is a problem. Is there
>> >> > sec
We have observed on few x86 machines with rtc-cmos device that
hpet_rtc_interrupt() is called just after irq registration and before
cmos_do_probe() could call hpet_rtc_timer_init().
So, neither hpet_default_delta nor hpet_t1_cmp is initialized by the time
interrupt is raised in the given situatio
Hello,
I've been testing out KASAN and experimenting with some other new
config settings related to security and kernel hardening, I ran into a
problem though and I've attached a snippet of my kernel log of the
stack trace as well as my kernel config. Also intermittently (every
few seconds just ab
On Wed, Sep 14, 2016 at 07:27:08PM -0700, Andy Lutomirski wrote:
> >> >
> >> > This RFC handle both cgroup and seccomp approaches in a similar way. I
> >> > don't see why building on top of cgroup v2 is a problem. Is there
> >> > security issues with delegation?
> >>
> >> What I mean is: cgroup v2
> -Original Message-
> From: Eugeniy Paltsev [mailto:eugeniy.palt...@synopsys.com]
> Sent: Wednesday, September 14, 2016 11:11 PM
> To: dmaeng...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; Appana Durga Kedareswara Rao
> ; vinod.k...@intel.com; dan.j.willi...@intel.com;
> andriy.s
On Thu, 15 Sep 2016 12:31:33 +1000
Dave Chinner wrote:
> On Wed, Sep 14, 2016 at 08:19:36PM +1000, Nicholas Piggin wrote:
> > On Wed, 14 Sep 2016 17:39:02 +1000
> > Dave Chinner wrote:
> > > Ok, looking back over your example, you seem to be suggesting a new
> > > page fault behaviour is requi
> -Original Message-
> From: Leon Romanovsky [mailto:l...@kernel.org]
> Sent: Wednesday, September 14, 2016 6:05 AM
> To: Salil Mehta
> Cc: dledf...@redhat.com; Huwei (Xavier); oulijun; Zhuangyuzeng (Yisen);
> xuwei (O); mehta.salil@gmail.com; linux-r...@vger.kernel.org;
> linux-kerne
Many embedded systems typically don't need them. This removes about
22KB from the kernel binary size on ARM when configured out.
Corresponding syscalls are routed to a stub logging the attempt to
use those syscalls which should be enough of a clue if they were
disabled without proper consideratio
Hi Matias,
After merging the lightnvm tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/lightnvm/sysfs.c: In function 'nvm_sysfs_register_dev':
drivers/lightnvm/sysfs.c:184:2: warning: ignoring return value of 'device_add',
declared with attribute warn_unused_re
> -Original Message-
> From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma-
> ow...@vger.kernel.org] On Behalf Of Leon Romanovsky
> Sent: Tuesday, September 13, 2016 8:00 AM
> To: Salil Mehta
> Cc: dledf...@redhat.com; Huwei (Xavier); oulijun; Zhuangyuzeng (Yisen);
> xuwei (O); meht
From: Wei Yongjun
There is a error message within devm_ioremap_resource
already, so remove the dev_err call to avoid redundant
error message.
Signed-off-by: Wei Yongjun
---
drivers/mailbox/platform_mhu.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/mailbox/pla
From: Wei Yongjun
In case of error, the function blk_mq_alloc_request() or
blk_mq_init_queue() returns ERR_PTR() not NULL. The NULL
test in the return value check should be replaced with
IS_ERR().
Fixes: fd8383fd88a2 ("nbd: convert to blkmq")
Signed-off-by: Wei Yongjun
---
drivers/block/nbd.c
From: Wei Yongjun
There is a error message within devm_ioremap_resource
already, so remove the dev_err call to avoid redundant
error message.
Signed-off-by: Wei Yongjun
---
drivers/gpu/drm/sun4i/sun4i_backend.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/gpu/
On Mon, Aug 29, 2016 at 5:38 AM, Eric W. Biederman
wrote:
> David Miller writes:
>
>> From: Dmitry Torokhov
>> Date: Tue, 16 Aug 2016 15:33:10 -0700
>>
>>> There are objects in /sys hierarchy (/sys/class/net/) that logically belong
>>> to a namespace/container. Unfortunately all sysfs objects st
Signed-off-by: bobcao3
---
drivers/gpu/drm/i915/i915_gem_gtt.c | 6
drivers/gpu/drm/i915/i915_gem_stolen.c | 61 -
drivers/gpu/drm/i915/i915_reg.h | 6
drivers/gpu/drm/i915/intel_ringbuffer.c | 19 +-
4 files changed, 59 insertions(
Hi Rafael,
On Wed, Sep 14, 2016 at 5:50 PM, Rafael J. Wysocki wrote:
> On Wednesday, September 14, 2016 04:08:28 PM Hoan Tran wrote:
>> This patch fixes overflow issue when calculating the desired_perf.
>>
>> Signed-off-by: Hoan Tran
>> ---
>> drivers/cpufreq/cppc_cpufreq.c | 3 ++-
>> 1 file c
so the skylake that was fuzzing finally is mostly locked up.
Really hard to tell what's going, especially as KASLR made looking up the
addresses a big pain.
The best I can tell things are getting wedged somehow in
perf_cgroup_switch() while interrupts are disabled. Interrupts are never
getti
On Wed, Sep 14, 2016 at 08:19:36PM +1000, Nicholas Piggin wrote:
> On Wed, 14 Sep 2016 17:39:02 +1000
> Dave Chinner wrote:
> > Ok, looking back over your example, you seem to be suggesting a new
> > page fault behaviour is required from filesystems that has not been
> > described or explained, an
From: Wei Yongjun
Remove .owner field if calls are used which set it automatically.
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
Signed-off-by: Wei Yongjun
---
drivers/staging/fsl-mc/bus/fsl-mc-allocator.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/
On Wed, Sep 14, 2016 at 7:19 PM, Alexei Starovoitov
wrote:
> On Wed, Sep 14, 2016 at 06:25:07PM -0700, Andy Lutomirski wrote:
>> On Wed, Sep 14, 2016 at 3:11 PM, Mickaël Salaün wrote:
>> >
>> > On 14/09/2016 20:27, Andy Lutomirski wrote:
>> >> On Wed, Sep 14, 2016 at 12:24 AM, Mickaël Salaün wro
From: Wei Yongjun
Using list_del_init() instead of list_del() + INIT_LIST_HEAD().
Signed-off-by: Wei Yongjun
---
drivers/staging/fsl-mc/bus/fsl-mc-allocator.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/fsl-mc/bus/fsl-mc-allocator.c
b/drivers/stag
Ian Kent writes:
> On Wed, 2016-09-14 at 12:28 -0500, Eric W. Biederman wrote:
>> Ian Kent writes:
>>
>> > If an automount mount is clone(2)ed into a file system that is
>> > propagation private, when it later expires in the originating
>> > namespace subsequent calls to autofs ->d_automount()
On Wed, Sep 14, 2016 at 6:17 PM, Andy Lutomirski wrote:
> On Wed, Sep 14, 2016 at 3:03 PM, Kyle Huey wrote:
>> On Wed, Sep 14, 2016 at 2:35 PM, Dave Hansen
>> wrote:
>>> On 09/14/2016 02:01 PM, Kyle Huey wrote:
>
>>> Is any of this useful to optimize away at compile-time? We have config
>>> opt
From: Wei Yongjun
In case of error, the function ion_device_create() returns ERR_PTR() and
never returns NULL. The NULL test in the return value check should be
replaced with IS_ERR().
Signed-off-by: Wei Yongjun
---
drivers/staging/android/ion/hisilicon/hi6220_ion.c | 4 ++--
1 file changed, 2
On Wed, Sep 14, 2016 at 06:25:07PM -0700, Andy Lutomirski wrote:
> On Wed, Sep 14, 2016 at 3:11 PM, Mickaël Salaün wrote:
> >
> > On 14/09/2016 20:27, Andy Lutomirski wrote:
> >> On Wed, Sep 14, 2016 at 12:24 AM, Mickaël Salaün wrote:
> >>> Add a new flag CGRP_NO_NEW_PRIVS for each cgroup. This f
On Wed, Sep 14, 2016 at 6:54 PM, Andy Lutomirski wrote:
> On Wed, Sep 14, 2016 at 6:47 PM, Kyle Huey wrote:
>> On Wed, Sep 14, 2016 at 6:29 PM, Andy Lutomirski wrote:
>>> On Wed, Sep 14, 2016 at 2:01 PM, Kyle Huey wrote:
>
+
+int set_cpuid_mode(struct task_struct *task, unsigned long
in_exception_stack() does some bad, bad things just so the unwinder can
print different values for different areas of the debug exception stack.
There's no need to clarify where exactly on the stack it is. Just print
"#DB" and be done with it.
Signed-off-by: Josh Poimboeuf
---
arch/x86/kernel/
When an interrupt happens in entry code while running on a software irq
stack, and the irq stack was empty, regs->sp will contain the stack end
address (e.g., irq_stack_ptr). If the regs are passed to dump_trace(),
get_stack_info() will report STACK_TYPE_UNKNOWN, causing dump_trace() to
return pre
valid_stack_ptr() is buggy: it assumes that all stacks are of size
THREAD_SIZE, which is not true for exception stacks. So the
walk_stack() callbacks will need to know the location of the beginning
of the stack as well as the end.
Another issue is that in general the various features of a stack (
This is the last batch before the new unwinder.
Josh Poimboeuf (4):
x86/dumpstack: simplify in_exception_stack()
x86/dumpstack: add get_stack_info() interface
x86/dumpstack: support for unwinding empty irq stacks
x86/dumpstack: add recursion checking for all stacks
arch/x86/events/core.c
in_exception_stack() has some recursion checking which makes sure the
stack trace code never traverses a given exception stack more than once.
This prevents an infinite loop if corruption somehow causes a stack's
"next stack" pointer to point to itself (directly or indirectly).
The recursion check
On Wed, Sep 14, 2016 at 6:47 PM, Kyle Huey wrote:
> On Wed, Sep 14, 2016 at 6:29 PM, Andy Lutomirski wrote:
>> On Wed, Sep 14, 2016 at 2:01 PM, Kyle Huey wrote:
>>> +
>>> +int set_cpuid_mode(struct task_struct *task, unsigned long val)
>>> +{
>>> + /* Only disable/enable_cpuid() if it is
Hello Stephen,
Am Donnerstag, 15 September 2016, 11:43:08 schrieb Stephen Rothwell:
> Hi Thiago,
>
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index 2a1f0ce7c59a..dcd1679f3005 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -1792,6 +1792,11 @@ config SECCOMP
> >
On Wed, Sep 14, 2016 at 6:29 PM, Andy Lutomirski wrote:
> On Wed, Sep 14, 2016 at 2:01 PM, Kyle Huey wrote:
>> Intel supports faulting on the CPUID instruction in newer processors. Bit
>> 31 of MSR_PLATFORM_INFO advertises support for this feature. It is
>> documented in detail in Section 2.3.2 o
Hi Philipp,
On 09/06/2016 02:26 AM, Philipp Zabel wrote:
Hi Steve,
Am Mittwoch, den 17.08.2016, 17:50 -0700 schrieb Steve Longerbeam:
This patch implements complete image conversion support to ipu-ic,
with tiling to support scaling to and from images up to 4096x4096.
Image rotation is also su
Hi Thiago,
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 2a1f0ce7c59a..dcd1679f3005 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -1792,6 +1792,11 @@ config SECCOMP
>
> source kernel/Kconfig.hz
>
> +# x86 needs to relocate the purgatory after the checksum is calcu
On Wed, Sep 14, 2016 at 04:47:47PM +0100, Al Viro wrote:
> Fixes for broken uaccess primitives - mostly lack of proper zeroing
> in copy_from_user()/get_user()/__get_user(), but for several architectures
> there's more (broken clear_user() on frv and strncpy_from_user() on hexagon).
> All of
On Wed, Sep 14, 2016 at 2:01 PM, Kyle Huey wrote:
> Intel supports faulting on the CPUID instruction in newer processors. Bit
> 31 of MSR_PLATFORM_INFO advertises support for this feature. It is
> documented in detail in Section 2.3.2 of
> http://www.intel.com/content/dam/www/public/us/en/document
On Wed, Sep 14, 2016 at 3:11 PM, Mickaël Salaün wrote:
>
> On 14/09/2016 20:27, Andy Lutomirski wrote:
>> On Wed, Sep 14, 2016 at 12:24 AM, Mickaël Salaün wrote:
>>> Add a new flag CGRP_NO_NEW_PRIVS for each cgroup. This flag is initially
>>> set for all cgroup except the root. The flag is clear
On Wed, Sep 14, 2016 at 3:14 PM, Mickaël Salaün wrote:
>
> On 14/09/2016 20:29, Andy Lutomirski wrote:
>> On Wed, Sep 14, 2016 at 12:24 AM, Mickaël Salaün wrote:
>>> This third origin of hook call should cover all possible trigger paths
>>> (e.g. page fault). Landlock eBPF programs can then take
2016-09-14 20:03 GMT+08:00 Radim Krčmář :
> 2016-09-14 11:40+0200, Paolo Bonzini:
>> On 14/09/2016 09:58, Wanpeng Li wrote:
>>> From: Wanpeng Li
>>>
>>> I observed that kvmvapic(to optimize flexpriority=N or AMD) is used
>>> to boost TPR access when testing kvm-unit-test/eventinj.flat tpr case
>>>
On Wed, Sep 14, 2016 at 3:03 PM, Kyle Huey wrote:
> On Wed, Sep 14, 2016 at 2:35 PM, Dave Hansen
> wrote:
>> On 09/14/2016 02:01 PM, Kyle Huey wrote:
>> Is any of this useful to optimize away at compile-time? We have config
>> options for when we're running as a guest, and this seems like a fea
On Wed, Sep 14, 2016 at 2:01 PM, Kyle Huey wrote:
> Signed-off-by: Kyle Huey
> ---
> arch/x86/entry/syscalls/syscall_32.tbl | 1 +
> arch/x86/kernel/process.c | 80
> ++
> arch/x86/kernel/process_64.c | 66
> 3
On Wed, Sep 14, 2016 at 12:39:02PM +0200, John Crispin wrote:
> This patch contains initial support for the QCA8337 switch. It
> will detect a QCA8337 switch, if present and declared in the DT.
>
> Each port will be represented through a standalone net_device interface,
> as for other DSA switches
On Friday, September 09, 2016 10:25:30 AM Ulf Hansson wrote:
> + Mark
>
> On 8 September 2016 at 23:27, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Currently, there is a problem with handling cases where functional
> > dependencies between devices are involved.
> >
> > What I me
On Wed, 2016-09-14 at 12:28 -0500, Eric W. Biederman wrote:
> Ian Kent writes:
>
> > If an automount mount is clone(2)ed into a file system that is
> > propagation private, when it later expires in the originating
> > namespace subsequent calls to autofs ->d_automount() for that
> > dentry in the
On Wed, Sep 14, 2016 at 3:29 PM, Dmitry Safonov <0x7f454...@gmail.com> wrote:
> 2016-09-15 1:08 GMT+03:00 Kyle Huey :
>> On Wed, Sep 14, 2016 at 2:59 PM, Dmitry Safonov <0x7f454...@gmail.com> wrote:
>>> 2016-09-15 0:08 GMT+03:00 Kyle Huey :
Signed-off-by: Kyle Huey
---
arch/x86/ent
2016-09-14 17:42 GMT+08:00 Paolo Bonzini :
>
>
> On 14/09/2016 05:57, Wanpeng Li wrote:
>> 2016-09-14 4:43 GMT+08:00 Paolo Bonzini :
>>>
>>>
>>> On 13/09/2016 21:01, Radim Krcmar wrote:
kvm_handle_interrupt() does
interrupt_request |= CPU_INTERRUPT_HARD
which later calls
The buffer hand-over mechanism allows the currently running kernel to pass
data to kernel that will be kexec'd via a kexec segment. The second kernel
can check whether the previous kernel sent data and retrieve it.
This is the architecture-specific part.
Signed-off-by: Thiago Jung Bauermann
---
This shows how kernel code can use the kexec buffer passing mechanism
to pass information to the next kernel.
This patch is not intended to be committed.
[a...@linux-foundation.org: coding-style fixes]
Signed-off-by: Thiago Jung Bauermann
Signed-off-by: Andrew Morton
Signed-off-by: Thiago Jung
Currently, the purgatory segment is skipped from the kexec image checksum
because it is modified to include the calculated digest.
By putting the digest in a separate kexec segment, we can include the
purgatory segment in the kexec image verification since it won't need
to be modified anymore.
Wi
kexec_update_segment allows a given segment in kexec_image to have
its contents updated. This is useful if the current kernel wants to
send information to the next kernel that is up-to-date at the time of
reboot.
Before modifying the segment the image checksum is verified, and after
the segment is
Hello,
This version of the patch series fixes two issues:
1. The previous version modified struct kexec_segment, but that broke
the ABI for at least 32-bit ARM.
2. The previous version didn't include the hand-over buffer in the kexec
image checksum verification.
Now the kexec image checks
The buffer hand-over mechanism allows the currently running kernel to pass
data to kernel that will be kexec'd via a kexec segment. The second kernel
can check whether the previous kernel sent data and retrieve it.
This is the architecture-independent part of the feature.
Signed-off-by: Thiago Ju
On 09/08, Alexandre Belloni wrote:
> Hi,
>
> This patch set improves the slow clock controller driver.
>
> The first patch simply moves some code around to avoid having extern
> functions declared.
>
> The second patch adds support for the SCKC found on sama5d4 and later.
> It is notably missing
On Wednesday, September 14, 2016 04:08:28 PM Hoan Tran wrote:
> This patch fixes overflow issue when calculating the desired_perf.
>
> Signed-off-by: Hoan Tran
> ---
> drivers/cpufreq/cppc_cpufreq.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/cppc_
On 06/07, Boris Brezillon wrote:
> On Tue, 7 Jun 2016 18:36:21 +0200
> Alexandre Belloni wrote:
>
> > On 01/06/2016 at 16:15:01 -0700, Stephen Boyd wrote :
> > > Now that we have clk_hw based provider APIs to register clks, we
> > > can get rid of struct clk pointers in this driver, allowing us t
On 06/02, Eric Anholt wrote:
> Stephen Boyd writes:
>
> > Now that we have clk_hw based provider APIs to register clks, we
> > can get rid of struct clk pointers while registering clks in
> > these drivers, allowing us to move closer to a clear split of
> > consumer and provider clk APIs.
>
> Th
On Thu, Sep 15, 2016 at 08:09:23AM +0800, Ian Kent wrote:
> On Wed, 2016-09-14 at 12:28 -0500, Eric W. Biederman wrote:
> > Ian Kent writes:
> >
> > > If an automount mount is clone(2)ed into a file system that is
> > > propagation private, when it later expires in the originating
> > > namespace
On 10/29, Jon Mason wrote:
> Make the clocks visible options that can be selected by anyone. This
> avoids the problems of:
> 1) Select is a reverse dependency and is hard for people to understand
> and can sometimes be a pain to track down
> 2) Build coverage goes down because configs are h
1 - 100 of 977 matches
Mail list logo
