linux-kernel - Re: [PATCH 1/3] x86: provide an init_mem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 26 Jul 2017 09:45:29 +0200
From:   Juergen Gross <jgross@...e.com>
To:     Boris Ostrovsky <boris.ostrovsky@...cle.com>,
        linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org,
        x86@...nel.org
Cc:     hpa@...or.com, tglx@...utronix.de, mingo@...hat.com
Subject: Re: [PATCH 1/3] x86: provide an init_mem_mapping hypervisor hook

On 25/07/17 16:09, Boris Ostrovsky wrote:
> On 07/25/2017 05:50 AM, Juergen Gross wrote:
>> Provide a hook in hypervisor_x86 called after setting up initial
>> memory mapping.
>>
>> This is needed e.g. by Xen HVM guests to map the hypervisor shared
>> info page.
> 
> This is not necessarily a problem specific to guests so I wonder whether
> the hook should be part of x86_platform_ops or some other x86 structure.

I'm fine with any solution. I've chosen the hypervisor struct as right
now there seems to be a need for HVM Xen guests only.


Juergen