Re: [PATCH v7 06/10] xen/domctl: Add XEN_DOMCTL_vmtrace_op

2021-01-29 Thread Andrew Cooper
On 26/01/2021 14:18, Jan Beulich wrote: >> +static int vmtrace_set_option(struct vcpu *v, uint64_t key, uint64_t value) >> +{ >> +struct vcpu_msrs *msrs = v->arch.msrs; >> +bool new_en, old_en = msrs->rtit.ctl & RTIT_CTL_TRACE_EN; >> + >> +switch ( key ) >> +{ >> +case MSR_RTIT_

Re: [PATCH v7 06/10] xen/domctl: Add XEN_DOMCTL_vmtrace_op

2021-01-26 Thread Jan Beulich
On 21.01.2021 22:27, Andrew Cooper wrote: > --- a/xen/arch/x86/domctl.c > +++ b/xen/arch/x86/domctl.c > @@ -155,6 +155,55 @@ void arch_get_domain_info(const struct domain *d, > info->arch_config.emulation_flags = d->arch.emulation_flags; > } > > +static int do_vmtrace_op(struct domain *d, s

[PATCH v7 06/10] xen/domctl: Add XEN_DOMCTL_vmtrace_op

2021-01-21 Thread Andrew Cooper
From: Michał Leszczyński Implement an interface to configure and control tracing operations. Reuse the existing SETDEBUGGING flask vector rather than inventing a new one. Userspace using this interface is going to need platform specific knowledge anyway to interpret the contents of the trace bu