From: Roger Pau Monne <roger.pau@citrix.com>
To: xen-devel@lists.xenproject.org
Subject: [PATCH v3 0/5] tools/libacpi: fix boot flags passed to PVHv2 guests
Date: Mon, 5 Dec 2016 15:04:52 +0000 [thread overview]
Message-ID: <20161205150457.68471-1-roger.pau@citrix.com> (raw)
Hello,
There are a couple of boot flags that should be passed to PVHv2 guests, that
report the lack of VGA and CMOS RTC, and we shouldn't also pass the 8042 flag,
because PVHv2 guests don't have access to such controller. The no CMOS RTC flags
requires that the FADT table is bumped to version 5 at least for PVHv2 guests.
Thanks, Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-12-05 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 15:04 Roger Pau Monne [this message]
2016-12-05 15:04 ` [PATCH v3 1/5] tools/libacpi: add _FADT_ to the FADT boot flags definitions Roger Pau Monne
2016-12-05 15:07 ` Andrew Cooper
2016-12-05 15:39 ` Wei Liu
2016-12-05 15:04 ` [PATCH v3 2/5] tools/libacpi: set FADT boot flag to notify lack of VGA for PVHv2 guests Roger Pau Monne
2016-12-05 15:04 ` [PATCH v3 3/5] tools/libacpi: don't announce a 8042 controller in the FADT " Roger Pau Monne
2016-12-05 15:04 ` [PATCH v3 4/5] tools/libacpi: update FADT layout to support version 5 Roger Pau Monne
2016-12-07 16:04 ` Jan Beulich
2016-12-12 10:45 ` Roger Pau Monne
2016-12-12 11:11 ` Jan Beulich
2016-12-05 15:04 ` [PATCH v3 5/5] tools/libacpi: announce that PVHv2 has no CMOS RTC in FADT Roger Pau Monne
2016-12-07 16:06 ` Jan Beulich
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=20161205150457.68471-1-roger.pau@citrix.com \
--to=roger.pau@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).