erent package?
thanks, Jan
--
--- /dev/null 2012-12-04 10:52:46.657720288 +0100
+++ s390_runtime_instr.22012-10-09 13:55:39.0 +0200
@@ -0,0 +1,73 @@
+.\" Copyright IBM Corp. 2012
+.\" Author: Jan Glauber
+.\"
+.TH S390_RUNTIME_INSTR 2 2012-10-09 "Linux Progr
The flogr instruction scans a bitmap starting from the leftmost bit.
Implement support for these bitops. This could be useful to scan
bitmaps like an interrupt vector set by the hardware starting
at the leftmost bit.
Signed-off-by: Jan Glauber
---
arch/s390/include/asm/bitops.h | 81
Signed-off-by: Jan Glauber
---
drivers/gpu/vga/Kconfig | 2 +-
include/video/vga.h | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/vga/Kconfig b/drivers/gpu/vga/Kconfig
index f348388..29437ea 100644
--- a/drivers/gpu/vga/Kconfig
+++ b/drivers/gpu/vga/Kconfig
Signed-off-by: Jan Glauber
---
arch/s390/Kconfig | 56 +--
1 file changed, 50 insertions(+), 6 deletions(-)
diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
index 5dba755..e3dd4aec 100644
--- a/arch/s390/Kconfig
+++ b/arch/s390/Kconfig
CLP instructions are used to query the firmware about detected PCI
functions, the attributes of those functions and to enable or disable
a PCI function. The CLP interface is the equivalent to a PCI bus scan.
Signed-off-by: Jan Glauber
---
arch/s390/include/asm/clp.h | 28
arch/s390
Add some s390 specific sysfs attributes to the PCI device directory.
The following attributes are introduced:
- function_id (PCI function ID)
- function_handle (PCI function handle)
- pchid (PCI channel ID)
- pfgid (PCI function group ID aka PCI root complex)
Signed-off-by: Jan Glauber
---
arch
/slots//power the PCI function
is moved to stand-by or configured state. If moved to the configured
state the device is automatically scanned by the s390 PCI layer.
Signed-off-by: Jan Glauber
---
arch/s390/include/asm/pci.h| 11 ++
arch/s390/include/asm/sclp.h | 2 +
arch/s390/pci
Add CHSC store-event-information support for PCI (notfication type 2)
and report error and availability events to the PCI architecture layer.
Signed-off-by: Jan Glauber
---
arch/s390/include/asm/pci.h | 4 ++
arch/s390/pci/Makefile | 3 +-
arch/s390/pci/pci_event.c | 93
function.
A hash table is used to map interrupt numbers to MSI descriptors.
The interrupt vector is scanned using the flogr instruction.
Only MSI/MSI-X interrupts are supported, no legacy INTs.
Signed-off-by: Jan Glauber
---
arch/s390/include/asm/hw_irq.h | 22 ++
arch/s390/include/asm/irq.h| 12
Add DMA IOMMU support using 4K page table entries. Implement dma_map_ops.
Signed-off-by: Jan Glauber
---
arch/s390/include/asm/dma-mapping.h | 76 ++
arch/s390/include/asm/dma.h | 19 +-
arch/s390/include/asm/pci.h | 21 ++
arch/s390/include/asm/pci_dma.h | 196
O_IOPORT, so maybe NO_USB, NO_SOUND, ...
c) Introduce a special CONFIG_PCI_S390 and add that explicitely to all
subsystems that we want to enable on s390
None of the above looks like the obvious winner to me.
Hope to get some feedback,
TIA, Jan
Jan Glauber (10):
s390/pci: base support
s390/
special pcilg/pcistg
- device, bus and domain allocation
Signed-off-by: Jan Glauber
---
arch/s390/Kbuild | 1 +
arch/s390/include/asm/io.h | 55 +++-
arch/s390/include/asm/pci.h | 82 +-
arch/s390/include/asm/pci_insn.h | 280
arch/s390/include
On Thu, Jun 27, 2013 at 10:00:51PM +0530, Siddhesh Poyarekar wrote:
> On 27 June 2013 21:32, Jan Glauber wrote:
> > But isn't that confusing to the user? At least it is to me. Imagine someone
> > who uses the maps or smaps output to determine the size of code, data and
&g
Commit b764375 added annotations of thread stacks. This annotation can be
wrong depending on the memory layout of a task (will probably only happen
under 32 bit).
If a large allocation happens before the creation of a thread you can get:
root@box:~# cat /proc/2032/maps
08048000-08049000 r-xp 000
On Wed, Jun 26, 2013 at 10:05:41PM +0530, Siddhesh Poyarekar wrote:
> On 26 June 2013 17:13, Jan Glauber wrote:
> > Any ideas how that can be fixed? The only solution that comes to my mind
> > is to prevent merging vma's that are used for thread stacks. There is
> > alr
On Mon, 2012-12-10 at 14:14 -0700, Bjorn Helgaas wrote:
> On Wed, Nov 14, 2012 at 2:41 AM, Jan Glauber wrote:
> > Add PCI support for s390, (only 64 bit mode is supported by hardware):
> > - PCI facility tests
> > - PCI instructions: pcilg, pcistg, pcistb, stpcifc, mpcifc, rp
the example later when the official documentation is released which
did not yet happen.
thanks, Jan
--- /dev/null 2012-12-17 11:58:11.967183723 +0100
+++ s390_runtime_instr.22012-12-17 12:55:20.942872393 +0100
@@ -0,0 +1,91 @@
+.\" Copyright IBM Corp. 2012
+.\" Author: Jan Gl
On Sat, 2007-11-10 at 18:27 +1100, Rusty Russell wrote:
> We fail rather than sleep in the "dependency isn't ready" case. Partially
> because it's not happened before, but partially because we risk nasty loops.
If we fail since we have to in the "dependency isn't ready" case then
the warning see
in that case and causes the warning.
---
Signed-off-by: Jan Glauber <[EMAIL PROTECTED]>
Index: linux-2.6/kernel/module.c
===
--- linux-2.6.orig/kernel/module.c 2007-11-12 13:53:44.0 +
+++ linux-2.6/kernel/mo
On Tue, 2007-11-13 at 13:52 +1100, Rusty Russell wrote:
> On Tuesday 13 November 2007 09:23:12 Rusty Russell wrote:
> > Better might be to put in a waitqueue and wake it up whenever a module is
> > deleted or changes status. Then use_module() can wait if
> > strong_try_module_get() returns -EBUSY
On Thu, 2007-07-19 at 21:38 +0200, Ingo Molnar wrote:
> * Jan Glauber <[EMAIL PROTECTED]> wrote:
>
> > > still, CFS needs time measurement across idle periods as well, for
> > > another purpose: to be able to do precise task statistics for /proc.
> > >
On Fri, 2007-07-20 at 09:22 +0200, Ingo Molnar wrote:
> * Paul Mackerras <[EMAIL PROTECTED]> wrote:
> > As with s390, 64-bit PowerPC also uses CONFIG_VIRT_CPU_ACCOUNTING.
> > That affects how tsk->utime and tsk->stime are accumulated (we call
> > account_user_time and account_system_time directly
Hi Ingo,
an outcome from the previous discussion about a virtual sched_clock() on s390
was that scheduler_tick() should also be called based on virtual time.
The second patch changes the scheduler_tick() call to only happen after a tick
passed for the virtual cpu.
The patches cause nothing obviou
From: Jan Glauber <[EMAIL PROTECTED]>
From: Christian Borntraeger <[EMAIL PROTECTED]>
This patch introduces a cpu time clock for s390 (only ticking if
the virtual cpu is running) and bases the s390 implementation of
sched_clock() on it.
The time slice length on a virtual cpu can
Make the scheduler_tick() dependent on the s390 cpu timer so it gets only
called after
a virtual cpu has completed a tick. Together with the virtual sched_clock()
this
should make the scheduler decisions for s390 based on virtual time.
Signed-off-by: Jan Glauber <[EMAIL PROTECTED]>
Sign
Hi Rusty,
I've seen a symbol-resolving race on s390. The qeth module uses symbols
from qdio and although the loading order seems correct and the qdio
symbols should be available the following error appears:
qdio: loading QDIO base support version 2
qeth: Unknown symbol qdio_synchronize
qeth: Unkn
On Thu, 2007-11-08 at 13:10 +1100, Rusty Russell wrote:
> On Wednesday 07 November 2007 21:01:30 Jan Glauber wrote:
> > Hi Rusty,
> >
> > I've seen a symbol-resolving race on s390. The qeth module uses symbols
> > from qdio and although the loading order seems
On Tue, 2006-12-05 at 14:07 +0100, Jan Glauber wrote:
> Yes, if an attacker knows the initial clock value a brute-force attack
> would be feasible to predict the output. But I don't know if the
> hardware completely relies on the clock values or if there is any
> internal s
On Fri, 2007-02-09 at 09:42 +0100, Heiko Carstens wrote:
> I just want to avoid that s390 has different semantics for
> smp_call_functiom*() than any other architecture. But then again it
> will probably not hurt since we allow more.
> Another thing that comes into my mind is smp_call_function toge
On Mon, 2006-12-04 at 11:15 -0500, [EMAIL PROTECTED] wrote:
> On Fri, 01 Dec 2006 14:19:15 +0100, Jan Glauber said:
> > New s390 machines have hardware support for the generation of pseudo-random
> > numbers. This patch implements a simple char driver that exports this
> >
On Thu, 2006-12-07 at 16:06 +0100, Arnd Bergmann wrote:
> On Friday 01 December 2006 14:19, Jan Glauber wrote:
> > I've chosen the char driver since it allows the user to decide which
> > pseudo-random
> > numbers he wants to use. That means there is a new interface for
On Thu, 2006-12-07 at 19:43 +0100, Arnd Bergmann wrote:
> On Thursday 07 December 2006 16:19, Jan Glauber wrote:
> > Hm, why is /dev/urandom implemented in the kernel?
> >
> > It could be done completely in user-space (like libica already does)
> > but I think having
2006-12-01 13:06:50.0
+0100
@@ -0,0 +1,206 @@
+/*
+ * Copyright 2006 IBM Corporation
+ * Author(s): Jan Glauber <[EMAIL PROTECTED]>
+ * Driver for the s390 pseudo random number generator
+ */
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+
.c
linux-2.5_prng/arch/s390/crypto/prng.c
--- linux-2.5/arch/s390/crypto/prng.c 1970-01-01 01:00:00.0 +0100
+++ linux-2.5_prng/arch/s390/crypto/prng.c 2006-12-01 16:14:22.0
+0100
@@ -0,0 +1,203 @@
+/*
+ * Copyright 2006 IBM Corporation
+ * Author(s): Jan Glauber <[EMAIL PROTECTED]
This patch introduces a cpu time clock for s390 (only ticking
if the virtual cpu is running) and bases the s390 implementation
of sched_clock() on it.
The times lice length on a virtual cpu can be anything
between the calculated time slice and zero. In reality
this doesn't seem to be problem, sinc
On Thu, 2007-07-19 at 18:00 +0200, Ingo Molnar wrote:
> * Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
>
> > > /*
> > > - * Monotonic_clock - returns # of nanoseconds passed since time_init()
> > > + * Scheduler clock - returns current time in nanosec units.
> > > + * Now based on virtual cpu t
Hi Thomas,
> with 2.6.20.4 it works great, but when switching to 2.6.21-rcX it breaks
> with this:
>
> drivers/crypto/Kconfig:55: can't open file "arch/s390/crypto/Kconfig"
arch/s390/crypto/Kconfig is included there since that is the right place
for the config options to show up.
> I tried to
On Fri, 2007-03-30 at 05:55 -0400, Robert P. J. Day wrote:
> i'm betting the S390 folks would *really* hate that idea but, if you
> look closely, the generic Kconfig file *already* has some
> arch-dependent content:
>
> ...
> config CRYPTO_DEV_PADLOCK
> tristate "Support for VIA PadLock
Move the register definitions to the drivers directory because they
are only used there.
Signed-off-by: Jan Glauber
Tested-by: Steven J. Hill
---
.../cvmx-mpi-defs.h => drivers/spi/spi-cavium.h| 32 +-
drivers/spi/spi-octeon.c | 3 +-
2 fi
tches #1-5 prepare the Octeon driver for re-use.
Patch #6 adds the ThunderX driver.
The series was tested on MIPS (Edge Router PRO and cn71xx) and ThunderX.
Feedback welcome!
thanks,
Jan
Jan Glauber (5):
spi: octeon: Store system clock freqency in struct octeon_spi
spi: octeon: Put register offs
Instead of hard-coding the register offsets put them into a struct
and set them in the probe function.
Signed-off-by: Jan Glauber
Tested-by: Steven J. Hill
---
drivers/spi/spi-octeon.c | 41 +++--
1 file changed, 27 insertions(+), 14 deletions(-)
diff --git
Add ThunderX SPI driver using the shared part from the Octeon
driver. The main difference of the ThunderX driver is that it
is a PCI device so probing is different. The system clock settings
can be specified in device tree.
Signed-off-by: Jan Glauber
---
drivers/spi/Kconfig | 7
Storing the system clock frequency in struct octeon_spi avoids
calling the MIPS specific octeon_get_io_clock_rate() for every transfer.
Signed-off-by: Jan Glauber
Tested-by: Steven J. Hill
---
drivers/spi/spi-octeon.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a
From: "Steven J. Hill"
Remove all calls to cvmx_read_csr()/cvmx_write_csr() and use
the portable readq()/writeq() functions.
Signed-off-by: Steven J. Hill
Signed-off-by: Jan Glauber
---
drivers/spi/spi-octeon.c | 23 +++
1 file changed, 11 insertions(+), 12
Separate driver probing from SPI transfer functions.
Signed-off-by: Jan Glauber
Tested-by: Steven J. Hill
---
drivers/spi/Makefile | 1 +
drivers/spi/spi-cavium-octeon.c| 104 +
drivers/spi/{spi-octeon.c => spi-cavium.c} |
In case the high-level controller (HLC) is used the status code is
reported at a different location. Check that location after HLC
write operations if the ready bit is not set and return an appropriate
error code instead of always returning -EAGAIN.
Signed-off-by: Jan Glauber
---
drivers/i2c
out of the bad state.
Signed-off-by: Dmitry Bazhenov
Signed-off-by: Jan Glauber
[Changed commit message]
---
drivers/i2c/busses/i2c-octeon-core.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/drivers/i2c/busses/i2c-octeon-core.c
b/drivers/i2c/busses/i2c
From: Dmitry Bazhenov
The set SCL recovery function unconditionally pulls the SCL line low.
Only pull SCL line low according to val parameter.
Signed-off-by: Dmitry Bazhenov
Signed-off-by: Jan Glauber
[Changed commit message]
---
drivers/i2c/busses/i2c-octeon-core.c | 2 +-
1 file changed, 1
t and were tested on ThunderX and Octeon
(by Steven J. Hill).
thanks,
Jan
--
Dmitry Bazhenov (2):
i2c: octeon,thunderx: Fix set SCL recovery function
i2c: octeon,thunderx: Avoid sending STOP during recovery
Jan Glauber (3):
i2c: octeon,thunderx: Fix high-level controller status c
Add an additional status check before starting a transaction and,
if required, trigger the recovery if the check fails.
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/i2c-octeon-core.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/i2c/busses/i2c-octeon
Do not infinitely retry register readq and writeq operations
in order to not lock up the CPU in case the TWSI gets stuck.
Return -EIO in case of a failed data read. For all other
cases just return so subsequent operations will fail
and trigger the recovery.
Signed-off-by: Jan Glauber
On Wed, Sep 21, 2016 at 10:55:41PM +0200, Wolfram Sang wrote:
> On Wed, Sep 21, 2016 at 08:51:05AM +0200, Jan Glauber wrote:
> > Add an additional status check before starting a transaction and,
> > if required, trigger the recovery if the check fails.
> >
> >
On Wed, Sep 21, 2016 at 11:03:35PM +0200, Wolfram Sang wrote:
> On Wed, Sep 21, 2016 at 08:51:06AM +0200, Jan Glauber wrote:
> > Do not infinitely retry register readq and writeq operations
> > in order to not lock up the CPU in case the TWSI gets stuck.
> >
> > Retu
Hi Wolfram,
here are the remaining two patches with iopoll.h usage and a timed wait
before entering the recovery on a failed bus check.
thanks,
Jan
-
Jan Glauber (2):
i2c: octeon: thunderx: Check bus state before starting a transaction
i2c: octeon: thunderx: Limit
Do not infinitely retry register readq and writeq operations
in order to not lock up the CPU in case the TWSI gets stuck.
Return -ETIMEDOUT in case of a failed data read. For all other
cases just return so subsequent operations will fail
and trigger the recovery.
Signed-off-by: Jan Glauber
Add an additional status check before starting a transaction. If the
check fails wait for some time to tolerate multi-master mode. After the
timeout expires trigger the recovery.
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/i2c-octeon-core.c | 29 +
1 file
On Sat, Sep 24, 2016 at 11:24:19AM +0200, Wolfram Sang wrote:
> On Fri, Sep 23, 2016 at 11:40:38AM +0200, Jan Glauber wrote:
> > Add an additional status check before starting a transaction. If the
> > check fails wait for some time to tolerate multi-master mode. After the
>
On Wed, Jul 27, 2016 at 07:08:24PM +0100, Mark Brown wrote:
> On Mon, Jul 25, 2016 at 07:56:22PM +0200, Jan Glauber wrote:
> > Add ThunderX SPI driver using the shared part from the Octeon
> > driver. The main difference of the ThunderX driver is that it
> > is a PCI device so
- Dropped merged patches
thanks,
Jan
------
Jan Glauber (2):
spi: octeon: Split driver into Octeon specific and common parts
spi: octeon: Add thunderx driver
drivers/spi/Kconfig| 7 ++
drivers/spi/Makefile | 3 +
drivers/spi/spi-caviu
Add ThunderX SPI driver using the shared part from the Octeon
driver. The main difference of the ThunderX driver is that it
is a PCI device so probing is different. The system clock settings
can be specified in device tree.
Signed-off-by: Jan Glauber
---
drivers/spi/Kconfig | 7
Separate driver probing from SPI transfer functions.
Signed-off-by: Jan Glauber
---
drivers/spi/Makefile | 1 +
drivers/spi/spi-cavium-octeon.c| 102
drivers/spi/{spi-octeon.c => spi-cavium.c} |
On Tue, Aug 23, 2016 at 10:57:25PM +0200, Wolfram Sang wrote:
> On Wed, Jun 15, 2016 at 03:51:30PM +0200, Jan Glauber wrote:
> > Add SMBUS alert interrupt support. For now only device tree is
> > supported for specifying the alert. In case of ACPI an error
> > is returned.
&
On Tue, Aug 23, 2016 at 11:39:48PM +0200, Wolfram Sang wrote:
> On Tue, Aug 23, 2016 at 11:28:59PM +0200, Jan Glauber wrote:
> > On Tue, Aug 23, 2016 at 10:57:25PM +0200, Wolfram Sang wrote:
> > > On Wed, Jun 15, 2016 at 03:51:30PM +0200, Jan Glauber wrote:
> > >
On Tue, Aug 23, 2016 at 10:36:29PM +0200, Wolfram Sang wrote:
>
> > i2c-octeon-objs := i2c-cavium.o i2c-octeon-core.o
> > obj-$(CONFIG_I2C_OCTEON) += i2c-octeon.o
> > +i2c-thunderx-objs := i2c-cavium.o i2c-thunderx-core.o
> > +obj-$(CONFIG_I2C_THUNDERX) += i2c-thunderx.o
>
> Shouldn't that ra
On Tue, Aug 23, 2016 at 10:39:41PM +0200, Wolfram Sang wrote:
> On Tue, Aug 23, 2016 at 10:36:29PM +0200, Wolfram Sang wrote:
> >
> > > i2c-octeon-objs := i2c-cavium.o i2c-octeon-core.o
> > > obj-$(CONFIG_I2C_OCTEON) += i2c-octeon.o
> > > +i2c-thunderx-objs := i2c-cavium.o i2c-thunderx-core.o
>
The ThunderX SOC uses the same i2c block as the Octeon SOC.
The main difference is that on ThunderX the device is a PCI device
so device probing is done via PCI, interrupts are MSI-X. The
clock rates can be set via device tree or ACPI.
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/Kconfig
-phrase SMBUS error/not-specified message
Thanks,
Jan
-
Jan Glauber (8):
i2c: octeon: Rename driver to prepare for split
i2c: octeon: Split the driver into two parts
i2c: thunderx: Add i2c driver for ThunderX SOC
i2c: thunderx: Add SMBUS alert
Initialize booleon values with true instead of 1.
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/i2c-octeon-core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/busses/i2c-octeon-core.c
b/drivers/i2c/busses/i2c-octeon-core.c
index a327a5f..f45ea5e
Add SMBUS alert interrupt support. For now only device tree is
supported for specifying the alert. In case of ACPI an error
is returned.
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/Kconfig | 1 +
drivers/i2c/busses/i2c-octeon-core.h | 3 +++
drivers/i2c/busses/i2c
The i2c Octeon and ThunderX drivers are maintained by Cavium.
While at it fix the whitespace errors of the next entry.
Signed-off-by: Jan Glauber
Acked-by: David Daney
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index a306795..11cba03
The register offsets are different between Octeon and ThunderX so move
them into the algorithm struct and get rid of the define.
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/i2c-octeon-core.c | 28 -
drivers/i2c/busses/i2c-octeon-core.h | 35
Move common functionality into a separate file in preparation of the
re-use from the ThunderX i2c driver.
Functions are slightly re-ordered but no other changes are included.
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/Makefile | 3 +-
drivers/i2c/busses/i2c-octeon-core.c
Sort include files alphabetically to reduce probability of merge
conflicts.
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/i2c-octeon-platdrv.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/i2c/busses/i2c-octeon-platdrv.c
b/drivers/i2c/busses/i2c
This is an intermediate commit in preparation of the driver split.
The module rename in this commit will be reverted in the next patch,
this is just done to make the series bisectible.
Signed-off-by: Jan Glauber
---
drivers/i2c/busses/Makefile | 2 +-
drivers/i2c
-by: Jan Glauber
---
drivers/vfio/pci/vfio_pci.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
index 063c1ce..029ba13 100644
--- a/drivers/vfio/pci/vfio_pci.c
+++ b/drivers/vfio/pci/vfio_pci.c
@@ -1196,6 +1196,12 @@ static int
l.org/lkml/2017/5/15/934):
- Prevent probing by vfio-pci
David Daney (2):
PCI: Allow PCI_DEV_FLAGS_NO_BUS_RESET to be used on bus device
PCI: Avoid bus reset for Cavium cn8xxx root ports
Jan Glauber (1):
vfio/pci: Don't probe devices that can't be reset
drivers/pci/pci.c
From: David Daney
Root ports of cn8xxx do not function after bus reset when used with
some e1000e and LSI HBA devices. Add a quirk to prevent bus reset on
these root ports.
Signed-off-by: David Daney
[jglau...@cavium.com: fixed typo and whitespaces]
Signed-off-by: Jan Glauber
---
drivers/pci
.
Signed-off-by: David Daney
[jglau...@cavium.com: fixed typo]
Signed-off-by: Jan Glauber
---
drivers/pci/pci.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index af0cc34..d9abbc9 100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -4290,6 +4290,10
Hi Trond,
is there a patch available for this issue? I'm running into with
4.14-rc5 on my ARM64 board.
thanks, Jan
2017-10-11 19:49 GMT+02:00 Trond Myklebust :
> On Tue, 2017-10-10 at 10:19 -0700, t...@kernel.org wrote:
>> Hello,
>>
>> On Tue, Oct 10, 2017 at 04:48:57PM +, Trond Myklebust wr
Split the Cavium EDAC entry into MIPS and ARM drivers because
they have different maintainers and mailing lists.
Add myself as additional maintainer to the ThunderX driver.
Signed-off-by: Jan Glauber
---
MAINTAINERS | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a
On Tue, Feb 27, 2018 at 01:26:20PM +, George Cherian wrote:
> Add support for SMBus alert mechanism to i2c-xlp9xx driver.
> The second interrupt is parsed to use for SMBus alert.
> The first interrupt is the i2c controller main interrupt.
>
> Signed-off-by: Kamlakant Patel
> Signed-off-by: Ge
I don't know how valuable same-company reviewed-by's are in the end,
but the patches look good to me with the small change in SMBalert, so you
could add:
Reviewed-by: Jan Glauber
--Jan
On Tue, Feb 27, 2018 at 01:26:18PM +, George Cherian wrote:
> I2C bus enters the STOP co
On Tue, Mar 06, 2018 at 02:12:29PM +0100, Arnd Bergmann wrote:
> On Fri, Mar 2, 2018 at 3:37 PM, Jan Glauber wrote:
> > ThunderX1 dual socket has 96 CPUs and ThunderX2 has 224 CPUs.
>
> Are you sure about those numbers? From my counting, I would have expected
> twice that nu
On Tue, Mar 06, 2018 at 03:02:01PM +0100, Jan Glauber wrote:
> On Tue, Mar 06, 2018 at 02:12:29PM +0100, Arnd Bergmann wrote:
> > On Fri, Mar 2, 2018 at 3:37 PM, Jan Glauber wrote:
> > > ThunderX1 dual socket has 96 CPUs and ThunderX2 has 224 CPUs.
> >
> > Are you
On Mon, Mar 26, 2018 at 11:28:28AM +0200, Arnd Bergmann wrote:
> On Mon, Mar 26, 2018 at 10:52 AM, Jan Glauber
> wrote:
> > On Tue, Mar 06, 2018 at 03:02:01PM +0100, Jan Glauber wrote:
> >> On Tue, Mar 06, 2018 at 02:12:29PM +0100, Arnd Bergmann wrote:
> >> > On
for test_comp().
Signed-off-by: Mahipal Challa
Signed-off-by: Balakrishna Bhamidipati
[jglau...@cavium.com: removed unrelated printk changes, rewrote commit msg,
fixed whitespace and unneeded initialization]
Signed-off-by: Jan Glauber
---
crypto/testmgr.c |
Some bug fixes for this driver after it stopped working with virtual mapped
stacks. I think the first two patches qualify for stable.
Jan Glauber (5):
crypto: thunderx_zip: Fix fallout from CONFIG_VMAP_STACK
crypto: thunderx_zip: Limit result reading attempts
crypto: thunderx_zip: Prevent
small delay between the reading attempts.
Signed-off-by: Jan Glauber
Reviewed-by: Robert Richter
Cc: stable # 4.14
---
drivers/crypto/cavium/zip/common.h | 21 +
drivers/crypto/cavium/zip/zip_deflate.c | 4 ++--
drivers/crypto/cavium/zip/zip_inflate.c | 4 ++--
3 files
The pending request counter was read from the wrong register. While
at it, there is no need to use an atomic for it as it is only read
localy in a loop.
Signed-off-by: Jan Glauber
Reviewed-by: Robert Richter
---
drivers/crypto/cavium/zip/zip_main.c | 13 +
drivers/crypto/cavium/zip
Avoid two potential divisions by zero when calculating average
values for the zip statistics.
Signed-off-by: Jan Glauber
Reviewed-by: Robert Richter
---
drivers/crypto/cavium/zip/zip_main.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/drivers/crypto/cavium/zip
occur but everything will continue to work, so just
ignore it.
Signed-off-by: Jan Glauber
Reviewed-by: Robert Richter
---
drivers/crypto/cavium/zip/zip_device.c | 4 ++--
drivers/crypto/cavium/zip/zip_main.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/crypto
forever for the completion byte to contain a non-zero value.
Allocating the result struct from 1:1 mapped memory resolves this
bug.
Signed-off-by: Jan Glauber
Reviewed-by: Robert Richter
Cc: stable # 4.14
---
drivers/crypto/cavium/zip/zip_crypto.c | 22 ++
1 file changed, 14
Hi Marc,
with 4.20-rc3 I see two WARN_ON's firing on a ThunderX2 system that come from
commit 3fb68faee867 (irqchip/gic-v3-its: Register LPI tables with EFI config
table).
Global efi_memreserve_root is NULL as it will only be set when early initcalls
are
running, but from the backtrace the WARN
On Tue, Nov 20, 2018 at 07:03:17PM +, Will Deacon wrote:
> On Tue, Nov 20, 2018 at 06:28:54PM +, Will Deacon wrote:
> > On Sat, Nov 10, 2018 at 11:17:03AM +0000, Jan Glauber wrote:
> > > On Fri, Nov 09, 2018 at 03:58:56PM +, Will Deacon wrote:
> > > > On F
On Wed, Nov 28, 2018 at 08:08:06PM +, Will Deacon wrote:
> I spent some more time looking at this today...
>
> On Fri, Nov 23, 2018 at 06:05:25PM +, Will Deacon wrote:
> > Doing some more debugging, it looks like the usual failure case is where
> > one CPU clears the inode field in the den
Hi Al,
I'm seeing the following oops reproducible with upstream kernel on arm64
(ThunderX2):
[ 5428.795719] Unable to handle kernel NULL pointer dereference at virtual
address 0040
[ 5428.813838] Mem abort info:
[ 5428.820721] ESR = 0x9606
[ 5428.828476] Exception class = DA
On Fri, Nov 09, 2018 at 03:58:56PM +, Will Deacon wrote:
> On Fri, Nov 09, 2018 at 02:37:51PM +0000, Jan Glauber wrote:
> > I'm seeing the following oops reproducible with upstream kernel on arm64
> > (ThunderX2):
>
> [...]
>
> > It happens after 1-3 ho
> [1]
> https://lkml.kernel.org/r/CA+55aFzCG-zNmZwX4A2FQpadafLfEzK6CC=qpxydaacu1rq...@mail.gmail.com
>
> Cc: David Daney
> Cc: Jan Glauber
> Cc: Borislav Petkov
> Cc: Mauro Carvalho Chehab
> Cc: linux-e...@vger.kernel.org
> Signed-off-by: Kees Cook
Acked-by: Jan Gl
On Fri, Oct 05, 2018 at 05:32:07PM +0200, Dmitry Vyukov wrote:
[...]
> This all makes me think that somebody else has left these 0xf8 in
> shadow before ext4_map_blocks started executing.
> Unfortunately debugging garbage in stack shadow is not completely
> trivial and there is no common recipe. I
Hi,
I'm getting below warning when I enable CONFIG_KASAN_EXTRA=y on a arm64
ThunderX2 system.
As far as I can tell this is present since KASAN_EXTRA was introduced (4.16).
[ 64.547333]
==
[ 64.561933] BUG: KASAN: use-after-scop
1 - 100 of 541 matches
Mail list logo
