From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: Aurelien Chartier <aurelien.chartier@citrix.com>
Cc: jbeulich@suse.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] xsm/flask: Fix XSM support for HVMOP_track_dirty_vram
Date: Tue, 02 Jul 2013 10:54:56 -0400 [thread overview]
Message-ID: <51D2E9C0.6010408@tycho.nsa.gov> (raw)
In-Reply-To: <1372759416-5372-1-git-send-email-aurelien.chartier@citrix.com>
On 07/02/2013 06:03 AM, Aurelien Chartier wrote:
> This patch is intended for Xen 4.1 branch.
>
> The XSM check for HVMOP_track_dirty_vram is done with a call to xsm_hvm_param,
> therefore the switch handling that case should be located in flask_hvm_param
> and not in flask_hvmcontext.
>
> This was fixed upstream by the two following patches :
> * 875756ca34fabc7243c4a682ffd7008710a907e2 (add case in flask_hvm_param)
> * 652f94327383c5517b709f0a3e4b970216b3d375 (remove case from flask_hvmcontext)
>
> Signed-off-by: Aurelien Chartier <aurelien.chartier@citrix.com>
Acked-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
prev parent reply other threads:[~2013-07-02 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 10:03 [PATCH] xsm/flask: Fix XSM support for HVMOP_track_dirty_vram Aurelien Chartier
2013-07-02 14:54 ` Daniel De Graaf [this message]
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=51D2E9C0.6010408@tycho.nsa.gov \
--to=dgdegra@tycho.nsa.gov \
--cc=aurelien.chartier@citrix.com \
--cc=jbeulich@suse.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).