From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: ehabkost@redhat.com, kvm@vger.kernel.org, mst@redhat.com,
gleb@kernel.org, mtosatti@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com, imammedo@redhat.com, pbonzini@redhat.com,
dan.j.williams@intel.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH 12/15] nvdimm acpi: support Get Namespace Label Size function
Date: Wed, 23 Mar 2016 11:46:21 +0800 [thread overview]
Message-ID: <56F2118D.9030200@linux.intel.com> (raw)
In-Reply-To: <20160317105845.GD14062@stefanha-x1.localdomain>
On 03/17/2016 06:58 PM, Stefan Hajnoczi wrote:
> On Thu, Mar 17, 2016 at 04:32:58PM +0800, Xiao Guangrong wrote:
>> - /* No function except function 0 is supported yet. */
>> - nvdimm_dsm_no_payload(1 /* Not Supported */, dsm_mem_addr);
>> + if (!nvdimm) {
>> + return nvdimm_dsm_no_payload(1 /* Non-Existing Memory Device */,
>
> "Non-existing Memory Device" is 2 according to the spec. 1 would be
> "Not Supported".
Yes, indeed.
>
> Please define constants for all these magic values instead of putting
> literals into the code:
>
> enum {
> NVDIMM_DSM_SUCCESS = 0,
> NVDIMM_DSM_NOT_SUPPORTED = 1,
> NVDIMM_DSM_NON_EXISTING_MEMORY_DEVICE = 2,
> NVDIMM_DSM_INVALID_INPUT_PARAMETERS = 3,
> NVDIMM_DSM_VENDOR_SPECIFIC_ERROR = 4,
> };
Er, it seems Michael much prefers the style which uses raw number which
is followed by a comment. :(
>
>> + dsm_mem_addr);
>> + }
>> +
>> + /* Encode DSM function according to DSM Spec Rev1. */
>> + switch (in->function) {
>> + case 4 /* Get Namespace Label Size */:
>> + if (nvdimm->reserve_label) {
>> + nvdimm_dsm_label_size(nvdimm, dsm_mem_addr);
>> + }
>> + break;
>
> What is the expected return status code if the device has no labels?
>
> This function must write a return status code, otherwise the guest will
> read the out buffer and attempt to interpret uninitialized memory.
>
Yes, my fault, will fix it. Thanks you for pointing it out.
next prev parent reply other threads:[~2016-03-23 3:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 8:32 [Qemu-devel] [PATCH 00/15] NVDIMM: introduce nvdimm label support Xiao Guangrong
2016-03-17 8:32 ` [Qemu-devel] [PATCH 01/15] pc-dimm: get memory region from ->get_memory_region() Xiao Guangrong
2016-03-17 8:32 ` [Qemu-devel] [PATCH 02/15] pc-dimm: introduce realize callback Xiao Guangrong
2016-03-17 8:32 ` [Qemu-devel] [PATCH 03/15] pc-dimm: keep the state of the whole backend memory Xiao Guangrong
2016-03-17 8:32 ` [Qemu-devel] [PATCH 04/15] nvdimm: support nvdimm label Xiao Guangrong
2016-03-17 10:28 ` Stefan Hajnoczi
2016-03-23 3:40 ` Xiao Guangrong
2016-03-17 8:32 ` [Qemu-devel] [PATCH 05/15] acpi: add aml_object_type Xiao Guangrong
2016-03-17 8:32 ` [Qemu-devel] [PATCH 06/15] acpi: add aml_call5 Xiao Guangrong
2016-03-17 8:32 ` [Qemu-devel] [PATCH 07/15] nvdimm acpi: set HDLE properly Xiao Guangrong
2016-03-17 8:32 ` [Qemu-devel] [PATCH 08/15] nvdimm acpi: save arg3 of _DSM method Xiao Guangrong
2016-03-17 8:32 ` [Qemu-devel] [PATCH 09/15] nvdimm acpi: check UUID Xiao Guangrong
2016-03-17 8:32 ` [Qemu-devel] [PATCH 10/15] nvdimm acpi: abstract the operations for root device and nvdimm devices Xiao Guangrong
2016-03-17 10:35 ` Stefan Hajnoczi
2016-03-23 3:43 ` Xiao Guangrong
2016-03-17 8:32 ` [Qemu-devel] [PATCH 11/15] nvdimm acpi: check revision Xiao Guangrong
2016-03-17 8:32 ` [Qemu-devel] [PATCH 12/15] nvdimm acpi: support Get Namespace Label Size function Xiao Guangrong
2016-03-17 10:58 ` Stefan Hajnoczi
2016-03-23 3:46 ` Xiao Guangrong [this message]
2016-03-17 8:32 ` [Qemu-devel] [PATCH 13/15] nvdimm acpi: support Get Namespace Label Data function Xiao Guangrong
2016-03-17 8:33 ` [Qemu-devel] [PATCH 14/15] nvdimm acpi: support Set " Xiao Guangrong
2016-03-17 8:33 ` [Qemu-devel] [PATCH 15/15] docs: add NVDIMM ACPI documentation Xiao Guangrong
2016-03-17 10:04 ` [Qemu-devel] [PATCH 00/15] NVDIMM: introduce nvdimm label support Stefan Hajnoczi
2016-03-22 15:37 ` Dan Williams
2016-03-22 20:30 ` Stefan Hajnoczi
2016-03-23 2:46 ` Xiao Guangrong
2016-03-23 16:48 ` Stefan Hajnoczi
2016-03-22 11:17 ` Michael S. Tsirkin
2016-03-23 3:47 ` Xiao Guangrong
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=56F2118D.9030200@linux.intel.com \
--to=guangrong.xiao@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=ehabkost@redhat.com \
--cc=gleb@kernel.org \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.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).