Re: [PATCH v6 14/34] x86/mm: Insure that boot memory areas are mapped properly

On Wed, Jun 07, 2017 at 02:15:39PM -0500, Tom Lendacky wrote: > The boot data and command line data are present in memory in a decrypted > state and are copied early in the boot process. The early page fault > support will map these areas as encrypted, so before attempting to copy > them, add

Re: [PATCH v6 13/34] x86/mm: Add support for early encrypt/decrypt of memory

On Wed, Jun 07, 2017 at 02:15:27PM -0500, Tom Lendacky wrote: > Add support to be able to either encrypt or decrypt data in place during > the early stages of booting the kernel. This does not change the memory > encryption attribute - it is used for ensuring that data present in either > an

Re: [PATCH v6 09/34] x86/mm: Simplify p[gum]d_page() macros

On Wed, Jun 07, 2017 at 02:14:45PM -0500, Tom Lendacky wrote: > Create a pgd_pfn() macro similar to the p[um]d_pfn() macros and then > use the p[gum]d_pfn() macros in the p[gum]d_page() macros instead of > duplicating the code. > > Signed-off-by: Tom Lendacky > --- >

Re: [PATCH v2 01/11] crypto: introduce crypto wait for async op

On Sat, Jun 10, 2017 at 11:05:39AM +0300, Gilad Ben-Yossef wrote: > > I guess there is a question if it really is important to know that > your request ended up > on the backlog, rather than being handled.I can imagine it can be used > as back pressure > indication but I wonder if someone is using

Re: [PATCH v2 01/11] crypto: introduce crypto wait for async op

On Sat, Jun 10, 2017 at 6:43 AM, Herbert Xu wrote: > On Mon, May 29, 2017 at 11:22:48AM +0300, Gilad Ben-Yossef wrote: >> >> +static inline int crypto_wait_req(int err, struct crypto_wait *wait) >> +{ >> + switch (err) { >> + case -EINPROGRESS: >> + case