Hi Brice,
Yes, you re-discovered the bug that Kan Liang pointed out last week.
I have updated this patch set, and the latest for testing is in my git tree on
kernel.org or
https://github.com/lenb/linux.git x86
Note that I took your advice and left the core_siblings with its original
definitio
On 2019-02-22 23:36, Rob Herring wrote:
> +boot-architecture list
>
> On Tue, Feb 19, 2019 at 07:52:47PM +0800, liaoweixiong wrote:
>> Create DT binding document for blkoops.
>>
>> Signed-off-by: liaoweixiong
>> ---
>> .../devicetree/bindings/pstore/blkoops.txt | 53
>> +++
Hi Paul,
sorry for the delay but this driver requires a bit more of attention.
Overall I disagree the driver because of its complexity. We should not
see that for this driver.
Did you check if using node alias to specify the clocksource and the
clockevent can fit your need.
https://git.kernel.o
Hi Szabolcs,
Thanks for looking into this. Comments below.
On Tue, Feb 19, 2019 at 06:38:31PM +, Szabolcs Nagy wrote:
> i think these rules work for the cases i care about, a more
> tricky question is when/how to check for the new syscall abi
> and when/how the TCR_EL1.TBI0 setting may be tur
On 25/02/2019 16:57, Catalin Marinas wrote:
> On Tue, Feb 19, 2019 at 06:38:31PM +, Szabolcs Nagy wrote:
>> i think these rules work for the cases i care about, a more
>> tricky question is when/how to check for the new syscall abi
>> and when/how the TCR_EL1.TBI0 setting may be turned off.
>
Quoting Paul Cercueil (2019-02-22 19:17:25)
> Hi,
>
> Anything new on this? It still happens on 5.0-rc7.
> It probes with late_initcall, and not with device_initcall.
> I have no clue what's going on.
>
I'm not sure what's going on either. You'll probably have to debug when
the device is created
On Sun, 24 Feb 2019 23:45:23 +0800
Zenghui Yu wrote:
> As linux-5.0 is coming up soon, the howto.rst document can be
> updated for the new kernel version. Change all 4.x references
> to 5.x now.
>
> Signed-off-by: Zenghui Yu
Overall: I think there's value in having the docs reflect current
num
Improve IIO documentation by fixing a few mistakes.
Signed-off-by: Tomasz Duszynski
---
Documentation/driver-api/iio/buffers.rst | 2 +-
Documentation/driver-api/iio/core.rst| 6 +++---
Documentation/driver-api/iio/hw-consumer.rst | 2 +-
Documentation/driver-api/iio/triggers.rst
Hi,
Le lun. 25 févr. 2019 à 12:55, Daniel Lezcano
a écrit :
Hi Paul,
sorry for the delay but this driver requires a bit more of attention.
Overall I disagree the driver because of its complexity. We should not
see that for this driver.
What's complex in this driver?
Did you check if usin
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-doc@vger.kernel.org
---
Documentation/x86/topology.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Do
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-doc@vger.kernel.org
---
Documentation/cputopology.txt | 6 ++
arch/x86/include/asm/topology.h | 1 +
drivers/base/topology.c | 4
incl
From: Len Brown
Syntax only, no functional or semantic change.
Signed-off-by: Len Brown
Cc: linux-doc@vger.kernel.org
---
Documentation/cputopology.txt | 46 +--
1 file changed, 23 insertions(+), 23 deletions(-)
diff --git a/Documentation/cputopology.txt b/Docu
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
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 sample
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| 1
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. Otherw
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 b
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 +
4
18 matches
Mail list logo
