From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>, xen-devel@lists.xenproject.org
Cc: Keir Fraser <keir@xen.org>, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v4 1/2] x86/hvm/viridian: keep APIC assist page mapped...
Date: Thu, 17 Mar 2016 10:50:36 +0000 [thread overview]
Message-ID: <56EA8BFC.3050209@citrix.com> (raw)
In-Reply-To: <1458203853-4441-2-git-send-email-paul.durrant@citrix.com>
On 17/03/16 08:37, Paul Durrant wrote:
> ... for the lifetime of the domain.
>
> If Xen is to make use of the APIC assist enlightenment then a persistent
> mapping needs to be kept, rather than the temporary one which is currently
> used only to initialize the page content.
>
> This patch also adds a comment block at the top of the source with
> information on the latest version of the spec. from Microsoft and the
> current URL where it may be found.
>
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
> Cc: Keir Fraser <keir@xen.org>
> Cc: Jan Beulich <jbeulich@suse.com>
> Cc: Andrew Cooper <andrew.cooper3@citrix.com>
By the looks of it, this patch textually depends on your Viridian TLB fixes?
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-17 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 8:37 [PATCH v4 0/2] x86/hvm/viridian: APIC assist Paul Durrant
2016-03-17 8:37 ` [PATCH v4 1/2] x86/hvm/viridian: keep APIC assist page mapped Paul Durrant
2016-03-17 10:50 ` Andrew Cooper [this message]
2016-03-17 11:13 ` Paul Durrant
2016-03-17 11:58 ` Jan Beulich
2016-03-17 12:00 ` Paul Durrant
2016-03-17 8:37 ` [PATCH v4 2/2] x86/hvm/viridian: Enable APIC assist enlightenment 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=56EA8BFC.3050209@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=paul.durrant@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.