From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: ehabkost@redhat.com, kvm@vger.kernel.org, mst@redhat.com,
gleb@kernel.org, Stefan Hajnoczi <stefanha@gmail.com>,
mtosatti@redhat.com, qemu-devel@nongnu.org, pbonzini@redhat.com,
imammedo@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: Wed, 21 Oct 2015 21:32:38 +0800 [thread overview]
Message-ID: <562793F6.5090904@linux.intel.com> (raw)
In-Reply-To: <20151021104937.GD13408@stefanha-thinkpad.redhat.com>
On 10/21/2015 06:49 PM, Stefan Hajnoczi wrote:
> On Wed, Oct 21, 2015 at 12:26:35AM +0800, Xiao Guangrong wrote:
>>
>>
>> On 10/20/2015 11:51 PM, Stefan Hajnoczi wrote:
>>> On Mon, Oct 19, 2015 at 08:54:14AM +0800, Xiao Guangrong wrote:
>>>> +exit:
>>>> + /* Write our output result to dsm memory. */
>>>> + ((dsm_out *)dsm_ram_addr)->len = out->len;
>>>
>>> Missing byteswap?
>>>
>>> I thought you were going to remove this field because it wasn't needed
>>> by the guest.
>>>
>>
>> The @len is the size of _DSM result buffer, for example, for the function of
>> DSM_FUN_IMPLEMENTED the result buffer is 8 bytes, and for
>> DSM_DEV_FUN_NAMESPACE_LABEL_SIZE the buffer size is 4 bytes. It tells ASL code
>> how much size of memory we need to return to the _DSM caller.
>>
>> In _DSM code, it's handled like this:
>>
>> "RLEN" is @len, “OBUF” is the left memory in DSM page.
>>
>> /* get @len*/
>> aml_append(method, aml_store(aml_name("RLEN"), aml_local(6)));
>> /* @len << 3 to get bits. */
>> aml_append(method, aml_store(aml_shiftleft(aml_local(6),
>> aml_int(3)), aml_local(6)));
>>
>> /* get @len << 3 bits from OBUF, and return it to the caller. */
>> aml_append(method, aml_create_field(aml_name("ODAT"), aml_int(0),
>> aml_local(6) , "OBUF"));
>>
>> Since @len is our internally used, it's not return to guest, so i did not do
>> byteswap here.
>
> I am not familiar with the ACPI details, but I think this emits bytecode
> that will be run by the guest's ACPI interpreter?
>
> You still need to define the endianness of fields since QEMU and the
> guest could have different endianness.
>
> In other words, will the following work if a big-endian ppc host is
> running a little-endian x86 guest?
>
> ((dsm_out *)dsm_ram_addr)->len = out->len;
>
Er... If we do byteswap in QEMU then it is also needed in ASL code, however,
ASL lacks this kind of instruction. I guess ACPI interpreter is smart enough
to change value to Littel-Endian for all 2 bytes / 4 bytes / 8 bytes accesses
I will do the change in next version, thanks for you pointing it out, Stefan!
next prev parent reply other threads:[~2015-10-21 13:39 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
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 [this message]
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=562793F6.5090904@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).