From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Dan Williams <dan.j.williams@intel.com>,
George Dunlap <george.dunlap@citrix.com>
Cc: linux-nvdimm <linux-nvdimm@lists.01.org>,
Roger Pau Monne <roger.pau@citrix.com>,
Jan Beulich <JBeulich@suse.com>, Yi Zhang <yi.z.zhang@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Draft NVDIMM proposal
Date: Tue, 15 May 2018 19:33:58 +0100 [thread overview]
Message-ID: <260a5bae-e878-3c85-ee1a-e5ee56506431__8397.02232410691$1526409195$gmane$org@citrix.com> (raw)
In-Reply-To: <CAPcyv4huEso9OHG65UvMh9vOp-yHOR9sptKpzSC_HhhtgbihOg@mail.gmail.com>
On 15/05/18 19:06, Dan Williams wrote:
> On Tue, May 15, 2018 at 7:19 AM, George Dunlap <george.dunlap@citrix.com> wrote:
>> On 05/11/2018 05:33 PM, Dan Williams wrote:
>>
>> This is all pretty foundational. Xen can read static ACPI tables, but
>> it can't do AML. So to do a proper design for Xen, we need to know:
> Oooh, ok, no AML in Xen...
>
>> 1. If Xen can find out, without Linux's help, what namespaces exist and
>> if there is one it can use for its own purposes
> Yeah, no, not without calling AML methods.
One particularly thorny issue with Xen's architecture is the ownership
of the ACPI OSPM, and the fact that there can only be one in the
system. Dom0 has to be the OSPM in practice, as we don't want to port
most of the Linux drivers and infrastructure in the hypervisor.
If we knew a priori that certain AML methods had no side effects, then
we could in principle execute them from the hypervisor, but this is an
undecideable problem in general. As a result, everything involving AML
requires dom0 to decipher the information and passing it to Xen at boot.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-05-15 18:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 17:29 Draft NVDIMM proposal George Dunlap
2018-05-09 17:35 ` George Dunlap
2018-05-11 16:33 ` Dan Williams
2018-05-11 16:33 ` Dan Williams
2018-05-15 10:05 ` Roger Pau Monné
2018-05-15 10:05 ` Roger Pau Monné
2018-05-15 10:12 ` George Dunlap
2018-05-15 10:12 ` George Dunlap
2018-05-15 12:26 ` Jan Beulich
2018-05-15 12:26 ` Jan Beulich
2018-05-15 13:05 ` George Dunlap
2018-05-15 13:05 ` George Dunlap
2018-05-15 17:33 ` Dan Williams
2018-05-15 17:33 ` Dan Williams
2018-05-15 14:19 ` George Dunlap
2018-05-15 14:19 ` George Dunlap
2018-05-15 18:06 ` Dan Williams
2018-05-15 18:33 ` Andrew Cooper
2018-05-15 18:33 ` Andrew Cooper [this message]
2018-05-17 14:52 ` George Dunlap
2018-05-23 0:31 ` Dan Williams
2018-05-23 0:31 ` Dan Williams
2018-05-17 14:52 ` George Dunlap
2018-05-15 18:06 ` Dan Williams
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='260a5bae-e878-3c85-ee1a-e5ee56506431__8397.02232410691$1526409195$gmane$org@citrix.com' \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=dan.j.williams@intel.com \
--cc=george.dunlap@citrix.com \
--cc=linux-nvdimm@lists.01.org \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yi.z.zhang@intel.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.