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: <823fbbfb-d9f7-3b6b-5941-239bf900d0cb@redhat.com>
Date:   Wed, 8 Nov 2017 13:26:16 +0100
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Juergen Gross <jgross@...e.com>, Jan Beulich <JBeulich@...e.com>
Cc:     len.brown@...el.com, x86@...nel.org, tglx@...utronix.de,
        xen-devel@...ts.xenproject.org, boris.ostrovsky@...cle.com,
        mingo@...hat.com, rkrcmar@...hat.com, rjw@...ysocki.net,
        pavel@....cz, kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
        hpa@...or.com
Subject: Re: [Xen-devel] [PATCH 3/3] x86/xen: use guest_late_init to detect
 Xen PVH guest

On 08/11/2017 13:24, Juergen Gross wrote:
>> My understanding of Xen is very rusty at this point, but I think a
>> "completely" legacy-free HVM domain will still have a PCI bus and the
>> Xen platform device on that bus.
>>
>> A PVH domain just knows how to access the Xen PV features.
>
> A HVM domain does so, too. Today maybe only partially, but e.g. event
> channels work in a HVM domain even without the Xen platform device.
> Grant tables can be made working without the platform device, too,
> and I'm already preparing a patch to do exactly that.

What about assigned PCI devices?  I think they are not PV pcifront for
HVM.  So the main difference in the end is the PCI bus.

Paolo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ