Hi Benjamin,
Thanks so much for your patch.
I have tested them for Elan Gen5/Gen6(new) touchpad with SMbus/PS2.
It works fine in my thinkpad so far but I find an issue today after
lid-close/open.
I am not sure if you can see it in T480S , I "guess" it may be relative to
i2c_i801.
The
Hi Benjamin,
Thanks so much for your patch.
I have tested them for Elan Gen5/Gen6(new) touchpad with SMbus/PS2.
It works fine in my thinkpad so far but I find an issue today after
lid-close/open.
I am not sure if you can see it in T480S , I "guess" it may be relative to
i2c_i801.
The
From: Fengguang Wu
PTR_ERR should normally access the value just tested by IS_ERR
Generated by: scripts/coccinelle/tests/odd_ptr_err.cocci
Fixes: 742243a44a73 ("drm: xlnx: pl_disp: Use xlnx pipeline calls")
CC: Hyun Kwon
Signed-off-by: Fengguang
From: Fengguang Wu
PTR_ERR should normally access the value just tested by IS_ERR
Generated by: scripts/coccinelle/tests/odd_ptr_err.cocci
Fixes: 742243a44a73 ("drm: xlnx: pl_disp: Use xlnx pipeline calls")
CC: Hyun Kwon
Signed-off-by: Fengguang Wu
Signed-off-by: Julia Lawall
---
tree:
On Thu, 2018-03-29 at 09:15 -0700, Dmitry Torokhov wrote:
>
>
> Oh, sorry, I did not realize you wanted my Ack for bindings. I usually
> leave it to Rob and simply ack the driver itself when I am happy with
> the code.
>
> I'll go and add my ack to the binding post if that will help merging
>
On Thu, 2018-03-29 at 09:15 -0700, Dmitry Torokhov wrote:
>
>
> Oh, sorry, I did not realize you wanted my Ack for bindings. I usually
> leave it to Rob and simply ack the driver itself when I am happy with
> the code.
>
> I'll go and add my ack to the binding post if that will help merging
>
On Tue, Mar 20, 2018 at 03:31:25PM -0700, Dmitry Torokhov wrote:
> The way we are supposed to put controller to sleep and wake it up does not
> depend on the platform, but rather on controller itself, so we want to get
> rid of suspend mode in platform data (and eventually get rid of platform
>
On Tue, Mar 20, 2018 at 03:31:25PM -0700, Dmitry Torokhov wrote:
> The way we are supposed to put controller to sleep and wake it up does not
> depend on the platform, but rather on controller itself, so we want to get
> rid of suspend mode in platform data (and eventually get rid of platform
>
On 09/04/18 20:51, Boris Ostrovsky wrote:
> Pre-4.17 kernels ignored start_info's rsdp_paddr pointer and instead
> relied on finding RSDP in standard location in BIOS RO memory. This
> has worked since that's where Xen used to place it.
>
> However, with recent Xen change (commit 4a5733771e6f
On 09/04/18 20:51, Boris Ostrovsky wrote:
> Pre-4.17 kernels ignored start_info's rsdp_paddr pointer and instead
> relied on finding RSDP in standard location in BIOS RO memory. This
> has worked since that's where Xen used to place it.
>
> However, with recent Xen change (commit 4a5733771e6f
Commit-ID: fcbd8fa44664e99a5d8c7ab97f1afdd82472f973
Gitweb: https://git.kernel.org/tip/fcbd8fa44664e99a5d8c7ab97f1afdd82472f973
Author: Sandipan Das
AuthorDate: Wed, 4 Apr 2018 23:34:19 +0530
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: fcbd8fa44664e99a5d8c7ab97f1afdd82472f973
Gitweb: https://git.kernel.org/tip/fcbd8fa44664e99a5d8c7ab97f1afdd82472f973
Author: Sandipan Das
AuthorDate: Wed, 4 Apr 2018 23:34:19 +0530
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 9 Apr 2018 11:13:09 -0300
perf tests
Commit-ID: 7854e499f33fd9c7e63288692ffb754d9b1d02fd
Gitweb: https://git.kernel.org/tip/7854e499f33fd9c7e63288692ffb754d9b1d02fd
Author: Sandipan Das
AuthorDate: Wed, 4 Apr 2018 23:34:18 +0530
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: 7854e499f33fd9c7e63288692ffb754d9b1d02fd
Gitweb: https://git.kernel.org/tip/7854e499f33fd9c7e63288692ffb754d9b1d02fd
Author: Sandipan Das
AuthorDate: Wed, 4 Apr 2018 23:34:18 +0530
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 9 Apr 2018 11:13:08 -0300
perf clang:
Commit-ID: c2fb54a183cfe77c6fdc9d71e2d5299c1c302a6e
Gitweb: https://git.kernel.org/tip/c2fb54a183cfe77c6fdc9d71e2d5299c1c302a6e
Author: Sandipan Das
AuthorDate: Wed, 4 Apr 2018 23:34:17 +0530
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: c2fb54a183cfe77c6fdc9d71e2d5299c1c302a6e
Gitweb: https://git.kernel.org/tip/c2fb54a183cfe77c6fdc9d71e2d5299c1c302a6e
Author: Sandipan Das
AuthorDate: Wed, 4 Apr 2018 23:34:17 +0530
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 9 Apr 2018 11:13:07 -0300
perf tools:
Commit-ID: ad0902e0c4004dc95bf15229933012121ff54033
Gitweb: https://git.kernel.org/tip/ad0902e0c4004dc95bf15229933012121ff54033
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 6 Apr 2018 14:53:56 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: ad0902e0c4004dc95bf15229933012121ff54033
Gitweb: https://git.kernel.org/tip/ad0902e0c4004dc95bf15229933012121ff54033
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 6 Apr 2018 14:53:56 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 9 Apr 2018 10:57:50 -0300
Commit-ID: 94e87a8bd529121ea90219164c65c36ea1d19e56
Gitweb: https://git.kernel.org/tip/94e87a8bd529121ea90219164c65c36ea1d19e56
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 6 Apr 2018 12:11:11 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: fdae6400809aa179f8ca04e32f3eb176fb3b3a9d
Gitweb: https://git.kernel.org/tip/fdae6400809aa179f8ca04e32f3eb176fb3b3a9d
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 6 Apr 2018 11:56:11 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: fdae6400809aa179f8ca04e32f3eb176fb3b3a9d
Gitweb: https://git.kernel.org/tip/fdae6400809aa179f8ca04e32f3eb176fb3b3a9d
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 6 Apr 2018 11:56:11 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 6 Apr 2018 12:22:06 -0300
Commit-ID: 94e87a8bd529121ea90219164c65c36ea1d19e56
Gitweb: https://git.kernel.org/tip/94e87a8bd529121ea90219164c65c36ea1d19e56
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 6 Apr 2018 12:11:11 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 6 Apr 2018 12:23:25 -0300
Commit-ID: b238db655796e74b59d9ece58b645ad0b494d615
Gitweb: https://git.kernel.org/tip/b238db655796e74b59d9ece58b645ad0b494d615
Author: Adrian Hunter
AuthorDate: Tue, 6 Mar 2018 11:13:18 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: b238db655796e74b59d9ece58b645ad0b494d615
Gitweb: https://git.kernel.org/tip/b238db655796e74b59d9ece58b645ad0b494d615
Author: Adrian Hunter
AuthorDate: Tue, 6 Mar 2018 11:13:18 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 6 Apr 2018 09:40:41 -0300
perf
Commit d65026c6c62e7d9616c8ceb5a53b68bcdc050525 ("vhost: validate log
when IOTLB is enabled") introduced a regression. The logic was
originally:
if (vq->iotlb)
return 1;
return A && B;
After the patch the short-circuit logic for A was inverted:
if (A || vq->iotlb)
return A;
Commit d65026c6c62e7d9616c8ceb5a53b68bcdc050525 ("vhost: validate log
when IOTLB is enabled") introduced a regression. The logic was
originally:
if (vq->iotlb)
return 1;
return A && B;
After the patch the short-circuit logic for A was inverted:
if (A || vq->iotlb)
return A;
Currently vhost *_access_ok() functions return int. This is error-prone
because there are two popular conventions:
1. 0 means failure, 1 means success
2. -errno means failure, 0 means success
Although vhost mostly uses #1, it does not do so consistently.
umem_access_ok() uses #2.
This patch
Currently vhost *_access_ok() functions return int. This is error-prone
because there are two popular conventions:
1. 0 means failure, 1 means success
2. -errno means failure, 0 means success
Although vhost mostly uses #1, it does not do so consistently.
umem_access_ok() uses #2.
This patch
v2:
* Rewrote the conditional to make the vq access check clearer [Linus]
* Added Patch 2 to make the return type consistent and harder to misuse [Linus]
The first patch fixes the vhost virtqueue access check which was recently
broken. The second patch replaces the int return type with bool to
v2:
* Rewrote the conditional to make the vq access check clearer [Linus]
* Added Patch 2 to make the return type consistent and harder to misuse [Linus]
The first patch fixes the vhost virtqueue access check which was recently
broken. The second patch replaces the int return type with bool to
;
> perf/x86/intel: Move regs->flags EXACT bit init (2018-04-05 09:28:40 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
> tags/perf-urgent-for-mingo-4.17-20180409
>
> for you to fetch changes up to
tel: Move regs->flags EXACT bit init (2018-04-05 09:28:40 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
> tags/perf-urgent-for-mingo-4.17-20180409
>
> for you to fetch changes up to fcbd8fa44664e99a5d8
Add the 3 optional power supplies using the exact description
found in the document named
"SiI9022A/SiI9024A HDMI Transmitter Data Sheet (August 2016)".
Signed-off-by: Philippe Cornu
---
drivers/gpu/drm/bridge/sii902x.c | 39 +++
1 file
Add the 3 optional power supplies using the exact description
found in the document named
"SiI9022A/SiI9024A HDMI Transmitter Data Sheet (August 2016)".
Signed-off-by: Philippe Cornu
---
drivers/gpu/drm/bridge/sii902x.c | 39 +++
1 file changed, 35
This patchset adds the 3 optional power supplies to the sii902x
drm bridge driver.
Philippe Cornu (2):
dt-bindings/display/bridge: sii902x: add optional power supplies
drm/bridge: sii902x: add optional power supplies
.../devicetree/bindings/display/bridge/sii902x.txt | 3 ++
This patchset adds the 3 optional power supplies to the sii902x
drm bridge driver.
Philippe Cornu (2):
dt-bindings/display/bridge: sii902x: add optional power supplies
drm/bridge: sii902x: add optional power supplies
.../devicetree/bindings/display/bridge/sii902x.txt | 3 ++
Add the 3 optional power supplies using the exact description
found in the document named
"SiI9022A/SiI9024A HDMI Transmitter Data Sheet (August 2016)".
Signed-off-by: Philippe Cornu
---
Documentation/devicetree/bindings/display/bridge/sii902x.txt | 3 +++
1 file changed,
Add the 3 optional power supplies using the exact description
found in the document named
"SiI9022A/SiI9024A HDMI Transmitter Data Sheet (August 2016)".
Signed-off-by: Philippe Cornu
---
Documentation/devicetree/bindings/display/bridge/sii902x.txt | 3 +++
1 file changed, 3 insertions(+)
diff
Hi,
On Monday 09 April 2018 03:11 PM, Gustavo Pimentel wrote:
> The PCIe controller dual mode is capable of operating in host mode as well
> as endpoint mode by configuration, therefore this patch aims to add
> endpoint mode support to the designware driver.
>
> Signed-off-by: Gustavo Pimentel
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/libnvdimm-for-4.17
...to receive the libnvdimm update for 4.17.
This cycle was was not something I ever want to repeat as there were
several late changes that have only now just settled. Half of the
Hi,
On Monday 09 April 2018 03:11 PM, Gustavo Pimentel wrote:
> The PCIe controller dual mode is capable of operating in host mode as well
> as endpoint mode by configuration, therefore this patch aims to add
> endpoint mode support to the designware driver.
>
> Signed-off-by: Gustavo Pimentel
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/libnvdimm-for-4.17
...to receive the libnvdimm update for 4.17.
This cycle was was not something I ever want to repeat as there were
several late changes that have only now just settled. Half of the
Hello,
syzbot hit the following crash on upstream commit
fd40ffc72e2f74c7db61e400903e7d50a88bc0b0 (Mon Apr 9 18:36:05 2018 +)
selinux: fix missing dput() before selinuxfs unmount
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=dd8fe49d0d1423aa5295
C reproducer:
Hello,
syzbot hit the following crash on upstream commit
fd40ffc72e2f74c7db61e400903e7d50a88bc0b0 (Mon Apr 9 18:36:05 2018 +)
selinux: fix missing dput() before selinuxfs unmount
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=dd8fe49d0d1423aa5295
C reproducer:
On Tue, Apr 10, 2018 at 10:52:52AM +0800, Jason Wang wrote:
> On 2018年04月02日 23:23, Tiwei Bie wrote:
> > This patch introduces a mdev (mediated device) based hardware
> > vhost backend. This backend is an abstraction of the various
> > hardware vhost accelerators (potentially any device that uses
Hi all,
Please do not add any v4.18 destined stuff to your linux-next included
trees until after v4.17-rc1 has been released.
Changes since 20180409:
The parisc-hd tree still had its build failure for which I applied a patch.
The nvdimm tree lost its build failure.
Non-merge commits (relative
On Tue, Apr 10, 2018 at 10:52:52AM +0800, Jason Wang wrote:
> On 2018年04月02日 23:23, Tiwei Bie wrote:
> > This patch introduces a mdev (mediated device) based hardware
> > vhost backend. This backend is an abstraction of the various
> > hardware vhost accelerators (potentially any device that uses
Hi all,
Please do not add any v4.18 destined stuff to your linux-next included
trees until after v4.17-rc1 has been released.
Changes since 20180409:
The parisc-hd tree still had its build failure for which I applied a patch.
The nvdimm tree lost its build failure.
Non-merge commits (relative
Hi Matthias,
On Mar 18, 2018, at 11:11 PM, Kai-Heng Feng
wrote:
The Dell Inspiron 5775 is a Raven Ridge. The Enable Slot command timed
out when a USB device gets plugged:
[ 212.156326] xhci_hcd :03:00.3: Error while assigning device slot ID
[ 212.156340]
On 4/9/18 9:45 PM, Ravi Bangoria wrote:
Hi Song,
On 12/07/2017 04:15 AM, Song Liu wrote:
With current kernel, user space tools can only create/destroy [k,u]probes
with a text-based API (kprobe_events and uprobe_events in tracefs). This
approach relies on user space to clean up the [k,u]probe
Hi Matthias,
On Mar 18, 2018, at 11:11 PM, Kai-Heng Feng
wrote:
The Dell Inspiron 5775 is a Raven Ridge. The Enable Slot command timed
out when a USB device gets plugged:
[ 212.156326] xhci_hcd :03:00.3: Error while assigning device slot ID
[ 212.156340] xhci_hcd :03:00.3: Max
On 4/9/18 9:45 PM, Ravi Bangoria wrote:
Hi Song,
On 12/07/2017 04:15 AM, Song Liu wrote:
With current kernel, user space tools can only create/destroy [k,u]probes
with a text-based API (kprobe_events and uprobe_events in tracefs). This
approach relies on user space to clean up the [k,u]probe
On Tue, 10 Apr 2018 02:23:26 +0200,
Andrew Morton wrote:
>
> On Sun, 8 Apr 2018 09:20:26 +0200 Takashi Iwai wrote:
>
> > We've got a bug report indicating a kernel panic at booting on an
> > x86-32 system, and it turned out to be the invalid resource assigned
> > after PCI
On Tue, 10 Apr 2018 02:23:26 +0200,
Andrew Morton wrote:
>
> On Sun, 8 Apr 2018 09:20:26 +0200 Takashi Iwai wrote:
>
> > We've got a bug report indicating a kernel panic at booting on an
> > x86-32 system, and it turned out to be the invalid resource assigned
> > after PCI resource
On 4/7/2018 3:37 AM, Daniel Kurtz wrote:
> Commit c31165d7400b ("mmc: sdhci-pci: Add support for HS200 tuning mode
> on AMD, eMMC-4.5.1") added a HS200 tuning method for use with AMD SDHCI
> controllers. As described in the commit subject, this tuning is specific
> for HS200. However, as
On 4/7/2018 3:37 AM, Daniel Kurtz wrote:
> Commit c31165d7400b ("mmc: sdhci-pci: Add support for HS200 tuning mode
> on AMD, eMMC-4.5.1") added a HS200 tuning method for use with AMD SDHCI
> controllers. As described in the commit subject, this tuning is specific
> for HS200. However, as
On Mon, Apr 09, 2018 at 12:01:59AM +0200, Mickaël Salaün wrote:
>
> On 04/08/2018 11:06 PM, Andy Lutomirski wrote:
> > On Sun, Apr 8, 2018 at 6:13 AM, Mickaël Salaün wrote:
> >>
> >> On 02/27/2018 10:48 PM, Mickaël Salaün wrote:
> >>>
> >>> On 27/02/2018 17:39, Andy Lutomirski
On Mon, Apr 09, 2018 at 12:01:59AM +0200, Mickaël Salaün wrote:
>
> On 04/08/2018 11:06 PM, Andy Lutomirski wrote:
> > On Sun, Apr 8, 2018 at 6:13 AM, Mickaël Salaün wrote:
> >>
> >> On 02/27/2018 10:48 PM, Mickaël Salaün wrote:
> >>>
> >>> On 27/02/2018 17:39, Andy Lutomirski wrote:
> On
Hi Song,
On 12/07/2017 04:15 AM, Song Liu wrote:
> With current kernel, user space tools can only create/destroy [k,u]probes
> with a text-based API (kprobe_events and uprobe_events in tracefs). This
> approach relies on user space to clean up the [k,u]probe after using them.
> However, this is
Hi Song,
On 12/07/2017 04:15 AM, Song Liu wrote:
> With current kernel, user space tools can only create/destroy [k,u]probes
> with a text-based API (kprobe_events and uprobe_events in tracefs). This
> approach relies on user space to clean up the [k,u]probe after using them.
> However, this is
On 04/09/2018 09:33 PM, Stephen Boyd wrote:
> Quoting Rajendra Nayak (2018-03-15 21:08:22)
>> diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
>> b/arch/arm64/boot/dts/qcom/msm8996.dtsi
>> index 0a6f7952bbb1..43757a078146 100644
>> --- a/arch/arm64/boot/dts/qcom/msm8996.dtsi
>> +++
On 04/09/2018 09:33 PM, Stephen Boyd wrote:
> Quoting Rajendra Nayak (2018-03-15 21:08:22)
>> diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
>> b/arch/arm64/boot/dts/qcom/msm8996.dtsi
>> index 0a6f7952bbb1..43757a078146 100644
>> --- a/arch/arm64/boot/dts/qcom/msm8996.dtsi
>> +++
On 04/10, Chao Yu wrote:
> On 2018/4/10 2:02, Jaegeuk Kim wrote:
> > On 04/08, Chao Yu wrote:
> >> On 2018/4/5 11:51, Jaegeuk Kim wrote:
> >>> On 04/04, Chao Yu wrote:
> This patch enlarges block plug coverage in __issue_discard_cmd, in
> order to collect more pending bios before issuing
On 04/10, Chao Yu wrote:
> On 2018/4/10 2:02, Jaegeuk Kim wrote:
> > On 04/08, Chao Yu wrote:
> >> On 2018/4/5 11:51, Jaegeuk Kim wrote:
> >>> On 04/04, Chao Yu wrote:
> This patch enlarges block plug coverage in __issue_discard_cmd, in
> order to collect more pending bios before issuing
Hi Laura,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.16 next-20180409]
[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
Hi Laura,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.16 next-20180409]
[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 04/10, Chao Yu wrote:
> On 2018/4/10 3:00, Jaegeuk Kim wrote:
> > From: Chao Yu
> >
> > Related to https://lkml.org/lkml/2018/4/8/661
> >
> > Sometimes, we need to write meta data to new allocated block address,
> > then we will allocate a zeroed page in inner inode's
On 04/10, Chao Yu wrote:
> On 2018/4/10 3:00, Jaegeuk Kim wrote:
> > From: Chao Yu
> >
> > Related to https://lkml.org/lkml/2018/4/8/661
> >
> > Sometimes, we need to write meta data to new allocated block address,
> > then we will allocate a zeroed page in inner inode's address space, and
> >
On Tue, Apr 10, 2018 at 11:12 AM, Steven Rostedt wrote:
> On Tue, 10 Apr 2018 10:32:36 +0800
> Zhaoyang Huang wrote:
>
>> For bellowing scenario, process A have no intension to exhaust the
>> memory, but will be likely to be selected by OOM for we
On Tue, Apr 10, 2018 at 11:12 AM, Steven Rostedt wrote:
> On Tue, 10 Apr 2018 10:32:36 +0800
> Zhaoyang Huang wrote:
>
>> For bellowing scenario, process A have no intension to exhaust the
>> memory, but will be likely to be selected by OOM for we set
>> OOM_CORE_ADJ_MIN for it.
>> process
On 09-04-18, 09:03, Stephen Boyd wrote:
> We should go and
> update the platform populate code to always ignore operating-points-v2
> compatible nodes too.
Will do that.
--
viresh
On 09-04-18, 09:03, Stephen Boyd wrote:
> We should go and
> update the platform populate code to always ignore operating-points-v2
> compatible nodes too.
Will do that.
--
viresh
On 2018/4/10 3:00, Jaegeuk Kim wrote:
> From: Chao Yu
>
> Related to https://lkml.org/lkml/2018/4/8/661
>
> Sometimes, we need to write meta data to new allocated block address,
> then we will allocate a zeroed page in inner inode's address space, and
> fill partial data in
On 2018/4/10 3:00, Jaegeuk Kim wrote:
> From: Chao Yu
>
> Related to https://lkml.org/lkml/2018/4/8/661
>
> Sometimes, we need to write meta data to new allocated block address,
> then we will allocate a zeroed page in inner inode's address space, and
> fill partial data in it, and leave other
Change log from v2:
- consider IO error case when dealing with metapage
- memset by fill_node_footer
Change log from v1:
- don't memset for recovered page
Related to https://lkml.org/lkml/2018/4/8/661
Sometimes, we need to write meta data to new allocated block address,
then we will
Change log from v2:
- consider IO error case when dealing with metapage
- memset by fill_node_footer
Change log from v1:
- don't memset for recovered page
Related to https://lkml.org/lkml/2018/4/8/661
Sometimes, we need to write meta data to new allocated block address,
then we will
On Tue, Apr 10, 2018 at 10:55:25AM +0800, Jason Wang wrote:
> On 2018年04月01日 22:12, Tiwei Bie wrote:
> > Hello everyone,
> >
> > This RFC implements packed ring support for virtio driver.
> >
> > The code was tested with DPDK vhost (testpmd/vhost-PMD) implemented
> > by Jens at
On Tue, Apr 10, 2018 at 10:55:25AM +0800, Jason Wang wrote:
> On 2018年04月01日 22:12, Tiwei Bie wrote:
> > Hello everyone,
> >
> > This RFC implements packed ring support for virtio driver.
> >
> > The code was tested with DPDK vhost (testpmd/vhost-PMD) implemented
> > by Jens at
2018-04-10 0:04 GMT+09:00 Kees Cook :
> On Mon, Apr 9, 2018 at 1:54 AM, Masahiro Yamada
> wrote:
>> 2018-03-28 20:18 GMT+09:00 Kees Cook :
>>> On Mon, Mar 26, 2018 at 10:29 PM, Masahiro Yamada
>>>
2018-04-10 0:04 GMT+09:00 Kees Cook :
> On Mon, Apr 9, 2018 at 1:54 AM, Masahiro Yamada
> wrote:
>> 2018-03-28 20:18 GMT+09:00 Kees Cook :
>>> On Mon, Mar 26, 2018 at 10:29 PM, Masahiro Yamada
>>> wrote:
diff --git a/arch/Kconfig b/arch/Kconfig
index 8e0d665..b42378d 100644
---
On 04/09, Steven Rostedt wrote:
>On Tue, 10 Apr 2018 09:23:40 +0800
>Ye Xiaolong wrote:
>
>> Hi, Steven
>>
>> On 04/09, Steven Rostedt wrote:
>> >On Mon, 9 Apr 2018 13:32:52 +0800
>> >kernel test robot wrote:
>> >
>> >> FYI, we noticed the
On 04/09, Steven Rostedt wrote:
>On Tue, 10 Apr 2018 09:23:40 +0800
>Ye Xiaolong wrote:
>
>> Hi, Steven
>>
>> On 04/09, Steven Rostedt wrote:
>> >On Mon, 9 Apr 2018 13:32:52 +0800
>> >kernel test robot wrote:
>> >
>> >> FYI, we noticed the following commit (built with gcc-7):
>> >>
>> >>
On Tue, 10 Apr 2018 10:32:36 +0800
Zhaoyang Huang wrote:
> For bellowing scenario, process A have no intension to exhaust the
> memory, but will be likely to be selected by OOM for we set
> OOM_CORE_ADJ_MIN for it.
> process A(-1000)
On Tue, 10 Apr 2018 10:32:36 +0800
Zhaoyang Huang wrote:
> For bellowing scenario, process A have no intension to exhaust the
> memory, but will be likely to be selected by OOM for we set
> OOM_CORE_ADJ_MIN for it.
> process A(-1000) process B
>
> i =
On 04/09/2018 06:41 PM, Matthew Wilcox wrote:
> On Mon, Apr 09, 2018 at 04:05:05PM -0700, Mike Kravetz wrote:
>> +/*
>> + * We need a tag: a new tag would expand every radix_tree_node by 8 bytes,
>> + * so reuse a tag which we firmly believe is never set or cleared on shmem.
>> + */
>> +#define
On 04/09/2018 06:41 PM, Matthew Wilcox wrote:
> On Mon, Apr 09, 2018 at 04:05:05PM -0700, Mike Kravetz wrote:
>> +/*
>> + * We need a tag: a new tag would expand every radix_tree_node by 8 bytes,
>> + * so reuse a tag which we firmly believe is never set or cleared on shmem.
>> + */
>> +#define
this is useing memmap=0x4101000-0x6aeff000 to free BIOS reserved memory
"6aeff000-6eff : reserved":
..
0010-6aefefff : System RAM
0100-0165537a : Kernel code
0165537b-01a8873f : Kernel data
01c31000-01f4efff : Kernel bss
Long,
> I hope this patch set goes through SCSI, because it's purpose is to
> improve storvsc.
>
> If this strategy is not possible, I can resubmit the 1st two patches to
> net, and the 3rd patch to scsi after the 1st two are merged.
Applied to my staging tree for 4.18/scsi-queue. Thanks!
--
this is useing memmap=0x4101000-0x6aeff000 to free BIOS reserved memory
"6aeff000-6eff : reserved":
..
0010-6aefefff : System RAM
0100-0165537a : Kernel code
0165537b-01a8873f : Kernel data
01c31000-01f4efff : Kernel bss
Long,
> I hope this patch set goes through SCSI, because it's purpose is to
> improve storvsc.
>
> If this strategy is not possible, I can resubmit the 1st two patches to
> net, and the 3rd patch to scsi after the 1st two are merged.
Applied to my staging tree for 4.18/scsi-queue. Thanks!
--
From: zoucao
Normally every BIOS reserved memory is used for some features, we can't
use them, but in some conditions, users can ensure some BIOS memories
are not used and reserved memory is well to free, they have not a good
way to free these memories, here add a
From: zoucao
Normally every BIOS reserved memory is used for some features, we can't
use them, but in some conditions, users can ensure some BIOS memories
are not used and reserved memory is well to free, they have not a good
way to free these memories, here add a new chareater "-" in memmap to
On Mon, Apr 09, 2018 at 07:41:52PM -0700, Matthew Wilcox wrote:
> On Tue, Apr 10, 2018 at 11:33:39AM +0900, Minchan Kim wrote:
> > @@ -522,7 +532,7 @@ EXPORT_SYMBOL(radix_tree_preload);
> > */
> > int radix_tree_maybe_preload(gfp_t gfp_mask)
> > {
> > - if (gfpflags_allow_blocking(gfp_mask))
On Mon, Apr 09, 2018 at 07:41:52PM -0700, Matthew Wilcox wrote:
> On Tue, Apr 10, 2018 at 11:33:39AM +0900, Minchan Kim wrote:
> > @@ -522,7 +532,7 @@ EXPORT_SYMBOL(radix_tree_preload);
> > */
> > int radix_tree_maybe_preload(gfp_t gfp_mask)
> > {
> > - if (gfpflags_allow_blocking(gfp_mask))
FYI, we noticed the following commit (built with gcc-7):
commit: e979e5a0591e70ad0b41cf876ee987de468a220e ("hugetlbfs: Convert to
fs_context")
https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git mount-context
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm
FYI, we noticed the following commit (built with gcc-7):
commit: e979e5a0591e70ad0b41cf876ee987de468a220e ("hugetlbfs: Convert to
fs_context")
https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git mount-context
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm
John,
> This patchset introduces some minor, more trivial patches, some of
> which have been sitting on our internal dev branch for a while.
Applied to 4.18/scsi-queue. Thank you!
--
Martin K. Petersen Oracle Linux Engineering
John,
> This patchset introduces some minor, more trivial patches, some of
> which have been sitting on our internal dev branch for a while.
Applied to 4.18/scsi-queue. Thank you!
--
Martin K. Petersen Oracle Linux Engineering
On 2018年04月01日 22:12, Tiwei Bie wrote:
Hello everyone,
This RFC implements packed ring support for virtio driver.
The code was tested with DPDK vhost (testpmd/vhost-PMD) implemented
by Jens at http://dpdk.org/ml/archives/dev/2018-January/089417.html
Minor changes are needed for the vhost
On 2018年04月01日 22:12, Tiwei Bie wrote:
Hello everyone,
This RFC implements packed ring support for virtio driver.
The code was tested with DPDK vhost (testpmd/vhost-PMD) implemented
by Jens at http://dpdk.org/ml/archives/dev/2018-January/089417.html
Minor changes are needed for the vhost
1 - 100 of 1768 matches
Mail list logo