From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: kevin.tian@intel.com, wei.liu2@citrix.com,
ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com,
andrew.cooper3@citrix.com, tim@xen.org, xen-devel@lists.xen.org,
eddie.dong@intel.com, Aravind.Gopalakrishnan@amd.com,
jun.nakajima@intel.com, suravee.suthikulpanit@amd.com,
boris.ostrovsky@oracle.com, keir@xen.org,
ian.jackson@eu.citrix.com
Subject: Re: [PATCH 3/5] xen/vm_event: Support for guest-requested events
Date: Fri, 08 May 2015 19:38:37 +0300 [thread overview]
Message-ID: <554CE68D.3010803@bitdefender.com> (raw)
In-Reply-To: <554CFD780200007800078729@mail.emea.novell.com>
On 05/08/2015 07:16 PM, Jan Beulich wrote:
>>>> On 06.05.15 at 19:12, <rcojocaru@bitdefender.com> wrote:
>> Added support for a new class of vm_events: VM_EVENT_REASON_REQUEST,
>
> Perhaps better VM_EVENT_REASON_GUEST_REQUEST?
It does sound better, I'll change it.
>> --- a/xen/arch/x86/hvm/event.c
>> +++ b/xen/arch/x86/hvm/event.c
>> @@ -167,6 +167,20 @@ void hvm_event_xsetbv(unsigned long xcr, uint64_t value)
>> hvm_event_traps(currad->monitor.xsetbv_sync, &req);
>> }
>>
>> +void hvm_event_requested(void)
>> +{
>> + struct vcpu *curr = current;
>> + struct arch_domain *currad = ¤t->domain->arch;
>
> So you latched current into curr and then use current again?
Ack, will fix that.
Thanks,
Razvan
next prev parent reply other threads:[~2015-05-08 16:38 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 17:12 [PATCH 0/5] Vm_event memory introspection helpers Razvan Cojocaru
2015-05-06 17:12 ` [PATCH 1/5] xen/vm_event: Added support for XSETBV events Razvan Cojocaru
2015-05-07 15:43 ` Tim Deegan
2015-05-07 17:44 ` Andrew Cooper
2015-05-07 18:03 ` Andrew Cooper
2015-05-08 6:18 ` Razvan Cojocaru
2015-05-08 7:31 ` Jan Beulich
2015-05-08 9:06 ` Razvan Cojocaru
2015-05-08 9:10 ` Andrew Cooper
[not found] ` <CAErYnsh=N9AvoKFUN+i2oyF_fyQhGY2u4wO=v6y7hXP-thXi+g@mail.gmail.com>
[not found] ` <554C9606.7070103@citrix.com>
2015-05-08 11:05 ` Tamas K Lengyel
2015-05-08 11:52 ` Jan Beulich
2015-05-08 12:09 ` Razvan Cojocaru
2015-05-08 12:39 ` Tamas K Lengyel
2015-05-08 12:21 ` Jan Beulich
2015-05-08 12:23 ` Razvan Cojocaru
2015-05-06 17:12 ` [PATCH 2/5] xen/vm_access: Support for memory-content hiding Razvan Cojocaru
2015-05-08 16:07 ` Jan Beulich
2015-05-08 16:49 ` Razvan Cojocaru
2015-05-08 23:34 ` Tamas K Lengyel
2015-05-09 6:55 ` Razvan Cojocaru
2015-05-09 8:33 ` Tamas K Lengyel
2015-05-09 15:11 ` Razvan Cojocaru
2015-05-11 7:50 ` Jan Beulich
2015-05-11 7:00 ` Jan Beulich
2015-06-08 10:02 ` Razvan Cojocaru
2015-06-08 10:20 ` Jan Beulich
2015-05-06 17:12 ` [PATCH 3/5] xen/vm_event: Support for guest-requested events Razvan Cojocaru
2015-05-07 17:05 ` Tamas K Lengyel
2015-05-07 17:43 ` Razvan Cojocaru
2015-05-08 11:00 ` Tamas K Lengyel
2015-05-08 16:16 ` Jan Beulich
2015-05-08 16:38 ` Razvan Cojocaru [this message]
2015-05-08 16:50 ` Andrew Cooper
2015-06-09 12:44 ` Razvan Cojocaru
2015-05-06 17:12 ` [PATCH 4/5] xen/vm_event: Deny MSR writes if refused by vm_event reply Razvan Cojocaru
2015-05-08 16:23 ` Jan Beulich
2015-05-08 17:05 ` Razvan Cojocaru
2015-05-11 7:03 ` Jan Beulich
2015-05-11 7:44 ` Razvan Cojocaru
2015-05-06 17:12 ` [PATCH 5/5] xen: Write CR0, CR3 and CR4 in arch_set_info_guest() Razvan Cojocaru
2015-05-13 12:11 ` Boris Ostrovsky
2015-05-15 15:57 ` Jan Beulich
2015-05-15 20:45 ` Razvan Cojocaru
2015-05-15 23:13 ` Andrew Cooper
2015-05-16 7:19 ` Razvan Cojocaru
2015-05-17 18:32 ` Tamas K Lengyel
2015-05-18 7:37 ` Razvan Cojocaru
2015-05-19 10:14 ` Tamas K Lengyel
2015-05-19 10:31 ` Jan Beulich
2015-05-19 10:45 ` Tamas K Lengyel
2015-05-19 13:45 ` Jan Beulich
2015-05-20 15:57 ` Tamas K Lengyel
2015-05-19 12:10 ` Razvan Cojocaru
2015-05-18 7:27 ` Jan Beulich
2015-05-18 7:58 ` Razvan Cojocaru
2015-05-18 8:05 ` Jan Beulich
2015-05-18 8:11 ` Razvan Cojocaru
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=554CE68D.3010803@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=eddie.dong@intel.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tim@xen.org \
--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.