From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1758360AbdEVNSy (ORCPT <rfc822;w@1wt.eu>);
        Mon, 22 May 2017 09:18:54 -0400
Received: from userp1040.oracle.com ([156.151.31.81]:20372 "EHLO
        userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751007AbdEVNSx (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 22 May 2017 09:18:53 -0400
Subject: Re: [PATCH 2/2] xen: add sysfs node for guest type
To: Juergen Gross <jgross@suse.com>, linux-kernel@vger.kernel.org,
        xen-devel@lists.xenproject.org
References: <20170522085700.488-1-jgross@suse.com>
 <20170522085700.488-3-jgross@suse.com>
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Message-ID: <39fb9867-edf8-8f99-1b1f-73ae78fe945c@oracle.com>
Date: Mon, 22 May 2017 09:17:40 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170522085700.488-3-jgross@suse.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Source-IP: userv0022.oracle.com [156.151.31.74]
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


> diff --git a/Documentation/ABI/testing/sysfs-hypervisor b/Documentation/ABI/testing/sysfs-hypervisor
> index 443196f0aa1c..06850f74ebd4 100644
> --- a/Documentation/ABI/testing/sysfs-hypervisor
> +++ b/Documentation/ABI/testing/sysfs-hypervisor
> @@ -19,6 +19,19 @@ Contact:	xen-devel@lists.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@lists.xenproject.org
> +Description:
> +		Type of guest:
> +		"native": standard guest type on arm
> +		"HVM": fully virtualized guest (x86)

Can we ever get this? Xen sysfs node won't load unless we are
!XEN_NATIVE and then we are either PVH or PVHVM.

-boris

> +		"PV": paravirtualized guest (x86)
> +		"PVH": fully virtualized guest without legacy emulation (x86)
> +		"PVHVM": fully virtualized guest using paravirtualized
> +			interfaces (e.g. interrupts, timers) (x86)
> +
>