From mboxrd@z Thu Jan  1 00:00:00 1970
From: Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [RFC] kvm: x86: export vCPU halted state to sysfs
Date: Mon, 5 Feb 2018 21:04:51 -0500
Message-ID: <20180205210451.05ba5d90@redhat.com>
References: <20180202110137.2e2c1816@redhat.com>
        <597d7701-ea7b-524e-7632-10073284d060@linux.vnet.ibm.com>
        <20180202174249.GA22556@localhost.localdomain>
        <20180202135033.3ecfdd7b@redhat.com>
        <20180202200912.GP26425@localhost.localdomain>
        <20180202151945.52847f8e@redhat.com>
        <20180202204144.GQ26425@localhost.localdomain>
        <14fc370a-0d33-6790-6f14-8e224311e676@linux.vnet.ibm.com>
        <20180205134727.GH25338@redhat.com>
        <20180205103701.59b69703@redhat.com>
        <20180205225020.GB3291@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "Daniel P. =?UTF-8?B?QmVycmFuZ8Op?=" <berrange@redhat.com>,
        Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>,
        Radim =?UTF-8?B?S3LEjW3DocWZ?= <rkrcmar@redhat.com>,
        kvm@vger.kernel.org, pbonzini@redhat.com,
        Peter Krempa <pkrempa@redhat.com>,
        John Ferlan <jferlan@redhat.com>, libvir-list@redhat.com,
        Christian Borntraeger <borntraeger@de.ibm.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:35176 "EHLO mx1.redhat.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752141AbeBFCE4 (ORCPT <rfc822;kvm@vger.kernel.org>);
        Mon, 5 Feb 2018 21:04:56 -0500
In-Reply-To: <20180205225020.GB3291@localhost.localdomain>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Mon, 5 Feb 2018 20:50:20 -0200
Eduardo Habkost <ehabkost@redhat.com> wrote:

> On Mon, Feb 05, 2018 at 10:37:01AM -0500, Luiz Capitulino wrote:
> [...]
> > However, IMHO, what we really want is to add an API to the guest agent
> > to export the CPU online bit from the guest userspace sysfs. This will
> > give the ultimate semantics and move us away from this halted mess.  
> 
> Can't this be detected on the host side without guest agent?  Why
> do we need the guest to tell us what's the state of the virtual
> hardware we're emulating?

I have no idea.