On 12/16/2015 09:32 AM, Robert Hu wrote:
On Fri, 2015-12-11 at 12:01 +, Ian Campbell wrote:
On Fri, 2015-12-11 at 11:48 +0800, Robert Hu wrote:
On Fri, 2015-12-11 at 01:16 +, osstest service owner wrote:
flight 65633 linux-3.14 real [real]
http://logs.test-lab.xenproject.org/osstest/
On 12/29/2015 07:28 PM, Haozhong Zhang wrote:
This patch series extends current vNVDIMM implementation to provide
vNVDIMM to HVM domains when QEMU is used as the device model of Xen.
This patch series is based on upstream qemu rather of qemu-xen,
because vNVDIMM support has not been in qemu-xe
Hi,
On 01/20/2016 06:15 PM, Haozhong Zhang wrote:
CCing QEMU vNVDIMM maintainer: Xiao Guangrong
Conceptually, an NVDIMM is just like a fast SSD which is linearly mapped
into memory. I am still on the dom0 side of this fence.
The real question is whether it is possible to take an NVDIMM
On 01/20/2016 07:20 PM, Jan Beulich wrote:
On 20.01.16 at 12:04, wrote:
On 01/20/16 01:46, Jan Beulich wrote:
On 20.01.16 at 06:31, wrote:
Secondly, the driver implements a convenient block device interface to
let software access areas where NVDIMM devices are mapped. The
existing vNVDIMM
On 01/20/2016 11:47 PM, Konrad Rzeszutek Wilk wrote:
On Wed, Jan 20, 2016 at 11:29:55PM +0800, Xiao Guangrong wrote:
On 01/20/2016 07:20 PM, Jan Beulich wrote:
On 20.01.16 at 12:04, wrote:
On 01/20/16 01:46, Jan Beulich wrote:
On 20.01.16 at 06:31, wrote:
Secondly, the driver
On 01/21/2016 12:47 AM, Konrad Rzeszutek Wilk wrote:
On Thu, Jan 21, 2016 at 12:25:08AM +0800, Xiao Guangrong wrote:
On 01/20/2016 11:47 PM, Konrad Rzeszutek Wilk wrote:
On Wed, Jan 20, 2016 at 11:29:55PM +0800, Xiao Guangrong wrote:
On 01/20/2016 07:20 PM, Jan Beulich wrote:
On
On 01/21/2016 01:07 AM, Jan Beulich wrote:
On 20.01.16 at 16:29, wrote:
On 01/20/2016 07:20 PM, Jan Beulich wrote:
To answer this I need to have my understanding of the partitioning
being done by firmware confirmed: If that's the case, then "normal"
means the part that doesn't get exposed as
On 01/21/2016 01:18 AM, Konrad Rzeszutek Wilk wrote:
c) hotplug support
How does that work? Ah the _DSM will point to the new ACPI NFIT for the OS
to scan. That would require the hypervisor also reading this for it to
update it's data-structures.
Similar as you said. The NVDIMM root device
On 01/21/2016 04:18 PM, Jan Beulich wrote:
On 20.01.16 at 18:17, wrote:
On 01/21/2016 01:07 AM, Jan Beulich wrote:
On 20.01.16 at 16:29, wrote:
On 01/20/2016 07:20 PM, Jan Beulich wrote:
To answer this I need to have my understanding of the partitioning
being done by firmware confirmed
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 d
10 matches
Mail list logo
