From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [MINUTES] Monthly Xen.org Technical Call
	(2015-07-22)
Date: Thu, 23 Jul 2015 13:42:58 -0400
Message-ID: <20150723174257.GD6598@konrad-lan.dumpdata.com>
References: <E1ZHxUW-0003iL-9o@ukmail1.uk.xensource.com>
	<1437642526.19412.54.camel@citrix.com>
	<30D22B78-9B4F-4F80-8CD4-CF2D6753052D@oracle.com>
	<55B0CD59.1060708@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <konrad.wilk@oracle.com>) id 1ZIKWS-0003GD-0e
	for xen-devel@lists.xenproject.org; Thu, 23 Jul 2015 17:43:08 +0000
Content-Disposition: inline
In-Reply-To: <55B0CD59.1060708@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Roger Pau =?iso-8859-1?Q?Monn=E9?= <roger.pau@citrix.com>
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>, Wei Liu <wei.liu2@citrix.com>, Ian Campbell <ian.campbell@citrix.com>, Andrew Cooper <Andrew.Cooper3@citrix.com>, George Dunlap <George.Dunlap@citrix.com>, Stefano Stabellini <Stefano.Stabellini@citrix.com>, David Vrabel <david.vrabel@citrix.com>, Jan Beulich <JBeulich@suse.com>, Ian Jackson <Ian.Jackson@citrix.com>, xen-devel@lists.xenproject.org, Boris Ostrovsky <boris.ostrovsky@oracle.com>
List-Id: xen-devel@lists.xenproject.org

On Thu, Jul 23, 2015 at 01:17:45PM +0200, Roger Pau Monn=E9 wrote:
> El 23/07/15 a les 12.59, Konrad Rzeszutek Wilk ha escrit:
> [...]
> > We forgot to speak about dom0. This work outlined will lay out how to d=
o it - but the pieces for dom0 are not implemented and would need work (whi=
ch actually may be following most of the is_pvh in the hypervisor).
> =

> Let's do that once we have DomU nailed down and the guest ABI marked as
> stable.
> =

> Some work will indeed be needed for Dom0, for example I would like to
> avoid using the current Dom0 builder (construct_dom0, that is suited for
> PV, but all the PVH hacks just make it almost impossible to understand)
> and start from scratch with a more sane approach.

Well construct_dom0 is huge already. Doing surgery on that beast
would be most welcome.

The other issues that I think we will still encounter - which Elena
was looking for AMD - is the handling of decoding of operations
on AMD without qemu-dm involvment. Which meant that we could not
use any of the mmio_handlers - that I believe will still be an
outstanding issue.

So will the setting of various states that the toolstack does right now
but had never been done in the hypervisor - such as the tsc_scaling
for AMD.

Lastly the E820 setup and poking/re-organizing the P2M to match it.

> =

> Roger.
> =