xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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: [RFC][v3][PATCH 1/6] xen:x86: record RMRR mappings
Date: Mon, 18 Aug 2014 15:45:29 +0800	[thread overview]
Message-ID: <53F1AF19.4080003@intel.com> (raw)
In-Reply-To: <53EDD539.90403@citrix.com>

On 2014/8/15 17:39, Andrew Cooper wrote:
> On 15/08/14 09:27, Tiejun Chen wrote:
>> We will expose RMRR mappings to VM so need to record all
>> RMRR mappings firstly.
>>
>> Signed-off-by: Tiejun Chen <tiejun.chen@intel.com>
>> ---
>>   xen/arch/x86/e820.c                |  2 ++
>>   xen/drivers/passthrough/vtd/dmar.c | 14 ++++++++++++++
>>   xen/include/asm-x86/e820.h         |  3 +++
>>   3 files changed, 19 insertions(+)
>>
>> diff --git a/xen/arch/x86/e820.c b/xen/arch/x86/e820.c
>> index 55fe0d6..db44afd 100644
>> --- a/xen/arch/x86/e820.c
>> +++ b/xen/arch/x86/e820.c
>> @@ -34,6 +34,8 @@ static bool_t __initdata e820_verbose;
>>   boolean_param("e820-verbose", e820_verbose);
>>
>>   struct e820map e820;
>> +/* Used to record RMRR mapping. */
>> +rmrr_maps_t rmrr_maps;
>>
>>   /*
>>    * This function checks if the entire range <start,end> is mapped with type.
>> diff --git a/xen/drivers/passthrough/vtd/dmar.c b/xen/drivers/passthrough/vtd/dmar.c
>> index 1152c3a..24321e3 100644
>> --- a/xen/drivers/passthrough/vtd/dmar.c
>> +++ b/xen/drivers/passthrough/vtd/dmar.c
>> @@ -29,6 +29,7 @@
>>   #include <xen/pci.h>
>>   #include <xen/pci_regs.h>
>>   #include <asm/string.h>
>> +#include <asm/e820.h>
>>   #include "dmar.h"
>>   #include "iommu.h"
>>   #include "extern.h"
>> @@ -80,6 +81,18 @@ static int __init acpi_register_rmrr_unit(struct acpi_rmrr_unit *rmrr)
>>       return 0;
>>   }
>>
>> +/* Record RMRR mapping to ready expose VM. */
>> +static int __init rmrr_maps_register(struct acpi_rmrr_unit *rmrr)
>> +{
>
> You absolutely need some protection against calling this function more

Could you show this assumed scenario?

IMO, this should never be happened since we always use a e820 table to 
cover RMRR range/entries.

> than 128 times, or you need to do dynamic allocation of the storage.
>
>> +    rmrr_maps.map[rmrr_maps.nr_map].addr = rmrr->base_address;
>> +    rmrr_maps.map[rmrr_maps.nr_map].size = rmrr->end_address -
>> +                                           rmrr->base_address;
>> +    rmrr_maps.map[rmrr_maps.nr_map].type = E820_RESERVED;
>> +    rmrr_maps.nr_map++;
>> +
>> +    return 0;
>> +}
>> +
>>   static void __init disable_all_dmar_units(void)
>>   {
>>       struct acpi_drhd_unit *drhd, *_drhd;
>> @@ -675,6 +688,7 @@ acpi_parse_one_rmrr(struct acpi_dmar_header *header)
>>                           " end_address %"PRIx64"\n",
>>                           rmrru->base_address, rmrru->end_address);
>>               acpi_register_rmrr_unit(rmrru);
>> +            rmrr_maps_register(rmrru);
>>           }
>>       }
>>
>> diff --git a/xen/include/asm-x86/e820.h b/xen/include/asm-x86/e820.h
>> index 71a804c..74262c9 100644
>> --- a/xen/include/asm-x86/e820.h
>> +++ b/xen/include/asm-x86/e820.h
>> @@ -23,6 +23,8 @@ struct e820map {
>>       struct e820entry map[E820MAX];
>>   };
>>
>> +typedef struct e820map rmrr_maps_t;
>
> This type is a single map of RMRR regions, not multiple maps.
> rmrr_map_t please.

Okay.

Thanks
Tiejun

>
> ~Andrew
>
>> +
>>   extern int e820_all_mapped(u64 start, u64 end, unsigned type);
>>   extern int reserve_e820_ram(struct e820map *e820, uint64_t s, uint64_t e);
>>   extern int e820_change_range_type(
>> @@ -32,6 +34,7 @@ extern int e820_add_range(
>>       struct e820map *, uint64_t s, uint64_t e, uint32_t type);
>>   extern unsigned long init_e820(const char *, struct e820entry *, int *);
>>   extern struct e820map e820;
>> +extern rmrr_maps_t rmrr_maps;
>>
>>   /* These symbols live in the boot trampoline. */
>>   extern struct e820entry e820map[];
>
>

  parent reply	other threads:[~2014-08-18  7:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15  8:27 [RFC][v3][PATCH 0/6] xen: reserve RMRR to avoid conflicting MMIO/RAM Tiejun Chen
2014-08-15  8:27 ` [RFC][v3][PATCH 1/6] xen:x86: record RMRR mappings Tiejun Chen
2014-08-15  9:39   ` Andrew Cooper
2014-08-15 16:29     ` Jan Beulich
2014-08-18  7:42       ` Chen, Tiejun
2014-08-18  9:57         ` Andrew Cooper
2014-08-18 10:05           ` Chen, Tiejun
2014-08-18 12:31           ` Jan Beulich
2014-08-19  2:14             ` Chen, Tiejun
2014-08-19  2:28               ` Chen, Tiejun
2014-08-19 13:12                 ` Jan Beulich
2014-08-18  7:45     ` Chen, Tiejun [this message]
2014-08-18  9:51       ` Andrew Cooper
2014-08-18 10:01         ` Chen, Tiejun
2014-08-18 12:56           ` Jan Beulich
2014-08-15  8:27 ` [RFC][v3][PATCH 2/6] xen:x86: introduce a new hypercall to get " Tiejun Chen
2014-08-15  9:46   ` Andrew Cooper
2014-08-18  7:46     ` Chen, Tiejun
2014-08-15  8:27 ` [RFC][v3][PATCH 3/6] tools:firmware:hvmloader: reserve RMRR mappings in e820 Tiejun Chen
2014-08-15  9:58   ` Andrew Cooper
2014-08-18  7:51     ` Chen, Tiejun
2014-08-18 10:00       ` Andrew Cooper
2014-08-15  8:27 ` [RFC][v3][PATCH 4/6] xen:x86: add XENMEM_reserved_device_memory_map to expose RMRR Tiejun Chen
2014-08-15 12:15   ` Andrew Cooper
2014-08-18  8:00     ` Chen, Tiejun
2014-08-18 10:06       ` Andrew Cooper
2014-08-15  8:27 ` [RFC][v3][PATCH 5/6] tools:libxc: check if mmio BAR is out of RMRR mappings Tiejun Chen
2014-08-15 12:21   ` Andrew Cooper
2014-08-18  8:05     ` Chen, Tiejun
2014-08-15  8:27 ` [RFC][v3][PATCH 6/6] 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=53F1AF19.4080003@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).