On Tue, Nov 20, 2018 at 10:34 PM Eric Anholt wrote:
> >> Eric Anholt hat am 20. November 2018 um 18:19
> >> geschrieben:
> >>
> >>
> >> This series moves the BCM2835 WDT driver that controls a fraction of
> >> the PM block out to soc/ and adds most of the rest of its
> >> functionality. My
On Tue, Nov 20, 2018 at 10:34 PM Eric Anholt wrote:
> >> Eric Anholt hat am 20. November 2018 um 18:19
> >> geschrieben:
> >>
> >>
> >> This series moves the BCM2835 WDT driver that controls a fraction of
> >> the PM block out to soc/ and adds most of the rest of its
> >> functionality. My
This patchset is provided as an RFC and should not be merged as is
(Turkey break in the USA and more validation needed). This is however
a good time to gather comments. This work is the result of multiple
email discussions to finally provide more flexibility for
distributions to chose whether to
From: Takashi Iwai
It's with CNP, supposed to be equivalent with CNL entry.
Signed-off-by: Takashi Iwai
Signed-off-by: Pierre-Louis Bossart
---
sound/soc/intel/skylake/skl-messages.c | 8
sound/soc/intel/skylake/skl.c | 3 +++
2 files changed, 11 insertions(+)
diff --git
This patchset is provided as an RFC and should not be merged as is
(Turkey break in the USA and more validation needed). This is however
a good time to gather comments. This work is the result of multiple
email discussions to finally provide more flexibility for
distributions to chose whether to
From: Takashi Iwai
It's with CNP, supposed to be equivalent with CNL entry.
Signed-off-by: Takashi Iwai
Signed-off-by: Pierre-Louis Bossart
---
sound/soc/intel/skylake/skl-messages.c | 8
sound/soc/intel/skylake/skl.c | 3 +++
2 files changed, 11 insertions(+)
diff --git
From: Takashi Iwai
Previous patches enabled distributions to select for which platform
the Skylake driver will be used. This is not enough however since the
DSP may or may not enabled by the BIOS, and a probe-time dynamic
fallback is highly desired.
This patch introduces a new AZX_DCAPS value,
Guenter Roeck and Stefan Wahren both wanted a MFD-style driver to
cover the PM node that lets WDT and soc/bcm2835-power both attach to
it. I think this is an ugly solution because it bloats this feature
addition by 25% more lines for all the boilerplate, but here it is.
Tested with V3D powering
This binding supersedes the bcm2835-pm-wdt binding which only covered
enough to provide a watchdog, but the HW block is actually mostly
about power domains.
Signed-off-by: Eric Anholt
---
.../bindings/soc/bcm/brcm,bcm2835-pm.txt | 42 +++
1 file changed, 42 insertions(+)
From: Takashi Iwai
Previous patches enabled distributions to select for which platform
the Skylake driver will be used. This is not enough however since the
DSP may or may not enabled by the BIOS, and a probe-time dynamic
fallback is highly desired.
This patch introduces a new AZX_DCAPS value,
Guenter Roeck and Stefan Wahren both wanted a MFD-style driver to
cover the PM node that lets WDT and soc/bcm2835-power both attach to
it. I think this is an ugly solution because it bloats this feature
addition by 25% more lines for all the boilerplate, but here it is.
Tested with V3D powering
This binding supersedes the bcm2835-pm-wdt binding which only covered
enough to provide a watchdog, but the HW block is actually mostly
about power domains.
Signed-off-by: Eric Anholt
---
.../bindings/soc/bcm/brcm,bcm2835-pm.txt | 42 +++
1 file changed, 42 insertions(+)
This provides a free software alternative to raspberrypi-power.c's
firmware calls to manage power domains. It also exposes a reset line,
where previously the vc4 driver had to try to force power off the
domain in order to trigger a reset.
Signed-off-by: Eric Anholt
---
drivers/mfd/bcm2835-pm.c
The PM block that the wdt driver was binding to actually has multiple
features we want to expose (power domains, reset, watchdog). Move the
DT attachment to a MFD driver and make WDT probe against MFD.
Signed-off-by: Eric Anholt
---
arch/arm/mach-bcm/Kconfig | 1 +
drivers/mfd/Makefile
bus->ppcap is now tested upfront, there is no need to re-check if the
DSP is present. Remove tests and remove indentation.
Signed-off-by: Pierre-Louis Bossart
---
sound/soc/intel/skylake/skl.c | 40 ---
1 file changed, 18 insertions(+), 22 deletions(-)
diff
Enable fallback for select PCI IDs
Signed-off-by: Pierre-Louis Bossart
---
sound/pci/hda/Kconfig | 40 +++
sound/pci/hda/hda_intel.c | 19 +--
sound/soc/intel/Kconfig | 6 ++
3 files changed, 59 insertions(+), 6 deletions(-)
diff
It was covering part of the PM block's range, up to the WDT regs. To
support the rest of the PM block's functionality, we need the full
register range plus the AXI Async Bridge regs for PM sequencing.
This doesn't convert any of the consumers over to the new binding yet,
since we will need to be
The GRAFX domain only contains V3D, and this driver should be the only
accessor of V3D (firmware usage gets disabled when V3D is in the DT),
so we can safely make Linux control the GRAFX and GRAFX_V3D power
domains.
Signed-off-by: Eric Anholt
---
arch/arm/boot/dts/bcm2835-rpi.dtsi | 4
Check immediately if the DSP can be found, bail and avoid doing inits
to enable legacy fallback without delay.
Signed-off-by: Pierre-Louis Bossart
---
sound/soc/intel/skylake/skl.c | 26 +-
1 file changed, 17 insertions(+), 9 deletions(-)
diff --git
This provides a free software alternative to raspberrypi-power.c's
firmware calls to manage power domains. It also exposes a reset line,
where previously the vc4 driver had to try to force power off the
domain in order to trigger a reset.
Signed-off-by: Eric Anholt
---
drivers/mfd/bcm2835-pm.c
The PM block that the wdt driver was binding to actually has multiple
features we want to expose (power domains, reset, watchdog). Move the
DT attachment to a MFD driver and make WDT probe against MFD.
Signed-off-by: Eric Anholt
---
arch/arm/mach-bcm/Kconfig | 1 +
drivers/mfd/Makefile
bus->ppcap is now tested upfront, there is no need to re-check if the
DSP is present. Remove tests and remove indentation.
Signed-off-by: Pierre-Louis Bossart
---
sound/soc/intel/skylake/skl.c | 40 ---
1 file changed, 18 insertions(+), 22 deletions(-)
diff
Enable fallback for select PCI IDs
Signed-off-by: Pierre-Louis Bossart
---
sound/pci/hda/Kconfig | 40 +++
sound/pci/hda/hda_intel.c | 19 +--
sound/soc/intel/Kconfig | 6 ++
3 files changed, 59 insertions(+), 6 deletions(-)
diff
It was covering part of the PM block's range, up to the WDT regs. To
support the rest of the PM block's functionality, we need the full
register range plus the AXI Async Bridge regs for PM sequencing.
This doesn't convert any of the consumers over to the new binding yet,
since we will need to be
The GRAFX domain only contains V3D, and this driver should be the only
accessor of V3D (firmware usage gets disabled when V3D is in the DT),
so we can safely make Linux control the GRAFX and GRAFX_V3D power
domains.
Signed-off-by: Eric Anholt
---
arch/arm/boot/dts/bcm2835-rpi.dtsi | 4
Check immediately if the DSP can be found, bail and avoid doing inits
to enable legacy fallback without delay.
Signed-off-by: Pierre-Louis Bossart
---
sound/soc/intel/skylake/skl.c | 26 +-
1 file changed, 17 insertions(+), 9 deletions(-)
diff --git
The current SKYLAKE kconfig is a all-you-can-eat selection that will
support all known plaforms. This is however not necessarily a good
thing: most platforms for SKL and KBL don't support the DSP, but a
number of CNL/WHL ones do. Selecting this driver in all cases isn't
really smart and will
The current SKYLAKE kconfig is a all-you-can-eat selection that will
support all known plaforms. This is however not necessarily a good
thing: most platforms for SKL and KBL don't support the DSP, but a
number of CNL/WHL ones do. Selecting this driver in all cases isn't
really smart and will
On Tue, Nov 20, 2018 at 1:19 PM Stephane Eranian wrote:
>
> On Tue, Nov 20, 2018 at 12:53 PM Kyle Huey wrote:
> >
> > On Tue, Nov 20, 2018 at 12:11 PM Andi Kleen wrote:
> > >
> > > > > > Given that we're already at rc3, and that this renders rr unusable,
> > > > > > we'd ask that counter
On Tue, Nov 20, 2018 at 1:19 PM Stephane Eranian wrote:
>
> On Tue, Nov 20, 2018 at 12:53 PM Kyle Huey wrote:
> >
> > On Tue, Nov 20, 2018 at 12:11 PM Andi Kleen wrote:
> > >
> > > > > > Given that we're already at rc3, and that this renders rr unusable,
> > > > > > we'd ask that counter
Stefan Wahren writes:
> Hi Eric,
>
>> Eric Anholt hat am 20. November 2018 um 18:19 geschrieben:
>>
>>
>> This series moves the BCM2835 WDT driver that controls a fraction of
>> the PM block out to soc/ and adds most of the rest of its
>> functionality. My motivation has been to have V3D be
Stefan Wahren writes:
> Hi Eric,
>
>> Eric Anholt hat am 20. November 2018 um 18:19 geschrieben:
>>
>>
>> This series moves the BCM2835 WDT driver that controls a fraction of
>> the PM block out to soc/ and adds most of the rest of its
>> functionality. My motivation has been to have V3D be
On Tue, 2018-11-20 at 21:42 +0100, Stefan Agner wrote:
> On 20.11.2018 20:13, Trent Piepho wrote:
> >
> > On IMX7d, there are significant blocks of 00s in the config space, and
> > all 0xff at 0xb50 on up.
> >
> > I.e., significant portions are empty, in the middle of the config
> > space, not
On Tue, 2018-11-20 at 21:42 +0100, Stefan Agner wrote:
> On 20.11.2018 20:13, Trent Piepho wrote:
> >
> > On IMX7d, there are significant blocks of 00s in the config space, and
> > all 0xff at 0xb50 on up.
> >
> > I.e., significant portions are empty, in the middle of the config
> > space, not
The pwm-backlight driver initializes BLON (the enable gpio) to
output-high if the gpio is input on probe. Initializing the gpio
to output-low before the driver probes prevents this action by
the pwm-backlight driver and gets rid of a nasty blink of full
backlight with an uninitialized panel.
The pwm-backlight driver initializes BLON (the enable gpio) to
output-high if the gpio is input on probe. Initializing the gpio
to output-low before the driver probes prevents this action by
the pwm-backlight driver and gets rid of a nasty blink of full
backlight with an uninitialized panel.
On Tue, Nov 20, 2018 at 12:53 PM Kyle Huey wrote:
>
> On Tue, Nov 20, 2018 at 12:11 PM Andi Kleen wrote:
> >
> > > > > Given that we're already at rc3, and that this renders rr unusable,
> > > > > we'd ask that counter freezing be disabled for the 4.20 release.
> > > >
> > > > The boot option
On Tue, Nov 20, 2018 at 12:53 PM Kyle Huey wrote:
>
> On Tue, Nov 20, 2018 at 12:11 PM Andi Kleen wrote:
> >
> > > > > Given that we're already at rc3, and that this renders rr unusable,
> > > > > we'd ask that counter freezing be disabled for the 4.20 release.
> > > >
> > > > The boot option
> I suppose that's fair that it's better for some use cases. The flip
> side is that it's no longer possible to get exactly accurate counts
> from user space if you're using the PMI (because any events between
> the overflow itself and the transition to the PMI handler are
> permanently lost)
> I suppose that's fair that it's better for some use cases. The flip
> side is that it's no longer possible to get exactly accurate counts
> from user space if you're using the PMI (because any events between
> the overflow itself and the transition to the PMI handler are
> permanently lost)
Hi Rafael,
Please pull the following update for Linux 4.20-rc4 or rc5 depending on
your pm pull schedule to Linus.
This cpupower update for Linux 4.20-rc4 consists of compile fixes to
allow use of outside build flags and override of CFLAGS from Jiri Olsa,
and fix to compilation with
Hi Rafael,
Please pull the following update for Linux 4.20-rc4 or rc5 depending on
your pm pull schedule to Linus.
This cpupower update for Linux 4.20-rc4 consists of compile fixes to
allow use of outside build flags and override of CFLAGS from Jiri Olsa,
and fix to compilation with
On Tue, Nov 20, 2018 at 02:02:49PM -0700, Andy Lutomirski wrote:
>
> > On Nov 20, 2018, at 1:47 PM, Joel Fernandes wrote:
> >
> >> On Tue, Nov 20, 2018 at 01:33:18PM -0700, Andy Lutomirski wrote:
> >>
> >>> On Nov 20, 2018, at 1:07 PM, Stephen Rothwell
> >>> wrote:
> >>>
> >>> Hi Joel,
>
On Tue, Nov 20, 2018 at 02:02:49PM -0700, Andy Lutomirski wrote:
>
> > On Nov 20, 2018, at 1:47 PM, Joel Fernandes wrote:
> >
> >> On Tue, Nov 20, 2018 at 01:33:18PM -0700, Andy Lutomirski wrote:
> >>
> >>> On Nov 20, 2018, at 1:07 PM, Stephen Rothwell
> >>> wrote:
> >>>
> >>> Hi Joel,
>
On Fri, Oct 26, 2018 at 12:59 PM, Dave Hansen wrote:
> On 10/26/18 12:51 PM, Dave Hansen wrote:
> ...
>> The result is that, after a fork(), the child's pkey state ends up
>> looking like it does after an execve(), which is totally wrong. pkeys
>> that are already allocated can be allocated
On Fri, Oct 26, 2018 at 12:59 PM, Dave Hansen wrote:
> On 10/26/18 12:51 PM, Dave Hansen wrote:
> ...
>> The result is that, after a fork(), the child's pkey state ends up
>> looking like it does after an execve(), which is totally wrong. pkeys
>> that are already allocated can be allocated
Add power-domain bindings for Q6V5 MSS on SDM845 SoCs.
Signed-off-by: Sibi Sankar
---
Add dt-binding corresponding to https://patchwork.kernel.org/patch/10586893/
(remoteproc: q6v5: Add support to vote for rpmh power domains)
.../devicetree/bindings/remoteproc/qcom,q6v5.txt | 11
Add power-domain bindings for Q6V5 MSS on SDM845 SoCs.
Signed-off-by: Sibi Sankar
---
Add dt-binding corresponding to https://patchwork.kernel.org/patch/10586893/
(remoteproc: q6v5: Add support to vote for rpmh power domains)
.../devicetree/bindings/remoteproc/qcom,q6v5.txt | 11
Hi,
On Tue, Nov 20, 2018 at 09:28:37AM +0200, Peter Ujfalusi wrote:
> On 19/11/2018 20.46, Aaro Koskinen wrote:
> > On Mon, Nov 19, 2018 at 12:40:40PM +0200, Peter Ujfalusi wrote:
> >> When the channel is configured for slave operation the LCH_TYPE needs to be
> >> set to LCh-P. For memcpy
Hi,
On Tue, Nov 20, 2018 at 09:28:37AM +0200, Peter Ujfalusi wrote:
> On 19/11/2018 20.46, Aaro Koskinen wrote:
> > On Mon, Nov 19, 2018 at 12:40:40PM +0200, Peter Ujfalusi wrote:
> >> When the channel is configured for slave operation the LCH_TYPE needs to be
> >> set to LCh-P. For memcpy
> On Nov 20, 2018, at 1:47 PM, Joel Fernandes wrote:
>
>> On Tue, Nov 20, 2018 at 01:33:18PM -0700, Andy Lutomirski wrote:
>>
>>> On Nov 20, 2018, at 1:07 PM, Stephen Rothwell wrote:
>>>
>>> Hi Joel,
>>>
> On Tue, 20 Nov 2018 10:39:26 -0800 Joel Fernandes
> wrote:
>
> On
> On Nov 20, 2018, at 1:47 PM, Joel Fernandes wrote:
>
>> On Tue, Nov 20, 2018 at 01:33:18PM -0700, Andy Lutomirski wrote:
>>
>>> On Nov 20, 2018, at 1:07 PM, Stephen Rothwell wrote:
>>>
>>> Hi Joel,
>>>
> On Tue, 20 Nov 2018 10:39:26 -0800 Joel Fernandes
> wrote:
>
> On
Add optional shutdown-irq binding required for sysmon shutdown on
SDM845/MSM8996/QCS404 SoCs.
Signed-off-by: Sibi Sankar
---
Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
After sending a sysmon shutdown request to the SSCTL service on the
subsystem, wait for the service to send shutdown-ack interrupt or
an indication message back.
Signed-off-by: Sibi Sankar
---
drivers/remoteproc/qcom_sysmon.c | 59 +++-
1 file changed, 58
Add optional shutdown-irq binding required for sysmon shutdown on
SDM845/MSM8996/QCS404 SoCs.
Signed-off-by: Sibi Sankar
---
Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
After sending a sysmon shutdown request to the SSCTL service on the
subsystem, wait for the service to send shutdown-ack interrupt or
an indication message back.
Signed-off-by: Sibi Sankar
---
drivers/remoteproc/qcom_sysmon.c | 59 +++-
1 file changed, 58
On Tue, 20 Nov 2018, Waiman Long wrote:
> On 11/20/2018 03:14 PM, Qian Cai wrote:
> > static struct debug_obj_descr *descr_test __read_mostly;
>
> The calculation for ODEBUG_POOL_SIZE is somewhat hard to read. Maybe you
> can do something like
>
> #ifdef CONFIG_DEBUG_OBJECTS_WORK
>
On Tue, 20 Nov 2018, Waiman Long wrote:
> On 11/20/2018 03:14 PM, Qian Cai wrote:
> > static struct debug_obj_descr *descr_test __read_mostly;
>
> The calculation for ODEBUG_POOL_SIZE is somewhat hard to read. Maybe you
> can do something like
>
> #ifdef CONFIG_DEBUG_OBJECTS_WORK
>
On 11/20/2018 03:14 PM, Qian Cai wrote:
> The current value of the early boot static pool size is not big enough
> for systems with large number of CPUs with timer or/and workqueue
> objects selected. As the results, systems have 60+ CPUs with both timer
> and workqueue objects enabled could
On 11/20/2018 03:14 PM, Qian Cai wrote:
> The current value of the early boot static pool size is not big enough
> for systems with large number of CPUs with timer or/and workqueue
> objects selected. As the results, systems have 60+ CPUs with both timer
> and workqueue objects enabled could
On Tue, Nov 20, 2018 at 12:11 PM Andi Kleen wrote:
>
> > > > Given that we're already at rc3, and that this renders rr unusable,
> > > > we'd ask that counter freezing be disabled for the 4.20 release.
> > >
> > > The boot option should be good enough for the release?
> >
> > I'm not entirely
On Tue, Nov 20, 2018 at 12:11 PM Andi Kleen wrote:
>
> > > > Given that we're already at rc3, and that this renders rr unusable,
> > > > we'd ask that counter freezing be disabled for the 4.20 release.
> > >
> > > The boot option should be good enough for the release?
> >
> > I'm not entirely
On Tue, Nov 20, 2018 at 01:33:18PM -0700, Andy Lutomirski wrote:
>
> > On Nov 20, 2018, at 1:07 PM, Stephen Rothwell wrote:
> >
> > Hi Joel,
> >
> >> On Tue, 20 Nov 2018 10:39:26 -0800 Joel Fernandes
> >> wrote:
> >>
> >>> On Tue, Nov 20, 2018 at 07:13:17AM -0800, Andy Lutomirski wrote:
>
On Tue, Nov 20, 2018 at 01:33:18PM -0700, Andy Lutomirski wrote:
>
> > On Nov 20, 2018, at 1:07 PM, Stephen Rothwell wrote:
> >
> > Hi Joel,
> >
> >> On Tue, 20 Nov 2018 10:39:26 -0800 Joel Fernandes
> >> wrote:
> >>
> >>> On Tue, Nov 20, 2018 at 07:13:17AM -0800, Andy Lutomirski wrote:
>
On Sun, Nov 11, 2018 at 10:36:18AM -0800, Paul E. McKenney wrote:
> On Sun, Nov 11, 2018 at 10:09:16AM -0800, Joel Fernandes wrote:
> > On Sat, Nov 10, 2018 at 08:22:10PM -0800, Paul E. McKenney wrote:
> > > On Sat, Nov 10, 2018 at 07:09:25PM -0800, Joel Fernandes wrote:
> > > > On Sat, Nov 10,
On Sun, Nov 11, 2018 at 10:36:18AM -0800, Paul E. McKenney wrote:
> On Sun, Nov 11, 2018 at 10:09:16AM -0800, Joel Fernandes wrote:
> > On Sat, Nov 10, 2018 at 08:22:10PM -0800, Paul E. McKenney wrote:
> > > On Sat, Nov 10, 2018 at 07:09:25PM -0800, Joel Fernandes wrote:
> > > > On Sat, Nov 10,
On 20.11.2018 20:13, Trent Piepho wrote:
> On Tue, 2018-11-20 at 18:19 +, Leonard Crestez wrote:
>> On Tue, 2018-11-20 at 17:56 +0100, Stefan Agner wrote:
>> > Define the length of the DBI registers. This makes sure that
>> > the kernel does not access registers beyond that point, avoiding
>>
On 20.11.2018 20:13, Trent Piepho wrote:
> On Tue, 2018-11-20 at 18:19 +, Leonard Crestez wrote:
>> On Tue, 2018-11-20 at 17:56 +0100, Stefan Agner wrote:
>> > Define the length of the DBI registers. This makes sure that
>> > the kernel does not access registers beyond that point, avoiding
>>
On Mon, Nov 19, 2018 at 05:25:07PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.3 release.
> There are 205 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Mon, Nov 19, 2018 at 05:25:07PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.3 release.
> There are 205 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On 20/11/2018 19:01:32+0100, Romain Izard wrote:
> Le mar. 20 nov. 2018 à 18:16, Alexandre Belloni
> a écrit :
> >
> > Hello Romain,
> >
> > On 20/11/2018 17:57:37+0100, Romain Izard wrote:
> > > The SAMA5D2 is different from SAMA5D3 and SAMA5D4, as there are two
> > > different clocks for the
On 20/11/2018 19:01:32+0100, Romain Izard wrote:
> Le mar. 20 nov. 2018 à 18:16, Alexandre Belloni
> a écrit :
> >
> > Hello Romain,
> >
> > On 20/11/2018 17:57:37+0100, Romain Izard wrote:
> > > The SAMA5D2 is different from SAMA5D3 and SAMA5D4, as there are two
> > > different clocks for the
On Mon, Nov 19, 2018 at 05:26:36PM +0100, Greg Kroah-Hartman wrote:
> --
> NOTE, this is going to be the last 4.18.y release. After this one it is
> end-of-life, please move to 4.19.y at this point in time.
> --
>
> This is the start of the stable review cycle for
On Mon, Nov 19, 2018 at 05:26:36PM +0100, Greg Kroah-Hartman wrote:
> --
> NOTE, this is going to be the last 4.18.y release. After this one it is
> end-of-life, please move to 4.19.y at this point in time.
> --
>
> This is the start of the stable review cycle for
On Mon, Nov 19, 2018 at 05:28:26PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.138 release.
> There are 83 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Mon, Nov 19, 2018 at 05:28:26PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.138 release.
> There are 83 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Mon, Nov 19, 2018 at 05:27:34PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.82 release.
> There are 124 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Mon, Nov 19, 2018 at 05:27:34PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.82 release.
> There are 124 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Mon, Nov 19, 2018 at 05:27:19PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.164 release.
> There are 160 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Mon, Nov 19, 2018 at 05:27:19PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.164 release.
> There are 160 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Mon, Nov 19, 2018 at 05:28:42PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.126 release.
> There are 90 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Mon, Nov 19, 2018 at 05:28:42PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.126 release.
> There are 90 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
> On Nov 20, 2018, at 1:07 PM, Stephen Rothwell wrote:
>
> Hi Joel,
>
>> On Tue, 20 Nov 2018 10:39:26 -0800 Joel Fernandes
>> wrote:
>>
>>> On Tue, Nov 20, 2018 at 07:13:17AM -0800, Andy Lutomirski wrote:
>>> On Mon, Nov 19, 2018 at 9:21 PM Joel Fernandes (Google)
>>> wrote:
> On Nov 20, 2018, at 1:07 PM, Stephen Rothwell wrote:
>
> Hi Joel,
>
>> On Tue, 20 Nov 2018 10:39:26 -0800 Joel Fernandes
>> wrote:
>>
>>> On Tue, Nov 20, 2018 at 07:13:17AM -0800, Andy Lutomirski wrote:
>>> On Mon, Nov 19, 2018 at 9:21 PM Joel Fernandes (Google)
>>> wrote:
Forgot to CC the mailing list...
On 11/20/18 1:18 PM, Jens Axboe wrote:
> Hi,
>
> So this is a fun one... While I was doing the aio polled work, I noticed
> that the submitting process spent a substantial amount of time copying
> data to/from userspace. For aio, that's iocb and io_event, which
Forgot to CC the mailing list...
On 11/20/18 1:18 PM, Jens Axboe wrote:
> Hi,
>
> So this is a fun one... While I was doing the aio polled work, I noticed
> that the submitting process spent a substantial amount of time copying
> data to/from userspace. For aio, that's iocb and io_event, which
When building with -ffunction-sections, the compiler will place each
function into its own ELF section, prefixed with ".text". For example,
a simple test module with functions test_module_do_work() and
test_module_wq_func():
% objdump --section-headers test_module.o | awk '/\.text/{print $2}'
When building with -ffunction-sections, the compiler will place each
function into its own ELF section, prefixed with ".text". For example,
a simple test module with functions test_module_do_work() and
test_module_wq_func():
% objdump --section-headers test_module.o | awk '/\.text/{print $2}'
Hi Steve,
I noticed that ftrace does not currently support functions built with
the -ffunction-sections option as they end up in .text.
ELF sections, never making into the __mcount_loc section.
I modified the recordmcount scripts to handle such .text. section
prefixes and this appears to work on
Hi Steve,
I noticed that ftrace does not currently support functions built with
the -ffunction-sections option as they end up in .text.
ELF sections, never making into the __mcount_loc section.
I modified the recordmcount scripts to handle such .text. section
prefixes and this appears to work on
The current value of the early boot static pool size is not big enough
for systems with large number of CPUs with timer or/and workqueue
objects selected. As the results, systems have 60+ CPUs with both timer
and workqueue objects enabled could trigger "ODEBUG: Out of memory.
ODEBUG disabled".
The current value of the early boot static pool size is not big enough
for systems with large number of CPUs with timer or/and workqueue
objects selected. As the results, systems have 60+ CPUs with both timer
and workqueue objects enabled could trigger "ODEBUG: Out of memory.
ODEBUG disabled".
Do you know if you are running with this patch (which was marked for stable)
commit 32a1fb36f6e50183871c2c1fcf5493c633e84732
Author: Ronnie Sahlberg
Date: Wed Oct 24 11:50:33 2018 +1000
cifs: allow calling SMB2_xxx_free(NULL)
Change these free functions to allow passing NULL as the
Do you know if you are running with this patch (which was marked for stable)
commit 32a1fb36f6e50183871c2c1fcf5493c633e84732
Author: Ronnie Sahlberg
Date: Wed Oct 24 11:50:33 2018 +1000
cifs: allow calling SMB2_xxx_free(NULL)
Change these free functions to allow passing NULL as the
> > > Given that we're already at rc3, and that this renders rr unusable,
> > > we'd ask that counter freezing be disabled for the 4.20 release.
> >
> > The boot option should be good enough for the release?
>
> I'm not entirely sure what you mean here. We want you to flip the
> default boot
> > > Given that we're already at rc3, and that this renders rr unusable,
> > > we'd ask that counter freezing be disabled for the 4.20 release.
> >
> > The boot option should be good enough for the release?
>
> I'm not entirely sure what you mean here. We want you to flip the
> default boot
Hi Joel,
On Tue, 20 Nov 2018 10:39:26 -0800 Joel Fernandes
wrote:
>
> On Tue, Nov 20, 2018 at 07:13:17AM -0800, Andy Lutomirski wrote:
> > On Mon, Nov 19, 2018 at 9:21 PM Joel Fernandes (Google)
> > wrote:
> > >
> > > A better way to do F_SEAL_FUTURE_WRITE seal was discussed [1] last week
>
Hi Joel,
On Tue, 20 Nov 2018 10:39:26 -0800 Joel Fernandes
wrote:
>
> On Tue, Nov 20, 2018 at 07:13:17AM -0800, Andy Lutomirski wrote:
> > On Mon, Nov 19, 2018 at 9:21 PM Joel Fernandes (Google)
> > wrote:
> > >
> > > A better way to do F_SEAL_FUTURE_WRITE seal was discussed [1] last week
>
Currently the EXT_CSD_CACHE_CTRL register is controlled by API
mmc_card_broken_hpi(), which only works for the quirks settings.
This commit enhances it to use card->ext_csd.hpi instead. This
flag works for both the quirks and the broken-hpi configuration
in the device tree.
Signed-off-by: Liming
Currently the EXT_CSD_CACHE_CTRL register is controlled by API
mmc_card_broken_hpi(), which only works for the quirks settings.
This commit enhances it to use card->ext_csd.hpi instead. This
flag works for both the quirks and the broken-hpi configuration
in the device tree.
Signed-off-by: Liming
401 - 500 of 1736 matches
Mail list logo
