Re: [PATCH v2 05/20] docs-rst: CodingStyle.rst: Convert to ReST markup

On Mon, 2016-09-12 at 23:17 -0300, Mauro Carvalho Chehab wrote: > - Fix all chapter identation; > - add c blocks where needed; Assuming this is really useful and people agree with simple conversions of .txt to .rst (and it does have some use), there are a couple funky conversions if

[PATCH v2 10/20] ManagementStyle.rst: convert it to ReST markup

- Convert document name to ReST; - Convert footnotes; - Convert sections to ReST format; - Don't use _foo_, as Sphinx doesn't support underline. Instead, use bold; - While here, remove whitespaces at the end of lines. Signed-off-by: Mauro Carvalho Chehab ---

[PATCH v2 14/20] SubmittingDrivers.rst: convert it to ReST markup

- Change the document title markup to make it on a higher level; - Add blank lines as needed, to improve the output; - use italics for the country-code at kernel.org ftp URL. Signed-off-by: Mauro Carvalho Chehab --- .../development-process/SubmittingDrivers.rst |

[PATCH v2 03/20] docs-rst: applying-patches.rst: convert it to ReST markup

- use the correct markup to identify each section; - Add some blank lines for Sphinx to properly interpret the markups; - Remove a blank space on some paragraphs; - Fix the verbatim and bold markups; - Cleanup the remaining errors to make Sphinx happy. Signed-off-by: Mauro Carvalho Chehab

[PATCH v2 12/20] stable_api_nonsense.rst: convert it to ReST markup

Add markups for it to be properly parsed by Sphinx. As people browsing this document may not notice that the source file title is "stable_api_nonsense", I opted to use bold to the rationale for this document. I also found it better to add a note when it says that the nonsense applies only to the

[PATCH v2 04/20] docs-rst: Changes.rst: convert it to ReST markup

- Fix chapter identation inconsistencies; - Convert table to ReST format; - use the right tag for bullets; - Fix bold emphasis; - mark blocks with :: tags; - use verbatim font for files; - make Sphinx happy Signed-off-by: Mauro Carvalho Chehab ---

[PATCH v2 18/20] doc: development-process: convert it to ReST markup

This document is on good shape: all it was needed was to fix the section markups, add a toctree, convert the tables and add a few code/quote blocks. While not strictly required, I opted to use lowercase for the titles, just like the other books that were converted to Sphinx. Signed-off-by: Mauro

[PATCH v2 15/20] SubmittingPatches.rst: convert it to ReST markup

- Change the sections to use ReST markup; - Add cross-references where needed; - convert aspas to verbatim text; - use code block tags; - make Sphinx happy. Signed-off-by: Mauro Carvalho Chehab --- .../development-process/SubmittingPatches.rst | 233

[PATCH v2 02/20] docs-rst: HOWTO.rst: convert to ReST notation

This document is almost compiant with ReST notation, but some small adjustments are needed to make it parse properly by Sphinx (mostly, add blank lines where needed). Signed-off-by: Mauro Carvalho Chehab --- Documentation/development-process/HOWTO.rst | 53

[PATCH v2 20/20] doc: Add the development-process to Sphinx build

Add an index and put it at Documentation/index.rst, in order to allow building the Kernel develpment documentation on Sphinx. Signed-off-by: Mauro Carvalho Chehab --- Documentation/conf.py | 2 ++ Documentation/development-process/conf.py | 10

[PATCH v2 01/20] docs-rst: move HOWTO and mentioned documents to a separate dir

In preparation to convert the Kernel development documentation to ReST, move them to a separate dir and rename their extension to RST. Please notice that the main README file was not moved. It probably makes sense to move it too as well, in order to be able to parse it via Sphinx, but this could

[PATCH v2 13/20] stable_kernel_rules.rst: convert it to ReST markup

- use ReST markups for section headers; - add cross-references to the options; - mark code blocks; - a few minor changes to make Sphinx happy. Signed-off-by: Mauro Carvalho Chehab --- .../development-process/stable_kernel_rules.rst| 101 ++--- 1

[PATCH v2 07/20] CodingStyle.rst: replace underline markups

Sphinx doesn't accept underline markups by purpose. While we might hack it via CSS, this won't be portable with non-html outputs. So, let's replace those by bold. Signed-off-by: Mauro Carvalho Chehab --- Documentation/development-process/CodingStyle.rst | 32

[PATCH v2 05/20] docs-rst: CodingStyle.rst: Convert to ReST markup

- Fix all chapter identation; - add c blocks where needed; Signed-off-by: Mauro Carvalho Chehab --- Documentation/development-process/CodingStyle.rst | 253 -- 1 file changed, 187 insertions(+), 66 deletions(-) diff --git

[PATCH v2 00/20] Create a book for Kernel development

There are several documents related to Kernel development, where the HOWTO working like an index to most of them. There are also a series of files describing the development process. Convert the documents mentioned at the HOWTO (including it) and the development-process/ documents to ReST and add

[PATCH v2 17/20] doc: development-process: rename files to rst

Prepare conversion to ReST by renaming all files to .rst. Signed-off-by: Mauro Carvalho Chehab --- Documentation/development-process/{1.Intro => 1.Intro.rst}| 0 Documentation/development-process/{2.Process => 2.Process.rst}| 0

[PATCH v2 16/20] HOWTO.rst: add cross-references to other documents

The other documents at kernel-development are all mentioned by HOWTO. Convert those mention to cross-references. Signed-off-by: Mauro Carvalho Chehab --- Documentation/development-process/Changes.rst | 2 ++ Documentation/development-process/CodingStyle.rst

[PATCH v2 06/20] CodingStyle.rst: use the proper tag for verbatim font

Instead of using "foo", use ``foo`` for the names that are literal. Signed-off-by: Mauro Carvalho Chehab --- Documentation/development-process/CodingStyle.rst | 98 +++ 1 file changed, 49 insertions(+), 49 deletions(-) diff --git

[PATCH v2 11/20] SecurityBugs.rst: convert it to ReST markup

Add a name for the document and convert the sections to ReST markups. Signed-off-by: Mauro Carvalho Chehab --- Documentation/development-process/SecurityBugs.rst | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git

Re: [PATCH 09/17] kernel-docs.rst: convert it to ReST markup

I just saved the new .rst file and tested it with rst2html and rst2pdf. Conversion ran without Errors, Markup/Layout looks sensible to me. Some nit-picking: > + > +BOOKS: (Not on-line) > + > + > + * Title: **Linux Device Drivers** > + > + :Author: Alessandro Rubini.

Re: Ping: [PATCH v15 00/13] support "task_isolation" mode

On 2016-09-12 12:01 PM, Chris Metcalf wrote: > The syscall test fails on x86: >> >> $ sudo ./isolation >> [...] >> test_syscall: FAIL (0x100) >> test_syscall (SIGUSR1): FAIL (0x100) > > Your next email suggested adding TIF_TASK_ISOLATION to the set of > flags in

Re: Ping: [PATCH v15 00/13] support "task_isolation" mode

On Monday, September 12, 2016 11:15:45 PM Rafael J. Wysocki wrote: > On Monday, September 12, 2016 06:14:44 PM Peter Zijlstra wrote: > > On Mon, Sep 12, 2016 at 12:01:58PM -0400, Chris Metcalf wrote: > > > On 9/7/2016 5:11 PM, Francis Giraldeau wrote: > > > >When running only the test_jitter(),

Re: [PATCH v5 1/3] mm, proc: Implement /proc//totmaps

Hey Oleg! Thanks for the feedback, I'll keep it in mind, but currently it looks like the patch is on ice for non-implementation related reasons. Rob. @@ -2854,6 +2854,7 @@ static const struct pid_entry tgid_base_stuff[] = { REG("clear_refs", S_IWUSR, proc_clear_refs_operations),

Re: Ping: [PATCH v15 00/13] support "task_isolation" mode

On Monday, September 12, 2016 06:14:44 PM Peter Zijlstra wrote: > On Mon, Sep 12, 2016 at 12:01:58PM -0400, Chris Metcalf wrote: > > On 9/7/2016 5:11 PM, Francis Giraldeau wrote: > > >When running only the test_jitter(), the isolation mode is lost: > > > > > > [ 6741.566048] isolation/9515:

Re: [PATCH v15 04/13] task_isolation: add initial support

On 9/12/2016 1:41 PM, Andy Lutomirski wrote: On Sep 9, 2016 1:40 PM, "Chris Metcalf" wrote: On 9/2/2016 1:28 PM, Andy Lutomirski wrote: On Sep 2, 2016 7:04 AM, "Chris Metcalf" wrote: On 8/30/2016 3:50 PM, Andy Lutomirski wrote: On Tue, Aug 30,

Re: [PATCH 00/17] Create a book for Kernel development

Em Mon, 12 Sep 2016 10:40:41 -0600 Jonathan Corbet escreveu: > On Mon, 12 Sep 2016 11:47:51 -0300 > Mauro Carvalho Chehab wrote: > > > There are several documents related to Kernel development, where the > > HOWTO working like an index to most of them.

Re: [RFC PATCH v2 20/20] x86: Add support to make use of Secure Memory Encryption

On Mon, Aug 22, 2016 at 05:39:08PM -0500, Tom Lendacky wrote: > This patch adds the support to check if SME has been enabled and if the > mem_encrypt=on command line option is set. If both of these conditions > are true, then the encryption mask is set and the kernel is encrypted > "in place." >

Re: Ping: [PATCH v15 00/13] support "task_isolation" mode

On 9/7/2016 5:11 PM, Francis Giraldeau wrote: On 2016-08-29 12:27 PM, Chris Metcalf wrote: On 8/16/2016 5:19 PM, Chris Metcalf wrote: Here is a respin of the task-isolation patch set. No concerns have been raised yet with the v15 version of the patch series in the two weeks since I posted it,

Re: [PATCH v5 0/3] mm, proc: Implement /proc//totmaps

On Mon, Sep 12, 2016 at 10:15 AM, Michal Hocko wrote: > On Mon 12-09-16 08:31:36, Sonny Rao wrote: >> On Mon, Sep 12, 2016 at 5:02 AM, Michal Hocko wrote: >> > On Mon 05-09-16 16:14:06, robert.f...@collabora.com wrote: >> >> From: Robert Foss

Re: [PATCH v5 0/3] mm, proc: Implement /proc//totmaps

On Mon 12-09-16 08:31:36, Sonny Rao wrote: > On Mon, Sep 12, 2016 at 5:02 AM, Michal Hocko wrote: > > On Mon 05-09-16 16:14:06, robert.f...@collabora.com wrote: > >> From: Robert Foss > >> > >> This series provides the /proc/PID/totmaps feature,

Re: [RFC PATCH v2 19/20] x86: Access the setup data through debugfs un-encrypted

On Mon, Aug 22, 2016 at 05:38:59PM -0500, Tom Lendacky wrote: > Since the setup data is in memory in the clear, it must be accessed as > un-encrypted. Always use ioremap (similar to sysfs setup data support) > to map the data. > > Signed-off-by: Tom Lendacky > --- >

Re: [RFC PATCH v2 11/20] mm: Access BOOT related data in the clear

On Aug 22, 2016 6:53 PM, "Tom Lendacky" wrote: > > BOOT data (such as EFI related data) is not encyrpted when the system is > booted and needs to be accessed as non-encrypted. Add support to the > early_memremap API to identify the type of data being accessed so that >

Re: [RFC PATCH v2 16/20] x86: Check for memory encryption on the APs

On Mon, Aug 22, 2016 at 05:38:29PM -0500, Tom Lendacky wrote: > Add support to check if memory encryption is active in the kernel and that > it has been enabled on the AP. If memory encryption is active in the kernel A small nit: let's write out "AP" the first time at least: "... on the

Re: [RFC PATCH v2 12/20] x86: Add support for changing memory encryption attribute

On Mon, Sep 12, 2016 at 10:41:29AM -0500, Tom Lendacky wrote: > Looking at __change_page_attr_set_clr() isn't it possible for some of > the pages to be changed before an error is encountered since it is > looping? If so, we may still need to flush. The CPA_FLUSHTLB flag > should take care of a

Re: [PATCH 00/17] Create a book for Kernel development

On Mon, 12 Sep 2016 11:47:51 -0300 Mauro Carvalho Chehab wrote: > There are several documents related to Kernel development, where the > HOWTO working like an index to most of them. > > Convert the documents mentioned at HOWTO (including it) to ReST and add them > at

Re: [RFC PATCH v2 11/20] mm: Access BOOT related data in the clear

On Mon, Sep 12, 2016 at 10:14:59AM -0500, Tom Lendacky wrote: > I did run checkpatch against everything, but was always under the > assumption that I shouldn't change existing warnings/errors like this. > If it's considered ok since I'm touching that line of code then I'll > take care of those

Re: [RFC PATCH v2 10/20] x86: Insure that memory areas are encrypted when possible

On Mon, Sep 12, 2016 at 10:05:36AM -0500, Tom Lendacky wrote: > I can look into that. The reason I put this here is this is all the > early page fault support that is very specific to this file. I modified > an existing static function to take advantage of the mapping support. Yeah, but all this

[PATCH] [media] MAINTAINERS: update documentation for media subsystem

With ReST conversion, the media subsystem documentation is now located on different directories. Update them. Suggested-by: Joe Perches Cc: LKML Cc: linux-doc Cc: Jonathan Corbet Signed-off-by: Mauro

Re: [PATCH v5 0/3] mm, proc: Implement /proc//totmaps

On Mon, Sep 12, 2016 at 5:02 AM, Michal Hocko wrote: > On Mon 05-09-16 16:14:06, robert.f...@collabora.com wrote: >> From: Robert Foss >> >> This series provides the /proc/PID/totmaps feature, which >> summarizes the information provided by

Re: [RFC PATCH v2 12/20] x86: Add support for changing memory encryption attribute

On 09/09/2016 12:23 PM, Borislav Petkov wrote: > On Mon, Aug 22, 2016 at 05:37:49PM -0500, Tom Lendacky wrote: >> This patch adds support to be change the memory encryption attribute for >> one or more memory pages. >> >> Signed-off-by: Tom Lendacky >> --- >>

Re: [RFC PATCH v2 11/20] mm: Access BOOT related data in the clear

On 09/09/2016 11:38 AM, Borislav Petkov wrote: > On Mon, Aug 22, 2016 at 05:37:38PM -0500, Tom Lendacky wrote: >> BOOT data (such as EFI related data) is not encyrpted when the system is >> booted and needs to be accessed as non-encrypted. Add support to the >> early_memremap API to identify the

Re: [RFC PATCH v2 10/20] x86: Insure that memory areas are encrypted when possible

On 09/09/2016 10:53 AM, Borislav Petkov wrote: > On Mon, Aug 22, 2016 at 05:37:23PM -0500, Tom Lendacky wrote: >> Encrypt memory areas in place when possible (e.g. zero page, etc.) so >> that special handling isn't needed afterwards. >> >> Signed-off-by: Tom Lendacky >>

[PATCH 12/17] stable_api_nonsense.rst: convert it to ReST markup

Add markups for it to be properly parsed by Sphinx. As people browsing this document may not notice that the source file title is "stable_api_nonsense", I opted to use bold to the rationale for this document. I also found it better to add a note when it says that the nonsense applies only to the

[PATCH 13/17] stable_kernel_rules.rst: convert it to ReST markup

- use ReST markups for section headers; - add cross-references to the options; - mark code blocks; - a few minor changes to make Sphinx happy. Signed-off-by: Mauro Carvalho Chehab --- .../kernel-development/stable_kernel_rules.rst | 101 ++--- 1

[PATCH 10/17] ManagementStyle.rst: convert it to ReST markup

- Convert document name to ReST; - Convert footnotes; - Convert sections to ReST format; - Don't use _foo_, as Sphinx doesn't support underline. Instead, use bold; - While here, remove whitespaces at the end of lines. Signed-off-by: Mauro Carvalho Chehab ---

[PATCH 11/17] SecurityBugs.rst: convert it to ReST markup

Add a name for the document and convert the sections to ReST markups. Signed-off-by: Mauro Carvalho Chehab --- Documentation/kernel-development/SecurityBugs.rst | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git

[PATCH 00/17] Create a book for Kernel development

There are several documents related to Kernel development, where the HOWTO working like an index to most of them. Convert the documents mentioned at HOWTO (including it) to ReST and add them at the Sphinx build. NOTE: HOWTO also mentions the /README document on it. While IMHO it makes sense to

[PATCH 03/17] docs-rst: applying-patches.rst: convert it to ReST markup

- use the correct markup to identify each section; - Add some blank lines for Sphinx to properly interpret the markups; - Remove a blank space on some paragraphs; - Fix the verbatim and bold markups; - Cleanup the remaining errors to make Sphinx happy. Signed-off-by: Mauro Carvalho Chehab

[PATCH 02/17] docs-rst: HOWTO.rst: convert to ReST notation

This document is almost compiant with ReST notation, but some small adjustments are needed to make it parse properly by Sphinx (mostly, add blank lines where needed). Signed-off-by: Mauro Carvalho Chehab --- Documentation/kernel-development/HOWTO.rst | 53

[PATCH 14/17] SubmittingDrivers.rst: convert it to ReST markup

- Change the document title markup to make it on a higher level; - Add blank lines as needed, to improve the output; - use italics for the country-code at kernel.org ftp URL. Signed-off-by: Mauro Carvalho Chehab --- .../kernel-development/SubmittingDrivers.rst |

[PATCH 04/17] docs-rst: Changes.rst: convert it to ReST markup

- Fix chapter identation inconsistencies; - Convert table to ReST format; - use the right tag for bullets; - Fix bold emphasis; - mark blocks with :: tags; - use verbatim font for files; - make Sphinx happy Signed-off-by: Mauro Carvalho Chehab ---

[PATCH 06/17] CodingStyle.rst: use the proper tag for verbatim font

Instead of using "foo", use ``foo`` for the names that are literal. Signed-off-by: Mauro Carvalho Chehab --- Documentation/kernel-development/CodingStyle.rst | 98 1 file changed, 49 insertions(+), 49 deletions(-) diff --git

[PATCH 05/17] docs-rst: CodingStyle.rst: Convert to ReST markup

- Fix all chapter identation; - add c blocks where needed; Signed-off-by: Mauro Carvalho Chehab --- Documentation/kernel-development/CodingStyle.rst | 253 +-- 1 file changed, 187 insertions(+), 66 deletions(-) diff --git

[PATCH 09/17] kernel-docs.rst: convert it to ReST markup

This one required lots of manual work, for it to be properly displayed. Signed-off-by: Mauro Carvalho Chehab --- Documentation/kernel-development/kernel-docs.rst | 1514 +++--- 1 file changed, 786 insertions(+), 728 deletions(-) diff --git

[PATCH 07/17] CodingStyle.rst: replace underline markups

Sphinx doesn't accept underline markups by purpose. While we might hack it via CSS, this won't be portable with non-html outputs. So, let's replace those by bold. Signed-off-by: Mauro Carvalho Chehab --- Documentation/kernel-development/CodingStyle.rst | 32

[PATCH 17/17] docs-rst: build stuff at kernel-development on Sphinx

Add an index and put it at Documentation/index.rst, in order to allow building the Kernel develpment documentation on Sphinx. Signed-off-by: Mauro Carvalho Chehab --- Documentation/index.rst| 1 + Documentation/kernel-development/index.rst | 29

Re: [RFC PATCH v2 18/20] x86/kvm: Enable Secure Memory Encryption of nested page tables

On Mon, Aug 22, 2016 at 05:38:49PM -0500, Tom Lendacky wrote: > Update the KVM support to include the memory encryption mask when creating > and using nested page tables. > > Signed-off-by: Tom Lendacky > --- > arch/x86/include/asm/kvm_host.h |3 ++- >

Re: [RFC PATCH v2 07/20] x86: Provide general kernel support for memory encryption

On 09/08/2016 08:55 AM, Borislav Petkov wrote: > On Thu, Sep 08, 2016 at 08:26:27AM -0500, Tom Lendacky wrote: >> When does this value get initialized? Since _PAGE_ENC is #defined to >> sme_me_mask, which is not set until the boot process begins, I'm afraid >> we'd end up using the initial value

Re: [RFC PATCH v2 15/20] iommu/amd: AMD IOMMU support for memory encryption

On Mon, Aug 22, 2016 at 05:38:20PM -0500, Tom Lendacky wrote: > Add support to the AMD IOMMU driver to set the memory encryption mask if > memory encryption is enabled. > > Signed-off-by: Tom Lendacky > --- > arch/x86/include/asm/mem_encrypt.h |2 ++ >

Re: [RFC PATCH v2 14/20] x86: DMA support for memory encryption

On Mon, Aug 22, 2016 at 05:38:07PM -0500, Tom Lendacky wrote: > Since DMA addresses will effectively look like 48-bit addresses when the > memory encryption mask is set, SWIOTLB is needed if the DMA mask of the > device performing the DMA does not support 48-bits. SWIOTLB will be > initialized to