From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Paul Durrant <paul.durrant@citrix.com>,
David Vrabel <david.vrabel@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: HVMlite ABI specification DRAFT B + implementation outline
Date: Tue, 9 Feb 2016 09:36:36 -0500 [thread overview]
Message-ID: <56B9F974.6090402@oracle.com> (raw)
In-Reply-To: <56B9D455.90909@citrix.com>
On 02/09/2016 06:58 AM, Roger Pau Monné wrote:
> El 9/2/16 a les 11:56, Andrew Cooper ha escrit:
>> On 08/02/16 19:03, Roger Pau Monné wrote:
>>>
>>> Description of physical hardware devices will always come from ACPI, in the
>>> absence of any physical hardware device no ACPI tables will be provided. The
>>> presence of ACPI tables can be detected by finding the RSDP, just like on
>>> bare metal.
>> As we are extending the base structure, why not have an RSDP paddr in it
>> as well? This avoids the need to scan RAM, and also serves as an
>> indication of "No ACPI".
> Right, this seems fine to me. I can send a patch later to expand the
> structure unless anyone else complains.
>
Isn't scanning memory the standard procedure for finding RSDP? Even if
we provide the address, guests will still search the memory (or is it
just Linux that does that?)
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-09 14:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 19:03 HVMlite ABI specification DRAFT B + implementation outline Roger Pau Monné
2016-02-08 21:26 ` Boris Ostrovsky
2016-02-09 10:56 ` Andrew Cooper
2016-02-09 11:58 ` Roger Pau Monné
2016-02-09 12:10 ` Jan Beulich
2016-02-09 13:00 ` Roger Pau Monné
2016-02-09 13:41 ` Jan Beulich
2016-02-09 16:32 ` Roger Pau Monné
2016-02-09 16:41 ` Jan Beulich
2016-02-09 14:36 ` Boris Ostrovsky [this message]
2016-02-09 14:42 ` Andrew Cooper
2016-02-09 14:48 ` Jan Beulich
2016-02-09 13:24 ` Jan Beulich
2016-02-09 15:06 ` Stefano Stabellini
2016-02-09 16:15 ` Jan Beulich
2016-02-09 16:17 ` David Vrabel
2016-02-09 16:28 ` Jan Beulich
2016-02-09 16:26 ` Stefano Stabellini
2016-02-09 16:33 ` Jan Beulich
2016-02-10 12:01 ` Roger Pau Monné
2016-02-10 12:53 ` Jan Beulich
2016-02-10 14:51 ` Roger Pau Monné
2016-02-10 15:14 ` Boris Ostrovsky
2016-02-09 15:14 ` Boris Ostrovsky
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=56B9F974.6090402@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=paul.durrant@citrix.com \
--cc=roger.pau@citrix.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--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.