From: Paul Durrant <paul.durrant@citrix.com>
To: xen-devel@lists.xen.org
Subject: [PATCH v2 0/3] x86/viridian improvements
Date: Mon, 4 Aug 2014 14:12:38 +0100 [thread overview]
Message-ID: <1407157961-7239-1-git-send-email-paul.durrant@citrix.com> (raw)
This patch incorporates several improvements to the code supporting
viridian (i.e. hyper-v compatible) enlightenments for Windows guests:
Patch #1 series lays the foundations for adding new viridian
enlightenments such that they can be optionally enabled, and not
immediately exposed to a guest across a save/restore boundary.
Patch #2 fixes a possible DoS issue by correctly noting that all the
logging in the viridian code is actually under the control of the guest
Patch #3 adds support for the 'Partition Time Reference Counter'
enlightenment.
v2:
- Addressed comments from Jan Beulich
- Added patch #2
next reply other threads:[~2014-08-04 13:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 13:12 Paul Durrant [this message]
2014-08-04 13:12 ` [PATCH v2 1/3] x86/viridian: Re-purpose the HVM parameter to be a feature mask Paul Durrant
2014-08-04 13:31 ` Andrew Cooper
2014-08-04 13:50 ` Jan Beulich
2014-08-04 14:50 ` Andrew Cooper
2014-08-04 15:13 ` Jan Beulich
2014-08-04 17:19 ` Paul Durrant
2014-08-04 13:45 ` Jan Beulich
2014-08-04 13:12 ` [PATCH v2 2/3] x86/viridian: Note that logging is under control of the guest Paul Durrant
2014-08-04 13:38 ` Andrew Cooper
2014-08-04 13:45 ` Paul Durrant
2014-08-04 13:12 ` [PATCH v2 3/3] x86/viridian: Add partition time reference counter MSR support Paul Durrant
2014-08-04 14:01 ` Jan Beulich
2014-08-04 14:12 ` Paul Durrant
2014-08-04 14:47 ` Paul Durrant
2014-08-04 15:11 ` Paul Durrant
2014-08-04 15:15 ` Jan Beulich
2014-08-04 15:23 ` Paul Durrant
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=1407157961-7239-1-git-send-email-paul.durrant@citrix.com \
--to=paul.durrant@citrix.com \
--cc=xen-devel@lists.xen.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).