On Thu, 18 Oct 2018 15:32:35 +
Michael Kelley wrote:
> From Olaf Hering Sent: Thursday, October 18, 2018 8:20 AM
> >
> > > This extends existing vmbus related sysfs structure to provide per-channel
> > > state information. This is useful when diagnosing issues with multiple
> > > queues
On Thu, 18 Oct 2018 15:32:35 +
Michael Kelley wrote:
> From Olaf Hering Sent: Thursday, October 18, 2018 8:20 AM
> >
> > > This extends existing vmbus related sysfs structure to provide per-channel
> > > state information. This is useful when diagnosing issues with multiple
> > > queues
On Thu, Oct 18, 2018 at 6:18 PM Borislav Petkov wrote:
>
> On Wed, Oct 17, 2018 at 09:40:53PM -0300, Leonardo Bras wrote:
> > The idea was to put it as default and fix all the shadowing warnings.
> > What do you think? I am open to suggestions.
>
> That's Masahiro's call. In the rest of the
On Thu, Oct 18, 2018 at 6:18 PM Borislav Petkov wrote:
>
> On Wed, Oct 17, 2018 at 09:40:53PM -0300, Leonardo Bras wrote:
> > The idea was to put it as default and fix all the shadowing warnings.
> > What do you think? I am open to suggestions.
>
> That's Masahiro's call. In the rest of the
On Thu, 18 Oct 2018 17:19:53 +0200
Olaf Hering wrote:
> Am Sun, 17 Sep 2017 20:54:18 -0700
> schrieb k...@exchange.microsoft.com:
>
> > This extends existing vmbus related sysfs structure to provide per-channel
> > state information. This is useful when diagnosing issues with multiple
> >
On Thu, 18 Oct 2018 17:19:53 +0200
Olaf Hering wrote:
> Am Sun, 17 Sep 2017 20:54:18 -0700
> schrieb k...@exchange.microsoft.com:
>
> > This extends existing vmbus related sysfs structure to provide per-channel
> > state information. This is useful when diagnosing issues with multiple
> >
On 2018-10-12 11:02:18 [-0700], Andy Lutomirski wrote:
> On Fri, Oct 12, 2018 at 10:54 AM Dave Hansen
> wrote:
> >
> > On 10/04/2018 07:05 AM, Sebastian Andrzej Siewior wrote:
> > > The PKRU value is not set for kernel threads because they do not have
> > > the ->initialized value set. As a
On 2018-10-12 11:02:18 [-0700], Andy Lutomirski wrote:
> On Fri, Oct 12, 2018 at 10:54 AM Dave Hansen
> wrote:
> >
> > On 10/04/2018 07:05 AM, Sebastian Andrzej Siewior wrote:
> > > The PKRU value is not set for kernel threads because they do not have
> > > the ->initialized value set. As a
From: Changbin Du
With '-Og' optimization level, GCC would not optimize a count for a loop
as a constant value. But BUILD_BUG_ON() only accept compile-time constant
values. Let's use __fix_to_virt() to avoid the error.
arch/arm/mm/mmu.o: In function `fix_to_virt':
From: Changbin Du
With '-Og' optimization level, GCC would not optimize a count for a loop
as a constant value. But BUILD_BUG_ON() only accept compile-time constant
values. Let's use __fix_to_virt() to avoid the error.
arch/arm/mm/mmu.o: In function `fix_to_virt':
From: Changbin Du
This will apply GCC '-Og' optimization level which is supported
since GCC 4.8. This optimization level offers a reasonable level
of optimization while maintaining fast compilation and a good
debugging experience. It is similar to '-O1' while perferring
to keep debug ability
From: Changbin Du
This will apply GCC '-Og' optimization level which is supported
since GCC 4.8. This optimization level offers a reasonable level
of optimization while maintaining fast compilation and a good
debugging experience. It is similar to '-O1' while perferring
to keep debug ability
From: Changbin Du
The level4_kernel_pgt is only defined when X86_5LEVEL is enabled. So
surround level4_kernel_pgt with #ifdef CONFIG_X86_5LEVEL...#endif to
make code correct.
Signed-off-by: Changbin Du
Acked-by: Steven Rostedt (VMware)
---
arch/x86/include/asm/pgtable_64.h | 2 ++
From: Changbin Du
This patch add a new kernel hacking option NO_AUTO_INLINE. Selecting
this option will prevent the compiler from optimizing the kernel by
auto-inlining functions not marked with the inline keyword.
With this option, only functions explicitly marked with "inline" will
be
Hi all,
I have posted this series several months ago but interrupted by personal
affairs. Now I get time to complete this task. Thanks for all of the
reviewers.
I know some kernel developers was searching for a method to dissable GCC
optimizations, probably they want to apply GCC '-O0' option.
From: Changbin Du
The level4_kernel_pgt is only defined when X86_5LEVEL is enabled. So
surround level4_kernel_pgt with #ifdef CONFIG_X86_5LEVEL...#endif to
make code correct.
Signed-off-by: Changbin Du
Acked-by: Steven Rostedt (VMware)
---
arch/x86/include/asm/pgtable_64.h | 2 ++
From: Changbin Du
This patch add a new kernel hacking option NO_AUTO_INLINE. Selecting
this option will prevent the compiler from optimizing the kernel by
auto-inlining functions not marked with the inline keyword.
With this option, only functions explicitly marked with "inline" will
be
Hi all,
I have posted this series several months ago but interrupted by personal
affairs. Now I get time to complete this task. Thanks for all of the
reviewers.
I know some kernel developers was searching for a method to dissable GCC
optimizations, probably they want to apply GCC '-O0' option.
We are an image team who can process 400+ images each day.
If you need any image editing service, please let us know.
Image cut out and clipping path, masking.
Such as for ecommerce photos, jewelry photos retouching, beauty and skin
images
and wedding photos.
We give test editing for your
We are an image team who can process 400+ images each day.
If you need any image editing service, please let us know.
Image cut out and clipping path, masking.
Such as for ecommerce photos, jewelry photos retouching, beauty and skin
images
and wedding photos.
We give test editing for your
>On Thu, 18 Oct 2018
>Ingo Molnar wrote:
>* Yangtao Li wrote:
>
>> ---
>> kernel/softirq.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/kernel/softirq.c b/kernel/softirq.c
>> index 6f584861d329..6193e1d1b30d 100644
>> --- a/kernel/softirq.c
>> +++
>On Thu, 18 Oct 2018
>Ingo Molnar wrote:
>* Yangtao Li wrote:
>
>> ---
>> kernel/softirq.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/kernel/softirq.c b/kernel/softirq.c
>> index 6f584861d329..6193e1d1b30d 100644
>> --- a/kernel/softirq.c
>> +++
On 10/18/2018 02:48 AM, Ingo Molnar wrote:
>
> * Thara Gopinath wrote:
>
>> On 10/16/2018 03:33 AM, Ingo Molnar wrote:
>>>
>>> * Thara Gopinath wrote:
>>>
>> Regarding testing, basic build, boot and sanity testing have been
>> performed on hikey960 mainline kernel with debian file
On 10/18/2018 02:48 AM, Ingo Molnar wrote:
>
> * Thara Gopinath wrote:
>
>> On 10/16/2018 03:33 AM, Ingo Molnar wrote:
>>>
>>> * Thara Gopinath wrote:
>>>
>> Regarding testing, basic build, boot and sanity testing have been
>> performed on hikey960 mainline kernel with debian file
The arm64 port now runs on servers which use IPMI. This patch enables
relevant core configs to save manually enabling them when testing
mainline.
Signed-off-by: John Garry
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index db8d364..fe8c097 100644
---
The arm64 port now runs on servers which use IPMI. This patch enables
relevant core configs to save manually enabling them when testing
mainline.
Signed-off-by: John Garry
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index db8d364..fe8c097 100644
---
Commit-ID: e45506ac0af9b56b221863e9649fe122d8bb42ff
Gitweb: https://git.kernel.org/tip/e45506ac0af9b56b221863e9649fe122d8bb42ff
Author: Yangtao Li
AuthorDate: Thu, 18 Oct 2018 10:21:33 -0400
Committer: Ingo Molnar
CommitDate: Thu, 18 Oct 2018 18:10:23 +0200
softirq: Fix typo in
Commit-ID: e45506ac0af9b56b221863e9649fe122d8bb42ff
Gitweb: https://git.kernel.org/tip/e45506ac0af9b56b221863e9649fe122d8bb42ff
Author: Yangtao Li
AuthorDate: Thu, 18 Oct 2018 10:21:33 -0400
Committer: Ingo Molnar
CommitDate: Thu, 18 Oct 2018 18:10:23 +0200
softirq: Fix typo in
Commit-ID: c2712b858187f5bcd7b042fe4daa3ba3a12635c0
Gitweb: https://git.kernel.org/tip/c2712b858187f5bcd7b042fe4daa3ba3a12635c0
Author: Steven Rostedt (VMware)
AuthorDate: Wed, 17 Oct 2018 16:59:51 -0400
Committer: Ingo Molnar
CommitDate: Thu, 18 Oct 2018 08:28:35 +0200
kprobes,
Commit-ID: c2712b858187f5bcd7b042fe4daa3ba3a12635c0
Gitweb: https://git.kernel.org/tip/c2712b858187f5bcd7b042fe4daa3ba3a12635c0
Author: Steven Rostedt (VMware)
AuthorDate: Wed, 17 Oct 2018 16:59:51 -0400
Committer: Ingo Molnar
CommitDate: Thu, 18 Oct 2018 08:28:35 +0200
kprobes,
On 2018-10-12 10:51:34 [-0700], Dave Hansen wrote:
> > diff --git a/arch/x86/include/asm/fpu/internal.h
> > b/arch/x86/include/asm/fpu/internal.h
> > index 16c4077ffc945..956d967ca824a 100644
> > --- a/arch/x86/include/asm/fpu/internal.h
> > +++ b/arch/x86/include/asm/fpu/internal.h
> > @@
On 2018-10-12 10:51:34 [-0700], Dave Hansen wrote:
> > diff --git a/arch/x86/include/asm/fpu/internal.h
> > b/arch/x86/include/asm/fpu/internal.h
> > index 16c4077ffc945..956d967ca824a 100644
> > --- a/arch/x86/include/asm/fpu/internal.h
> > +++ b/arch/x86/include/asm/fpu/internal.h
> > @@
* Amir Goldstein:
> On Thu, Oct 18, 2018 at 4:11 PM Miklos Szeredi wrote:
>>
>> Constants of the *_ALL type can be actively harmful due to the fact that
>> developers will usually fail to consider the possible effects of future
>> changes to the definition.
>>
>> Remove STATX_ALL from the uapi,
* Amir Goldstein:
> On Thu, Oct 18, 2018 at 4:11 PM Miklos Szeredi wrote:
>>
>> Constants of the *_ALL type can be actively harmful due to the fact that
>> developers will usually fail to consider the possible effects of future
>> changes to the definition.
>>
>> Remove STATX_ALL from the uapi,
* Yangtao Li wrote:
> ---
> kernel/softirq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/softirq.c b/kernel/softirq.c
> index 6f584861d329..6193e1d1b30d 100644
> --- a/kernel/softirq.c
> +++ b/kernel/softirq.c
> @@ -257,7 +257,7 @@ asmlinkage __visible
* Yangtao Li wrote:
> ---
> kernel/softirq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/softirq.c b/kernel/softirq.c
> index 6f584861d329..6193e1d1b30d 100644
> --- a/kernel/softirq.c
> +++ b/kernel/softirq.c
> @@ -257,7 +257,7 @@ asmlinkage __visible
Miklos Szeredi wrote:
> I'm trying to implement statx for fuse and ran into the following issues:
>
> - Need a STATX_ATTRIBUTES bit, so that userspace can explicitly ask
> for stx_attribute; otherwise if querying has non-zero cost, then
> filesystem cannot do it without regressing performance.
Miklos Szeredi wrote:
> I'm trying to implement statx for fuse and ran into the following issues:
>
> - Need a STATX_ATTRIBUTES bit, so that userspace can explicitly ask
> for stx_attribute; otherwise if querying has non-zero cost, then
> filesystem cannot do it without regressing performance.
This place looks like a small mistake. :-)
-- Yangtao Li
>On Thu, 18 Oct 2018
>Steven Rostedt (VMware) wrote:
>I don't know if the trivial tree is dead or not, but this would be a
>prime candidate.
>
>Acked-by: Steven Rostedt (VMware)
>
>-- Steve
>
>
>On Thu, 18 Oct 2018 10:21:33 -0400
This place looks like a small mistake. :-)
-- Yangtao Li
>On Thu, 18 Oct 2018
>Steven Rostedt (VMware) wrote:
>I don't know if the trivial tree is dead or not, but this would be a
>prime candidate.
>
>Acked-by: Steven Rostedt (VMware)
>
>-- Steve
>
>
>On Thu, 18 Oct 2018 10:21:33 -0400
We are an image team who can process 400+ images each day.
If you need any image editing service, please let us know.
Image cut out and clipping path, masking.
Such as for ecommerce photos, jewelry photos retouching, beauty and skin
images
and wedding photos.
We give test editing for your
We are an image team who can process 400+ images each day.
If you need any image editing service, please let us know.
Image cut out and clipping path, masking.
Such as for ecommerce photos, jewelry photos retouching, beauty and skin
images
and wedding photos.
We give test editing for your
TISCI abstracts the handling of IRQ routes where interrupt sources
are not directly connected to host interrupt controller. This series
adds support for:
- TISCI commands needed for IRQ configuration
- Interrupt Router(INTR) and Interrupt Aggregator(INTA) drivers
More information on TISCI IRQ
TISCI abstracts the handling of IRQ routes where interrupt sources
are not directly connected to host interrupt controller. This series
adds support for:
- TISCI commands needed for IRQ configuration
- Interrupt Router(INTR) and Interrupt Aggregator(INTA) drivers
More information on TISCI IRQ
From: Grygorii Strashko
TISCI has been updated to have support for Resource management(likes
interrupts etc..). And there can be multiple device instances of a
resource type in a SoC. So every driver corresponding to a resource type
should get a TISCI handle so that it can make TISCI calls. And
From: Grygorii Strashko
TISCI has been updated to have support for Resource management(likes
interrupts etc..). And there can be multiple device instances of a
resource type in a SoC. So every driver corresponding to a resource type
should get a TISCI handle so that it can make TISCI calls. And
Each resource with in the device can be uniquely identified
by a type and subtype as defined by TISCI. Since this is generic
across the devices, resource allocation also can be made generic
instead of each client driver handling the resource. So add helper
apis to manage the resource.
Add the DT binding documentation for Interrupt Aggregator driver.
Signed-off-by: Lokesh Vutla
---
Changes since v1:
- New patch
.../interrupt-controller/ti,sci-inta.txt | 74 +++
MAINTAINERS | 1 +
2 files changed, 75 insertions(+)
Each resource with in the device can be uniquely identified
by a type and subtype as defined by TISCI. Since this is generic
across the devices, resource allocation also can be made generic
instead of each client driver handling the resource. So add helper
apis to manage the resource.
Add the DT binding documentation for Interrupt Aggregator driver.
Signed-off-by: Lokesh Vutla
---
Changes since v1:
- New patch
.../interrupt-controller/ti,sci-inta.txt | 74 +++
MAINTAINERS | 1 +
2 files changed, 75 insertions(+)
Texas Instruments' K3 generation SoCs has an IP Interrupt Router
that does allows for multiplexing of input interrupts to host
interrupt controller. Interrupt Router inputs are either from a
peripheral or from an Interrupt Aggregator which is another
interrupt controller.
Configuration of the
Select all the TISCI dependent interrupt controller drivers
for AM6 SoC.
Suggested-by: Marc Zyngier
Signed-off-by: Lokesh Vutla
---
Changes since v1:
- new patch
drivers/soc/ti/Kconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/soc/ti/Kconfig b/drivers/soc/ti/Kconfig
index
TISCI provides support for getting the resources(IRQ, RING etc..)
assigned to a specific device. These resources can be handled by
the client and in turn sends TISCI cmd to configure the resources.
It is very important that client should keep track on usage of these
resources.
Add support for
Texas Instruments' K3 generation SoCs has an IP Interrupt Router
that does allows for multiplexing of input interrupts to host
interrupt controller. Interrupt Router inputs are either from a
peripheral or from an Interrupt Aggregator which is another
interrupt controller.
Configuration of the
Select all the TISCI dependent interrupt controller drivers
for AM6 SoC.
Suggested-by: Marc Zyngier
Signed-off-by: Lokesh Vutla
---
Changes since v1:
- new patch
drivers/soc/ti/Kconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/soc/ti/Kconfig b/drivers/soc/ti/Kconfig
index
TISCI provides support for getting the resources(IRQ, RING etc..)
assigned to a specific device. These resources can be handled by
the client and in turn sends TISCI cmd to configure the resources.
It is very important that client should keep track on usage of these
resources.
Add support for
Texas Instruments' K3 generation SoCs has an IP Interrupt Aggregator
which is an interrupt controller that does the following:
- Converts events to interrupts that can be understood by
an interrupt router.
- Allows for multiplexing of events to interrupts.
- Allows for grouping of multiple
Texas Instruments' K3 generation SoCs has an IP Interrupt Aggregator
which is an interrupt controller that does the following:
- Converts events to interrupts that can be understood by
an interrupt router.
- Allows for multiplexing of events to interrupts.
- Allows for grouping of multiple
Add the DT binding documentation for Interrupt router driver.
Signed-off-by: Lokesh Vutla
---
Changes since v1:
- Drop dependency on GIC
- Updated supported interrupt types.
.../interrupt-controller/ti,sci-intr.txt | 81 +++
MAINTAINERS |
Add the DT binding documentation for Interrupt router driver.
Signed-off-by: Lokesh Vutla
---
Changes since v1:
- Drop dependency on GIC
- Updated supported interrupt types.
.../interrupt-controller/ti,sci-intr.txt | 81 +++
MAINTAINERS |
TISCI abstracts the handling of IRQ routes where interrupt sources
are not directly connected to interrupt controller. Add support for
the set of TISCI commands for requesting and releasing IRQs.
Signed-off-by: Lokesh Vutla
---
Changes since v1:
- None.
drivers/firmware/ti_sci.c |
TISCI abstracts the handling of IRQ routes where interrupt sources
are not directly connected to interrupt controller. Add support for
the set of TISCI commands for requesting and releasing IRQs.
Signed-off-by: Lokesh Vutla
---
Changes since v1:
- None.
drivers/firmware/ti_sci.c |
From: Peter Ujfalusi
Add the resource mapping table for AM654 SoC as defined
in http://downloads.ti.com/tisci/esd/latest/5_soc_doc/am6x/resasg_types.html
Introduce a new compatible for AM654 "ti,am654-sci" for using
this resource map table.
Signed-off-by: Peter Ujfalusi
Signed-off-by: Lokesh
From: Peter Ujfalusi
Add the resource mapping table for AM654 SoC as defined
in http://downloads.ti.com/tisci/esd/latest/5_soc_doc/am6x/resasg_types.html
Introduce a new compatible for AM654 "ti,am654-sci" for using
this resource map table.
Signed-off-by: Peter Ujfalusi
Signed-off-by: Lokesh
On Thu, 18 Oct 2018 17:02:21 +0200
Oscar Salvador wrote:
> On Thu, Oct 18, 2018 at 03:24:34PM +0100, Jonathan Cameron wrote:
> > Tested-by: Jonathan Cameron
>
> Thanks a lot Jonathan for having tested it!
>
> Did you test the whole serie or only this patch?
> Since you have caught some bugs
On Thu, 18 Oct 2018 17:02:21 +0200
Oscar Salvador wrote:
> On Thu, Oct 18, 2018 at 03:24:34PM +0100, Jonathan Cameron wrote:
> > Tested-by: Jonathan Cameron
>
> Thanks a lot Jonathan for having tested it!
>
> Did you test the whole serie or only this patch?
> Since you have caught some bugs
On Thu, Oct 18, 2018 at 4:33 AM Vivek Gautam
wrote:
>
> Hi Evan,
>
> On Wed, Oct 17, 2018 at 10:55 PM Evan Green wrote:
> >
> > This change adds the UFS controller and PHY to SDM845.
> >
> > Signed-off-by: Evan Green
> > Signed-off-by: Douglas Anderson
> > ---
> >
On Thu, Oct 18, 2018 at 4:33 AM Vivek Gautam
wrote:
>
> Hi Evan,
>
> On Wed, Oct 17, 2018 at 10:55 PM Evan Green wrote:
> >
> > This change adds the UFS controller and PHY to SDM845.
> >
> > Signed-off-by: Evan Green
> > Signed-off-by: Douglas Anderson
> > ---
> >
In coreboot_table_init(), a for loop is used to copy the entries of the
coreboot table. For each entry, the header of the entry, which is a
structure coreboot_table_entry and includes the size of the entry, is
firstly copied from the IO region 'ptr_entry' to 'entry' through the first
In coreboot_table_init(), a for loop is used to copy the entries of the
coreboot table. For each entry, the header of the entry, which is a
structure coreboot_table_entry and includes the size of the entry, is
firstly copied from the IO region 'ptr_entry' to 'entry' through the first
[ add Ross ]
On Thu, Oct 18, 2018 at 12:15 AM Kees Cook wrote:
>
> On Wed, Oct 17, 2018 at 5:49 PM, Dan Williams
> wrote:
> > On Wed, Oct 17, 2018 at 5:29 PM Kees Cook wrote:
> >>
> >> When ramoops reserved a memory region in the kernel, it had an unhelpful
> >> label of "persistent_memory".
[ add Ross ]
On Thu, Oct 18, 2018 at 12:15 AM Kees Cook wrote:
>
> On Wed, Oct 17, 2018 at 5:49 PM, Dan Williams
> wrote:
> > On Wed, Oct 17, 2018 at 5:29 PM Kees Cook wrote:
> >>
> >> When ramoops reserved a memory region in the kernel, it had an unhelpful
> >> label of "persistent_memory".
>From Olaf Hering Sent: Thursday, October 18, 2018 8:20 AM
>
> > This extends existing vmbus related sysfs structure to provide per-channel
> > state information. This is useful when diagnosing issues with multiple
> > queues in networking and storage.
>
> > +++ b/drivers/hv/vmbus_drv.c
> >
>From Olaf Hering Sent: Thursday, October 18, 2018 8:20 AM
>
> > This extends existing vmbus related sysfs structure to provide per-channel
> > state information. This is useful when diagnosing issues with multiple
> > queues in networking and storage.
>
> > +++ b/drivers/hv/vmbus_drv.c
> >
On Wed, 17 Oct 2018, Tim Chen wrote:
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -4196,7 +4196,10 @@
> lite - turn on mitigation for non-dumpable
>processes (i.e.
On Wed, 17 Oct 2018, Tim Chen wrote:
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -4196,7 +4196,10 @@
> lite - turn on mitigation for non-dumpable
>processes (i.e.
On Thu, Oct 18, 2018 at 04:54:56PM +0200, Petr Mladek wrote:
> On Mon 2018-10-15 18:01:43, Miroslav Benes wrote:
> > On Fri, 12 Oct 2018, Petr Mladek wrote:
> >
> > > On Wed 2018-09-05 11:34:06, Miroslav Benes wrote:
> > > > On Tue, 28 Aug 2018, Petr Mladek wrote:
> > > > > Also the API and logic
On Thu, Oct 18, 2018 at 04:54:56PM +0200, Petr Mladek wrote:
> On Mon 2018-10-15 18:01:43, Miroslav Benes wrote:
> > On Fri, 12 Oct 2018, Petr Mladek wrote:
> >
> > > On Wed 2018-09-05 11:34:06, Miroslav Benes wrote:
> > > > On Tue, 28 Aug 2018, Petr Mladek wrote:
> > > > > Also the API and logic
On Thu, Oct 18, 2018 at 06:02:16PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> News: I will not be doing linux-next releases next week. Unfortunately
> this will probably be the first week of the merge window. :-(
>
Note: Every individual on Cc: might want to have a look. Either one of
your
On 10/18/18 12:02 AM, Stephen Rothwell wrote:
> Hi all,
>
> News: I will not be doing linux-next releases next week. Unfortunately
> this will probably be the first week of the merge window. :-(
>
> Changes since 20181017:
>
on x86_64 or i386:
../drivers/cpufreq/intel_pstate.c: In function
On Thu, Oct 18, 2018 at 06:02:16PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> News: I will not be doing linux-next releases next week. Unfortunately
> this will probably be the first week of the merge window. :-(
>
Note: Every individual on Cc: might want to have a look. Either one of
your
On 10/18/18 12:02 AM, Stephen Rothwell wrote:
> Hi all,
>
> News: I will not be doing linux-next releases next week. Unfortunately
> this will probably be the first week of the merge window. :-(
>
> Changes since 20181017:
>
on x86_64 or i386:
../drivers/cpufreq/intel_pstate.c: In function
> -Original Message-
> From: Linuxarm [mailto:linuxarm-boun...@huawei.com] On Behalf Of
> Shameerali Kolothum Thodi
> Sent: 18 October 2018 14:34
> To: Robin Murphy ; lorenzo.pieral...@arm.com;
> jean-philippe.bruc...@arm.com
> Cc: mark.rutl...@arm.com; vkil...@codeaurora.org;
>
> -Original Message-
> From: Linuxarm [mailto:linuxarm-boun...@huawei.com] On Behalf Of
> Shameerali Kolothum Thodi
> Sent: 18 October 2018 14:34
> To: Robin Murphy ; lorenzo.pieral...@arm.com;
> jean-philippe.bruc...@arm.com
> Cc: mark.rutl...@arm.com; vkil...@codeaurora.org;
>
Am Sun, 17 Sep 2017 20:54:18 -0700
schrieb k...@exchange.microsoft.com:
> This extends existing vmbus related sysfs structure to provide per-channel
> state information. This is useful when diagnosing issues with multiple
> queues in networking and storage.
> +++ b/drivers/hv/vmbus_drv.c
>
Am Sun, 17 Sep 2017 20:54:18 -0700
schrieb k...@exchange.microsoft.com:
> This extends existing vmbus related sysfs structure to provide per-channel
> state information. This is useful when diagnosing issues with multiple
> queues in networking and storage.
> +++ b/drivers/hv/vmbus_drv.c
>
Miklos Szeredi wrote:
> + /* Having anything in attributes_mask means attributes are valid. */
> + if (tmp.stx_attributes_mask)
> + tmp.stx_mask |= STATX_ATTRIBUTES;
That would be superfluous, since userspace can make this check too.
Note that fsinfo() might inform you
Miklos Szeredi wrote:
> + /* Having anything in attributes_mask means attributes are valid. */
> + if (tmp.stx_attributes_mask)
> + tmp.stx_mask |= STATX_ATTRIBUTES;
That would be superfluous, since userspace can make this check too.
Note that fsinfo() might inform you
On Thu, Oct 18, 2018 at 04:28:20PM +0200, Krzysztof Kozlowski wrote:
> From: Stephen Warren
>
> commit daa35bd95634a2a2d72d1049c93576a02711cb1a upstream
>
> When the gadget serial device has no associated TTY, do not pass any
> received data into the TTY layer for processing; simply drop it
On Thu, Oct 18, 2018 at 04:28:20PM +0200, Krzysztof Kozlowski wrote:
> From: Stephen Warren
>
> commit daa35bd95634a2a2d72d1049c93576a02711cb1a upstream
>
> When the gadget serial device has no associated TTY, do not pass any
> received data into the TTY layer for processing; simply drop it
On Wed, 17 Oct 2018, Tim Chen wrote:
> +void arch_set_dumpable(struct task_struct *tsk, unsigned int value)
> +{
> + bool update;
> +
> + if (!static_branch_unlikely(_v2_app_lite))
> + return;
> + if (!static_cpu_has(X86_FEATURE_STIBP))
> + return;
> + if
On Wed, 17 Oct 2018, Tim Chen wrote:
> +void arch_set_dumpable(struct task_struct *tsk, unsigned int value)
> +{
> + bool update;
> +
> + if (!static_branch_unlikely(_v2_app_lite))
> + return;
> + if (!static_cpu_has(X86_FEATURE_STIBP))
> + return;
> + if
On Wed, 2018-10-17 at 01:54 -0700, Christoph Hellwig wrote:
> On Mon, Oct 15, 2018 at 05:53:44PM +, Woodruff, Robert J wrote:
> > James Harvey wrote,
> >
> > >Short: Is libibscif dead, and should OS repositories remove it?
> >
> > Libibscif is for an old product, Intel's KNC, that is no
On Wed, 2018-10-17 at 01:54 -0700, Christoph Hellwig wrote:
> On Mon, Oct 15, 2018 at 05:53:44PM +, Woodruff, Robert J wrote:
> > James Harvey wrote,
> >
> > >Short: Is libibscif dead, and should OS repositories remove it?
> >
> > Libibscif is for an old product, Intel's KNC, that is no
Miklos Szeredi wrote:
> Constants of the *_ALL type can be actively harmful due to the fact that
> developers will usually fail to consider the possible effects of future
> changes to the definition.
>
> Remove STATX_ALL from the uapi, while no damage has been done yet.
You don't know that
Miklos Szeredi wrote:
> Constants of the *_ALL type can be actively harmful due to the fact that
> developers will usually fail to consider the possible effects of future
> changes to the definition.
>
> Remove STATX_ALL from the uapi, while no damage has been done yet.
You don't know that
On Wed, 17 Oct 2018, Tim Chen wrote:
> Currently the STIBP is always turned on for CPUs vulnerable to Spectre V2.
> A new lite protection mode option is created. In this new mode, we protect
> security sensitive processes with STIBP and IBPB against application to
> application attack based on
On Wed, 17 Oct 2018, Tim Chen wrote:
> Currently the STIBP is always turned on for CPUs vulnerable to Spectre V2.
> A new lite protection mode option is created. In this new mode, we protect
> security sensitive processes with STIBP and IBPB against application to
> application attack based on
I don't know if the trivial tree is dead or not, but this would be a
prime candidate.
Acked-by: Steven Rostedt (VMware)
-- Steve
On Thu, 18 Oct 2018 10:21:33 -0400
Yangtao Li wrote:
> ---
> kernel/softirq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
I don't know if the trivial tree is dead or not, but this would be a
prime candidate.
Acked-by: Steven Rostedt (VMware)
-- Steve
On Thu, 18 Oct 2018 10:21:33 -0400
Yangtao Li wrote:
> ---
> kernel/softirq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
801 - 900 of 1550 matches
Mail list logo
