All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Lars Kurth <lars.kurth@citrix.com>, "Tim (Xen.org)" <tim@xen.org>,
	Andrew Cooper <Andrew.Cooper3@citrix.com>
Cc: "Keir (Xen.org)" <keir@xen.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Don Slutz <dslutz@verizon.com>,
	xen-devel <xen-devel@lists.xen.org>,
	Jan Beulich <JBeulich@suse.com>,
	Ian Jackson <Ian.Jackson@citrix.com>
Subject: Re: [RFC] When to use "domain creation flag" or "HVM param"?
Date: Thu, 26 Feb 2015 15:33:08 +0000	[thread overview]
Message-ID: <54EF3CB4.3010408@linaro.org> (raw)
In-Reply-To: <D114AEBD.18B22%lars.kurth@citrix.com>

Hi,

On 26/02/15 11:09, Lars Kurth wrote:
> Tim, Andrew, Jan,
> it seems as if we are slowly coming to some conclusion on this thread. If
> I am mistaken, I am wondering whether it would make sense to have an IRC
> meeting with all the involved stake-holders and report back to the list.

I'm not sure where I should answer...

We have a similar problem on ARM where we have arch-specific information
(GIC version, number of interrupts) which changes between each domain.

On Xen 4.5, we took the approach to create a separate DOMCTL for passing
information. It has to be called before any VCPUs is created
(DOMCTL_set_max_vcpus) and make the code more complicate to handle
because we have to defer some domain initialization.

I took another approach for Xen 4.6 based on Jan suggestion [1]. A v3 as
been send recently [2] and we had some discussion about what is the best
approach.

I hope this will help to sort out a good approach for both ARM and x86.

Regards,

[1] http://lists.xen.org/archives/html/xen-devel/2014-11/msg00522.html
[2] http://lists.xen.org/archives/html/xen-devel/2015-01/msg01184.html

-- 
Julien Grall

  reply	other threads:[~2015-02-26 15:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 20:08 [RFC] When to use "domain creation flag" or "HVM param"? Don Slutz
2015-02-24 10:24 ` Tim Deegan
2015-02-24 10:31   ` Jan Beulich
2015-02-24 10:43     ` Tim Deegan
2015-02-24 10:50     ` Andrew Cooper
2015-02-24 16:48       ` Don Slutz
2015-02-26 10:52       ` Tim Deegan
2015-02-26 11:09         ` Lars Kurth
2015-02-26 15:33           ` Julien Grall [this message]
2015-02-26 15:43             ` Tim Deegan

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=54EF3CB4.3010408@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=dslutz@verizon.com \
    --cc=keir@xen.org \
    --cc=lars.kurth@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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.