When IOTLB is not enabled, we should forbid IOTLB invalidation to
avoid a NULL pointer dereference.
Signed-off-by: Jason Wang
---
drivers/vhost/vhost.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
index c6f2d89..7d338d5 100644
--- a/driver
Hi Andy (&list),
this is more of a heads up than a bug report, since it turns out you
already fixed this in
731e33e: x86/arch_prctl/64: Remove FSBASE/GSBASE < 4G optimization
In any case, without that commit, trying to use PTRACE_SETREGS to set
either fs_base, or gs_base to 0 when it was previou
Signed-off-by: Jason Wang
---
include/uapi/linux/vhost.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/uapi/linux/vhost.h b/include/uapi/linux/vhost.h
index 56b7ab5..60180c0 100644
--- a/include/uapi/linux/vhost.h
+++ b/include/uapi/linux/vhost.h
@@ -172,8 +172,6 @@ struct vhost_me
2016. 11. 18. 16:16 Krzysztof Kozlowski wrote:
> All Samsung platforms, including the Exynos, are selecting HZ_FIXED with
> 200 Hz. Unfortunately in case of multiplatform image this affects also
> other platforms when Exynos is enabled.
>
> This looks like an very old legacy code, dating back t
Mark Lord [mailto:ml...@pobox.com]
> Sent: Thursday, November 17, 2016 9:42 PM
[...]
> What the above sample shows, is the URB transfer buffer ran out of space in
> the
> middle
> of a packet, and the hardware then tried to just continue that same packet in
> the
> next URB,
> without an rx_desc
On Thu, Nov 10, 2016 at 10:00:48AM +0100, Patrice Chotard wrote:
> Hi Arnd, Kevin, Olof
>
> PLease consider this second round of STi dts update for v4.10 :
>
> The following changes since commit 97a0b97f9e8197429eee5f87ce14373f73dbd9d3:
>
> ARM: dts: stih410-clocks: Add PROC_STFE as a critical
On Thu, Nov 10, 2016 at 10:00:32AM +0100, Patrice Chotard wrote:
> Hi Olof, Arnd and Kevin,
>
> Please consider the second round of multi_v7_defconfig updates for v4.10 :
>
>
> The following changes since commit 620c52f4db4d47e1f33c64e641392fe575d5397f:
>
> ARM: multi_v7_defconfig: Remove sti
Hi,
On Tue, Nov 08, 2016 at 08:26:28PM +0200, Krzysztof Kozlowski wrote:
> Hi,
>
> Hurray! New board! ... Exynos4415 slowly is going away.
>
> Best regards,
> Krzysztof
>
>
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50
On Tue, Nov 08, 2016 at 08:26:27PM +0200, Krzysztof Kozlowski wrote:
> Hi,
>
> Nothing special.
>
> Best regards,
> Krzysztof
>
>
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git reposit
On Tue, Nov 08, 2016 at 08:26:29PM +0200, Krzysztof Kozlowski wrote:
> Hi,
>
> Exynos5433 + two boards using it. Mobile boards! :)
>
> I am really happy to push it. I know that it has been a lot of effort
> in Samsung to mainline this.
>
> Best regards,
> Krzysztof
>
>
> The following changes
On Thu, Nov 17, 2016 at 08:07:09PM -0500, Sandy Harris wrote:
> Add Ted T'so to cc list. Shouldn't he be included on anything affecting
> the random(4) driver?
>
Blindy used get_maintainer.pl, and since the file is in crypto, hw_random
people were not set.
Note that get_maintainer.pl on drivers/
On Thu, Nov 17, 2016 at 06:29:08PM -0500, James Simmons wrote:
> From: Mikhail Pershin
>
> - llh_cat_idx may become bigger than llog bitmap size in
> llog_cat_set_first_idx() function
> - it is wrong to use previous cur_offset as new buffer offset,
> new offset should be calculated from value
On Thu 17-11-16 14:30:21, Johannes Weiner wrote:
> The bug in khugepaged fixed earlier in this series shows that radix
> tree slot replacement is fragile; and it will become more so when not
> only NULL<->!NULL transitions need to be caught but transitions from
> and to exceptional entries as well.
On Thu, Nov 17, 2016 at 12:46:12PM +0100, Sergio Paracuellos wrote:
> On Thu, Nov 17, 2016 at 12:33 PM, Dan Carpenter
> wrote:
> > Give it a shot and see if the warnings go away. I don't think the tag
> > is correct.
>
> Just removing __iomem tag in shmem_data field of slic_shmemory struct
> mak
On Thu 17-11-16 14:29:45, Johannes Weiner wrote:
> The way the page cache is sneaking shadow entries of evicted pages
> into the radix tree past the node entry accounting and tracking them
> manually in the upper bits of node->count is fraught with problems.
>
> These shadow entries are marked in
On Fri, 18 Nov 2016, Ingo Molnar wrote:
>
> * Kyle Huey wrote:
>
> > In order to introduce new arch_prctls that are not 64 bit only, rename the
> > existing 64 bit implementation to do_arch_prctl_64(). Also rename the second
> > argument to arch_prctl(), which will no longer always be an addres
On Thu 17-11-16 14:11:32, Johannes Weiner wrote:
> When the shadow page shrinker tries to reclaim a radix tree node but
> finds it in an unexpected state - it should contain no pages, and
> non-zero shadow entries - there is no need to kill the executing task
> or even the entire system. Warn about
* Kyle Huey wrote:
> --- a/include/linux/compat.h
> +++ b/include/linux/compat.h
> @@ -716,16 +716,18 @@ int __compat_save_altstack(compat_stack_t __user *,
> unsigned long);
> } while (0);
>
> asmlinkage long compat_sys_sched_rr_get_interval(compat_pid_t pid,
>
On Thu 17-11-16 14:11:31, Johannes Weiner wrote:
> The radix tree counts valid entries in each tree node. Entries stored
> in the tree cannot be removed by simpling storing NULL in the slot or
> the internal counters will be off and the node never gets freed again.
>
> When collapsing a shmem page
On Thu 17-11-16 14:11:30, Johannes Weiner wrote:
> When a radix tree iteration drops the tree lock, another thread might
> swoop in and free the node holding the current slot. The iteration
> needs to do another tree lookup from the current index to continue.
>
> [kirill.shute...@linux.intel.com:
* Kyle Huey wrote:
> In order to introduce new arch_prctls that are not 64 bit only, rename the
> existing 64 bit implementation to do_arch_prctl_64(). Also rename the second
> argument to arch_prctl(), which will no longer always be an address.
> #ifdef CONFIG_X86_64
> void entry_SYSCALL_64(
All Samsung platforms, including the Exynos, are selecting HZ_FIXED with
200 Hz. Unfortunately in case of multiplatform image this affects also
other platforms when Exynos is enabled.
This looks like an very old legacy code, dating back to initial
upstreaming of S3C24xx. Probably it was required
The PLL-MIPI clock is somewhat special as it has its own LDOs which
need to be turned on for this PLL to actually work and output a clock
signal.
Add the 2 LDO enable bits to the gate bits. This fixes issues with
the TCON not sending vblank interrupts when the tcon and dot clock are
indirectly clo
On Thu, Nov 17, 2016 at 02:23:50PM -0800, Guenter Roeck wrote:
> On Thu, Nov 17, 2016 at 11:31:33AM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.8.9 release.
> > There are 92 patches in this series, all will be posted as a response
> > to this one. If
Add the mshc_2 node for supporting T-flash.
And it needs to add the "mshc*" aliases. Because dwmmc driver should be
assigned to "ctrl_id" after parsing to "mshc".
If there is no aliases for mshc, then it might be set to the wrong
capabilities.
Signed-off-by: Jaehoon Chung
---
arch/arm64/boot/dt
(Seeing that it was me who initiated those patches I guess I should
speak up here)
On 11/18/2016 06:16 AM, NeilBrown wrote:
> Hi,
>
> I've been sitting on these patches for a while because although they
> solve a real problem, it is a fairly limited use-case, and I don't
> really like some of
Hi Hugh,
On Thu, Nov 17, 2016 at 08:35:10PM -0800, Hugh Dickins wrote:
> On Fri, 11 Nov 2016, Minchan Kim wrote:
> > Sorry for sending a wrong version. Here is new one.
> >
> > From 2d42ead9335cde51fd58d6348439ca03cf359ba2 Mon Sep 17 00:00:00 2001
> > From: Minchan Kim
> > Date: Fri, 11 Nov 2016
Hi Sagi,
On 31 October 2016 at 02:42, Sagi Grimberg wrote:
>> The semaphore 'sem' in isert_device is used as completion, so convert
>> it to struct completion. Semaphores are going away in the future.
>
>
> Umm, this is 100% *not* true. np->sem is designed as a counting to
> sync the iscsi login
The code actually checks rt_queued not rt_nr_running
in pick_next_task_rt(), so change the corresponding
comment.
Signed-off-by: T.Zhou
---
kernel/sched/rt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
index 2516b8d..9b4a5c5 100644
--
On Thu, Nov 17, 2016 at 01:35:45PM +0100, Arnd Bergmann wrote:
> On Monday, November 14, 2016 8:27:05 PM CET Krzysztof Kozlowski wrote:
> > @@ -1497,7 +1497,7 @@ source kernel/Kconfig.preempt
> > config HZ_FIXED
> > int
> > default 200 if ARCH_EBSA110 || ARCH_S3C24XX || \
> > -
Hi Marty,
On 2016/11/17 11:03, Jiancheng Xue wrote:
> Hi Wei，
>
> On 2016/11/16 17:31, Wei Xu wrote:
>> Hi Pan,
>>
>> On 2016/11/16 8:56, wenpan wrote:
>>> Hi Marty，
>>> Does this confict with your patch？ If not，I hope this could be merged
>>> first. Besides could you tell me the link to your r
See @flags is not used there, so delete it.
Signed-off-by: T.Zhou
---
kernel/sched/deadline.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
index c61b461..f276a81 100644
--- a/kernel/sched/deadline.c
+++ b/kernel/sch
From: Len Brown
Upon removal of the "is_idle" flag, x86_test_and_clear_bit_percpu()
is no longer used.
Signed-off-by: Len Brown
Acked-by: Peter Zijlstra (Intel)
---
arch/x86/include/asm/percpu.h | 11 ---
1 file changed, 11 deletions(-)
diff --git a/arch/x86/include/asm/percpu.h b/ar
From: Len Brown
Upon removal of the i7300_idle driver, the idle_notifer is unused.
Signed-off-by: Len Brown
Acked-by: Peter Zijlstra (Intel)
---
arch/x86/include/asm/idle.h | 7 ---
arch/x86/kernel/process.c | 15 ---
2 files changed, 22 deletions(-)
diff --git a/arch/x86/
From: Len Brown
Upon removal of the is_idle flag, these routines became NOPs.
Signed-off-by: Len Brown
Acked-by: Peter Zijlstra (Intel)
---
arch/x86/include/asm/apic.h | 1 -
arch/x86/include/asm/idle.h | 9 -
arch/x86/kernel/kvm.c| 2 --
arch/x86/kernel/proce
From: Len Brown
In preparation for removing the idle_notifier,
remove its only user, the i7300_idle driver.
i7300_idle was deployed in 2008 to reduce idle memory power
on systems using the i7300 chipset. The driver worked by throttling
the fully-buffered DIMMs during idle periods using the IOAT
The return from idle path is latency sensitive,
so the less code and fewer data accesses, the better.
Remove the un-maintained i7300_idle driver,
the only user of the x86 idle-notifier,
and then remove the notifier itself.
From: Len Brown
Upon removal of the idle_notifier, all accesses to
the "is_idle" flag serve no purpose.
Signed-off-by: Len Brown
Acked-by: Peter Zijlstra (Intel)
---
arch/x86/kernel/process.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel
Extend the inkern api with functions for reading and writing ext_info
of iio channels.
---
drivers/iio/inkern.c | 55
include/linux/iio/consumer.h | 6 +
2 files changed, 61 insertions(+)
diff --git a/drivers/iio/inkern.c b/drivers/iio/ink
Aaron Tomlin writes:
> By default, during the access permission modification of a module's core
> and init pages, we only ignore modules that are malformed. Albeit for a
> module which is going away, it does not make sense to change its text to
> RO since the module should be RW, before deallocati
On Friday, November 18, 2016 5:23 AM Jens Axboe wrote:
>
> We ran into a funky issue, where someone doing 256K buffered reads saw
> 128K requests at the device level. Turns out it is read-ahead capping
> the request size, since we use 128K as the default setting. This doesn't
> make a lot of sens
From: Vadim Pasternak
Device driver for Mellanox I2C controller logic, implemented in Lattice
CPLD device.
Device supports:
- Master mode
- One physical bus
- Polling mode
The Kconfig currently controlling compilation of this code is:
drivers/i2c/busses/Kconfig:config I2C_MLXCPLD
Signed-off-
From: Andy Shevchenko
There is already one and at least one more user coming which
require an access to Primary to Sideband bridge (P2SB) in order
to get IO or MMIO bar hidden by BIOS.
Create a driver to access P2SB for x86 devices.
Signed-off-by: Yong, Jonathan
Signed-off-by: Andy Shevchenko
Move the enum's definition into a standalone header file which can be used
wherever its definition is needed.
Signed-off-by: Tan Jui Nee
Reviewed-by: Mika Westerberg
---
Changes in V11:
- No change
Changes in V10:
- No change
Changes in V9:
- No change
Changes in V8:
Adding Intel codename Apollo Lake platform device IDs for PCH.
Signed-off-by: Tan Jui Nee
Acked-for-MFD-by: Lee Jones
---
Changes in V11:
- No change
Changes in V10:
- No change
Changes in V9:
- No change
Changes in V8:
- No change
drivers/mfd/lpc_ich_core.c
This driver uses the P2SB hide/unhide mechanism cooperatively
to pass the PCI BAR address to the gpio platform driver.
Signed-off-by: Tan Jui Nee
Reviewed-by: Mika Westerberg
---
Changes in V11:
- Remove duplicated object file lpc_ich-objs in Makefile.
- Put p2sb.h header file in
Add support for non ACPI system, such as system that uses Advanced Boot
Loader (ABL) whereby a platform device has to be created in order to bind
with PINCTRL/GPIO.
At the moment, Intel Apollo Lake SoC requires P2SB driver to hide and
unhide P2SB to lookup P2SB BAR and pass the PCI BAR address to
This patch follows the example of mfd/wm831x to rename the driver
from "lpc_ich" to "lpc_ich_core".
Signed-off-by: Tan Jui Nee
Reviewed-by: Mika Westerberg
---
Changes in V11:
- No change
Changes in V10:
- No change
Changes in V9:
- Remove the filename from the header o
Hi,
The patches are to cater the need for non-ACPI system whereby
a platform device has to be created in order to bind with
Apollo Lake Pinctrl GPIO platform driver.
The MMIO BAR is accessed over the Primary to Sideband bridge
(P2SB). Since the BIOS prevents the P2SB device from being
enumerated b
Hi, Daniel:
On Fri, 2016-11-18 at 11:22 +0800, Daniel Kurtz wrote:
> Hi CK,
>
> On Thu, Nov 17, 2016 at 1:36 PM, CK Hu wrote:
> > Hi, Jitao:
> >
> >
> > On Wed, 2016-11-16 at 11:20 +0800, Jitao Shi wrote:
> >> Tune dsi frame rate by pixel clock, dsi add some extra signal (i.e.
> >> Tlpx, Ths-pre
When writing to a fastfail device we use MD_FASTFAIL unless
it is the only device being written to.
For resync/recovery, assume there was a working device to
read from so always use REQ_FASTFAIL_DEV.
If a write for resync/recovery fails, we just fail the
device - there is not much else to do.
If
If a device is marked FailFast, and it is not the only
device we can read from, we mark the bio as MD_FAILFAST.
If this does fail-fast, we don't try read repair but just
allow failure.
If it was the last device, it doesn't get marked Faulty so
the retry happens on the same device - this time with
When writing to a fastfail device, we use MD_FASTFAIL unless
it is the only device being written to. For
resync/recovery, assume there was a working device to read
from so always use MD_FASTFAIL.
If a write for resync/recovery fails, we just fail the
device - there is not much else to do.
If a n
If a device is marked FailFast and it is not the only device
we can read from, we mark the bio with REQ_FAILFAST_* flags.
If this does fail, we don't try read repair but just allow
failure. If it was the last device it doesn't fail of
course, so the retry happens on the same device - this time
wi
Hi,
I've been sitting on these patches for a while because although they
solve a real problem, it is a fairly limited use-case, and I don't
really like some of the details.
So I'm posting them as RFC in the hope that a different perspective
might help me like them better, or find a better ap
This patch just adds a 'failfast' per-device flag which can be stored
in v0.90 or v1.x metadata.
The flag is not used yet but the intent is that it can be used for
mirrored (raid1/raid10) arrays where low latency is more important
than keeping all devices on-line.
Setting the flag for a device eff
This can only be supported on personalities which ensure
that md_error() never causes an array to enter the 'failed'
state. i.e. if marking a device Faulty would cause some
data to be inaccessible, the device is status is left as
non-Faulty. This is true for RAID1 and RAID10.
If we get a failure
Hi YT,
I don't see a reason to handle device_data in such a generic way at
the generic mtk_ddp_comp layer.
The device data is very component specific, so just define different
structs for different comp types, ie:
struct mtk_disp_ovl_driver_data {
unsigned int reg_ovl_addr;
unsigned int f
From: Ross Zwisler [mailto:ross.zwis...@linux.intel.com]
> On Wed, Nov 16, 2016 at 04:17:01PM -0800, Matthew Wilcox wrote:
> > From: Matthew Wilcox
> >
> > Hi Andrew,
> >
> > Please include these patches in the -mm tree for 4.10. Mostly these are
> > improvements; the only bug fixes in here relat
On Fri, 11 Nov 2016, Minchan Kim wrote:
> Sorry for sending a wrong version. Here is new one.
>
> From 2d42ead9335cde51fd58d6348439ca03cf359ba2 Mon Sep 17 00:00:00 2001
> From: Minchan Kim
> Date: Fri, 11 Nov 2016 15:02:57 +0900
> Subject: [PATCH] mm: support anonymous stable page
>
> For develo
On Thu, Nov 17, 2016 at 3:14 AM, Yao Yuan wrote:
> On Thu, Nov 17, 2016 at 06:50:55AM +, Krzeminski, Marcin (Nokia -
> PL/Wroclaw) wrote:
>> > > > On Thu, Aug 18, 2016 at 2:38 AM, Yunhui Cui
>> > > > wrote:
>> > > > > From: Yunhui Cui
>> > > > >
>> > > > > With the physical sectors combinat
Hi Rafal,
On Thu, Nov 17, 2016 at 7:05 PM, Rafal Ozieblo wrote:
> -Original Message-
> From: Nicolas Ferre [mailto:nicolas.fe...@atmel.com]
> Sent: 17 listopada 2016 14:29
> To: Harini Katakam; Rafal Ozieblo
> Cc: harini.kata...@xilinx.com; net...@vger.kernel.org;
> linux-kernel@vger.ker
On Fri, Nov 18 2016, Andreas Dilger wrote:
> [ Unknown signature status ]
>
>> On Nov 17, 2016, at 1:00 PM, J. Bruce Fields wrote:
>>
>> On Thu, Nov 17, 2016 at 04:45:45PM +, David Howells wrote:
>>> One Thousand Gnomes wrote:
>>>
> (2) Lightweight stat (AT_STATX_DONT_SYNC): Ask for ju
> -Original Message-
> From: Han Xu [mailto:xhnj...@gmail.com]
> Sent: Wednesday, November 16, 2016 6:11 PM
> To: Krzeminski, Marcin (Nokia - PL/Wroclaw)
>
> Cc: Yunhui Cui ; Yunhui Cui ;
> David Woodhouse ; linux-kernel@vger.kernel.org;
> linux-...@lists.infradead.org; han...@freescale.
On Fri, Nov 18, 2016 at 12:32:06PM +0900, Namhyung Kim wrote:
> Btw I prefer using the kvmtool for my kernel work since it's much more
> simpler..
>
> Thanks,
> Namhyung
Up to you but then you should extend that to support 1.0 spec.
I strongly object to adding to the list of legacy interfaces
we
Hello Rui, linux-pm,
These are essentially driver fixes, meant for an rcX. But given that we are
already 4.9-rc5 going for rc6, please, consider the following changes
for v4.10-rc1. This is my first request, I will continue monitoring
the mailing list for outstanding changes.
Therefore, please co
Hi,
Thanks for your detailed information,
On Wed, Nov 16, 2016 at 07:10:36AM -0500, Paolo Bonzini wrote:
> > Not sure how independent ERST is from ACPI and other specs. It looks
> > like referencing UEFI spec at least.
>
> It is just the format of error records that comes from the UEFI spec
> (
On Nov 17, 2016, at 6:35 AM, David Howells wrote:
>
> Return enhanced file attributes from the Ext4 filesystem. This includes
> the following:
>
> (1) The inode creation time (i_crtime) as stx_btime, setting STATX_BTIME.
>
> (2) The inode i_version as stx_version if a file with I_VERSION set o
On Nov 17, 2016, at 4:40 PM, Dave Chinner wrote:
>
> On Thu, Nov 17, 2016 at 01:35:03PM +, David Howells wrote:
>> Add a system call to make extended file information available, including
>> file creation, data version and some attribute flags where available
>> through the underlying filesys
On 17-11-16, 21:54, Stratos Karafotis wrote:
> Commit 18b46abd0009 ("cpufreq: governor: Be friendly towards latency-
> sensitive bursty workloads"), introduced a method to copy the calculated
> load from the previous sampling period in case of a deferred timer
> (update).
>
> This helps on bursty
Hi CK,
On Thu, Nov 17, 2016 at 1:36 PM, CK Hu wrote:
> Hi, Jitao:
>
>
> On Wed, 2016-11-16 at 11:20 +0800, Jitao Shi wrote:
>> Tune dsi frame rate by pixel clock, dsi add some extra signal (i.e.
>> Tlpx, Ths-prepare, Ths-zero, Ths-trail,Ths-exit) when enter and exit LP
>> mode, those signals will
On Thursday 17 November 2016 10:33 PM, Arnd Bergmann wrote:
> On Thursday, November 17, 2016 9:50:27 AM CET pankaj.dubey wrote:
>>
> of_scu_enable() which _only_ looks up the SCU address in DT and enables
> it if it finds it, otherwise returning failure.
>
> a9_scu_enable() which
Hi YT,
Sorry for the very late review.
My biggest problem with this patch is it describes itself as adding
support for a new use case "DSI -> panel", but makes many changes to
the existing working flow "DSI -> bridge -> panel".
If these changes are really needed, or improve the existing flow, I'd
On 17-11-16, 16:08, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> There are two places in the cpufreq core in which low-level driver
> callbacks may be invoked for an inactive cpufreq policy, which isn't
> guaranteed to work in general. Both are due to possible races with
> CPU offline.
Hi Arnd,
在 2016年11月16日 22:22, Arnd Bergmann 写道:
The newly added OTG support has an obvious uninitialized variable
access that gcc warns about:
drivers/phy/phy-rockchip-inno-usb2.c: In function 'rockchip_chg_detect_work':
drivers/phy/phy-rockchip-inno-usb2.c:717:7: error: 'tmout' may be used
un
If CONFIG_STM_SOURCE_FTRACE is selected, Function trace data can be writen
to sink via STM, all functions that related to writing data packets to
STM should be marked 'notrace' to avoid being traced by Ftrace, otherwise
the program would stall into an endless loop.
Signed-off-by: Chunyan Zhang
Ac
On 17-11-16, 10:38, Markus Mayer wrote:
> No, because I am trying to find the lowest frequency that doesn't
> require safe mode and it's looping through the table from highest to
> lowest. So there could still be a lower frequency after the current
> one that doesn't require safe mode.
>
> What I
This patch adds a driver that models itself as an stm_source called
stm_ftrace. Once the stm device and stm_ftrace have been linked via
sysfs, the driver registers itself as a trace_export and everything
passed to the interface from Ftrace subsystem will end up in the STM
trace engine.
Signed-off-
Currently Function traces can be only exported to ring buffer, this
patch added trace_export concept which can process traces and export
them to a registered destination as an addition to the current only
one output of Ftrace - i.e. ring buffer.
In this way, if we want Function traces to be sent t
IP blocks allowing a variety of trace sources to log debugging
information to a pre-defined area have been introduced on a couple of
architecture [1][2]. These system trace blocks (also known as STM)
typically follow the MIPI STPv2 protocol [3] and provide a system wide
logging facility to any devi
On 26-10-16, 12:02, Viresh Kumar wrote:
> Hi,
>
> Some platforms (like TI) have complex DVFS configuration for CPU
> devices, where multiple regulators are required to be configured to
> change DVFS state of the device. This was explained well by Nishanth
> earlier [1].
>
> One of the major compl
This corrects a problem that appears to be similar to ERR006358. But
while ERR006358 is a race when the tx queue transitions from empty to
not empty, this problem is a race when the rx queue transitions from
full to not full.
The symptom is a receive queue that is stuck. The ENET_RDAR register
w
On Thu, 17 Nov 2016, Vince Weaver wrote:
> On Thu, 17 Nov 2016, Vince Weaver wrote:
> > >
> > > [ 911.507365]
> > > ==
> > > [ 911.514824] BUG: KASAN: global-out-of-bounds in
> > > match_token+0x268/0x310 at addr b14ad058
> On Nov 17, 2016, at 11:39 AM, Jeff Layton wrote:
>
> On Thu, 2016-11-17 at 13:35 +, David Howells wrote:
>> Add a system call to make extended file information available, including
>> file creation, data version and some attribute flags where available
>> through the underlying filesystem.
> On Nov 17, 2016, at 1:00 PM, J. Bruce Fields wrote:
>
> On Thu, Nov 17, 2016 at 04:45:45PM +, David Howells wrote:
>> One Thousand Gnomes wrote:
>>
(2) Lightweight stat (AT_STATX_DONT_SYNC): Ask for just those details of
interest, and allow a network fs to approximate anyth
Hi Peter,
Thank you for your comments.
> -Original Message-
> From: Peter Rosin [mailto:p...@axentia.se]
> Sent: Thursday, November 17, 2016 10:06 AM
> To: Vadim Pasternak ; w...@the-dreams.de
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; j...@resnulli.us;
> Michael Shych
Kees Cook writes:
> On Thu, Nov 17, 2016 at 2:53 AM, Michael Ellerman wrote:
>> kbuild test robot writes:
>>> [auto build test ERROR on char-misc/char-misc-testing]
>>> [also build test ERROR on v4.9-rc5]
>>> [cannot apply to next-20161115]
>>> [if your patch is applied to the wrong git tree, p
On Thu, 2016-11-17 at 15:35 -0800, Stephen Boyd wrote:
> On 11/17, Honghui Zhang wrote:
> > On Wed, 2016-11-16 at 11:38 -0800, Stephen Boyd wrote:
> > > On 11/16, Arnd Bergmann wrote:
> > > > After the MT2701 clock driver was added, we get a harmless warning for
> > > > the iommu driver that select
On 2016-11-17 18:34, Paul Moore wrote:
> On Tue, Nov 15, 2016 at 3:49 AM, Richard Guy Briggs wrote:
> > On 2016-11-14 15:17, Paul Moore wrote:
> >> On Thu, Nov 10, 2016 at 1:41 AM, Richard Guy Briggs
> >> wrote:
> >> > The value (unsigned int)-1 is used as a sentinel to indicate the
> >> > sessi
On 11/18/2016 10:00 AM, Kirti Wankhede wrote:
> On 11/18/2016 3:35 AM, Neo Jia wrote:
>> On Thu, Nov 17, 2016 at 02:25:15PM -0700, Alex Williamson wrote:
>>> On Thu, 17 Nov 2016 02:16:12 +0530
>>> Kirti Wankhede wrote:
Documentation/ABI/testing/sysfs-bus-vfio-mdev | 111 ++
Docume
On Fri, Nov 18, 2016 at 3:02 AM, Maxime Ripard
wrote:
> On Wed, Nov 16, 2016 at 05:37:31PM +0800, Chen-Yu Tsai wrote:
>> The sun4i DRM driver counts the number of endpoints it found and
>> registers the whole DRM pipeline if any endpoints are found.
>>
>> However, if the TCON and its child endpoin
Hello,
This isn't really a bug report, but just a description of a
frequency/IPC
dependent behavior that I'm curious if we should worry about. The
behavior
is exposed by questionable design so I'm leaning towards don't-care.
Consider these threads running in parallel on two ARM64 CPUs running
Somewhere around
Commit: 20d0189b1012 ("block: Introduce new bio_split()")
and
Commit: 4b1faf931650 ("block: Kill bio_pair_split()")
in 3.14 we lost the call to trace_block_split() from bio_split().
Commit: cda22646adaa ("block: add call to split trace point")
in 4.5 added it back for blk_queu
On Fri, Nov 18, 2016 at 3:05 AM, Maxime Ripard
wrote:
> On Wed, Nov 16, 2016 at 05:37:32PM +0800, Chen-Yu Tsai wrote:
>> If we attempt to read/write the TCON registers before the bus clock
>> is enabled, those accesses get ignored.
>>
>> In practice this almost never occurs because U-boot had alre
Allow power sequencing for the Marvell SD8787 Wifi/BT chip.
This can be abstracted to other chipsets if needed in the future.
Cc: Tony Lindgren
Cc: Ulf Hansson
Cc: Mark Rutland
Cc: Srinivas Kandagatla
Signed-off-by: Matt Ranostay
---
.../devicetree/bindings/mmc/mmc-pwrseq-sd8787.txt | 14 +
On 11/18/2016 3:35 AM, Neo Jia wrote:
> On Thu, Nov 17, 2016 at 02:25:15PM -0700, Alex Williamson wrote:
>> On Thu, 17 Nov 2016 02:16:12 +0530
>> Kirti Wankhede wrote:
>>>
>>> Documentation/ABI/testing/sysfs-bus-vfio-mdev | 111 ++
>>> Documentation/vfio-mediated-device.txt| 399 +
On 11/17/2016 5:24 PM, Or Gerlitz wrote:
> On Thu, Nov 17, 2016 at 9:44 PM, Doug Ledford wrote:
>> On 11/17/16 1:49 PM, Leon Romanovsky wrote:
>>> On Thu, Nov 17, 2016 at 07:13:54AM -0500, Doug Ledford wrote:
Hi Linus,
Due to various issues, I've been away and couldn't send a pull r
Make modifications to data column alignment
Signed-off-by: Walt Feasel
---
v2 makes changes to correct for email format patch submission
drivers/staging/xgifb/XGI_main.h | 54
1 file changed, 27 insertions(+), 27 deletions(-)
diff --git a/drivers/stagin
On Thu, Nov 17, 2016 at 7:23 AM, John Garry wrote:
> On 11/11/2016 08:49, wangyijing wrote:
>
> I have not seen the flutter issue. I am just trying to solve the
> horrible WARN dump.
> However I do understand that there may be a issue related to how we
> queue the events; there
> "John" == John Garry writes:
John> @Maintainers, would you be willing to accept this patch as an
John> interim fix for the dastardly WARN while we try to fix the flutter
John> issue?
I'll defer to James since I don't have much libsas experience.
--
Martin K. Petersen Oracle Linux En
1 - 100 of 952 matches
Mail list logo
