On Sun, Dec 16, 2018 at 09:16:16PM +0800, Lianbo Jiang wrote:
> +
> +Common variables
> +
> +
> +init_uts_ns.name.release
> +
> +The number of OS release. Based on this version number, people can find
> +the source code for the corresponding v
On Sun, Dec 16, 2018 at 09:16:15PM +0800, Lianbo Jiang wrote:
> This patchset did two things:
> a. add a new document for vmcoreinfo
>
> This document lists some variables that export to vmcoreinfo, and briefly
> describles what these variables indicate. It should be instructive for
> many people
On Sun, Dec 16, 2018 at 09:16:16PM +0800, Lianbo Jiang wrote:
This...
> +node_online_map
> +===
> +It is a macro definition, actually it is an array node_states[N_ONLINE],
> +and it represents the set of online node in a system, one bit position
> +per node number.
> +
> +This is used
On Sun, Dec 16, 2018 at 09:16:16PM +0800, Lianbo Jiang wrote:
> +clear_idx
> +=
> +The index that the next printk record to read after the last 'clear'
> +command. It indicates the first record after the last SYSLOG_ACTION
> +_CLEAR, like issued by 'dmesg -c'.
What is that used for by the
On Sun, Dec 16, 2018 at 09:16:17PM +0800, Lianbo Jiang wrote:
> For AMD machine with SME feature, makedumpfile tools need to know
> whether the crash kernel was encrypted or not. If SME is enabled
> in the first kernel, the crash kernel's page table(pgd/pud/pmd/pte)
> contains the memory encryption
On Fri, Dec 14, 2018 at 01:45:13PM +, Ayan Halder wrote:
> On Tue, Dec 04, 2018 at 04:50:51PM +, Liviu Dudau wrote:
>
> Hi Liviu,
>
> Please let me know if you agree with my comments. Then I will send a
> v4 patch for this.
> > On Mon, Dec 03, 2018 at 11:31:58AM +, Ayan Halder wrote:
From: Claudiu Beznea
Add basic PWM modes: normal and complementary. These modes should
differentiate the single output PWM channels from two outputs PWM
channels. These modes could be set as follow:
1. PWM channels with one output per channel:
- normal mode
2. PWM channels with two outputs per ch
From: Claudiu Beznea
Add PWM normal and complementary modes.
Signed-off-by: Claudiu Beznea
---
Hi Rob,
In prevous version I had your Acked-by tag on this patch but I removed it
in this version since there are some changes b/w the previous one and this
one. Please see bellow and let me know if
From: Claudiu Beznea
Add support for PWM push-pull mode. This is only supported by SAMA5D2 SoCs.
Signed-off-by: Claudiu Beznea
---
drivers/pwm/pwm-atmel.c | 40
1 file changed, 36 insertions(+), 4 deletions(-)
diff --git a/drivers/pwm/pwm-atmel.c b/dri
From: Claudiu Beznea
Hi,
This series extends PWM framework with PWM modes.
The current patch series add the following PWM modes:
- PWM mode normal
- PWM mode complementary
- PWM mode push-pull
In the following description PWMx_y refers to output y of PWM with ID x.
Normal mode - for PWM chann
From: Claudiu Beznea
Add push-pull mode support. In push-pull mode the channels' outputs have
same polarities and the edges are complementary delayed for one period.
Signed-off-by: Claudiu Beznea
---
drivers/pwm/core.c | 3 +++
include/linux/pwm.h | 3 +++
2 files changed, 6 insertions(+)
di
From: Claudiu Beznea
Add pwm capabilities for Atmel/Microchip PWM controllers.
Signed-off-by: Claudiu Beznea
---
drivers/pwm/pwm-atmel.c | 86 -
1 file changed, 57 insertions(+), 29 deletions(-)
diff --git a/drivers/pwm/pwm-atmel.c b/drivers/pwm
From: Claudiu Beznea
Add documentation for PWM push-pull mode.
Signed-off-by: Claudiu Beznea
---
Hi Rob,
In prevous version I had your Revie
On Fri, Dec 14, 2018 at 02:12:23PM +, Ayan Halder wrote:
> On Tue, Dec 04, 2018 at 04:57:46PM +, Liviu Dudau wrote:
>
> Hi Liviu,
> > On Mon, Dec 03, 2018 at 11:32:00AM +, Ayan Halder wrote:
> > > We have added some new formats to be supported on DP500/DP550/DP650.
> >
> > Make a bit
Please ignore this one, the number of patches in cover letter is wrong: 0/9
should be 0/6.
Thank you,
Claudiu Beznea
On 17.12.2018 16:03, Claudiu Beznea - M18063 wrote:
> From: Claudiu Beznea
>
> Hi,
>
> This series extends PWM framework with PWM modes.
>
> The current patch series add the fo
From: Claudiu Beznea
Hi,
This series extends PWM framework with PWM modes.
The current patch series add the following PWM modes:
- PWM mode normal
- PWM mode complementary
- PWM mode push-pull
In the following description PWMx_y refers to output y of PWM with ID x.
Normal mode - for PWM chann
From: Claudiu Beznea
Add documentation for PWM push-pull mode.
Signed-off-by: Claudiu Beznea
---
Hi Rob,
In prevous version I had your Revie
From: Claudiu Beznea
Add pwm capabilities for Atmel/Microchip PWM controllers.
Signed-off-by: Claudiu Beznea
---
drivers/pwm/pwm-atmel.c | 86 -
1 file changed, 57 insertions(+), 29 deletions(-)
diff --git a/drivers/pwm/pwm-atmel.c b/drivers/pwm
From: Claudiu Beznea
Add PWM normal and complementary modes.
Signed-off-by: Claudiu Beznea
---
Hi Rob,
In prevous version I had your Acked-by tag on this patch but I removed it
in this version since there are some changes b/w the previous one and this
one. Please see bellow and let me know if
From: Claudiu Beznea
Add push-pull mode support. In push-pull mode the channels' outputs have
same polarities and the edges are complementary delayed for one period.
Signed-off-by: Claudiu Beznea
---
drivers/pwm/core.c | 3 +++
include/linux/pwm.h | 3 +++
2 files changed, 6 insertions(+)
di
From: Claudiu Beznea
Add support for PWM push-pull mode. This is only supported by SAMA5D2 SoCs.
Signed-off-by: Claudiu Beznea
---
drivers/pwm/pwm-atmel.c | 40
1 file changed, 36 insertions(+), 4 deletions(-)
diff --git a/drivers/pwm/pwm-atmel.c b/dri
From: Claudiu Beznea
Add basic PWM modes: normal and complementary. These modes should
differentiate the single output PWM channels from two outputs PWM
channels. These modes could be set as follow:
1. PWM channels with one output per channel:
- normal mode
2. PWM channels with two outputs per ch
On Fri, Dec 14, 2018 at 09:15:05AM -0800, Suren Baghdasaryan wrote:
> Eliminate the idle mode and keep the worker doing 2s update intervals
> at all times.
That sounds like a bad deal.. esp. so for battery powered devices like
say Andoird.
In general the push has been to always idle everything, s
On Fri, Dec 14, 2018 at 09:15:06AM -0800, Suren Baghdasaryan wrote:
> The psi monitoring patches will need to determine the same states as
> record_times(). To avoid calculating them twice, maintain a state mask
> that can be consulted cheaply. Do this in a separate patch to keep the
> churn in the
Hi Peter,
On 14/12/2018 14:33, Peter Maydell wrote:
> On Fri, 14 Dec 2018 at 13:56, James Morse wrote:
>> On 14/12/2018 10:15, Dongjiu Geng wrote:
>>> When user space do memory recovery, it will check whether KVM and
>>> guest support the error recovery, only when both of them support,
>>> user s
Hi gengdongjiu, Peter,
I think the root issue here is the name of the cpufeature 'RAS Extensions', this
doesn't mean RAS is new, or even requires these features. It's just standardised
records, classification and a barrier.
Not only is it possible to build a platform that supports RAS without this
Hi! Find my first contribution to the kernel documentation in the reply to this
mail. Hopefully a lot more will follow. This patch got triggered while working
on an update for reporting-bugs.rst, as improving the documentation around
reporting bugs and regressions was one of the main things that a
Add a section about /proc/sys/kernel/tainted and a command that decodes it to
Documentation/admin-guide/tainted-kernels.rst. While at it introduce a table
that shows the various bits as well as the letters used in oops and panic
messages. Make the document more user focused and easier to understand
On Fri, Dec 14, 2018 at 09:15:08AM -0800, Suren Baghdasaryan wrote:
> +ssize_t psi_trigger_parse(char *buf, size_t nbytes, enum psi_res res,
> + enum psi_states *state, u32 *threshold_us, u32 *win_sz_us)
> +{
> + bool some;
> + bool threshold_pct;
> + u32 threshold;
> + u32 win_
On Fri, Dec 14, 2018 at 09:15:08AM -0800, Suren Baghdasaryan wrote:
> @@ -358,28 +526,23 @@ static void psi_update_work(struct work_struct *work)
> {
> struct delayed_work *dwork;
> struct psi_group *group;
> + u64 next_update;
>
> dwork = to_delayed_work(work);
> gro
On Sat, 15 Dec 2018, Nathan Chancellor wrote:
> While building arm32 allyesconfig, I ran into the following errors:
>
> arch/arm/lib/xor-neon.c:17:2: error: You should compile this file with
> '-mfloat-abi=softfp -mfpu=neon'
>
> In file included from lib/raid6/neon1.c:27:
> /home/nathan/
On Mon, 17 Dec 2018 16:20:42 +0100
Thorsten Leemhuis wrote:
> Hi! Find my first contribution to the kernel documentation in the reply to
> this
> mail. Hopefully a lot more will follow.
Hopefully! Looking forward to it.
> Sorry for using the simple table format for the table. I only noticed t
On Fri, Dec 14, 2018 at 1:34 PM Vincenzo Frascino
wrote:
>
> On 12/12/18 3:04 PM, Andrey Konovalov wrote:
> > On Tue, Dec 11, 2018 at 5:22 PM Vincenzo Frascino
> > wrote:
> >>
> >> Hi Andrey,
> >>
> >> On 06/12/2018 12:24, Andrey Konovalov wrote:
> >>> This commit adds tag-based KASAN specific ho
On Mon, Dec 17, 2018 at 01:23:52PM -0500, Nicolas Pitre wrote:
> On Sat, 15 Dec 2018, Nathan Chancellor wrote:
>
> > While building arm32 allyesconfig, I ran into the following errors:
> >
> > arch/arm/lib/xor-neon.c:17:2: error: You should compile this file with
> > '-mfloat-abi=softfp -mfpu
On Mon, 17 Dec 2018 20:33:42 +0100 Andrey Konovalov
wrote:
> > Curiosity, did you try your patches with SLUB red zoning enabled?
> > Since the area used for the Redzone is just after the payload, aligning the
> > object_size independently from the allocator could have side effects, at
> > least
On Wed, Dec 12, 2018 at 11:08:58PM +0100, Paul Cercueil wrote:
> Add documentation about how to properly use the Ingenic TCU
> (Timer/Counter Unit) drivers from devicetree.
>
> Signed-off-by: Paul Cercueil
> ---
>
> Notes:
> v4: New patch in this series. Corresponds to V2 patches 3-4-5 with
On 12/17/18 10:24 AM, Jonathan Corbet wrote:
> Here's an idea if you feel like improving this: rather than putting an
> inscrutable program inline, add a taint_status script to scripts/ that
> prints out the status in fully human-readable form, with the explanation
> for every set bit.
And some p
On 12/17/18 7:20 AM, Thorsten Leemhuis wrote:
>
> Signed-off-by: Thorsten Leemhuis
> ---
> Documentation/admin-guide/tainted-kernels.rst | 105 --
> 1 file changed, 96 insertions(+), 9 deletions(-)
>
> diff --git a/Documentation/admin-guide/tainted-kernels.rst
> b/Documentation
Hi Rob,
Le lun. 17 déc. 2018 à 22:05, Rob Herring a écrit :
On Wed, Dec 12, 2018 at 11:08:58PM +0100, Paul Cercueil wrote:
Add documentation about how to properly use the Ingenic TCU
(Timer/Counter Unit) drivers from devicetree.
Signed-off-by: Paul Cercueil
---
Notes:
v4: New pat
Quoting Paul Cercueil (2018-12-12 14:08:56)
> This header provides clock numbers for the ingenic,tcu
> DT binding.
>
> Signed-off-by: Paul Cercueil
> Reviewed-by: Rob Herring
> ---
Acked-by: Stephen Boyd
On Mon, Dec 17, 2018 at 6:58 AM Peter Zijlstra wrote:
>
> On Fri, Dec 14, 2018 at 09:15:05AM -0800, Suren Baghdasaryan wrote:
> > Eliminate the idle mode and keep the worker doing 2s update intervals
> > at all times.
>
> That sounds like a bad deal.. esp. so for battery powered devices like
> say
On Mon, Dec 17, 2018 at 7:55 AM Peter Zijlstra wrote:
>
> On Fri, Dec 14, 2018 at 09:15:06AM -0800, Suren Baghdasaryan wrote:
> > The psi monitoring patches will need to determine the same states as
> > record_times(). To avoid calculating them twice, maintain a state mask
> > that can be consulte
On Mon, Dec 17, 2018 at 8:22 AM Peter Zijlstra wrote:
>
> On Fri, Dec 14, 2018 at 09:15:08AM -0800, Suren Baghdasaryan wrote:
> > +ssize_t psi_trigger_parse(char *buf, size_t nbytes, enum psi_res res,
> > + enum psi_states *state, u32 *threshold_us, u32 *win_sz_us)
> > +{
> > + bool some;
On Mon, Dec 17, 2018 at 8:37 AM Peter Zijlstra wrote:
>
> On Fri, Dec 14, 2018 at 09:15:08AM -0800, Suren Baghdasaryan wrote:
> > @@ -358,28 +526,23 @@ static void psi_update_work(struct work_struct *work)
> > {
> > struct delayed_work *dwork;
> > struct psi_group *group;
> > + u6
On Wed, Dec 12, 2018 at 06:49:02PM +0100, Oleg Nesterov wrote:
> On 12/11, Roman Gushchin wrote:
> >
> > On Tue, Dec 11, 2018 at 05:26:32PM +0100, Oleg Nesterov wrote:
> > > On 12/07, Roman Gushchin wrote:
> > > >
> > > > Cgroup v2 freezer tries to put tasks into a state similar to jobctl
> > > > s
在 2018年12月17日 21:00, Borislav Petkov 写道:
> On Sun, Dec 16, 2018 at 09:16:16PM +0800, Lianbo Jiang wrote:
>> +clear_idx
>> +=
>> +The index that the next printk record to read after the last 'clear'
>> +command. It indicates the first record after the last SYSLOG_ACTION
>> +_CLEAR, like issu
在 2018年12月17日 21:01, Borislav Petkov 写道:
> On Sun, Dec 16, 2018 at 09:16:17PM +0800, Lianbo Jiang wrote:
>> For AMD machine with SME feature, makedumpfile tools need to know
>> whether the crash kernel was encrypted or not. If SME is enabled
>> in the first kernel, the crash kernel's page table(pgd
[RESENDING BECAUSE BOUNCED]
> Il giorno 10 dic 2018, alle ore 14:45, Angelo Ruocco
> ha scritto:
>
> 2018-11-30 19:53 GMT+01:00, Paolo Valente :
>>
>>
>>> Il giorno 30 nov 2018, alle ore 19:42, Tejun Heo ha
>>> scritto:
>>>
>>> Hello, Paolo.
>>>
>>> On Fri, Nov 30, 2018 at 07:23:24PM +0100
48 matches
Mail list logo
