[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [RFC XEN PATCH 03/16] xen/x86: add a hypercall XENPF_pmem_add to report host pmem regions
- To: Jan Beulich <JBeulich@xxxxxxxx>
- From: Haozhong Zhang <haozhong.zhang@xxxxxxxxx>
- Date: Mon, 12 Dec 2016 16:38:38 +0800
- Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxx, Xiao Guangrong <guangrong.xiao@xxxxxxxxxxxxxxx>
- Delivery-date: Mon, 12 Dec 2016 08:38:46 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
- Mail-followup-to: Jan Beulich <JBeulich@xxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad@xxxxxxxxxx>, Xiao Guangrong <guangrong.xiao@xxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxx, Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
On 12/12/16 01:30 -0700, Jan Beulich wrote:
On 12.12.16 at 05:16, <haozhong.zhang@xxxxxxxxx> wrote:
On 12/09/16 17:02 -0500, Konrad Rzeszutek Wilk wrote:
On Mon, Oct 10, 2016 at 08:32:22AM +0800, Haozhong Zhang wrote:
+static int pmem_add_check(unsigned long spfn, unsigned long epfn,
+ unsigned long rsv_spfn, unsigned long rsv_epfn,
+ unsigned long data_spfn, unsigned long data_epfn)
+{
+ if ( spfn >= epfn || rsv_spfn >= rsv_epfn || data_spfn >= data_epfn )
+ return 0;
Hm, I think it ought to be possible to have no rsv area..?
A reserved area must be provided to storing frametable and M2P table of
NVDIMM.
Is this really "must" rather than just "should", i.e. can't you do
without even if you prefer to have it?
Jan
It's a must in this version, but I relax this requirement in the WIP
v2 patch that fallback to the ordinary RAM if no reserved pmem area is
indicated.
Haozhong
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel
|
