Now that jedec_ddr_data.c was moved from lib/ to drivers/memory/,
is included only from drivers/memory/.
Make it a local header of drivers/memory/.
The directory include/memory is now gone.
While I am here, I also changed #include to
. Because CONFIG_DDR is bool, jedec_ddr_data.c is
never
On Wed, 15 May 2019, Dan Carpenter wrote:
> The problem is that on 64bit systems then we don't clear the higher
> bits of the "pending" variable. So when we do:
>
> ack = pending & ~BIT(STMFX_REG_IRQ_SRC_EN_GPIO);
> if (ack) {
>
> the if (ack) condition relies on uninitialized
> Am 01.06.2019 um 23:57 schrieb Linus Walleij :
>
> On Fri, May 31, 2019 at 7:06 PM H. Nikolaus Schaller
> wrote:
>
>> Now, this was not a (visible) problem until patch
>>
>>8b9f9d4dc511 regmap: verify if register is writeable before writing
>> operations
>>
>> enforces to check
On Fri 2019-05-31 14:37:52, Miroslav Benes wrote:
> On Fri, 31 May 2019, Petr Mladek wrote:
>
> > The err_buf array uses 128 bytes of stack space. Move it off the stack
> > by making it static. It's safe to use a shared buffer because
> > klp_try_switch_task() is called under klp_mutex.
> >
>
On Fri, 2019-04-26 at 15:06:34 UTC, =?utf-8?q?Pawe=C5=82_Chmiel?= wrote:
> From: Jonathan Bakker
>
> Used in several S5PV210-based Galaxy S devices, among them SGH-T959V,
> SGH-T959P, SGH-T839, and SPH-D700.
>
> Signed-off-by: Jonathan Bakker
> Signed-off-by: Paweł Chmiel
Applied to
On Wed, 2019-05-01 at 19:22:14 UTC, Kamal Dasu wrote:
> The oobregion->offset for large page nand parts was wrong, change
> fixes this error in calculation.
>
> Fixes: ef5eeea6e911 ("mtd: nand: brcm: switch to mtd_ooblayout_ops")
> Signed-off-by: Kamal Dasu
> Reviewed-by: Florian Fainelli
On Mon, 3 Jun 2019 at 01:28, Andrew Jeffery wrote:
> On Fri, 31 May 2019, at 18:40, Alexander Filippov wrote:
> > VESNIN is an OpenPower machine with an Aspeed 2400 BMC SoC manufactured
> > by YADRO.
> >
> > Signed-off-by: Alexander Filippov
>
> Reviewed-by: Andrew Jeffery
Thanks. Applied to
mv88e6xxx_g1_stats_wait has no users outside global1.c, so make it
static.
Signed-off-by: Rasmus Villemoes
---
drivers/net/dsa/mv88e6xxx/global1.c | 2 +-
drivers/net/dsa/mv88e6xxx/global1.h | 1 -
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/dsa/mv88e6xxx/global1.c
On Tue, May 28, 2019 at 1:55 PM Gareth Williams
wrote:
> The driver is gaining power domain support, so add the new property
> to the DT binding and update the examples.
>
> Signed-off-by: Gareth Williams
> Reviewed-by: Geert Uytterhoeven
> ---
> v4:
> - Added missing HCLK to UART0 example to
On Sat, Jun 01, 2019 at 06:27:33PM -0400, Joel Fernandes (Google) wrote:
> +#define list_for_each_entry_rcu(pos, head, member, cond...) \
> + if (COUNT_VARGS(cond) != 0) { \
> + __list_check_rcu_cond(0, ## cond); \
> +
On Tue, 2019-05-21 at 14:44:21 UTC, Kamal Dasu wrote:
> nand-ecc-strength and nand-ecc-step-size can be made optional as
> brcmnand driver can support using raw NAND layer detected values.
>
> Signed-off-by: Kamal Dasu
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git
On Wed, 2019-05-22 at 22:05:55 UTC, Jeff Kletsky wrote:
> From: Jeff Kletsky
>
> The GigaDevice GD5F1GQ4UFxxG SPI NAND is in current production devices
> and, while it has the same logical layout as the E-series devices,
> it differs in the SPI interfacing in significant ways.
>
> This support
On Wed, 2019-05-22 at 22:05:53 UTC, Jeff Kletsky wrote:
> From: Jeff Kletsky
>
> The GigaDevice GD5F1GQ4UFxxG SPI NAND utilizes three-byte addresses
> for its page-read ops.
>
> http://www.gigadevice.com/datasheet/gd5f1gq4xfxxg/
>
> Signed-off-by: Jeff Kletsky
Applied to
On Wed, 2019-05-22 at 22:05:54 UTC, Jeff Kletsky wrote:
> From: Jeff Kletsky
>
> The GigaDevice GD5F1GQ4UFxxG SPI NAND utilizes two-byte device IDs.
>
> http://www.gigadevice.com/datasheet/gd5f1gq4xfxxg/
>
> Signed-off-by: Jeff Kletsky
Applied to
On Fri, 2019-05-31 at 10:17 -0700, Evan Green wrote:
> On Fri, May 31, 2019 at 1:06 AM Chuanjia Liu
> wrote:
> >
> > On Thu, 2019-05-30 at 10:12 -0700, Evan Green wrote:
> > > On Wed, May 15, 2019 at 1:05 AM Nicolas Boichat
> > > wrote:
> > > >
> > > > On Wed, May 15, 2019 at 4:14 AM Stephen
On Tue, May 28, 2019 at 1:55 PM Gareth Williams
wrote:
> There are several clocks on the r9a06g032 which are currently not
> enabled in their drivers that can be delegated to clock domain system
> for power management. Therefore add support for clock domain
> functionality to the r9a06g032 clock
Thanks Bjorn for your review.
On 6/1/2019 2:09 AM, Bjorn Helgaas wrote:
> [+cc Lukas, author of 07f4f97d7b4b ("vga_switcheroo: Use device link
> for HDA controller")]
>
> On Fri, May 31, 2019 at 10:31:09AM +0530, Abhishek Sahu wrote:
>> NVIDIA Turing GPUs include hardware support for USB Type-C
On 30.05.19 09:23, Richard Weinberger wrote:
> - Ursprüngliche Mail -
>> Von: "Herbert Xu"
>> An: "richard"
>> CC: "Linux Crypto Mailing List" ,
>> linux-arm-ker...@lists.infradead.org, "linux-kernel"
>> , linux-...@nxp.com, feste...@gmail.com,
>> "kernel" , "Sascha Hauer"
>> ,
On Mon, 13 May 2019, Heiko Stuebner wrote:
> From: Daniel Schultz
>
> The Rockchip PMIC driver can automatically detect connected component
> versions by reading the ID_MSB and ID_LSB registers. The probe function
> will always fail with RK818 PMICs because the ID_MSK is 0xFFF0 and the
> RK818
On 03.06.19 04:31, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 2ee567d31a5812cf93c0ec943b142de252ce1cff ("KVM: selftests: enable
> pgste option for the linker on s390")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
On Mon, Jun 3, 2019 at 11:22 AM Young Xiao <92siuy...@gmail.com> wrote:
>
> Clearing the IFF_ALLMULTI flag on a down interface could cause an allmulti
> overflow on the underlying interface.
>
> Attempting the set IFF_ALLMULTI on the underlying interface would cause an
> error and the log message:
On Sun, Jun 02, 2019 at 10:35:22PM +0200, Linus Walleij wrote:
> On Sun, Jun 2, 2019 at 3:51 PM Linus Walleij wrote:
> > On Wed, May 29, 2019 at 4:53 PM Thierry Reding
> > wrote:
> >
> > > From: Thierry Reding
> > >
> > > Hierarchical IRQ domains can be used to stack different IRQ controllers
On Sun, Jun 02, 2019 at 03:46:00PM +0200, Linus Walleij wrote:
> On Wed, May 29, 2019 at 4:53 PM Thierry Reding
> wrote:
>
> > From: Thierry Reding
> >
> > Hierarchical IRQ domains can be used to stack different IRQ controllers
> > on top of each other. One specific use-case where this can be
Hi Finn,
On Mon, Jun 3, 2019 at 9:40 AM Finn Thain wrote:
> On Mon, 3 Jun 2019, Geert Uytterhoeven wrote:
> > On Mon, Jun 3, 2019 at 1:32 AM Finn Thain
> > wrote:
> > > On Sun, 2 Jun 2019, Geert Uytterhoeven wrote:
> > > > On Sun, Jun 2, 2019 at 3:29 AM Finn Thain
> > > > wrote:
> > > > > A
The macros have an extraneous '800' (after 0180C2 there should be just
six nibbles, with X representing one), while the comments have
interchanged c2 and 80 and an extra :00.
Signed-off-by: Rasmus Villemoes
---
drivers/net/dsa/mv88e6xxx/global1.c | 16
On 31.05.2019 23:59, Evan Green wrote:
The manpage for modprobe mentions that dashes and underscores are
treated interchangeably in module names. The stack trace dumps seem
to print module names with underscores. Use bash to replace _ with
the pattern [-_] so that file names with dashes or
Am Freitag, 31. Mai 2019 schrieb Arnd Bergmann:
Just for information about the history and maybe state of parts of the old
ISDN drivers.
There are still some large private ISDN networks available and will stay
available for several years. I am still serving solutions there, but without
i4l or
On 31.05.19 11:36, David Hildenbrand wrote:
> systemd-modules-load.service automatically tries to load the pkey module
> on systems that have MSA.
>
> Pkey also requires the MSA3 facility and a bunch of subfunctions.
> Failing with -EOPNOTSUPP makes "systemd-modules-load.service" fail on
> any
Hi Kees,
> Am 22.05.2019 um 08:02 schrieb H. Nikolaus Schaller :
>
> It turns out that HOSTCC and HOSTCXX are a gcc-4.9.4 installed through
> MacPorts.
> And CC is the self-bootstrapped cross-gcc-4.9.2 toolchain for arm.
>
> The problem is likely that they do not know of each other, i.e. the
On Sun, Jun 02, 2019 at 03:39:48PM +0800, Hillf Danton wrote:
>
> Hi Christoph
>
> On Sat, 1 Jun 2019 09:49:53 +0200 Christoph Hellwig wrote:
> >
> > diff --git a/arch/sparc/include/asm/pgtable_64.h
> > b/arch/sparc/include/asm/pgtable_64.h
> > index a93eca29e85a..2301ab5250e4 100644
> > ---
On Sat, Jun 01, 2019 at 09:28:54AM -0700, Linus Torvalds wrote:
> Both sparc64 and sh had this pattern, but now that I look at it more
> closely, I think your version is wrong, or at least nonoptimal.
I bet it is. Then again these symbols are just required for the code
to compile, as neither
Hi,
On Fri, May 31, 2019 at 12:27:55PM +0200, Luca Weiss wrote:
> On Freitag, 24. Mai 2019 11:20:01 CEST Maxime Ripard wrote:
> >
> > It would be great to drop the -keys from the compatible, and to
> > document the bindings
> >
> > Looks good otherwise
> >
> > Maxime
>
> So I should just document
On Sat, Jun 01, 2019 at 09:14:17AM -0700, Linus Torvalds wrote:
> On Sat, Jun 1, 2019 at 12:50 AM Christoph Hellwig wrote:
> >
> > Pass in the already calculated end value instead of recomputing it, and
> > leave the end > start check in the callers instead of duplicating them
> > in the arch
On Mon, 3 Jun 2019, Geert Uytterhoeven wrote:
> Hi Finn,
>
> On Mon, Jun 3, 2019 at 1:32 AM Finn Thain wrote:
> > On Sun, 2 Jun 2019, Geert Uytterhoeven wrote:
> > > On Sun, Jun 2, 2019 at 3:29 AM Finn Thain
> > > wrote:
> > > > A system bus error during a PDMA transfer can mess up the
Hi, Abel
> -Original Message-
> From: Abel Vesa
> Sent: Monday, June 3, 2019 3:30 PM
> To: Anson Huang
> Cc: mturque...@baylibre.com; sb...@kernel.org; robh...@kernel.org;
> mark.rutl...@arm.com; shawn...@kernel.org; s.ha...@pengutronix.de;
> ker...@pengutronix.de; feste...@gmail.com;
On Mon, Jun 03, 2019 at 09:15:08AM +0900, Masahiro Yamada wrote:
> On Mon, Jun 3, 2019 at 2:15 AM Greg KH wrote:
> >
> > On Sun, Jun 02, 2019 at 09:03:46PM +0900, Masahiro Yamada wrote:
> > > On Sun, Jun 2, 2019 at 4:17 PM Greg KH wrote:
> > > >
> > > > The following changes since commit
> > >
On 24/05/19 3:25 AM, Alan Mikhak wrote:
> Always skip odd bar when skipping 64bit BARs in pci_epf_test_set_bar()
> and pci_epf_test_alloc_space().
>
> Otherwise, pci_epf_test_set_bar() will call pci_epc_set_bar() on odd loop
> index when skipping reserved 64bit BAR. Moreover,
Document drive strength settings for Bitmain BM1880 SoC.
Signed-off-by: Manivannan Sadhasivam
---
.../bindings/pinctrl/bitmain,bm1880-pinctrl.txt | 11 +++
1 file changed, 11 insertions(+)
diff --git
a/Documentation/devicetree/bindings/pinctrl/bitmain,bm1880-pinctrl.txt
Add drive strength support for Bitmain BM1880 SoC.
Signed-off-by: Manivannan Sadhasivam
---
drivers/pinctrl/pinctrl-bm1880.c | 290 ++-
1 file changed, 287 insertions(+), 3 deletions(-)
diff --git a/drivers/pinctrl/pinctrl-bm1880.c b/drivers/pinctrl/pinctrl-bm1880.c
On 19-06-03 09:27:47, anson.hu...@nxp.com wrote:
> From: Anson Huang
>
> This patch adds basic i.MM8MN DDR4 EVK board support.
>
> Signed-off-by: Anson Huang
> ---
> No changes.
> ---
> arch/arm64/boot/dts/freescale/Makefile| 1 +
>
On 19-06-03 09:35:03, anson.hu...@nxp.com wrote:
> From: Anson Huang
>
> Enable CONFIG_CLK_IMX8MN to support i.MX8MN clock driver.
>
> Signed-off-by: Anson Huang
> ---
> No changes.
> ---
> arch/arm64/configs/defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
On 19-06-03 09:35:02, anson.hu...@nxp.com wrote:
> From: Anson Huang
>
> This patch adds i.MX8MN clock driver support.
>
> Signed-off-by: Anson Huang
> ---
> Changes since V1:
> - add GPIOx clocks.
...
> +static struct imx_pll14xx_clk imx8mn_sys_pll __initdata = {
> + .type
On Sat, 11 May 2019, Daniel Gomez wrote:
> MODULE_DEVICE_TABLE(of, should be called to complete DT
> OF mathing mechanism and register it.
>
> Before this patch:
> modinfo ./drivers/mfd/madera.ko | grep alias
>
> After this patch:
> modinfo ./drivers/mfd/madera.ko | grep alias
> alias:
On Mon, Jun 3, 2019 at 4:26 PM Hans Verkuil wrote:
>
> On 5/31/19 10:01 AM, Stanimir Varbanov wrote:
> > Hi,
> >
> > On 5/27/19 11:18 AM, Tomasz Figa wrote:
> >> On Mon, May 27, 2019 at 4:39 PM Hans Verkuil wrote:
> >>>
> >>> On 5/27/19 5:51 AM, Tomasz Figa wrote:
> On Tue, May 21, 2019 at
ROHM BD70528 PMIC includes battery charger block. Support charger
staus queries and doing few basic settings like input current limit
and charging current.
Signed-off-by: Matti Vaittinen
Acked-by: Sebastian Reichel
---
Staticized the const array to move it to RO section as suggested by
On Sat, Jun 1, 2019 at 4:15 AM Gen Zhang wrote:
> In selinux_sb_eat_lsm_opts(), 'arg' is allocated by kmemdup_nul(). It
> returns NULL when fails. So 'arg' should be checked. And 'mnt_opts'
> should be freed when error.
>
> Signed-off-by: Gen Zhang
> Reviewed-by: Ondrej Mosnacek
> Fixes:
On Thu, May 30, 2019 at 10:40:09AM +0100, Chris Wilson wrote:
> Quoting Janusz Krzysztofik (2019-05-30 10:24:26)
> > In order to support driver hot unbind, some cleanup operations, now
> > performed on PCI driver remove, must be called later, after all device
> > file descriptors are closed.
> >
Hello dear,
We are in the market for your products after meeting at your stand during last
expo.
Please kindly send us your latest catalog and price list so as to start a new
project/order as promised during the exhibition.
I would appreciate your response about the above details required
Support RTC block in ROHM bd70528 power management IC. Support
getting and setting the time and date as well as arming an alarm
which can also be used to wake the PMIC from standby state.
HW supports wake interrupt only for the next 24 hours (sec, minute
and hour information only) so we limit
ROHM BD70528 PMIC has 4 GPIO pins. Allow them to be
controlled by GPIO framework.
IRQs are handled by regmap-irq and GPIO driver is not
aware of the irq usage.
Signed-off-by: Matti Vaittinen
Reviewed-by: Linus Walleij
---
Unchanged from v14
drivers/gpio/Kconfig| 11 ++
Document bindings for regulators (3 bucks, 3 LDOs and 2 LED
drivers) and 4 GPIO pins which can be configured for I/O or
as interrupt sources withe configurable trigger levels.
Signed-off-by: Matti Vaittinen
Reviewed-by: Rob Herring
Acked-by: Linus Walleij
Acked-for-MFD-by: Lee Jones
---
Hi Eugeniu,
On Fri, May 31, 2019 at 5:25 PM Eugeniu Rosca wrote:
> On Tue, May 28, 2019 at 11:19:04AM +0200, Geert Uytterhoeven wrote:
> [..]
> > > + wlan_en: regulator-wlan_en {
> > > + compatible = "regulator-fixed";
> > > + regulator-name =
On 5/31/19 10:01 AM, Stanimir Varbanov wrote:
> Hi,
>
> On 5/27/19 11:18 AM, Tomasz Figa wrote:
>> On Mon, May 27, 2019 at 4:39 PM Hans Verkuil wrote:
>>>
>>> On 5/27/19 5:51 AM, Tomasz Figa wrote:
On Tue, May 21, 2019 at 9:27 PM Hans Verkuil wrote:
>
> On 5/21/19 11:09 AM, Tomasz
ROHM BD70528 is an ultra low power PMIC with similar 32K clk as
bd718x7. Only difference (from clk perspective) is register address.
Add support for controlling BD70528 clk using bd718x7 driver.
Signed-off-by: Matti Vaittinen
Acked-by: Stephen Boyd
---
Unchanged from v14
drivers/clk/Kconfig
ROHM BD70528MWV is an ultra-low quiescent current general
purpose single-chip power management IC for battery-powered
portable devices.
Add MFD core which enables chip access for following subdevices:
- regulators/LED drivers
- battery-charger
- gpios
- 32.768kHz
Split the bd718x7.h to ROHM common and bd718x7 specific parts
so that we do not need to add same things in every new ROHM
PMIC header. Please note that this change requires changes also
in bd718x7 sub-device drivers for regulators and clk.
Signed-off-by: Matti Vaittinen
Acked-by: Mark Brown
On Wed, 08 May 2019, Heiko Stuebner wrote:
> I've picked up and rebased Tony's patch-series for rk809 and rk817.
> From the last iteration it looks like the regulator-portion did
> fall through the cracks, the other patches seem to be sufficiently
> reviewed/acked.
>
> The regulator-patch could
Patch series introducing support for ROHM BD70528 PMIC
ROHM BD70528 is a programmable Power Management IC for battery
powered 'ultra low power' systems like the pre-announced NXP
i.MX7 ULP. This patch series introduces support for the PMIC. Please
note that this driver only supports HW setup
On Mon, Jun 03, 2019 at 12:01:14PM +0800, Herbert Xu wrote:
> On Sun, Jun 02, 2019 at 08:47:07PM -0700, Paul E. McKenney wrote:
> >
> > CPU2: if (b != 1)
> > CPU2: b = 1;
>
> Stop right there. The kernel is full of code that assumes that
> assignment to an
On Sat, Jun 1, 2019 at 4:15 AM Gen Zhang wrote:
> In selinux_sb_eat_lsm_opts(), 'arg' is allocated by kmemdup_nul(). It
> returns NULL when fails. So 'arg' should be checked. And 'mnt_opts'
> should be freed when error.
>
> Signed-off-by: Gen Zhang
> Reviewed-by: Ondrej Mosnacek
It looks like
On Fri, May 31, 2019 at 03:33:41PM +0300, Dmitry Osipenko wrote:
> 31.05.2019 11:26, Peter De Schrijver пишет:
> > On Fri, May 24, 2019 at 06:32:45PM +0300, Dmitry Osipenko wrote:
> >> Hello,
> >>
> >> This series primarily unifies the driver code across all Tegra SoC
> >> generations. In a result
On Fri 31-05-19 23:34:07, Minchan Kim wrote:
> On Fri, May 31, 2019 at 04:03:32PM +0200, Michal Hocko wrote:
> > On Fri 31-05-19 22:39:04, Minchan Kim wrote:
> > > On Fri, May 31, 2019 at 10:47:52AM +0200, Michal Hocko wrote:
> > > > On Fri 31-05-19 15:43:08, Minchan Kim wrote:
> > > > > When a
Hi Yamada-san,
On Sat, Jun 1, 2019 at 5:24 AM Masahiro Yamada
wrote:
> Prior to the adoption of SPDX, it was difficult for tools to determine
> the correct license due to incomplete or badly formatted license text.
> The SPDX solves this issue, assuming people can correctly spell
>
Hi,
Ok, can you share your .config ?
Christophe
Le 31/05/2019 à 03:29, Daniel Axtens a écrit :
Hi Christophe,
I tried this on the t4240rdb and it fails to boot if KASAN is
enabled. It does boot with the patch applied but KASAN disabled, so that
narrows it down a little bit.
I need to focus
On 6/1/19 11:04 AM, Christoph Hellwig wrote:
Looks good,
Reviewed-by: Christoph Hellwig
Thanks for your time,
Alex
___
linux-riscv mailing list
linux-ri...@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
On 5/31/2019 4:15 AM, Herrenschmidt, Benjamin wrote:
On Thu, 2019-05-30 at 11:19 -0700, Boris Petkov wrote:
On May 30, 2019 3:15:29 AM PDT, Hanna Hawa wrote:
Add support for error detection and correction for Amazon's
Annapurna
Labs SoCs for L1/L2 caches.
So this should be a driver for
On Sat, Jun 1, 2019 at 7:15 PM David Ahern wrote:
>
> On 6/1/19 12:05 AM, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:dfb569f2 net: ll_temac: Fix compile error
> > git tree: net-next
> syzbot team:
>
> Is there any way to know the history of
On (05/28/19 15:42), Petr Mladek wrote:
> On Tue 2019-05-28 13:46:19, Sergey Senozhatsky wrote:
> > On (05/28/19 13:15), Sergey Senozhatsky wrote:
> > > On (05/28/19 01:24), Dmitry Safonov wrote:
> > > [..]
> > > > While handling sysrq the console_loglevel is bumped to default to print
> > > >
On 6/3/2019 10:36 PM, Jin Yao wrote:
In some cases small changes in hot loops can show big differences.
But it's difficult to identify these differences.
perf diff currently can only diff symbols (functions). We can also expand
it to diff cycles of individual programs blocks as reported by
csky pmu counter may have different io width. When the counter is smaller
then 64 bits and counter value is smaller than the old value, it will
result to a extremely large delta value. So the sampled value should be
extend to 64 bits to avoid this, the extension bits base on the
reg-io-width
This patch adds the documentation to describe that how to add pmu node in
dts.
Signed-off-by: Mao Han
CC: Rob Herring
CC: Guo Ren
CC: linux-c...@vger.kernel.org
---
Documentation/devicetree/bindings/csky/pmu.txt | 38 ++
1 file changed, 38 insertions(+)
create mode
This patch change the csky pmu initialization from arch init to
device init. The pmu can be configued with information from
device tree(pmu device name, irq number and etc.).
Signed-off-by: Mao Han
CC: Guo Ren
CC: linux-c...@vger.kernel.org
---
arch/csky/kernel/perf_event.c | 58
csky_pmu_event_init is called several times during the perf record
initialzation. After configure the event counter in either kernel
space or user space, csky_pmu_event_init is called twice with no
attr specified. Configuration will be overwritten with sampling in
both kernel space and user space.
This patch set add hardware sampling support for csky-pmu, and
also add some properties to pmu node definition. perf can record
on hardware event with this patch applied.
Changes since v2:
- update dt-binding(csky pmu use rising edge interrupt)
- use cpuhp_setup_state to enable irq(fix irq
From: Guo Ren
ck810 pmu only support event with index 0-8 and 0xd; ck860 only
support event 1~4, 0xa~0x1b. So do not register unsupport event
to hardware cache event, which may leader to unknown behavior.
Signed-off-by: Guo Ren
Signed-off-by: Mao Han
CC: Guo Ren
CC:
This patch add interrupt request and handler for csky pmu.
perf can record on hardware event with this patch applied.
Signed-off-by: Mao Han
CC: Guo Ren
CC: linux-c...@vger.kernel.org
---
arch/csky/kernel/perf_event.c | 293 +++---
1 file changed, 277
perf diff currently can only diff symbols(functions). We should expand it
to diff cycles of individual programs blocks as reported by timed LBR.
This would allow to identify changes in specific code accurately.
We need a new structure to maintain the basic block information, such as,
The hist__account_cycles() can account cycles per basic
block. The basic block information is saved in cycles_hist
structure.
This patch processes each symbol, get basic blocks from
cycles_hist and add the basic block entries to a new hists
(block_hists in hist_entry). Using a hists is because
we
In some cases small changes in hot loops can show big differences.
But it's difficult to identify these differences.
perf diff currently can only diff symbols (functions). We can also expand
it to diff cycles of individual programs blocks as reported by timed LBR.
This would allow to identify
perf record -b ./div
perf record -b ./div
Following is the default perf diff output
# perf diff
# Event 'cycles'
#
# Baseline Delta Abs Shared Object Symbol
# .
#
49.03% +0.30% div [.]
The block_info contains the program basic block information, i.e,
contains the start address and the end address of this basic block and
how much cycles it takes. We need to compare, sort and even print out
the basic block by some orders, i.e. sort by cycles.
For this purpose, we add block_info
Documentation the new computation selection 'cycles'.
Signed-off-by: Jin Yao
---
tools/perf/Documentation/perf-diff.txt | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/tools/perf/Documentation/perf-diff.txt
b/tools/perf/Documentation/perf-diff.txt
index
We will expand perf diff to support diff cycles of individual programs
blocks, so it requires all data files having branch stacks.
This patch checks HEADER_BRANCH_STACK in header, and only set the flag
has_br_stack when HEADER_BRANCH_STACK are set in all data files.
v2:
---
Move
The target is to compare the performance difference (cycles
diff) for the same basic blocks in different data files.
The same basic block means same function, same start address
and same end address. This patch finds the same basic blocks
from different data files and link them together and
The task_struct argument is not getting used in __do_page_fault(). Hence
just drop it and use current or cuurent->mm instead where ever required.
This does not change any functionality.
Signed-off-by: Anshuman Khandual
Cc: Catalin Marinas
Cc: Will Deacon
Cc: Mark Rutland
Cc: James Morse
Cc:
On Sun 2019-06-02 08:24:35, Joel Fernandes wrote:
> On Sun, Jun 2, 2019 at 8:20 AM Joel Fernandes wrote:
> >
> > On Sun, Jun 2, 2019 at 3:00 AM Pavel Machek wrote:
> > >
> > > On Sat 2019-06-01 18:27:34, Joel Fernandes (Google) wrote:
> > > > Signed-off-by: Joel Fernandes (Google)
> > >
> > >
This consolidates page fault information capture and move them bit earlier.
While here it also adds an wrapper is_el0_write_abort(). It also saves some
cycles by replacing multiple user_mode() calls into a single one earlier
during the fault.
Signed-off-by: Anshuman Khandual
Cc: Catalin Marinas
__do_page_fault() is over complicated with multiple goto statements. This
cleans up the code flow and while there drops local variable vm_fault_t.
Signed-off-by: Anshuman Khandual
Cc: Catalin Marinas
Cc: Will Deacon
Cc: Mark Rutland
Cc: James Morse
Cc: Andrey Konovalov
Cc: Christoph Hellwig
On Mon, Jun 03, 2019 at 01:26:26PM +0800, Herbert Xu wrote:
> On Sun, Jun 02, 2019 at 08:47:07PM -0700, Paul E. McKenney wrote:
> >
> > 1. These guarantees are of full memory barriers, -not- compiler
> > barriers.
>
> What I'm saying is that wherever they are, they must come with
> compiler
This contains some clean ups for page fault handling in do_page_fault().
This has been boot tested on arm64 platform along with some stress test
but just build tested on others.
Cc: Catalin Marinas
Cc: Will Deacon
Cc: Mark Rutland
Cc: James Morse
Cc: Andrey Konovalov
Cc: Christoph Hellwig
There is an inconsistency between down_read_trylock() success and failure
paths while dealing with kernel access for non exception table areas where
it calls __do_kernel_fault(). In case of failure it just bails out without
holding mmap_sem but when it succeeds it does so while holding mmap_sem.
Hi all,
Changes since 20190531:
Reinstated tree: sh
New tree: risc-v-fixes
My fixes tree is empty again.
The crypto tree gained a conflict against Linus' tree.
The net-next tree lost its build failure.
The clockevents tree gained a build failure for which I reverted a commit.
The xarray
As for FOLL_LONGTERM, it is checked in the slow path
__gup_longterm_unlocked(). But it is not checked in the fast path, which
means a possible leak of CMA page to longterm pinned requirement through
this crack.
Place a check in the fast path.
Signed-off-by: Pingfan Liu
Cc: Ira Weiny
Cc: Andrew
To better reflect the held state of pages and make code self-explaining,
rename nr as nr_pinned.
Signed-off-by: Pingfan Liu
Cc: Ira Weiny
Cc: Andrew Morton
Cc: Mike Rapoport
Cc: Dan Williams
Cc: Matthew Wilcox
Cc: John Hubbard
Cc: "Aneesh Kumar K.V"
Cc: Keith Busch
Cc:
The komeda internal resources (pipelines) are shared between crtcs,
and resources release by disable_crtc. This commit is working for once
user forgot disabling crtc like app quit abnomally, and then the
resources can not be used by another crtc. Adds drop_master to
shutdown the device and make
For a long time we used to hard-code CROSS_COMPILE prefix
for ARC until it started to cause problems, so we decided to
solely rely on CROSS_COMPILE externally set by a user:
commit 40660f1fcee8 ("ARC: build: Don't set CROSS_COMPILE in arch's Makefile").
While it works perfectly fine for
> From: Christopherson, Sean J
> Sent: Friday, May 31, 2019 4:32 PM
>
> Do not allow an enclave page to be mapped with PROT_EXEC if the source page
> is backed by a
> file on a noexec file system.
>
> Signed-off-by: Sean Christopherson
> ---
> arch/x86/kernel/cpu/sgx/driver/ioctl.c | 26
> From: Christopherson, Sean J
> Sent: Friday, May 31, 2019 4:32 PM
>
> ...to support (the equivalent) of existing Linux Security Module
> functionality.
>
> Because SGX manually manages EPC memory, all enclave VMAs are backed by the
> same vm_file,
> i.e. /dev/sgx/enclave, so that SGX can
> From: Christopherson, Sean J
> Sent: Friday, May 31, 2019 4:32 PM
>
> To support LSM integration, SGX will require userspace to explicitly specify
> the allowed
> protections for each page. The allowed protections will be supplied to and
> modified by
> LSMs (based on their policies).
> To
> From: Christopherson, Sean J
> Sent: Friday, May 31, 2019 4:32 PM
>
> diff --git a/include/linux/security.h b/include/linux/security.h index
> 659071c2e57c..2f7925eeef7e 100644
> --- a/include/linux/security.h
> +++ b/include/linux/security.h
> @@ -392,6 +392,8 @@ void
1101 - 1200 of 1209 matches
Mail list logo
