On Mon, Dec 12, 2016 at 05:34:29PM +0700, Suravee Suthikulpanit wrote:
> Hi Konrad,
>
> Thanks for review comments.
>
> On 10/14/2016 10:20 PM, Konrad Rzeszutek Wilk wrote:
> > On Mon, Sep 19, 2016 at 12:52:45AM -0500, Suravee Suthikulpanit wrote:
> > > AVIC introduces two #vmexit handlers:
> > >
>>> On 19.09.16 at 07:52, wrote:
> +void svm_avic_vmexit_do_incomp_ipi(struct cpu_user_regs *regs)
> +{
> +struct vcpu *v = current;
Please name such variables "curr", which at once avoids the need for
the unusual name ...
> +struct vmcb_struct *vmcb = v->arch.hvm_svm.vmcb;
> +u32 ic
Hi Konrad,
Thanks for review comments.
On 10/14/2016 10:20 PM, Konrad Rzeszutek Wilk wrote:
On Mon, Sep 19, 2016 at 12:52:45AM -0500, Suravee Suthikulpanit wrote:
AVIC introduces two #vmexit handlers:
+ * IPIs when the specified Message Type is Fixed
+ * (also known as fixed d
On Mon, Sep 19, 2016 at 12:52:45AM -0500, Suravee Suthikulpanit wrote:
> AVIC introduces two #vmexit handlers:
> * VMEXIT_INCOMP_IPI
> * VMEXIT_DO_NOACCEL
Great.. Can you describe what you are suppose to do with them?
Please keep in mind that the point of the commit description is to
say some
AVIC introduces two #vmexit handlers:
* VMEXIT_INCOMP_IPI
* VMEXIT_DO_NOACCEL
Signed-off-by: Suravee Suthikulpanit
---
xen/arch/x86/hvm/svm/avic.c| 279 +
xen/arch/x86/hvm/svm/svm.c | 8 ++
xen/include/asm-x86/hvm/svm/avic.h | 3 +
xen/
