During certain workloads, the default CM response timeout is too
short, leading to excessive retries. Hence, make it configurable
through sysctl. While at it, also make number of CM retries
configurable.
The defaults are not changed.
Signed-off-by: Håkon Bugge
---
v1 -> v2:
* Added
This adds the device-tree bindings for the OSD101T2587-53TS 10.1"
1920x1200 panel from One Stop Displays.
Note: the panel is similar to OSD101T2045-53TS, but it needs additional
MIPI_DSI_TURN_ON_PERIPHERAL message from the host.
Signed-off-by: Peter Ujfalusi
Reviewed-by: Rob Herring
---
On Fri, Sep 28, 2018 at 06:09:03AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:1042caa79e93 net-ipv4: remove 2 always zero parameters fro..
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=13fff71140
>
The panel is similar to OSD101T2045-53TS (which is handled by panel-simple)
with one big difference: osd101t2587-53ts needs MIPI_DSI_TURN_ON_PERIPHERAL
message to be sent from the host to be operational and thus can not be
handled by panel-simple.
Signed-off-by: Peter Ujfalusi
Reviewed-by: Sam
On Tue, Feb 26, 2019 at 09:46:12AM +0200, Mike Rapoport wrote:
[...]
> > > > > > +int mwriteprotect_range(struct mm_struct *dst_mm, unsigned long
> > > > > > start,
> > > > > > + unsigned long len, bool enable_wp, bool
> > > > > > *mmap_changing)
> > > > > > +{
> > > > > > +
This adds the device-tree bindings for the OSD101T2045-53TS 10.1"
1920x1200 panel from One Stop Displays.
Signed-off-by: Peter Ujfalusi
Reviewed-by: Rob Herring
---
.../bindings/display/panel/osd,osd101t2045-53ts.txt | 11 +++
1 file changed, 11 insertions(+)
create mode 100644
Hi,
Changes since v2:
- Added Reviewed-by from Rob to the binding patches
- Added help text to Kconfig (osd101t2587-53ts)
- Print the error values in dev_err/warn
- Added Reviewed-by from Sam to the osd101t2587-53ts patch
Changes since v1 (only panel-osd-osd101t2587-53ts changed):
- Removed
On Tue, Feb 26, 2019 at 08:58:36AM +0200, Mike Rapoport wrote:
> On Tue, Feb 12, 2019 at 10:56:32AM +0800, Peter Xu wrote:
> > This patch adds uffd tests for write protection.
> >
> > Instead of introducing new tests for it, let's simply squashing uffd-wp
> > tests into existing uffd-missing test
On 2/8/19 4:10 AM, Gustavo A. R. Silva wrote:
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
> struct foo {
> int stuff;
Dear Friend,
I know that this letter will come to you as surprise, I got your contact
address while I search for foreign partner to assist me in this business
transaction that is present in our favor now, My name is Mr. KARIM ZAKARI, I
am the Bill and Exchange (assistant) Manager (BOA)
On Tue, Feb 26, 2019 at 03:20:28PM +0800, Peter Xu wrote:
> On Tue, Feb 26, 2019 at 08:43:47AM +0200, Mike Rapoport wrote:
> > On Tue, Feb 26, 2019 at 02:06:27PM +0800, Peter Xu wrote:
> > > On Mon, Feb 25, 2019 at 10:52:34PM +0200, Mike Rapoport wrote:
> > > > On Tue, Feb 12, 2019 at 10:56:26AM
Hi Mike,
On Thu, Feb 21, 2019 at 11:11:06AM -0800, Mike Kravetz wrote:
> On 2/20/19 10:09 PM, Andrew Morton wrote:
> > On Tue, 12 Feb 2019 14:14:00 -0800 Mike Kravetz
> > wrote:
> >> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> >> index a80832487981..f859e319e3eb 100644
> >> --- a/mm/hugetlb.c
>
On Tue, Feb 26, 2019 at 09:04:25AM +0200, Mike Rapoport wrote:
> On Tue, Feb 26, 2019 at 02:53:42PM +0800, Peter Xu wrote:
> > On Mon, Feb 25, 2019 at 11:19:32PM +0200, Mike Rapoport wrote:
> > > On Tue, Feb 12, 2019 at 10:56:30AM +0800, Peter Xu wrote:
> > > > From: Martin Cracauer
> > > >
> >
On Tue, Feb 26, 2019 at 09:29:33AM +0200, Mike Rapoport wrote:
> On Tue, Feb 26, 2019 at 02:24:52PM +0800, Peter Xu wrote:
> > On Mon, Feb 25, 2019 at 11:09:35PM +0200, Mike Rapoport wrote:
> > > On Tue, Feb 12, 2019 at 10:56:29AM +0800, Peter Xu wrote:
> > > > It does not make sense to try to
Le 25/02/2019 à 19:57, Dave Hansen a écrit :
From: Dave Hansen
walk_system_ram_range() can return an error code either becuase
*it* failed, or because the 'func' that it calls returned an
error. The memory hotplug does the following:
ret = walk_system_ram_range(..., func);
On Tue, Jun 19, 2018 at 10:34:01PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:ba4dbdedd3ed Merge tag 'jfs-4.18' of git://github.com/klei..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=112e9ce440
>
Hi Andrew,
After merging the akpm tree, today's linux-next build (powerpc
allnoconfig) failed like this:
/home/sfr/next/next/arch/powerpc/kernel/setup_32.c:176:21: error: redefinition
of 'alloc_stack'
static void *__init alloc_stack(void)
^~~
On Sun, 24 Feb 2019, Andreas Klinger wrote:
comments below
> Add MaxSonar-I2CXL ultrasonic distance sensors of type family mb12x2
> using the i2c interface
>
> Implemented functionality:
> - reading the distance via in_distance_raw
> - buffered mode with trigger
> - make use of status gpio to
On Wed, Feb 20, 2019 at 05:03:38PM +0100, 'Dmitry Vyukov' via syzkaller-bugs
wrote:
> On Mon, Oct 8, 2018 at 12:06 PM Ard Biesheuvel
> wrote:
> >
> > (add the TLS maintainers)
> >
> > On 6 October 2018 at 15:04, syzbot
> > wrote:
> > > Hello,
> > >
> > > syzbot found the following crash on:
> >
Leverage __ATTR_RO_MODE to define rev sysfs instead of using open code
to define the attribute.
Signed-off-by: Wei Yang
---
drivers/firmware/qemu_fw_cfg.c | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
diff --git a/drivers/firmware/qemu_fw_cfg.c
Hi,
I'm using kernel v4.19.24 and have found that there is an issue when
using perf probe to define a new dynamic tracepoint.
$ perf probe -a handle_mm_fault
Failed to write event: Numerical result out of range
Error: Failed to add events.
I've also tried kernel v4.20, and it can pass.
So
On Thu, Jul 12, 2018 at 06:44:55AM -0400, Boris Pismenny wrote:
> It seems to me that the crash here is due to write_space being called after
> the close system call. Maybe the correct solution is to move the TX software
> state to be released in sk_destruct. As we already do for the device state
On Tue, Feb 26, 2019 at 02:24:52PM +0800, Peter Xu wrote:
> On Mon, Feb 25, 2019 at 11:09:35PM +0200, Mike Rapoport wrote:
> > On Tue, Feb 12, 2019 at 10:56:29AM +0800, Peter Xu wrote:
> > > It does not make sense to try to wake up any waiting thread when we're
> > > write-protecting a memory
Enable SUN6I SPI controller for Allwinner ARM64 SoC's.
This would helpful to setup spi flash, for another booting source.
mark it as static since it require during boot.
Signed-off-by: Jagan Teki
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
On Fri, Jun 08, 2018 at 06:11:02AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:7170e6045a6a strparser: Add __strp_unpause and use it in k..
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=114236af80
>
On Tue, Feb 26, 2019 at 06:39:28AM +, ajay.kat...@microchip.com wrote:
On 2/26/2019 8:58 AM, Bo YU wrote:
The patch fixes following sparse warning:
drivers/staging/wilc1000/host_interface.c:450:30: warning: incorrect type in
assignment (different base types)
Fix sparse warning:
drivers/staging/wilc1000/host_interface.c:450:30: warning: incorrect type in
assignment (different base types)
drivers/staging/wilc1000/host_interface.c:450:30:expected restricted __le16
[usertype] beacon_period
drivers/staging/wilc1000/host_interface.c:450:30:got
On Sun, 24 Feb 2019, Andreas Klinger wrote:
> Makefile and Kconfig: add configuration for mb12x2 ultrasonic proximity
> driver
>
> diff --git a/drivers/iio/proximity/Makefile b/drivers/iio/proximity/Makefile
> index 6d031f903c4c..c56b72a8be87 100644
> --- a/drivers/iio/proximity/Makefile
> +++
On Tue, Feb 26, 2019 at 08:43:47AM +0200, Mike Rapoport wrote:
> On Tue, Feb 26, 2019 at 02:06:27PM +0800, Peter Xu wrote:
> > On Mon, Feb 25, 2019 at 10:52:34PM +0200, Mike Rapoport wrote:
> > > On Tue, Feb 12, 2019 at 10:56:26AM +0800, Peter Xu wrote:
> > > > From: Shaohua Li
> > > >
> > > >
On Tue, 26 Feb 2019 at 05:03, wrote:
>
> Clang warns: vector initializers are not compatible with NEON intrinsics
> in big endian mode [-Wnonportable-vector-initialization]
>
> While this is usually the case, it's not an issue for this case since
> we're initializing the uint8x16_t (16x
This uses simple-audio-card machine driver adding 1 CPU DAI
and 1 Codec DAI.
Signed-off-by: Daniel Baluta
---
arch/arm64/boot/dts/freescale/imx8mq-evk.dts | 29
1 file changed, 29 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mq-evk.dts
This sets the pin configuration for SAI pins BLCK/MCLK/FSYNC/DATA.
GPIO_01 is used for mute.
Signed-off-by: Daniel Baluta
---
arch/arm64/boot/dts/freescale/imx8mq-evk.dts | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mq-evk.dts
SAI2 is part of AIPS-3 memory region and it's the DAI through
which the wm8524 codec gets its data.
Signed-off-by: Daniel Baluta
---
arch/arm64/boot/dts/freescale/imx8mq.dtsi | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mq.dtsi
This enables SAI2 digital audio interface to be used with
wm8524 codec.
wm8524 works only in slave mode, so we make sure that IMX8MQ_CLK_SAI2
has an appropriate frequency in order to easily derive rates divisible
with 8000.
Signed-off-by: Daniel Baluta
---
SDMA1 is part of AIPS-3 region and SDMA2 is part
of AIPS-1 region.
Signed-off-by: Anson Huang
[initial submit in i.MX internal tree]
Signed-off-by: Daniel Baluta
[adaptation for linux-next]
---
arch/arm64/boot/dts/freescale/imx8mq.dtsi | 22 ++
1 file changed, 22
On i.MX8MQ we can start the party using the wm8524 codec
which gets it's data through the SAI2 interface.
In order to make it work this patch series enables the SDMA nodes,
sets the correct pinctrl configuration and uses the simple card
machine driver to put everything together.
Changes since
On Mon, Feb 25, 2019 at 5:35 PM Ley Foon Tan wrote:
>
> On Tue, 2019-02-19 at 16:23 +, Lorenzo Pieralisi wrote:
> > On Thu, Feb 14, 2019 at 11:20:36PM +0800, Ley Foon Tan wrote:
> > >
> > > Add PCIe Root Port support for Stratix 10 device.
> > >
> > > Main differences:
> > Main differences
SDM845 sports two PCIe controller/phy pairs; one GEN2 and one GEN3. Add
the nodes for the GEN2 pair.
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 103 +++
1 file changed, 103 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
On Tue, Feb 26, 2019 at 02:53:42PM +0800, Peter Xu wrote:
> On Mon, Feb 25, 2019 at 11:19:32PM +0200, Mike Rapoport wrote:
> > On Tue, Feb 12, 2019 at 10:56:30AM +0800, Peter Xu wrote:
> > > From: Martin Cracauer
> > >
> > > Adds documentation about the write protection support.
> > >
> > >
The PCIe PIPE clock in the GCC is fed by the PIPE clock coming from the
PHY, describe this relationship.
Signed-off-by: Bjorn Andersson
---
drivers/clk/qcom/gcc-sdm845.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/clk/qcom/gcc-sdm845.c b/drivers/clk/qcom/gcc-sdm845.c
index
Implement libzstd feature check, NO_LIBZSTD and LIBZSTD_DIR defines
to override Zstd library sources or disable the feature from the
command line:
$ make -C tools/perf LIBZSTD_DIR=/path/to/zstd/sources/ clean all
$ make -C tools/perf NO_LIBZSTD=1 clean all
Auto detection feature status is
The SDM845 has one Gen2 and one Gen3 controller, add support for these.
Due to lack of hardware only the Gen2 controller has been verified.
Signed-off-by: Bjorn Andersson
---
.../devicetree/bindings/pci/qcom,pcie.txt | 19 +++
drivers/pci/controller/dwc/pcie-qcom.c| 146
When DWC3 is set to host mode by programming register DWC3_GCTL, VBUS
(or its control signal) will be turned on immediately on related Root Hub
ports. Then, the VBUS is turned off for a little while(15us) when do xhci
reset (conducted by xhci driver) and back to normal finally, we can
observe a
When DWC3 is set to host mode by programming register DWC3_GCTL, VBUS
(or its control signal) will turn on immediately on related Root Hub
ports. Then the VBUS will be de-asserted for a little while during xhci
reset (conducted by xhci driver) for a little while and back to normal.
This VBUS
On Tue, Feb 12, 2019 at 10:56:32AM +0800, Peter Xu wrote:
> This patch adds uffd tests for write protection.
>
> Instead of introducing new tests for it, let's simply squashing uffd-wp
> tests into existing uffd-missing test cases. Changes are:
>
> (1) Bouncing tests
>
> We do the
qcom_qmp_phy_init() is extended to support the additional register
writes needed in PCS MISC and the appropriate sequences and resources
are defined for SDM845.
Signed-off-by: Bjorn Andersson
---
.../devicetree/bindings/phy/qcom-qmp-phy.txt | 7 +
drivers/phy/qualcomm/phy-qcom-qmp.c
On 一, 2019-02-25 at 23:41 -0500, Len Brown wrote:
> On Thu, Feb 21, 2019 at 12:44 AM Len Brown wrote:
> >
> >
> > On Wed, Feb 20, 2019 at 6:02 AM Peter Zijlstra > g> wrote:
> >
> > >
> > > >
> > > > list_for_each_entry(rp, _packages, plist) {
> > > > @@ -1457,7 +1457,7 @@ static void
On Mon, Feb 25, 2019 at 11:19:32PM +0200, Mike Rapoport wrote:
> On Tue, Feb 12, 2019 at 10:56:30AM +0800, Peter Xu wrote:
> > From: Martin Cracauer
> >
> > Adds documentation about the write protection support.
> >
> > Signed-off-by: Andrea Arcangeli
> > [peterx: rewrite in rst format; fixups
On Tue, Feb 12, 2019 at 10:56:31AM +0800, Peter Xu wrote:
> Introduce uffd_stats structure for statistics of the self test, at the
> same time refactor the code to always pass in the uffd_stats for either
> read() or poll() typed fault handling threads instead of using two
> different ways to
Hello,
syzbot found the following crash on:
HEAD commit:8a61716ff2ab Merge tag 'ceph-for-5.0-rc8' of git://github...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=161b71d4c0
kernel config: https://syzkaller.appspot.com/x/.config?x=7132344728e7ec3f
Hi, Daniel and Andrea,
"Huang, Ying" writes:
> From: Huang Ying
>
> When swapin is performed, after getting the swap entry information from
> the page table, system will swap in the swap entry, without any lock held
> to prevent the swap device from being swapoff. This may cause the race
>
Hi Ming Lei,
On 26/02/19 7:11 AM, Ming Lei wrote:
> On Mon, Feb 25, 2019 at 9:14 PM Faiz Abbas wrote:
>>
>> Hi Naresh,
>>
>> + Commit authors.
>>
>> On 19/02/19 6:38 PM, Faiz Abbas wrote:
>>> Hi Naresh,
>>>
>>> On 18/02/19 6:57 PM, Naresh Kamboju wrote:
Do you see this error on am57xx-evm
On Tue, Feb 26, 2019 at 02:06:27PM +0800, Peter Xu wrote:
> On Mon, Feb 25, 2019 at 10:52:34PM +0200, Mike Rapoport wrote:
> > On Tue, Feb 12, 2019 at 10:56:26AM +0800, Peter Xu wrote:
> > > From: Shaohua Li
> > >
> > > Add API to enable/disable writeprotect a vma range. Unlike mprotect,
> > >
On 2/26/2019 8:58 AM, Bo YU wrote:
> The patch fixes following sparse warning:
>
> drivers/staging/wilc1000/host_interface.c:450:30: warning: incorrect type in
> assignment (different base types)
> drivers/staging/wilc1000/host_interface.c:450:30:expected restricted
> __le16 [usertype]
blkoops is a sample for pstore/blk. It can only record oops, excluding
panics as no read/write apis for panic registered. It support settings
on Kconfg/module parameters. It can record oops log even power failure
if "PSTORE_BLKOOPS_BLKDEV" on Kconfig or "blkdev" on module parameter
is valid.
CET - Control-flow Enforcement Technology, it's used to
protect against return/jump oriented programming (ROP)
attacks. It provides the following capabilities to defend
against ROP/JOP style control-flow subversion attacks:
- Shadow Stack (SHSTK):
A second stack for the program
Why should we need pstore_block?
1. Most embedded intelligent equipment have no persistent ram, which
increases costs. We perfer to cheaper solutions, like block devices.
In fast, there is already a sample for block device logger in driver
MTD (drivers/mtd/mtdoops.c).
2. Do not any equipment have
The CET runtime settings, i.e., CET state control bits(IA32_U_CET/
IA32_S_CET), CET SSP(IA32_PL3_SSP/IA32_PL0_SSP) and SSP table address
(IA32_INTERRUPT_SSP_TABLE_ADDR) are task/thread specific, therefore,
OS needs to save/restore the states properly during context switch,
e.g., task/thread
The document, at Documentation/admin-guide/pstore-block.rst,
tells user how to use pstore_blk and the attentions about panic
read/write
Signed-off-by: liaoweixiong
---
Documentation/admin-guide/pstore-block.rst | 233 +
MAINTAINERS|
To enable pmsg, just set pmsg_size when block device register blkzone.
Signed-off-by: liaoweixiong
---
fs/pstore/Kconfig | 21
fs/pstore/blkoops.c| 10 ++
fs/pstore/blkzone.c| 253 +
include/linux/pstore_blk.h | 1 +
pstore_blk is similar to pstore_ram, but dump log to block devices
rather than persistent ram.
Why should we need pstore_blk?
1. Most embedded intelligent equipment have no persistent ram, which
increases costs. We perfer to cheaper solutions, like block devices.
In fact, there is already a
Control-flow Enforcement Technology (CET) provides protection against
return/jump-oriented programming (ROP) attacks. To make kvm Guest OS own
the capability, this patch-set is required. It enables CET related CPUID
report, xsaves/xrstors, vmx entry configuration etc. for Guest OS.
PATCH 1:
Guest CET SHSTK and IBT capability are reported via
CPUID.(EAX=7, ECX=0):ECX[bit 7] and EDX[bit 20] respectively.
Guest user mode and supervisor mode xsaves component size
is reported via CPUID.(EAX=0xD, ECX=1):ECX[bit 11] and ECX[bit 12]
respectively.
Signed-off-by: Zhang Yi Z
Signed-off-by:
Guest queries CET SHSTK and IBT support by CPUID.(EAX=0x7,ECX=0),
in return, ECX[bit 7] corresponds to SHSTK feature, and EDX[bit 20]
corresponds to IBT feature.
CR4.CET[bit 23] is CET master enable bit, it controls CET feature
availability in guest OS.
Note: Although SHSTK or IBT can be enabled
According to latest Software Development Manual vol.2/3.2,
for CPUID.(EAX=0xD,ECX=1), it should report xsaves area size
containing all states enabled by XCR0|IA32_MSR_XSS.
Signed-off-by: Zhang Yi Z
Signed-off-by: Yang Weijiang
---
arch/x86/kvm/cpuid.c | 3 ++-
1 file changed, 2 insertions(+),
The Guest MSRs are stored in fpu storage area, they are
operated by XSAVES/XRSTORS, so use kvm_load_guest_fpu
to restore them is a convenient way to let KVM access
them. After finish operation, need to restore Host MSR
contents by kvm_put_guest_fpu.
Signed-off-by: Yang Weijiang
---
"Load Guest CET state" bit controls whether guest CET states
will be loaded at Guest entry. Before doing that, KVM needs
to check if CPU CET feature is available.
Signed-off-by: Zhang Yi Z
Signed-off-by: Yang Weijiang
---
arch/x86/kvm/vmx.c | 32
1 file
For Guest XSS, right now, only bit 11(user states) and bit 12
(supervisor states) are supported, if other bits are being set,
need to modify KVM_SUPPORTED_XSS macro to have support.
Signed-off-by: Zhang Yi Z
Signed-off-by: Yang Weijiang
---
arch/x86/kvm/vmx.c | 8 +---
1 file changed, 5
On Mon, Feb 25, 2019 at 11:03:51PM +0200, Mike Rapoport wrote:
> On Tue, Feb 12, 2019 at 10:56:27AM +0800, Peter Xu wrote:
> > From: Andrea Arcangeli
> >
> > v1: From: Shaohua Li
> >
> > v2: cleanups, remove a branch.
> >
> > [peterx writes up the commit message, as below...]
> >
> > This
Initialized decompression API so COMPRESSED records would be
decompressed into the resulting output data file.
Signed-off-by: Alexey Budankov
---
tools/perf/builtin-inject.c | 4
1 file changed, 4 insertions(+)
diff --git a/tools/perf/builtin-inject.c b/tools/perf/builtin-inject.c
index
Trace frames containing PERF_RECORD_COMPRESSED records are
decompressed using functions from zstd.c into a linked list
of mmaped memory regions of mmap_comp_len size (struct decomp).
After decompression of one COMPRESSED record its content is
iterated and fetched for usual processing. The
On Mon, Feb 25, 2019 at 11:09:35PM +0200, Mike Rapoport wrote:
> On Tue, Feb 12, 2019 at 10:56:29AM +0800, Peter Xu wrote:
> > It does not make sense to try to wake up any waiting thread when we're
> > write-protecting a memory region. Only wake up when resolving a write
> > protected page fault.
On Sun, Feb 24, 2019 at 04:53:03PM +, Michael Kelley wrote:
> From: Kimberly Brown Sent: Thursday, February 21, 2019
> 7:47 PM
> >
> > The "_show" functions that access channel ring buffer data are
> > vulnerable to a race condition that can result in a NULL pointer
> > dereference. This
From: Zhang Rui
The RAPL domain "name" attribute contains "Package-N",
which is ambiguous on multi-die per-package systems.
Update the name to "package-X-die-Y" on those systems.
No change on systems without multi-die.
Driver debug messages are also updated.
Signed-off-by: Zhang Rui
Implemented -z,--compression_level=n option that enables compression
of mmaped kernel data buffers content in runtime during perf record
sampling collection.
Compression is implemented using the functions from zstd.c. As the
memory to operate on the compression employs mmap->data buffer in
This patch series does 4 things.
1. Parses the new CPUID.1F leaf to discover multi-die/package topology
2. Export multi-die topology inside the kernel
3. Update 3 places (coretemp, pkgtemp, rapl) that that need to know
the difference between die and package-scope MSR.
(Note: Kan Liang
From: Len Brown
Syntax only, no functional or semantic change.
Signed-off-by: Len Brown
Cc: linux-...@vger.kernel.org
---
Documentation/cputopology.txt | 46 +--
1 file changed, 23 insertions(+), 23 deletions(-)
diff --git a/Documentation/cputopology.txt
From: Len Brown
Syntax only, no functional or semantic change.
reflect actual cpuinfo_x86 field name:
s/logical_id/logical_proc_id/
Signed-off-by: Len Brown
Cc: linux-...@vger.kernel.org
---
Documentation/x86/topology.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Tue, 26 Feb 2019, Jing Xiangfeng wrote:
> On 2019/2/26 3:17, David Rientjes wrote:
> > On Mon, 25 Feb 2019, Mike Kravetz wrote:
> >
> >> Ok, what about just moving the calculation/check inside the lock as in the
> >> untested patch below?
> >>
> >> Signed-off-by: Mike Kravetz
> >> ---
> >>
From: Zhang Rui
On the new dual-die/package systems, the RAPL MSR becomes die-scope.
Thus instead of one powercap device per physical package, now there
should be one powercap device for each unique die on these systems.
This patch introduces intel_rapl driver support for new
dual-die/package
From: Zhang Rui
This patch introduces coretemp driver support
for new dual-die/package systems.
On the new dual-die/package systems, the package temperature MSRs becomes
die-scope. Thus instead of one hwmon device per physical package, now
there should be one hwmon device for each die on these
From: Len Brown
Define topology_logical_die_id() ala
existing topology_logical_package_id()
Signed-off-by: Len Brown
---
arch/x86/include/asm/processor.h | 1 +
arch/x86/include/asm/topology.h | 3 +++
arch/x86/kernel/smpboot.c| 43
3 files changed,
From: Len Brown
The sysfs cpu/topology/core_siblings (and core_siblings_list)
attributes are documented, implemented, and used by programs to
represent set of logical CPU threads sharing the same package.
This makes sense if the next topology level above a core
is always a package. But on
From: Zhang Rui
On the new dual-die/package systems, the package temperature MSR becomes
die-scope. Thus instead of one thermal zone device per physical package,
now there should be one thermal_zone for each die on these systems.
This patch introduces x86_pkg_temp_thermal support for new
From: Len Brown
Some new systems have multiple software-visible die within each package.
Update Linux parsing of the Intel CPUID "Extended Topology Leaf"
to handle either CPUID.B, or the new CPUID.1F.
Add cpuinfo_x86.die_id and cpuinfo_x86.max_dies to store the result.
die_id will be non-zero
From: Len Brown
Create CPU topology sysfs attributes:
"core_threads" and "core_threads_list"
These attributes represent all of the logical CPU threads that share the
same core.
These attriutes is synonymous with the existing "thread_siblings" and
"thread_siblings_list" attribute, which will be
From: Len Brown
Export die_id in cpu topology, for the benefit of hardware that
has multiple-die/package.
Signed-off-by: Len Brown
Cc: linux-...@vger.kernel.org
---
Documentation/cputopology.txt | 6 ++
arch/x86/include/asm/topology.h | 1 +
drivers/base/topology.c | 4
From: Len Brown
The die_threads show all the logical CPUs that share the same die_id.
Signed-off-by: Len Brown
Suggested-by: Brice Goglin
---
Documentation/cputopology.txt | 12
arch/x86/include/asm/smp.h | 1 +
arch/x86/include/asm/topology.h | 1 +
From: Len Brown
Syntax only, no functional or semantic change.
This routine matches packages, not die, so name it thus.
Signed-off-by: Len Brown
---
arch/x86/kernel/smpboot.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/smpboot.c
From: Zhang Rui
Syntax only, no functional or semantic change.
Simplify how the code to discover a package is called.
Rename find_package_by_id() to rapl_find_package()
Signed-off-by: Zhang Rui
Signed-off-by: Len Brown
Acked-by: Rafael J. Wysocki
Cc: linux...@vger.kernel.org
---
Schönen Tag,
Mein Name ist Mavis Wanczyk, Gewinner des Powerball-Jackpots im August 2017 in
Höhe von 758,7 Millionen US-Dollar. Ich und meine Familie haben beschlossen,
jeweils fünf Millionen US-Dollar an einige glückliche Personen auf der ganzen
Welt auszugeben. Kontaktieren Sie mich über
On 25.02.19 15:43, Rob Herring wrote:
> On Tue, Jan 29, 2019 at 11:23:46AM +0100, Martin Kepplinger wrote:
>> From: Martin Kepplinger
>>
>> The st1232 driver reads this via gpiod.
>
> What a driver does is not relevant to the binding. This breaks
> compatibility so you need to mention that and
Hi Dmitry,
On Tue, Feb 19, 2019 at 3:46 PM Jagan Teki wrote:
>
> This is v6 patchset for supporting goodix GT5553 CTP. Here is the
> previous version[1]
>
> Changes for v5:
> - document bindings for required regulators, which are need during
> power-on sequence
> - enable, disable required
Hi Rob,
On Tue, Feb 12, 2019 at 5:22 PM Jagan Teki wrote:
>
> Add vendor prefix for feiyang, known as
> Shenzhen Fly Young Technology Co.,LTD. a known producer for LCD modules.
>
> Signed-off-by: Jagan Teki
> ---
> Note: notation about using 'feiyang' is based on the datasheet
>
Implemented functions are based on Zstd streaming compression
API. The functions are used in runtime to compress data that
come from mmaped kernel buffer data and then stored into a trace.
Signed-off-by: Alexey Budankov
---
tools/perf/util/Build | 2 +
tools/perf/util/compress.h | 18
Hi Peter,
> -Original Message-
> From: Peter Rosin [mailto:p...@axentia.se]
> Sent: Monday, 25 February, 2019 08:14 PM
> To: Pankaj Bansal ; Leo Li
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v3 2/2] drivers: mux: Add Generic regmap bitfield-based
> multiplexer in mmio-mux
>
On Mon, Feb 25, 2019 at 10:52:34PM +0200, Mike Rapoport wrote:
> On Tue, Feb 12, 2019 at 10:56:26AM +0800, Peter Xu wrote:
> > From: Shaohua Li
> >
> > Add API to enable/disable writeprotect a vma range. Unlike mprotect,
> > this doesn't split/merge vmas.
> >
> > Cc: Andrea Arcangeli
> > Cc:
Rob,
On Thu, Feb 21, 2019 at 7:32 PM Guenter Roeck wrote:
>
> On 2/20/19 9:22 AM, Jagan Teki wrote:
> > On Tue, Feb 12, 2019 at 5:08 PM Jagan Teki
> > wrote:
> >>
> >> Add missing dt-binding documentation for lm75 hwmon sensor.
> >>
> >> Signed-off-by: Jagan Teki
> >> ---
> >> Changes for v2:
Implemented mmap data buffer that is used as the memory to operate
on when compressing sampling data in case of serial trace streaming.
In case of AIO trace streaming AIO buffers are used to implement
sampling data compression.
Signed-off-by: Alexey Budankov
---
tools/perf/builtin-record.c |
Oceanic A64-5inMFD is a 5 inch Multi function display baseboard
designed to mount SoPine SOM.
Key features:
- Allwinner A64 Cortex-A53
- Mali-400MP2 GPU
- AXP803 PMIC
- 2GB DDR3 RAM
- SD Slot
- SPI-NOR flash
- EMAC, RTL8211E
- MCP2515 CAN
- MIPI-DSI
- Goodix 911 CTP
- USB Host
- 12V DC power
1 - 100 of 1288 matches
Mail list logo
