On Fri, May 18, 2018 at 01:27:03AM +, Trent Piepho wrote:
>
> I've hit this on an embedded system. mke2fs hangs trying to format a
> persistent writable filesystem, which is where the random seed to
> initialize the kernel entropy pool would be stored, because it wants 16
> bytes of non-crypt
Add gpio support to pinctrl driver for Actions Semi S900 SoC.
Signed-off-by: Manivannan Sadhasivam
---
drivers/pinctrl/actions/Kconfig| 1 +
drivers/pinctrl/actions/pinctrl-owl.c | 206 +
drivers/pinctrl/actions/pinctrl-owl.h | 20
drivers/pinctr
Add gpio line names to Actions Semi S900 based Bubblegum-96 board.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm64/boot/dts/actions/s900-bubblegum-96.dts | 175 ++
1 file changed, 175 insertions(+)
diff --git a/arch/arm64/boot/dts/actions/s900-bubblegum-96.dts
b/arch/ar
This patchset adds gpio support for Actions Semi S900 SoC by extending
the pinctrl driver. There were previous patches submitted for adding a
standalone gpio driver based on gpiolib. But later on it has been realised
that the gpio functionality is closely tied with pinctrl subsystem for this
OWL fa
Add gpio properties to pinctrl node for Actions Semi S900 SoC.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm64/boot/dts/actions/s900.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/actions/s900.dtsi
b/arch/arm64/boot/dts/actions/s900.dtsi
index 0156483f0f4d..0
Add gpio bindings for Actions Semi S900 SoC.
Signed-off-by: Manivannan Sadhasivam
---
.../devicetree/bindings/pinctrl/actions,s900-pinctrl.txt| 13 +
1 file changed, 13 insertions(+)
diff --git a/Documentation/devicetree/bindings/pinctrl/actions,s900-pinctrl.txt
b/Documentation
Please reply me back
Hi,
On 2018년 05월 17일 15:02, Saravana Kannan wrote:
> The firmware present in some QCOM chipsets offloads the steps necessary for
> changing the frequency of some devices (Eg: L3). This driver implements the
> devfreq interface for this firmware so that various governors could be used
> to scale th
On 5/17/2018 8:22 PM, Long Li wrote:
From: Long Li
This patchset implements direct user I/O through RDMA.
In normal code path (even with cache=none), CIFS copies I/O data from
user-space to kernel-space for security reasons.
With this patchset, a new mounting option is introduced to have CIFS
On 17-05-18, 21:00, Dmitry Osipenko wrote:
> Tegra20-cpufreq driver require a platform device in order to be loaded,
> instantiate a simple platform device for the driver during of the machines
> late initialization.
>
> Signed-off-by: Dmitry Osipenko
> ---
> arch/arm/mach-tegra/tegra.c | 4
On 17-05-18, 21:00, Dmitry Osipenko wrote:
> -static int __init tegra_cpufreq_init(void)
> +static int tegra20_cpufreq_probe(struct platform_device *pdev)
> {
> + struct tegra20_cpufreq_data *data;
> int err;
>
> - if (!of_machine_is_compatible("nvidia,tegra20"))
> - re
On (05/17/18 16:39), Petr Mladek wrote:
>
> CPU0 CPU1CPU2
>
> printk()
> vprintk_emit()
> spin_lock(&logbuf_lock)
>
> trigger_all_cpu_backtrace()
> raise()
>
Use the existing audit_log_session_info() function rather than
hardcoding its functionality.
Signed-off-by: Richard Guy Briggs
---
kernel/auditfilter.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/kernel/auditfilter.c b/kernel/auditfilter.c
index d7a807e..9e87377 100644
The __dentry_open function was removed in
commit <2a027e7a18738>("fold __dentry_open() into its sole caller").
Signed-off-by: Li Qiang
---
include/linux/fs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/fs.h b/include/linux/fs.h
index 760d8da1b6c7..7f07977bdf
On 17-05-18, 21:00, Dmitry Osipenko wrote:
> Nothing prevents Tegra20 CPUFreq module to be unloaded, hence allow it to
> be built as a non-builtin kernel module.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/cpufreq/Kconfig.arm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> di
From: "Joel Fernandes (Google)"
Here we add unit tests for the preemptoff and irqsoff tracer by using a
kernel module introduced previously to trigger atomic sections in the
kernel.
Cc: Steven Rostedt
Cc: Peter Zilstra
Cc: Ingo Molnar
Cc: Mathieu Desnoyers
Cc: Tom Zanussi
Cc: Namhyung Kim
On 17-05-18, 21:00, Dmitry Osipenko wrote:
> Remove unneeded variable initialization solely for consistency.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/cpufreq/tegra20-cpufreq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/tegra20-cpufreq.c
>
On 17-05-18, 21:00, Dmitry Osipenko wrote:
> Don't even try to request the clocks during of module initialization on
> non-Tegra20 machines (this is the case for a multi-platform kernel) for
> consistency.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/cpufreq/tegra20-cpufreq.c | 4
> 1
From: "Joel Fernandes (Google)"
Hi,
Here is test code and kselftest for testing the preemptoff and irqsoff
tracers. I am posting it separately just for early feedback since its
the first time I'm writing a kselftest.
I am planning to include these tests in the next series posting of
"Centralize
On 17-05-18, 21:00, Dmitry Osipenko wrote:
> Remove checking of the CPU number for consistency as it won't ever fail
> unless there is a severe bug in the cpufreq core.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/cpufreq/tegra20-cpufreq.c | 5 -
> 1 file changed, 5 deletions(-)
>
> d
From: "Joel Fernandes (Google)"
In this patch we introduce a test module for simulating a long atomic
section in the kernel which the preemptoff or irqsoff tracers can
detect. This module is to be used only for test purposes and is default
disabled.
Following is the expected output (only briefly
On 17-05-18, 21:00, Dmitry Osipenko wrote:
> Remove unused/unneeded headers and sort them in the alphabet order.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/cpufreq/tegra20-cpufreq.c | 11 ++-
> 1 file changed, 2 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/cpufreq/tegr
On 17-05-18, 21:00, Dmitry Osipenko wrote:
> Properly put requested clocks in the module init/exit code.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/cpufreq/tegra20-cpufreq.c | 31 ++-
> 1 file changed, 26 insertions(+), 5 deletions(-)
>
> diff --git a/drivers
On 17-05-18, 21:00, Dmitry Osipenko wrote:
> The EMC driver has been gone 4 years ago, since the commit a7cbe92cef27
> ("ARM: tegra: remove tegra EMC scaling driver"). Remove the EMC clock
> usage as it does nothing. We may consider re-implementing the EMC scaling
> later, probably using PM Memory
Here we add unit tests for the preemptoff and irqsoff tracer by using a
kernel module introduced previously to trigger atomic sections in the
kernel.
Cc: Steven Rostedt
Cc: Peter Zilstra
Cc: Ingo Molnar
Cc: Mathieu Desnoyers
Cc: Tom Zanussi
Cc: Namhyung Kim
Cc: Thomas Glexiner
Cc: Boqun Fen
On 17-05-18, 21:00, Dmitry Osipenko wrote:
> Change module description to be in line with the other Tegra drivers, just
> for consistency.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/cpufreq/tegra20-cpufreq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/driver
On 17-05-18, 21:00, Dmitry Osipenko wrote:
> Remove unneeded blank line and replace whitespaces with a tab in the code
> for consistency.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/cpufreq/tegra20-cpufreq.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drive
Hi Suzuki
On 5/17/2018 11:03 PM, Suzuki K Poulose Wrote:
> On 17/05/18 13:46, Jia He wrote:
>> Hi Suzuki
>>
>> On 5/17/2018 4:17 PM, Suzuki K Poulose Wrote:
>>>
>>> Hi Jia,
>>>
>>> On 17/05/18 07:11, Jia He wrote:
I ever met a panic under memory pressure tests(start 20 guests and run
mem
On 2018/5/8 5:36, Jaegeuk Kim wrote:
> On 05/07, Chao Yu wrote:
>> Thread A Thread BThread C
>> - f2fs_remount
>> - stop_gc_thread
>> - f2fs_sbi_store
>> - issue_discard_thread
>>
On 17-05-18, 14:19, Ilia Lin wrote:
> +static int __init qcom_cpufreq_kryo_driver_init(void)
> +{
> + size_t len;
> + int ret = 0;
> + u32 versions;
> + enum _msm8996_version msm8996_version;
> + u8 *speedbin;
> + struct device *cpu_dev_silver, *cpu_dev_gold;
> + struct
On Thu, May 17, 2018 at 6:41 PM, hl wrote:
> On Thursday, May 17, 2018 09:51 PM, Sean Paul wrote:
>> On Thu, May 17, 2018 at 05:18:00PM +0800, Lin Huang wrote:
>>> DP firmware uses fixed phy config values to do training, but some
>>> boards need to adjust these values to fit for their unique hardw
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 3acf4e395260e3bd30a6fa29ba7eada4bf7566ca
commit: ea14b57e8a181ac0561eba7a787e088f8c89f822 sched/cpufreq: Provide
migration hint
date: 2 months ago
reproduce: make htmldocs
All warnings (new ones prefixed
+ Kishon
On Thursday, May 17, 2018 09:51 PM, Sean Paul wrote:
On Thu, May 17, 2018 at 05:18:00PM +0800, Lin Huang wrote:
DP firmware uses fixed phy config values to do training, but some
boards need to adjust these values to fit for their unique hardware
design. So get phy config values from d
On 05/17/18 at 07:04pm, James Morse wrote:
> Hi Baoquan,
>
> On 17/05/18 03:15, Baoquan He wrote:
> > On 05/17/18 at 10:10am, Baoquan He wrote:
> >> On 05/07/18 at 02:59pm, AKASHI Takahiro wrote:
> >>> On Tue, May 01, 2018 at 06:46:09PM +0100, James Morse wrote:
> On 25/04/18 07:26, AKASHI Ta
Hi Jaegeuk,
Could you recheck this patch?
On 2018/4/23 10:36, Chao Yu wrote:
> After revoking atomic write, related LBA can be reused by others, so we
> need to wait page writeback before reusing the LBA, in order to avoid
> interference between old atomic written in-flight IO and new IO.
>
> Si
Since I wasn't on this thread from the start, I can only find a way to
reply to message in mbox format on patchwork, and this seemed the best.
On Fri, 2018-04-27 at 16:10 -0400, Theodore Tso wrote:
>
>
> This is why ultimately, we do need to attack this problem from both
> ends, which means teac
A coresight topology doesn't need to include links, i.e., a source can
be directly connected to a sink. As such, selecting and/or depending on
LINKS_AND_SINKS is no longer needed.
Suggested-by: Mathieu Poirier
Cc: Alexander Shishkin
Signed-off-by: Kim Phillips
---
drivers/hwtracing/coresight/
barrier_pkt[] is used in various coresight components.
Change barrier_pkt[] to a static definition in the coresight
private header. Needed prior to allowing coresight to be
built as modules.
Suggested-by: Mathieu Poirier
Signed-off-by: Kim Phillips
---
drivers/hwtracing/coresight/coresight-pri
Allow to build coresight as modules. This greatly enhances developer
efficiency by allowing the development to take place exclusively on the
target, and without needing to reboot in between changes.
- Kconfig bools become tristates, to allow =m
- use -objs to denote merge object directives in Ma
Checking for CONFIG_x fails if CONFIG_x=m, use IS_ENABLED that is
true for built-ins and modules instead. Required when building
various coresight components as modules.
Signed-off-by: Kim Phillips
---
drivers/hwtracing/coresight/coresight-etm-perf.h | 2 +-
drivers/hwtracing/coresight/coresigh
From: Florian Fainelli Sent: 2018年5月18日 4:08
> The Freescale FEC driver builds fine with COMPILE_TEST, so make that
> possible.
>
> Signed-off-by: Florian Fainelli
Acked-by: Fugang Duan
> ---
> drivers/net/ethernet/freescale/Kconfig| 2 +-
> drivers/net/ethernet/freescale/fec.h | 2
coresight-stm unconditionally calls stm_register_device. This
patch makes it therefore depend on STM instead of just selecting STM.
Signed-off-by: Kim Phillips
---
drivers/hwtracing/coresight/Kconfig | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/hwtracing/coresig
Necessary prior to enabling to be built as modules.
Signed-off-by: Kim Phillips
---
drivers/hwtracing/coresight/coresight-dynamic-replicator.c | 4
drivers/hwtracing/coresight/coresight-etb10.c | 5 +
drivers/hwtracing/coresight/coresight-etm-cp14.c | 4
driv
My powerpc-linux-gnu-gcc v4.4.5 compiler can't build a 32-bit kernel
any more:
arch/powerpc/lib/sstep.c: In function 'do_popcnt':
arch/powerpc/lib/sstep.c:1068: error: integer constant is too large for 'long'
type
arch/powerpc/lib/sstep.c:1069: error: integer constant is too large for 'long'
typ
On Thu, 2018-05-17 at 21:39 +0200, Alexandre Belloni wrote:
> On 17/05/2018 12:28:59-0700, Joe Perches wrote:
> > On Thu, 2018-05-17 at 21:23 +0200, Alexandre Belloni wrote:
> > > ocelot_qsys.h is missing the SPDX identfier, fix that.
> > >
> > > Signed-off-by: Alexandre Belloni
> >
> > Only the
Hi, Stefan
Anson Huang
Best Regards!
> -Original Message-
> From: Stefan Agner [mailto:ste...@agner.ch]
> Sent: Thursday, May 17, 2018 7:22 PM
> To: Anson Huang
> Cc: shawn...@kernel.org; ker...@pengutronix.de; Fabio Estevam
> ; robh...@kernel.org; mark.rutl...@arm.com;
> mturque...@bay
ENET "ipg" clock should be IMX7D_ENETx_IPG_ROOT_CLK
rather than IMX7D_ENET_AXI_ROOT_CLK which is for ENET bus
clock.
Based on Andy Duan's patch from the NXP kernel tree.
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx7d.dtsi | 2 +-
arch/arm/boot/dts/imx7s.dtsi | 2 +-
2 files changed, 2 i
On 05/17, Chao Yu wrote:
> On 2018/5/17 16:03, Sahitya Tummala wrote:
> > f2fs_ioc_shutdown() ioctl gets stuck in the below path
> > when issued with F2FS_GOING_DOWN_FULLSYNC option.
> >
> > __switch_to+0x90/0xc4
> > percpu_down_write+0x8c/0xc0
> > freeze_super+0xec/0x1e4
> > freeze_bdev+0xc4/0xcc
Hi Alexander,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc5 next-20180517]
[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
IMX7D_ENET_PHY_REF_ROOT_DIV supplies clock for PHY directly,
there is no clock gate after it, rename it to
IMX7D_ENET_PHY_REF_ROOT_CLK to avoid device tree change.
Signed-off-by: Anson Huang
---
drivers/clk/imx/clk-imx7d.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/dri
Correct enet clock gates as below:
CCGR6: IMX7D_ENET_AXI_ROOT_CLK (enet1 and enet2 bus clocks)
CCGR112: IMX7D_ENET1_TIME_ROOT_CLK, IMX7D_ENET1_IPG_ROOT_CLK
CCGR113: IMX7D_ENET2_TIME_ROOT_CLK, IMX7D_ENET2_IPG_ROOT_CLK
Just rename unused IMX7D_ENETx_REF_ROOT_CLK for
IMX7D_ENETx_IPG_ROOT_CLK instead
Hi,
On Thu, May 17, 2018 at 5:16 PM, David Collins wrote:
> On 05/17/2018 02:22 PM, Doug Anderson wrote:
>> On Fri, May 11, 2018 at 7:28 PM, David Collins
>> wrote:
>>> +- qcom,regulator-initial-microvolt
>>> + Usage: optional; VRM regulators only
>>> + Value type:
>>> +
Hi Vikash,
On 5/17/2018 4:32 AM, Vikash Garodia wrote:
This adds support to load the video firmware
and bring ARM9 out of reset. This is useful
for platforms which does not have trustzone
to reset the ARM9.
ARM9 = video core here? May be commit text needs little bit more detail.
+static in
On Thu, May 17, 2018 at 1:20 PM, Richard Guy Briggs wrote:
> Enable fork.c compilation with audit disabled.
>
> Signed-off-by: Richard Guy Briggs
> ---
> Hi Paul, this one got caught by the 0-day kbuildbot. Can you squash it
> down if you haven't merged it yet?
See my comment in the original pa
On 5/18/2018 4:27 AM, Jiri Olsa wrote:
On Thu, May 17, 2018 at 01:27:50PM -0300, Arnaldo Carvalho de Melo wrote:
Em Thu, May 10, 2018 at 09:59:22PM +0800, Jin Yao escreveu:
See example,
perf record -e cycles,branches ./div
perf annotate main --stdio or
perf annotate main --stdio2 or
perf ann
From: Long Li
When cache=rdma is enabled on mount options, CIFS do not allocate internal data
buffer pages for I/O, data is read/writen directly to user memory via RDMA.
Signed-off-by: Long Li
---
fs/cifs/cifs_fs_sb.h | 2 ++
fs/cifs/cifsglob.h | 1 +
fs/cifs/connect.c| 9 +
fs/c
On 5/17/2018 7:48 AM, Mimi Zohar wrote:
> In order for LSMs and IMA-appraisal to differentiate between the original
> and new syscalls (eg. kexec, kernel modules, firmware), both the original
> and new syscalls must call an LSM hook.
>
> Commit 2e72d51b4ac3 ("security: introduce kernel_module_from_
From: Long Li
When doing RDMA send, the offset needs to be checked as data may start in an
offset
in the 1st page.
Signed-off-by: Long Li
---
fs/cifs/smb2pdu.c | 3 ++-
fs/cifs/smbdirect.c | 25 +++--
2 files changed, 21 insertions(+), 7 deletions(-)
diff --git a/fs/ci
From: Long Li
This patchset implements direct user I/O through RDMA.
In normal code path (even with cache=none), CIFS copies I/O data from
user-space to kernel-space for security reasons.
With this patchset, a new mounting option is introduced to have CIFS pin the
user-space buffer into memory
From: Long Li
When using direct pages from user space, there is no need to allocate pages.
Just ping those user pages for RDMA.
Signed-off-by: Long Li
---
fs/cifs/cifsproto.h | 2 +-
fs/cifs/cifssmb.c | 10 +++---
fs/cifs/file.c | 4 ++--
3 files changed, 10 insertions(+), 6 dele
From: Long Li
There is no need to allocate pages when using pages directly from user buffer
Signed-off-by: Long Li
---
fs/cifs/file.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/fs/cifs/file.c b/fs/cifs/file.c
index a6ec896..ed25e04 100644
--- a/fs/cifs/fi
From: Long Li
It's possible that we may want to read data into an offset to the 1st page,
change
the functions to pass the offset to transport.
Signed-off-by: Long Li
---
fs/cifs/cifsproto.h | 2 +-
fs/cifs/connect.c | 4 ++--
fs/cifs/file.c | 4 ++--
fs/cifs/smb2ops.c | 2 +-
4 file
On 05/17/2018 04:26 PM, a...@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2018-05-17-16-26 has been uploaded to
>
>http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of m
From: Long Li
Currently CIFS allocates its own pages for data transfer, they don't need offset
since it's always 0 in the 1st page.
Direct data transfer needs to define an offset because user-data may not start
on the page boundary
Signed-off-by: Long Li
---
fs/cifs/cifsglob.h | 5 +
1 fi
From: Long Li
The actaul data buffer may start with an offset in the 1st page, modify RDMA
recv
function to read the data to the correct buffer.
Signed-off-by: Long Li
---
fs/cifs/smbdirect.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/fs/cifs/smbdirect.c
From: Long Li
Now momory registration needs to recognize offset in page when direct transfer
is
used.
Signed-off-by: Long Li
---
fs/cifs/smb2pdu.c | 19 +-
fs/cifs/smbdirect.c | 74 +++--
fs/cifs/smbdirect.h | 2 +-
3 files change
From: Long Li
Implement the main filesystem interface for doing read and write. These
functions
don't copy the user data into a kenrel buffer for data transfer. Pages are
directly
pinned and passed to the RDMA transport.
Signed-off-by: Long Li
---
fs/cifs/cifsfs.c | 19
fs/cifs/cifsfs.
On 05/17/2018 02:22 PM, Doug Anderson wrote:
> On Fri, May 11, 2018 at 7:28 PM, David Collins
> wrote:
>> +- qcom,regulator-initial-microvolt
>> + Usage: optional; VRM regulators only
>> + Value type:
>> + Definition: Specifies the initial voltage in microvolts to request
On 05/17/2018 02:23 PM, Doug Anderson wrote:
> On Fri, May 11, 2018 at 7:28 PM, David Collins
> wrote:
>> + /*
>> +* Default the voltage selector to an error value in
>> the
>> +* case that qcom,regulator-initial-microvolt is
On 5/18/2018 4:06 AM, Arnaldo Carvalho de Melo wrote:
Em Thu, May 17, 2018 at 10:58:38PM +0800, Jin Yao escreveu:
In perf annotate view, a new hotkey 'c' is created for
showing the max/min cycles.
I just changed everything from "max/min" to "min/max", as it looked
strange print the max first
Even if commit 1d27732f411d ("net: dsa: setup and teardown ports") indicated
that registering a devlink instance for unused ports is not a problem, and this
is true, this can be confusing nonetheless, so let's not do it.
Fixes: 1d27732f411d ("net: dsa: setup and teardown ports")
Reported-by: Jiri
On Thu, May 17, 2018, at 11:28 PM, Mathieu Desnoyers wrote:
> - On May 16, 2018, at 9:19 PM, Boqun Feng boqun.f...@gmail.com wrote:
>
> > On Wed, May 16, 2018 at 04:13:16PM -0400, Mathieu Desnoyers wrote:
> >> - On May 16, 2018, at 12:18 PM, Peter Zijlstra pet...@infradead.org
> >> wrot
On Fri, 2018-05-18 at 00:35 +0100, Dmitry Safonov wrote:
> The x86 mmap() code selects the mmap base for an allocation depending
> on
> the bitness of the syscall. For 64bit sycalls it select mm->mmap_base
> and
> for 32bit mm->mmap_compat_base.
>
> exec() calls mmap() which in turn uses in_compa
On Thu, 17 May 2018 14:07:40 -0700
Michael Kelley wrote:
> Current code allocates 240 Kbytes (in typical configs) for
> each synthetic SCSI controller to use as temp cpumask variables.
> Recode to avoid needing the temp cpumask variables and remove the
> memory allocation.
>
> Signed-off-by: Mic
The x86 mmap() code selects the mmap base for an allocation depending on
the bitness of the syscall. For 64bit sycalls it select mm->mmap_base and
for 32bit mm->mmap_compat_base.
exec() calls mmap() which in turn uses in_compat_syscall() to check whether
the mapping is for a 32bit or a 64bit task.
This patch-set deals with an interesting yet stupid problem: kernel code
that does not get inlined despite its simplicity. There are several
causes for this behavior: "cold" attribute on __init, different function
optimization levels; conditional constant computations based on
__builtin_constant_p(
GCC considers the number of statements in inlined assembly blocks,
according to new-lines and semicolons, as an indication to the cost of
the block in time and space. This data is distorted by the kernel code,
which puts information in alternative sections. As a result, the
compiler may perform inc
Hi,
Please resend the patch with related other patches.
It is hard to check the dependency/sequence of your patches.
On 2018년 05월 18일 07:32, Matthias Kaehlcke wrote:
> Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding the
> devfreq device") initializes df->min/max_freq with the min
Hi,
On 2018년 05월 18일 08:07, Matthias Kaehlcke wrote:
> Hi,
>
> On Thu, May 17, 2018 at 11:01:34AM +0900, Chanwoo Choi wrote:
>> Hi,
>>
>> Could you give some use-case of DEVFREQ_POLICY_NOTIFIER
>> or send use-case patch with this patch?
>
> This is a WIP patch that makes use of the DEVFREQ_POLIC
GCC considers the number of statements in inlined assembly blocks,
according to new-lines and semicolons, as an indication to the cost of
the block in time and space. This data is distorted by the kernel code,
which puts information in alternative sections. As a result, the
compiler may perform inc
On Thu, 17 May 2018 at 16:16, Niklas Cassel
wrote:
> diff --git a/drivers/net/wireless/ath/ath10k/txrx.c
b/drivers/net/wireless/ath/ath10k/txrx.c
> index cda164f6e9f6..1d3b2d2c3fee 100644
> --- a/drivers/net/wireless/ath/ath10k/txrx.c
> +++ b/drivers/net/wireless/ath/ath10k/txrx.c
> @@ -95,6 +95,
GCC considers the number of statements in inlined assembly blocks,
according to new-lines and semicolons, as an indication to the cost of
the block in time and space. This data is distorted by the kernel code,
which puts information in alternative sections. As a result, the
compiler may perform inc
GCC considers the number of statements in inlined assembly blocks,
according to new-lines and semicolons, as an indication to the cost of
the block in time and space. This data is distorted by the kernel code,
which puts information in alternative sections. As a result, the
compiler may perform inc
GCC considers the number of statements in inlined assembly blocks,
according to new-lines and semicolons, as an indication to the cost of
the block in time and space. This data is distorted by the kernel code,
which puts information in alternative sections. As a result, the
compiler may perform inc
GCC considers the number of statements in inlined assembly blocks,
according to new-lines and semicolons, as an indication to the cost of
the block in time and space. This data is distorted by the kernel code,
which puts information in alternative sections. As a result, the
compiler may perform inc
The mm-of-the-moment snapshot 2018-05-17-16-26 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
> From: Jacob Pan [mailto:jacob.jun@linux.intel.com]
> Sent: Thursday, May 17, 2018 11:59 PM
> On Thu, 17 May 2018 11:41:56 +
> "Liu, Yi L" wrote:
>
> > > +int iommu_report_device_fault(struct device *dev, struct
> > > +iommu_fault_event *evt) {
> > > + int ret = 0;
> > > + struct iommu_f
Hi,
On 2018년 05월 18일 01:35, Matthias Kaehlcke wrote:
> On Thu, May 17, 2018 at 10:07:56AM +0900, Chanwoo Choi wrote:
>> Hi,
>>
>> On 2018년 05월 17일 07:57, Matthias Kaehlcke wrote:
>>> Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding
>>> the devfreq device") introduced the initializa
On 2018년 05월 18일 07:41, Matthias Kaehlcke wrote:
> On Wed, May 16, 2018 at 02:10:51PM -0700, Matthias Kaehlcke wrote:
>> The performance, powersave, simpleondemand and userspace governors
>> determine a target frequency and then adjust it according to the
>> df->min/max_freq limits that might have
The following problem was observed when running iperf:
[ 3] 0.0- 1.0 sec 2.00 MBytes 16.8 Mbits/sec
[ 3] 1.0- 2.0 sec 3.12 MBytes 26.2 Mbits/sec
[ 3] 2.0- 3.0 sec 3.25 MBytes 27.3 Mbits/sec
[ 3] 3.0- 4.0 sec 655 KBytes 5.36 Mbits/sec
[ 3] 4.0- 5.0 sec 0.00 Bytes 0.00 bits/sec
Hi,
On 2018년 05월 18일 00:47, Matthias Kaehlcke wrote:
> Hi,
>
> On Thu, May 17, 2018 at 10:44:08AM +0900, Chanwoo Choi wrote:
>> Hi,
>>
>> On 2018년 05월 17일 06:10, Matthias Kaehlcke wrote:
>>> The performance, powersave, simpleondemand and userspace governors
>>> determine a target frequency and th
Hi,
On Thu, May 17, 2018 at 11:01:34AM +0900, Chanwoo Choi wrote:
> Hi,
>
> Could you give some use-case of DEVFREQ_POLICY_NOTIFIER
> or send use-case patch with this patch?
This is a WIP patch that makes use of the DEVFREQ_POLICY_NOTIFIER:
https://chromium-review.googlesource.com/c/chromiumos/
On Wed, May 16, 2018 at 7:55 AM, Richard Guy Briggs wrote:
> The audit-related parameters in struct task_struct should ideally be
> collected together and accessed through a standard audit API.
>
> Collect the existing loginuid, sessionid and audit_context together in a
> new struct audit_task_inf
On Wed, May 16, 2018 at 7:55 AM, Richard Guy Briggs wrote:
> On the rebase of the following commit on the new seccomp actions_logged
> function, one audit_context access was missed.
>
> commit cdfb6b341f0f2409aba24b84f3b4b2bba50be5c5
> ("audit: use inline function to get audit context")
>
> Signed
On Wed, May 16, 2018 at 7:55 AM, Richard Guy Briggs wrote:
> Recognizing that the loginuid is an internal audit value, use an access
> function to retrieve the audit loginuid value for the task rather than
> reaching directly into the task struct to get it.
>
> Signed-off-by: Richard Guy Briggs
>
On Thu, 17 May 2018 22:58:11 +0200
Jiri Olsa wrote:
> On Thu, May 17, 2018 at 05:15:53PM -0300, Arnaldo Carvalho de Melo wrote:
> > So parse_state->error == NULL, Jiri, ideas?
>
> yep, we don't use it in tests.. and when trying intel_pt on
> system without that pmu, the parse_events_add_pmu fail
On May 17, 2018 2:30:01 PM PDT, Alexey Dobriyan wrote:
>32-bit instructions are 1 byte shorter than 16-bit instructions.
>
>Signed-off-by: Alexey Dobriyan
>---
>
> arch/x86/kernel/verify_cpu.S |8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
>--- a/arch/x86/kernel/verify_cpu.S
On Wed, May 16, 2018 at 02:10:51PM -0700, Matthias Kaehlcke wrote:
> The performance, powersave, simpleondemand and userspace governors
> determine a target frequency and then adjust it according to the
> df->min/max_freq limits that might have been set by user space. This
> adjustment is redundant
The new challenge is to remove VLAs from the kernel
(see https://lkml.org/lkml/2018/3/7/621) to eventually
turn on -Wvla.
Using a kmalloc array is the easy way to fix this but kmalloc is still
more expensive than stack allocation. Introduce a fast path with a
fixed size stack array to cover most c
On Wed, May 16, 2018 at 10:44 AM Rishabh Bhatnagar
wrote:
> LLCC (Last Level Cache Controller) provides additional cache memory
> in the system. LLCC is partitioned into multiple slices and each
> slice gets its own priority, size, ID and other config parameters.
> LLCC driver programs these para
101 - 200 of 1043 matches
Mail list logo
