From: Haozhong Zhang <haozhong.zhang@intel.com> To: qemu-devel@nongnu.org, xen-devel@lists.xensource.com Cc: Xiao Guangrong <guangrong.xiao@linux.intel.com>, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, Haozhong Zhang <haozhong.zhang@intel.com>, "Michael S. Tsirkin" <mst@redhat.com>, Igor Mammedov <imammedo@redhat.com> Subject: [Qemu-devel] [RFC QEMU PATCH 3/8] nvdimm acpi: do not use fw_cfg on Xen Date: Mon, 10 Oct 2016 08:34:18 +0800 [thread overview] Message-ID: <20161010003423.4333-4-haozhong.zhang@intel.com> (raw) In-Reply-To: <20161010003423.4333-1-haozhong.zhang@intel.com> No fw_cfg is created when QEMU is used as the device model of Xen. Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com> --- Cc: Xiao Guangrong <guangrong.xiao@linux.intel.com> Cc: "Michael S. Tsirkin" <mst@redhat.com> Cc: Igor Mammedov <imammedo@redhat.com> --- hw/acpi/nvdimm.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/hw/acpi/nvdimm.c b/hw/acpi/nvdimm.c index e486128..c9c2a84 100644 --- a/hw/acpi/nvdimm.c +++ b/hw/acpi/nvdimm.c @@ -770,8 +770,11 @@ void nvdimm_init_acpi_state(AcpiNVDIMMState *state, MemoryRegion *io, state->dsm_mem = g_array_new(false, true /* clear */, 1); acpi_data_push(state->dsm_mem, sizeof(NvdimmDsmIn)); - fw_cfg_add_file(fw_cfg, NVDIMM_DSM_MEM_FILE, state->dsm_mem->data, - state->dsm_mem->len); + /* No fw_cfg is used when running on Xen */ + if (fw_cfg) { + fw_cfg_add_file(fw_cfg, NVDIMM_DSM_MEM_FILE, state->dsm_mem->data, + state->dsm_mem->len); + } } #define NVDIMM_COMMON_DSM "NCAL" -- 2.10.1
WARNING: multiple messages have this Message-ID (diff)
From: Haozhong Zhang <haozhong.zhang@intel.com> To: qemu-devel@nongnu.org, xen-devel@lists.xensource.com Cc: Haozhong Zhang <haozhong.zhang@intel.com>, Igor Mammedov <imammedo@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>, Xiao Guangrong <guangrong.xiao@linux.intel.com> Subject: [RFC QEMU PATCH 3/8] nvdimm acpi: do not use fw_cfg on Xen Date: Mon, 10 Oct 2016 08:34:18 +0800 [thread overview] Message-ID: <20161010003423.4333-4-haozhong.zhang@intel.com> (raw) In-Reply-To: <20161010003423.4333-1-haozhong.zhang@intel.com> No fw_cfg is created when QEMU is used as the device model of Xen. Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com> --- Cc: Xiao Guangrong <guangrong.xiao@linux.intel.com> Cc: "Michael S. Tsirkin" <mst@redhat.com> Cc: Igor Mammedov <imammedo@redhat.com> --- hw/acpi/nvdimm.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/hw/acpi/nvdimm.c b/hw/acpi/nvdimm.c index e486128..c9c2a84 100644 --- a/hw/acpi/nvdimm.c +++ b/hw/acpi/nvdimm.c @@ -770,8 +770,11 @@ void nvdimm_init_acpi_state(AcpiNVDIMMState *state, MemoryRegion *io, state->dsm_mem = g_array_new(false, true /* clear */, 1); acpi_data_push(state->dsm_mem, sizeof(NvdimmDsmIn)); - fw_cfg_add_file(fw_cfg, NVDIMM_DSM_MEM_FILE, state->dsm_mem->data, - state->dsm_mem->len); + /* No fw_cfg is used when running on Xen */ + if (fw_cfg) { + fw_cfg_add_file(fw_cfg, NVDIMM_DSM_MEM_FILE, state->dsm_mem->data, + state->dsm_mem->len); + } } #define NVDIMM_COMMON_DSM "NCAL" -- 2.10.1 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-10-10 0:35 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-10-10 0:34 [Qemu-devel] [RFC QEMU PATCH 0/8] Implement vNVDIMM for Xen HVM guest Haozhong Zhang 2016-10-10 0:34 ` Haozhong Zhang 2016-10-10 0:34 ` [Qemu-devel] [RFC QEMU PATCH 1/8] nvdimm: do not initialize label_data if label_size is zero Haozhong Zhang 2016-10-10 0:34 ` Haozhong Zhang 2017-02-15 22:18 ` [Qemu-devel] " Konrad Rzeszutek Wilk 2017-02-15 22:18 ` Konrad Rzeszutek Wilk 2016-10-10 0:34 ` [Qemu-devel] [RFC QEMU PATCH 2/8] xen-hvm: add a function to copy ACPI to guest Haozhong Zhang 2016-10-10 0:34 ` Haozhong Zhang 2016-10-10 0:34 ` Haozhong Zhang [this message] 2016-10-10 0:34 ` [RFC QEMU PATCH 3/8] nvdimm acpi: do not use fw_cfg on Xen Haozhong Zhang 2016-10-10 0:34 ` [Qemu-devel] [RFC QEMU PATCH 4/8] nvdimm acpi: build and copy NFIT to guest " Haozhong Zhang 2016-10-10 0:34 ` Haozhong Zhang 2016-10-10 0:34 ` [Qemu-devel] [RFC QEMU PATCH 5/8] nvdimm acpi: build and copy NVDIMM namespace devices " Haozhong Zhang 2016-10-10 0:34 ` Haozhong Zhang 2016-10-10 0:34 ` [Qemu-devel] [RFC QEMU PATCH 6/8] hostmem: add a host memory backend for Xen Haozhong Zhang 2016-10-10 0:34 ` Haozhong Zhang 2016-10-10 0:34 ` [Qemu-devel] [RFC QEMU PATCH 7/8] xen-hvm: create hotplug memory region for HVM guest Haozhong Zhang 2016-10-10 0:34 ` Haozhong Zhang 2016-10-10 0:34 ` [Qemu-devel] [RFC QEMU PATCH 8/8] qmp: add a qmp command 'query-nvdimms' to get plugged NVDIMM devices Haozhong Zhang 2016-10-10 0:34 ` Haozhong Zhang 2016-10-10 19:16 ` [Qemu-devel] " Eric Blake 2016-10-10 19:16 ` Eric Blake 2016-10-11 6:31 ` [Qemu-devel] " Haozhong Zhang 2016-10-11 6:31 ` Haozhong Zhang 2016-10-11 8:22 ` [Qemu-devel] " Markus Armbruster 2016-10-11 8:22 ` Markus Armbruster 2016-10-11 10:12 ` [Qemu-devel] " Haozhong Zhang 2016-10-11 10:12 ` Haozhong Zhang 2016-10-11 14:45 ` [Qemu-devel] " Eric Blake 2016-10-11 14:45 ` Eric Blake 2016-10-10 16:52 ` [Qemu-devel] [RFC QEMU PATCH 0/8] Implement vNVDIMM for Xen HVM guest no-reply 2016-10-10 16:52 ` no-reply
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=20161010003423.4333-4-haozhong.zhang@intel.com \ --to=haozhong.zhang@intel.com \ --cc=guangrong.xiao@linux.intel.com \ --cc=imammedo@redhat.com \ --cc=konrad.wilk@oracle.com \ --cc=mst@redhat.com \ --cc=qemu-devel@nongnu.org \ --cc=xen-devel@lists.xensource.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.