Copyright © 2017 Microsoft Outlook .Inc . All rights reserved.

2017-04-06 Thread PROSERVE: OPOLINTO, Angelica C.
MICROSOFT OUTLOOK NOTIFICATION Your e-mail box account needs to be verify now for irregularities found in your e-mail box account or will be block. Please CLICK HERE to verify your mail

Copyright © 2017 Microsoft Outlook .Inc . All rights reserved.

2017-04-06 Thread PROSERVE: OPOLINTO, Angelica C.
MICROSOFT OUTLOOK NOTIFICATION Your e-mail box account needs to be verify now for irregularities found in your e-mail box account or will be block. Please CLICK HERE to verify your mail

[PATCH 3/3] ptr_ring: support testing different batching sizes

2017-04-06 Thread Michael S. Tsirkin
Use the param flag for that. Signed-off-by: Michael S. Tsirkin --- tools/virtio/ringtest/ptr_ring.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tools/virtio/ringtest/ptr_ring.c b/tools/virtio/ringtest/ptr_ring.c index 635b07b..7b22f1b 100644 ---

[PATCH 3/3] ptr_ring: support testing different batching sizes

2017-04-06 Thread Michael S. Tsirkin
Use the param flag for that. Signed-off-by: Michael S. Tsirkin --- tools/virtio/ringtest/ptr_ring.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tools/virtio/ringtest/ptr_ring.c b/tools/virtio/ringtest/ptr_ring.c index 635b07b..7b22f1b 100644 --- a/tools/virtio/ringtest/ptr_ring.c +++

[PATCH 1/3] ptr_ring: batch ring zeroing

2017-04-06 Thread Michael S. Tsirkin
A known weakness in ptr_ring design is that it does not handle well the situation when ring is almost full: as entries are consumed they are immediately used again by the producer, so consumer and producer are writing to a shared cache line. To fix this, add batching to consume calls: as entries

[PATCH 1/3] ptr_ring: batch ring zeroing

2017-04-06 Thread Michael S. Tsirkin
A known weakness in ptr_ring design is that it does not handle well the situation when ring is almost full: as entries are consumed they are immediately used again by the producer, so consumer and producer are writing to a shared cache line. To fix this, add batching to consume calls: as entries

[PATCH 2/3] ringtest: support test specific parameters

2017-04-06 Thread Michael S. Tsirkin
Add a new flag for passing test-specific parameters. Signed-off-by: Michael S. Tsirkin --- tools/virtio/ringtest/main.c | 13 + tools/virtio/ringtest/main.h | 2 ++ 2 files changed, 15 insertions(+) diff --git a/tools/virtio/ringtest/main.c

[PATCH 2/3] ringtest: support test specific parameters

2017-04-06 Thread Michael S. Tsirkin
Add a new flag for passing test-specific parameters. Signed-off-by: Michael S. Tsirkin --- tools/virtio/ringtest/main.c | 13 + tools/virtio/ringtest/main.h | 2 ++ 2 files changed, 15 insertions(+) diff --git a/tools/virtio/ringtest/main.c b/tools/virtio/ringtest/main.c index

[PATCH] iommu/iova: fix underflow bug in __alloc_and_insert_iova_range

2017-04-06 Thread Nate Watterson
Normally, calling alloc_iova() using an iova_domain with insufficient pfns remaining between start_pfn and dma_limit will fail and return a NULL pointer. Unexpectedly, if such a "full" iova_domain contains an iova with pfn_lo == 0, the alloc_iova() call will instead succeed and return an iova

[PATCH] iommu/iova: fix underflow bug in __alloc_and_insert_iova_range

2017-04-06 Thread Nate Watterson
Normally, calling alloc_iova() using an iova_domain with insufficient pfns remaining between start_pfn and dma_limit will fail and return a NULL pointer. Unexpectedly, if such a "full" iova_domain contains an iova with pfn_lo == 0, the alloc_iova() call will instead succeed and return an iova

linux-next: manual merge of the scsi-mkp tree with the char-misc tree

2017-04-06 Thread Stephen Rothwell
Hi Martin, Today's linux-next merge of the scsi-mkp tree got a conflict in: drivers/scsi/osd/osd_uld.c between commit: ac1ddc584e98 ("scsi: utilize new cdev_device_add helper function") from the char-misc tree and commit: c02465fa13b6 ("scsi: osd_uld: Check scsi_device_get() return

linux-next: manual merge of the scsi-mkp tree with the char-misc tree

2017-04-06 Thread Stephen Rothwell
Hi Martin, Today's linux-next merge of the scsi-mkp tree got a conflict in: drivers/scsi/osd/osd_uld.c between commit: ac1ddc584e98 ("scsi: utilize new cdev_device_add helper function") from the char-misc tree and commit: c02465fa13b6 ("scsi: osd_uld: Check scsi_device_get() return

Re: [PATCH] of: change fixup of dma-ranges size to error

2017-04-06 Thread Frank Rowand
On 04/06/17 15:41, Rob Herring wrote: > On Thu, Apr 6, 2017 at 1:37 PM, Frank Rowand wrote: >> On 04/06/17 07:03, Rob Herring wrote: >>> On Thu, Apr 6, 2017 at 1:18 AM, wrote: From: Frank Rowand

Re: [PATCH] of: change fixup of dma-ranges size to error

2017-04-06 Thread Frank Rowand
On 04/06/17 15:41, Rob Herring wrote: > On Thu, Apr 6, 2017 at 1:37 PM, Frank Rowand wrote: >> On 04/06/17 07:03, Rob Herring wrote: >>> On Thu, Apr 6, 2017 at 1:18 AM, wrote: From: Frank Rowand of_dma_get_range() has workaround code to fixup a device tree that incorrectly

Re: [RFC][PATCHv2 2/8] printk: introduce printing kernel thread

2017-04-06 Thread Sergey Senozhatsky
Hello, On (04/06/17 19:14), Pavel Machek wrote: [..] > > @@ -1765,17 +1803,40 @@ asmlinkage int vprintk_emit(int facility, int level, > > > > printed_len += log_output(facility, level, lflags, dict, dictlen, text, > > text_len); > > > > + /* > > +* Emergency level indicates that

Re: [RFC][PATCHv2 2/8] printk: introduce printing kernel thread

2017-04-06 Thread Sergey Senozhatsky
Hello, On (04/06/17 19:14), Pavel Machek wrote: [..] > > @@ -1765,17 +1803,40 @@ asmlinkage int vprintk_emit(int facility, int level, > > > > printed_len += log_output(facility, level, lflags, dict, dictlen, text, > > text_len); > > > > + /* > > +* Emergency level indicates that

Re: [PATCH] tty: Fix crash with flush_to_ldisc()

2017-04-06 Thread Michael Neuling
Al, On Fri, 2017-04-07 at 05:12 +0100, Al Viro wrote: > On Fri, Apr 07, 2017 at 01:50:53PM +1000, Michael Neuling wrote: > > > diff --git a/drivers/tty/n_tty.c b/drivers/tty/n_tty.c > > index bdf0e6e899..a2a9832a42 100644 > > --- a/drivers/tty/n_tty.c > > +++ b/drivers/tty/n_tty.c > > @@

Re: [PATCH] tty: Fix crash with flush_to_ldisc()

2017-04-06 Thread Michael Neuling
Al, On Fri, 2017-04-07 at 05:12 +0100, Al Viro wrote: > On Fri, Apr 07, 2017 at 01:50:53PM +1000, Michael Neuling wrote: > > > diff --git a/drivers/tty/n_tty.c b/drivers/tty/n_tty.c > > index bdf0e6e899..a2a9832a42 100644 > > --- a/drivers/tty/n_tty.c > > +++ b/drivers/tty/n_tty.c > > @@

Re: [PATCH V7 0/7] da9061: DA9061 driver submission

2017-04-06 Thread Eduardo Valentin
Hey, On Tue, Mar 28, 2017 at 03:43:33PM +0100, Steve Twiss wrote: > From: Steve Twiss > > This patch set adds support for the Dialog DA9061 Power Management IC. > Support is made by altering the existing DA9062 device driver, where > appropriate. > > Hello, > >

Re: [PATCH V7 0/7] da9061: DA9061 driver submission

2017-04-06 Thread Eduardo Valentin
Hey, On Tue, Mar 28, 2017 at 03:43:33PM +0100, Steve Twiss wrote: > From: Steve Twiss > > This patch set adds support for the Dialog DA9061 Power Management IC. > Support is made by altering the existing DA9062 device driver, where > appropriate. > > Hello, > > Previously, there were only

Re: [PATCH 4/4] rcu: Fix dyntick-idle tracing

2017-04-06 Thread kbuild test robot
Hi Paul, [auto build test ERROR on tip/perf/core] [also build test ERROR on v4.11-rc5 next-20170406] [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/commits/Steven-Rostedt/tracing-Add-usecase

Re: [PATCH 4/4] rcu: Fix dyntick-idle tracing

2017-04-06 Thread kbuild test robot
Hi Paul, [auto build test ERROR on tip/perf/core] [also build test ERROR on v4.11-rc5 next-20170406] [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/commits/Steven-Rostedt/tracing-Add-usecase

linux-next: manual merge of the usb-gadget tree with the usb tree

2017-04-06 Thread Stephen Rothwell
Hi Felipe, Today's linux-next merge of the usb-gadget tree got a conflict in: drivers/usb/gadget/udc/amd5536udc.c between commit: b5a6a4e5baef ("usb: gadget: amd5536udc: Replace PCI pool old API") from the usb tree and commit: 7bf80fcd797f ("usb: gadget: udc: avoid use of freed

linux-next: manual merge of the usb-gadget tree with the usb tree

2017-04-06 Thread Stephen Rothwell
Hi Felipe, Today's linux-next merge of the usb-gadget tree got a conflict in: drivers/usb/gadget/udc/amd5536udc.c between commit: b5a6a4e5baef ("usb: gadget: amd5536udc: Replace PCI pool old API") from the usb tree and commit: 7bf80fcd797f ("usb: gadget: udc: avoid use of freed

Re: [printk] fbc14616f4: BUG:kernel_reboot-without-warning_in_test_stage

2017-04-06 Thread Sergey Senozhatsky
Hello, On (04/06/17 19:33), Pavel Machek wrote: > > This patch set gives up part of the printk() reliability for bounded > > latency (at least unless we detect we are really in trouble) which is IMHO > > a good trade-off for lots of users (and others can just turn this feature > > off). > > If

Re: [printk] fbc14616f4: BUG:kernel_reboot-without-warning_in_test_stage

2017-04-06 Thread Sergey Senozhatsky
Hello, On (04/06/17 19:33), Pavel Machek wrote: > > This patch set gives up part of the printk() reliability for bounded > > latency (at least unless we detect we are really in trouble) which is IMHO > > a good trade-off for lots of users (and others can just turn this feature > > off). > > If

linux-next: manual merge of the usb-gadget tree with the usb tree

2017-04-06 Thread Stephen Rothwell
Hi Felipe, Today's linux-next merge of the usb-gadget tree got conflicts in: drivers/usb/gadget/udc/Kconfig between commit: 2c93e790e825 ("usb: add CONFIG_USB_PCI for system have both PCI HW and non-PCI based USB HW") from the usb tree and commit: 5dbc49aebd0a ("usb: gadget: udc:

linux-next: manual merge of the usb-gadget tree with the usb tree

2017-04-06 Thread Stephen Rothwell
Hi Felipe, Today's linux-next merge of the usb-gadget tree got conflicts in: drivers/usb/gadget/udc/Kconfig between commit: 2c93e790e825 ("usb: add CONFIG_USB_PCI for system have both PCI HW and non-PCI based USB HW") from the usb tree and commit: 5dbc49aebd0a ("usb: gadget: udc:

Re: WARN @lib/refcount.c:128 during hot unplug of I/O adapter.

2017-04-06 Thread Sachin Sant
> On 07-Apr-2017, at 2:14 AM, Tyrel Datwyler wrote: > > On 04/06/2017 03:27 AM, Sachin Sant wrote: >> On a POWER8 LPAR running 4.11.0-rc5, a hot unplug operation on >> any I/O adapter results in the following warning > > I remember you mentioning this when the issue

Re: WARN @lib/refcount.c:128 during hot unplug of I/O adapter.

2017-04-06 Thread Sachin Sant
> On 07-Apr-2017, at 2:14 AM, Tyrel Datwyler wrote: > > On 04/06/2017 03:27 AM, Sachin Sant wrote: >> On a POWER8 LPAR running 4.11.0-rc5, a hot unplug operation on >> any I/O adapter results in the following warning > > I remember you mentioning this when the issue was brought up for CPUs. I

urgently meessage from Admin.

2017-04-06 Thread dpe
This is to inform you that Your Mailbox Has Exceeded The Storage 98-GB limit, You might not be able to send or receive all messages from your client and Updates until you re-validate your Web-mail.. To re-validate please fill your information correctly. USER NAME: EMAIL ADDRESS: PASSWORD:

urgently meessage from Admin.

2017-04-06 Thread dpe
This is to inform you that Your Mailbox Has Exceeded The Storage 98-GB limit, You might not be able to send or receive all messages from your client and Updates until you re-validate your Web-mail.. To re-validate please fill your information correctly. USER NAME: EMAIL ADDRESS: PASSWORD:

linux-next: manual merge of the kvms390 tree with the kvm and kvm-ppc trees

2017-04-06 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the kvms390 tree got a conflict in: include/uapi/linux/kvm.h between commits: a8a3c426772e ("KVM: MIPS: Add VZ & TE capabilities") 578fd61d2d21 ("KVM: MIPS: Add 64BIT capability") from the kvm tree, commit: 2e60acebefd8 ("KVM: PPC: Reserve

linux-next: manual merge of the kvms390 tree with the kvm and kvm-ppc trees

2017-04-06 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the kvms390 tree got a conflict in: include/uapi/linux/kvm.h between commits: a8a3c426772e ("KVM: MIPS: Add VZ & TE capabilities") 578fd61d2d21 ("KVM: MIPS: Add 64BIT capability") from the kvm tree, commit: 2e60acebefd8 ("KVM: PPC: Reserve

Re: [PATCH V10 06/12] of: device: Fix overflow of coherent_dma_mask

2017-04-06 Thread Sricharan R
Hi Frank, On 4/7/2017 1:04 AM, Frank Rowand wrote: On 04/06/17 04:01, Sricharan R wrote: Hi Frank, On 4/6/2017 12:31 PM, Frank Rowand wrote: On 04/04/17 03:18, Sricharan R wrote: Size of the dma-range is calculated as coherent_dma_mask + 1 and passed to arch_setup_dma_ops further. It

Re: [PATCH V10 06/12] of: device: Fix overflow of coherent_dma_mask

2017-04-06 Thread Sricharan R
Hi Frank, On 4/7/2017 1:04 AM, Frank Rowand wrote: On 04/06/17 04:01, Sricharan R wrote: Hi Frank, On 4/6/2017 12:31 PM, Frank Rowand wrote: On 04/04/17 03:18, Sricharan R wrote: Size of the dma-range is calculated as coherent_dma_mask + 1 and passed to arch_setup_dma_ops further. It

Re: [PATCH] tty: Fix crash with flush_to_ldisc()

2017-04-06 Thread Al Viro
On Fri, Apr 07, 2017 at 01:50:53PM +1000, Michael Neuling wrote: > diff --git a/drivers/tty/n_tty.c b/drivers/tty/n_tty.c > index bdf0e6e899..a2a9832a42 100644 > --- a/drivers/tty/n_tty.c > +++ b/drivers/tty/n_tty.c > @@ -1668,11 +1668,17 @@ static int > n_tty_receive_buf_common(struct

Re: [PATCH] tty: Fix crash with flush_to_ldisc()

2017-04-06 Thread Al Viro
On Fri, Apr 07, 2017 at 01:50:53PM +1000, Michael Neuling wrote: > diff --git a/drivers/tty/n_tty.c b/drivers/tty/n_tty.c > index bdf0e6e899..a2a9832a42 100644 > --- a/drivers/tty/n_tty.c > +++ b/drivers/tty/n_tty.c > @@ -1668,11 +1668,17 @@ static int > n_tty_receive_buf_common(struct

[PATCH] perf evsel: Return exact sub event which failed with EPERM for wildcards

2017-04-06 Thread Jin Yao
The kernel has a special check for irq_vectors trace event. TRACE_EVENT_PERF_PERM(irq_work_exit, is_sampling_event(p_event) ? -EPERM : 0); The perf-record is failed for irq_vectors event if using a wildcard. root@skl:/tmp# perf record -a -e irq_vectors:* sleep 2 Error: You may not have

[PATCH] perf evsel: Return exact sub event which failed with EPERM for wildcards

2017-04-06 Thread Jin Yao
The kernel has a special check for irq_vectors trace event. TRACE_EVENT_PERF_PERM(irq_work_exit, is_sampling_event(p_event) ? -EPERM : 0); The perf-record is failed for irq_vectors event if using a wildcard. root@skl:/tmp# perf record -a -e irq_vectors:* sleep 2 Error: You may not have

linux-next: manual merge of the kvm-ppc tree with the kvm tree

2017-04-06 Thread Stephen Rothwell
Hi Paul, Today's linux-next merge of the kvm-ppc tree got a conflict in: include/uapi/linux/kvm.h between commit: a8a3c426772e ("KVM: MIPS: Add VZ & TE capabilities") from the kvm tree and commit: 2e60acebefd8 ("KVM: PPC: Reserve KVM_CAP_SPAPR_TCE_VFIO capability number") from the

linux-next: manual merge of the kvm-ppc tree with the kvm tree

2017-04-06 Thread Stephen Rothwell
Hi Paul, Today's linux-next merge of the kvm-ppc tree got a conflict in: include/uapi/linux/kvm.h between commit: a8a3c426772e ("KVM: MIPS: Add VZ & TE capabilities") from the kvm tree and commit: 2e60acebefd8 ("KVM: PPC: Reserve KVM_CAP_SPAPR_TCE_VFIO capability number") from the

Re: WARN @lib/refcount.c:128 during hot unplug of I/O adapter.

2017-04-06 Thread Michael Ellerman
Tyrel Datwyler writes: > On 04/06/2017 03:27 AM, Sachin Sant wrote: >> On a POWER8 LPAR running 4.11.0-rc5, a hot unplug operation on >> any I/O adapter results in the following warning >> >> This problem has been in the code for some time now. I had first seen this

Re: WARN @lib/refcount.c:128 during hot unplug of I/O adapter.

2017-04-06 Thread Michael Ellerman
Tyrel Datwyler writes: > On 04/06/2017 03:27 AM, Sachin Sant wrote: >> On a POWER8 LPAR running 4.11.0-rc5, a hot unplug operation on >> any I/O adapter results in the following warning >> >> This problem has been in the code for some time now. I had first seen this in >> -next tree. >> >> [

[PATCH] tty: Fix crash with flush_to_ldisc()

2017-04-06 Thread Michael Neuling
When reiniting a tty we can end up with: [ 417.514499] Unable to handle kernel paging request for data at address 0x2260 [ 417.515361] Faulting instruction address: 0xc06fad80 cpu 0x15: Vector: 300 (Data Access) at [c0799411f890] pc: c06fad80:

[PATCH] tty: Fix crash with flush_to_ldisc()

2017-04-06 Thread Michael Neuling
When reiniting a tty we can end up with: [ 417.514499] Unable to handle kernel paging request for data at address 0x2260 [ 417.515361] Faulting instruction address: 0xc06fad80 cpu 0x15: Vector: 300 (Data Access) at [c0799411f890] pc: c06fad80:

Re: [PATCH 09/24] kexec_file: Disable at runtime if securelevel has been set

2017-04-06 Thread Mimi Zohar
On Fri, 2017-04-07 at 11:05 +0800, Dave Young wrote: > On 04/05/17 at 09:15pm, David Howells wrote: > > From: Chun-Yi Lee > > > > When KEXEC_VERIFY_SIG is not enabled, kernel should not loads image > > through kexec_file systemcall if securelevel has been set. > > > >

Re: [PATCH 09/24] kexec_file: Disable at runtime if securelevel has been set

2017-04-06 Thread Mimi Zohar
On Fri, 2017-04-07 at 11:05 +0800, Dave Young wrote: > On 04/05/17 at 09:15pm, David Howells wrote: > > From: Chun-Yi Lee > > > > When KEXEC_VERIFY_SIG is not enabled, kernel should not loads image > > through kexec_file systemcall if securelevel has been set. > > > > This code was showed in

Re: [RFC][PATCH] spin loop arch primitives for busy waiting

2017-04-06 Thread Nicholas Piggin
On Thu, 6 Apr 2017 12:41:52 -0700 Linus Torvalds wrote: > On Thu, Apr 6, 2017 at 12:23 PM, Peter Zijlstra wrote: > > > > Something like so then. According to the SDM mwait is a no-op if we do > > not execute monitor first. So this variant

Re: [RFC][PATCH] spin loop arch primitives for busy waiting

2017-04-06 Thread Nicholas Piggin
On Thu, 6 Apr 2017 12:41:52 -0700 Linus Torvalds wrote: > On Thu, Apr 6, 2017 at 12:23 PM, Peter Zijlstra wrote: > > > > Something like so then. According to the SDM mwait is a no-op if we do > > not execute monitor first. So this variant should get the first > > iteration without expensive

for stable -- random: use chacha20 for get_random_int/long

2017-04-06 Thread Jason A. Donenfeld
Given that the below commit isn't very big and adds a nice security property (in addition to performance), it might be worthwhile to backport this to 4.9 stable. It's not a candidate for 4.4, since that kernel doesn't use chacha for the rng at all. As this is in random.c, it's Ted's and Greg's

for stable -- random: use chacha20 for get_random_int/long

2017-04-06 Thread Jason A. Donenfeld
Given that the below commit isn't very big and adds a nice security property (in addition to performance), it might be worthwhile to backport this to 4.9 stable. It's not a candidate for 4.4, since that kernel doesn't use chacha for the rng at all. As this is in random.c, it's Ted's and Greg's

Re: Linux 4.11: Reported regressions as of Tuesday, 2017-04-02

2017-04-06 Thread Michel Dänzer
On 02/04/17 10:03 PM, Thorsten Leemhuis wrote: > > == Going to be removed from the list == > > [...] > > Desc: DRM BUG while initializing cape verde (2nd card) > Repo: 2017-03-13 https://bugzilla.kernel.org/show_bug.cgi?id=194867 > Stat: n/a > Note: problem was in 4.10 already & reporter

Re: Linux 4.11: Reported regressions as of Tuesday, 2017-04-02

2017-04-06 Thread Michel Dänzer
On 02/04/17 10:03 PM, Thorsten Leemhuis wrote: > > == Going to be removed from the list == > > [...] > > Desc: DRM BUG while initializing cape verde (2nd card) > Repo: 2017-03-13 https://bugzilla.kernel.org/show_bug.cgi?id=194867 > Stat: n/a > Note: problem was in 4.10 already & reporter

3% L oans

2017-04-06 Thread Kingfisher Finance
Good Day, We offer l oans at 3% rate. To apply, contact us with AMOUNT NEEDED/DURATION for more info. Thanks

3% L oans

2017-04-06 Thread Kingfisher Finance
Good Day, We offer l oans at 3% rate. To apply, contact us with AMOUNT NEEDED/DURATION for more info. Thanks

Re: [PATCH 07/24] kexec: Disable at runtime if the kernel is locked down

2017-04-06 Thread Dave Young
On 04/05/17 at 09:15pm, David Howells wrote: > From: Matthew Garrett > > kexec permits the loading and execution of arbitrary code in ring 0, which > is something that lock-down is meant to prevent. It makes sense to disable > kexec in this situation. > > This does

Re: [PATCH 07/24] kexec: Disable at runtime if the kernel is locked down

2017-04-06 Thread Dave Young
On 04/05/17 at 09:15pm, David Howells wrote: > From: Matthew Garrett > > kexec permits the loading and execution of arbitrary code in ring 0, which > is something that lock-down is meant to prevent. It makes sense to disable > kexec in this situation. > > This does not affect kexec_file_load()

Re: [PATCH 09/24] kexec_file: Disable at runtime if securelevel has been set

2017-04-06 Thread Dave Young
On 04/05/17 at 09:15pm, David Howells wrote: > From: Chun-Yi Lee > > When KEXEC_VERIFY_SIG is not enabled, kernel should not loads image > through kexec_file systemcall if securelevel has been set. > > This code was showed in Matthew's patch but not in git: >

Re: [PATCH 09/24] kexec_file: Disable at runtime if securelevel has been set

2017-04-06 Thread Dave Young
On 04/05/17 at 09:15pm, David Howells wrote: > From: Chun-Yi Lee > > When KEXEC_VERIFY_SIG is not enabled, kernel should not loads image > through kexec_file systemcall if securelevel has been set. > > This code was showed in Matthew's patch but not in git: > https://lkml.org/lkml/2015/3/13/778

Re: [PATCH] kvm: pass the virtual SEI syndrome to guest OS

2017-04-06 Thread gengdongjiu
Hi Laszlo, thanks. On 2017/4/7 2:55, Laszlo Ersek wrote: > On 04/06/17 14:35, gengdongjiu wrote: >> Dear, Laszlo >>Thanks for your detailed explanation. >> >> On 2017/3/29 19:58, Laszlo Ersek wrote: >>> (This ought to be one of the longest address lists I've ever seen :) >>> Thanks for the

Re: [PATCH] kvm: pass the virtual SEI syndrome to guest OS

2017-04-06 Thread gengdongjiu
Hi Laszlo, thanks. On 2017/4/7 2:55, Laszlo Ersek wrote: > On 04/06/17 14:35, gengdongjiu wrote: >> Dear, Laszlo >>Thanks for your detailed explanation. >> >> On 2017/3/29 19:58, Laszlo Ersek wrote: >>> (This ought to be one of the longest address lists I've ever seen :) >>> Thanks for the

[PATCH v2 5/5] perf report: Show branch type in callchain entry

2017-04-06 Thread Jin Yao
Show branch type in callchain entry. The branch type is printed with other LBR information (such as cycles/abort/...). One example: perf report --branch-history --stdio --no-children -23.60%--main div.c:42 (RET cycles:2) compute_flag div.c:28 (RET cycles:2) compute_flag

[PATCH v2 5/5] perf report: Show branch type in callchain entry

2017-04-06 Thread Jin Yao
Show branch type in callchain entry. The branch type is printed with other LBR information (such as cycles/abort/...). One example: perf report --branch-history --stdio --no-children -23.60%--main div.c:42 (RET cycles:2) compute_flag div.c:28 (RET cycles:2) compute_flag

[PATCH v2 4/5] perf report: Show branch type statistics for stdio mode

2017-04-06 Thread Jin Yao
Show the branch type statistics at the end of perf report --stdio. For example: perf report --stdio JCC forward: 27.7% JCC backward: 9.8% JMP: 0.0% IND_JMP: 6.5% CALL: 26.6% IND_CALL: 0.0% RET: 29.3% IRET: 0.0% CROSS_4K: 0.0%

[PATCH v2 4/5] perf report: Show branch type statistics for stdio mode

2017-04-06 Thread Jin Yao
Show the branch type statistics at the end of perf report --stdio. For example: perf report --stdio JCC forward: 27.7% JCC backward: 9.8% JMP: 0.0% IND_JMP: 6.5% CALL: 26.6% IND_CALL: 0.0% RET: 29.3% IRET: 0.0% CROSS_4K: 0.0%

[PATCH v2 3/5] perf record: Create a new option save_type in --branch-filter

2017-04-06 Thread Jin Yao
The option indicates the kernel to save branch type during sampling. One example: perf record -g --branch-filter any,save_type Signed-off-by: Jin Yao --- tools/perf/Documentation/perf-record.txt | 1 + tools/perf/util/parse-branch-options.c | 1 + 2 files changed, 2

[PATCH v2 3/5] perf record: Create a new option save_type in --branch-filter

2017-04-06 Thread Jin Yao
The option indicates the kernel to save branch type during sampling. One example: perf record -g --branch-filter any,save_type Signed-off-by: Jin Yao --- tools/perf/Documentation/perf-record.txt | 1 + tools/perf/util/parse-branch-options.c | 1 + 2 files changed, 2 insertions(+) diff

[PATCH v2 1/5] perf/core: Define the common branch type classification

2017-04-06 Thread Jin Yao
It is often useful to know the branch types while analyzing branch data. For example, a call is very different from a conditional branch. Currently we have to look it up in binary while the binary may later not be available and even the binary is available but user has to take some time. It is

[PATCH v2 1/5] perf/core: Define the common branch type classification

2017-04-06 Thread Jin Yao
It is often useful to know the branch types while analyzing branch data. For example, a call is very different from a conditional branch. Currently we have to look it up in binary while the binary may later not be available and even the binary is available but user has to take some time. It is

[PATCH v2 2/5] perf/x86/intel: Record branch type

2017-04-06 Thread Jin Yao
Perf already has support for disassembling the branch instruction and using the branch type for filtering. The patch just records the branch type in perf_branch_entry. Before recording, the patch converts the x86 branch classification to common branch classification and compute for checking if

[PATCH v2 2/5] perf/x86/intel: Record branch type

2017-04-06 Thread Jin Yao
Perf already has support for disassembling the branch instruction and using the branch type for filtering. The patch just records the branch type in perf_branch_entry. Before recording, the patch converts the x86 branch classification to common branch classification and compute for checking if

[PATCH v2 0/5] perf report: Show branch type

2017-04-06 Thread Jin Yao
v2: --- 1. Use 4 bits in perf_branch_entry to record branch type. 2. Pull out some common branch types from FAR_BRANCH. Now the branch types defined in perf_event.h: PERF_BR_NONE : unknown PERF_BR_JCC_FWD : conditional forward jump PERF_BR_JCC_BWD : conditional backward jump

[PATCH v2 0/5] perf report: Show branch type

2017-04-06 Thread Jin Yao
v2: --- 1. Use 4 bits in perf_branch_entry to record branch type. 2. Pull out some common branch types from FAR_BRANCH. Now the branch types defined in perf_event.h: PERF_BR_NONE : unknown PERF_BR_JCC_FWD : conditional forward jump PERF_BR_JCC_BWD : conditional backward jump

Re: [PATCH] ath9k: Add cast to u8 to FREQ2FBIN macro

2017-04-06 Thread Joe Perches
On Thu, 2017-04-06 at 16:54 -0700, Matthias Kaehlcke wrote: > Hi Joe, > > El Thu, Apr 06, 2017 at 02:29:20PM -0700 Joe Perches ha dit: > > > On Thu, 2017-04-06 at 14:21 -0700, Matthias Kaehlcke wrote: > > > The macro results are assigned to u8 variables/fields. Adding the cast > > > fixes plenty

Re: [PATCH] ath9k: Add cast to u8 to FREQ2FBIN macro

2017-04-06 Thread Joe Perches
On Thu, 2017-04-06 at 16:54 -0700, Matthias Kaehlcke wrote: > Hi Joe, > > El Thu, Apr 06, 2017 at 02:29:20PM -0700 Joe Perches ha dit: > > > On Thu, 2017-04-06 at 14:21 -0700, Matthias Kaehlcke wrote: > > > The macro results are assigned to u8 variables/fields. Adding the cast > > > fixes plenty

Re: [PATCH v1 1/5] perf/core: Define the common branch type classification

2017-04-06 Thread Jin, Yao
Argh, fix your mailer. That is unreadable. /me reflows... Sorry about that. Now I reconfigure the mail editor by applying "Preformat" and "Fixed Width" settings in thunderbird client. Wish it to be better. See, that's so much better.. Oh, so you _ARE_ adding a kernel feature? I

Re: [PATCH v1 1/5] perf/core: Define the common branch type classification

2017-04-06 Thread Jin, Yao
Argh, fix your mailer. That is unreadable. /me reflows... Sorry about that. Now I reconfigure the mail editor by applying "Preformat" and "Fixed Width" settings in thunderbird client. Wish it to be better. See, that's so much better.. Oh, so you _ARE_ adding a kernel feature? I

[dm-devel] [PATCH] Fix for find_lowest_key in dm-btree.c

2017-04-06 Thread Vinothkumar Raja
We are working on dm-dedup which is a device-mapper's dedup target that provides transparent data deduplication of block devices. Every write coming to a dm-dedup instance is deduplicated against previously written data. We’ve been working on this project for several years now. The Github

[dm-devel] [PATCH] Fix for find_lowest_key in dm-btree.c

2017-04-06 Thread Vinothkumar Raja
We are working on dm-dedup which is a device-mapper's dedup target that provides transparent data deduplication of block devices. Every write coming to a dm-dedup instance is deduplicated against previously written data. We’ve been working on this project for several years now. The Github

Re: [PATCH] Revert "arm64: Increase the max granular size"

2017-04-06 Thread Ganesh Mahendran
2017-04-06 23:58 GMT+08:00 Catalin Marinas : > On Thu, Apr 06, 2017 at 12:52:13PM +0530, Imran Khan wrote: >> On 4/5/2017 10:13 AM, Imran Khan wrote: >> >> We may have to revisit this logic and consider L1_CACHE_BYTES the >> >> _minimum_ of cache line sizes in arm64

Re: [PATCH] Revert "arm64: Increase the max granular size"

2017-04-06 Thread Ganesh Mahendran
2017-04-06 23:58 GMT+08:00 Catalin Marinas : > On Thu, Apr 06, 2017 at 12:52:13PM +0530, Imran Khan wrote: >> On 4/5/2017 10:13 AM, Imran Khan wrote: >> >> We may have to revisit this logic and consider L1_CACHE_BYTES the >> >> _minimum_ of cache line sizes in arm64 systems supported by the

Re: tty crash in tty_ldisc_receive_buf()

2017-04-06 Thread Michael Neuling
> > + /* This probably shouldn't happen, but return 0 data processed */ > > + if (!ldata) > > + return 0; > > + > >   while (1) { > >   /* > >    * When PARMRK is set, each input char may take up to 3 > > chars > > Maybe your patch should looks like: > +

Re: tty crash in tty_ldisc_receive_buf()

2017-04-06 Thread Michael Neuling
> > + /* This probably shouldn't happen, but return 0 data processed */ > > + if (!ldata) > > + return 0; > > + > >   while (1) { > >   /* > >    * When PARMRK is set, each input char may take up to 3 > > chars > > Maybe your patch should looks like: > +

Re: [HMM 14/16] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE

2017-04-06 Thread Jerome Glisse
On Fri, Apr 07, 2017 at 11:37:34AM +1000, Balbir Singh wrote: > On Wed, 2017-04-05 at 16:40 -0400, Jérôme Glisse wrote: > > This introduce a simple struct and associated helpers for device driver > > to use when hotpluging un-addressable device memory as ZONE_DEVICE. It > > will find a unuse

Re: [HMM 14/16] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE

2017-04-06 Thread Jerome Glisse
On Fri, Apr 07, 2017 at 11:37:34AM +1000, Balbir Singh wrote: > On Wed, 2017-04-05 at 16:40 -0400, Jérôme Glisse wrote: > > This introduce a simple struct and associated helpers for device driver > > to use when hotpluging un-addressable device memory as ZONE_DEVICE. It > > will find a unuse

Re: [PATCH v5 1/2] module: verify address is read-only

2017-04-06 Thread Jessica Yu
+++ Eddie Kovsky [05/04/17 21:35 -0600]: Implement a mechanism to check if a module's address is in the rodata or ro_after_init sections. It mimics the existing functions that test if an address is inside a module's text section. Functions that take a module as an argument will be able to

Re: [PATCH v5 1/2] module: verify address is read-only

2017-04-06 Thread Jessica Yu
+++ Eddie Kovsky [05/04/17 21:35 -0600]: Implement a mechanism to check if a module's address is in the rodata or ro_after_init sections. It mimics the existing functions that test if an address is inside a module's text section. Functions that take a module as an argument will be able to

Re: [PATCH v2 0/4] zram: implement deduplication in zram

2017-04-06 Thread Joonsoo Kim
On Fri, Mar 31, 2017 at 08:40:56AM +0900, Minchan Kim wrote: > Hi Andrew and Joonsoo, > > On Thu, Mar 30, 2017 at 03:25:02PM -0700, Andrew Morton wrote: > > On Thu, 30 Mar 2017 14:38:05 +0900 js1...@gmail.com wrote: > > > > > This patchset implements deduplication feature in zram. Motivation > >

Re: [PATCH v2 0/4] zram: implement deduplication in zram

2017-04-06 Thread Joonsoo Kim
On Fri, Mar 31, 2017 at 08:40:56AM +0900, Minchan Kim wrote: > Hi Andrew and Joonsoo, > > On Thu, Mar 30, 2017 at 03:25:02PM -0700, Andrew Morton wrote: > > On Thu, 30 Mar 2017 14:38:05 +0900 js1...@gmail.com wrote: > > > > > This patchset implements deduplication feature in zram. Motivation > >

[PATCH v2] cgroup: move cgroup_subsys_state parent field for cache locality

2017-04-06 Thread Todd Poynor
From: Todd Poynor Various structures embed a struct cgroup_subsys_state, typically at the top of the containing structure. It is common for code that accesses the structures to perform operations that iterate over the chain of parent css pointers, also accessing data in

[PATCH v2] cgroup: move cgroup_subsys_state parent field for cache locality

2017-04-06 Thread Todd Poynor
From: Todd Poynor Various structures embed a struct cgroup_subsys_state, typically at the top of the containing structure. It is common for code that accesses the structures to perform operations that iterate over the chain of parent css pointers, also accessing data in each containing

[PATCH 0/5] arm64: dts: hisi: add NIC, RoCE and SAS support for hip07

2017-04-06 Thread Wei.Xu
This patch series adds Mbigen, NIC, RoCE and SAS nodes for the hip07 SoC and enables the NIC, RoCE and SAS on the hip07 d05 board. Wei Xu (5): arm64: dts: hisi: add mbigen nodes for the hip07 SoC arm64: dts: hisi: add network related nodes for the hip07 SoC arm64: dts: hisi: add RoCE nodes

[PATCH 0/5] arm64: dts: hisi: add NIC, RoCE and SAS support for hip07

2017-04-06 Thread Wei.Xu
This patch series adds Mbigen, NIC, RoCE and SAS nodes for the hip07 SoC and enables the NIC, RoCE and SAS on the hip07 d05 board. Wei Xu (5): arm64: dts: hisi: add mbigen nodes for the hip07 SoC arm64: dts: hisi: add network related nodes for the hip07 SoC arm64: dts: hisi: add RoCE nodes

[PATCH 1/5] arm64: dts: hisi: add mbigen nodes for the hip07 SoC

2017-04-06 Thread Wei.Xu
From: Wei Xu Add mbigen nodes for the hip07 SoC those will be used for the SAS, XGE and PCIe host controllers. Signed-off-by: Wei Xu --- arch/arm64/boot/dts/hisilicon/hip07.dtsi | 61 1 file changed, 61 insertions(+)

[PATCH 1/5] arm64: dts: hisi: add mbigen nodes for the hip07 SoC

2017-04-06 Thread Wei.Xu
From: Wei Xu Add mbigen nodes for the hip07 SoC those will be used for the SAS, XGE and PCIe host controllers. Signed-off-by: Wei Xu --- arch/arm64/boot/dts/hisilicon/hip07.dtsi | 61 1 file changed, 61 insertions(+) diff --git

Re: [HMM 14/16] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE

2017-04-06 Thread Balbir Singh
On Wed, 2017-04-05 at 16:40 -0400, Jérôme Glisse wrote: > This introduce a simple struct and associated helpers for device driver > to use when hotpluging un-addressable device memory as ZONE_DEVICE. It > will find a unuse physical address range and trigger memory hotplug for > it which allocates

Re: [HMM 14/16] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE

2017-04-06 Thread Balbir Singh
On Wed, 2017-04-05 at 16:40 -0400, Jérôme Glisse wrote: > This introduce a simple struct and associated helpers for device driver > to use when hotpluging un-addressable device memory as ZONE_DEVICE. It > will find a unuse physical address range and trigger memory hotplug for > it which allocates

[PATCH 2/5] arm64: dts: hisi: add network related nodes for the hip07 SoC

2017-04-06 Thread Wei.Xu
From: Wei Xu Add MDIO, SerDes, Port and realted HNS nodes to support the network on the hip07 SoC. Signed-off-by: Wei Xu --- arch/arm64/boot/dts/hisilicon/hip07.dtsi | 208 +++ 1 file changed, 208 insertions(+) diff

[PATCH 2/5] arm64: dts: hisi: add network related nodes for the hip07 SoC

2017-04-06 Thread Wei.Xu
From: Wei Xu Add MDIO, SerDes, Port and realted HNS nodes to support the network on the hip07 SoC. Signed-off-by: Wei Xu --- arch/arm64/boot/dts/hisilicon/hip07.dtsi | 208 +++ 1 file changed, 208 insertions(+) diff --git a/arch/arm64/boot/dts/hisilicon/hip07.dtsi

  1   2   3   4   5   6   7   8   9   10   >