Re: [PATCH v9 04/38] x86/CPU/AMD: Add the Secure Memory Encryption CPU feature

On Tue, Jul 11, 2017 at 01:07:46AM -0400, Brian Gerst wrote: > > If I make the scattered feature support conditional on CONFIG_X86_64 > > (based on comment below) then cpu_has() will always be false unless > > CONFIG_X86_64 is enabled. So this won't need to be wrapped by the > > #ifdef. > > If

Re: [PATCH v9 04/38] x86/CPU/AMD: Add the Secure Memory Encryption CPU feature

On Tue, Jul 11, 2017 at 01:07:46AM -0400, Brian Gerst wrote: > > If I make the scattered feature support conditional on CONFIG_X86_64 > > (based on comment below) then cpu_has() will always be false unless > > CONFIG_X86_64 is enabled. So this won't need to be wrapped by the > > #ifdef. > > If

Re: [PATCH] net: chelsio: cxgb3: constify attribute_group structures.

Hi Joe, On Tuesday 11 July 2017 11:17 AM, Joe Perches wrote: On Tue, 2017-07-11 at 11:11 +0530, Arvind Yadav wrote: Hi Joe, On Monday 10 July 2017 10:30 PM, Joe Perches wrote: On Mon, 2017-07-10 at 16:04 +0530, Arvind Yadav wrote: attribute_groups are not supposed to change at runtime.

Re: [PATCH] net: chelsio: cxgb3: constify attribute_group structures.

Hi Joe, On Tuesday 11 July 2017 11:17 AM, Joe Perches wrote: On Tue, 2017-07-11 at 11:11 +0530, Arvind Yadav wrote: Hi Joe, On Monday 10 July 2017 10:30 PM, Joe Perches wrote: On Mon, 2017-07-10 at 16:04 +0530, Arvind Yadav wrote: attribute_groups are not supposed to change at runtime.

Re: [PATCH] net: chelsio: cxgb3: constify attribute_group structures.

On Tue, 2017-07-11 at 11:11 +0530, Arvind Yadav wrote: > Hi Joe, > > > On Monday 10 July 2017 10:30 PM, Joe Perches wrote: > > On Mon, 2017-07-10 at 16:04 +0530, Arvind Yadav wrote: > > > attribute_groups are not supposed to change at runtime. All functions > > > working with attribute_groups

Re: [PATCH] net: chelsio: cxgb3: constify attribute_group structures.

On Tue, 2017-07-11 at 11:11 +0530, Arvind Yadav wrote: > Hi Joe, > > > On Monday 10 July 2017 10:30 PM, Joe Perches wrote: > > On Mon, 2017-07-10 at 16:04 +0530, Arvind Yadav wrote: > > > attribute_groups are not supposed to change at runtime. All functions > > > working with attribute_groups

Re: [PATCH] net: chelsio: cxgb3: constify attribute_group structures.

Hi Joe, On Monday 10 July 2017 10:30 PM, Joe Perches wrote: On Mon, 2017-07-10 at 16:04 +0530, Arvind Yadav wrote: attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as

Re: [PATCH] net: chelsio: cxgb3: constify attribute_group structures.

Hi Joe, On Monday 10 July 2017 10:30 PM, Joe Perches wrote: On Mon, 2017-07-10 at 16:04 +0530, Arvind Yadav wrote: attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as

Re: [greybus-dev] [PATCH v2] staging: greybus: arche: wrap over-length lines

On Mon, 2017-07-10 at 15:01 +0530, Viresh Kumar wrote: > On 10-07-17, 11:30, Frans Klaver wrote: > > On Mon, Jul 10, 2017 at 6:46 AM, Viresh Kumar > > wrote: > > > Hi Mitchell, > > > > > > On 09-07-17, 20:25, Mitchell Tasman wrote: > > > > Adjust formatting of various

Re: [greybus-dev] [PATCH v2] staging: greybus: arche: wrap over-length lines

On Mon, 2017-07-10 at 15:01 +0530, Viresh Kumar wrote: > On 10-07-17, 11:30, Frans Klaver wrote: > > On Mon, Jul 10, 2017 at 6:46 AM, Viresh Kumar > > wrote: > > > Hi Mitchell, > > > > > > On 09-07-17, 20:25, Mitchell Tasman wrote: > > > > Adjust formatting of various statements to keep line

Re: [PATCH v2 4/6] cpufreq: schedutil: update CFS util only if used

On Mon, Jul 10, 2017 at 10:49 AM, Vikram Mulukutla wrote: [..] > >>> Given that the utilization update hooks are called with the per-cpu rq >>> lock >>> held (for all classes), I don't think PELT utilization can change >>> throughout >>> the lifetime of the

Re: [PATCH v2 4/6] cpufreq: schedutil: update CFS util only if used

On Mon, Jul 10, 2017 at 10:49 AM, Vikram Mulukutla wrote: [..] > >>> Given that the utilization update hooks are called with the per-cpu rq >>> lock >>> held (for all classes), I don't think PELT utilization can change >>> throughout >>> the lifetime of the cpufreq_update_{util,this_cpu} call?

Re: [PATCH V4 5/6] iommu/arm-smmu: Add support for MMU40x/500 clocks

Hi Rob, On 07/10/2017 09:07 AM, Rob Herring wrote: On Thu, Jul 06, 2017 at 03:07:04PM +0530, Vivek Gautam wrote: From: Sricharan R The MMU400x/500 is the implementation of the SMMUv2 arch specification. It is split in to two blocks TBU, TCU. TBU caches the page

Re: [PATCH V4 5/6] iommu/arm-smmu: Add support for MMU40x/500 clocks

Hi Rob, On 07/10/2017 09:07 AM, Rob Herring wrote: On Thu, Jul 06, 2017 at 03:07:04PM +0530, Vivek Gautam wrote: From: Sricharan R The MMU400x/500 is the implementation of the SMMUv2 arch specification. It is split in to two blocks TBU, TCU. TBU caches the page table, instantiated for each

Re: [PATCH 1/3] ASoC: codec: cpcap: new codec

* Mark Brown [170710 10:52]: > On Fri, Jul 07, 2017 at 06:42:27PM +0200, Sebastian Reichel wrote: > > +#ifdef CONFIG_OF > > +static const struct of_device_id cpcap_audio_of_match[] = { > > + { .compatible = "motorola,cpcap-audio-codec", }, > > + {}, > > +}; > >

Re: [PATCH 1/3] ASoC: codec: cpcap: new codec

* Mark Brown [170710 10:52]: > On Fri, Jul 07, 2017 at 06:42:27PM +0200, Sebastian Reichel wrote: > > +#ifdef CONFIG_OF > > +static const struct of_device_id cpcap_audio_of_match[] = { > > + { .compatible = "motorola,cpcap-audio-codec", }, > > + {}, > > +}; > > +MODULE_DEVICE_TABLE(of,

Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient

Hi Juri, On Mon, Jul 10, 2017 at 3:55 AM, Juri Lelli wrote: > Hi Joel, > > On 09/07/17 10:08, Joel Fernandes wrote: >> Currently the iowait_boost feature in schedutil makes the frequency go to >> max. >> This feature was added to handle a case that Peter described where the

Re: [PATCH RFC v4] cpufreq: schedutil: Make iowait boost more energy efficient

Hi Juri, On Mon, Jul 10, 2017 at 3:55 AM, Juri Lelli wrote: > Hi Joel, > > On 09/07/17 10:08, Joel Fernandes wrote: >> Currently the iowait_boost feature in schedutil makes the frequency go to >> max. >> This feature was added to handle a case that Peter described where the >> throughput of

Re: [PATCH v9 04/38] x86/CPU/AMD: Add the Secure Memory Encryption CPU feature

On Mon, Jul 10, 2017 at 3:41 PM, Tom Lendacky wrote: > On 7/8/2017 7:50 AM, Brian Gerst wrote: >> >> On Fri, Jul 7, 2017 at 9:38 AM, Tom Lendacky >> wrote: >>> >>> Update the CPU features to include identifying and reporting on the >>> Secure

Re: [PATCH v9 04/38] x86/CPU/AMD: Add the Secure Memory Encryption CPU feature

On Mon, Jul 10, 2017 at 3:41 PM, Tom Lendacky wrote: > On 7/8/2017 7:50 AM, Brian Gerst wrote: >> >> On Fri, Jul 7, 2017 at 9:38 AM, Tom Lendacky >> wrote: >>> >>> Update the CPU features to include identifying and reporting on the >>> Secure Memory Encryption (SME) feature. SME is identified

Re: sun4v+DMA related boot crash on 4.13-git

> > > I tested yesterdayd 4.12+git on sparc64 to see if the sparc merge works > > > fine, and on all of my sun4v machines (T1000, T2000, T5120) it crashed > > > on boot with DMA-related stacktrace (below). Allt he machines are sun4v > > > physical machines, not VM-s. Older sun4 machines do not

Re: sun4v+DMA related boot crash on 4.13-git

> > > I tested yesterdayd 4.12+git on sparc64 to see if the sparc merge works > > > fine, and on all of my sun4v machines (T1000, T2000, T5120) it crashed > > > on boot with DMA-related stacktrace (below). Allt he machines are sun4v > > > physical machines, not VM-s. Older sun4 machines do not

Re: [PATCH 5/5] powernv:idle: Disable LOSE_FULL_CONTEXT states when stop-api fails.

On Sat, Jul 08, 2017 at 07:05:26PM +1000, Nicholas Piggin wrote: > On Fri, 7 Jul 2017 23:07:10 +0530 > Gautham R Shenoy wrote: > > > On Fri, Jul 07, 2017 at 01:29:16AM +1000, Nicholas Piggin wrote: > > > On Wed, 5 Jul 2017 22:08:16 +0530 > > > "Gautham R. Shenoy"

Re: [PATCH 5/5] powernv:idle: Disable LOSE_FULL_CONTEXT states when stop-api fails.

On Sat, Jul 08, 2017 at 07:05:26PM +1000, Nicholas Piggin wrote: > On Fri, 7 Jul 2017 23:07:10 +0530 > Gautham R Shenoy wrote: > > > On Fri, Jul 07, 2017 at 01:29:16AM +1000, Nicholas Piggin wrote: > > > On Wed, 5 Jul 2017 22:08:16 +0530 > > > "Gautham R. Shenoy" wrote: > > > > > > > From:

Re: [PATCH v2 3/4] btrfs: Add zstd support

On 7/10/17, 5:36 AM, "Austin S. Hemmelgarn" wrote: > On 2017-07-07 23:07, Adam Borowski wrote: >> On Sat, Jul 08, 2017 at 01:40:18AM +0200, Adam Borowski wrote: >>> On Fri, Jul 07, 2017 at 11:17:49PM +, Nick Terrell wrote: On 7/6/17, 9:32 AM, "Adam Borowski"

Re: [PATCH v2 3/4] btrfs: Add zstd support

On 7/10/17, 5:36 AM, "Austin S. Hemmelgarn" wrote: > On 2017-07-07 23:07, Adam Borowski wrote: >> On Sat, Jul 08, 2017 at 01:40:18AM +0200, Adam Borowski wrote: >>> On Fri, Jul 07, 2017 at 11:17:49PM +, Nick Terrell wrote: On 7/6/17, 9:32 AM, "Adam Borowski" wrote: > Got a

Re: [PATCH v9 07/38] x86/mm: Remove phys_to_virt() usage in ioremap()

On Mon, Jul 10, 2017 at 3:50 PM, Tom Lendacky wrote: > On 7/8/2017 7:57 AM, Brian Gerst wrote: >> >> On Fri, Jul 7, 2017 at 9:39 AM, Tom Lendacky >> wrote: >>> >>> Currently there is a check if the address being mapped is in the ISA >>> range

Re: [PATCH v9 07/38] x86/mm: Remove phys_to_virt() usage in ioremap()

On Mon, Jul 10, 2017 at 3:50 PM, Tom Lendacky wrote: > On 7/8/2017 7:57 AM, Brian Gerst wrote: >> >> On Fri, Jul 7, 2017 at 9:39 AM, Tom Lendacky >> wrote: >>> >>> Currently there is a check if the address being mapped is in the ISA >>> range (is_ISA_range()), and if it is, then phys_to_virt()

linux-next: Tree for Jul 11

Hi all, Please do not add any v4.14 material to you linux-next included branches until after v4.13-rc1 has been released. Changes since 20170710: The mips tree gained a conflict against Linus' tree. The vfs tree lost its build failures but gained another for which I applied a fix patch

linux-next: Tree for Jul 11

Hi all, Please do not add any v4.14 material to you linux-next included branches until after v4.13-rc1 has been released. Changes since 20170710: The mips tree gained a conflict against Linus' tree. The vfs tree lost its build failures but gained another for which I applied a fix patch

Re: [PATCH v2 1/3] of: overlay: add overlay unittest data for node names and symbols

On 07/10/17 19:31, Rob Herring wrote: > On Mon, Jul 10, 2017 at 2:05 PM, wrote: >> From: Frank Rowand >> >> Add nodes and properties to overlay_base and overlay dts files to >> test for >>- incorrect existing node name detection when overlay

Re: [PATCH v2 1/3] of: overlay: add overlay unittest data for node names and symbols

On 07/10/17 19:31, Rob Herring wrote: > On Mon, Jul 10, 2017 at 2:05 PM, wrote: >> From: Frank Rowand >> >> Add nodes and properties to overlay_base and overlay dts files to >> test for >>- incorrect existing node name detection when overlay node name >> has a unit-address >>-

Re: [RFC PATCH v1 00/11] Create fast idle path for short idle periods

On 2017/7/11 1:27, Andi Kleen wrote: > On Mon, Jul 10, 2017 at 06:42:06PM +0200, Peter Zijlstra wrote: >> On Mon, Jul 10, 2017 at 07:46:09AM -0700, Andi Kleen wrote: So how much of the gain is simply due to skipping NOHZ? Mike used to carry a patch that would throttle NOHZ. And that is a

Re: [RFC PATCH v1 00/11] Create fast idle path for short idle periods

On 2017/7/11 1:27, Andi Kleen wrote: > On Mon, Jul 10, 2017 at 06:42:06PM +0200, Peter Zijlstra wrote: >> On Mon, Jul 10, 2017 at 07:46:09AM -0700, Andi Kleen wrote: So how much of the gain is simply due to skipping NOHZ? Mike used to carry a patch that would throttle NOHZ. And that is a

Re: [RFC] mm/mremap: Remove redundant checks inside vma_expandable()

On 07/10/2017 07:19 PM, Michal Hocko wrote: > On Mon 10-07-17 16:40:59, Anshuman Khandual wrote: >> As 'delta' is an unsigned long, 'end' (vma->vm_end + delta) cannot >> be less than 'vma->vm_end'. > > This just doesn't make any sense. This is exactly what the overflow > check is for. Maybe

Re: [RFC] mm/mremap: Remove redundant checks inside vma_expandable()

On 07/10/2017 07:19 PM, Michal Hocko wrote: > On Mon 10-07-17 16:40:59, Anshuman Khandual wrote: >> As 'delta' is an unsigned long, 'end' (vma->vm_end + delta) cannot >> be less than 'vma->vm_end'. > > This just doesn't make any sense. This is exactly what the overflow > check is for. Maybe

Re: [RFC] mm/mremap: Remove redundant checks inside vma_expandable()

On 07/10/2017 07:19 PM, Michal Hocko wrote: > On Mon 10-07-17 16:40:59, Anshuman Khandual wrote: >> As 'delta' is an unsigned long, 'end' (vma->vm_end + delta) cannot >> be less than 'vma->vm_end'. > > This just doesn't make any sense. This is exactly what the overflow > check is for. Maybe

Re: [RFC] mm/mremap: Remove redundant checks inside vma_expandable()

On 07/10/2017 07:19 PM, Michal Hocko wrote: > On Mon 10-07-17 16:40:59, Anshuman Khandual wrote: >> As 'delta' is an unsigned long, 'end' (vma->vm_end + delta) cannot >> be less than 'vma->vm_end'. > > This just doesn't make any sense. This is exactly what the overflow > check is for. Maybe

Re: [RFC v5 01/11] mm: Dont assume page-table invariance during faults

On Mon, 10 Jul 2017 19:48:43 +0200 Laurent Dufour wrote: > On 07/07/2017 09:07, Balbir Singh wrote: > > On Fri, 2017-06-16 at 19:52 +0200, Laurent Dufour wrote: > >> From: Peter Zijlstra > >> > >> One of the side effects of speculating on

Re: [RFC v5 01/11] mm: Dont assume page-table invariance during faults

On Mon, 10 Jul 2017 19:48:43 +0200 Laurent Dufour wrote: > On 07/07/2017 09:07, Balbir Singh wrote: > > On Fri, 2017-06-16 at 19:52 +0200, Laurent Dufour wrote: > >> From: Peter Zijlstra > >> > >> One of the side effects of speculating on faults (without holding > >> mmap_sem) is that we can

Re: [PATCH 3/3] Make LSM Writable Hooks a command line option

Hi Igor, [auto build test ERROR on linus/master] [cannot apply to v4.12] [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/Igor-Stoppa/mm-security-ro-protection-for-dynamic-data/20170711-084116

Re: [PATCH 3/3] Make LSM Writable Hooks a command line option

Hi Igor, [auto build test ERROR on linus/master] [cannot apply to v4.12] [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/Igor-Stoppa/mm-security-ro-protection-for-dynamic-data/20170711-084116

Re: [PATCH 2/5] mm/device-public-memory: device memory cache coherent with CPU v2

On Mon, 3 Jul 2017 17:14:12 -0400 Jérôme Glisse wrote: > Platform with advance system bus (like CAPI or CCIX) allow device > memory to be accessible from CPU in a cache coherent fashion. Add > a new type of ZONE_DEVICE to represent such memory. The use case > are the same as

Re: [PATCH 2/5] mm/device-public-memory: device memory cache coherent with CPU v2

On Mon, 3 Jul 2017 17:14:12 -0400 Jérôme Glisse wrote: > Platform with advance system bus (like CAPI or CCIX) allow device > memory to be accessible from CPU in a cache coherent fashion. Add > a new type of ZONE_DEVICE to represent such memory. The use case > are the same as for the

Re: [PATCH] printk: Modify operators of printed_len

hi Petr > I just noticed that the same applies also to text_len > variable. Well, it was caused by another commit ddb9baa822265b55 > ("printk: report lost messages in printk safe/nmi contexts"). > Could you please send a patch for this as well? sure and it is my pleasure. > > This seems to be

Re: [PATCH] printk: Modify operators of printed_len

hi Petr > I just noticed that the same applies also to text_len > variable. Well, it was caused by another commit ddb9baa822265b55 > ("printk: report lost messages in printk safe/nmi contexts"). > Could you please send a patch for this as well? sure and it is my pleasure. > > This seems to be

[PATCH] staging: unisys: visorbus: fix function open braces

Resolve multiple checkpatch errors by relocating open braces following function definitions to the next line. Signed-off-by: Mitchell Tasman --- drivers/staging/unisys/visorbus/visorbus_main.c | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff

[PATCH] staging: unisys: visorbus: fix function open braces

Resolve multiple checkpatch errors by relocating open braces following function definitions to the next line. Signed-off-by: Mitchell Tasman --- drivers/staging/unisys/visorbus/visorbus_main.c | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git

Re: [PATCH 1/5] mm/persistent-memory: match IORES_DESC name and enum memory_type one

On Wed, 5 Jul 2017 14:49:33 -0400 Jerome Glisse wrote: > On Wed, Jul 05, 2017 at 09:15:35AM -0700, Dan Williams wrote: > > On Wed, Jul 5, 2017 at 7:25 AM, Jerome Glisse wrote: > > > On Mon, Jul 03, 2017 at 04:49:18PM -0700, Dan Williams wrote: > > >>

Re: [PATCH 1/5] mm/persistent-memory: match IORES_DESC name and enum memory_type one

On Wed, 5 Jul 2017 14:49:33 -0400 Jerome Glisse wrote: > On Wed, Jul 05, 2017 at 09:15:35AM -0700, Dan Williams wrote: > > On Wed, Jul 5, 2017 at 7:25 AM, Jerome Glisse wrote: > > > On Mon, Jul 03, 2017 at 04:49:18PM -0700, Dan Williams wrote: > > >> On Mon, Jul 3, 2017 at 2:14 PM, Jérôme

[git pull] m68knommu changes for v4.13

Hi Linus, Can you please pull the m68knommu git tree, for-next branch. Only a single change, to remove old Kconfig options from defconfigs. Regards Greg The following changes since commit c0bc126f97fb929b3ae02c1c62322645d70eb408: Linux 4.12-rc7 (2017-06-25 18:30:05 -0700) are available

[git pull] m68knommu changes for v4.13

Hi Linus, Can you please pull the m68knommu git tree, for-next branch. Only a single change, to remove old Kconfig options from defconfigs. Regards Greg The following changes since commit c0bc126f97fb929b3ae02c1c62322645d70eb408: Linux 4.12-rc7 (2017-06-25 18:30:05 -0700) are available

Re: [PATCH] input: serio: constify attribute_group structures.

On Wed, Jul 05, 2017 at 03:12:53PM +0530, Arvind Yadav wrote: > attribute_groups are not supposed to change at runtime. All functions > working with attribute_groups provided by work with const > attribute_group. So mark the non-const structs as const. > > File size before: >text

Re: [PATCH] input: serio: constify attribute_group structures.

On Wed, Jul 05, 2017 at 03:12:53PM +0530, Arvind Yadav wrote: > attribute_groups are not supposed to change at runtime. All functions > working with attribute_groups provided by work with const > attribute_group. So mark the non-const structs as const. > > File size before: >text

I am Rv.Father paul Olo,

RE:ATTN:PAYMENT NOTIFICATION! 10/7/2017 GOOD DAY, I am Rv.Father paul Olo. This is to bring to your notice that, I have paid the DHL courier Service charges and the delivery of your ATM CARD.I paid it because the ATM CARD worth {USD$10.5M}has less Four weeks and four days to expire and when

I am Rv.Father paul Olo,

RE:ATTN:PAYMENT NOTIFICATION! 10/7/2017 GOOD DAY, I am Rv.Father paul Olo. This is to bring to your notice that, I have paid the DHL courier Service charges and the delivery of your ATM CARD.I paid it because the ATM CARD worth {USD$10.5M}has less Four weeks and four days to expire and when

Re: [greybus-dev] [PATCH v3] staging: greybus: arche: wrap over-length lines

On 10-07-17, 23:14, Mitchell Tasman wrote: > Adjust formatting of several comments to keep line length within > the 80 column limit preferred by the Linux kernel coding style. > > Signed-off-by: Mitchell Tasman > --- > Changes in v3: Narrow scope of patch per Viresh Kumar's

Re: [greybus-dev] [PATCH v3] staging: greybus: arche: wrap over-length lines

On 10-07-17, 23:14, Mitchell Tasman wrote: > Adjust formatting of several comments to keep line length within > the 80 column limit preferred by the Linux kernel coding style. > > Signed-off-by: Mitchell Tasman > --- > Changes in v3: Narrow scope of patch per Viresh Kumar's feedback > Changes in

[GIT PULL] chrome-platform updates for v4.13

Hi Linus, Please pull chrome-platform updates for Linux v4.13 from signed tag: git://git.kernel.org/pub/scm/linux/kernel/git/bleung/chrome-platform.git tags/chrome-platform-for-linus-4.13 Sorry for the delay on getting this into the merge window. My first merge window as maintainer. Thanks,

[GIT PULL] chrome-platform updates for v4.13

Hi Linus, Please pull chrome-platform updates for Linux v4.13 from signed tag: git://git.kernel.org/pub/scm/linux/kernel/git/bleung/chrome-platform.git tags/chrome-platform-for-linus-4.13 Sorry for the delay on getting this into the merge window. My first merge window as maintainer. Thanks,

[PATCH v3] staging: greybus: arche: wrap over-length lines

Adjust formatting of several comments to keep line length within the 80 column limit preferred by the Linux kernel coding style. Signed-off-by: Mitchell Tasman --- Changes in v3: Narrow scope of patch per Viresh Kumar's feedback Changes in v2: Add back a missing space in a

[PATCH v3] staging: greybus: arche: wrap over-length lines

Adjust formatting of several comments to keep line length within the 80 column limit preferred by the Linux kernel coding style. Signed-off-by: Mitchell Tasman --- Changes in v3: Narrow scope of patch per Viresh Kumar's feedback Changes in v2: Add back a missing space in a comment

Re: [PATCH v6 1/7] perf/core: Define the common branch type classification

On 7/11/2017 10:28 AM, Michael Ellerman wrote: "Jin, Yao" writes: On 7/10/2017 9:46 PM, Peter Zijlstra wrote: On Mon, Jul 10, 2017 at 08:10:50AM -0500, Segher Boessenkool wrote: PERF_BR_INT is triggered by instruction "int" . PERF_BR_IRQ is triggered by

Re: [PATCH v6 1/7] perf/core: Define the common branch type classification

On 7/11/2017 10:28 AM, Michael Ellerman wrote: "Jin, Yao" writes: On 7/10/2017 9:46 PM, Peter Zijlstra wrote: On Mon, Jul 10, 2017 at 08:10:50AM -0500, Segher Boessenkool wrote: PERF_BR_INT is triggered by instruction "int" . PERF_BR_IRQ is triggered by interrupts, traps, faults (the

Re: [PATCH v2 4/8] objtool: add undwarf debuginfo generation

On Fri, Jul 07, 2017 at 11:44:37AM +0200, Ingo Molnar wrote: > > * Josh Poimboeuf wrote: > > > On Thu, Jun 29, 2017 at 10:06:52AM -0500, Josh Poimboeuf wrote: > > > On Thu, Jun 29, 2017 at 04:46:18PM +0200, Ingo Molnar wrote: > > > > > > > > * Josh Poimboeuf

Re: [PATCH v2 4/8] objtool: add undwarf debuginfo generation

On Fri, Jul 07, 2017 at 11:44:37AM +0200, Ingo Molnar wrote: > > * Josh Poimboeuf wrote: > > > On Thu, Jun 29, 2017 at 10:06:52AM -0500, Josh Poimboeuf wrote: > > > On Thu, Jun 29, 2017 at 04:46:18PM +0200, Ingo Molnar wrote: > > > > > > > > * Josh Poimboeuf wrote: > > > > > > > > > > Plus,

Re: [PATCH v2 2/2] dt: Add bindings for IDT VersaClock 5P49V5925

On Sun, Jul 09, 2017 at 08:40:05PM +0300, Vladimir Barinov wrote: > From: Vladimir Barinov > > IDT VersaClock 5 5P49V5925 has 5 clock outputs, 4 fractional dividers. > Input clock source can be taken only from external reference clock. > >

Re: [PATCH v2 2/2] dt: Add bindings for IDT VersaClock 5P49V5925

On Sun, Jul 09, 2017 at 08:40:05PM +0300, Vladimir Barinov wrote: > From: Vladimir Barinov > > IDT VersaClock 5 5P49V5925 has 5 clock outputs, 4 fractional dividers. > Input clock source can be taken only from external reference clock. > > Signed-off-by: Vladimir Barinov > --- > Changes in

Re: [PATCH v4 1/3] cpufreq: mediatek: Add support of cpufreq to MT2701/MT7623 SoC

Hi Sean, On Mon, 2017-07-10 at 22:23 +0800, sean.w...@mediatek.com wrote: > From: Sean Wang > > MT2701/MT7623 is a 32-bit ARMv7 based quad-core (4 * Cortex-A7) with > single cluster and this hardware is also compatible with the existing > driver through enabling CPU

Re: [PATCH v4 1/3] cpufreq: mediatek: Add support of cpufreq to MT2701/MT7623 SoC

Hi Sean, On Mon, 2017-07-10 at 22:23 +0800, sean.w...@mediatek.com wrote: > From: Sean Wang > > MT2701/MT7623 is a 32-bit ARMv7 based quad-core (4 * Cortex-A7) with > single cluster and this hardware is also compatible with the existing > driver through enabling CPU frequency feature with

Re: [PATCH RFC 0/2] KVM: x86: Support using the VMX preemption timer for APIC Timer periodic/oneshot mode

2017-07-11 8:13 GMT+08:00 Andy Lutomirski : > On 10/11/2016 05:17 AM, Wanpeng Li wrote: >> >> Most windows guests which I have on hand currently still utilize APIC >> Timer >> periodic/oneshot mode instead of APIC Timer tsc-deadline mode: >> - windows 2008 server r2 >> - windows

Re: [PATCH RFC 0/2] KVM: x86: Support using the VMX preemption timer for APIC Timer periodic/oneshot mode

2017-07-11 8:13 GMT+08:00 Andy Lutomirski : > On 10/11/2016 05:17 AM, Wanpeng Li wrote: >> >> Most windows guests which I have on hand currently still utilize APIC >> Timer >> periodic/oneshot mode instead of APIC Timer tsc-deadline mode: >> - windows 2008 server r2 >> - windows 2012 server r2 >>

[PATCH] clk: mediatek: fixed static checker warning in clk_cpumux_get_parent call

From: Sean Wang Fixed the signedness bug returning '(-22)' on the return type as u8 with moving the sanity checker into clk_cpumux_set_parent() to ensure always validity in clk_cpumux_get_parent() got called. Fixes: commit 1e17de9049da ("clk: mediatek: add missing cpu

[PATCH] clk: mediatek: fixed static checker warning in clk_cpumux_get_parent call

From: Sean Wang Fixed the signedness bug returning '(-22)' on the return type as u8 with moving the sanity checker into clk_cpumux_set_parent() to ensure always validity in clk_cpumux_get_parent() got called. Fixes: commit 1e17de9049da ("clk: mediatek: add missing cpu mux causing Mediatek

Re: [PATCH v2 1/3] of: overlay: add overlay unittest data for node names and symbols

On Mon, Jul 10, 2017 at 2:05 PM, wrote: > From: Frank Rowand > > Add nodes and properties to overlay_base and overlay dts files to > test for >- incorrect existing node name detection when overlay node name > has a unit-address >-

Re: [PATCH v2 1/3] of: overlay: add overlay unittest data for node names and symbols

On Mon, Jul 10, 2017 at 2:05 PM, wrote: > From: Frank Rowand > > Add nodes and properties to overlay_base and overlay dts files to > test for >- incorrect existing node name detection when overlay node name > has a unit-address >- adding overlay __symbols__ properties to live tree

Re: [PATCH v6 1/7] perf/core: Define the common branch type classification

"Jin, Yao" writes: > On 7/10/2017 9:46 PM, Peter Zijlstra wrote: >> On Mon, Jul 10, 2017 at 08:10:50AM -0500, Segher Boessenkool wrote: >> PERF_BR_INT is triggered by instruction "int" . PERF_BR_IRQ is triggered by interrupts, traps, faults (the ring 0,3

Re: [PATCH v6 1/7] perf/core: Define the common branch type classification

"Jin, Yao" writes: > On 7/10/2017 9:46 PM, Peter Zijlstra wrote: >> On Mon, Jul 10, 2017 at 08:10:50AM -0500, Segher Boessenkool wrote: >> PERF_BR_INT is triggered by instruction "int" . PERF_BR_IRQ is triggered by interrupts, traps, faults (the ring 0,3 transition). >>> So your

Re: [PATCH] mm/mremap: Document MREMAP_FIXED dependency on MREMAP_MAYMOVE

On 07/10/2017 11:01 PM, Mike Kravetz wrote: > On 07/10/2017 06:41 AM, Michal Hocko wrote: >> On Mon 10-07-17 17:02:11, Anshuman Khandual wrote: >>> In the header file, just specify the dependency of MREMAP_FIXED >>> on MREMAP_MAYMOVE and make it explicit for the user space. >> I really fail to see

Re: [PATCH] mm/mremap: Document MREMAP_FIXED dependency on MREMAP_MAYMOVE

On 07/10/2017 11:01 PM, Mike Kravetz wrote: > On 07/10/2017 06:41 AM, Michal Hocko wrote: >> On Mon 10-07-17 17:02:11, Anshuman Khandual wrote: >>> In the header file, just specify the dependency of MREMAP_FIXED >>> on MREMAP_MAYMOVE and make it explicit for the user space. >> I really fail to see

Re: [patches] Re: [PATCH 01/17] lib: Add shared copies of some GCC library routines

On 07/10/2017 07:09 PM, Palmer Dabbelt wrote: > On Mon, 10 Jul 2017 19:03:44 PDT (-0700), rdun...@infradead.org wrote: >> On 07/10/2017 07:02 PM, Stephen Rothwell wrote: >>> Hi Palmer, >>> >>> On Mon, 10 Jul 2017 18:39:08 -0700 Palmer Dabbelt >>> wrote: This patch

Re: [patches] Re: [PATCH 01/17] lib: Add shared copies of some GCC library routines

On 07/10/2017 07:09 PM, Palmer Dabbelt wrote: > On Mon, 10 Jul 2017 19:03:44 PDT (-0700), rdun...@infradead.org wrote: >> On 07/10/2017 07:02 PM, Stephen Rothwell wrote: >>> Hi Palmer, >>> >>> On Mon, 10 Jul 2017 18:39:08 -0700 Palmer Dabbelt >>> wrote: This patch adds a new copy of

Re: [PATCH v6 1/7] perf/core: Define the common branch type classification

Segher Boessenkool writes: > Hi! > > On Mon, Jul 10, 2017 at 07:46:17PM +0800, Jin, Yao wrote: >> 1. We all agree these definitions: >> >> +PERF_BR_COND= 1,/* conditional */ >> +PERF_BR_UNCOND = 2,/* unconditional */ >> +

Re: [PATCH v6 1/7] perf/core: Define the common branch type classification

Segher Boessenkool writes: > Hi! > > On Mon, Jul 10, 2017 at 07:46:17PM +0800, Jin, Yao wrote: >> 1. We all agree these definitions: >> >> +PERF_BR_COND= 1,/* conditional */ >> +PERF_BR_UNCOND = 2,/* unconditional */ >> +PERF_BR_IND = 3,/*

Re: [PATCH v4 1/4] ARM: dts: imx6ul-geam-kit: Remove re-enabled usdhc1

On Fri, Jun 16, 2017 at 12:34:37PM +0530, Jagan Teki wrote: > From: Jagan Teki > > usdhc1 is enabled and assigned pinctrl-0 on imx6ul-geam.dtsi > but same thing done on imx6ul-geam-kit.dts, so remove this > re-enabled node from the same. > > Signed-off-by: Jagan Teki

Re: [PATCH v4 1/4] ARM: dts: imx6ul-geam-kit: Remove re-enabled usdhc1

On Fri, Jun 16, 2017 at 12:34:37PM +0530, Jagan Teki wrote: > From: Jagan Teki > > usdhc1 is enabled and assigned pinctrl-0 on imx6ul-geam.dtsi > but same thing done on imx6ul-geam-kit.dts, so remove this > re-enabled node from the same. > > Signed-off-by: Jagan Teki Applied all, thanks.

Re: [patches] Re: [PATCH 01/17] lib: Add shared copies of some GCC library routines

On Mon, 10 Jul 2017 19:03:44 PDT (-0700), rdun...@infradead.org wrote: > On 07/10/2017 07:02 PM, Stephen Rothwell wrote: >> Hi Palmer, >> >> On Mon, 10 Jul 2017 18:39:08 -0700 Palmer Dabbelt wrote: >>> >>> This patch adds a new copy of these library routine files, which are

Re: [patches] Re: [PATCH 01/17] lib: Add shared copies of some GCC library routines

On Mon, 10 Jul 2017 19:03:44 PDT (-0700), rdun...@infradead.org wrote: > On 07/10/2017 07:02 PM, Stephen Rothwell wrote: >> Hi Palmer, >> >> On Mon, 10 Jul 2017 18:39:08 -0700 Palmer Dabbelt wrote: >>> >>> This patch adds a new copy of these library routine files, which are >>> functionally

Re: [PATCH 01/17] lib: Add shared copies of some GCC library routines

On Mon, 10 Jul 2017 19:02:19 PDT (-0700), s...@canb.auug.org.au wrote: > Hi Palmer, > > On Mon, 10 Jul 2017 18:39:08 -0700 Palmer Dabbelt wrote: >> >> This patch adds a new copy of these library routine files, which are >> functionally identical to the various other copies.

Re: [PATCH 01/17] lib: Add shared copies of some GCC library routines

On Mon, 10 Jul 2017 19:02:19 PDT (-0700), s...@canb.auug.org.au wrote: > Hi Palmer, > > On Mon, 10 Jul 2017 18:39:08 -0700 Palmer Dabbelt wrote: >> >> This patch adds a new copy of these library routine files, which are >> functionally identical to the various other copies. These are >>

Re: [PATCH] tty: Fix TIOCGPTPEER ioctl definition

This ioctl does nothing to justify an _IOC_READ or _IOC_WRITE flag because it doesn't copy anything from/to userspace to access the argument. Acked-by: Aleksa Sarai Oops, I misunderstood what _IOR means semantically. TIL -- thanks! -- Aleksa Sarai Software Engineer

Re: [PATCH] tty: Fix TIOCGPTPEER ioctl definition

This ioctl does nothing to justify an _IOC_READ or _IOC_WRITE flag because it doesn't copy anything from/to userspace to access the argument. Acked-by: Aleksa Sarai Oops, I misunderstood what _IOR means semantically. TIL -- thanks! -- Aleksa Sarai Software Engineer (Containers) SUSE Linux

Re: [PATCH v2 2/8] exec: Move security_bprm_secureexec() earlier

On Mon, Jul 10, 2017 at 10:18 AM, Eric W. Biederman wrote: > Kees Cook writes: > >> On Mon, Jul 10, 2017 at 1:57 AM, Eric W. Biederman >> wrote: >>> Kees Cook writes: >>> There are several places

Re: [PATCH v2 2/8] exec: Move security_bprm_secureexec() earlier

On Mon, Jul 10, 2017 at 10:18 AM, Eric W. Biederman wrote: > Kees Cook writes: > >> On Mon, Jul 10, 2017 at 1:57 AM, Eric W. Biederman >> wrote: >>> Kees Cook writes: >>> There are several places where exec needs to know if a privilege-gain has happened. These should be using the

Re: [PATCH 1/3] Protectable memory support

Hi Igor, [auto build test WARNING on linus/master] [also build test WARNING on v4.12 next-20170710] [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/Igor-Stoppa/mm-security-ro-protection

Re: [PATCH 1/3] Protectable memory support

Hi Igor, [auto build test WARNING on linus/master] [also build test WARNING on v4.12 next-20170710] [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/Igor-Stoppa/mm-security-ro-protection

Re: [PATCH v4 1/3] ARM: dts: imx6ul-isiot: Move common nodes in imx6ul-isiot.dtsi

On Thu, Jun 15, 2017 at 05:33:37PM +0530, Jagan Teki wrote: > From: Jagan Teki > > Maintaining separate dtsi file with common nodes make unclear and > confusing since -isiot.dtsi is available for adding common nodes. > If the nodes are common between the dts files

Re: [PATCH v4 1/3] ARM: dts: imx6ul-isiot: Move common nodes in imx6ul-isiot.dtsi

On Thu, Jun 15, 2017 at 05:33:37PM +0530, Jagan Teki wrote: > From: Jagan Teki > > Maintaining separate dtsi file with common nodes make unclear and > confusing since -isiot.dtsi is available for adding common nodes. > If the nodes are common between the dts files then mark status > as "okay"

Re: [PATCH 01/17] lib: Add shared copies of some GCC library routines

On 07/10/2017 07:02 PM, Stephen Rothwell wrote: > Hi Palmer, > > On Mon, 10 Jul 2017 18:39:08 -0700 Palmer Dabbelt wrote: >> >> This patch adds a new copy of these library routine files, which are >> functionally identical to the various other copies. These are >> availiable

Re: [PATCH 01/17] lib: Add shared copies of some GCC library routines

On 07/10/2017 07:02 PM, Stephen Rothwell wrote: > Hi Palmer, > > On Mon, 10 Jul 2017 18:39:08 -0700 Palmer Dabbelt wrote: >> >> This patch adds a new copy of these library routine files, which are >> functionally identical to the various other copies. These are >> availiable via Kconfig as

  1   2   3   4   5   6   7   8   9   10   >