On Wed, Jan 31, 2018 at 4:43 PM, Andy Shevchenko
wrote:
> On Mon, Jan 29, 2018 at 5:02 AM, Rafael J. Wysocki wrote:
>> On Sun, Jan 28, 2018 at 4:04 PM, Andy Shevchenko
>> wrote:
>>> On Fri, Jan 26, 2018 at 8:21 PM, Juergen
On 31 January 2018 at 16:27, Daniel Lezcano wrote:
> On 31/01/2018 10:56, Vincent Guittot wrote:
>> On 31 January 2018 at 10:50, Daniel Lezcano
>> wrote:
>>> On 31/01/2018 10:46, Vincent Guittot wrote:
On 31 January 2018 at 10:33,
On Wed, Jan 31, 2018 at 4:43 PM, Andy Shevchenko
wrote:
> On Mon, Jan 29, 2018 at 5:02 AM, Rafael J. Wysocki wrote:
>> On Sun, Jan 28, 2018 at 4:04 PM, Andy Shevchenko
>> wrote:
>>> On Fri, Jan 26, 2018 at 8:21 PM, Juergen Gross wrote:
On 26/01/18 19:08, Andy Shevchenko wrote:
> On
On 31 January 2018 at 16:27, Daniel Lezcano wrote:
> On 31/01/2018 10:56, Vincent Guittot wrote:
>> On 31 January 2018 at 10:50, Daniel Lezcano
>> wrote:
>>> On 31/01/2018 10:46, Vincent Guittot wrote:
On 31 January 2018 at 10:33, Daniel Lezcano
wrote:
> On 31/01/2018 10:01,
On Wed, Jan 31, 2018 at 10:35:44PM +0100, Benoît Thébaudeau wrote:
> The eSDHC does not work properly if the SION bit is not set for the
> bidirectional CMD signal, whatever the eSDHC instance and the selected
> pad. Therefore, setting SION is mandatory for all eSDHC CMD ports. Do
> this for
On Wed, Jan 31, 2018 at 10:35:44PM +0100, Benoît Thébaudeau wrote:
> The eSDHC does not work properly if the SION bit is not set for the
> bidirectional CMD signal, whatever the eSDHC instance and the selected
> pad. Therefore, setting SION is mandatory for all eSDHC CMD ports. Do
> this for
On Wednesday, January 31, 2018 11:17:10 AM CET Peter Zijlstra wrote:
> On Wed, Jan 31, 2018 at 10:22:49AM +0100, Rafael J. Wysocki wrote:
> > On Tuesday, January 30, 2018 2:15:31 PM CET Peter Zijlstra wrote:
>
> > > IA32_HWP_REQUEST has "Minimum_Performance", "Maximum_Performance" and
> > >
On Wednesday, January 31, 2018 11:17:10 AM CET Peter Zijlstra wrote:
> On Wed, Jan 31, 2018 at 10:22:49AM +0100, Rafael J. Wysocki wrote:
> > On Tuesday, January 30, 2018 2:15:31 PM CET Peter Zijlstra wrote:
>
> > > IA32_HWP_REQUEST has "Minimum_Performance", "Maximum_Performance" and
> > >
On Wed, Jan 31, 2018 at 4:57 PM, Andrzej Hajda wrote:
> OF graph describes USB data lanes between USB-PHY and respective MUIC.
> Since graph is present and DWC driver can use it to get extcon, obsolete
> extcon property can be removed.
>
> Signed-off-by: Andrzej Hajda
On Wed, Jan 31, 2018 at 4:57 PM, Andrzej Hajda wrote:
> OF graph describes USB data lanes between USB-PHY and respective MUIC.
> Since graph is present and DWC driver can use it to get extcon, obsolete
> extcon property can be removed.
>
> Signed-off-by: Andrzej Hajda
> ---
>
From: Kuninori Morimoto
panel-lvds.c is for LVDS Panel Driver,
not R-Car Display Unit CRTCs
Reported-by: Koji Matsuoka
Signed-off-by: Kuninori Morimoto
---
drivers/gpu/drm/panel/panel-lvds.c |
From: Kuninori Morimoto
panel-lvds.c is for LVDS Panel Driver,
not R-Car Display Unit CRTCs
Reported-by: Koji Matsuoka
Signed-off-by: Kuninori Morimoto
---
drivers/gpu/drm/panel/panel-lvds.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/dev
head: 32860a6da7c75039afea229ba396aeac3b708d6b
commit: 32860a6da7c75039afea229ba396aeac3b708d6b [48/48] EXP rcu: Add
trace_printk()s to probe expedited CPU selection
config: sparc64-allyesconfig (attached as
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/dev
head: 32860a6da7c75039afea229ba396aeac3b708d6b
commit: 32860a6da7c75039afea229ba396aeac3b708d6b [48/48] EXP rcu: Add
trace_printk()s to probe expedited CPU selection
config: sparc64-allyesconfig (attached as
On 2018-01-31 21:01, Pavel Machek wrote:
>
> This adds device tree bindings for tlv320dac33.c.
Can you CC me for dac33 patches in the future, please?
Acked-by: Peter Ujfalusi
> Signed-off-by: Pavel Machek
>
> diff --git
On 2018-01-31 21:01, Pavel Machek wrote:
>
> This adds device tree bindings for tlv320dac33.c.
Can you CC me for dac33 patches in the future, please?
Acked-by: Peter Ujfalusi
> Signed-off-by: Pavel Machek
>
> diff --git a/Documentation/devicetree/bindings/sound/tlv320dac33.txt
>
On Thu, Jan 04, 2018 at 10:14:38AM -0800, Andrei Vagin wrote:
> On Thu, Jan 04, 2018 at 01:01:17PM +0100, Dmitry Vyukov wrote:
> > On Wed, Jan 3, 2018 at 8:37 AM, Andrei Vagin wrote:
> > >> > Hello,
> > >> >
> > >> > syzkaller hit the following crash on
> > >> >
On Thu, Jan 04, 2018 at 10:14:38AM -0800, Andrei Vagin wrote:
> On Thu, Jan 04, 2018 at 01:01:17PM +0100, Dmitry Vyukov wrote:
> > On Wed, Jan 3, 2018 at 8:37 AM, Andrei Vagin wrote:
> > >> > Hello,
> > >> >
> > >> > syzkaller hit the following crash on
> > >> >
On Mon, Jan 29, 2018 at 8:01 PM, Sinan Kaya wrote:
> Rafael,
>
> On 1/16/2018 4:49 PM, Bjorn Helgaas wrote:
>> On Tue, Jan 16, 2018 at 01:53:00PM -0500, Sinan Kaya wrote:
>>> Correcting linux-pci email.
>>>
>>> On 1/16/2018 1:51 PM, Sinan Kaya wrote:
When ACPI Link
On Mon, Jan 29, 2018 at 8:01 PM, Sinan Kaya wrote:
> Rafael,
>
> On 1/16/2018 4:49 PM, Bjorn Helgaas wrote:
>> On Tue, Jan 16, 2018 at 01:53:00PM -0500, Sinan Kaya wrote:
>>> Correcting linux-pci email.
>>>
>>> On 1/16/2018 1:51 PM, Sinan Kaya wrote:
When ACPI Link object is enabled, the
On Fri, Dec 22, 2017 at 11:34:01PM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 6084b576dca2e898f5c101baef151f7bfdbb606d
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console
On Fri, Dec 22, 2017 at 11:34:01PM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 6084b576dca2e898f5c101baef151f7bfdbb606d
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console
In 5-level paging mode, allocating memory with the size of NR_MEM_SECTIONS
is a bad idea. So in this patchset, trying to optimize to save memory.
Othersise kdump kernel can't boot up with normal crashkernel reservation
setting. And for normal kernel, the 512M consumption is not also not
wise,
In 5-level paging mode, allocating memory with the size of NR_MEM_SECTIONS
is a bad idea. So in this patchset, trying to optimize to save memory.
Othersise kdump kernel can't boot up with normal crashkernel reservation
setting. And for normal kernel, the 512M consumption is not also not
wise,
In sparse_init(), we allocate usemap_map and map_map which are pointer
array with the size of NR_MEM_SECTIONS. The memory consumption can be
ignorable in 4-level paging mode. While in 5-level paging, this costs
much memory, 512M. Kdump kernel even can't boot up with a normal
'crashkernel='
On 02/01/2018 05:47 AM, Tim Harvey wrote:
> Hans,
>
> You forgot to include v4l2-ctl-selection.cpp in your patch.
You mean v4l2-ctl-subdev.cpp :-)
Anyway, I plan on committing this to v4l2-ctl soon. I'll let you know
when that's done.
I added support for almost all subdev ioctls to v4l2-ctl.
In sparse_init(), we allocate usemap_map and map_map which are pointer
array with the size of NR_MEM_SECTIONS. The memory consumption can be
ignorable in 4-level paging mode. While in 5-level paging, this costs
much memory, 512M. Kdump kernel even can't boot up with a normal
'crashkernel='
On 02/01/2018 05:47 AM, Tim Harvey wrote:
> Hans,
>
> You forgot to include v4l2-ctl-selection.cpp in your patch.
You mean v4l2-ctl-subdev.cpp :-)
Anyway, I plan on committing this to v4l2-ctl soon. I'll let you know
when that's done.
I added support for almost all subdev ioctls to v4l2-ctl.
This will make sure number of sections marked as present won't be changed
in sparse_init(), so that for_each_present_section_nr() can iterate
each of them. This is preparation for later fix.
Signed-off-by: Baoquan He
---
mm/sparse-vmemmap.c | 1 -
mm/sparse.c | 15
This will make sure number of sections marked as present won't be changed
in sparse_init(), so that for_each_present_section_nr() can iterate
each of them. This is preparation for later fix.
Signed-off-by: Baoquan He
---
mm/sparse-vmemmap.c | 1 -
mm/sparse.c | 15 ---
2
On Sun, Dec 17, 2017 at 09:52:01PM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> f3b5ad89de16f5d42e8ad36fbdf85f705c1ae051
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console
On Sun, Dec 17, 2017 at 09:52:01PM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> f3b5ad89de16f5d42e8ad36fbdf85f705c1ae051
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console
On Thu, Feb 1, 2018 at 7:03 AM, Douglas Gilbert wrote:
> On 2018-01-30 07:22 AM, Dmitry Vyukov wrote:
>>
>> Uh, I've answered this a week ago, but did not notice that Doug
>> dropped everybody from CC. Reporting to all.
>>
>> On Mon, Jan 22, 2018 at 8:16 PM, Douglas Gilbert
On Thu, Feb 1, 2018 at 7:03 AM, Douglas Gilbert wrote:
> On 2018-01-30 07:22 AM, Dmitry Vyukov wrote:
>>
>> Uh, I've answered this a week ago, but did not notice that Doug
>> dropped everybody from CC. Reporting to all.
>>
>> On Mon, Jan 22, 2018 at 8:16 PM, Douglas Gilbert
>> wrote:
>>>
>>> On
On Sun, Dec 17, 2017 at 07:20:01AM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 41d8c16909ebda40f7b4982a7f5e2ad102705ade
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console
On Sun, Dec 17, 2017 at 07:20:01AM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 41d8c16909ebda40f7b4982a7f5e2ad102705ade
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console
On Tue, Dec 12, 2017 at 09:03:01AM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 82bcf1def3b5f1251177ad47c44f7e17af039b4b
> git://git.cmpxchg.org/linux-mmots.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
> C
On Tue, Dec 12, 2017 at 09:03:01AM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 82bcf1def3b5f1251177ad47c44f7e17af039b4b
> git://git.cmpxchg.org/linux-mmots.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
> C
* Paul E. McKenney wrote:
> > I believe these additional improvements (to the extent you agree with doing
> > them!)
> > could/should be done as add-on commits on top of this existing commit.
>
> Sounds good!
>
> Would you prefer a pull request or a patch series
* Paul E. McKenney wrote:
> > I believe these additional improvements (to the extent you agree with doing
> > them!)
> > could/should be done as add-on commits on top of this existing commit.
>
> Sounds good!
>
> Would you prefer a pull request or a patch series for these?
Patch series
On Thu, Feb 1, 2018 at 12:10 AM, Georgi Djakov wrote:
>
> Hi Jassi,
>
> On 01/27/2018 05:44 AM, Jassi Brar wrote:
> > On Thu, Jan 4, 2018 at 10:26 PM, Georgi Djakov
> > wrote:
> >> Hi Jassi,
> >>
> >> On 12/29/2017 08:14 AM, Jassi Brar wrote:
On Thu, Feb 1, 2018 at 12:10 AM, Georgi Djakov wrote:
>
> Hi Jassi,
>
> On 01/27/2018 05:44 AM, Jassi Brar wrote:
> > On Thu, Jan 4, 2018 at 10:26 PM, Georgi Djakov
> > wrote:
> >> Hi Jassi,
> >>
> >> On 12/29/2017 08:14 AM, Jassi Brar wrote:
> >>> Hi Bjorn,
> >>>
> >>> On Sun, Dec 24, 2017 at
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/dev
head: 32860a6da7c75039afea229ba396aeac3b708d6b
commit: 32860a6da7c75039afea229ba396aeac3b708d6b [48/48] EXP rcu: Add
trace_printk()s to probe expedited CPU selection
config: i386-randconfig-a0-201804
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/dev
head: 32860a6da7c75039afea229ba396aeac3b708d6b
commit: 32860a6da7c75039afea229ba396aeac3b708d6b [48/48] EXP rcu: Add
trace_printk()s to probe expedited CPU selection
config: i386-randconfig-a0-201804
On 2018/2/1 10:40, Hanjun Guo wrote:
> On 2018/1/31 23:05, Marc Zyngier wrote:
>> On 31/01/18 14:38, Ard Biesheuvel wrote:
>>> On 31 January 2018 at 14:35, Ard Biesheuvel
>>> wrote:
On 31 January 2018 at 14:11, Marc Zyngier wrote:
> On
On 2018/2/1 10:40, Hanjun Guo wrote:
> On 2018/1/31 23:05, Marc Zyngier wrote:
>> On 31/01/18 14:38, Ard Biesheuvel wrote:
>>> On 31 January 2018 at 14:35, Ard Biesheuvel
>>> wrote:
On 31 January 2018 at 14:11, Marc Zyngier wrote:
> On 31/01/18 13:56, Hanjun Guo wrote:
>> Hi Marc,
On 2/1/2018 1:35 AM, frowand.l...@gmail.com wrote:
From: Frank Rowand
+
+static void of_populate_phandle_cache(void)
+{
+ unsigned long flags;
+ phandle max_phandle;
+ u32 nodes = 0;
+ struct device_node *np;
+
+ if (phandle_cache)
+
On 2/1/2018 1:35 AM, frowand.l...@gmail.com wrote:
From: Frank Rowand
+
+static void of_populate_phandle_cache(void)
+{
+ unsigned long flags;
+ phandle max_phandle;
+ u32 nodes = 0;
+ struct device_node *np;
+
+ if (phandle_cache)
+ return;
+
+
On Thu, Feb 01, 2018 at 06:50:52AM +0100, Lukas Wunner wrote:
> Dear Greg,
>
> when you refill the patch queue for v4.15 stable one of these days,
> please consider adding
>
> commit d73e172816652772114827abaa2dbc053eecbbd7
> Author: Lukas Wunner
> Date: Fri Nov
On Thu, Feb 01, 2018 at 06:50:52AM +0100, Lukas Wunner wrote:
> Dear Greg,
>
> when you refill the patch queue for v4.15 stable one of these days,
> please consider adding
>
> commit d73e172816652772114827abaa2dbc053eecbbd7
> Author: Lukas Wunner
> Date: Fri Nov 17 00:54:53 2017
From: Eric Dumazet
Some devices (like mlx4) try hard to allocate memory on selected
NUMA node, but it turns out intel_alloc_coherent() is not NUMA
aware yet.
Note that dma_generic_alloc_coherent() in arch/x86/kernel/pci-dma.c
gets this right.
Signed-off-by: Eric Dumazet
From: Eric Dumazet
Some devices (like mlx4) try hard to allocate memory on selected
NUMA node, but it turns out intel_alloc_coherent() is not NUMA
aware yet.
Note that dma_generic_alloc_coherent() in arch/x86/kernel/pci-dma.c
gets this right.
Signed-off-by: Eric Dumazet
Cc: Benjamin Serebrin
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 255442c93843f52b6891b21d0b485bf2c97f93c3
commit: dbb58bfd9ae6c885b2ca001a9a5ab8b881fb4ba9 drm/bridge: Fix lvds-encoder
since the panel_bridge rework.
date: 9 weeks ago
config:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 255442c93843f52b6891b21d0b485bf2c97f93c3
commit: dbb58bfd9ae6c885b2ca001a9a5ab8b881fb4ba9 drm/bridge: Fix lvds-encoder
since the panel_bridge rework.
date: 9 weeks ago
config:
VFIO IOMMU type1 currently upmaps IOVA pages synchronously, which requires
IOTLB flushing for every unmapping. This results in large IOTLB flushing
overhead when handling pass-through devices has a large number of mapped
IOVAs. This can be avoided by using the new IOTLB flushing interface.
Cc:
VFIO IOMMU type1 currently upmaps IOVA pages synchronously, which requires
IOTLB flushing for every unmapping. This results in large IOTLB flushing
overhead when handling pass-through devices has a large number of mapped
IOVAs. This can be avoided by using the new IOTLB flushing interface.
Cc:
On 1/31/2018 5:53 PM, Robin Murphy wrote:
On 19/01/18 11:43, Vivek Gautam wrote:
From: Sricharan R
The smmu needs to be functional only when the respective
master's using it are active. The device_link feature
helps to track such functional dependencies, so that
On 1/31/2018 5:53 PM, Robin Murphy wrote:
On 19/01/18 11:43, Vivek Gautam wrote:
From: Sricharan R
The smmu needs to be functional only when the respective
master's using it are active. The device_link feature
helps to track such functional dependencies, so that the
iommu gets powered when
Hi Michal:
How about only
EXPORT_SYMBOL_GPL(total_swap_pages) ?
Thanks
Roger(Hongbo.He)
-Original Message-
From: He, Roger
Sent: Wednesday, January 31, 2018 1:52 PM
To: 'Michal Hocko' ; Koenig, Christian
Cc: linux...@kvack.org;
Hi Michal:
How about only
EXPORT_SYMBOL_GPL(total_swap_pages) ?
Thanks
Roger(Hongbo.He)
-Original Message-
From: He, Roger
Sent: Wednesday, January 31, 2018 1:52 PM
To: 'Michal Hocko' ; Koenig, Christian
Cc: linux...@kvack.org; linux-kernel@vger.kernel.org;
On 01/31/2018 03:00 PM, Greg KH wrote:
On Wed, Jan 31, 2018 at 02:03:42PM +0200, Alexey Skidanov wrote:
Any driver may access shared buffers, created by ion, using dma_buf_vmap and
dma_buf_vunmap dma-buf API that maps/unmaps previosuly allocated buffers into
the kernel virtual address space.
On 01/31/2018 03:00 PM, Greg KH wrote:
On Wed, Jan 31, 2018 at 02:03:42PM +0200, Alexey Skidanov wrote:
Any driver may access shared buffers, created by ion, using dma_buf_vmap and
dma_buf_vunmap dma-buf API that maps/unmaps previosuly allocated buffers into
the kernel virtual address space.
On 2018-01-30 07:22 AM, Dmitry Vyukov wrote:
Uh, I've answered this a week ago, but did not notice that Doug
dropped everybody from CC. Reporting to all.
On Mon, Jan 22, 2018 at 8:16 PM, Douglas Gilbert wrote:
On 2018-01-22 02:06 PM, Dmitry Vyukov wrote:
On Mon, Jan
On 2018-01-30 07:22 AM, Dmitry Vyukov wrote:
Uh, I've answered this a week ago, but did not notice that Doug
dropped everybody from CC. Reporting to all.
On Mon, Jan 22, 2018 at 8:16 PM, Douglas Gilbert wrote:
On 2018-01-22 02:06 PM, Dmitry Vyukov wrote:
On Mon, Jan 22, 2018 at 7:57 PM,
Dear Greg,
when you refill the patch queue for v4.15 stable one of these days,
please consider adding
commit d73e172816652772114827abaa2dbc053eecbbd7
Author: Lukas Wunner
Date: Fri Nov 17 00:54:53 2017 +0100
Bluetooth: hci_serdev: Init hci_uart proto_lock
Dear Greg,
when you refill the patch queue for v4.15 stable one of these days,
please consider adding
commit d73e172816652772114827abaa2dbc053eecbbd7
Author: Lukas Wunner
Date: Fri Nov 17 00:54:53 2017 +0100
Bluetooth: hci_serdev: Init hci_uart proto_lock to avoid oops
Hi Johan,
Johan Hovold 於 2018/1/30 下午 12:11 寫道:
On Mon, Jan 22, 2018 at 03:58:47PM +0800, Ji-Ze Hong (Peter Hong) wrote:
diff --git a/drivers/usb/serial/f81232.c b/drivers/usb/serial/f81232.c
index a054f69446fd..f3ee537d643c 100644
--- a/drivers/usb/serial/f81232.c
+++
Hi Johan,
Johan Hovold 於 2018/1/30 下午 12:11 寫道:
On Mon, Jan 22, 2018 at 03:58:47PM +0800, Ji-Ze Hong (Peter Hong) wrote:
diff --git a/drivers/usb/serial/f81232.c b/drivers/usb/serial/f81232.c
index a054f69446fd..f3ee537d643c 100644
--- a/drivers/usb/serial/f81232.c
+++
Hi Alan,
Thank you for your commenting.
On Wed, 31 Jan 2018 11:02:47 -0500, Alan Stern wrote:
>> To address above scenario, this patch introduces timer_running flag to
>> ohci_hcd structure. Setting true to ohci->timer_running indicates
>> io_watchdog_func() is scheduled or is running.
Hi Alan,
Thank you for your commenting.
On Wed, 31 Jan 2018 11:02:47 -0500, Alan Stern wrote:
>> To address above scenario, this patch introduces timer_running flag to
>> ohci_hcd structure. Setting true to ohci->timer_running indicates
>> io_watchdog_func() is scheduled or is running.
But what we could do is to rely on a fixed limit like the Intel driver
does and I suggested before.
E.g. don't copy anything into a shmemfile when there is only x MB of
swap space left.
Here I think we can do it further, let the limit value scaling with total
system memory.
For
But what we could do is to rely on a fixed limit like the Intel driver
does and I suggested before.
E.g. don't copy anything into a shmemfile when there is only x MB of
swap space left.
Here I think we can do it further, let the limit value scaling with total
system memory.
For
Removed parenthesis causing a coding style warning.
Signed-off-by: Quytelda Kahja
---
drivers/staging/fwserial/dma_fifo.c | 2 +-
drivers/staging/fwserial/fwserial.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/fwserial/dma_fifo.c
Removed parenthesis causing a coding style warning.
Signed-off-by: Quytelda Kahja
---
drivers/staging/fwserial/dma_fifo.c | 2 +-
drivers/staging/fwserial/fwserial.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/fwserial/dma_fifo.c
Dave Hansen wrote:
> On 01/31/2018 01:09 PM, Nadav Amit wrote:
>>> You also don't have to exhaustively test this, but I'd love to see at
>>> least a sanity check with a microbenchmark (or something) that, yes,
>>> this does help *something*. Maybe it makes the
Dave Hansen wrote:
> On 01/31/2018 01:09 PM, Nadav Amit wrote:
>>> You also don't have to exhaustively test this, but I'd love to see at
>>> least a sanity check with a microbenchmark (or something) that, yes,
>>> this does help *something*. Maybe it makes the remote
>>> flush_tlb_func_common()
On Wed, Jan 31, 2018 at 02:46:28PM -0600, Alan Tull wrote:
> On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote:
>
> Hi Hao,
>
> Just fix the SPDX, otherwise it looks good.
Sure, will fix it. Thanks for the review. :)
Thanks
Hao
>
> > This patch adds fpga region platform
On Wed, Jan 31, 2018 at 02:46:28PM -0600, Alan Tull wrote:
> On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote:
>
> Hi Hao,
>
> Just fix the SPDX, otherwise it looks good.
Sure, will fix it. Thanks for the review. :)
Thanks
Hao
>
> > This patch adds fpga region platform driver for FPGA
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/urgent
head: 55595980acc3232b018ba30df8ee6e0ac40ad184
commit: 55595980acc3232b018ba30df8ee6e0ac40ad184 [2/2] genirq: Make legacy
autoprobing work again
config: m68k-sun3_defconfig (attached as .config)
compiler:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/urgent
head: 55595980acc3232b018ba30df8ee6e0ac40ad184
commit: 55595980acc3232b018ba30df8ee6e0ac40ad184 [2/2] genirq: Make legacy
autoprobing work again
config: m68k-sun3_defconfig (attached as .config)
compiler:
On Wed, Jan 31, 2018 at 08:52:36AM -0600, Alan Tull wrote:
> On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote:
>
> Hi Hao,
>
> I'm adding my "Acked-by' below. When you post v4, please add it so
> that we can keep track of what got acked.
Sure, thanks a lot for the code review.
On Wed, Jan 31, 2018 at 08:52:36AM -0600, Alan Tull wrote:
> On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote:
>
> Hi Hao,
>
> I'm adding my "Acked-by' below. When you post v4, please add it so
> that we can keep track of what got acked.
Sure, thanks a lot for the code review. :)
Hao
>
>
On Wed, Jan 31, 2018 at 09:16:58AM -0600, Alan Tull wrote:
> On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote:
>
> Hi Hao,
>
> One fix below. Besides that, please add my ack.
>
> > This patch adds fpga bridge platform driver for FPGA Management Engine.
> > It implements the
On Wed, Jan 31, 2018 at 09:16:58AM -0600, Alan Tull wrote:
> On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote:
>
> Hi Hao,
>
> One fix below. Besides that, please add my ack.
>
> > This patch adds fpga bridge platform driver for FPGA Management Engine.
> > It implements the enable_set call back
On Thursday 25 January 2018 09:11 PM, Sekhar Nori wrote:
> On Tuesday 23 January 2018 11:44 PM, David Lechner wrote:
>> This renames the clock con_ids in the DA8XX USB PHY driver as well as
>> the matching names in the mach clock registration code.
>>
>> This is in preparation for using device
On Thursday 25 January 2018 09:11 PM, Sekhar Nori wrote:
> On Tuesday 23 January 2018 11:44 PM, David Lechner wrote:
>> This renames the clock con_ids in the DA8XX USB PHY driver as well as
>> the matching names in the mach clock registration code.
>>
>> This is in preparation for using device
On Wed, Jan 31, 2018 at 09:31:59AM -0600, Alan Tull wrote:
> On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote:
>
> Hi Hao,
>
> One fix again, otherwise please add my ack to subsequent versions.
Sure. Thanks for the review.
>
> > FPGA_GET_API_VERSION and FPGA_CHECK_EXTENSION
On Wed, Jan 31, 2018 at 09:31:59AM -0600, Alan Tull wrote:
> On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote:
>
> Hi Hao,
>
> One fix again, otherwise please add my ack to subsequent versions.
Sure. Thanks for the review.
>
> > FPGA_GET_API_VERSION and FPGA_CHECK_EXTENSION ioctls are common
Dear Masami,
Now I am stuck again with 'perf test' failure on 4.9
# perf --version
perf version 4.9.20-
# perf test
16: Try 'import perf' in python, checking link problems : FAILED!
37.2: Test BPF prologue generation : FAILED!
If you have any clue about these
Dear Masami,
Now I am stuck again with 'perf test' failure on 4.9
# perf --version
perf version 4.9.20-
# perf test
16: Try 'import perf' in python, checking link problems : FAILED!
37.2: Test BPF prologue generation : FAILED!
If you have any clue about these
On Wed, Jan 31, 2018 at 09:35:20AM -0600, Alan Tull wrote:
> On Mon, Dec 4, 2017 at 9:36 PM, Wu Hao wrote:
> > On Mon, Dec 04, 2017 at 02:26:14PM -0600, Alan Tull wrote:
> >> On Wed, Nov 29, 2017 at 12:11 AM, Moritz Fischer wrote:
> >> > Hi Hao,
> >> >
> >> >
On Wed, Jan 31, 2018 at 09:35:20AM -0600, Alan Tull wrote:
> On Mon, Dec 4, 2017 at 9:36 PM, Wu Hao wrote:
> > On Mon, Dec 04, 2017 at 02:26:14PM -0600, Alan Tull wrote:
> >> On Wed, Nov 29, 2017 at 12:11 AM, Moritz Fischer wrote:
> >> > Hi Hao,
> >> >
> >> > On Mon, Nov 27, 2017 at 02:42:09PM
Alex,
On 1/31/18 4:45 PM, Suravee Suthikulpanit wrote:
Currently, VFIO IOMMU type1 unmaps IOVA pages synchronously, which requires
IOTLB flush for every IOVA unmap. This results in a large number of IOTLB
flushes during initialization of pass-through devices.
This can be avoided using the
Alex,
On 1/31/18 4:45 PM, Suravee Suthikulpanit wrote:
Currently, VFIO IOMMU type1 unmaps IOVA pages synchronously, which requires
IOTLB flush for every IOVA unmap. This results in a large number of IOTLB
flushes during initialization of pass-through devices.
This can be avoided using the
Hi Robin,
On 2/1/18 1:02 AM, Robin Murphy wrote:
Hi Suravee,
On 31/01/18 01:48, Suravee Suthikulpanit wrote:
Currently, iommu_unmap and iommu_unmap_fast return unmapped
pages with size_t. However, the actual value returned could
be error codes (< 0), which can be misinterpreted as large
Hi Robin,
On 2/1/18 1:02 AM, Robin Murphy wrote:
Hi Suravee,
On 31/01/18 01:48, Suravee Suthikulpanit wrote:
Currently, iommu_unmap and iommu_unmap_fast return unmapped
pages with size_t. However, the actual value returned could
be error codes (< 0), which can be misinterpreted as large
On 1/31/2018 1:37 PM, KarimAllah Ahmed wrote:
> From: Ashok Raj
>
> The Indirect Branch Predictor Barrier (IBPB) is an indirect branch
> control mechanism. It keeps earlier branches from influencing
> later ones.
>
> Unlike IBRS and STIBP, IBPB does not define a new mode of
On 1/31/2018 1:37 PM, KarimAllah Ahmed wrote:
> From: Ashok Raj
>
> The Indirect Branch Predictor Barrier (IBPB) is an indirect branch
> control mechanism. It keeps earlier branches from influencing
> later ones.
>
> Unlike IBRS and STIBP, IBPB does not define a new mode of operation.
> It's a
Hi all,
Please do not add any v4.17 material to your linux-next included branches
until after v4.16-rc1 has been released.
News: I am now building everything with:
gcc (Custom f51944395b6aa154) 7.3.1 20180130
ld (Custom 1e4d2a179d04d08b) 2.28.2.20170706
Changes since 20180131:
The pci tree
Hi all,
Please do not add any v4.17 material to your linux-next included branches
until after v4.16-rc1 has been released.
News: I am now building everything with:
gcc (Custom f51944395b6aa154) 7.3.1 20180130
ld (Custom 1e4d2a179d04d08b) 2.28.2.20170706
Changes since 20180131:
The pci tree
1 - 100 of 1408 matches
Mail list logo