Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Masayoshi Mizuma <msys.mizuma@xxxxxxxxx>
Subject: Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory
From: Borislav Petkov <bp@xxxxxxxxx>
Date: Tue, 6 Nov 2018 21:45:11 +0100
Cc: Baoquan He <bhe@xxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Chao Fan <fanc.fnst@xxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, x86@xxxxxxxxxx, linux-efi@xxxxxxxxxxxxxxx, linux-acpi@xxxxxxxxxxxxxxx, mingo@xxxxxxxxxx, hpa@xxxxxxxxx, keescook@xxxxxxxxxxxx, rjw@xxxxxxxxxxxxx, lenb@xxxxxxxxxx, ard.biesheuvel@xxxxxxxxxx, indou.takao@xxxxxxxxxxxxxx, caoj.fnst@xxxxxxxxxxxxxx
In-reply-to: <20181106193636.svyjwuwrlgnpuyyf@gabell>
References: <20181015005035.z3xym6nx43hogdge@gabell> <20181016151353.punyk7exekut2543@gabell> <20181016191113.GI5212@zn.tnic> <20181016195429.tovdgqq77gz3eek2@gabell> <20181016195902.GK5212@zn.tnic> <20181022154204.kagmdb55jtoez4ca@gabell> <20181025103345.GF14020@nazgul.tnic> <20181025134050.ggiir77ehntikbwg@gabell> <20181106184519.GA16391@zn.tnic> <20181106193636.svyjwuwrlgnpuyyf@gabell>
User-agent: Mutt/1.10.1 (2018-07-13)

On Tue, Nov 06, 2018 at 02:36:38PM -0500, Masayoshi Mizuma wrote:
> Yes, I think I can see what you are saying. However, I'm not sure how
> I use the setup_data in legacy BIOS environment.

What is "legacy BIOS environment" and what does that have to do with
setup_data?

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

Follow-Ups:
- Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory
  - From: Masayoshi Mizuma

References:
- Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory
  - From: Masayoshi Mizuma
- Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory
  - From: Masayoshi Mizuma
- Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory
  - From: Borislav Petkov
- Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory
  - From: Masayoshi Mizuma
- Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory
  - From: Borislav Petkov
- Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory
  - From: Masayoshi Mizuma
- Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory
  - From: Borislav Petkov
- Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory
  - From: Masayoshi Mizuma
- Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory
  - From: Borislav Petkov
- Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory
  - From: Masayoshi Mizuma

Prev by Date: Re: [PATCH 2/4] efi/arm: defer persistent reservations until after paging_init()
Next by Date: Re: [PATCH 1/4] arm64: memblock: don't permit memblock resizing until linear mapping is up
Previous by thread: Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory
Next by thread: Re: [PATCH v8 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]