On Thu, Jan 19, 2017 at 6:32 PM, Vikas Shivappa
wrote:
> Resending including Thomas , also with some changes. Sorry for the spam
>
> Based on Thomas and Peterz feedback Can think of two design
> variants which target:
>
> -Support monitoring and allocating using the same resctrl group.
> user can
Applied including other two patches.
Thanks.
2017년 01월 17일 23:15에 Andrzej Hajda 이(가) 쓴 글:
> decon_commit is called just after reset so video is disabled anyway.
>
> Signed-off-by: Andrzej Hajda
> ---
> drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 2 --
> 1 file changed, 2 deletions(-)
>
>
On Tue, Jan 10, 2017 at 03:02:41PM +0800, Peter Chen wrote:
> On Sat, Jan 07, 2017 at 10:54:56AM +0200, Krzysztof Kozlowski wrote:
> > On Thu, Jan 05, 2017 at 02:01:53PM +0800, Peter Chen wrote:
> > > We have an well-known problem that the device needs to do some power
> > > sequence before it can
If rcar_sysc_pd_init will fail, Handle ERROR properly.
-Release memory
-Unmap I/O memory from kernel address space.
In rcar_sysc_init, If ioremap_nocache will fail. It will return NULL.
Kernel can run into a NULL-pointer dereference.
Signed-off-by: Arvind Yadav
---
drivers/soc/renesas/rcar-sy
Jan Kiszka writes:
> When using the a device with edge-triggered interrupts, such as MSIs,
> the interrupt handler has to ensure that there is a point in time during
> its execution where all interrupts sources are silent so that a new
> event can trigger a new interrupt again.
>
> This is achiev
On 2017/1/20 15:07, Eddie Cai wrote:
2017-01-20 10:29 GMT+08:00 Shawn Lin :
On 2017/1/19 10:11, Eddie Cai wrote:
This patch add basic support for RK3288-Tinker board. We can boot in to rootfs
with this patch.
Signed-off-by: Eddie Cai
---
arch/arm/boot/dts/Makefile | 1 +
arch/ar
Hi Finn,
Am 15.01.2017 um 17:42 schrieb Finn Thain:
>> No, we can't check either FDC or SCSI interrupts (or indeed any chip
>> registers) without touching the ST-DMA. The moment we select a FDC or
>> SCSI register for read, DMA is terminated no questions asked.
>>
>
> Perhaps we can convert DM
On Thu, Jan 19, 2017 at 9:41 AM, Thomas Gleixner wrote:
> On Wed, 18 Jan 2017, David Carrillo-Cisneros wrote:
>> On Wed, Jan 18, 2017 at 12:53 AM, Thomas Gleixner wrote:
>> There are use cases where the RMID to CLOSID mapping is not that simple.
>> Some of them are:
>>
>> 1. Fine-tuning of cache
Hi Jinbum,
[auto build test ERROR on mmotm/master]
[also build test ERROR on v4.10-rc4 next-20170119]
[cannot apply to tip/x86/core]
[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/Jinbum-Park
On Fri, Jan 20, 2017 at 11:47:53AM +0900, Michel Dänzer wrote:
> On 20/01/17 04:35 AM, Nils Holland wrote:
> >
> > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c2016-12-11
> > 20:17:54.0 +0100
> > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c2017-01-19
> > 15:38:56.972034489
On Thu, Jan 19, 2017 at 9:31 PM, kbuild test robot wrote:
> Hi Gideon,
>
> [auto build test ERROR on m68k/for-next]
> [also build test ERROR on v4.10-rc4 next-20170119]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
&g
On Thu, Jan 19, 2017 at 6:19 PM, Yong Mao wrote:
>
> From: yong mao
>
> Add description for mtk-hs200-cmd-int-delay
> Add description for mtk-hs400-cmd-int-delay
> Add description for mtk-hs400-cmd-resp-sel
>
> Signed-off-by: Yong Mao
> ---
> Documentation/devicetree/bindings/mmc/mtk-sd.txt |
Commit-ID: acb04058de49458010c44bb35b849d45113fd668
Gitweb: http://git.kernel.org/tip/acb04058de49458010c44bb35b849d45113fd668
Author: Peter Zijlstra
AuthorDate: Thu, 19 Jan 2017 14:36:33 +0100
Committer: Ingo Molnar
CommitDate: Fri, 20 Jan 2017 02:38:46 +0100
sched/clock: Fix hotplug
On Wed, Dec 28, 2016 at 02:56:46PM -0800, Stephen Boyd wrote:
> The state of USB ChipIdea support on Qualcomm's platforms is not great.
> The DT description of these devices requires up to three different nodes
> for what amounts to be the same hardware block, when there should really
> only be one
On 20 January 2017 at 03:42, Shawn Lin wrote:
> On 2017/1/19 22:13, Ulf Hansson wrote:
>>
>> +Shawn
>>
>> On 13 January 2017 at 06:29, Matt Ranostay
>> wrote:
>>>
>>> Allow power sequencing for the Marvell SD8787 Wifi/BT chip.
>>> This can be abstracted to other chipsets if needed in the future.
* Jason Baron wrote:
> struct static_key {
> atomic_t enabled;
> +/*
> + * bit 0 => 1 if key is initially true
> + * 0 if initially false
> + * bit 1 => 1 if points to struct static_key_mod
> + * 0 if points to struct jump_entry
> + */
> + union {
> + unsigned
2017-01-20 10:29 GMT+08:00 Shawn Lin :
>
> On 2017/1/19 10:11, Eddie Cai wrote:
>>
>> This patch add basic support for RK3288-Tinker board. We can boot in to
>> rootfs
>> with this patch.
>>
>> Signed-off-by: Eddie Cai
>> ---
>> arch/arm/boot/dts/Makefile | 1 +
>> arch/arm/boot/dts/r
From: Tang Yuantian
Enable DMA coherence in SATA controller on condition that
dma-coherent property exists in sata node in DTS.
Signed-off-by: Tang Yuantian
---
v2:
- use of_dma_is_coherent() instead of open-coding.
drivers/ata/ahci_qoriq.c | 15 +++
1 file changed, 11 insertion
From: Tang Yuantian
For ls1021a, and armv8 chasis 2 socs, sata ecc must be disabled.
If ecc register is not found in sata node in dts, report error.
This is a chip erratum described as bellow:
The Read DMA operations get early termination indication from the
controller. This issue is observed as
From: Tang Yuantian
Ls2088a is new introduced arm-based soc with sata support with
following features:
1. Complies with the serial ATA 3.0 specification and the AHCI 1.3.1
specification
2. Contains a high-speed descriptor-based DMA controller
3. Supports the following:
a. Speeds of 1.5 Gb/s
2017-01-19 17:58 GMT+08:00 Heiko Stuebner :
> Hi Eddie,
>
> Am Donnerstag, 19. Januar 2017, 10:11:59 CET schrieb Eddie Cai:
>> This patch add basic support for RK3288-Tinker board. We can boot in to
>> rootfs with this patch.
>>
>> Signed-off-by: Eddie Cai
>
> looks good in general, just some smal
On Thu, Jan 19, 2017 at 02:48:03PM -0800, Dmitry Torokhov wrote:
> Let's drop legacy platform data support (there are no users in mainline)
> and switch to using generic device properties, which will make the driver
> simpler (non-OF boards can use property sets to describe hardware).
>
> Signed-o
On Friday, January 20, 2017 6:58 AM David Rientjes wrote:
>
> Commit 82e7d3abec86 ("oom: print nodemask in the oom report") implicitly
> sets the allocation nodemask to cpuset_current_mems_allowed when there is
> no effective mempolicy. cpuset_current_mems_allowed is only effective
> when cpuset
> I think you really could have squashed patches 1-3 into a single patch
> that returns directly after any failure.
Thanks for your constructive feedback.
I have got software development concerns around such patch squashing.
> At this point you might as well remove that label and move the kfree
Commit-ID: d852d39432f5d9822dd0ea8760573448338caf41
Gitweb: http://git.kernel.org/tip/d852d39432f5d9822dd0ea8760573448338caf41
Author: Geliang Tang
AuthorDate: Tue, 20 Dec 2016 21:57:44 +0800
Committer: Thomas Gleixner
CommitDate: Fri, 20 Jan 2017 08:03:42 +0100
timerqueue: Use rb_entr
In case of interlace mode irq is generated for odd and even fields, but
vblank should be signaled only for the last emitted field.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 7 +++
include/video/exynos5433_decon.h | 1 +
2 files changed, 8 i
VSI infoframe registers address space is non-contiguous, so infoframe write
should be split into two chunks.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/exynos/exynos_hdmi.c
b/drivers
In some platforms there is attached another device to the end of HDMI.
The patch adds support for it.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 56 +---
1 file changed, 46 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/e
297MHz is used by Ultra HD modes.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/gpu/drm/exynos/exynos_hdmi.c
b/drivers/gpu/drm/exynos/exynos_hdmi.c
index 5ed8b1e..bef8965 100644
--- a/drivers/gpu/drm/ex
Hi Inki,
This patchset adds support for UltraHD and intrelace modes on DECON and HDMI
drivers of Exynos5433 chipset. To fully support it on TM2(e) platforms MHL
patches are alse required which will be posted in separate patchset.
Krzysztof, DTS patch do not depend on the previous patches, so ther
Current settings for 27MHz and 27.027MHz do not work. Use the settings from
vendor code instead.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_hdmi.c
b/drivers/
Some registers should be programmed differently in interlace mode.
Additionally IP does not signal stop state properly in interlaced
mode, so warning has been removed.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/exynos/exynos5433_drm_decon.c | 45 +++
include/video/e
Ultra HD modes requires clock ticking at increased rate.
Signed-off-by: Andrzej Hajda
---
arch/arm64/boot/dts/exynos/exynos5433.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/boot/dts/exynos/exynos5433.dtsi
b/arch/arm64/boot/dts/exynos/exynos5433.dtsi
index f120d99..314d
On Tue, Dec 13, 2016 at 04:52:50PM +0100, Clemens Gruber wrote:
> When first implementing support for changing the output frequency, an
> optimization was added to continue the PWM after changing the prescaler
> without having to reprogram the ON and OFF registers for the duty cycle,
> in case the
* Stephen Rothwell wrote:
> Hi James,
>
> Today's linux-next merge of the scsi tree got a conflict in:
>
> drivers/scsi/mpt3sas/mpt3sas_scsih.c
>
> between commit:
>
> e963b7088dac ("scsi: mpt3sas: Fix hang on ata passthru commands")
>
> from the tip tree and commit:
>
> ffb584565894
The rtl8152_post_reset() should sumbit rx urb and interrupt transfer,
otherwise the rx wouldn't work and the linking change couldn't be
detected.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/
On Thursday, January 19, 2017 6:08 PM Mel Gorman wrote:
>
> If it's definitely required and is proven to fix the
> infinite-loop-without-oom workload then I'll back off and withdraw my
> objections. However, I'd at least like the following untested patch to
> be considered as an alternative. It
On Thu, Jan 19, 2017 at 05:52:10PM +0100, Clemens Gruber wrote:
> On Thu, Jan 19, 2017 at 06:10:08PM +0200, Andy Shevchenko wrote:
> > Combining with your proposal I would see the best approach is to set
> > pca->period_ns accordingly to current prescaler value if you want to.
>
> Yes, I agree.
>
On 2017-01-19 Michal Hocko wrote:
> On Thu 19-01-17 03:48:50, Trevor Cordes wrote:
> > On 2017-01-17 Michal Hocko wrote:
> > > On Tue 17-01-17 14:21:14, Mel Gorman wrote:
> > > > On Tue, Jan 17, 2017 at 02:52:28PM +0100, Michal Hocko
> > > > wrote:
> > > > > On Mon 16-01-17 11:09:34, Mel Go
Commit 501db511397f ("virtio: don't set VIRTIO_NET_HDR_F_DATA_VALID on
xmit") in fact disables VIRTIO_HDR_F_DATA_VALID on receiving path too,
fixing this by adding a hint (has_data_valid) and set it only on the
receiving path.
Cc: Rolf Neugebauer
Signed-off-by: Jason Wang
---
drivers/net/macvta
> Subject: [PATCH net] r8152: fix the rx doesn't work
>
> The rtl8152_post_reset() doesn't submit the rx urb, so the rx wouldn't work.
>
> Signed-off-by: Hayes Wang
Excuse me. Please ignore this patch. I would submit another one.
Hi Adrian,
Thanks for reviewing.
On 1/19/2017 5:24 PM, Adrian Hunter wrote:
On 10/01/17 08:41, Ritesh Harjani wrote:
print error log message and dump sdhc registers for debugging
purpose in case of data errors (except when tuning commands
generate CRC/timeout/end bit errors).
It is a bit ugl
The patch under discussion just appears wrong. Part of what we are
detecting when we ask if a task is dumpable is if a process might have
under gone a security transition. If a process has undergone a security
transition (calling setuid or the like) it is quite possible that
everyone with it's c
Hi,
On 01/17/2017 10:38 PM, Romain Perier wrote:
> Hi,
>
> In my case I can reproduce the issue on the rock2 and the firefly-rk3288. A
> workaround is to
>
> comment the line ".pm = <&pm_ops_foo>" .
Sorry for late. I'm checking runtime PM for this.
After that, i will decide whether revert or
On Thu, Jan 19, 2017 at 09:59:52AM +0800, Baoyou Xie wrote:
> This patch adds watchdog controller driver for ZTE's zx2967 family.
>
> Signed-off-by: Baoyou Xie
> ---
> drivers/watchdog/Kconfig | 10 ++
> drivers/watchdog/Makefile | 1 +
> drivers/watchdog/zx2967_wdt.c | 383
> ++
The rtl8152_post_reset() doesn't submit the rx urb, so the rx wouldn't work.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index f3b48ad..e8f4f88 100644
--- a/drivers/net/usb/r8152.c
+++
On 1/19/2017 4:13 PM, Adrian Hunter wrote:
On 18/01/17 09:57, Ritesh Harjani wrote:
Hi Shawn,
On 1/10/2017 2:45 PM, Shawn Lin wrote:
On 2017/1/10 14:41, Ritesh Harjani wrote:
From: Sahitya Tummala
Add new host operation ->platform_dumpregs to provide a
mechanism through which host drivers
Hi Adrian,
On 1/19/2017 4:25 PM, Adrian Hunter wrote:
On 10/01/17 08:41, Ritesh Harjani wrote:
From: Sahitya Tummala
Implement ->platform_dumpregs host operation to print the
platform specific registers in addition to standard SDHC
register during error conditions.
You could add an example
Hari Bathini writes:
> Get rid of multiple definitions of append_elf_note() & final_note()
> functions. Reuse these functions compiled under CONFIG_CRASH_CORE
> Also, define Elf_Word and use it instead of generic u32 or the more
> specific Elf64_Word.
>
> Signed-off-by: Hari Bathini
> ---
>
> Ch
Hi Laura,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc4]
[cannot apply to next-20170119]
[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/Laura-Abbott/Better
Hi,
This series of patches is a global rework of the mtk driver.
Fix bug - incomplete DMA data transfer when SG buffer dst.len != src.len
It also updates some part of the code to make them more generic. For
instance the crypto request queue management supports both async block
cipher and AEAD req
This patch adds support to the CTR mode.
Signed-off-by: Ryder Lee
---
drivers/crypto/mediatek/mtk-aes.c | 151 --
1 file changed, 146 insertions(+), 5 deletions(-)
diff --git a/drivers/crypto/mediatek/mtk-aes.c
b/drivers/crypto/mediatek/mtk-aes.c
index 5e7c3
This patch moves hardware control block members from
mtk_*_rec to transformation context and refines related
definition. This makes operational context to manage its
own control information easily for each DMA transfer.
Signed-off-by: Ryder Lee
---
drivers/crypto/mediatek/mtk-aes.c | 144 ++
This patch adds support to the GCM mode.
Signed-off-by: Ryder Lee
---
drivers/crypto/Kconfig | 2 +
drivers/crypto/mediatek/mtk-aes.c | 369 -
drivers/crypto/mediatek/mtk-platform.h | 2 +
3 files changed, 369 insertions(+), 4 deletions(-)
This patch only regroup functions by usage.
This will help to integrate the GCM support patch later by
adjusting some shared code section, such as common code which
will be reused by GCM, AES mode setting, and DMA transfer.
Signed-off-by: Ryder Lee
---
drivers/crypto/mediatek/mtk-aes.c | 272 +++
This patch introduces a new callback 'resume' in the struct mtk_aes_rec.
This callback is run to resume/complete the processing of the crypto
request when woken up by AES interrupts when DMA completion.
This callback will help implementing the GCM mode support in further
patches.
Signed-off-by: R
This patch changes mtk_aes_handle_queue() to make it more generic.
The function argument is now a pointer to struct crypto_async_request,
which is the common base of struct ablkcipher_request and
struct aead_request.
Also this patch introduces struct mtk_aes_base_ctx which will be the
common base
This patch fixes mtk_aes_xmit() data transfer bug.
The original function uses the same loop and ring->pos
to handle both command and result descriptors. But this
produces incomplete results when src.sg_len != dst.sg_len.
To solve the problem, we splits the descriptors into different
loops and use
Dummy patch to fix typo and indentation.
Signed-off-by: Ryder Lee
---
drivers/crypto/mediatek/mtk-aes.c | 90 +-
drivers/crypto/mediatek/mtk-platform.h | 2 +-
drivers/crypto/mediatek/mtk-sha.c | 40 +++
3 files changed, 63 insertions(+), 69
Update MAINTAINERS file with cpufreq's selftest directory.
Signed-off-by: Viresh Kumar
---
Hi shuah,
Can you please add this one as well along with the code? Thanks.
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index c36976d3bd1a..bf414a1a5f82 10064
Hi Ted,
On Wed, Jan 18, 2017 at 4:49 AM, Theodore Ts'o wrote:
> You're using a union for the entropy_u64 and entropy_u32 arrays, and
> the position field is used to indexed into those two arrays.
>
> So if the first caller calls get_random_u64 with position=0, it will
> get the first 64 bits out
The kmalloc(sizeof(struct foo), ...) => kmalloc(sizeof(*foo), ...)
ones are OK.
The rest is cargo-cult programming.
Jeff
--
Jeff Dike
AddToIt
978-254-0789 (o)
978-394-8986 (c)
t ERROR on m68k/for-next]
> [also build test ERROR on v4.10-rc4 next-20170119]
> [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/Gideon-Israel-Dsouza/compiler-gcc-h-Added
On 1/20/2017 2:23 AM, Ulf Hansson wrote:
On 10 January 2017 at 08:00, Ritesh Harjani wrote:
Hi,
Resending this patch series, as no one could review it -possibly due to
holidays during that time.
This patch series mainly provides enhanced strobe support to sdhci-msm driver
along with some add
On Wed, Jan 18, 2017 at 1:17 AM, Dmitry Vyukov wrote:
> On Tue, Jan 17, 2017 at 10:21 PM, Cong Wang wrote:
>> On Mon, Jan 16, 2017 at 1:32 AM, Dmitry Vyukov wrote:
>>> On Fri, Dec 9, 2016 at 7:41 AM, Al Viro wrote:
On Thu, Dec 08, 2016 at 10:32:00PM -0800, Cong Wang wrote:
> > Why
drivers/mmc/host/mtk-sd.c:1400:4-5: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: yong mao
Signed-off-by: Fengguang Wu
---
mtk-sd.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/mmc/host/mtk-sd.c
+++ b/driv
Hi yong,
[auto build test WARNING on robh/for-next]
[also build test WARNING on v4.10-rc4 next-20170119]
[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/Yong-Mao/mmc-mediatek-Use-data-tune-for
Hi all,
Changes since 20170119:
The staging tree gained a conflict against the devicetree tree.
The scsi tree gained a conflict against the tip tree.
Non-merge commits (relative to Linus' tree): 4186
4975 files changed, 155300 insertions(+), 92435 dele
On Thu, Jan 19, 2017 at 6:39 PM, Alexei Starovoitov
wrote:
> On Wed, Jan 18, 2017 at 06:29:22PM -0800, Andy Lutomirski wrote:
>> I think it could work by making a single socket cgroup controller that
>> handles all cgroup things that are bound to a socket. Using
>
> Such 'socket cgroup controller
Aleksa Sarai writes:
>> Please verify but the ptrace issue that allowed processes in a container
>> to call setns on our processes should be fixed as of 4.10-rc1. And the
>> change has been marked for backporting.
>
> ptrace(2) is not the only issue, the issue that we had in runC is that
> a pro
Hi Greg,
After merging the staging tree, today's linux-next build (powerpc
allyesconfig) produced this warning:
warning: (IIO_ST_ACCEL_3AXIS) selects IIO_ST_ACCEL_I2C_3AXIS which has unmet
direct dependencies (IIO && !SENSORS_LIS3_I2C && IIO_ST_ACCEL_3AXIS &&
IIO_ST_SENSORS_I2C)
warning: (IIO_S
From: Mike Frysinger
The SECCOMP_RET_KILL mode is documented as immediately killing the
process as if a SIGSYS had been sent and not caught (similar to a
SIGKILL). However, a SIGSYS is documented as triggering a coredump
which does not happen today.
This has the advantage of being able to more
Hello Jingoo, Bjorn,
On Thursday 05 January 2017 09:47 AM, Jaehoon Chung wrote:
> On 01/05/2017 12:53 PM, Pankaj Dubey wrote:
>> From: Niyas Ahmed S T
>>
>> Currently Exynos PCIe driver is only supported for Exynos5440 SoC.
>> This patch does refactoring of Exynos PCIe driver to extend support
>>
Hi Javier,
On Wednesday 18 January 2017 09:06 PM, Javier Martinez Canillas wrote:
> Hello,
>
> On 01/18/2017 04:04 AM, Chanwoo Choi wrote:
>> Hi Pankaj,
>>
>> This issue already posted by Javier Martinez Canillas[1].
>> Maybe, he will post v2.
>>
>
> That's correct, I didn't post a v2 since I wa
This is a set of 12 fixes including the mpt3sas one that was causing
hangs on ATA passthrough. The others are a couple of zoned block
device fixes, a SAS device detection bug which lead to SATA drives not
being matched to bays, two qla2xxx MSI fixes, a qla2xxx req for rsp
confusion caused by cut a
The pmem driver assumes if platform firmware describes the memory
devices associated with a persistent memory range and
CONFIG_ARCH_HAS_PMEM_API=y that it has all the mechanism necessary to
flush data to a power-fail safe zone. We warn if the firmware does not
describe memory devices, but we also n
Allow volatile nfit ranges to participate in all the same infrastructure
provided for persistent memory regions. A resulting resulting namespace
device will still be called "pmem", but the parent region type will be
"nd_volatile". This is in preparation for disabling the dax ->flush()
operation in
These stand-alone trigger drivers were using iio_trigger_put()
where they should have been using iio_trigger_free(). The
iio_trigger_put() adds a module_put which is bad since they
never did a module_get.
In the sysfs driver, module_get/put's are used as triggers are
added & removed. This extra m
There are platforms that arrange for caches to be flushed on a power
fail event. When the platform has this capability it is redundant to
spend cycles flushing caches at fsync(). Provide a libnvdimm module
parameter to override the default flushing behavior since there is no
other mechanism defined
The pmem driver attaches to both persistent and volatile memory ranges
advertised by the ACPI NFIT. When the region is volatile it is redundant
to spend cycles flushing caches at fsync(). Check if the hosting region
is volatile and do not publish a ->flush() dax method if so.
Cc: Jan Kara
Cc: Jef
The pmem and nd_blk drivers both have need to copy data through the cpu
cache to persistent memory. To date they have been abusing
__copy_user_nocache through the memcpy_to_pmem abstraction, but this has
several problems:
* __copy_user_nocache does not guarantee that it will always avoid the
cache
Introduce copy_from_iter_ops() to enable passing custom sub-routines to
iterate_and_advance(). Define pmem operations that guarantee cache
bypass to supplement the existing usage of __copy_from_iter_nocache()
backed by arch_wb_cache_pmem().
Cc: Jan Kara
Cc: Jeff Moyer
Cc: Christoph Hellwig
Cc:
Kill this globally defined wrapper and move to libnvdimm so that we can
ultimately remove the public pmem api.
Cc:
Cc: Jan Kara
Cc: Jeff Moyer
Cc: Ingo Molnar
Cc: Christoph Hellwig
Cc: "H. Peter Anvin"
Cc: Thomas Gleixner
Cc: Matthew Wilcox
Cc: Ross Zwisler
Signed-off-by: Dan Williams
--
With all calls to this routine re-directed through the pmem driver, we
can kill the pmem api indirection. arch_wb_cache_pmem() is now
optionally supplied by an arch specific extension to libnvdimm. Same as
before, pmem flushing is only defined for x86_64, but it is
straightforward to add other arc
Prepare for the removal of memcpy_to_pmem() and copy_from_iter_pmem() by
introducing dax_ops. This allows for driver specific overrides for the
routines that transfer data to a dax capable block device.
Cc:
Cc: Jan Kara
Cc: Jens Axboe
Cc: Jeff Moyer
Cc: Christoph Hellwig
Cc: Toshi Kani
Cc: M
The clear_pmem() helper simply combines a memset() plus a cache flush.
Now that the flush routine is optionally provided by the dax device
driver we can avoid unnecessary cache management on dax devices fronting
volatile memory.
With clear_pmem() gone we can follow on with a patch to make pmem cac
Filesystem-DAX flushes caches whenever it writes to the address returned
through dax_map_atomic() and when writing back dirty radix entries. That
flushing is only required in the pmem case, so add a dax operation to
allow pmem to take this extra action, but skip it for other dax capable
block_devic
memcpy_from_pmem() maps directly to memcpy_mcsafe(). The wrapper
serves no real benefit aside from affording a more generic function name
than the x86-specific 'mcsafe'. However this would not be the first time
that x86 terminology leaked into the global namespace. For lack of
better name, just use
A couple weeks back, in the course of reviewing the memcpy_nocache()
proposal from Brian, Linus subtly suggested that the pmem specific
memcpy_to_pmem() routine be moved to be implemented at the driver
level [1]:
"Quite frankly, the whole 'memcpy_nocache()' idea or (ab-)using
copy_user_noca
The direct-I/O write path for a pmem device must ensure that data is flushed
to a power-fail safe zone when the operation is complete. However, other
dax capable block devices, like brd, do not have this requirement.
Introduce a 'copy_from_iter' dax operation so that pmem can inject
cache managemen
It will be used when checking graph filter hashes later.
Signed-off-by: Namhyung Kim
---
kernel/trace/ftrace.c | 14 +-
kernel/trace/trace.h | 14 ++
2 files changed, 15 insertions(+), 13 deletions(-)
diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
index 37b0
Use ftrace_hash instead of a static array of a fixed size. This is
useful when a graph filter pattern matches to a large number of
functions. Now hash lookup is done with preemption disabled to protect
from the hash being changed/freed.
Signed-off-by: Namhyung Kim
---
kernel/trace/ftrace.c | 1
The __ftrace_hash_move() is to allocates properly-sized hash and move
entries in the src ftrace_hash. It will be used to set function graph
filters which has nothing to do with the dyn_ftrace records.
Signed-off-by: Namhyung Kim
---
kernel/trace/ftrace.c | 40 ---
Hi James,
Today's linux-next merge of the scsi tree got a conflict in:
drivers/scsi/mpt3sas/mpt3sas_scsih.c
between commit:
e963b7088dac ("scsi: mpt3sas: Fix hang on ata passthru commands")
from the tip tree and commit:
ffb584565894 ("scsi: mpt3sas: fix hang on ata passthrough commands"
On 01/19/17 13:45, Denys Vlasenko wrote:
> On Wed, Jan 18, 2017 at 7:07 PM, Theodore Ts'o wrote:
>> In the ideal world, yes. I've acknowledged this is a bug, in the "be
>> conservative in what you send, liberal in what you receive" sense..
>> But no one complained for three year, and userspace ne
On Thu, Jan 19, 2017 at 8:55 PM, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the staging tree got a conflict in:
>
> Documentation/devicetree/bindings/vendor-prefixes.txt
>
> between commit:
>
> 566088d1d2a0 ("devicetree: Add Fujitsu Ltd. vendor prefix")
>
> from the dev
On Fri, 2017-01-13 at 09:27 +0800, Horng-Shyang Liao wrote:
> On Wed, 2017-01-04 at 11:06 +0800, HS Liao wrote:
> > Hi,
> >
> > This is Mediatek MT8173 Command Queue(CMDQ) driver. The CMDQ is used
> > to help write registers with critical time limitation, such as
> > updating display configuration
> -Original Message-
> From: Tejun Heo [mailto:hte...@gmail.com] On Behalf Of Tejun Heo
> Sent: Thursday, January 19, 2017 3:54 AM
> To: Y.T. Tang
> Cc: robh...@kernel.org; mark.rutl...@arm.com; linux-...@vger.kernel.org;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; linux-
Hi Ingo,
On 01/19/2017 05:12 PM, Ingo Molnar wrote:
> * Lu Baolu wrote:
>
>> xHCI debug capability (DbC) is an optional but standalone
>> functionality provided by an xHCI host controller. With DbC
>> hardware initialized, the system will present a debug device
>> through the USB3 debug port (nor
On Fri, Jan 20, 2017 at 3:34 AM, Agustin Vega-Frias
wrote:
> Add support for IRQ combiners in the Top-level Control and Status
> Registers (TCSR) hardware block in Qualcomm Technologies chips.
>
> The first patch prevents the ACPI core from attempting to map IRQ resources
> with a valid ResourceSo
1 - 100 of 929 matches
Mail list logo
