From: Wei Liu <wei.liu2@citrix.com>
To: Alexandru Isaila <aisaila@bitdefender.com>
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
rcojocaru@bitdefender.com, George.Dunlap@eu.citrix.com,
ian.jackson@eu.citrix.com, tim@xen.org, xen-devel@lists.xen.org,
tamas@tklengyel.com, jbeulich@suse.com,
andrew.cooper3@citrix.com
Subject: Re: [PATCH v6] x86/hvm: Allow guest_request vm_events coming from userspace
Date: Tue, 22 Aug 2017 15:18:46 +0100 [thread overview]
Message-ID: <20170822141846.y4iutid5znkvuoq4@citrix.com> (raw)
In-Reply-To: <1502970619-25599-1-git-send-email-aisaila@bitdefender.com>
On Thu, Aug 17, 2017 at 02:50:19PM +0300, Alexandru Isaila wrote:
> In some introspection usecases, an in-guest agent needs to communicate
> with the external introspection agent. An existing mechanism is
> HVMOP_guest_request_vm_event, but this is restricted to kernel usecases
> like all other hypercalls.
>
> Introduce a mechanism whereby the introspection agent can whitelist the
> use of HVMOP_guest_request_vm_event directly from userspace.
>
> Signed-off-by: Alexandru Isaila <aisaila@bitdefender.com>
>
> ---
> Changes since V5:
> - Added the bool allow_userspace to the xc_monitor_guest_request
> function
> ---
> tools/libxc/include/xenctrl.h | 2 +-
> tools/libxc/xc_monitor.c | 3 ++-
Acked-by: Wei Liu <wei.liu2@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-08-22 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 11:50 [PATCH v6] x86/hvm: Allow guest_request vm_events coming from userspace Alexandru Isaila
2017-08-18 18:12 ` Tamas K Lengyel
2017-08-22 14:18 ` Wei Liu [this message]
2017-08-25 12:13 ` Jan Beulich
2017-08-25 13:00 ` Alexandru Stefan ISAILA
2017-08-25 13:44 ` Jan Beulich
2017-08-25 15:30 ` Tamas K Lengyel
2017-08-25 15:49 ` George Dunlap
2017-08-25 15:58 ` Jan Beulich
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=20170822141846.y4iutid5znkvuoq4@citrix.com \
--to=wei.liu2@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=aisaila@bitdefender.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=rcojocaru@bitdefender.com \
--cc=sstabellini@kernel.org \
--cc=tamas@tklengyel.com \
--cc=tim@xen.org \
--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.