From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
JBeulich@suse.com, ian.jackson@eu.citrix.com,
stefano.stabellini@eu.citrix.com, ian.campbell@citrix.com,
yang.z.zhang@intel.com, kevin.tian@intel.com
Cc: xen-devel@lists.xen.org
Subject: Re: [v4][PATCH 3/9] tools:libxc: introduce hypercall for xc_reserved_device_memory_map
Date: Mon, 25 Aug 2014 19:11:43 +0800 [thread overview]
Message-ID: <53FB19EF.9090303@intel.com> (raw)
In-Reply-To: <53F721AD.8010300@citrix.com>
On 2014/8/22 18:55, Andrew Cooper wrote:
> On 22/08/14 11:09, Tiejun Chen wrote:
>> We will introduce that hypercall xc_reserved_device_memory_map
>> to libxc.
>>
>> Signed-off-by: Tiejun Chen <tiejun.chen@intel.com>
>> ---
>> tools/libxc/xc_domain.c | 29 +++++++++++++++++++++++++++++
>> tools/libxc/xenctrl.h | 4 ++++
>> 2 files changed, 33 insertions(+)
>>
>> diff --git a/tools/libxc/xc_domain.c b/tools/libxc/xc_domain.c
>> index c67ac9a..08dc16f 100644
>> --- a/tools/libxc/xc_domain.c
>> +++ b/tools/libxc/xc_domain.c
>> @@ -649,6 +649,35 @@ int xc_domain_set_memory_map(xc_interface *xch,
>>
>> return rc;
>> }
>> +
>> +int xc_reserved_device_memory_map(xc_interface *xch,
>> + struct xen_reserved_device_memory entries[],
>> + uint32_t max_entries)
>> +{
>> + int rc;
>> + struct xen_reserved_device_memory_map memmap = {
>> + .nr_entries = max_entries
>> + };
>> + DECLARE_HYPERCALL_BOUNCE(entries,
>> + sizeof(struct xen_reserved_device_memory) *
>> + max_entries, XC_HYPERCALL_BUFFER_BOUNCE_OUT);
>> +
>> + if ( xc_hypercall_bounce_pre(xch, entries) )
>> + return -1;
>> +
>> + set_xen_guest_handle(memmap.buffer, entries);
>> +
>> + rc = do_memory_op(xch, XENMEM_reserved_device_memory_map,
>> + &memmap, sizeof(memmap));
>> +
>> + xc_hypercall_bounce_post(xch, entries);
>> +
>> + if ( errno == ENOBUFS )
>> + return memmap.nr_entries;
>> +
>> + return rc ? -errno : memmap.nr_entries;
>
> So how does the caller distinguish between "xen filled in N entries" and
> "xen said you need N entries for all the information" ?
Thanks for your reminder, I will add something to check this point.
I think the caller can compare that number of entries as that input
parameter with the return value. If equal, this should be in case of
"xen filled in N entries". If not, this is in case of "xen said you need
N entries for all the information".
Thanks
Tiejun
>
> ~Andrew
>
>> +}
>> +
>> int xc_get_machine_memory_map(xc_interface *xch,
>> struct e820entry entries[],
>> uint32_t max_entries)
>> diff --git a/tools/libxc/xenctrl.h b/tools/libxc/xenctrl.h
>> index 1c5d0db..1cc7852 100644
>> --- a/tools/libxc/xenctrl.h
>> +++ b/tools/libxc/xenctrl.h
>> @@ -1270,6 +1270,10 @@ int xc_domain_set_memory_map(xc_interface *xch,
>> int xc_get_machine_memory_map(xc_interface *xch,
>> struct e820entry entries[],
>> uint32_t max_entries);
>> +
>> +int xc_reserved_device_memory_map(xc_interface *xch,
>> + struct xen_reserved_device_memory entries[],
>> + uint32_t max_entries);
>> #endif
>> int xc_domain_set_time_offset(xc_interface *xch,
>> uint32_t domid,
>
>
next prev parent reply other threads:[~2014-08-25 11:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 10:09 [v4][PATCH 0/9] xen: reserve RMRR to avoid conflicting MMIO/RAM Tiejun Chen
2014-08-22 10:09 ` [v4][PATCH 1/9] xen:vtd:rmrr: export acpi_rmrr_units Tiejun Chen
2014-08-22 10:09 ` [v4][PATCH 2/9] xen:x86: define a new hypercall to get RMRR mappings Tiejun Chen
2014-08-22 10:53 ` Andrew Cooper
2014-08-22 11:36 ` Jan Beulich
2014-08-25 11:03 ` Chen, Tiejun
2014-08-25 11:21 ` Chen, Tiejun
2014-08-25 12:07 ` Andrew Cooper
2014-08-26 3:12 ` Chen, Tiejun
2014-08-26 9:25 ` Andrew Cooper
2014-08-22 10:09 ` [v4][PATCH 3/9] tools:libxc: introduce hypercall for xc_reserved_device_memory_map Tiejun Chen
2014-08-22 10:55 ` Andrew Cooper
2014-08-25 11:11 ` Chen, Tiejun [this message]
2014-08-25 11:58 ` Andrew Cooper
2014-08-22 10:09 ` [v4][PATCH 4/9] tools:libxc: check if mmio BAR is out of RMRR mappings Tiejun Chen
2014-08-26 20:36 ` Ian Campbell
2014-08-27 1:46 ` Chen, Tiejun
2014-08-27 2:20 ` Ian Campbell
2014-08-27 2:40 ` Chen, Tiejun
2014-08-27 2:47 ` Chen, Tiejun
2014-08-22 10:09 ` [v4][PATCH 5/9] hvm_info_table: introduce nr_reserved_device_memory_map Tiejun Chen
2014-08-26 20:38 ` Ian Campbell
2014-08-27 1:54 ` Chen, Tiejun
2014-08-27 1:57 ` Chen, Tiejun
2014-08-27 2:21 ` Ian Campbell
2014-08-27 2:28 ` Chen, Tiejun
2014-08-22 10:09 ` [v4][PATCH 6/9] xen:x86:: support xc_reserved_device_memory_map in compat case Tiejun Chen
2014-08-22 10:09 ` [v4][PATCH 7/9] tools:firmware:hvmloader: introduce hypercall for xc_reserved_device_memory_map Tiejun Chen
2014-08-22 10:09 ` [v4][PATCH 8/9] tools:firmware:hvmloader: check to reserve RMRR mappings in e820 Tiejun Chen
2014-08-22 10:09 ` [v4][PATCH 9/9] xen:vtd: make USB RMRR mapping safe Tiejun Chen
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=53FB19EF.9090303@intel.com \
--to=tiejun.chen@intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@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;
as well as URLs for NNTP newsgroup(s).