>>> On 09.11.16 at 15:28, wrote:
> On 11/09/2016 01:17 PM, Jan Beulich wrote:
> On 09.11.16 at 10:42, wrote:
>>> +static bool svm_get_pending_event(struct vcpu *v, struct hvm_trap *info)
>>> +{
>>> +struct vmcb_struct *vmcb =
On 11/09/2016 01:17 PM, Jan Beulich wrote:
On 09.11.16 at 10:42, wrote:
>> +static bool svm_get_pending_event(struct vcpu *v, struct hvm_trap *info)
>> +{
>> +struct vmcb_struct *vmcb = v->arch.hvm_svm.vmcb;
>> +
>> +if ( vmcb->eventinj.fields.v )
>> +
>>> On 09.11.16 at 12:49, wrote:
> On 09/11/16 11:32, Razvan Cojocaru wrote:
>> On 11/09/2016 01:17 PM, Jan Beulich wrote:
>> On 09.11.16 at 10:42, wrote:
@@ -259,6 +266,13 @@ struct vm_event_cpuid {
uint32_t _pad;
};
On 11/09/2016 04:04 PM, Jan Beulich wrote:
On 09.11.16 at 12:32, wrote:
>> On 11/09/2016 01:17 PM, Jan Beulich wrote:
>> On 09.11.16 at 10:42, wrote:
--- a/xen/arch/x86/hvm/hvm.c
+++ b/xen/arch/x86/hvm/hvm.c
@@ -532,11
>>> On 09.11.16 at 12:32, wrote:
> On 11/09/2016 01:17 PM, Jan Beulich wrote:
> On 09.11.16 at 10:42, wrote:
>>> --- a/xen/arch/x86/hvm/hvm.c
>>> +++ b/xen/arch/x86/hvm/hvm.c
>>> @@ -532,11 +532,23 @@ void hvm_do_resume(struct vcpu *v)
On 11/09/2016 01:17 PM, Jan Beulich wrote:
>> @@ -259,6 +266,13 @@ struct vm_event_cpuid {
>> > uint32_t _pad;
>> > };
>> >
>> > +struct vm_event_interrupt {
>> > +uint32_t vector;
>> > +uint32_t type;
>> > +uint32_t error_code;
>> > +uint64_t cr2;
>> > +};
> This being
On 09/11/16 11:32, Razvan Cojocaru wrote:
> On 11/09/2016 01:17 PM, Jan Beulich wrote:
> On 09.11.16 at 10:42, wrote:
>>> Added support for a new event type, VM_EVENT_REASON_INTERRUPT,
>>> which is now fired in a one-shot manner when enabled via the new
>>>
On 11/09/2016 01:17 PM, Jan Beulich wrote:
On 09.11.16 at 10:42, wrote:
>> Added support for a new event type, VM_EVENT_REASON_INTERRUPT,
>> which is now fired in a one-shot manner when enabled via the new
>> VM_EVENT_FLAG_GET_NEXT_INTERRUPT vm_event response flag.
>>> On 09.11.16 at 10:42, wrote:
> Added support for a new event type, VM_EVENT_REASON_INTERRUPT,
> which is now fired in a one-shot manner when enabled via the new
> VM_EVENT_FLAG_GET_NEXT_INTERRUPT vm_event response flag.
> The patch also fixes the behaviour of the