All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Roger Pau Monné" <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>
Subject: Re: [MINUTES] Monthly Xen.org Technical Call (2015-07-22)
Date: Thu, 23 Jul 2015 13:42:58 -0400	[thread overview]
Message-ID: <20150723174257.GD6598@konrad-lan.dumpdata.com> (raw)
In-Reply-To: <55B0CD59.1060708@citrix.com>

On Thu, Jul 23, 2015 at 01:17:45PM +0200, Roger Pau Monné 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 do it - but the pieces for dom0 are not implemented and would need work (which 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.
> 

  parent reply	other threads:[~2015-07-23 17:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 17:07 [MINUTES] Monthly Xen.org Technical Call (2015-07-22) Ian Campbell
2015-07-23  9:08 ` Ian Campbell
2015-07-23  9:23   ` Roger Pau Monné
2015-07-23  9:35   ` Andrew Cooper
2015-07-23 10:10     ` Ian Campbell
2015-07-23 10:59   ` Konrad Rzeszutek Wilk
2015-07-23 11:17     ` Roger Pau Monné
2015-07-23 11:18       ` Andrew Cooper
2015-07-23 11:26       ` Ian Campbell
2015-07-23 17:44         ` Konrad Rzeszutek Wilk
2015-07-24  8:59           ` Ian Campbell
2015-07-23 17:42       ` Konrad Rzeszutek Wilk [this message]
2015-07-23 13:45   ` David Vrabel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150723174257.GD6598@konrad-lan.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=Ian.Jackson@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Stefano.Stabellini@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=elena.ufimtseva@oracle.com \
    --cc=ian.campbell@citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.