From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Tamas K Lengyel <tlengyel@novetta.com>, xen-devel@lists.xen.org
Cc: kevin.tian@intel.com, wei.liu2@citrix.com,
ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com,
ian.jackson@eu.citrix.com, eddie.dong@intel.com,
jbeulich@suse.com, jun.nakajima@intel.com,
andrew.cooper3@citrix.com, keir@xen.org
Subject: Re: [PATCH v4 1/3] x86/monitor: add get_capabilities to monitor_op domctl
Date: Thu, 9 Jul 2015 16:00:07 +0300 [thread overview]
Message-ID: <559E7057.1000709@bitdefender.com> (raw)
In-Reply-To: <1436395978-11048-1-git-send-email-tlengyel@novetta.com>
On 07/09/2015 01:52 AM, Tamas K Lengyel wrote:
> Add option to monitor_op domctl to determine the monitor capabilities of the
> system.
>
> Signed-off-by: Tamas K Lengyel <tlengyel@novetta.com>
> ---
> v4: add inline function wrapper for is_singlestep_supported to hvm.h
> v3: move is_singlestep_supported into vmx
> sanity check capabilities for each monitor_op enable/disable
> fix comment typo
> v2: skipped
For the monitor part:
Acked-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
Cheers,
Razvan
prev parent reply other threads:[~2015-07-09 13:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 22:52 [PATCH v4 1/3] x86/monitor: add get_capabilities to monitor_op domctl Tamas K Lengyel
2015-07-08 22:52 ` [PATCH v4 2/3] x86/vm_event: toggle singlestep from vm_event response Tamas K Lengyel
2015-07-08 22:52 ` [PATCH v4 3/3] x86/monitor: don't use hvm_funcs directly Tamas K Lengyel
2015-07-09 6:15 ` Razvan Cojocaru
2015-07-09 8:15 ` Jan Beulich
2015-07-09 12:50 ` Lengyel, Tamas
2015-07-09 12:52 ` Lengyel, Tamas
2015-07-09 12:55 ` Razvan Cojocaru
2015-07-09 9:05 ` [PATCH v4 1/3] x86/monitor: add get_capabilities to monitor_op domctl Ian Campbell
2015-07-09 12:37 ` Lengyel, Tamas
2015-07-09 13:00 ` Razvan Cojocaru [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=559E7057.1000709@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=andrew.cooper3@citrix.com \
--cc=eddie.dong@intel.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tlengyel@novetta.com \
--cc=wei.liu2@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 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.