From: Shuo A Liu <shuo.a.liu@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
"H . Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Yu Wang <yu1.wang@intel.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Zhi Wang <zhi.a.wang@intel.com>,
Zhenyu Wang <zhenyuw@linux.intel.com>
Subject: Re: [PATCH v7 08/18] virt: acrn: Introduce EPT mapping management
Date: Mon, 11 Jan 2021 12:03:21 +0800 [thread overview]
Message-ID: <20210111040321.GE22447@shuo-intel.sh.intel.com> (raw)
In-Reply-To: <X/h7bhf9RRGjnJ+a@kroah.com>
On Fri 8.Jan'21 at 16:34:06 +0100, Greg Kroah-Hartman wrote:
>On Wed, Jan 06, 2021 at 03:50:45PM +0800, shuo.a.liu@intel.com wrote:
>> +/**
>> + * struct acrn_vm_memmap - A EPT memory mapping info for a User VM.
>> + * @type: Type of the memory mapping (ACRM_MEMMAP_*).
>> + * Pass to hypervisor directly.
>> + * @attr: Attribute of the memory mapping.
>> + * Pass to hypervisor directly.
>> + * @user_vm_pa: Physical address of User VM.
>> + * Pass to hypervisor directly.
>> + * @service_vm_pa: Physical address of Service VM.
>> + * Pass to hypervisor directly.
>> + * @vma_base: VMA address of Service VM. Pass to hypervisor directly.
>> + * @len: Length of the memory mapping.
>> + * Pass to hypervisor directly.
>> + */
>> +struct acrn_vm_memmap {
>> + __u32 type;
>> + __u32 attr;
>> + __u64 user_vm_pa;
>> + union {
>> + __u64 service_vm_pa;
>> + __u64 vma_base;
>> + };
>> + __u64 len;
>> +};
>
>Endianness?
Same consideration within patch 06/18. Need i specify these values? They
are more like ioctls' paramter values.
Thanks
shuo
>
next prev parent reply other threads:[~2021-01-11 4:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 7:50 [PATCH v7 00/18] HSM driver for ACRN hypervisor shuo.a.liu
2021-01-06 7:50 ` [PATCH v7 01/18] docs: acrn: Introduce ACRN shuo.a.liu
2021-01-18 22:30 ` Randy Dunlap
2021-01-19 1:36 ` Shuo A Liu
2021-01-06 7:50 ` [PATCH v7 02/18] x86/acrn: Introduce acrn_{setup, remove}_intr_handler() shuo.a.liu
2021-01-06 7:50 ` [PATCH v7 03/18] x86/acrn: Introduce acrn_cpuid_base() and hypervisor feature bits shuo.a.liu
2021-01-06 7:50 ` [PATCH v7 04/18] x86/acrn: Introduce hypercall interfaces shuo.a.liu
2021-01-06 7:50 ` [PATCH v7 05/18] virt: acrn: Introduce ACRN HSM basic driver shuo.a.liu
2021-01-06 7:50 ` [PATCH v7 06/18] virt: acrn: Introduce VM management interfaces shuo.a.liu
2021-01-08 15:31 ` Greg Kroah-Hartman
2021-01-11 3:55 ` Shuo A Liu
2021-01-06 7:50 ` [PATCH v7 07/18] virt: acrn: Introduce an ioctl to set vCPU registers state shuo.a.liu
2021-01-08 15:33 ` Greg Kroah-Hartman
2021-01-11 3:59 ` Shuo A Liu
2021-01-06 7:50 ` [PATCH v7 08/18] virt: acrn: Introduce EPT mapping management shuo.a.liu
2021-01-08 15:34 ` Greg Kroah-Hartman
2021-01-11 4:03 ` Shuo A Liu [this message]
2021-01-06 7:50 ` [PATCH v7 09/18] virt: acrn: Introduce I/O request management shuo.a.liu
2021-01-11 21:52 ` Davidlohr Bueso
2021-01-12 6:05 ` Shuo A Liu
2021-01-12 17:29 ` Davidlohr Bueso
2021-01-06 7:50 ` [PATCH v7 10/18] virt: acrn: Introduce PCI configuration space PIO accesses combiner shuo.a.liu
2021-01-06 7:50 ` [PATCH v7 11/18] virt: acrn: Introduce interfaces for PCI device passthrough shuo.a.liu
2021-01-06 7:50 ` [PATCH v7 12/18] virt: acrn: Introduce interrupt injection interfaces shuo.a.liu
2021-01-06 7:50 ` [PATCH v7 13/18] virt: acrn: Introduce interfaces to query C-states and P-states allowed by hypervisor shuo.a.liu
2021-01-06 7:50 ` [PATCH v7 14/18] virt: acrn: Introduce I/O ranges operation interfaces shuo.a.liu
2021-01-06 7:50 ` [PATCH v7 15/18] virt: acrn: Introduce ioeventfd shuo.a.liu
2021-01-06 7:50 ` [PATCH v7 16/18] virt: acrn: Introduce irqfd shuo.a.liu
2021-01-06 7:50 ` [PATCH v7 17/18] virt: acrn: Introduce an interface for Service VM to control vCPU shuo.a.liu
2021-01-06 7:50 ` [PATCH v7 18/18] sample/acrn: Introduce a sample of HSM ioctl interface usage shuo.a.liu
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=20210111040321.GE22447@shuo-intel.sh.intel.com \
--to=shuo.a.liu@intel.com \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yu1.wang@intel.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@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