This checks and rejects any dma map request outside valid iova
range.
Signed-off-by: Shameer Kolothum
---
drivers/vfio/vfio_iommu_type1.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
index
Get a copy of iova list on _group_detach and try to update the list.
On success replace the current one with the copy. Leave the list as
it is if update fails.
Signed-off-by: Shameer Kolothum
---
drivers/vfio/vfio_iommu_type1.c | 91 +
1 file changed, 91
This series introduces an iova list associated with a vfio
iommu. The list is kept updated taking care of iommu apertures,
and reserved regions. Also this series adds checks for any conflict
with existing dma mappings whenever a new device group is attached to
the domain.
User-space can retrieve
This pretty much reverts commit 273df9635385 ("iommu/dma: Make PCI
window reservation generic") by moving the PCI window region
reservation back into the dma specific path so that these regions
doesn't get exposed via the IOMMU API interface. With this change,
the vfio interface will report only
This introduces an iova list that is valid for dma mappings. Make
sure the new iommu aperture window doesn't conflict with the current
one or with any existing dma mappings during attach.
Signed-off-by: Shameer Kolothum
---
drivers/vfio/vfio_iommu_type1.c | 183
Javier
> On 17 Apr 2018, at 05.12, Matias Bjørling wrote:
>
> On 4/16/18 12:25 PM, Javier González wrote:
>> Remove unnecessary argument on pblk_line_free()
>
> Why was the argument no longer needed?
You can see it is not used... It a straightforward clean up.
Javier
signature.asc
On Thursday 08 March 2018 23:53:30 Pali Rohár wrote:
> On Monday 26 February 2018 21:32:55 Wolfram Sang wrote:
> >
> > > I'm not maintainer of i2c-i801.ko, Jean Delvare & Wolfram Sang are.
> > > Therefore instructing future contributors would be up to them.
> >
> > This is really Jean's realm.
>
From: Colin Ian King
Rename several macros that contain mispellings of UNKNOWN
Signed-off-by: Colin Ian King
---
drivers/net/wireless/ralink/rt2x00/rt2800.h | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/net/wireless/ralink/rt2x00/rt2800.h
Michal Hocko wrote:
> On Tue 17-04-18 19:52:41, David Rientjes wrote:
> > Since exit_mmap() is done without the protection of mm->mmap_sem, it is
> > possible for the oom reaper to concurrently operate on an mm until
> > MMF_OOM_SKIP is set.
> >
> > This allows munlock_vma_pages_all() to
> On 17 Apr 2018, at 05.03, Matias Bjørling wrote:
>
> On 4/16/18 12:25 PM, Javier González wrote:
>> Check that the lba stored in the LBA metadata is correct in the GC path
>> too. This requires a new helper function to check random reads in the
>> vector read.
>> Signed-off-by: Javier González
We had commit 06e226c7fb23 ("clk: sunxi-ng: Move all clock types to a
library") and commit 799c43415442 ("kbuild: thin archives make default
for all archs") in the same development cycle, from different trees.
With migration to the thin archive, the entire drivers/clk/sunxi-ng/lib.a
is linked to
On Wed 18-04-18 20:43:11, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > > Don't complain if IS_ERR_VALUE(),
> >
> > this is simply wrong. We do want to warn on the failure because this is
> > when the actual clash happens. We should just warn on EEXIST.
>
> >From
On Wed, Apr 18, 2018 at 12:47:50PM +0100, Colin King wrote:
> From: Colin Ian King
>
> Rename several macros that contain mispellings of UNKNOWN
>
> Signed-off-by: Colin Ian King
Acked-by: Stanislaw Gruszka
On 15/04/2018 23:22, Tony Krowiak wrote:
Registers a group notifier during the open of the mediated
matrix device to get information on KVM presence through the
VFIO_GROUP_NOTIFY_SET_KVM event. When notified, the pointer
to the kvm structure is saved inside the mediated matrix
device. Once the
> On 17 Apr 2018, at 04.48, Matias Bjørling wrote:
>
> On 4/16/18 12:21 PM, Javier González wrote:
>> Allocate line bitmaps outside of the line lock on line preparation.
>> Signed-off-by: Javier González
>
>
> The patch description tells what the patch does, it should tell why
> the change
On Wed 18-04-18 20:49:11, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > On Tue 17-04-18 19:52:41, David Rientjes wrote:
> > > Since exit_mmap() is done without the protection of mm->mmap_sem, it is
> > > possible for the oom reaper to concurrently operate on an mm until
> > > MMF_OOM_SKIP is set.
The patch
regulator: pfuze100: update voltage setting for pfuze3000 sw1a
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
pblk allocates line bitmaps within the line lock unnecessarily. In order
to take pressure out of the fast patch, allocate line bitmaps outside
of this lock and refactor accordingly.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-core.c | 97 +---
Changes since V1 - from Matias:
- rename a function to line__reinit
- propagate error code
- improve commit message
Javier González (1):
lightnvm: pblk: take bitmap alloc. out of critical section
drivers/lightnvm/pblk-core.c | 97 +---
1 file
On Wed, Apr 18, 2018 at 12:07:21PM +0200, Borislav Petkov wrote:
> On Wed, Apr 18, 2018 at 10:11:40AM +0200, Vitezslav Samel wrote:
> > Could be done anything to prevent this panic?
>
> Yes, for starters, is there anything preventing you from using an initrd
> and doing early microcode loading?
> On 17 Apr 2018, at 05.11, Matias Bjørling wrote:
>
> On 4/16/18 12:25 PM, Javier González wrote:
>> Remove unnecessary indirection on the read path.
>
> Title and description are the same. Can you elaborate what changed
> since pblk_submit_io now directly can be returned, and doesn't have
>
From: Michal Hocko
Li Wang has reported that LTP move_pages04 test fails with the current
tree:
LTP move_pages04:
TFAIL : move_pages04.c:143: status[1] is EPERM, expected EFAULT
The test allocates an array of two pages, one is present while the other
is not (resp. backed by zero page) and
On 18/04/18 12:41, Alban wrote:
On Tue, 17 Apr 2018 18:00:40 +0200
Alban wrote:
On Tue, 17 Apr 2018 16:44:01 +0100
Srinivas Kandagatla wrote:
Thanks for explaining,
On 17/04/18 15:54, Alban wrote:
This will not only allow reading the calibration data from nvmem, but
will also create a
Hi Quentin,
On Fri, Apr 06, 2018 at 04:36:05PM +0100, Dietmar Eggemann wrote:
> From: Quentin Perret
>
> In preparation for the definition of an energy-aware wakeup path, a
> helper function is provided to estimate the consequence on system energy
> when a specific task wakes-up on a specific
+ Rafael.
On Mon, Apr 16, 2018 at 08:39:37AM -0700, Dave Hansen wrote:
> On 04/16/2018 08:16 AM, Andy Lutomirski wrote:
> > On Mon, Apr 16, 2018 at 2:43 AM, Joerg Roedel wrote:
> >> From: Joerg Roedel
> >>
> >> The |= operator will let us end up with an invalid PTE. Use
> >> the correct &=
On Wed, Apr 18, 2018 at 02:08:40PM +0200, Vitezslav Samel wrote:
> I switched to firmware-in-kernel early loading and that works OK.
Ok, and keep using that from now on.
People should all move away from that late loading dance. I'm saying
that in case someone else reads this on lkml.
> But
Hi Dave,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.17-rc1 next-20180418]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On Wed, Apr 18, 2018 at 09:38:47AM +, Vicenţiu Galanopulo wrote:
>
>
> > > Having dev-addr stored in devices_addrs, in get_phy_c45_ids(), when
> > > probing the identifiers, dev-addr can be extracted from devices_addrs
> > > and probed if devices_addrs[current_identifier] is not 0.
> >
> >
We have a new mailing list, so update the MAINTAINERS file.
Signed-off-by: Richard Weinberger
---
MAINTAINERS | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index b60179d948bb..4834d1551248 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14768,8
On Wednesday, April 04/18/18, 2018 at 11:45:46 +0530, Dave Young wrote:
> Hi Rahul,
> On 04/17/18 at 01:14pm, Rahul Lakkireddy wrote:
> > On production servers running variety of workloads over time, kernel
> > panic can happen sporadically after days or even months. It is
> > important to collect
On Wed, 18 Apr 2018 13:12:48 +0100
Srinivas Kandagatla wrote:
> On 18/04/18 12:41, Alban wrote:
> > On Tue, 17 Apr 2018 18:00:40 +0200
> > Alban wrote:
> >
> >> On Tue, 17 Apr 2018 16:44:01 +0100
> >> Srinivas Kandagatla wrote:
> >>
> >>> Thanks for explaining,
> >>>
> >>> On 17/04/18
On 18.03.2018 17:12, Borislav Petkov wrote:
> On Fri, Mar 16, 2018 at 12:07:42AM +0100, Maciej S. Szmigiero wrote:
>> verify_patch_size() function verifies whether the microcode container file
>> remaining size is large enough to contain a patch of the indicated size.
>>
>> However, the section
On 04/18/2018 11:35 AM, Jonathan Cameron wrote:
> On Tue, 17 Apr 2018 12:19:06 -0700
> Dmitry Torokhov wrote:
>
>> Hi Eugen,
>>
>> On Tue, Apr 17, 2018 at 10:39:24AM +0300, Eugen Hristev wrote:
>>>
>>>
>>> On 17.04.2018 02:58, Dmitry Torokhov wrote:
On Sun, Apr 15, 2018 at 08:33:21PM
On 04/18/2018 01:55 PM, Roger Pau Monné wrote:
On Wed, Apr 18, 2018 at 01:39:35PM +0300, Oleksandr Andrushchenko wrote:
On 04/18/2018 01:18 PM, Paul Durrant wrote:
-Original Message-
From: Xen-devel [mailto:xen-devel-boun...@lists.xenproject.org] On Behalf
Of Roger Pau Monné
Sent: 18
> Il giorno 18 apr 2018, alle ore 11:18, jiang.bi...@zte.com.cn ha scritto:
>
> Hi,
>>> Il giorno 17 apr 2018, alle ore 09:10, Jiang Biao
>>> ha scritto:
>>>
>>> As described in the comment of blkcg_activate_policy(),
>>> *Update of each blkg is protected by both queue and blkcg locks so
>>>
On Wednesday 18 April 2018 04:54 PM, Mark Brown wrote:
On Wed, Apr 18, 2018 at 04:34:52PM +0530, Vijendar Mukunda wrote:
When multiple I2S controller instances created,
i2s_instance parameter refers to i2s controller instance value.
You're missing the point here a bit - it's not just the
On Tue, Apr 17, 2018 at 02:37:38PM -0500, Eric W. Biederman wrote:
> Dave Martin writes:
>
> > Hmmm
> >
> > memset()/clear_siginfo() may ensure that there are no uninitialised
> > explicit fields except for those in inactive union members, but I'm not
> > sure that this approach is guaranteed to
On i.MX6 ULL using PLL3 seems to cause a freeze when setting
the parent to IMX6UL_CLK_PLL3_USB_OTG. This only seems to appear
since commit 6f9575e55632 ("clk: imx: Add CLK_IS_CRITICAL flag
for busy divider and busy mux"), probably because the clock is
now forced to be on.
Fixes:
With FIFO enabled it is possible to read multiple bytes
at once in the interrupt handler as long as RXRDY is
set. This may also reduce the number of interrupts.
Signed-off-by: David Engraf
---
drivers/i2c/busses/i2c-at91.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff
It seems that this is a copy-paste error and that the proper
variable to use in this particular case is video_out2 instead
of video_out.
Addresses-Coverity-ID: 1467961 ("Copy-paste error")
Fixes: 45e46b3bbe18 ("[media] davinci: vpfe: dm365: resizer driver based on
media framework")
According to the data sheet the 3rd choice is the bypass clock
of pll2. This should not have any effect in practice as this
selection is not used currently.
Signed-off-by: Stefan Agner
---
drivers/clk/imx/clk-imx6ul.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
The ioread8/iowrite8 functions expect a memory offset argument. This
patch fixes the ports array to provide the memory addresses of the
respective device I/O registers.
Fixes: ca37081595a2 ("gpio: pcie-idio-24: Implement get_multiple/set_multiple
callbacks")
Signed-off-by: William Breathitt Gray
The ioread8 function expects a memory offset argument. This patch fixes
the ports array to provide the memory addresses of the respective device
I/O registers.
Fixes: 810ebfc5efca ("gpio: pci-idio-16: Implement get_multiple callback")
Signed-off-by: William Breathitt Gray
---
Em Tue, Apr 17, 2018 at 05:41:28PM -0400, Steven Rostedt escreveu:
> On Tue, 17 Apr 2018 15:13:04 -0300 Arnaldo Carvalho de Melo
> wrote:
> > Yeah, failing:
> > [root@jouet ~]# strace -e openat -e file perf test -F -v "mmap interface"
> > |& grep syscalls
> > openat(AT_FDCWD,
> >
On 18/04/18 13:32, Alban wrote:
I was also suggesting you to use nvmem-cell subnode, but make it a
proper nvmem provider device, rather than reusing its parent device.
You would end up some thing like this in dt.
flash@0 {
#address-cells = <1>;
#size-cells = <1>;
The GPIO PCI-IDIO-16 and PCIE-IDIO-24 drivers utilize the ioread8 and
iowrite8 functions to interact with their devices' respective I/O
registers. To simplify the get_multiple/set_multiple callbacks, a local
array 'ports' is used to hold the memory address offsets of the
respective device I/O
Hi Kirill,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on mmotm/master]
[also build test WARNING on next-20180418]
[cannot apply to v4.17-rc1]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
On 18.04.2018 11:23, Uwe Kleine-König wrote:
> On Wed, Apr 18, 2018 at 10:56:03AM +0300, Alexander Popov wrote:
>> On 18.04.2018 10:07, Uwe Kleine-König wrote:
>>> Your commit log is wrong (and I think the patch, too).
>>
>> I believe this bug is not a memdup_user() issue. There is a nice
On 2018-04-17 09:21, Stephen Boyd wrote:
Quoting Amit Nischal (2018-04-03 06:22:41)
diff --git a/drivers/clk/qcom/Kconfig b/drivers/clk/qcom/Kconfig
index fbf4532..c961e89 100644
--- a/drivers/clk/qcom/Kconfig
+++ b/drivers/clk/qcom/Kconfig
@@ -218,6 +218,15 @@ config MSM_MMCC_8996
Hi,
On 18.04.2018 15:55, kbuild test robot wrote:
> Hi Kirill,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on mmotm/master]
> [also build test WARNING on next-20180418]
> [cannot apply to v4.17-rc1]
> [if your patch is appli
On 04/18/2018 08:31 AM, Peter Ujfalusi wrote:
>
> On 2018-04-17 18:54, Lars-Peter Clausen wrote:
>> On 04/17/2018 04:53 PM, Peter Ujfalusi wrote:
>>> On 2018-04-17 16:58, Lars-Peter Clausen wrote:
>> There are two options.
>>
>> Either you extend the generic interfaces so it can cover
From: Tom Talpey
> Sent: 18 April 2018 12:32
...
> On 4/17/2018 8:33 PM, Long Li wrote:
> > From: Long Li
> >
> > The data buffer allocated on the stack can't be DMA'ed, and hence can't send
> > through RDMA via SMB Direct.
>
> This comment is confusing. Any registered memory can be DMA'd, need
Le 18/04/2018 à 10:36, Mathieu Malaterre a écrit :
Christophe,
On Wed, Apr 18, 2018 at 8:34 AM, Christophe LEROY
wrote:
Le 17/04/2018 à 19:10, Mathieu Malaterre a écrit :
On Tue, Apr 17, 2018 at 6:49 PM, Christophe LEROY
wrote:
Le 17/04/2018 à 18:45, Mathieu Malaterre a écrit :
Hi Christoph,
On Wed, Apr 18, 2018 at 03:47:03AM -0700, Christoph Hellwig wrote:
> On Tue, Apr 17, 2018 at 03:35:23PM +0200, Jacopo Mondi wrote:
> > With commit ce88313069c36eef80f21fd7 ("arch/sh: make the DMA mapping
> > operations observe dev->dma_pfn_offset") the generic DMA allocation
> >
Dear Shaohui,
I plead an indulgence if I have invaded your privacy by receiving this
mail from me without prior permission.With due respect,I contact you
purposely based on the similarities of names between you and my
deceased client who was an oil servicing contractor with shell
petroleum in West
Hi all,
The ROHM BD9571MWV PMIC on the Renesas Salvator-X(S) and ULCB
development boards supports DDR Backup Power, which means that the DDR
power rails can be kept powered while the main SoC is powered down.
Currently performing a system suspend/resume cycle involves several
manual
Document the new optional properties related to DDR Backup Mode and
toggle/momentary power switches.
Signed-off-by: Geert Uytterhoeven
Reviewed-by: Rob Herring
---
Acked-for-MFD-by: Lee Jones
v3:
- Add Reviewed-by, Acked-for-MFD-by (for Lee's own reference),
- Use a hex value for the bit
Add definitions for the KEEPON_* bits in the "BKUP Mode Cnt" register,
which control the DDR rails to be kept powered when backup mode is
enabled.
Signed-off-by: Geert Uytterhoeven
Acked-by: Lee Jones
---
v3:
- No changes,
v2:
- Add Acked-by.
---
include/linux/mfd/bd9571mwv.h | 5 +
1
Enable read/write access to the BD9571MWV_BKUP_MODE_CNT register, which
is amongst others used to configure DDR Backup Power.
Signed-off-by: Geert Uytterhoeven
---
Acked-for-MFD-by: Lee Jones
v3:
- No changes,
v2:
- Expand "a.o.",
- Add Acked-for-MFD-by.
---
drivers/mfd/bd9571mwv.c | 2
The BD9571MWV PMIC supports backup mode, which keeps one or more DDR
rails powered while the main SoC is powered down.
Which DDR rails are to be kept powered is board-specific, and controlled
using the optional "rohm,ddr-backup-power" DT property. In the absence
of this property, backup mode is
On Tue, Apr 17, 2018 at 07:37:27PM +0100, Mark Rutland wrote:
> In subsequent patches we're going to expose ptrauth to the host kernel
> and userspace, but things are a bit trickier for guest kernels. For the
> time being, let's hide ptrauth from KVM guests.
>
> Regardless of how well-behaved the
+++ Thomas Richter [18/04/18 09:14 +0200]:
Reading file /proc/modules shows the correct address:
[root@s35lp76 ~]# cat /proc/modules | egrep '^qeth_l2'
qeth_l2 94208 1 - Live 0x03ff80401000
and reading file /sys/module/qeth_l2/sections/.text
[root@s35lp76 ~]# cat
On Wed, Apr 18, 2018 at 09:54:37AM +0200, Michal Hocko wrote:
> On Wed 18-04-18 16:41:17, Minchan Kim wrote:
> > On Wed, Apr 18, 2018 at 09:20:02AM +0200, Michal Hocko wrote:
> > > On Wed 18-04-18 11:29:12, Minchan Kim wrote:
> [...]
> > > > Let's not make user scared.
> > >
> > > This is not a
This was the only error path during probe without a message being logged
about what went wrong, this fixes this.
Signed-off-by: Hans de Goede
---
drivers/virt/vboxguest/vboxguest_core.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
Move the declarations of functions from vboxguest_utils.c which are only
meant for vboxguest internal use from include/linux/vbox_utils.h to
drivers/virt/vboxguest/vboxguest_core.h.
Cc: sta...@vger.kernel.org
Signed-off-by: Hans de Goede
---
drivers/virt/vboxguest/vboxguest_core.h | 8
It is not possible to get DMA32 zone memory through kmalloc, causing
the vboxguest driver to malfunction due to getting memory above
4G which the PCI device cannot handle.
This commit changes the kmalloc calls where the 4G limit matters to
using __get_free_pages() fixing vboxguest not working on
This is a preparation patch for fixing issues on x86_64 virtual-machines
with more then 4G of RAM, atm we pass __GFP_DMA32 to kmalloc, but kmalloc
does not honor that, so we need to switch to get_pages, which means we
will not be able to use kfree to free memory allocated with vbg_alloc_req.
Hi Greg,
I know you are not entirely happy with the direct get_pages usage in this
patch-set, but as discussed that is currently the only way to get DMA32
memory.
Adding a better API for getting DMA32 mem really falls outside of the scope
of these patches and in the mean time the vboxguest
Michal Hocko wrote:
> > > Can we try a simpler way and get back to what I was suggesting before
> > > [1] and simply not play tricks with
> > > down_write(>mmap_sem);
> > > up_write(>mmap_sem);
> > >
> > > and use the write lock in exit_mmap for oom_victims?
> >
> > You mean
On Tue, Apr 17, 2018 at 11:06:50PM +0200, Borislav Petkov wrote:
> On Tue, Apr 17, 2018 at 03:16:55PM -0500, Josh Poimboeuf wrote:
> > I don't think the stack tracing code could do anything better here. #3
> > and #4 seem like an issue with the scheduler, it doesn't realize the
> > rest of the
On Wed 18-04-18 22:23:28, Minchan Kim wrote:
> On Wed, Apr 18, 2018 at 09:54:37AM +0200, Michal Hocko wrote:
> > On Wed 18-04-18 16:41:17, Minchan Kim wrote:
> > > On Wed, Apr 18, 2018 at 09:20:02AM +0200, Michal Hocko wrote:
> > > > On Wed 18-04-18 11:29:12, Minchan Kim wrote:
> > [...]
> > > > >
Hi all,
On Wed, Mar 14, 2018 at 12:26 PM, Geert Uytterhoeven
wrote:
> The ROHM BD9571MWV PMIC on the Renesas Salvator-X(S) and ULCB
> development boards supports DDR Backup Power, which means that the DDR
> power rails can be kept powered while the main SoC is powered down.
>
> This patch series
On Wed, Apr 18, 2018 at 11:29:12AM +0900, Minchan Kim wrote:
> If there are heavy memory pressure, page allocation with __GFP_NOWAIT
> fails easily although it's order-0 request.
> I got below warning 9 times for normal boot.
>
> Let's not make user scared.
Actually, can you explain why it's OK
When using half-duplex mode (which disables receiver during txing)
the RTS signal cannot be driven low during transmission. This seems
to be a limitation of the i.MX UART IP: The RTS (CTS_B) signal is
controlled by the receiver. When the receiver is disabled, the
signal stays in UART logic idle
Changes in v5:
1. Adressed review comments for v3 and v4 version of GCC driver for SDM845
https://lkml.org/lkml/2018/4/16/1129
2. Removed bi_tcxo clock being modelled from the GCC driver, as RPMH clock
driver would provide the same. https://lkml.org/lkml/2018/4/13/685
3. The GCC clock
On Wed, 18 Apr 2018 13:53:56 +0100
Srinivas Kandagatla wrote:
> On 18/04/18 13:32, Alban wrote:
> >> I was also suggesting you to use nvmem-cell subnode, but make it a
> >> proper nvmem provider device, rather than reusing its parent device.
> >>
> >> You would end up some thing like this in dt.
From: Taniya Das
Add support for the global clock controller found on SDM845
based devices. This should allow most non-multimedia device
drivers to probe and control their clocks.
Signed-off-by: Taniya Das
Signed-off-by: Amit Nischal
---
.../devicetree/bindings/clock/qcom,gcc.txt |
For some root clock generators, there could be child branches which are
controlled by an entity other than application processor subsystem. For
such RCGs, as per application processor subsystem clock driver, all of
its downstream clocks are disabled and RCG is in disabled state but in
reality
This option does dead code and data elimination with the linker by
compiling with -ffunction-sections -fdata-sections and linking with
--gc-sections.
By selecting this option on mpc885_ads_defconfig,
vmlinux LOAD segment size gets reduced by 10%
Program Header before the patch:
LOAD off
This patch fixes vmlinux.lds script to build properly with
CONFIG_LD_DEAD_CODE_DATA_ELIMINATION enabled
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/vmlinux.lds.S | 4 ++--
include/asm-generic/vmlinux.lds.h | 6 +-
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git
Hello,
FYI this happens in mainline kernel 4.17.0-rc1.
It looks like a new regression.
It occurs in 5 out of 5 boots.
[6.524361] ledtrig-cpu: registered to indicate activity on CPUs
[6.527658] NET: Registered protocol family 4
[6.528191] comedi: version 0.7.76 -
On Wed, 18 Apr 2018 13:42:03 +0200
Miklos Szeredi wrote:
> On Wed, Apr 18, 2018 at 10:19 AM, Amir Goldstein wrote:
> > On Thu, Apr 12, 2018 at 6:08 PM, Miklos Szeredi
> > wrote:
> >> This reverts commit a118084432d642eeccb961c7c8cc61525a941fcb.
> >>
> >> No user of d_real_inode() remains,
On 4/17/2018 6:53 PM, John David Anglin wrote:
> On 2018-04-17 2:28 PM, Sinan Kaya wrote:
>> The correct terminology here would be to use observability. Yes, it can be
>> cached in whatever part of the system for some amount of time as long as
>> PCI device sees it in the correct order.
>>
>>
On Wed 18-04-18 06:31:39, Matthew Wilcox wrote:
> On Wed, Apr 18, 2018 at 11:29:12AM +0900, Minchan Kim wrote:
> > If there are heavy memory pressure, page allocation with __GFP_NOWAIT
> > fails easily although it's order-0 request.
> > I got below warning 9 times for normal boot.
> >
> > Let's
On Tue, Apr 17, 2018 at 03:34:23PM +0100, Gustavo Pimentel wrote:
> The PCIe controller dual mode is capable of operating in host mode as well
> as endpoint mode by configuration.
>
> Signed-off-by: Gustavo Pimentel
> ---
> Change v1->v2:
> - Register new device id following Kishon's
On Wed 18-04-18 22:25:54, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > > > Can we try a simpler way and get back to what I was suggesting before
> > > > [1] and simply not play tricks with
> > > > down_write(>mmap_sem);
> > > > up_write(>mmap_sem);
> > > >
> > > >
Hello Stefan,
On Wed, Apr 18, 2018 at 03:32:17PM +0200, Stefan Agner wrote:
> diff --git a/drivers/tty/serial/imx.c b/drivers/tty/serial/imx.c
> index 91f3a1a5cb7f..1ba7e98ddc76 100644
> --- a/drivers/tty/serial/imx.c
> +++ b/drivers/tty/serial/imx.c
> @@ -1833,6 +1833,10 @@ static int
Add gpio-line-names property for Dragonboard820c based on APQ8096 SoC.
There are 4 gpio-controllers present on this board, including the
APQ8096 SoC, PM8994 (GPIO and MPP) and PMI8994 (GPIO).
Lines names are derived from 96Boards CE Specification 1.0, Appendix
"Expansion Connector Signal
Add gpio-line-names property for 96Boards Dragonboard820c development
board based on APQ8096 SoC. The lines are named after the 96Boards
CE Specification 1.0, Appendix "Expansion Connector Signal Description".
There are 4 gpio-controllers present on this board, including the
APQ8096 SoC, PM8994
On Wed, Apr 18, 2018 at 03:19:26PM +0200, Andrew Jones wrote:
> On Tue, Apr 17, 2018 at 07:37:27PM +0100, Mark Rutland wrote:
> > @@ -1000,6 +1000,15 @@ static u64 read_id_reg(struct sys_reg_desc const *r,
> > bool raz)
> > task_pid_nr(current));
> >
> >
Hi,
Because the timeout task gets the main spinlock and disable the current cpu's
irq,
there is no other task on the same cpu can run, and tasks on the other cpus can
not
enter the dm9000_timeout() again. So in the whole dm9000_timeout() routine,
db->timeout_cpu can not be changed by other
On Wed, Apr 18, 2018 at 12:03:27PM +0200, Mylène Josserand wrote:
> Hello,
>
> On Wed, 18 Apr 2018 11:36:27 +0200
> Geert Uytterhoeven wrote:
>
> > Hi Mylène,
> >
> > On Mon, Apr 16, 2018 at 11:50 PM, Mylène Josserand
> > wrote:
> > > Now that a common function is available for CNTVOFF's
> >
On Wed, Apr 18, 2018 at 3:38 PM, Steven Rostedt wrote:
> On Wed, 18 Apr 2018 13:42:03 +0200
> Miklos Szeredi wrote:
>
>> On Wed, Apr 18, 2018 at 10:19 AM, Amir Goldstein wrote:
>> > On Thu, Apr 12, 2018 at 6:08 PM, Miklos Szeredi
>> > wrote:
>> >> This reverts commit
On Wed, 18 Apr 2018 18:34:34 +0900
Masami Hiramatsu wrote:
> On Fri, 13 Apr 2018 10:44:32 -0400
> Steven Rostedt wrote:
>
> > On Fri, 13 Apr 2018 09:24:34 -0500
> > Tom Zanussi wrote:
> >
> > > Yeah, I agree - I'd rather get it right than get it in now. I thought
> > > this made sense,
In case of error, the function ioremap() returns NULL pointer not
ERR_PTR(). The IS_ERR() test in the return value check should be
replaced with NULL test.
Fixes: bf114d773167 ("m68k: force use of __raw_read/__raw_write address to be
iomem")
Signed-off-by: Wei Yongjun
---
=lkp
job=/lkp/scheduled/vm-intel12-yocto-x86_64-2/boot-1-yocto-minimal-x86_64-2016-04-22.cgz-60cc43fc888428bb2f18f08997432d426a243338-20180418-63270-jrkd3n-1.yaml
ARCH=x86_64 kconfig=x86_64-randconfig-s0-04090505
branch=linux-devel/devel-spot-201804082042
commit
On Wed, Apr 18, 2018 at 02:22:12PM +0200, Borislav Petkov wrote:
> On Wed, Apr 18, 2018 at 02:08:40PM +0200, Vitezslav Samel wrote:
> > I switched to firmware-in-kernel early loading and that works OK.
firmware-in-kernel means you compile your microcode image in linux?
Can you tell me which
On Wed, Apr 18, 2018 at 02:39:27PM +0200, Maciej S. Szmigiero wrote:
> Can't really find this commit in any tree I have looked at (bp.git and
> tip.git at kernel.org).
> Was it pushed somewhere else?
No. Still waiting for the rest.
--
Regards/Gruss,
Boris.
Good mailing practices for 400:
[there's no entry in MAINTAINERS for the ORC unwinder. I'm guessing
at the mailing lists that might be interested in this]
I've done something stupid and fallen off the end of the stack. ORC
appears not to handle this very well (see backtrace at the bottom).
Look at this loop:
[ 60.750032]
Hello,
FYI here is a slightly different boot error in mainline kernel 4.17.0-rc1.
It also dates back to v4.16 .
It occurs in 4 out of 4 boots.
[0.00] Built 1 zonelists, mobility grouping on. Total pages: 128873
[0.00] Kernel command line: root=/dev/ram0 hung_task_panic=1 debug
1101 - 1200 of 1686 matches
Mail list logo
