From: Julien Grall <julien.grall@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Shannon Zhao <zhaoshenglong@huawei.com>
Cc: Hangaohuai <hangaohuai@huawei.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
andrew@fubar.geek.nz,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
David Vrabel <david.vrabel@citrix.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel <xen-devel@lists.xen.org>,
Parth Dixit <parth.dixit@linaro.org>,
Christoffer Dall <christoffer.dall@linaro.org>,
Shannon Zhao <shannon.zhao@linaro.org>
Subject: Re: Design doc of adding ACPI support for arm64 on Xen - version 4
Date: Wed, 19 Aug 2015 11:37:07 -0700 [thread overview]
Message-ID: <55D4CCD3.4050103@citrix.com> (raw)
In-Reply-To: <55D4A95C020000780009BF99@prv-mh.provo.novell.com>
Hi Jan,
On 19/08/2015 07:05, Jan Beulich wrote:
> ... wouldn't it make more sense to leave the generation of these
> Linux-specific tags to Linux (and allow them to continue to be Linux
> specific), by the same or a second, parallel (Xen) stub? This would
> then also move at least some of the awkward table creation (and
> ideally also copying) to that stub.
We don't want to use a specific Xen entry path. So having a Xen stub is
has to be rule out.
Anyway as said multiple time, there is no issue to drop the "linux," in
the properties. They are only used internally between the stub and the
kernel (both are built in the same image).
It would be pointless to create a stub just for renaming the properties...
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-08-19 18:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 12:13 Design doc of adding ACPI support for arm64 on Xen - version 4 Shannon Zhao
2015-08-19 14:05 ` Jan Beulich
2015-08-19 18:37 ` Julien Grall [this message]
2015-08-20 9:22 ` Jan Beulich
2015-08-20 3:41 ` Shannon Zhao
2015-08-20 9:30 ` Jan Beulich
2015-08-20 12:56 ` Shannon Zhao
2015-08-20 14:06 ` Jan Beulich
2015-08-21 2:25 ` Shannon Zhao
2015-08-21 10:01 ` Jan Beulich
2015-08-27 0:37 ` Julien Grall
2015-08-27 7:52 ` Jan Beulich
2015-08-27 13:50 ` Shannon Zhao
2015-08-27 14:13 ` Jan Beulich
2015-08-27 14:21 ` Shannon Zhao
2015-08-19 15:02 ` Roger Pau Monné
2015-08-20 3:07 ` Shannon Zhao
2015-08-20 4:58 ` Julien Grall
2015-08-20 8:20 ` Roger Pau Monné
2015-08-20 11:22 ` Shannon Zhao
2015-08-20 11:28 ` Roger Pau Monné
2015-08-20 12:13 ` Jan Beulich
2015-08-20 12:29 ` Shannon Zhao
2015-08-20 13:46 ` Roger Pau Monné
2015-08-20 14:09 ` Jan Beulich
2015-08-21 3:04 ` Shannon Zhao
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=55D4CCD3.4050103@citrix.com \
--to=julien.grall@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew@fubar.geek.nz \
--cc=boris.ostrovsky@oracle.com \
--cc=christoffer.dall@linaro.org \
--cc=david.vrabel@citrix.com \
--cc=hangaohuai@huawei.com \
--cc=ian.campbell@citrix.com \
--cc=parth.dixit@linaro.org \
--cc=peter.huangpeng@huawei.com \
--cc=shannon.zhao@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=zhaoshenglong@huawei.com \
/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.