From: Jan Beulich <jbeulich@suse.com>
To: Wei Liu <wl@xen.org>
Cc: "Wei Liu" <liuwe@microsoft.com>, "Paul Durrant" <paul@xen.org>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Michael Kelley" <mikelley@microsoft.com>,
"Xen Development List" <xen-devel@lists.xenproject.org>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH v4 3/7] x86/hyperv: provide Hyper-V hypercall functions
Date: Thu, 23 Jan 2020 12:28:00 +0100 [thread overview]
Message-ID: <c714a185-ee86-c4f4-53fe-4c7f5c05a582@suse.com> (raw)
In-Reply-To: <20200122202343.5703-4-liuwe@microsoft.com>
On 22.01.2020 21:23, Wei Liu wrote:
> --- /dev/null
> +++ b/xen/include/asm-x86/guest/hyperv-hcall.h
> @@ -0,0 +1,98 @@
> +/******************************************************************************
> + * asm-x86/guest/hyperv-hcall.h
> + *
> + * This program is free software; you can redistribute it and/or
> + * modify it under the terms and conditions of the GNU General Public
> + * License, version 2, as published by the Free Software Foundation.
> + *
> + * This program is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> + * General Public License for more details.
> + *
> + * You should have received a copy of the GNU General Public
> + * License along with this program; If not, see <http://www.gnu.org/licenses/>.
> + *
> + * Copyright (c) 2019 Microsoft.
> + */
> +
> +#ifndef __X86_HYPERV_HCALL_H__
> +#define __X86_HYPERV_HCALL_H__
> +
> +#include <xen/lib.h>
> +#include <xen/types.h>
> +
> +#include <asm/asm_defns.h>
> +#include <asm/fixmap.h>
> +#include <asm/guest/hyperv-tlfs.h>
> +#include <asm/page.h>
> +
> +static inline uint64_t hv_do_hypercall(uint64_t control, paddr_t input_addr,
> + paddr_t output_addr)
> +{
> + uint64_t status;
> + register unsigned long r8 asm("r8") = output_addr;
> +
> + asm volatile ("INDIRECT_CALL %P[hcall_page]"
> + : "=a" (status), "+c" (control),
> + "+d" (input_addr) ASM_CALL_CONSTRAINT
> + : "r" (r8),
> + [hcall_page] "p" (fix_x_to_virt(FIX_X_HYPERV_HCALL))
> + : "memory");
> +
> + return status;
> +}
> +
> +static inline uint64_t hv_do_fast_hypercall(uint16_t code,
> + uint64_t input1, uint64_t input2)
> +{
> + uint64_t status;
> + uint64_t control = code | HV_HYPERCALL_FAST_BIT;
> + register unsigned long r8 asm("r8") = input2;
> +
> + asm volatile ("INDIRECT_CALL %P[hcall_page]"
> + : "=a" (status), "+c" (control),
> + "+d" (input1) ASM_CALL_CONSTRAINT
> + : "r" (r8),
> + [hcall_page] "p" (fix_x_to_virt(FIX_X_HYPERV_HCALL))
> + :);
This comes through as a smiley in my mail viewer, because of the
missing blanks immediately inside the outermost parentheses.
> +
> + return status;
> +}
> +
> +static inline uint64_t hv_do_rep_hypercall(uint16_t code, uint16_t rep_count,
> + uint16_t varhead_size,
> + paddr_t input, paddr_t output)
> +{
> + uint64_t control = code;
> + uint64_t status;
> + uint16_t rep_comp;
> +
> + control |= (uint64_t)varhead_size << HV_HYPERCALL_VARHEAD_OFFSET;
> + control |= (uint64_t)rep_count << HV_HYPERCALL_REP_COMP_OFFSET;
What about the upper bit(s) spilling into the next field? Perhaps
better use MASK_INSR() here too?
Also, this leaves the START field zero, which makes me think you
mean ...
> + do {
> + status = hv_do_hypercall(control, input, output);
> + if ( (status & HV_HYPERCALL_RESULT_MASK) != HV_STATUS_SUCCESS )
> + break;
> +
> + rep_comp = MASK_EXTR(status, HV_HYPERCALL_REP_COMP_MASK);
> +
> + control &= ~HV_HYPERCALL_REP_START_MASK;
> + control |= MASK_INSR(rep_comp, HV_HYPERCALL_REP_COMP_MASK);
... REP_START_MASK here.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-01-23 11:28 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 20:23 [Xen-devel] [PATCH v4 0/7] More Hyper-V infrastructure Wei Liu
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 1/7] x86: provide executable fixmap facility Wei Liu
2020-01-22 20:56 ` Andrew Cooper
2020-01-28 15:09 ` Wei Liu
2020-01-23 11:04 ` Jan Beulich
2020-01-28 15:15 ` Wei Liu
2020-01-28 15:38 ` Jan Beulich
2020-01-29 14:42 ` Wei Liu
2020-01-29 14:59 ` Jan Beulich
2020-01-29 16:37 ` Wei Liu
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 2/7] x86/hyperv: setup hypercall page Wei Liu
2020-01-22 21:31 ` Andrew Cooper
2020-01-23 10:04 ` Jan Beulich
2020-01-28 15:19 ` Wei Liu
2020-01-23 1:35 ` Michael Kelley
2020-01-28 15:20 ` Wei Liu
2020-01-23 11:18 ` Jan Beulich
2020-01-23 15:20 ` Michael Kelley
2020-01-28 15:30 ` Wei Liu
2020-01-28 15:41 ` Jan Beulich
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 3/7] x86/hyperv: provide Hyper-V hypercall functions Wei Liu
2020-01-22 21:57 ` Andrew Cooper
2020-01-23 10:13 ` Jan Beulich
2020-01-29 18:25 ` Wei Liu
2020-01-23 11:28 ` Jan Beulich [this message]
2020-01-29 18:37 ` Wei Liu
2020-01-30 8:12 ` Jan Beulich
2020-01-30 11:55 ` Wei Liu
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 4/7] DO NOT APPLY: x86/hyperv: issue an hypercall Wei Liu
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 5/7] x86/hyperv: provide percpu hypercall input page Wei Liu
2020-01-23 15:45 ` Jan Beulich
2020-01-28 15:50 ` Wei Liu
2020-01-28 16:15 ` Jan Beulich
2020-01-28 16:52 ` Wei Liu
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 6/7] x86/hyperv: retrieve vp_index from Hyper-V Wei Liu
2020-01-23 15:48 ` Jan Beulich
2020-01-28 15:55 ` Wei Liu
2020-01-28 16:18 ` Jan Beulich
2020-01-28 16:33 ` Durrant, Paul
2020-01-28 16:53 ` Wei Liu
2020-01-28 17:01 ` Durrant, Paul
2020-01-22 20:23 ` [Xen-devel] [PATCH v4 7/7] x86/hyperv: setup VP assist page Wei Liu
2020-01-22 22:05 ` Andrew Cooper
2020-01-23 15:50 ` Jan Beulich
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=c714a185-ee86-c4f4-53fe-4c7f5c05a582@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=liuwe@microsoft.com \
--cc=mikelley@microsoft.com \
--cc=paul@xen.org \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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;
as well as URLs for NNTP newsgroup(s).