Re: [PATCH v4 02/14] x86/boot: Add setup_indirect support in early_memremap_is_setup_data

2021-09-22 Thread Daniel Kiper
unctionality was updated. This adds comparable support to the other > function where it was missing. > > Fixes: b3c72fc9a78e ("x86/boot: Introduce setup_indirect") > > Signed-off-by: Ross Philipson Reviewed-by: Daniel Kiper This is the fix. So, I think it should be tak

Re: [PATCH v4 01/14] x86/boot: Fix memremap of setup_indirect structures

2021-09-22 Thread Daniel Kiper
uot;x86/boot: Introduce setup_indirect") > > Signed-off-by: Ross Philipson Reviewed-by: Daniel Kiper This is the fix. So, I think it should be taken now, regardless of the fate of the other patches in the series. Daniel ___ iommu ma

Re: [PATCH 07/13] x86: Secure Launch kernel early boot stub

2020-10-21 Thread Daniel Kiper
On Mon, Oct 19, 2020 at 01:18:22PM -0400, Arvind Sankar wrote: > On Mon, Oct 19, 2020 at 04:51:53PM +0200, Daniel Kiper wrote: > > On Fri, Oct 16, 2020 at 04:51:51PM -0400, Arvind Sankar wrote: > > > On Thu, Oct 15, 2020 at 08:26:54PM +0200, Daniel Kiper wrote: > > > >

Re: [PATCH 07/13] x86: Secure Launch kernel early boot stub

2020-10-19 Thread Daniel Kiper
On Fri, Oct 16, 2020 at 04:51:51PM -0400, Arvind Sankar wrote: > On Thu, Oct 15, 2020 at 08:26:54PM +0200, Daniel Kiper wrote: > > > > I am discussing with Ross the other option. We can create > > .rodata.mle_header section and put it at fixed offset as > > kernel_info

Re: [PATCH 07/13] x86: Secure Launch kernel early boot stub

2020-10-15 Thread Daniel Kiper
On Tue, Sep 29, 2020 at 10:03:47AM -0400, Ross Philipson wrote: > On 9/25/20 3:18 PM, Arvind Sankar wrote: [...] > > You should see them if you do > > readelf -r arch/x86/boot/compressed/vmlinux > > > > In terms of the code, things like: > > > > addl%ebx, (sl_gdt_desc + 2)(%ebx) > > >

Re: [RFC PATCH v1 10/18] x86/efi: Access EFI related tables in the clear

2016-05-25 Thread Daniel Kiper
On Tue, May 24, 2016 at 09:54:31AM -0500, Tom Lendacky wrote: > On 05/12/2016 01:20 PM, Tom Lendacky wrote: > > On 05/10/2016 08:57 AM, Borislav Petkov wrote: > >> On Tue, May 10, 2016 at 02:43:58PM +0100, Matt Fleming wrote: > >>> Is it not possible to maintain some kind of kernel virtual address