Re: [patch] mm, oom: prevent additional oom kills before memory is freed

Michal Hocko wrote: > On Thu 15-06-17 22:01:33, Tetsuo Handa wrote: > > Michal Hocko wrote: > > > On Thu 15-06-17 14:03:35, Michal Hocko wrote: > > > > On Thu 15-06-17 20:32:39, Tetsuo Handa wrote: > > > > > @@ -556,25 +553,21 @@ static void oom_reap_task(struct task_struct > > > > > *tsk) > > >

Re: [patch] mm, oom: prevent additional oom kills before memory is freed

Michal Hocko wrote: > On Thu 15-06-17 22:01:33, Tetsuo Handa wrote: > > Michal Hocko wrote: > > > On Thu 15-06-17 14:03:35, Michal Hocko wrote: > > > > On Thu 15-06-17 20:32:39, Tetsuo Handa wrote: > > > > > @@ -556,25 +553,21 @@ static void oom_reap_task(struct task_struct > > > > > *tsk) > > >

Re: [patch] mm, oom: prevent additional oom kills before memory is freed

On Thu 15-06-17 14:26:26, David Rientjes wrote: > On Thu, 15 Jun 2017, Michal Hocko wrote: > > > > If mm->mm_users is not incremented because it is already zero by the oom > > > reaper, meaning the final refcount has been dropped, do not set > > > MMF_OOM_SKIP prematurely. > > > > > > __mmput()

Re: [patch] mm, oom: prevent additional oom kills before memory is freed

On Thu 15-06-17 14:26:26, David Rientjes wrote: > On Thu, 15 Jun 2017, Michal Hocko wrote: > > > > If mm->mm_users is not incremented because it is already zero by the oom > > > reaper, meaning the final refcount has been dropped, do not set > > > MMF_OOM_SKIP prematurely. > > > > > > __mmput()

Re: [PATCH] reconnect_one(): fix a missing error code

On Thu, Jun 15, 2017 at 07:54:57AM +1000, NeilBrown wrote: > On Wed, Jun 14 2017, J. Bruce Fields wrote: > > > On Wed, Jun 14, 2017 at 12:30:02PM +0300, Dan Carpenter wrote: > >> I found this bug by reviewing places where we do ERR_PTR(0) (which is > >> NULL). > >> > >> We used to return an

Re: [PATCH] reconnect_one(): fix a missing error code

On Thu, Jun 15, 2017 at 07:54:57AM +1000, NeilBrown wrote: > On Wed, Jun 14 2017, J. Bruce Fields wrote: > > > On Wed, Jun 14, 2017 at 12:30:02PM +0300, Dan Carpenter wrote: > >> I found this bug by reviewing places where we do ERR_PTR(0) (which is > >> NULL). > >> > >> We used to return an

Re: [PATCH 2/2] Input: pm8941-pwrkey: Introduce reboot mode support

On Thu, Jun 15, 2017 at 1:33 PM, Bjorn Andersson wrote: > On Thu 15 Jun 09:26 PDT 2017, Sebastian Reichel wrote: > >> Hi, >> >> On Mon, Jun 12, 2017 at 04:32:03PM -0700, Bjorn Andersson wrote: > [..] >> > As such if we split the non-input related handling into another

Re: [PATCH 2/2] Input: pm8941-pwrkey: Introduce reboot mode support

On Thu, Jun 15, 2017 at 1:33 PM, Bjorn Andersson wrote: > On Thu 15 Jun 09:26 PDT 2017, Sebastian Reichel wrote: > >> Hi, >> >> On Mon, Jun 12, 2017 at 04:32:03PM -0700, Bjorn Andersson wrote: > [..] >> > As such if we split the non-input related handling into another driver >> > we would need to

Re: [patch] mm, oom: prevent additional oom kills before memory is freed

On Thu, 15 Jun 2017, Tetsuo Handa wrote: > David is trying to avoid setting MMF_OOM_SKIP when the OOM reaper found that > mm->users == 0. Yes, because MMF_OOM_SKIP enables the oom killer to select another process to kill and will do so without the original victim's mm being able to undergo

Re: [patch] mm, oom: prevent additional oom kills before memory is freed

On Thu, 15 Jun 2017, Tetsuo Handa wrote: > David is trying to avoid setting MMF_OOM_SKIP when the OOM reaper found that > mm->users == 0. Yes, because MMF_OOM_SKIP enables the oom killer to select another process to kill and will do so without the original victim's mm being able to undergo

Re: [PATCH v2] libnvdimm, pmem: Add sysfs notifications to badblocks

On Mon, Jun 12, 2017 at 3:25 PM, Toshi Kani wrote: > Sysfs "badblocks" information may be updated during run-time that: > - MCE, SCI, and sysfs "scrub" may add new bad blocks > - Writes and ioctl() may clear bad blocks > > Add support to send sysfs notifications to sysfs

Re: [PATCH v2] libnvdimm, pmem: Add sysfs notifications to badblocks

On Mon, Jun 12, 2017 at 3:25 PM, Toshi Kani wrote: > Sysfs "badblocks" information may be updated during run-time that: > - MCE, SCI, and sysfs "scrub" may add new bad blocks > - Writes and ioctl() may clear bad blocks > > Add support to send sysfs notifications to sysfs "badblocks" file >

Re: [PATCH] atm: solos-pci: remove useless variable assignments

From: "Gustavo A. R. Silva" Date: Thu, 15 Jun 2017 14:56:21 -0500 > Value assigned to variable _data32_ at lines 1254 and 1257 is > overwritten at line 1260 before it can be used. This makes > such variable assignments useless. > > Addresses-Coverity-ID: 1227049 >

Re: [PATCH] atm: solos-pci: remove useless variable assignments

From: "Gustavo A. R. Silva" Date: Thu, 15 Jun 2017 14:56:21 -0500 > Value assigned to variable _data32_ at lines 1254 and 1257 is > overwritten at line 1260 before it can be used. This makes > such variable assignments useless. > > Addresses-Coverity-ID: 1227049 > Signed-off-by: Gustavo A. R.

Re: [PATCH 3/4] of: Custom printk format specifier for device node

On Wed, Jun 14, 2017 at 01:56:48PM -0700, Joe Perches wrote: > On Wed, 2017-06-14 at 15:30 -0500, Rob Herring wrote: > > From: Pantelis Antoniou > > I think the commit subject is wrong. > It adds an "of" specific bit to vsprintf.c. > The subject should be >

Re: [PATCH 3/4] of: Custom printk format specifier for device node

On Wed, Jun 14, 2017 at 01:56:48PM -0700, Joe Perches wrote: > On Wed, 2017-06-14 at 15:30 -0500, Rob Herring wrote: > > From: Pantelis Antoniou > > I think the commit subject is wrong. > It adds an "of" specific bit to vsprintf.c. > The subject should be > 'vsprintf:  Add %p extension "%pO" for

Re: [patch] mm, oom: prevent additional oom kills before memory is freed

On Thu, 15 Jun 2017, Michal Hocko wrote: > > If mm->mm_users is not incremented because it is already zero by the oom > > reaper, meaning the final refcount has been dropped, do not set > > MMF_OOM_SKIP prematurely. > > > > __mmput() may not have had a chance to do exit_mmap() yet, so memory

Re: [patch] mm, oom: prevent additional oom kills before memory is freed

On Thu, 15 Jun 2017, Michal Hocko wrote: > > If mm->mm_users is not incremented because it is already zero by the oom > > reaper, meaning the final refcount has been dropped, do not set > > MMF_OOM_SKIP prematurely. > > > > __mmput() may not have had a chance to do exit_mmap() yet, so memory

Re: [PATCH net-next] net: dsa: assign default CPU port to all ports

From: Vivien Didelot Date: Thu, 15 Jun 2017 15:06:54 -0400 > The current code only assigns the default cpu_dp to all user ports of > the switch to which the CPU port belongs. The user ports of the other > switches of the fabric thus don't have a default CPU

Re: [PATCH net-next] net: dsa: assign default CPU port to all ports

From: Vivien Didelot Date: Thu, 15 Jun 2017 15:06:54 -0400 > The current code only assigns the default cpu_dp to all user ports of > the switch to which the CPU port belongs. The user ports of the other > switches of the fabric thus don't have a default CPU port. > > This patch fixes this by

Re: [PATCH] PCI: mediatek: fix error handling in mtk_pcie_parse_and_add_res()

On Mon, Jun 05, 2017 at 02:27:58PM +0800, Ryder Lee wrote: > The 'linkup' variable would always increment by one whether the link > status is true or not. Therefore, this patch fixes the return value in > mtk_pcie_parse_and_add_res() and removes unnecessary 'linkup' variable. > > Signed-off-by:

Re: [PATCH] PCI: mediatek: fix error handling in mtk_pcie_parse_and_add_res()

On Mon, Jun 05, 2017 at 02:27:58PM +0800, Ryder Lee wrote: > The 'linkup' variable would always increment by one whether the link > status is true or not. Therefore, this patch fixes the return value in > mtk_pcie_parse_and_add_res() and removes unnecessary 'linkup' variable. > > Signed-off-by:

Re: [Intel-wired-lan] [PATCH] intel: i40e: virtchnl: fix incorrect variable assignment

Hi Jesse, Quoting Jesse Brandeburg : On Wed, 14 Jun 2017 21:38:26 -0500 "Gustavo A. R. Silva" wrote: Fix incorrect variable assignment. Based on line 1511: aq_ret = I40_ERR_PARAM; the correct variable to be used in this instance is aq_ret

Re: [Intel-wired-lan] [PATCH] intel: i40e: virtchnl: fix incorrect variable assignment

Hi Jesse, Quoting Jesse Brandeburg : On Wed, 14 Jun 2017 21:38:26 -0500 "Gustavo A. R. Silva" wrote: Fix incorrect variable assignment. Based on line 1511: aq_ret = I40_ERR_PARAM; the correct variable to be used in this instance is aq_ret instead of ret. Also, variable ret is updated at

Re: [PATCH] PCI: imx6: add regulator support

On Thu, Jun 08, 2017 at 10:07:42AM +0200, Quentin Schulz wrote: > Some boards might require to control a regulator to power the PCIe port. > > This adds support for an optional regulator defined in Device Tree > linked in the PCIe controller under `vpcie-supply`. If present, the > regulator will

Re: [PATCH] PCI: imx6: add regulator support

On Thu, Jun 08, 2017 at 10:07:42AM +0200, Quentin Schulz wrote: > Some boards might require to control a regulator to power the PCIe port. > > This adds support for an optional regulator defined in Device Tree > linked in the PCIe controller under `vpcie-supply`. If present, the > regulator will

Re: [PATCH] mm/list_lru.c: use cond_resched_lock() for nlru->lock

On Mon, 12 Jun 2017 06:17:20 +0530 Sahitya Tummala wrote: > __list_lru_walk_one() can hold the spin lock for longer duration > if there are more number of entries to be isolated. > > This results in "BUG: spinlock lockup suspected" in the below path - > > []

Re: [PATCH] mm/list_lru.c: use cond_resched_lock() for nlru->lock

On Mon, 12 Jun 2017 06:17:20 +0530 Sahitya Tummala wrote: > __list_lru_walk_one() can hold the spin lock for longer duration > if there are more number of entries to be isolated. > > This results in "BUG: spinlock lockup suspected" in the below path - > > [] spin_bug+0x90 > []

Re: [PATCH] acpi: acpica: fix acpi parse and parseext cache leaks

Hello, Robert. My research system are based on virtual machine and Intel NUC machine, and they are still working despite of ACPI subsystem shutdown. So, I can find the acpi memory leaks by using "dmesg" command. Best regards. 2017-06-16 4:52 GMT+09:00 Moore, Robert : >

Re: [PATCH] acpi: acpica: fix acpi parse and parseext cache leaks

Hello, Robert. My research system are based on virtual machine and Intel NUC machine, and they are still working despite of ACPI subsystem shutdown. So, I can find the acpi memory leaks by using "dmesg" command. Best regards. 2017-06-16 4:52 GMT+09:00 Moore, Robert : > This might be a dumb

Re: [PATCH 2/2] c6x: remove unused KTHREAD_SIZE definition

On Mon, 2017-06-12 at 13:09 -0400, Jérémy Lefaure wrote: > KTHREAD_SIZE has never been used since it has been defined for c6x arch. > Let's remove this useless definition. > > Signed-off-by: Jérémy Lefaure > --- >  arch/c6x/kernel/asm-offsets.c | 1 - >  1 file

Re: [PATCH 2/2] c6x: remove unused KTHREAD_SIZE definition

On Mon, 2017-06-12 at 13:09 -0400, Jérémy Lefaure wrote: > KTHREAD_SIZE has never been used since it has been defined for c6x arch. > Let's remove this useless definition. > > Signed-off-by: Jérémy Lefaure > --- >  arch/c6x/kernel/asm-offsets.c | 1 - >  1 file changed, 1 deletion(-) > > diff

Re: [PATCH v1 1/1] gpio: gpio-wcove: Fix GPIO control register offset calculation

Hi Andy, On 06/15/2017 02:06 AM, Andy Shevchenko wrote: On Thu, Jun 15, 2017 at 12:39 AM, wrote: From: Kuppuswamy Sathyanarayanan According to Whiskey Cove PMIC GPIO controller specification, for GPIO

Re: [PATCH v1 1/1] gpio: gpio-wcove: Fix GPIO control register offset calculation

Hi Andy, On 06/15/2017 02:06 AM, Andy Shevchenko wrote: On Thu, Jun 15, 2017 at 12:39 AM, wrote: From: Kuppuswamy Sathyanarayanan According to Whiskey Cove PMIC GPIO controller specification, for GPIO pins 0-12, GPIO input and output register control address range from, 0x4e44-0x4e50 for

Re: [PATCH] clockevents/tcb_clksrc: implement suspend/resume

On 15/06/2017 21:40, Alexandre Belloni wrote: > On 14/04/2017 at 21:13:36 +0200, Daniel Lezcano wrote: >>> +void tc_clksrc_resume(struct clocksource *cs) >>> +{ >>> + int i; >>> + >>> + for (i = 0; i < 3; i++) { >> >> s/3/ARRAY_SIZE(tcb_cache)/ >> >>> + __raw_writel(tcb_cache[i].cmr,

Re: [PATCH] clockevents/tcb_clksrc: implement suspend/resume

On 15/06/2017 21:40, Alexandre Belloni wrote: > On 14/04/2017 at 21:13:36 +0200, Daniel Lezcano wrote: >>> +void tc_clksrc_resume(struct clocksource *cs) >>> +{ >>> + int i; >>> + >>> + for (i = 0; i < 3; i++) { >> >> s/3/ARRAY_SIZE(tcb_cache)/ >> >>> + __raw_writel(tcb_cache[i].cmr,

Re: [PATCH v3] misc: sram-exec: Use aligned fncpy instead of memcpy

On 05/18/2017 08:07 AM, Dave Gerlach wrote: > Currently the sram-exec functionality, which allows allocation of > executable memory and provides an API to move code to it, is only > selected in configs for the ARM architecture. Based on commit > 5756e9dd0de6 ("ARM: 6640/1: Thumb-2: Symbol

Re: [PATCH v3] misc: sram-exec: Use aligned fncpy instead of memcpy

On 05/18/2017 08:07 AM, Dave Gerlach wrote: > Currently the sram-exec functionality, which allows allocation of > executable memory and provides an API to move code to it, is only > selected in configs for the ARM architecture. Based on commit > 5756e9dd0de6 ("ARM: 6640/1: Thumb-2: Symbol

Re: [Intel-wired-lan] [PATCH] intel: i40e: virtchnl: fix incorrect variable assignment

On Wed, 14 Jun 2017 21:38:26 -0500 "Gustavo A. R. Silva" wrote: > Fix incorrect variable assignment. > Based on line 1511: aq_ret = I40_ERR_PARAM; the correct variable to be > used in this instance is aq_ret instead of ret. Also, variable ret is > updated at line 1602

Re: [Intel-wired-lan] [PATCH] intel: i40e: virtchnl: fix incorrect variable assignment

On Wed, 14 Jun 2017 21:38:26 -0500 "Gustavo A. R. Silva" wrote: > Fix incorrect variable assignment. > Based on line 1511: aq_ret = I40_ERR_PARAM; the correct variable to be > used in this instance is aq_ret instead of ret. Also, variable ret is > updated at line 1602 just before return, so

Re: [PATCH v3] PCI: dwc: dra7xx: Fix compilation warning.

On Thu, Jun 15, 2017 at 02:19:20PM +0530, Arvind Yadav wrote: > drivers/pci/dwc/pci-dra7xx.c: In function ‘dra7xx_pcie_enable_msi_interrupts’: > drivers/pci/dwc/pci-dra7xx.c:177:7: warning: large integer implicitly > truncated to unsigned type [-Woverflow] >~LEG_EP_INTERRUPTS & ~MSI); >

Re: [PATCH v3] PCI: dwc: dra7xx: Fix compilation warning.

On Thu, Jun 15, 2017 at 02:19:20PM +0530, Arvind Yadav wrote: > drivers/pci/dwc/pci-dra7xx.c: In function ‘dra7xx_pcie_enable_msi_interrupts’: > drivers/pci/dwc/pci-dra7xx.c:177:7: warning: large integer implicitly > truncated to unsigned type [-Woverflow] >~LEG_EP_INTERRUPTS & ~MSI); >

RE

Greetings, We are contracted probate researchers. This is an investigation about a client with whom you share the same surname, your assistance will be greatly appreciated.Please clarify if you have any relative whose last known contact address was Monte-Carlo, Monaco? Are you aware of

RE

Greetings, We are contracted probate researchers. This is an investigation about a client with whom you share the same surname, your assistance will be greatly appreciated.Please clarify if you have any relative whose last known contact address was Monte-Carlo, Monaco? Are you aware of

Re: [PATCH v4] fscrypt: Add support for AES-128-CBC

On Thu, Jun 15, 2017 at 01:41:29PM -0700, Michael Halcrow wrote: > > static int validate_user_key(struct fscrypt_info *crypt_info, > > struct fscrypt_context *ctx, u8 *raw_key, > > - const char *prefix) > > + const char *prefix, int

Re: [PATCH v4] fscrypt: Add support for AES-128-CBC

On Thu, Jun 15, 2017 at 01:41:29PM -0700, Michael Halcrow wrote: > > static int validate_user_key(struct fscrypt_info *crypt_info, > > struct fscrypt_context *ctx, u8 *raw_key, > > - const char *prefix) > > + const char *prefix, int

Re: [PATCH] drm/core: Fail atomic IOCTL with no CRTC state but with signaling.

Just a reminder. Thanks. On 06/09/2017 05:30 PM, Andrey Grodzovsky wrote: Problem: While running IGT kms_atomic_transition test suite i encountered a hang in drmHandleEvent immidietly follwoing an atomic_commit. After dumping the atomic state I relized that in this case there was not even one

Re: [PATCH] drm/core: Fail atomic IOCTL with no CRTC state but with signaling.

Just a reminder. Thanks. On 06/09/2017 05:30 PM, Andrey Grodzovsky wrote: Problem: While running IGT kms_atomic_transition test suite i encountered a hang in drmHandleEvent immidietly follwoing an atomic_commit. After dumping the atomic state I relized that in this case there was not even one

[PATCH] af9013: add check on af9013_wr_regs() return value

Check return value from call to af9013_wr_regs(), so in case of error print debug message and return. Addresses-Coverity-ID: 1227035 Signed-off-by: Gustavo A. R. Silva --- drivers/media/dvb-frontends/af9013.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH] af9013: add check on af9013_wr_regs() return value

Check return value from call to af9013_wr_regs(), so in case of error print debug message and return. Addresses-Coverity-ID: 1227035 Signed-off-by: Gustavo A. R. Silva --- drivers/media/dvb-frontends/af9013.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 6/7] drm/panel: Add support for the Raspberry Pi 7" Touchscreen.

This driver communicates with the Atmel microcontroller for sequencing the poweron of the TC358762 DSI-DPI bridge and controlling the backlight PWM. v2: Set the same default orientation as the closed source firmware used, which is the best for viewing angle. v3: Rewrite as an i2c client

[PATCH 0/7] RPi touchscreen as a panel driver again

After splitting the panel driver out into a panel and bridge due to panel review, the feedback from bridge maintainers was that it didn't make sense as a bridge. I completely agree with them. This series returns the driver to being a panel, but this time probing as an i2c client rather than a

[PATCH 6/7] drm/panel: Add support for the Raspberry Pi 7" Touchscreen.

This driver communicates with the Atmel microcontroller for sequencing the poweron of the TC358762 DSI-DPI bridge and controlling the backlight PWM. v2: Set the same default orientation as the closed source firmware used, which is the best for viewing angle. v3: Rewrite as an i2c client

[PATCH 0/7] RPi touchscreen as a panel driver again

After splitting the panel driver out into a panel and bridge due to panel review, the feedback from bridge maintainers was that it didn't make sense as a bridge. I completely agree with them. This series returns the driver to being a panel, but this time probing as an i2c client rather than a

[PATCH 2/7] drm/vc4: Fix DSI T_INIT timing.

The DPHY spec requires a much larger T_INIT than I was specifying before. In the absence of clear specs from the slave of what their timing is, just use the value that the firmware was using. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_dsi.c | 12 +++- 1

[PATCH 2/7] drm/vc4: Fix DSI T_INIT timing.

The DPHY spec requires a much larger T_INIT than I was specifying before. In the absence of clear specs from the slave of what their timing is, just use the value that the firmware was using. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_dsi.c | 12 +++- 1 file changed, 11

Re: [PATCH v4] fscrypt: Add support for AES-128-CBC

On Tue, May 23, 2017 at 07:11:20AM +0200, David Gstir wrote: > From: Daniel Walter > > fscrypt provides facilities to use different encryption algorithms which > are selectable by userspace when setting the encryption policy. Currently, > only AES-256-XTS for file contents

Re: [PATCH v4] fscrypt: Add support for AES-128-CBC

On Tue, May 23, 2017 at 07:11:20AM +0200, David Gstir wrote: > From: Daniel Walter > > fscrypt provides facilities to use different encryption algorithms which > are selectable by userspace when setting the encryption policy. Currently, > only AES-256-XTS for file contents and AES-256-CBC-CTS

[PATCH 1/7] drm/bridge: Support hotplugging panel-bridge.

If the panel-bridge is being set up after the drm_mode_config_reset(), then the connector's state would never get initialized, and we'd dereference the NULL in the hotplug path. We also need to register the connector, so that userspace can get at it. Signed-off-by: Eric Anholt

[PATCH 1/7] drm/bridge: Support hotplugging panel-bridge.

If the panel-bridge is being set up after the drm_mode_config_reset(), then the connector's state would never get initialized, and we'd dereference the NULL in the hotplug path. We also need to register the connector, so that userspace can get at it. Signed-off-by: Eric Anholt ---

[PATCH 4/7] drm/vc4: Use drm_mode_vrefresh() in DSI fixup, in case vrefresh is 0.

I'm not sure what changed where I started getting vrefresh=0 from the mode to be fixed up. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_dsi.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/vc4/vc4_dsi.c

[PATCH 3/7] drm/vc4: Fix misleading name of the continuous flag.

The logic was all right in the end, the name was just backwards. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_dsi.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/vc4/vc4_dsi.c b/drivers/gpu/drm/vc4/vc4_dsi.c index

[PATCH 7/7] ARM: dts: bcm2835: Enable the Raspberry Pi touchscreen panel.

This commit is not intended to be merged. Instead we will use overlays to enable the panel, and this commit is just a demo of how things get wired up. Signed-off-by: Eric Anholt --- arch/arm/boot/dts/bcm2835-rpi-b-plus.dts | 5

[PATCH 5/7] dt-bindings: Document the Raspberry Pi Touchscreen nodes.

This doesn't yet cover input, but the driver does get the display working when the firmware is disabled from talking to our I2C lines. Signed-off-by: Eric Anholt --- .../panel/raspberrypi,7inch-touchscreen.txt| 49 ++ 1 file changed, 49 insertions(+)

[PATCH 4/7] drm/vc4: Use drm_mode_vrefresh() in DSI fixup, in case vrefresh is 0.

I'm not sure what changed where I started getting vrefresh=0 from the mode to be fixed up. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_dsi.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/vc4/vc4_dsi.c b/drivers/gpu/drm/vc4/vc4_dsi.c index

[PATCH 3/7] drm/vc4: Fix misleading name of the continuous flag.

The logic was all right in the end, the name was just backwards. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_dsi.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/vc4/vc4_dsi.c b/drivers/gpu/drm/vc4/vc4_dsi.c index

[PATCH 7/7] ARM: dts: bcm2835: Enable the Raspberry Pi touchscreen panel.

This commit is not intended to be merged. Instead we will use overlays to enable the panel, and this commit is just a demo of how things get wired up. Signed-off-by: Eric Anholt --- arch/arm/boot/dts/bcm2835-rpi-b-plus.dts | 5 arch/arm/boot/dts/bcm2835-rpi-b-rev2.dts |

[PATCH 5/7] dt-bindings: Document the Raspberry Pi Touchscreen nodes.

This doesn't yet cover input, but the driver does get the display working when the firmware is disabled from talking to our I2C lines. Signed-off-by: Eric Anholt --- .../panel/raspberrypi,7inch-touchscreen.txt| 49 ++ 1 file changed, 49 insertions(+) create mode

[RFC PATCH 08/13] switchtec_ntb: add skeleton ntb driver

This patch simply adds a skeleton NTB driver which will be filled out in subsequent patches. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates Reviewed-by: Kurt Schwemmer --- drivers/ntb/hw/mscc/switchtec_ntb.c |

[RFC PATCH 09/13] switchtec_ntb: add link management

switchtec_ntb checks for a link by looking at the shared memory window. If the magic number is correct and the otherside indicates their link is enabled then we take the link to be up. Whenever we change our local link status we send a msg to the otherside to check whether it's up and change

[RFC PATCH 08/13] switchtec_ntb: add skeleton ntb driver

This patch simply adds a skeleton NTB driver which will be filled out in subsequent patches. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates Reviewed-by: Kurt Schwemmer --- drivers/ntb/hw/mscc/switchtec_ntb.c | 134 +++- include/linux/ntb.h

[RFC PATCH 09/13] switchtec_ntb: add link management

switchtec_ntb checks for a link by looking at the shared memory window. If the magic number is correct and the otherside indicates their link is enabled then we take the link to be up. Whenever we change our local link status we send a msg to the otherside to check whether it's up and change

[RFC PATCH 05/13] switchtec_ntb: introduce initial ntb driver

Seeing the switchtec NTB hardware shares the same endpoint as the management endpoint we utilize the class_interface api to register an NTB driver for every switchtec device in the system that has the NTB class code. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates

[RFC PATCH 02/13] switchtec: export class symbol for use in upper layer driver

We switch to class_register/unregister and a declared class which is exported for use in the switchtec_ntb driver. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates Reviewed-by: Kurt Schwemmer ---

[RFC PATCH 05/13] switchtec_ntb: introduce initial ntb driver

Seeing the switchtec NTB hardware shares the same endpoint as the management endpoint we utilize the class_interface api to register an NTB driver for every switchtec device in the system that has the NTB class code. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates Reviewed-by: Kurt

[RFC PATCH 02/13] switchtec: export class symbol for use in upper layer driver

We switch to class_register/unregister and a declared class which is exported for use in the switchtec_ntb driver. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates Reviewed-by: Kurt Schwemmer --- drivers/pci/switch/switchtec.c | 21 +++-- include/linux/switchtec.h

[RFC PATCH 01/13] switchtec: move structure definitions into a common header

Create the switchtec.h header in include/linux with hardware defines and the switchtec_dev structure moved directly from switchtec.c. This is a prep patch for created an NTB driver for switchtec. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates

[RFC PATCH 01/13] switchtec: move structure definitions into a common header

Create the switchtec.h header in include/linux with hardware defines and the switchtec_dev structure moved directly from switchtec.c. This is a prep patch for created an NTB driver for switchtec. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates Reviewed-by: Kurt Schwemmer ---

[RFC PATCH 13/13] switchtec_ntb: update switchtec documentation with notes for ntb

The switchtec_ntb driver has a couple requirements on the switchec's hardware configuration so we add these notes to the documentation. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates Reviewed-by: Kurt Schwemmer

[RFC PATCH 06/13] switchtec_ntb: initialize hardware for memory windows

This commit adds the code to initialize the memory windows in the hardware. This includes setting up the requester ID table, and figuring out which bar corresponds to which memory window. (Seeing the switch can be configured with any number of bars.) Also, seeing the device doesn't have hardware

[RFC PATCH 06/13] switchtec_ntb: initialize hardware for memory windows

This commit adds the code to initialize the memory windows in the hardware. This includes setting up the requester ID table, and figuring out which bar corresponds to which memory window. (Seeing the switch can be configured with any number of bars.) Also, seeing the device doesn't have hardware

[RFC PATCH 13/13] switchtec_ntb: update switchtec documentation with notes for ntb

The switchtec_ntb driver has a couple requirements on the switchec's hardware configuration so we add these notes to the documentation. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates Reviewed-by: Kurt Schwemmer --- Documentation/switchtec.txt | 12 1 file changed, 12

[RFC PATCH 10/13] switchtec_ntb: implement doorbell registers

Pretty straightforward implementation of doorbell registers. The shift and mask were setup in an earlier patch and this just hooks up the approprirate portion of the idb register as the local doorbells and the opposite portion of odb as the peer doorbells. The db mask is protected by a spinlock to

[RFC PATCH 10/13] switchtec_ntb: implement doorbell registers

Pretty straightforward implementation of doorbell registers. The shift and mask were setup in an earlier patch and this just hooks up the approprirate portion of the idb register as the local doorbells and the opposite portion of odb as the peer doorbells. The db mask is protected by a spinlock to

[RFC PATCH 11/13] switchtec_ntb: implement scratchpad registers

Seeing there is no dedicated hardware for this, we simply add these as entries in the shared memory window. Thus, we could support any number of them but 128 seems like enough, for now. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates

[RFC PATCH 12/13] switchtec_ntb: add memory window support

The switchtec hardware has two types of memory windows: LUTs and Direct. The first area in each BAR is for LUT windows and the remaining area is for the direct region. The total number of LUT entries is set by a configuration setting in hardware and they all must be the same size. (This is fixed

[RFC PATCH 11/13] switchtec_ntb: implement scratchpad registers

Seeing there is no dedicated hardware for this, we simply add these as entries in the shared memory window. Thus, we could support any number of them but 128 seems like enough, for now. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates Reviewed-by: Kurt Schwemmer ---

[RFC PATCH 12/13] switchtec_ntb: add memory window support

The switchtec hardware has two types of memory windows: LUTs and Direct. The first area in each BAR is for LUT windows and the remaining area is for the direct region. The total number of LUT entries is set by a configuration setting in hardware and they all must be the same size. (This is fixed

[RFC PATCH 04/13] switchtec: add link event notifier block

In order for the switchtec NTB code to handle link change events we create a notifier block in the switchtec code which gets called whenever an appropriate event interrupt occurs. In order to preserve userspace's ability to follow these events, we compare the event count with a stored copy from

[RFC PATCH 04/13] switchtec: add link event notifier block

In order for the switchtec NTB code to handle link change events we create a notifier block in the switchtec code which gets called whenever an appropriate event interrupt occurs. In order to preserve userspace's ability to follow these events, we compare the event count with a stored copy from

Re: [PATCH v9 5/7] vfio: Define vfio based dma-buf operations

On Thu, 15 Jun 2017 18:00:38 +0200 Gerd Hoffmann wrote: > Hi, > > > > +struct vfio_dmabuf_mgr_plane_info { > > > + __u64 start; > > > + __u64 drm_format_mod; > > > + __u32 drm_format; > > > + __u32 width; > > > + __u32 height; > > > + __u32 stride; > > > + __u32 size; > > >

Re: [PATCH v9 5/7] vfio: Define vfio based dma-buf operations

On Thu, 15 Jun 2017 18:00:38 +0200 Gerd Hoffmann wrote: > Hi, > > > > +struct vfio_dmabuf_mgr_plane_info { > > > + __u64 start; > > > + __u64 drm_format_mod; > > > + __u32 drm_format; > > > + __u32 width; > > > + __u32 height; > > > + __u32 stride; > > > + __u32 size; > > > + __u32 x_pos; > >

[RFC PATCH 00/13] Switchtec NTB Support

Hi, This patchset implements Non-Transparent Bridge (NTB) support for the Microsemi Switchtec series of switches. We're looking for some review from the community at this point but hope to get it upstreamed for v4.14. Switchtec NTB support is configured over the same function and bar as the

[RFC PATCH 00/13] Switchtec NTB Support

Hi, This patchset implements Non-Transparent Bridge (NTB) support for the Microsemi Switchtec series of switches. We're looking for some review from the community at this point but hope to get it upstreamed for v4.14. Switchtec NTB support is configured over the same function and bar as the

Re: [PATCH 1/2] perf report: ensure the perf DSO mapping matches what libdw sees

On Mon, 05 Jun 2017 12:41:30 +0200, Jiri Olsa wrote: > On Fri, Jun 02, 2017 at 04:37:52PM +0200, Milian Wolff wrote: > > Debug output showed me that libdw found a module for the last frame > > address, but it thinks it belongs to /usr/lib/ld-2.25.so. I find your patch as a correct workaround of

[RFC PATCH 07/13] switchtec_ntb: initialize hardware for doorbells and messages

This patch sets up some hardware registers and creates interrupt service routines for the doorbells and messages. There are 64 doorbells in the switch that are shared between all partitions. The upper 4 doorbells are also shared with the messages and are there for not used. Thus, this code

[RFC PATCH 03/13] switchtec: add ntb hardware register definitions

There are two additional regions: ctrl and dbmsg. The first is for generic ntb control and memory windows. The second for doorbells and message registers. This patch also adds a number of related constants for using these registers. Signed-off-by: Logan Gunthorpe

[RFC PATCH 07/13] switchtec_ntb: initialize hardware for doorbells and messages

This patch sets up some hardware registers and creates interrupt service routines for the doorbells and messages. There are 64 doorbells in the switch that are shared between all partitions. The upper 4 doorbells are also shared with the messages and are there for not used. Thus, this code

[RFC PATCH 03/13] switchtec: add ntb hardware register definitions

There are two additional regions: ctrl and dbmsg. The first is for generic ntb control and memory windows. The second for doorbells and message registers. This patch also adds a number of related constants for using these registers. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates

Re: [PATCH 1/2] perf report: ensure the perf DSO mapping matches what libdw sees

On Mon, 05 Jun 2017 12:41:30 +0200, Jiri Olsa wrote: > On Fri, Jun 02, 2017 at 04:37:52PM +0200, Milian Wolff wrote: > > Debug output showed me that libdw found a module for the last frame > > address, but it thinks it belongs to /usr/lib/ld-2.25.so. I find your patch as a correct workaround of

<    1   2   3   4   5   6   7   8   9   10   >