linux-kernel - Re: [Xen-devel] [RFC PATCH v4 2/7] xen/pvh: Move PVH entry code out of Xen specific tree

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]

Message-ID: <98eda294-8491-35a2-b278-aeedc079640f@redhat.com>
Date:   Thu, 1 Mar 2018 09:46:23 +0100
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Juergen Gross <jgross@...e.com>,
        Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
        Maran Wilson <maran.wilson@...cle.com>
Cc:     boris.ostrovsky@...cle.com, roger.pau@...rix.com,
        andrew.cooper3@...rix.com, hch@...radead.org, JBeulich@...e.com,
        x86@...nel.org, xen-devel@...ts.xenproject.org,
        linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
        thomas.lendacky@....com, dave.hansen@...ux.intel.com,
        rkrcmar@...hat.com, gregkh@...uxfoundation.org, mchehab@...nel.org,
        hpa@...or.com, linus.walleij@...aro.org, mingo@...hat.com,
        rdunlap@...radead.org, luto@...nel.org, jpoimboe@...hat.com,
        tglx@...utronix.de, bp@...e.de, davem@...emloft.net,
        kirill.shutemov@...ux.intel.com
Subject: Re: [Xen-devel] [RFC PATCH v4 2/7] xen/pvh: Move PVH entry code out
 of Xen specific tree

On 01/03/2018 07:11, Juergen Gross wrote:
>> Probably a better place for these would be
>> arch/x86/platform/pvh/{enlighten.c,head.S}.  (Just because there are no
>> .c or .S files in arch/x86).
> Right.
> 
>> Maybe Xen ought to be moved under
>> arch/x86/platform too.
> And hyperv and kvm, too?

Actually yes, though for kvm I'd move the files in arch/x86/kernel
(arch/x86/kvm is the hypervisor itself, not the "platform").

> No, I think arch/x86/xen/ is fine.

np, it was just a (somewhat crazy) suggestion. :)

Paolo