From: "Jan Beulich" <JBeulich@suse.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v5 0/3] x86/viridian improvements
Date: Tue, 12 Aug 2014 11:38:36 +0100 [thread overview]
Message-ID: <53EA0ACC020000780002B830@mail.emea.novell.com> (raw)
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD0424793@AMSPEX01CL01.citrite.net>
>>> On 12.08.14 at 12:16, <Paul.Durrant@citrix.com> wrote:
> Ping?
I'm afraid just pinging the list rather than specific people not responding
won't have much of an effect.
Jan
>> -----Original Message-----
>> From: xen-devel-bounces@lists.xen.org [mailto:xen-devel-
>> bounces@lists.xen.org] On Behalf Of Paul Durrant
>> Sent: 05 August 2014 14:07
>> To: xen-devel@lists.xen.org
>> Subject: [Xen-devel] [PATCH v5 0/3] x86/viridian improvements
>>
>> This patch series 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 makes logging less verbose
>>
>> Patch #3 adds support for the 'Partition Time Reference Counter'
>> enlightenment.
>>
>> v2:
>> - Addressed comments from Jan Beulich
>> - Added patch #2
>>
>> v3:
>> - Addressed comments from Andrew Cooper and Jan Beulich
>> - Re-worked patch #2
>> - Simplified patch #3 to use guest TSC
>>
>> v4:
>> - Added missing domain info to printks in patch #2
>>
>> v5:
>> - Clarified comment of patch #1 as suggested by David Vrabel
>> - More logging tweaks in patch #2 as suggested by Andrew Cooper
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-08-12 10:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 13:07 [PATCH v5 0/3] x86/viridian improvements Paul Durrant
2014-08-05 13:07 ` [PATCH v5 1/3] x86/viridian: Re-purpose the HVM parameter to be a feature mask Paul Durrant
2014-08-12 15:25 ` Ian Jackson
2014-08-13 11:09 ` Paul Durrant
2014-08-26 20:24 ` Ian Campbell
2014-08-26 20:28 ` Ian Campbell
2014-08-27 8:11 ` Paul Durrant
2014-08-05 13:07 ` [PATCH v5 2/3] x86/viridian: Make logging less verbose Paul Durrant
2014-08-05 13:07 ` [PATCH v5 3/3] x86/viridian: Add partition time reference counter MSR support Paul Durrant
2014-08-12 15:27 ` Ian Jackson
2014-08-13 15:27 ` Egger, Christoph
2014-08-27 14:04 ` Paul Durrant
2014-08-12 10:16 ` [PATCH v5 0/3] x86/viridian improvements Paul Durrant
2014-08-12 10:38 ` Jan Beulich [this message]
2014-08-12 11:49 ` Paul Durrant
2014-08-12 12:17 ` 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=53EA0ACC020000780002B830@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=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).