From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>,
Tamas K Lengyel <tamas@tklengyel.com>,
xen-devel@lists.xenproject.org
Cc: Keir Fraser <keir@xen.org>, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH 2/2] vm_event: Add altp2m info to HVM events as well
Date: Wed, 23 Dec 2015 17:18:32 +0000 [thread overview]
Message-ID: <567AD768.2080501@citrix.com> (raw)
In-Reply-To: <567AC0EF.5080806@bitdefender.com>
On 23/12/2015 15:42, Razvan Cojocaru wrote:
> On 12/23/2015 04:53 PM, Tamas K Lengyel wrote:
>> Add altp2m information to HVM events as well when altp2m is active.
>>
>> Cc: Razvan Cojocaru <rcojocaru@bitdefender.com>
>> Cc: Keir Fraser <keir@xen.org>
>> Cc: Jan Beulich <jbeulich@suse.com>
>> Cc: Andrew Cooper <andrew.cooper3@citrix.com>
>> Signed-off-by: Tamas K Lengyel <tamas@tklengyel.com>
>> ---
>> xen/arch/x86/hvm/event.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
> Acked-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
next prev parent reply other threads:[~2015-12-23 17:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 14:53 [PATCH 1/2] vm_event: sync domctl Tamas K Lengyel
2015-12-23 14:53 ` [PATCH 2/2] vm_event: Add altp2m info to HVM events as well Tamas K Lengyel
2015-12-23 15:42 ` Razvan Cojocaru
2015-12-23 17:18 ` Andrew Cooper [this message]
2016-01-06 11:32 ` Jan Beulich
2016-01-06 11:42 ` Tamas K Lengyel
2016-01-06 11:48 ` Andrew Cooper
2016-01-06 11:50 ` Tamas K Lengyel
2016-01-12 10:21 ` Jan Beulich
2016-01-12 12:13 ` Tamas K Lengyel
2015-12-23 15:41 ` [PATCH 1/2] vm_event: sync domctl Razvan Cojocaru
2015-12-23 17:17 ` Andrew Cooper
2015-12-23 18:11 ` Tamas K Lengyel
2015-12-23 19:11 ` Razvan Cojocaru
2015-12-23 19:14 ` Andrew Cooper
2015-12-23 20:55 ` Tamas K Lengyel
2015-12-23 21:06 ` Tamas K Lengyel
2015-12-23 21:13 ` Andrew Cooper
2016-01-06 15:48 ` Ian Campbell
2016-01-06 18:29 ` Tamas K Lengyel
2016-01-07 9:58 ` Ian Campbell
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=567AD768.2080501@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=rcojocaru@bitdefender.com \
--cc=tamas@tklengyel.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 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).