From: Borislav Petkov <bp@alien8.de>
To: Zhao Yakui <yakui.zhao@intel.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, tglx@linutronix.de,
Jason Chen CJ <jason.cj.chen@intel.com>
Subject: Re: [PATCH v6 4/4] x86/acrn: Add hypercall for ACRN guest
Date: Wed, 15 May 2019 09:37:15 +0200 [thread overview]
Message-ID: <20190515073715.GC24212@zn.tnic> (raw)
In-Reply-To: <1556595926-17910-5-git-send-email-yakui.zhao@intel.com>
On Tue, Apr 30, 2019 at 11:45:26AM +0800, Zhao Yakui wrote:
> When the ACRN hypervisor is detected, the hypercall is needed so that the
> ACRN guest can query/config some settings. For example: it can be used
> to query the resources in hypervisor and manage the CPU/memory/device/
> interrupt for guest operating system.
>
> Add the hypercall so that the ACRN guest can communicate with the
> low-level ACRN hypervisor. On x86 it is implemented with the VMCALL
> instruction.
>
> Co-developed-by: Jason Chen CJ <jason.cj.chen@intel.com>
> Signed-off-by: Jason Chen CJ <jason.cj.chen@intel.com>
> Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>
> Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
> ---
> V1->V2: Refine the comments for the function of acrn_hypercall0/1/2
> v2->v3: Use the "vmcall" mnemonic to replace hard-code byte definition
> v4->v5: Use _ASM_X86_ACRN_HYPERCALL_H instead of _ASM_X86_ACRNHYPERCALL_H.
> Use the "VMCALL" mnemonic in comment/commit log.
> Uppercase r8/rdi/rsi/rax for hypercall parameter register in comment.
> v5->v6: Remove explicit local register variable for inline assembly
> ---
> arch/x86/include/asm/acrn_hypercall.h | 84 +++++++++++++++++++++++++++++++++++
> 1 file changed, 84 insertions(+)
> create mode 100644 arch/x86/include/asm/acrn_hypercall.h
>
> diff --git a/arch/x86/include/asm/acrn_hypercall.h b/arch/x86/include/asm/acrn_hypercall.h
> new file mode 100644
> index 0000000..5cb438e
> --- /dev/null
> +++ b/arch/x86/include/asm/acrn_hypercall.h
Questions:
* why isn't this in acrn.h and needs to be a separate header?
* why aren't those functions used anywhere?
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-05-15 7:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 3:45 [PATCH v6 0/4] x86: Add the support of ACRN guest under x86 Zhao Yakui
2019-04-30 3:45 ` [PATCH v6 1/4] x86/Kconfig: Add new config symbol to unify conditional definition of hv_irq_callback_count Zhao Yakui
2019-04-30 3:45 ` [PATCH v6 2/4] x86: Add the support of Linux guest on ACRN hypervisor Zhao Yakui
2019-04-30 3:45 ` [PATCH v6 3/4] x86/acrn: Use HYPERVISOR_CALLBACK_VECTOR for ACRN guest upcall vector Zhao Yakui
2019-05-15 17:23 ` Borislav Petkov
2019-05-27 2:21 ` Zhao, Yakui
2019-05-27 22:43 ` Borislav Petkov
2019-04-30 3:45 ` [PATCH v6 4/4] x86/acrn: Add hypercall for ACRN guest Zhao Yakui
2019-05-15 7:37 ` Borislav Petkov [this message]
2019-05-27 2:57 ` Zhao, Yakui
2019-05-27 22:46 ` Borislav Petkov
2019-05-28 1:08 ` Zhao, Yakui
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=20190515073715.GC24212@zn.tnic \
--to=bp@alien8.de \
--cc=jason.cj.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yakui.zhao@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®