From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xiao Guangrong Subject: Re: [PATCH 4/4] hvmloader: add support to load extra ACPI tables from qemu Date: Thu, 21 Jan 2016 17:10:50 +0800 Message-ID: <56A0A09A.2050101@linux.intel.com> References: <1451388711-18646-1-git-send-email-haozhong.zhang@intel.com> <1451388711-18646-5-git-send-email-haozhong.zhang@intel.com> <5699362402000078000C7803@prv-mh.provo.novell.com> <20160118005255.GC3528@hz-desktop.sh.intel.com> <569CB47502000078000C7CFB@prv-mh.provo.novell.com> <20160120053132.GA5005@hz-desktop.sh.intel.com> <569F575902000078000C8EDC@prv-mh.provo.novell.com> <20160120110449.GD4939@hz-desktop.sh.intel.com> <569F7B8302000078000C8FF8@prv-mh.provo.novell.com> <569FA7F3.8080506@linux.intel.com> <569FCCED02000078000C94BA@prv-mh.provo.novell.com> <569FC112.9060309@linux.intel.com> <56A0A25002000078000C971B@prv-mh.provo.novell.com> <56A095E3.5060507@linux.intel.com> <56A0AA8A02000078000C977D@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <56A0AA8A02000078000C977D@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Haozhong Zhang , Kevin Tian , Wei Liu , Ian Campbell , Stefano Stabellini , Andrew Cooper , Ian Jackson , xen-devel@lists.xen.org, Jun Nakajima , Keir Fraser List-Id: xen-devel@lists.xenproject.org On 01/21/2016 04:53 PM, Jan Beulich wrote: >>>> On 21.01.16 at 09:25, wrote: >> On 01/21/2016 04:18 PM, Jan Beulich wrote: >>> Yes. But then - other than you said above - it still looks to me as >>> if the split between PMEM and PBLK is arranged for by firmware? >> >> Yes. But OS/Hypervisor is not excepted to dynamically change its configure >> (re-split), >> i,e, for PoV of OS/Hypervisor, it is static. > > Exactly, that has been my understanding. And hence the PMEM part > could be under the hypervisor's control, while the PBLK part could be > Dom0's responsibility. > I am not sure if i have understood your point. What your suggestion is that leave PMEM for hypervisor and all other parts (PBLK and _DSM handling) to Dom0? If yes, we should: a) handle hotplug in hypervisor (new PMEM add/remove) that causes hyperivsor interpret ACPI SSDT/DSDT. b) some _DSMs control PMEM so you should filter out these kind of _DSMs and handle them in hypervisor. c) hypervisor should mange PMEM resource pool and partition it to multiple VMs.