From: Wei Liu <wei.liu2@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: Wei Liu <wei.liu2@citrix.com>
Subject: [HACKATHON] PVH session note
Date: Wed, 20 Apr 2016 18:36:39 +0100 [thread overview]
Message-ID: <20160420173639.GE11151@citrix.com> (raw)
* HVMlite domu support, some emulation in hypervisor, some modes to consider:
| lapic | ioapic | pit | pic | hpet | pm timer | rtc | comments |
|-------+--------+-----+-----+------+----------+-----+----------|
| n | n | n | n | n | n | n | 0 |
| y | n | n | n | n | n | n | 1 |
| y | y | n | n | n | n | n | 2 |
0. useful for unikernel
1. sensible default -- Andrew and others, lapic part of the cpu core,
others belong to platform
2. pci passthrough and dom0 configuration, use native way as much as
possible, need to implement pci emulation in xen. Andrew: major
portion in xen already. Jan: doubt that. Roger: need to construct
acpi table for guest (boris sent patches already)
Roger: dom0 should use #2, simplify event handling (no need to use
physdev op), acpi tables same as on native and manipulated as needed.
Anderw: invent an acpi table that looks like rsdt pointer, let dom0
refers to.
Korand: no need, it already works.
Anderw: dom0 has access to all tables other than dmar. (only hidden,
dom0 could still access it if tries hard)
(drifted to acpi talks with too many tables names involved)
Everyone please read the manuals / references to understand what's required or
whatnot.
* A new entry point for both dom0 and domu?
No conclusion reached. The discussion will continue.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
reply other threads:[~2016-04-20 17:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160420173639.GE11151@citrix.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).