Hi,
On 02/13/18 at 04:22pm, Gioh Kim wrote:
> Jumping between the system kernel and the dump-capture kernel
> has been supported for long time but there is no description
> how to use it. This patch adds the description how to use kexec tool
> to jump to the dump-capture kernel and jump back to
On Tue, 13 Feb 2018 15:55:11 -0800 (PST) David Rientjes
wrote:
> >
> > Is this fine-grained enough? We've had percentage-based tunables in
> > the past, and 10 years later when systems are vastly larger, 1% is too
> > much.
> >
>
> They still have the (current) ability
On 02/13/2018 05:00 PM, David Rientjes wrote:
> Specify that movablecore= can use a percent value.
>
> Remove comment about hugetlb pages not being movable per Mike.
>
> Cc: Mike Kravetz
> Signed-off-by: David Rientjes
Thanks! FWIW,
Reviewed-by:
Specify that movablecore= can use a percent value.
Remove comment about hugetlb pages not being movable per Mike.
Cc: Mike Kravetz
Signed-off-by: David Rientjes
---
.../admin-guide/kernel-parameters.txt | 22 +--
1 file
On Tue, 13 Feb 2018, Mike Kravetz wrote:
> > diff --git a/Documentation/admin-guide/kernel-parameters.txt
> > b/Documentation/admin-guide/kernel-parameters.txt
> > --- a/Documentation/admin-guide/kernel-parameters.txt
> > +++ b/Documentation/admin-guide/kernel-parameters.txt
> > @@ -1825,30
On 02/12/2018 04:24 PM, David Rientjes wrote:
> Both kernelcore= and movablecore= can be used to define the amount of
> ZONE_NORMAL and ZONE_MOVABLE on a system, respectively. This requires
> the system memory capacity to be known when specifying the command line,
> however.
>
> This introduces
On Tue, 13 Feb 2018, Andrew Morton wrote:
> > Both kernelcore= and movablecore= can be used to define the amount of
> > ZONE_NORMAL and ZONE_MOVABLE on a system, respectively. This requires
> > the system memory capacity to be known when specifying the command line,
> > however.
> >
> > This
On Mon, 12 Feb 2018 16:24:25 -0800 (PST) David Rientjes
wrote:
> Both kernelcore= and movablecore= can be used to define the amount of
> ZONE_NORMAL and ZONE_MOVABLE on a system, respectively. This requires
> the system memory capacity to be known when specifying the
Without this patch, the points 1-9 in the list are rendered as an HTML
blockquote containing a list, causing them to be indented further than
the rest of the list.
While at it, also fix the quotation marks around G and P.
Signed-off-by: Jonathan Neuschäfer
---
The mailing list archives[1,2] show no activity since September 2011.
[1]: https://lists.linuxfoundation.org/pipermail/bugme-new/
[2]: https://lists.linuxfoundation.org/pipermail/bugme-janitors/
Signed-off-by: Jonathan Neuschäfer
---
Documentation/process/howto.rst | 8
On 02/13/2018 01:18 PM, Matthew Wilcox wrote:
> On Tue, Feb 13, 2018 at 01:03:18PM -0800, Randy Dunlap wrote:
>> As long as the examples don't dictate style...
>> E.g., Matthew likes to use:
>>
>> + * @gfp: Memory allocation flags.
>>
>> a. Capitalize the first word after @param:
>> b. end with a
On Tue, 13 Feb 2018 13:15:32 -0800
Matthew Wilcox wrote:
> Jon asked me to redo the Context: patch on top of his current docs tree.
> Unfortunately, I was on a plane at the time, so I started fixing some
> other small things, and before I knew it, I'd completely restructured
On Tue, Feb 13, 2018 at 01:03:18PM -0800, Randy Dunlap wrote:
> On 02/13/2018 12:59 PM, Jonathan Corbet wrote:
> > I think this makes sense to do, but I really would like to see an intro
> > comment on the split-man.pl script itself. Somebody wandering through
> > the scripts directory should be
From: Matthew Wilcox
Line up the second line in the way that the example purports to be
showing.
Signed-off-by: Matthew Wilcox
---
Documentation/doc-guide/kernel-doc.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Matthew Wilcox
Instead of asking the user to copy and paste a small perl script from
the documentation, just distribute the perl script in the scripts
directory.
Signed-off-by: Matthew Wilcox
---
Documentation/doc-guide/kernel-doc.rst | 30
From: Matthew Wilcox
I found the layout confusing with multiple introductions to what
kernel-doc is and how to use it.
I made the following changes:
- Moved the 'Including kernel-doc comments' section to the end of
the document -- we should explain what it *is*
From: Matthew Wilcox
The author clearly meant to use the word 'which' here. Also replace
some tabs with spaces which fixes the syntax highlighting in my editor.
Signed-off-by: Matthew Wilcox
---
Documentation/doc-guide/kernel-doc.rst | 16
From: Matthew Wilcox
Jon asked me to redo the Context: patch on top of his current docs tree.
Unfortunately, I was on a plane at the time, so I started fixing some
other small things, and before I knew it, I'd completely restructured
the entire doc-guide/kernel-doc.rst
From: Matthew Wilcox
This section is mentioned in scripts/kernel-doc, so we should mention it
in doc-guide/kernel-doc.rst. There are close to 500 comments using the
Context section already, and almost 300 using a Locking section which
fulfills much the same purpose (and
On Sat, 10 Feb 2018 13:55:15 +0100
Dominik Brodowski wrote:
> Up to now, all commit messages have used the "d" in lower case.
Applied, thanks.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to
On Sun, 04 Feb 2018 18:14:24 +0800
Xiongwei Song wrote:
> There is no file named 'enabled' in the directory tracing/events. It should
> be the file 'enable'.
Makes sense, applied to the docs tree, thanks.
jon
--
To unsubscribe from this list: send the line "unsubscribe
On 02/13/2018 12:59 PM, Jonathan Corbet wrote:
> On Thu, 8 Feb 2018 06:45:07 -0800
> Matthew Wilcox wrote:
>
>> Jon asked me to redo the Context: patch on top of his current docs tree.
>> Unfortunately, I was on a plane at the time, so I started fixing some
>> other small
On Thu, 8 Feb 2018 06:45:07 -0800
Matthew Wilcox wrote:
> Jon asked me to redo the Context: patch on top of his current docs tree.
> Unfortunately, I was on a plane at the time, so I started fixing some
> other small things, and before I knew it, I'd completely restructured
On Tue, Feb 13, 2018 at 8:52 PM, Gioh Kim wrote:
> Jumping between the system kernel and the dump-capture kernel
> has been supported for long time but there is no description
> how to use it. This patch adds the description how to use kexec tool
> to jump to the
Commit d92a8cfcb37e ("locking/lockdep: Rework FS_RECLAIM annotation") removed
reclaim_fs lockdep STATE.
Reflect the change in documentation.
While we are at it, also clarify formula to calculate number of state
bits.
Signed-off-by: Juri Lelli
Cc: Peter Zijlstra
Add section about annotations that can be used to perform additional runtime
checking of locking correctness: assert that certain locks are held and
prevent accidental unlocking.
Signed-off-by: Juri Lelli
Cc: Peter Zijlstra
Cc: Ingo Molnar
Hi,
a couple of patches to lockdep docs.
First one is a small fix for that fact that Peter made documentation
stale (as usual :P).
Second one is an RFC. I thought that adding some info about lockdep
asserts might help spread adoption even wider (mostly regarding
lockdep_pin_lock stuff, which is
>
>
> From: James Hogan [jho...@kernel.org]
> Sent: Thursday, February 8, 2018 12:55 PM
>
> Hi,
>
> On Thu, Dec 07, 2017 at 11:33:47AM +, Miodrag Dinic wrote:
> > > On Wed, Dec 06, 2017 at 05:50:52PM +, Maciej W. Rozycki wrote:
> > > > What
Jumping between the system kernel and the dump-capture kernel
has been supported for long time but there is no description
how to use it. This patch adds the description how to use kexec tool
to jump to the dump-capture kernel and jump back to the system kernel.
Signed-off-by: Gioh Kim
When function description includes brackets after the function name as
suggested by Documentation/doc-guide/kernel-doc, the kernel-doc script
omits the function name from "Scanning doc for" report.
Extending match for identifier name with optional brackets fixes this
issue.
Signed-off-by: Mike
On Fri, 09 Feb 2018, Linus Torvalds wrote:
> On Fri, Feb 9, 2018 at 1:32 AM, Jani Nikula
> wrote:
>>> + # miguel-style comment kludge, look for blank lines after
>>> + # @parameter line to signify start of description
>>
>> The
31 matches
Mail list logo