On 07/06/2015 01:27 PM, Jan Beulich wrote:
>>> No XSM check here or in the handler? Shouldn't the admin controlling
>>> guest properties from the host perspective be permitted control here?
>>> Cc-ing Daniel for his input ...
>>
>> Thinking more about this, the goal here is to be able to monitor
>>
On Mon, Jul 6, 2015 at 6:26 AM, Jan Beulich wrote:
> >>> On 30.06.15 at 16:48, wrote:
> >> > --- a/xen/include/asm-x86/domain.h
> >
> >> >> +++ b/xen/include/asm-x86/domain.h
> >> >> @@ -342,13 +342,15 @@ struct arch_domain
> >> >>
> >> >> /* Monitor options */
> >> >> struct {
> >> >>
>>> On 30.06.15 at 16:23, wrote:
> On 06/26/2015 10:02 AM, Jan Beulich wrote:
> On 15.06.15 at 11:03, wrote:
>>> Added support for a new class of vm_events: VM_EVENT_REASON_REQUEST,
>>> sent via HVMOP_request_vm_event. The guest can request that a
>>> generic vm_event (containing only the vm_
>>> On 30.06.15 at 16:48, wrote:
>> > --- a/xen/include/asm-x86/domain.h
>
>> >> +++ b/xen/include/asm-x86/domain.h
>> >> @@ -342,13 +342,15 @@ struct arch_domain
>> >>
>> >> /* Monitor options */
>> >> struct {
>> >> -uint16_t write_ctrlreg_enabled : 4;
>> >> -uin
On 06/30/2015 05:48 PM, Lengyel, Tamas wrote:
>>> --- a/xen/include/asm-x86/domain.h
>
> >> +++ b/xen/include/asm-x86/domain.h
> >> @@ -342,13 +342,15 @@ struct arch_domain
> >>
> >> /* Monitor options */
> >> struct {
> >> -uint16_t write_ctrlreg_enabled
On 06/30/2015 05:48 PM, Lengyel, Tamas wrote:
>>> --- a/xen/include/asm-x86/domain.h
>
> >> +++ b/xen/include/asm-x86/domain.h
> >> @@ -342,13 +342,15 @@ struct arch_domain
> >>
> >> /* Monitor options */
> >> struct {
> >> -uint16_t write_ctrlreg_enabled
>> --- a/xen/include/asm-x86/domain.h
> >> +++ b/xen/include/asm-x86/domain.h
> >> @@ -342,13 +342,15 @@ struct arch_domain
> >>
> >> /* Monitor options */
> >> struct {
> >> -uint16_t write_ctrlreg_enabled : 4;
> >> -uint16_t write_ctrlreg_sync : 4;
> >> -
On 06/26/2015 10:02 AM, Jan Beulich wrote:
On 15.06.15 at 11:03, wrote:
>> Added support for a new class of vm_events: VM_EVENT_REASON_REQUEST,
>> sent via HVMOP_request_vm_event. The guest can request that a
>> generic vm_event (containing only the vm_event-filled guest registers
>> as infor
>>> On 26.06.15 at 09:17, wrote:
> On 06/26/2015 10:02 AM, Jan Beulich wrote:
> On 15.06.15 at 11:03, wrote:
>>> --- a/xen/include/public/hvm/hvm_op.h
>>> +++ b/xen/include/public/hvm/hvm_op.h
>>> @@ -389,6 +389,10 @@
>>> DEFINE_XEN_GUEST_HANDLE(xen_hvm_evtchn_upcall_vector_t);
>>>
>>> #e
On 06/26/2015 10:02 AM, Jan Beulich wrote:
On 15.06.15 at 11:03, wrote:
>> Added support for a new class of vm_events: VM_EVENT_REASON_REQUEST,
>> sent via HVMOP_request_vm_event. The guest can request that a
>> generic vm_event (containing only the vm_event-filled guest registers
>> as infor
>>> On 15.06.15 at 11:03, wrote:
> Added support for a new class of vm_events: VM_EVENT_REASON_REQUEST,
> sent via HVMOP_request_vm_event. The guest can request that a
> generic vm_event (containing only the vm_event-filled guest registers
> as information) be sent to userspace by setting up the c
On 06/25/2015 11:37 AM, Jan Beulich wrote:
On 25.06.15 at 09:55, wrote:
>> On 06/24/2015 06:03 PM, Jan Beulich wrote:
>> On 24.06.15 at 16:56, wrote:
Would it be fair to say that HVMOP_request_vm_event should be an
exception to this rule (i.e. something along the lines of "if (
>>> On 25.06.15 at 09:55, wrote:
> On 06/24/2015 06:03 PM, Jan Beulich wrote:
> On 24.06.15 at 16:56, wrote:
>>> Would it be fair to say that HVMOP_request_vm_event should be an
>>> exception to this rule (i.e. something along the lines of "if (
>>> unlikely(r12 == HVMOP_request_vm_event) &&
On 06/24/2015 06:03 PM, Jan Beulich wrote:
On 24.06.15 at 16:56, wrote:
>> Would it be fair to say that HVMOP_request_vm_event should be an
>> exception to this rule (i.e. something along the lines of "if (
>> unlikely(r12 == HVMOP_request_vm_event) && orig_pc == regs->pc )",
>> etc.)? Even i
>>> On 24.06.15 at 16:56, wrote:
> On 06/15/2015 12:03 PM, Razvan Cojocaru wrote:
>> Added support for a new class of vm_events: VM_EVENT_REASON_REQUEST,
>> sent via HVMOP_request_vm_event. The guest can request that a
>> generic vm_event (containing only the vm_event-filled guest registers
>> as
On 06/15/2015 12:03 PM, Razvan Cojocaru wrote:
> Added support for a new class of vm_events: VM_EVENT_REASON_REQUEST,
> sent via HVMOP_request_vm_event. The guest can request that a
> generic vm_event (containing only the vm_event-filled guest registers
> as information) be sent to userspace by set
Added support for a new class of vm_events: VM_EVENT_REASON_REQUEST,
sent via HVMOP_request_vm_event. The guest can request that a
generic vm_event (containing only the vm_event-filled guest registers
as information) be sent to userspace by setting up the correct
registers and doing a VMCALL. For e
17 matches
Mail list logo
