From: Keir Fraser <keir@xen.org>
To: Jean Guyader <jean.guyader@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: "jwcart2@tycho.nsa.gov" <jwcart2@tycho.nsa.gov>,
Jean Guyader <Jean.Guyader@citrix.com>
Subject: Re: Re: [PATCH] xsm: Add support for HVMOP_track_dirty_vram.
Date: Thu, 17 Nov 2011 09:15:35 +0000 [thread overview]
Message-ID: <CAEA8137.343AD%keir@xen.org> (raw)
In-Reply-To: <20111117060115.GA1901@spongy.cam.xci-test.com>
On 17/11/2011 06:01, "Jean Guyader" <jean.guyader@eu.citrix.com> wrote:
> On 07/11 07:53, Jean Guyader wrote:
>>
>> Xen try to inforce the xsm policy when a HVMOP_track_dirty_vram
>> is received (xen/arch/x86/hvm/hvm.c:3637). It was failing because
>> in flask_hvmcontext, xsm didn't have any case for this operation.
>>
>> Signed-off-by: Jean Guyader <jean.guyader@eu.citrix.com>
>
> Can this patch go to 4.1 as well?
Done.
> Thanks,
> Jean
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-11-17 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 19:53 [PATCH] xsm: Add support for HVMOP_track_dirty_vram Jean Guyader
2011-11-17 6:01 ` Jean Guyader
2011-11-17 9:15 ` Keir Fraser [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=CAEA8137.343AD%keir@xen.org \
--to=keir@xen.org \
--cc=Jean.Guyader@citrix.com \
--cc=jean.guyader@eu.citrix.com \
--cc=jwcart2@tycho.nsa.gov \
--cc=xen-devel@lists.xensource.com \
/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).