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>] [day] [month] [year] [list]
Message-ID: <f3ba02bc-5d88-81a4-85ba-87b6f7c014d9@suse.com>
Date:   Mon, 22 May 2017 17:52:33 +0200
From:   Juergen Gross <jgross@...e.com>
To:     Jan Beulich <JBeulich@...e.com>
Cc:     xen-devel@...ts.xenproject.org, boris.ostrovsky@...cle.com,
        Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [Xen-devel] [PATCH 2/2] xen: add sysfs node for guest type

On 22/05/17 17:37, Jan Beulich wrote:
>>>> On 22.05.17 at 17:28, <jgross@...e.com> wrote:
>> On 22/05/17 17:23, Konrad Rzeszutek Wilk wrote:
>>> On Mon, May 22, 2017 at 10:57:00AM +0200, Juergen Gross wrote:
>>>> --- a/Documentation/ABI/testing/sysfs-hypervisor
>>>> +++ b/Documentation/ABI/testing/sysfs-hypervisor
>>>> @@ -19,6 +19,19 @@ Contact:	xen-devel@...ts.xenproject.org 
>>>>  Description:
>>>>  		Compiler which was used to build the Xen hypervisor
>>>>  
>>>> +What:		/sys/hypervisor/guest_type
>>>> +Date:		May 2017
>>>> +KernelVersion:	4.12
>>>> +Contact:	xen-devel@...ts.xenproject.org 
>>>> +Description:
>>>> +		Type of guest:
>>>> +		"native": standard guest type on arm
>>>> +		"HVM": fully virtualized guest (x86)
>>>> +		"PV": paravirtualized guest (x86)
>>>> +		"PVH": fully virtualized guest without legacy emulation (x86)
>>>> +		"PVHVM": fully virtualized guest using paravirtualized
>>>> +			interfaces (e.g. interrupts, timers) (x86)
>>>
>>> What about KVM? Shouldn't that also be here?
>>
>> /sys/hypervisor is Xen-only (at least up to now).
> 
> How that? It's being created by drivers/base/hypervisor.c,
> and iirc had been introduced for s390 originally.

Hmm, cscope fooled me. Maybe it should build the data base for all
architectures...

Thanks for the note!


Juergen

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ