From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: kevin.tian@intel.com, stefano.stabellini@eu.citrix.com,
ian.jackson@eu.citrix.com, xen-devel@lists.xen.org,
JBeulich@suse.com, yang.z.zhang@intel.com
Subject: Re: [v4][PATCH 4/9] tools:libxc: check if mmio BAR is out of RMRR mappings
Date: Wed, 27 Aug 2014 09:46:57 +0800 [thread overview]
Message-ID: <53FD3891.5020202@intel.com> (raw)
In-Reply-To: <1409085374.28009.37.camel@citrix.com>
On 2014/8/27 4:36, Ian Campbell wrote:
> On Fri, 2014-08-22 at 18:09 +0800, Tiejun Chen wrote:
>
>> + /* We should check if mmio range is out of RMRR mapping.
>> + *
>> + * Assume we have one entry if not enough we'll expand.
>> + */
>
> The usual approach with such hypervisor interfaces (which I suppose
> xc_reserved_device_memory_map turns into) is to first call it with NULL
> to get the required size and then allocate a suitable buffer and call a
> second time.
Ofentimes, RMRR should be rare with one or two entries, even zero. So I
think its reasonable to start posting one entry since this can cover
such a scenario the platform really owns one entry.
>
>
>> + for ( i = 0; i < rc; i++ )
>> + {
>> + rmrr_start = map[i].pfn << PAGE_SHIFT;
>> + rmrr_end = rmrr_start + map[i].count * PAGE_SIZE;
>> + if ( check_mmio_hole(rmrr_start, map[i].count * PAGE_SIZE,
>
> Adding rmrr_size = map... & PAGE_SIZE could be used twice here.
>
Yes, so I think the follows should be expected:
--- a/tools/libxc/xc_hvm_build_x86.c
+++ b/tools/libxc/xc_hvm_build_x86.c
@@ -251,7 +251,7 @@ static int check_rmrr_overlap(xc_interface *xch,
uint64_t mmio_start,
uint64_t mmio_size)
{
struct xen_mem_reserved_device_memory *map = NULL;
- uint64_t rmrr_start = 0, rmrr_end = 0;
+ uint64_t rmrr_start = 0, rmrr_end = 0, rmrr_size = 0;
unsigned int i = 0;
int rc = 0;
/* Assume we have one entry if not enough we'll expand.*/
@@ -295,9 +295,9 @@ static int check_rmrr_overlap(xc_interface *xch,
uint64_t mmio_start,
for ( i = 0; i < rc; i++ )
{
rmrr_start = map[i].start_pfn << PAGE_SHIFT;
- rmrr_end = rmrr_start + map[i].nr_pages * PAGE_SIZE;
- if ( check_mmio_hole(rmrr_start, map[i].nr_pages * PAGE_SIZE,
- mmio_start, mmio_size) )
+ rmrr_size = map[i].nr_pages * PAGE_SIZE;
+ rmrr_end = rmrr_start + rmrr_size;
+ if ( check_mmio_hole(rmrr_start, rmrr_size, mmio_start,
mmio_size) )
{
PERROR("MMIO: [%lx]<->[%lx] overlap RMRR [%lx]<->[%lx]\n",
mmio_start, (mmio_start + mmio_size), rmrr_start,
rmrr_end);
Thanks
Tiejun
> Ian.
>
>
next prev parent reply other threads:[~2014-08-27 1:46 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
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 [this message]
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=53FD3891.5020202@intel.com \
--to=tiejun.chen@intel.com \
--cc=JBeulich@suse.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).