Instead of doing a linear search through the insn_table for each
instruction, use the opcode as direct index into the table. This will
give constant time lookup performance as the number of supported
opcodes increases. Make the tables const as they are only ever read.
For uasm-mips.c sort the tab
The enum opcode list started out sorted, but many elements have since
been added. Resort it.
No functional change.
Signed-off-by: David Daney
---
arch/mips/mm/uasm.c | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/arch/mips/mm/uasm.c b/arc
On Thu, 25 May 2017 10:08:33 -0400
Don Zickus wrote:
> On Thu, May 25, 2017 at 06:28:56PM +1000, Nicholas Piggin wrote:
> > After reconfiguring watchdog sysctls etc., architecture specific
> > watchdogs may not get all their parameters updated.
> >
> > watchdog_reconfigure() can be implemented t
In the context of recovering from crash, rproc_trigger_recovery() does
rproc_shutdown() followed by rproc_boot(). The remoteproc resources are
cleaned up in rproc_shutdown() and immediately reallocated in
rproc_boot() which is an unnecessary overhead. Furthermore, we want the
memory regions to be a
Replace rproc_shutdown() by rproc_stop() and rproc_boot() by
rproc_start() in the recovery path, in order to avoid remoteproc
resources re-allocation overhead and to assist with extracting the
coredumps after stopping the remote processor.
Signed-off-by: Sarangdhar Joshi
---
Changes from v1:
*
On Thu, May 25, 2017 at 4:24 PM, Linus Torvalds
wrote:
> On Thu, May 25, 2017 at 1:33 PM, Kirill A. Shutemov
> wrote:
>> Here' my first attempt to bring boot-time between 4- and 5-level paging.
>> It looks not too terrible to me. I've expected it to be worse.
>
> If I read this right, you just ma
DSHD was incorrectly classified as being BSHFL, and DSHD was missing
altogether.
Signed-off-by: David Daney
---
arch/mips/include/uapi/asm/inst.h | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/arch/mips/include/uapi/asm/inst.h
b/arch/mips/include/uapi/asm/inst.h
ind
kmod <= v19 was broken -- it could return 0 to modprobe calls,
incorrectly assuming that a kernel module was built-in, whereas in
reality the module was just forming in the kernel. The reason for this
is an incorrect userspace heuristics. A userspace kmod fix is available
for it [0], however should
As I've been working on polishing my PCID code, a major problem I've
encountered is that there are too many x86 TLB flushing code paths and
that they have too many inconsequential differences. The result was
that earlier versions of the PCID code were a colossal mess and very
difficult to understa
The UP tlbflush generates somewhat nicer code than the SMP version.
Aside from that, it's fallen quite a bit behind the SMP code:
- flush_tlb_mm_range() didn't flush individual pages if the range
was small.
- The lazy TLB code was much weaker. This usually wouldn't matter,
but, if a kern
The local flush path is very similar to the remote flush path.
Merge them.
This is intended to make no difference to behavior whatsoever. It
removes some code and will make future changes to the flushing
mechanics simpler.
This patch does remove one small optimization: flush_tlb_mm_range()
now h
Nadav pointed out that some code used PAGE_SIZE and other code used
PAGE_SHIFT. Use PAGE_SHIFT instead of multiplying or dividing by
PAGE_SIZE.
Requested-by: Nadav Amit
Cc: Rik van Riel
Cc: Dave Hansen
Cc: Nadav Amit
Cc: Michal Hocko
Cc: Arjan van de Ven
Cc: Andrew Morton
Signed-off-by: An
When PCID is enabled, CR3's PCID bits can change during context
switches, so KVM won't be able to treat CR3 as a per-mm constant any
more.
I structured this like the existing CR4 handling. Under ordinary
circumstances (PCID disabled or if the current PCID and the value
that's already in the VMCS
Rather than passing all the contents of flush_tlb_info to
flush_tlb_others(), pass a pointer to the structure directly. For
consistency, this also removes the unnecessary cpu parameter from
uv_flush_tlb_others() to make its signature match the other
*flush_tlb_others() functions.
This serves two p
Lazy TLB state is currently managed in a rather baroque manner.
AFAICT, there are three possible states:
- Non-lazy. This means that we're running a user thread or a
kernel thread that has called use_mm(). current->mm ==
current->active_mm == cpu_tlbstate.active_mm and
cpu_tlbstate.sta
Now there's only one copy of the local tlb flush logic for
non-kernel pages on SMP kernels.
The only functional change is that arch_tlbbatch_flush() will now
leave_mm() on the local CPU if that CPU is in the batch and is in
TLBSTATE_LAZY mode.
Cc: Rik van Riel
Cc: Dave Hansen
Cc: Nadav Amit
Cc
On a remote TLB flush, we leave_mm() if we're TLBSTATE_LAZY. For a
local flush_tlb_mm_range(), we leave_mm() if !current->mm. These
are approximately the same condition -- the scheduler sets lazy TLB
mode when switching to a thread with no mm.
I'm about to merge the local and remote flush code,
Ming Lei writes:
> On Thu, May 25, 2017 at 02:46:28PM +0800, Huang, Ying wrote:
>> From: Huang Ying
>>
>> In this patch, BIO_MAX_PAGES is changed from 256 to HPAGE_PMD_NR if
>> CONFIG_THP_SWAP is enabled and HPAGE_PMD_NR > 256. This is to support
>> THP (Transparent Huge Page) swap optimizatio
On Thu, May 25, 2017 at 05:16:29PM -0700, Luis R. Rodriguez wrote:
> This adds helpers for getting access to the kmod limit from
> userspace. This knob should help userspace more gracefully and
> deterministically handle module loading.
I think more details is needed before we add a new ABI to the
Hi Yan,
The bug is present in gcc 4.8 and 4.9 and m68k has newer gcc to use,
so kbuild test robot needs to upgrade its m68k gcc (maybe it has done it).
FYI Debian has gcc-6 package for m68k and we're using it.
Thanks,
Fengguang
Since bridge node is referenced during in the probe, it should be
released on removal.
Suggested-by: Andrzej Hajda
Signed-off-by: Hoegeun Kwon
---
Hi Inki,
This patch seems to have been forgotten... :)
Changes for V2:
- Checked for rebase 4.12-rc2
Best regards,
Hoegeun
drivers/gpu/drm/exyn
2017년 05월 26일 10:02에 Hoegeun Kwon 이(가) 쓴 글:
> Since bridge node is referenced during in the probe, it should be
> released on removal.
>
> Suggested-by: Andrzej Hajda
> Signed-off-by: Hoegeun Kwon
> ---
> Hi Inki,
>
> This patch seems to have been forgotten... :)
Yeah, forgot this. Merged.
On Thu, May 25, 2017 at 05:16:27PM -0700, Luis R. Rodriguez wrote:
> When checking if we want to allow a kmod thread to kick off we increment,
> then read to see if we should enable a thread. If we were over the allowed
> limit limit we decrement. Splitting the increment far apart from decrement
>
On Thu, 2017-05-25 at 22:28 +0200, Daniel Lezcano wrote:
> On Tue, May 16, 2017 at 03:58:40PM +0800, Andrew Jeffery wrote:
> > Also clean up space-before-tab issues in the documentation.
>
> Andrew,
>
> I reworked the patch to apply to the changes Linus did recently to convert to
> the fttrm010 d
Greg,
Sure, I will fix it and resend a fresh patch.
Thanks,
Hari
On Thu, 25 May 2017 08:14:01 -0700
"Paul E. McKenney" wrote:
> On Thu, May 25, 2017 at 08:15:55AM +0200, Ingo Molnar wrote:
> >
> > * Masami Hiramatsu wrote:
> >
> > > --- a/kernel/kprobes.c
> > > +++ b/kernel/kprobes.c
> > > @@ -377,6 +377,23 @@ static inline void copy_kprobe(struct kprobe *a
On Thu, 25 May 2017 11:18:02 -0400
Steven Rostedt wrote:
> On Thu, 25 May 2017 19:34:43 +0900
> Masami Hiramatsu wrote:
>
>
> > OK, I've ensured that following command hits same BUG.
> >
> > grep t /proc/kallsyms | cut -f3 -d" " | grep -v .*\\..* | \
> > head -n 256 | while read i; do echo p
On Thu, May 25, 2017 at 11:04:44AM +0800, zhong jiang wrote:
>I hit the overlap issue, but it is hard to reproduced. if you think it is
>safe. and the situation
>is not happen. AFAIC, it is no need to add the code.
>
>if you insist on the point. Maybe VM_WARN_ON is a choice.
>
Do you have some l
On Thu, 2017-05-25 at 17:47 -0700, Andy Lutomirski wrote:
>
> +++ b/arch/x86/mm/tlb.c
> @@ -311,7 +311,7 @@ void flush_tlb_mm_range(struct mm_struct *mm,
> unsigned long start,
> goto out;
> }
>
> - if (!current->mm) {
> + if (this_cpu_read(cpu_tlbstate.state) != TLBS
-邮件原件-
发件人: Rob Herring [mailto:r...@kernel.org]
发送时间: 2017年5月25日 20:39
收件人: songxiaowei
抄送: Wangzhou (B); Gabriele Paoloni; bhelg...@google.com; mark.rutl...@arm.com;
xuwei (O); catalin.mari...@arm.com; will.dea...@arm.com;
linux-...@vger.kernel.org; devicet...@vger.kernel.org;
linux
Hi Olof,
2017-05-26 8:59 GMT+09:00 Olof Johansson :
> On Mon, May 22, 2017 at 11:03:49AM +0900, Masahiro Yamada wrote:
>> Hi Arnd, Olof,
>>
>> Last week, I thought I found a problem in my pull request,
>> but it turned out my misunderstanding.
>>
>> So, my pull request I sent is OK.
>> I am re-sen
> On May 25, 2017, at 5:47 PM, Andy Lutomirski wrote:
>
> On a remote TLB flush, we leave_mm() if we're TLBSTATE_LAZY. For a
> local flush_tlb_mm_range(), we leave_mm() if !current->mm. These
> are approximately the same condition -- the scheduler sets lazy TLB
> mode when switching to a threa
This patch enables support for Toshiba BENAND. It was originally posted on
https://lkml.org/lkml/2015/7/24/571
This patch is rewrote to adapt the recent mtd "separate vendor specific code
from core" cleanup process.
Signed-off-by: KOBAYASHI Yoshitake
---
drivers/mtd/nand/Kconfig| 17
Hi Alex W,
I don't need the kernel patch anymore. However it looks the kernel could be
improved to handle this more gracefully when PCI resource allocation fail. Do
you have a plan to improve it in kernel PCI code?
-Collins Cheng
-Original Message-
From: Cheng, Collins
Sent: Wednesda
Add PCIe node for hi3660, and add binding documentation.
Cc: Guodong Xu
Signed-off-by: Xiaowei Song
---
arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 31 +++
1 file changed, 31 insertions(+)
diff --git a/arch/arm64/boot/dts/hisilicon/hi3660.dtsi
b/arch/arm64/boot/dts
On Wed, May 24, 2017 at 6:18 PM, Philipp Zabel wrote:
> Hi Joel,
>
> On Wed, 2017-05-24 at 14:53 +1000, Joel Stanley wrote:
>> @@ -132,6 +134,18 @@ static int of_platform_serial_setup(struct
>> platform_device *ofdev,
>> }
>> }
>>
>> + info->rst = devm_reset_control_get_op
This adds the hooks for an optional reset controller in the 8250 device
tree node.
Signed-off-by: Joel Stanley
---
v2:
Address Philipp's comments. Thanks for the review!
- use _shared variant
- remove unnecessary error handling
Documentation/devicetree/bindings/serial/8250.txt | 1 +
drive
Hi Kees,
On 05/25/2017 09:45 PM, Kees Cook wrote:
On Thu, May 25, 2017 at 11:50 AM, Manfred Spraul
wrote:
Hi all,
Updated series. The series got longer, because I merged all patches
from Kees.
Main changes are:
- sems[] instead of sem[0].
- Immediately use BUILD_BUG_ON()
- Immediately move t
Cc: Guodong Xu
Signed-off-by: Xiaowei Song
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 7c48028ec64a..d56d8f1062ab 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfi
Signed-off-by: Xiaowei Song
---
.../devicetree/bindings/pci/kirin-pcie.txt | 49 ++
1 file changed, 49 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pci/kirin-pcie.txt
diff --git a/Documentation/devicetree/bindings/pci/kirin-pcie.txt
b/Documenta
Hisilicon PCIe Driver shares the common functions for PCIe dw-host
The poweron functions is developed on hi3660 SoC,
while Others Functions are common for Kirin series SoCs.
Low power mode(L1 sub-state and Suspend/Resume), hotplug
and MSI feature are not supported currently.
Cc: Guodong Xu
Sign
Before Version Patches
==
patch V7
https://www.spinics.net/lists/linux-pci/msg61664.html
patch V6
https://www.spinics.net/lists/linux-pci/msg61610.html
patch V4
https://www.spinics.net/lists/linux-pci/msg61406.html
patch V3
https://www.spinics.net/lists/linux-pci/msg61399.html
On Thu, May 25, 2017 at 6:39 PM, Rik van Riel wrote:
> On Thu, 2017-05-25 at 17:47 -0700, Andy Lutomirski wrote:
>>
>> +++ b/arch/x86/mm/tlb.c
>> @@ -311,7 +311,7 @@ void flush_tlb_mm_range(struct mm_struct *mm,
>> unsigned long start,
>> goto out;
>> }
>>
>> - if (!current
On 2017/5/26 9:36, Wei Yang wrote:
> On Thu, May 25, 2017 at 11:04:44AM +0800, zhong jiang wrote:
>> I hit the overlap issue, but it is hard to reproduced. if you think it is
>> safe. and the situation
>> is not happen. AFAIC, it is no need to add the code.
>>
>> if you insist on the point. Maybe
On Wed, May 24, 2017 at 09:16:28AM +0200, Ingo Molnar wrote:
> So the interdiff between your two patches and the 3 commits already queued up
> is:
>
> diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
> index e3043873fcdc..30253ed0380b 100644
> --- a/kernel/time/tick-sched.c
> +++
On Tue 16 May 11:02 PDT 2017, Avaneesh Kumar Dwivedi wrote:
> +static int q6v5_assign_mem_to_subsys(struct q6v5 *qproc,
> + phys_addr_t addr, size_t size)
> +{
> + struct qcom_scm_destVmPerm next[] = {{ QCOM_SCM_VMID_MSS_MSA,
> + (QCOM_SCM_PERM_READ | QCOM_SCM_PERM_WRIT
Currently we only call this from dumb_create, which would guarantee the
size is non-zero.
But it would be harmless to add a sanity check for it for further
extension.
This is much the same as:
1a5dff5 drm/msm: Don't allow zero sized buffer objects
v2: Rewrite commit message.
Signed-off-by: Jeff
On Thu, May 25, 2017 at 05:38:26PM -0700, David Daney wrote:
> Since the eBPF machine has 64-bit registers, we only support this in
> 64-bit kernels. As of the writing of this commit log test-bpf is showing:
>
> test_bpf: Summary: 316 PASSED, 0 FAILED, [308/308 JIT'ed]
>
> All current test cas
Hi sean,
On 05/25/2017 11:30 PM, Sean Paul wrote:
On Tue, May 23, 2017 at 02:39:43PM +0800, Jeffy Chen wrote:
The system would crash when trying to alloc zero sized gem buffer:
[6.712435] Unable to handle kernel NULL pointer dereference at virtual address
0010 <--ZERO_SIZE_PTR
...
[
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
fs/jfs/jfs_metapage.c: In function 'force_metapage':
fs/jfs/jfs_metapage.c:714:2: warning: ignoring return value of
'write_one_page', declared with attribute warn_unused_resu
Ccing Xunlei he is reading the patches see what need to be done for
kdump. There should still be several places to handle to make kdump work.
On 05/18/17 at 07:01pm, Borislav Petkov wrote:
> On Tue, Apr 18, 2017 at 04:22:12PM -0500, Tom Lendacky wrote:
> > Add sysfs support for SME so that user-sp
This patch fixes the checkpoint.pl warning:
WARNING: Prefer printk_ratelimited or pr__ratelimited to
printk_ratelimit
Signed-off-by: Konrad Malkowski
---
drivers/staging/lustre/lnet/libcfs/tracefile.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/drivers/stagi
This is my first version of patch series for adding signature
verification to firmware loading.
The original idea and code came from the work by Luis some time ago,
and I migrated it with some improvements to new driver data APIs,
leaving request_firmware() intact.
For details about how it works,
Systems that have module signing currently enabled may
wish to extend vetting of firmware passed to the kernel
as well. We can re-use most of the code for module signing
for firmware signature verification and signing. This will
also later enable re-use of this same code for subsystems
that wish to
add descriptions and usage about firmware signing in driver data APIs.
Signed-off-by: AKASHI Takahiro
Cc: Luis R. Rodriguez
---
Documentation/driver-api/firmware/driver_data.rst | 6 ++
.../driver-api/firmware/fallback-mechanisms.rst| 5 +-
Documentation/driver-api/firmware/signing.rst
This new option (-f) allows us to create a signature file (*.p7s) for
firmware binary.
Signed-off-by: AKASHI Takahiro
Cc: Luis R. Rodriguez
---
scripts/sign-file.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/scripts/sign-file.c b/scripts/sign-file.c
index fbd34b8e8f5
Add the following tests:
No.15 - verify loaded data witha signature
No.16 - verify loaded data witha signature under signature enforcing
For each test, there are several test cases:
* no signature provided
* valid signature provided
* invalid signature provided
Signed-off-by: AKASHI Takahiro
Cc:
Hi all,
Changes since 20170525:
New tree: realtek
Non-merge commits (relative to Linus' tree): 2775
3084 files changed, 111008 insertions(+), 61381 deletions(-)
I have created today's linux-next t
Hi zhichang.yuan,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.12-rc2 next-20170525]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Gabriele-Paoloni/LPC-legacy-ISA-I-O
looks good to me.
On 2017/5/25 17:22, Andreas Färber wrote:
> The hi6220_reset driver fails to load:
>
> [ 10.423640] hi6220_reset: module license 'unspecified' taints kernel.
> [ 10.423644] Disabling lock debugging due to kernel taint
> [ 10.423735] hi6220_reset: Unknown symbol regmap
On Thu, 25 May 2017 12:37:40 -0500
Michael Bringmann wrote:
> Removing or adding memory via the PowerPC hotplug interface shows
> anomalies in the association between memory and nodes. The code
> was updated to ensure that all nodes found at boot are still available
> to subsequent DLPAR hotplug
On Thu, 25 May 2017, Marcelo Tosatti wrote:
> Argument? We're showing you the data that this is causing a latency
> problem for us.
Sorry I am not sure where the data shows a latency problem. There are
interrupts and scheduler ticks. But what does this have to do with vmstat?
Show me your dpdk c
Hello,
In the Aspeed SoCs we have some reset registers spread out in various parts of
the soc: in the system controller IP, as well as other peripherals. I need to be
able to deassert those resets before other drivers work.
In writing a driver to do this I realised it was very generic. So instead
This driver is a basic single-register reset controller driver that
supports clearing a single bit in a register.
Signed-off-by: Joel Stanley
---
drivers/reset/Kconfig | 6 +++
drivers/reset/Makefile | 1 +
drivers/reset/reset-basic.c | 109
This adds the bindings documentation for a basic single-register reset
controller.
The bindings describe a single 32-bit register that contains up to 32
reset lines, each deasserted by clearing the appropriate bit in the
register.
Signed-off-by: Joel Stanley
---
.../devicetree/bindings/reset/re
On Thu, May 25, 2017 at 12:34 PM, Kees Cook wrote:
> On Thu, May 25, 2017 at 11:50 AM, Manfred Spraul
> wrote:
>> ipc has two management structures that exist for every id:
>> - struct kern_ipc_perm, it contains e.g. the permissions.
>> - struct ipc_rcu, it contains the rcu head for rcu handling
Hi Heiko,
在 2017/5/26 5:12, Heiko Stuebner 写道:
Requiring developers to calculate this pin-bit-value for each bank
is cumbersome and error-prone. With the routes-struct known in
the driver (see above and below), you can keep the the value element
in rockchip_pin_bank, but calculate the per-bank v
On Mon, May 22, 2017 at 4:10 PM, Daniel Micay wrote:
> diff --git a/arch/x86/include/asm/string_64.h
> b/arch/x86/include/asm/string_64.h
> index 733bae07fb29..3c5b26e07b85 100644
> --- a/arch/x86/include/asm/string_64.h
> +++ b/arch/x86/include/asm/string_64.h
> @@ -77,6 +77,11 @@ int strcmp(con
On Thu, May 25, 2017 at 5:20 PM, Mickaël Salaün wrote:
> Add metadata to kselftest_harness.h to be able to include the comments
> in the Sphinx documentation.
>
> Changes since v3:
> * document macros as actual functions (suggested by Jonathan Corbet)
> * remove the TEST_API() wrapper to expose th
On Thu, 25 May 2017 10:10:11 -0500
Reza Arbab wrote:
> On Thu, May 25, 2017 at 04:19:53PM +1000, Michael Ellerman wrote:
> >The commit message for 3af229f2071f says:
> >
> >In practice, we never see a system with 256 NUMA nodes, and in fact, we
> >do not support node hotplug on power in t
Reza Arbab writes:
> On Thu, May 25, 2017 at 04:19:53PM +1000, Michael Ellerman wrote:
>>The commit message for 3af229f2071f says:
>>
>>In practice, we never see a system with 256 NUMA nodes, and in fact, we
>>do not support node hotplug on power in the first place, so the nodes
>>^^^
On Fri, May 26, 2017 at 6:30 AM, André Przywara wrote:
> On 25/05/17 20:26, Jagan Teki wrote:
>> From: Jagan Teki
>>
>> Orangepi Win/WinPlus is an open-source single-board computer
>> using the Allwinner A64 SOC.
>>
>> A64 Orangepi Win/WinPlus has
>> - A64 Quad-core Cortex-A53 64bit
>> - 1GB(Win)
From: Stephen Hemminger
Date: Thu, 25 May 2017 15:05:02 -0700
> Ok, the issue is that lockdep is being stupid and thinking that
> seqcount's behave like locks.
Well.. they do. That's why they have that annotation.
On Thu, May 25, 2017 at 04:07:08PM +0200, Paolo Bonzini wrote:
> I think we should do the fixup backwards.
>
> That is:
>
> - first do get_fpu
>
> - if the fixup is necessary, i.e. ctxt->mode < X86EMUL_MODE_PROT64, do
> fxsave into &fxstate.
>
> - then do segmented_read_std with the correct siz
On Wed, May 24, 2017 at 05:16:18PM +0900, Sergey Senozhatsky wrote:
> On (05/23/17 22:38), Nick Desaulniers wrote:
> > Fixes the following warning, found with Clang:
> well, no objections from my side. MM seems to be getting more and
> more `__maybe_unused' annotations because of clang.
Indeed, bu
On 04/19/2017 at 05:21 AM, Tom Lendacky wrote:
> Provide support so that kexec can be used to boot a kernel when SME is
> enabled.
>
> Support is needed to allocate pages for kexec without encryption. This
> is needed in order to be able to reboot in the kernel in the same manner
> as originally b
Hi,
On 05/25/2017 05:04 AM, Kuninori Morimoto wrote:
Hi Mark
Cc: DRM maintainer
ALSA SoC needs to know connected DAI ID for probing.
It is not a big problem if device/driver was only for sound,
but getting DAI ID will be difficult if device includes both
Video/Sound, like HDMI.
As far as I
On 05/26/2017 09:46 AM, Archit Taneja wrote:
Hi,
On 05/25/2017 05:04 AM, Kuninori Morimoto wrote:
Hi Mark
Cc: DRM maintainer
ALSA SoC needs to know connected DAI ID for probing.
It is not a big problem if device/driver was only for sound,
but getting DAI ID will be difficult if device incl
On 05/25/2017 07:49 PM, Jose Abreu wrote:
Introduce a new helper function which calls mode_valid() callback
for all bridges in an encoder chain.
Reviewed-by: Archit Taneja
Signed-off-by: Jose Abreu
Reviewed-by: Daniel Vetter
Cc: Carlos Palminha
Cc: Ville Syrjälä
Cc: Dave Airlie
Cc: A
On Thu, May 25, 2017 at 05:40:16PM -0700, Andy Lutomirski wrote:
> On Thu, May 25, 2017 at 4:24 PM, Linus Torvalds
> wrote:
> > On Thu, May 25, 2017 at 1:33 PM, Kirill A. Shutemov
> > wrote:
> >> Here' my first attempt to bring boot-time between 4- and 5-level paging.
> >> It looks not too terrib
On 05/25/2017 07:49 PM, Jose Abreu wrote:
Now that we have a callback to check if bridge supports a given mode
we can use it in Analogix bridge so that we restrict the number of
probbed modes to the ones we can actually display.
Also, there is no need to use mode_fixup() callback as mode_valid
Hi Linus,
Not a whole lot happening here, a set of amdgpu fixes and one core
deadlock fix, and some misc drivers fixes.
Dave.
The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d:
Linux 4.12-rc2 (2017-05-21 19:30:23 -0700)
are available in the git repository at:
gi
On Tue, May 16, 2017 at 10:27:46AM +0200, Michal Hocko wrote:
> I guess it is worth reporting this to clang bugzilla. Could you take
> care of that Nick?
>From https://bugs.llvm.org//show_bug.cgi?id=33065#c5
it seems that this is indeed a sequence bug in the previous version of
this code and not a
Add a testcase to test kprobes via ftrace interface
with many concurrent kprobe events.
This tries to add many kprobe events (up to 256) on
kernel functions. To avoid making ftrace-based
kprobes (kprobes on fentry), it skips first N bytes
(on x86 N=5, on ppc or arm N=4) of function entry.
After th
Hi Thomas,
Thanks for the patch. However, we have received this issue from multiple people
and different disro but it occurs only on Gigabyte hardware. With reference AM4
ryzen board we are not facing this issue.
We are in discussion with gigabyte to check the BIOS part. Once we have clarity
on
On 26-04-17, 11:41, Lukasz Luba wrote:
> Hi Viresh,
>
> I went through the v4 code and it looks good to me.
> Feel free to add for the v4 series
> Reviewed-by: Lukasz Luba
@Eduardo: You missed adding this to the patches.
--
viresh
Hi Bjorn,
On 5/26/2017 12:33 AM, Bjorn Andersson wrote:
> On Mon 22 May 06:26 PDT 2017, Dwivedi, Avaneesh Kumar (avani) wrote:
>> On 5/22/2017 4:07 PM, Sricharan R wrote:
>>> Hi,
>>>
>>> On 5/22/2017 3:03 PM, Dwivedi, Avaneesh Kumar (avani) wrote:
On 5/20/2017 8:25 AM, Sricharan R wrote:
From: Jiada Wang
previously burst length (BURST_LENGTH) is always set to equal
to bits_per_word, causes a 10us gap between each word in
transfer, which significantly affects performance.
This patch uses 32 bits transfer to simulate lower bits transfer,
and adjusts burst length runtimely to use b
On 05/26/2017 at 10:49 AM, Dave Young wrote:
> Ccing Xunlei he is reading the patches see what need to be done for
> kdump. There should still be several places to handle to make kdump work.
>
> On 05/18/17 at 07:01pm, Borislav Petkov wrote:
>> On Tue, Apr 18, 2017 at 04:22:12PM -0500, Tom Lendacky
Lieber Freund,
Ich bin Frau Dionisia Denis Perman aus Island, verheiratet mit Late Engineer
Denis Perman {PhD}, der mit MULTINATIONAL OIL COMPANY EXXON AS A gearbeitet hat
DRILLING RIG SUPPLIER in Kuwait seit 19 Jahren, bevor er auf der
22. August 2009. Wir waren seit vierundzwanzig Jahren verheir
Clang warns:
drivers/input/mousedev.c:653:63: error: implicit conversion from 'int'
to 'signed char' changes value from 200 to -56
[-Wconstant-conversion]
client->ps2[1] = 0x60; client->ps2[2] = 3; client->ps2[3] = 200;
~ ^~~
As far as
From: Nicholas Bellinger
This patch fixes a OOPs originally introduced by:
commit bb048357dad6d604520c91586334c9c230366a14
Author: Nicholas Bellinger
Date: Thu Sep 5 14:54:04 2013 -0700
iscsi-target: Add sk->sk_state_change to cleanup after TCP failure
which would trigger a NULL
Michael Bringmann writes:
> Removing or adding memory via the PowerPC hotplug interface shows
> anomalies in the association between memory and nodes.
What anomalies? Please describe the actual problem you're seeing, with
details, and why you think this is the correct fix.
This is a revert of 3
Bjorn,
can you take this regression fix and sent it to Linux before -rc3?
I had hope we could get it into -rc2 but already missed that, and
I haven't heard a comment since..
On Sat, May 20, 2017 at 06:59:54PM +0200, Christoph Hellwig wrote:
> We need to return an error for any call that asks for
On Fri, May 26, 2017 at 10:30:09AM +0800, jeffy wrote:
> Hi sean,
>
> On 05/25/2017 11:30 PM, Sean Paul wrote:
> > On Tue, May 23, 2017 at 02:39:43PM +0800, Jeffy Chen wrote:
> > > The system would crash when trying to alloc zero sized gem buffer:
> > > [6.712435] Unable to handle kernel NULL
firefly reload board not support sd card yet. so support it.
Signed-off-by: Eddie Cai
---
arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi | 31 +++
1 file changed, 31 insertions(+)
diff --git a/arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi
b/arch/arm/boot/dts/rk3288-f
On May 24, 2017 4:17:39 AM PDT, "Andrey Jr. Melnikov"
wrote:
>In gmane.linux.kernel sean.w...@mediatek.com wrote:
>> From: Sean Wang
>
>> MT7530 is a 7-ports Gigabit Ethernet Switch that could be found on
>> Mediatek router platforms such as MT7623A or MT7623N platform which
>> includes 7-port G
From: Teng Qin
Allow BPF program to attach to all perf_event types supported
by the current bpf and perf code logic, including HW_CACHE, RAW,
and dynamic pmu events.
Also add support for reading these event counters using
bpf_perf_event_read() helper.
Signed-off-by: Teng Qin
Signed-off-by: Ale
From: Teng Qin
This commit updates documentation of the bpf_perf_event_output and
bpf_perf_event_read helpers to match their implementation.
Signed-off-by: Teng Qin
Signed-off-by: Alexei Starovoitov
---
include/uapi/linux/bpf.h | 11 +++
tools/include/uapi/linux/bpf.h | 11 +
v1->v2: address Peter's feedback. Refactor patch 1 to allow attaching
bpf programs to all event types and reading counters from all of them as well
patch 2 - more tests
patch 3 - address Dave's feedback and document bpf_perf_event_read()
and bpf_perf_event_output() properly
Teng Qin (3):
perf, b
1 - 100 of 901 matches
Mail list logo
