qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Cc: ehabkost@redhat.com, kvm@vger.kernel.org, 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 v4 28/33] nvdimm acpi: support DSM_FUN_IMPLEMENTED function
Date: Sun, 18 Oct 2015 21:05:24 +0300	[thread overview]
Message-ID: <20151018205030-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <1445216059-88521-29-git-send-email-guangrong.xiao@linux.intel.com>

On Mon, Oct 19, 2015 at 08:54:14AM +0800, Xiao Guangrong wrote:
> __DSM is defined in ACPI 6.0: 9.14.1 _DSM (Device Specific Method)
> 
> Function 0 is a query function. We do not support any function on root
> device and only 3 functions are support for NVDIMM device,
> DSM_DEV_FUN_NAMESPACE_LABEL_SIZE, DSM_DEV_FUN_GET_NAMESPACE_LABEL_DATA and
> DSM_DEV_FUN_SET_NAMESPACE_LABEL_DATA, that means we currently only allow to
> access device's Label Namespace
> 
> Signed-off-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
> ---
>  hw/acpi/nvdimm.c | 184 ++++++++++++++++++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 182 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/acpi/nvdimm.c b/hw/acpi/nvdimm.c
> index b211b8b..37fea1c 100644
> --- a/hw/acpi/nvdimm.c
> +++ b/hw/acpi/nvdimm.c
> @@ -260,6 +260,22 @@ static uint32_t nvdimm_slot_to_dcr_index(int slot)
>      return nvdimm_slot_to_spa_index(slot) + 1;
>  }
>  
> +static NVDIMMDevice
> +*nvdimm_get_device_by_handle(GSList *list, uint32_t handle)
> +{
> +    for (; list; list = list->next) {
> +        NVDIMMDevice *nvdimm = list->data;
> +        int slot = object_property_get_int(OBJECT(nvdimm), DIMM_SLOT_PROP,
> +                                           NULL);
> +
> +        if (nvdimm_slot_to_handle(slot) == handle) {
> +            return nvdimm;
> +        }
> +    }
> +
> +    return NULL;
> +}
> +
>  /*
>   * Please refer to ACPI 6.0: 5.2.25.1 System Physical Address Range
>   * Structure
> @@ -411,6 +427,60 @@ static void nvdimm_build_nfit(GArray *structures, GArray *table_offsets,
>  /* detailed _DSM design please refer to docs/specs/acpi_nvdimm.txt */
>  #define NOTIFY_VALUE      0x99

Again, please prefix everything consistently.

>  
> +enum {
> +    DSM_FUN_IMPLEMENTED = 0,
> +
> +    /* NVDIMM Root Device Functions */
> +    DSM_ROOT_DEV_FUN_ARS_CAP = 1,
> +    DSM_ROOT_DEV_FUN_ARS_START = 2,
> +    DSM_ROOT_DEV_FUN_ARS_QUERY = 3,
> +
> +    /* NVDIMM Device (non-root) Functions */
> +    DSM_DEV_FUN_SMART = 1,
> +    DSM_DEV_FUN_SMART_THRESHOLD = 2,
> +    DSM_DEV_FUN_BLOCK_NVDIMM_FLAGS = 3,
> +    DSM_DEV_FUN_NAMESPACE_LABEL_SIZE = 4,
> +    DSM_DEV_FUN_GET_NAMESPACE_LABEL_DATA = 5,
> +    DSM_DEV_FUN_SET_NAMESPACE_LABEL_DATA = 6,
> +    DSM_DEV_FUN_VENDOR_EFFECT_LOG_SIZE = 7,
> +    DSM_DEV_FUN_GET_VENDOR_EFFECT_LOG = 8,
> +    DSM_DEV_FUN_VENDOR_SPECIFIC = 9,
> +};

Does FUN stand for "function"? FUNC or FN is probably better.

Please list exact names as they appear in spec so
they can be searched for.



> +
> +enum {
> +    /* Common return status codes. */
> +    DSM_STATUS_SUCCESS = 0,                   /* Success */
> +    DSM_STATUS_NOT_SUPPORTED = 1,             /* Not Supported */
> +
> +    /* NVDIMM Root Device _DSM function return status codes*/
> +    DSM_ROOT_DEV_STATUS_INVALID_PARAS = 2,    /* Invalid Input Parameters */
> +    DSM_ROOT_DEV_STATUS_FUNCTION_SPECIFIC_ERROR = 3, /* Function-Specific
> +                                                        Error */
> +
> +    /* NVDIMM Device (non-root) _DSM function return status codes*/
> +    DSM_DEV_STATUS_NON_EXISTING_MEM_DEV = 2,  /* Non-Existing Memory Device */
> +    DSM_DEV_STATUS_INVALID_PARAS = 3,         /* Invalid Input Parameters */
> +    DSM_DEV_STATUS_VENDOR_SPECIFIC_ERROR = 4, /* Vendor Specific Error */
> +};
> +
> +/* Current revision supported by DSM specification is 1. */
> +#define DSM_REVISION        (1)
> +
> +/*
> + * please refer to ACPI 6.0: 9.14.1 _DSM (Device Specific Method): Return
> + * Value Information:

Drop "please refer to".

> + *   if set to zero, no functions are supported (other than function zero)
> + *   for the specified UUID and Revision ID. If set to one, at least one
> + *   additional function is supported.
> + */
> +
> +/* do not support any function on root. */
> +#define ROOT_SUPPORT_FUN     (0ULL)

Needs a name that implies the comment somehow.

> +#define DIMM_SUPPORT_FUN    ((1 << DSM_FUN_IMPLEMENTED)                   \
> +                           | (1 << DSM_DEV_FUN_NAMESPACE_LABEL_SIZE)      \
> +                           | (1 << DSM_DEV_FUN_GET_NAMESPACE_LABEL_DATA)  \
> +                           | (1 << DSM_DEV_FUN_SET_NAMESPACE_LABEL_DATA))
> +

I think it's best to just drop these macros.
There's a single point of use - just add a comment there
explaining what does it mean.
You will be able to drop all _FUN_ macros too.


>  struct dsm_in {
>      uint32_t handle;
>      uint32_t revision;
> @@ -420,6 +490,11 @@ struct dsm_in {
>  } QEMU_PACKED;
>  typedef struct dsm_in dsm_in;
>  
> +struct cmd_out_implemented {
> +    uint64_t cmd_list;
> +};
> +typedef struct cmd_out_implemented cmd_out_implemented;
> +
>  struct dsm_out {
>      /* the size of buffer filled by QEMU. */
>      uint32_t len;
> @@ -434,12 +509,115 @@ nvdimm_dsm_read(void *opaque, hwaddr addr, unsigned size)
>      return 0;
>  }
>  
> +static void nvdimm_dsm_write_status(GArray *out, uint32_t status)
> +{
> +    /* status locates in the first 4 bytes in the dsm memory. */

located?

> +    assert(!out->len);


But dsm itself can be part of a bigger table.
So don't do it.

> +
> +    status = cpu_to_le32(status);
> +    g_array_append_vals(out, &status, sizeof(status));

I think this should just use the (unfortunately named)
build_append_int_noprefix. Same applied everywhere
where you add single values.

> +}
> +
> +static void nvdimm_dsm_write_root(dsm_in *in, GArray *out)
> +{
> +    uint32_t status = DSM_STATUS_NOT_SUPPORTED;
> +
> +    /* please refer to ACPI 6.0: 9.14.1 _DSM (Device Specific Method) */
> +    if (in->function == DSM_FUN_IMPLEMENTED) {
> +        uint64_t cmd_list = cpu_to_le64(ROOT_SUPPORT_FUN);

see about about single use values.


> +
> +        g_array_append_vals(out, &cmd_list, sizeof(cmd_list));
> +        return;
> +    }
> +
> +    nvdimm_debug("Return status %#x.\n", status);
> +    nvdimm_dsm_write_status(out, status);
> +}
> +
> +static void nvdimm_dsm_write_nvdimm(dsm_in *in, GArray *out)
> +{
> +    GSList *list = nvdimm_get_plugged_device_list();
> +    NVDIMMDevice *nvdimm = nvdimm_get_device_by_handle(list, in->handle);
> +    uint32_t status = DSM_DEV_STATUS_NON_EXISTING_MEM_DEV;
> +    uint64_t cmd_list;
> +
> +    if (!nvdimm) {
> +        goto set_status_free;
> +    }
> +
> +    switch (in->function) {
> +    /* please refer to ACPI 6.0: 9.14.1 _DSM (Device Specific Method) */
> +    case DSM_FUN_IMPLEMENTED:
> +        cmd_list = cpu_to_le64(DIMM_SUPPORT_FUN);
> +        g_array_append_vals(out, &cmd_list, sizeof(cmd_list));
> +        goto free;
> +    default:
> +        status = DSM_STATUS_NOT_SUPPORTED;
> +    };
> +
> +set_status_free:
> +    nvdimm_debug("Return status %#x.\n", status);
> +    nvdimm_dsm_write_status(out, status);
> +free:
> +    g_slist_free(list);
> +}
> +
>  static void
>  nvdimm_dsm_write(void *opaque, hwaddr addr, uint64_t val, unsigned size)
>  {
> +    NVDIMMState *state = opaque;
> +    MemoryRegion *dsm_ram_mr;
> +    dsm_in *in;
> +    GArray *out;
> +    void *dsm_ram_addr;


Why don't you give this the correct type? Will avoid need for casts.

> +
>      if (val != NOTIFY_VALUE) {
>          fprintf(stderr, "BUG: unexepected notify value 0x%" PRIx64, val);
>      }
> +
> +    dsm_ram_mr = memory_region_find(&state->mr, getpagesize(),
> +                                    getpagesize()).mr;
> +    dsm_ram_addr = memory_region_get_ram_ptr(dsm_ram_mr);


This needs a validity check for size.

> +
> +    /*
> +     * copy all input data to our local memory to avoid potential issue
> +     * as the dsm memory is visible to guest.

this comment doesn't help.
pls replace "potential issue" with an explanation.

> +     */
> +    in = g_malloc(memory_region_size(dsm_ram_mr));
> +    memcpy(in, dsm_ram_addr, memory_region_size(dsm_ram_mr));
> +
> +    le32_to_cpus(&in->revision);
> +    le32_to_cpus(&in->function);
> +    le32_to_cpus(&in->handle);
> +
> +    nvdimm_debug("Revision %#x Handler %#x Function %#x.\n", in->revision,
> +                 in->handle, in->function);
> +
> +    out = g_array_new(false, true /* clear */, 1);
> +
> +    if (in->revision != DSM_REVISION) {
> +        nvdimm_debug("Revision %#x is not supported, expect %#x.\n",
> +                      in->revision, DSM_REVISION);
> +        nvdimm_dsm_write_status(out, DSM_STATUS_NOT_SUPPORTED);
> +        goto exit;
> +    }
> +
> +    /* Handle 0 is reserved for NVDIMM Root Device. */
> +    if (!in->handle) {
> +        nvdimm_dsm_write_root(in, out);
> +        goto exit;
> +    }
> +
> +    nvdimm_dsm_write_nvdimm(in, out);
> +
> +exit:
> +    /* Write our output result to dsm memory. */
> +    ((dsm_out *)dsm_ram_addr)->len = out->len;
> +    memcpy(((dsm_out *)dsm_ram_addr)->data, out->data, out->len);

This breaks migration as memory is not dirtied.

address_space_write is generally preferable to change memory.



> +
> +    g_free(in);
> +    g_array_free(out, true);
> +    memory_region_unref(dsm_ram_mr);
>  }
>  
>  static const MemoryRegionOps nvdimm_dsm_ops = {
> @@ -547,7 +725,8 @@ static void build_nvdimm_devices(NVDIMMState *state, GSList *device_list,
>           */
>          BUILD_DSM_METHOD(dev, method,
>                           handle /* NVDIMM Device Handle */,
> -                         3 /* Invalid Input Parameters */,
> +                         DSM_DEV_STATUS_INVALID_PARAS, /* error code if UUID
> +                                                         is not matched. */
>                           "4309AC30-0D11-11E4-9191-0800200C9A66"
>                           /* UUID for NVDIMM Devices. */);
>  
> @@ -669,7 +848,8 @@ static void nvdimm_build_acpi_devices(NVDIMMState *state, GSList *device_list,
>       */
>      BUILD_DSM_METHOD(dev, method,
>                       0 /* 0 is reserved for NVDIMM Root Device*/,
> -                     2 /* Invalid Input Parameters */,
> +                     DSM_ROOT_DEV_STATUS_INVALID_PARAS, /* error code if
> +                                                     UUID is not matched. */
>                       "2F10E7A4-9E91-11E4-89D3-123B93F75CBA"
>                       /* UUID for NVDIMM Root Devices. */);
>  
> -- 
> 1.8.3.1

  reply	other threads:[~2015-10-18 18:05 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19  0:53 [Qemu-devel] [PATCH v4 00/33] implement vNVDIMM Xiao Guangrong
2015-10-19  0:53 ` [Qemu-devel] [PATCH v4 01/33] acpi: add aml_derefof Xiao Guangrong
2015-10-19  0:53 ` [Qemu-devel] [PATCH v4 02/33] acpi: add aml_sizeof Xiao Guangrong
2015-10-19  0:53 ` [Qemu-devel] [PATCH v4 03/33] acpi: add aml_create_field Xiao Guangrong
2015-10-19  0:53 ` [Qemu-devel] [PATCH v4 04/33] acpi: add aml_concatenate Xiao Guangrong
2015-10-19  0:53 ` [Qemu-devel] [PATCH v4 05/33] acpi: add aml_object_type Xiao Guangrong
2015-10-19  0:53 ` [Qemu-devel] [PATCH v4 06/33] acpi: add aml_method_serialized Xiao Guangrong
2015-10-19  0:53 ` [Qemu-devel] [PATCH v4 07/33] util: introduce qemu_file_get_page_size() Xiao Guangrong
2015-10-19  0:53 ` [Qemu-devel] [PATCH v4 08/33] exec: allow memory to be allocated from any kind of path Xiao Guangrong
2015-10-19  0:53 ` [Qemu-devel] [PATCH v4 09/33] exec: allow file_ram_alloc to work on file Xiao Guangrong
2015-10-19  0:53 ` [Qemu-devel] [PATCH v4 10/33] hostmem-file: clean up memory allocation Xiao Guangrong
2015-10-19  0:53 ` [Qemu-devel] [PATCH v4 11/33] hostmem-file: use whole file size if possible Xiao Guangrong
2015-10-19  0:53 ` [Qemu-devel] [PATCH v4 12/33] pc-dimm: remove DEFAULT_PC_DIMMSIZE Xiao Guangrong
2015-10-19  0:53 ` [Qemu-devel] [PATCH v4 13/33] pc-dimm: make pc_existing_dimms_capacity static and rename it Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 14/33] pc-dimm: drop the prefix of pc-dimm Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 15/33] stubs: rename qmp_pc_dimm_device_list.c Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 16/33] pc-dimm: rename pc-dimm.c and pc-dimm.h Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 17/33] dimm: abstract dimm device from pc-dimm Xiao Guangrong
2015-10-24  3:20   ` Bharata B Rao
2015-10-28 14:31     ` Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 18/33] dimm: get mapped memory region from DIMMDeviceClass->get_memory_region Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 19/33] dimm: keep the state of the whole backend memory Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 20/33] dimm: introduce realize callback Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 21/33] nvdimm: implement NVDIMM device abstract Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 22/33] docs: add NVDIMM ACPI documentation Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 23/33] nvdimm acpi: init the address region used by NVDIMM ACPI Xiao Guangrong
2015-10-18 17:15   ` Michael S. Tsirkin
2015-10-19  3:58     ` Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 24/33] nvdimm acpi: build ACPI NFIT table Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 25/33] nvdimm acpi: init the address region used by DSM Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 26/33] nvdimm acpi: build ACPI nvdimm devices Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 27/33] nvdimm acpi: save arg3 for NVDIMM device _DSM method Xiao Guangrong
2015-10-18 17:16   ` Michael S. Tsirkin
2015-10-19  4:04     ` Xiao Guangrong
2015-10-19  6:57       ` Michael S. Tsirkin
2015-10-19  7:09       ` Michael S. Tsirkin
2015-10-19 17:29         ` Dan Williams
2015-10-19 21:19           ` Michael S. Tsirkin
2015-10-19 21:29             ` Dan Williams
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 28/33] nvdimm acpi: support DSM_FUN_IMPLEMENTED function Xiao Guangrong
2015-10-18 18:05   ` Michael S. Tsirkin [this message]
2015-10-19  4:39     ` Xiao Guangrong
2015-10-19  7:06       ` Michael S. Tsirkin
2015-10-19  7:39         ` Xiao Guangrong
2015-10-20 15:51   ` Stefan Hajnoczi
2015-10-20 16:05     ` Michael S. Tsirkin
2015-10-20 16:26     ` Xiao Guangrong
2015-10-20 16:29       ` Xiao Guangrong
2015-10-21 10:49       ` Stefan Hajnoczi
2015-10-21 13:32         ` Xiao Guangrong
2015-10-29 14:36           ` Igor Mammedov
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 29/33] nvdimm acpi: support DSM_DEV_FUN_NAMESPACE_LABEL_SIZE function Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 30/33] nvdimm acpi: support DSM_DEV_FUN_GET_NAMESPACE_LABEL_DATA Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 31/33] nvdimm acpi: support DSM_DEV_FUN_SET_NAMESPACE_LABEL_DATA Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 32/33] nvdimm: allow using whole backend memory as pmem Xiao Guangrong
2015-10-19  0:54 ` [Qemu-devel] [PATCH v4 33/33] nvdimm: add maintain info 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=20151018205030-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=ehabkost@redhat.com \
    --cc=gleb@kernel.org \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=imammedo@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --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).