This array property is used to indicate the maximum burst transaction
length supported by each DMA channel.
Signed-off-by: Serge Semin
Cc: Alexey Malahov
Cc: Thomas Bogendoerfer
Cc: Paul Burton
Cc: Ralf Baechle
Cc: Arnd Bergmann
Cc: Viresh Kumar
Cc: Andy Shevchenko
Cc: Dan Williams
Cc:
Fix the @data and @fd allocations that are leaked in the error path of
apply_xbc().
Fixes: 85c46b78da58 ("bootconfig: Add bootconfig magic word for indicating
bootconfig explicitly")
Fixes: 950313ebf79c ("tools: bootconfig: Add bootconfig command")
Acked-by: Masami Hiramatsu
Signed-off-by:
Full multi-block transfers functionality is enabled in DW DMA
controller only if CHx_MULTI_BLK_EN is set. But LLP-based transfers
can be executed only if hardcode channel x LLP register feature isn't
enabled, which can be switched on at the IP core synthesis for
optimization. If it's enabled then
Extend -D,--delay option with -1 to start collection
with events disabled to be enbled later by enable
command provided via control file descriptor.
Signed-off-by: Alexey Budankov
---
tools/perf/Documentation/perf-record.txt | 5 +++--
tools/perf/builtin-record.c | 12
Baikal-T1 SoC has an DW DMAC on-board to provide a Mem-to-Mem, low-speed
peripherals Dev-to-Mem and Mem-to-Dev functionality. Mostly it's compatible
with currently implemented in the kernel DW DMAC driver, but there are some
peculiarities which must be taken into account in order to have the
Introduce --ctl-fd[-ack] options to pass open file descriptors numbers
from command line. Extend perf-stat.txt file with --ctl-fd[-ack] options
description. Document possible usage model introduced by --ctl-fd[-ack]
options by providing example bash shell script.
Signed-off-by: Alexey Budankov
Implement handling of 'enable' and 'disable' control commands
coming from control file descriptor.
Signed-off-by: Alexey Budankov
---
tools/perf/builtin-stat.c | 48 +--
1 file changed, 36 insertions(+), 12 deletions(-)
diff --git
Introduce support for Papr nvDimm Specific Methods (PDSM) in papr_scm
modules and add the command family to the white list of NVDIMM command
sets. Also advertise support for ND_CMD_CALL for the dimm
command mask and implement necessary scaffolding in the module to
handle ND_CMD_CALL ioctl and PDSM
'seq_buf' provides a very useful abstraction for writing to a string
buffer without needing to worry about it over-flowing. However even
though the API has been stable for couple of years now its stills not
exported to external modules limiting its usage.
Hence this patch proposes update to
Implement support for fetching nvdimm health information via
H_SCM_HEALTH hcall as documented in Ref[1]. The hcall returns a pair
of 64-bit big-endian integers, bitwise-and of which is then stored in
'struct papr_scm_priv' and subsequently partially exposed to
user-space via newly introduced dimm
This patch implements support for PDSM request 'PAPR_SCM_PDSM_HEALTH'
that returns a newly introduced 'struct nd_papr_pdsm_health' instance
containing dimm health information back to user space in response to
ND_CMD_CALL. This functionality is implemented in newly introduced
papr_scm_get_health()
Add documentation to 'papr_hcalls.rst' describing the bitmap flags
that are returned from H_SCM_HEALTH hcall as per the PAPR-SCM
specification.
Cc: Dan Williams
Cc: Michael Ellerman
Cc: "Aneesh Kumar K . V"
Signed-off-by: Vaibhav Jain
---
Changelog:
v6..v7:
* None
v5..v6
* New patch in the
The PAPR standard[1][3] provides mechanisms to query the health and
performance stats of an NVDIMM via various hcalls as described in
Ref[2]. Until now these stats were never available nor exposed to the
user-space tools like 'ndctl'. This is partly due to PAPR platform not
having support for
Extend -D,--delay option with -1 value to start monitoring with
events disabled to be enabled later by enable command provided
via control file descriptor.
Signed-off-by: Alexey Budankov
---
tools/perf/Documentation/perf-stat.txt | 5 +++--
tools/perf/builtin-stat.c | 18
Factor out event handling loop into handle_events() function.
Signed-off-by: Alexey Budankov
---
tools/perf/builtin-stat.c | 85 +++
1 file changed, 50 insertions(+), 35 deletions(-)
diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
index
On Wed, 6 May 2020 17:24:40 -0400
Jared Rossi wrote:
> Remove the explicit prefetch check when using vfio-ccw devices.
> This check does not trigger in practice as all Linux channel programs
> are intended to use prefetch.
>
> It is expected that all ORBs issued by Linux will request prefetch.
Implement functions of initialization, finalization and processing
of control commands coming from control file descriptors.
Signed-off-by: Alexey Budankov
---
tools/perf/util/evlist.c | 128 +++
tools/perf/util/evlist.h | 17 ++
2 files changed, 145
Define and initialize control file descriptors.
Signed-off-by: Alexey Budankov
---
tools/perf/util/evlist.c | 3 +++
tools/perf/util/evlist.h | 3 +++
2 files changed, 6 insertions(+)
diff --git a/tools/perf/util/evlist.c b/tools/perf/util/evlist.c
index 0a0b760d6948..2db4bedc4f81 100644
---
On Thu, 07 May 2020 17:06:19 +0100,
Neeraj Upadhyay wrote:
>
> Hi,
>
> I have one query regarding pseudo NMI support on GIC v3; from what I
> could understand, GIC v3 supports pseudo NMI setup for SPIs and PPIs.
> However the request_nmi() in irq framework requires NMI to be per cpu
> interrupt
Changes in v3:
- renamed functions and types from perf_evlist_ to evlist_ to avoid
clash with libperf code;
- supported commands to be strings of variable length consisting of
command name and also possibly including command specific data;
- merged docs update with the code changes;
-
On Fri, 8 May 2020, Jeremy Kerr wrote:
> Hi Julia,
>
> > Other uses of >aff_list_head, eg in spufs_assert_affinity, indicate
> > that the list elements have type spu_context, not spu as used here. Change
> > the type of tmp accordingly.
>
> Looks good to me; we could even use ctx there,
On Tue, May 05, 2020 at 10:40:43PM -0700, Randy Dunlap wrote:
> On 5/5/20 3:29 PM, a...@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2020-05-05-15-28 has been uploaded to
> >
> >http://www.ozlabs.org/~akpm/mmotm/
> >
> > mmotm-readme.txt says
> >
> > README for
On Fri, May 08, 2020 at 10:11:28AM +0200, Peter Zijlstra wrote:
> On Thu, May 07, 2020 at 07:09:58PM +0100, Quentin Perret wrote:
> > One challenge to implement GKI is to avoid bloating the kernel by
> > compiling too many things in, especially given that different devices
> > need different
On Thu, 7 May 2020 at 21:11, Paul Kocialkowski
wrote:
>
> Hi Emil,
>
> Thanks for the review!
>
> On Mon 04 May 20, 14:28, Emil Velikov wrote:
> > Just had a casual quick look for custom KMS properties, since new
> > drivers made that mistake in the past.
> > Thanks for not including any o/
>
>
On Fri, May 8, 2020 at 4:49 AM Shakeel Butt wrote:
>
> One way to measure the efficiency of memory reclaim is to look at the
> ratio (pgscan+pfrefill)/pgsteal. However at the moment these stats are
> not updated consistently at the system level and the ratio of these are
> not very meaningful.
On 05/05/2020 15:41, Ezequiel Garcia wrote:
> From: Boris Brezillon
>
> The Rockchip VDEC supports VP9 profile 0 up to 4096x2304@30fps. Add
> a backend for this new format.
>
> Signed-off-by: Boris Brezillon
> Signed-off-by: Ezequiel Garcia
> ---
> drivers/staging/media/rkvdec/Makefile |
Hi Gustavo,
"Gustavo A. R. Silva" wrote on Thu, 7 May 2020
14:00:33 -0500:
> The current codebase makes use of the zero-length array language
> extension to the C90 standard, but the preferred mechanism to declare
> variable-length types such as these ones is a flexible array member[1][2],
>
On 2020/5/8 17:30, Dan Carpenter wrote:
> On Fri, May 08, 2020 at 02:51:15PM +0800, Yunfeng Ye wrote:
>> diff --git a/tools/bootconfig/main.c b/tools/bootconfig/main.c
>> index 16b9a420e6fd..d034f86022b7 100644
>> --- a/tools/bootconfig/main.c
>> +++ b/tools/bootconfig/main.c
>> @@ -314,31
On Fri, May 8, 2020 at 11:33 AM Dmitry Vyukov wrote:
>
> On Thu, May 7, 2020 at 5:56 PM 'Andrey Konovalov' via syzkaller-bugs
> wrote:
> >
> > On Wed, May 6, 2020 at 1:50 PM Andrey Konovalov
> > wrote:
> > >
> > > On Wed, May 6, 2020 at 10:54 AM Oliver Neukum wrote:
> > > >
> > > > Am
When more than one coresight components uses the obsolete DT bindings,
warning is displayed for only one component and not for the others.
Lets warn it for all components by replacing dev_warn_once with dev_warn.
Signed-off-by: Kathiravan T
---
drivers/hwtracing/coresight/coresight-platform.c |
On Thu, 7 May 2020 14:22:28 -0500, Gustavo A. R. Silva wrote:
> The current codebase makes use of the zero-length array language
> extension to the C90 standard, but the preferred mechanism to declare
> variable-length types such as these ones is a flexible array member[1][2],
> introduced in C99:
On Thu, 7 May 2020 15:27:35 +0800, YueHaibing wrote:
> When CONFIG_SND_SOC_SOF_BAYTRAIL is not set, gcc warns:
>
> sound/soc/sof/intel/byt.c:85:41: warning: âcht_debugfsâ defined but not
> used [-Wunused-const-variable=]
> static const struct snd_sof_debugfs_map cht_debugfs[] = {
>
On 05/05/2020 15:41, Ezequiel Garcia wrote:
> From: Boris Brezillon
>
> Add the VP9 stateless decoder controls plus the documentation that goes
> with it.
>
> Signed-off-by: Boris Brezillon
> Signed-off-by: Ezequiel Garcia
> ---
> .../userspace-api/media/v4l/biblio.rst| 10 +
>
On Fri, May 8, 2020 at 1:15 PM Serge Semin
wrote:
>
> On Fri, May 08, 2020 at 01:03:11PM +0300, Andy Shevchenko wrote:
> > On Fri, May 8, 2020 at 12:37 PM Serge Semin
> > wrote:
> > >
> > > This SPI-controller is a part of the Baikal-T1 System Controller and
> > > is based on the DW APB SSI
On Sun, Apr 26, 2020 at 09:16:30PM +0200, Christophe JAILLET wrote:
> 'host1x_debug_init()' must be reverted in an error handling path.
>
> This is already fixed in the remove function since commit 44156eee91ba
> ("gpu: host1x: Clean up debugfs on removal")
>
> Signed-off-by: Christophe JAILLET
Hi Chao,
On Fri, May 08, 2020 at 05:47:09PM +0800, Chao Yu wrote:
> For lz4 worst compress case, caller should allocate buffer with size
> of LZ4_compressBound(inputsize) for target compressed data storing.
>
> However lz4 supports partial data compression, so we can get rid of
> output buffer
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
tools/testing/selftests/vm/Makefile
between commit:
b0d449922eb8 ("mm/hmm/test: add selftests for HMM")
from the hmm tree and commit:
3a07caa68f66 ("selftests: vm: pkeys: fix multilib builds for x86")
from
On Fri, May 08, 2020 at 01:15:41PM +0300, Serge Semin wrote:
> On Fri, May 08, 2020 at 01:03:11PM +0300, Andy Shevchenko wrote:
> > > slave device. Taking into account the peculiarities of the controller
> > > registers and physically mapped SPI flash access, very limited resources
> > > and
> From: Mimi Zohar [mailto:zo...@linux.ibm.com]
> On Thu, 2020-05-07 at 16:47 +, Roberto Sassu wrote:
> > > > > On Wed, 2020-05-06 at 15:44 -0400, Mimi Zohar wrote:
> > > > > > Since copying the EVM HMAC or original signature isn't applicable, I
> > > > > > would prefer exploring an EVM
weeks ago
config: powerpc-randconfig-r035-20200508 (attached as .config)
compiler: powerpc-linux-gcc (GCC) 9.3.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout
On 07/05/2020 20:05, John Mathew wrote:
[...]
> diff --git a/Documentation/scheduler/cfs-overview.rst
> b/Documentation/scheduler/cfs-overview.rst
> new file mode 100644
> index ..b717f2d3e340
> --- /dev/null
> +++ b/Documentation/scheduler/cfs-overview.rst
> @@ -0,0 +1,113 @@
> +..
> Btw, these leaks are totally harmless. This is a short running user
> space program with is going to immediately exit on error so the memory
> will be freed anyway.
Can such a view mean that the function call “free(data)” should be omitted here
for a quicker program termination?
> But the
On Tue, May 5, 2020 at 4:02 PM Andy Shevchenko
wrote:
>
> On Mon, May 4, 2020 at 4:44 PM Mateusz Holenko wrote:
> > On Tue, Apr 28, 2020 at 5:50 PM Andy Shevchenko
> > wrote:
> > > On Sat, Apr 25, 2020 at 2:45 PM Mateusz Holenko
> > > wrote:
>
> ...
>
> > > > Signed-off-by: Filip Kokosinski
On Fri, May 08, 2020 at 02:14:38AM +, Luis Chamberlain wrote:
> Device driver firmware can crash, and sometimes, this can leave your
> system in a state which makes the device or subsystem completely
> useless. Detecting this by inspecting /proc/sys/kernel/tainted instead
> of scraping some
On Thu, 2020-05-07 at 18:04 -0700, Bart Van Assche wrote:
> > + GEOMETRY_DESC_PARAM_HPB_REGION_SIZE = 0x48,
> > + GEOMETRY_DESC_PARAM_HPB_NUMBER_LU = 0x49,
> > + GEOMETRY_DESC_PARAM_HPB_SUBREGION_SIZE = 0x4A,
> > + GEOMETRY_DESC_PARAM_HPB_MAX_ACTIVE_REGIONS = 0x4B,
> >
On Fri, May 08, 2020 at 01:03:11PM +0300, Andy Shevchenko wrote:
> On Fri, May 8, 2020 at 12:37 PM Serge Semin
> wrote:
> >
> > This SPI-controller is a part of the Baikal-T1 System Controller and
> > is based on the DW APB SSI IP-core, but with very limited resources:
> > no IRQ, no DMA, only a
Le jeudi 07 mai 2020 à 17:06 +0100, Bryan O'Donoghue a écrit :
> On 07/05/2020 16:57, Bryan O'Donoghue wrote:
> > On 23/04/2020 11:34, Bryan O'Donoghue wrote:
> > > V3:
> > > This update removes the old clock name arrays which I forgot to prune in
> > > the previous V2.
> > >
> > > git diff
On Tue, Apr 28, 2020 at 1:51 PM Miklos Szeredi wrote:
>
> On Mon, Apr 27, 2020 at 3:46 PM Chakra Divi wrote:
> >
> > On Tue, Apr 21, 2020 at 4:21 PM Chakra Divi wrote:
> > >
> > > On Mon, Apr 20, 2020 at 4:55 PM Miklos Szeredi wrote:
> > > >
> > > > On Wed, Apr 1, 2020 at 11:31 AM Chakra Divi
Hi Julia,
> Other uses of >aff_list_head, eg in spufs_assert_affinity, indicate
> that the list elements have type spu_context, not spu as used here. Change
> the type of tmp accordingly.
Looks good to me; we could even use ctx there, rather than the separate
tmp variable.
Reviewed-by: Jeremy
On Thu, May 07, 2020 at 11:24:49PM +0200, Thomas Gleixner wrote:
> But over our IRC conversation I came up with a 3rd variant:
>
> For most of the vectors the indirect call overhead is just noise, so
> we can run them through the ASM switcher, but for the resched IPI
> we can just use a
On Fri, May 8, 2020 at 11:59 AM Grygorii Strashko
wrote:
>
> From: Clay McClure
>
> My recent commit b6d49cab44b5 ("net: Make PTP-specific drivers depend on
> PTP_1588_CLOCK") exposes a missing dependency in defconfigs that select
> TI_CPTS without selecting PTP_1588_CLOCK, leading to linker
Baikal-T1 Boot Controller provides an access to a RO storages, which are
physically mapped into the MMIO space. In particularly there are the
Internal ROM embedded into the SoC with a pre-installed firmware,
externally attached SPI flash (also accessed in the read-only mode) and a
memory region,
On Thu, 2020-05-07 at 18:34 -0700, Randy Dunlap wrote:
> Hi,
>
> On 5/4/20 7:20 AM, huob...@gmail.com wrote:
> > diff --git a/drivers/scsi/ufs/Kconfig b/drivers/scsi/ufs/Kconfig
> > index e2005aeddc2d..0224f224a641 100644
> > --- a/drivers/scsi/ufs/Kconfig
> > +++ b/drivers/scsi/ufs/Kconfig
> >
On Friday 08 May 2020 at 10:07:59 (+0200), Peter Zijlstra wrote:
> On Thu, May 07, 2020 at 07:10:06PM +0100, Quentin Perret wrote:
> > It will be needed by schedutil once modularized, export it.
> >
> > Signed-off-by: Quentin Perret
> > ---
> > This is only needed for cpu_rq() -> cpu_bw_dl() in
On Fri, May 8, 2020 at 12:37 PM Serge Semin
wrote:
>
> This SPI-controller is a part of the Baikal-T1 System Controller and
> is based on the DW APB SSI IP-core, but with very limited resources:
> no IRQ, no DMA, only a single native chip-select and just 8 bytes Tx/Rx
> FIFO available. In order
Add DT binding for Texas Instruments K3 Multicore SoC platforms chipid
module which is represented by CTRLMMR_xxx_JTAGID register and contains
information about SoC id and revision.
Signed-off-by: Grygorii Strashko
Reviewed-by: Lokesh Vutla
Reviewed-by: Tero Kristo
---
The Texas Instruments K3 Multicore SoC platforms have chipid module which
is represented by CTRLMMR_xxx_JTAGID register and contains information
about SoC id and revision.
Bits:
31-28 VARIANT Device variant
27-12 PARTNO Part number
11-1 MFG Indicates TI as manufacturer (0x17)
1
On 5/8/20 9:07 AM, Vasily Averin wrote:
> On 5/8/20 6:36 AM, Matthew Wilcox wrote:
>> On Thu, May 07, 2020 at 05:02:42PM -0700, Andrew Morton wrote:
>>> Here's how I resolved things. Please check?
>>>
>>> static struct kern_ipc_perm *sysvipc_find_ipc(struct ipc_ids *ids, loff_t
>>> pos,
>>>
Hi!
> > But I might be confused. I recall some audio patches were needed for
> > basic phone calls (setting up mixers to connect gsm<->audio), but
> > those worked before gsmux support was enabled. (Maybe some hardcoded
> > commands were needed to be sent to gsmmux somewhere).
>
> We're
Hi All,
This series introduces TI K3 Multicore SoC platforms chipid module driver
which provides identification support of the TI K3 SoCs (family, revision)
and register this information with the SoC bus. It is available under
/sys/devices/soc0/ for user space, and can be checked, where needed,
From: Clay McClure
My recent commit b6d49cab44b5 ("net: Make PTP-specific drivers depend on
PTP_1588_CLOCK") exposes a missing dependency in defconfigs that select
TI_CPTS without selecting PTP_1588_CLOCK, leading to linker errors of the
form:
drivers/net/ethernet/ti/cpsw.o: in function
On Fri, May 8, 2020 at 5:18 AM David E. Box wrote:
>
> Intel Platform Monitoring Technology (PMT) is an architecture for
> enumerating and accessing hardware monitoring capabilities on a device.
> With customers increasingly asking for hardware telemetry, engineers not
> only have to figure out
On Fri, May 8, 2020 at 5:18 AM David E. Box wrote:
>
> PMT Telemetry is a capability of the Intel Platform Monitoring Technology.
> The Telemetry capability provides access to device telemetry metrics that
> provide hardware performance data to users from continuous, memory mapped,
> read-only
On Fri, May 08, 2020 at 11:27:39AM +0200, Arnd Bergmann wrote:
> Right, makes sense. It would be nice though to have a way of intentionally
> turning all objtool warnings into errors. I do my randconfig tests
> with '-Werror'
> at the moment in order to catch all new warnings, but this does not
Other uses of >aff_list_head, eg in spufs_assert_affinity, indicate
that the list elements have type spu_context, not spu as used here. Change
the type of tmp accordingly.
This has no impact on the execution, because tmp is not used in the body of
the loop.
Fixes: c5fc8d2a92461 ("[CELL] cell:
On 08/05/20 10:42, Xu, Like wrote:
>> Given the bugs, it is clear that you should also modify the pmu.c
>> testcase for kvm-unit-tests to cover full-width writes (and especially
>> the non-full-width write behavior of MSR_IA32_PERFCTRn). Even before
>> the QEMU side is begin worked on, you can
I would just do small changes to the validity checks for MSRs.
On 08/05/20 10:32, Like Xu wrote:
> return 0;
> + case MSR_IA32_PERF_CAPABILITIES:
> + *data = vcpu->arch.perf_capabilities;
> + return 0;
This should be:
if
In f2fs_try_to_free_nids(), .nid_list_lock spinlock critical region will
increase as expected shrink number increase, to avoid spining other CPUs
for long time, we change to release nid caches with small batch each time
under .nid_list_lock coverage.
Signed-off-by: Chao Yu
---
v2:
- shrink free
Hi Robert,
On Thu, May 7, 2020 16:39 Robert Foss wrote:
> On Thu, 7 May 2020 at 10:06, Kao, Ben wrote:
> >
> > Hi Robert,
> >
> > On 20-05-05 12:01, Robert Foss wrote:
> > > Add match table, enable ov8856_probe() to support both ACPI and DT modes.
> > >
> > > ACPI and DT modes are primarily
Hi Li,
On Thu, May 7, 2020 at 11:58 PM Li Yang wrote:
> On Thu, May 7, 2020 at 6:31 AM Geert Uytterhoeven
> wrote:
> > Several QorIQ blocks are only present on Freescale or NXP SoCs.
> > This series adds platform dependencies to the corresponding config
> > ymbols, to avoid asking the user
For lz4 worst compress case, caller should allocate buffer with size
of LZ4_compressBound(inputsize) for target compressed data storing.
However lz4 supports partial data compression, so we can get rid of
output buffer size limitation now, then we can avoid 2 * 4KB size
intermediate buffer
Hi Marco Felsch,
> 20-05-08 04:22, Marco Felsch wrote:
> Hi Ben,
>
> On 20-05-07 08:06, Kao, Ben wrote:
> > Hi Robert,
> >
> > On 20-05-05 12:01, Robert Foss wrote:
> > > Add match table, enable ov8856_probe() to support both ACPI and DT modes.
> > >
> > > ACPI and DT modes are primarily
On Thu, May 07, 2020 at 06:29:41PM -0500, Josh Poimboeuf wrote:
> On Wed, May 06, 2020 at 04:07:25PM +0200, Arnd Bergmann wrote:
> > Hi,
> >
> > During randconfig testing with clang-10 I came across a number
> > of additional objtool warnings, I'll send another mail about those
> > when I have
[Answering for Emanuele because he's not available until Monday]
On 07/05/20 19:45, Jonathan Adams wrote:
> This is good work. As David Rientjes mentioned, I'm currently investigating
> a similar project, based on a google-internal debugfs-based FS we call
> "metricfs". It's
> designed in a
Ok, I will pay attation. thank you.
On 05/08/2020 04:25 PM, Peter Zijlstra wrote:
Checkpatch can sod off. Please don't ever submit pure checkpatch patches
to anything I maintain
This SPI-controller is a part of the Baikal-T1 System Controller and
is based on the DW APB SSI IP-core, but with very limited resources:
no IRQ, no DMA, only a single native chip-select and just 8 bytes Tx/Rx
FIFO available. In order to provide a transparent initial boot code
execution this
Baikal-T1 SoC System Controller is equipped with a Boot Controller. It's
responsible for the system starting up from different sources. In
particular it's possible to boot the chip either from an internal firmware
or from an externally attached 16MB SPI flash or from the SoC SRAM
pre-initialized
Baikal-T1 Boot SPI is a part of the SoC System Controller and is
responsible for the system bootup from an external SPI flash. It's a DW
APB SSI-based SPI-controller with no interrupts, no DMA, with just one
native chip-select available and a single reference clock. Since Baikal-T1
SoC is normally
An experimental patch series of mine reworks how warnings are processed
in Kbuild. A side effect is a new warning about a harmless aliasing
rule violation in an inline function:
In file included from
include/linux/rhashtable-types.h:15:0,
from include/linux/ipc.h:7,
>
> On Tue, Apr 07, 2020 at 02:42:48PM +0800, Biwen Li wrote:
> > From: Biwen Li
> >
> > The patch adds ftm_alarm0 DT node for Soc LX2160A
> > FlexTimer1 module is used to wakeup the system in deep sleep
> >
> > Signed-off-by: Biwen Li
> > ---
> > arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
On Thu, May 07, 2020 at 10:13:37PM +0300, Serge Semin wrote:
> On Thu, May 07, 2020 at 01:09:51PM +0200, Thomas Bogendoerfer wrote:
> > On Wed, May 06, 2020 at 08:42:29PM +0300, sergey.se...@baikalelectronics.ru
> > wrote:
> > > From: Serge Semin
> > >
> > > Indeed according to the P5600/P6000
On Thu, May 7, 2020 at 5:56 PM 'Andrey Konovalov' via syzkaller-bugs
wrote:
>
> On Wed, May 6, 2020 at 1:50 PM Andrey Konovalov wrote:
> >
> > On Wed, May 6, 2020 at 10:54 AM Oliver Neukum wrote:
> > >
> > > Am Freitag, den 20.03.2020, 12:28 -0700 schrieb syzbot:
> > > > Hello,
> > > >
> > > >
On Fri, May 08, 2020 at 12:19:23AM +0300, Serge Semin wrote:
> On Thu, May 07, 2020 at 01:17:35PM +0200, Thomas Bogendoerfer wrote:
> > P5600 is CPU_MIPS_R5 so can't you select it here and drop all the ||
> > CPU_5600
> > above/below ?
>
> Alas, We can't do this so easy.
On Fri, May 08, 2020 at 02:51:15PM +0800, Yunfeng Ye wrote:
> diff --git a/tools/bootconfig/main.c b/tools/bootconfig/main.c
> index 16b9a420e6fd..d034f86022b7 100644
> --- a/tools/bootconfig/main.c
> +++ b/tools/bootconfig/main.c
> @@ -314,31 +314,33 @@ int apply_xbc(const char *path, const char
Le 08/05/2020 à 10:49, Dan Carpenter a écrit :
On Wed, May 06, 2020 at 10:09:07PM +0200, Christophe JAILLET wrote:
@@ -237,7 +239,7 @@ static int tegra186_emc_probe(struct platform_device *pdev)
"failed to set rate range [%lu-%lu] for %pC\n",
Hello,
syzbot found the following crash on:
HEAD commit:3c40cdb0 Merge branch 'linus' of git://git.kernel.org/pub/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14733d6c10
kernel config: https://syzkaller.appspot.com/x/.config?x=b0212dbee046bc1f
On Fri, May 8, 2020 at 1:29 AM Josh Poimboeuf wrote:
>
> On Wed, May 06, 2020 at 04:07:25PM +0200, Arnd Bergmann wrote:
> > Hi,
> >
> > During randconfig testing with clang-10 I came across a number
> > of additional objtool warnings, I'll send another mail about those
> > when I have collected
On Fri, 8 May 2020, Peter Zijlstra wrote:
> On Thu, May 07, 2020 at 07:06:25PM +0800, Jason Yan wrote:
> > Fix the following coccicheck warning:
> >
> > kernel/sched/fair.c:9375:9-10: WARNING: return of 0/1 in function
> > 'voluntary_active_balance' with return type bool
>
> That's not a
Hi Al,
this series fixes a few issues and cleans up the helpers that read from
or write to kernel space buffers, and ensures that we don't change the
address limit if we are using the ->read_iter and ->write_iter methods
that don't need the changed address limit.
Current minimum required version of binutils is 2.23,
which supports INVPCID instruction mnemonic.
Replace the byte-wise specification of INVPCID with
this proper mnemonic.
Signed-off-by: Uros Bizjak
CC: "H. Peter Anvin"
CC: Ingo Molnar
CC: Thomas Gleixner
---
arch/x86/include/asm/invpcid.h
Fold it into the two callers.
Signed-off-by: Christoph Hellwig
---
fs/read_write.c| 43 +--
include/linux/fs.h | 1 -
2 files changed, 21 insertions(+), 23 deletions(-)
diff --git a/fs/read_write.c b/fs/read_write.c
index
Consolidate the two in-kernel write helpers to make upcoming changes
easier. The only difference are the missing call to rw_verify_area
in kernel_write, and an access_ok check that doesn't make sense for
kernel buffers to start with.
Signed-off-by: Christoph Hellwig
---
fs/read_write.c | 13
We still need to check if the fѕ is open write, even for the low-level
helper.
Signed-off-by: Christoph Hellwig
---
fs/read_write.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/read_write.c b/fs/read_write.c
index d5aaf3a4198b9..d5c754080e5a5 100644
--- a/fs/read_write.c
+++
We always need to take a reference on the file system we are writing
to.
Signed-off-by: Christoph Hellwig
---
fs/read_write.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/read_write.c b/fs/read_write.c
index bbfa9b12b15eb..d5aaf3a4198b9 100644
--- a/fs/read_write.c
+++
Just open coding the methods calls is a lot easier to follow.
Signed-off-by: Christoph Hellwig
---
drivers/block/loop.c | 4 ++--
drivers/target/target_core_file.c | 4 ++--
fs/aio.c | 4 ++--
fs/io_uring.c | 4 ++--
fs/read_write.c
If we write to a file that implements ->write_iter there is no need
to change the address limit if we send a kvec down. Implement that
case, and prefer it over using plain ->write with a changed address
limit if available.
Signed-off-by: Christoph Hellwig
---
fs/read_write.c | 34
Consolidate the two in-kernel read helpers to make upcoming changes
easier. The only difference are the missing call to rw_verify_area
in kernel_read, and an access_ok check that doesn't make sense for
kernel buffers to start with.
Signed-off-by: Christoph Hellwig
---
fs/read_write.c | 13
If we read to a file that implements ->read_iter there is no need
to change the address limit if we send a kvec down. Implement that
case, and prefer it over using plain ->read with a changed address
limit if available.
Signed-off-by: Christoph Hellwig
---
fs/read_write.c | 24
Fold it into the two callers.
Signed-off-by: Christoph Hellwig
---
fs/read_write.c | 46 ++
1 file changed, 22 insertions(+), 24 deletions(-)
diff --git a/fs/read_write.c b/fs/read_write.c
index 6b456a257b31c..67a035782874b 100644
---
__kernel_read has a bunch of additional sanity checks, and this moves
the set_fs out of non-core code.
Signed-off-by: Christoph Hellwig
---
security/integrity/iint.c | 14 +-
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git a/security/integrity/iint.c
1601 - 1700 of 1926 matches
Mail list logo
