From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Schmauss, Erik" <erik.schmauss@intel.com>
Cc: "imammedo@redhat.com" <imammedo@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"He, Junyan" <junyan.he@intel.com>,
"Moore, Robert" <robert.moore@intel.com>
Subject: Re: [Qemu-devel] RFC: altering the NVDIMM acpi table
Date: Tue, 24 Apr 2018 02:05:09 +0300 [thread overview]
Message-ID: <20180424020443-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20180423234259-mutt-send-email-mst@kernel.org>
On Mon, Apr 23, 2018 at 11:57:04PM +0300, Michael S. Tsirkin wrote:
> On Mon, Apr 23, 2018 at 08:35:45PM +0000, Schmauss, Erik wrote:
> > Hello,
> >
> > I work on ACPICA and we have recently made changes to the behavior of
> > the Linux AML interpreter to match other OS implementations. After
> > sending the patches to upstream Linux, we have identified that
> > hw/acpi/nvdimm.c specifies an ACPI table with a forward reference
> > (MEMA is a forward reference that is no longer supported as of Linux
> > 4.17-rc1).
>
> Interesting. What is the result if such a table is encountered?
> Will this break on old hypervisors that already
> shipped with this set of tables?
>
> > We would like to change this file to move the declaration of Name
> > (MEMA,...) to appear as the very first declaration in the SSDT. Below is a patch outlining the change that I would like to make.
>
> I think this will work just fine, but I would like to see a
> comment explaining what the issue is.
> Names aren't actually resolved until method actually runs, right?
> For example, a name could be defined by a dynamically loaded
> definition block ...
>
> > However, I am having a hard time getting make check to run
> > to completion in a reasonable amount of time. It always seems to fail
> > on some sort of checksum test...
>
> Are you running this on Linux? On bare metal or within a VM?
> Most people here test it on Linux with KVM.
In addition, isn't https://github.com/acpica/acpica/commit/0c08790c
trying to fix exactly this configuration?
> > It would be great if you could let me
> > know what you think of the change and what I can do to speed up the
> > execution time of make check...
>
> You could limit to just qtest tests.
>
> make check-qtest
>
> >
> > Thanks,
> >
> > Erik Schmauss
> >
> > diff --git a/hw/acpi/nvdimm.c b/hw/acpi/nvdimm.c
> > index 59d6e4254c..7c9efd9ac7 100644
> > --- a/hw/acpi/nvdimm.c
> > +++ b/hw/acpi/nvdimm.c
> > @@ -1234,6 +1234,9 @@ static void nvdimm_build_ssdt(GArray *table_offsets, GArray *table_data,
> > ssdt = init_aml_allocator();
> > acpi_data_push(ssdt->buf, sizeof(AcpiTableHeader));
> >
> > + mem_addr_offset = build_append_named_dword(table_data,
> > + NVDIMM_ACPI_MEM_ADDR);
> > +
> > sb_scope = aml_scope("\\_SB");
> >
> > dev = aml_device("NVDR");
> > @@ -1266,9 +1269,6 @@ static void nvdimm_build_ssdt(GArray *table_offsets, GArray *table_data,
> >
> > /* copy AML table into ACPI tables blob and patch header there */
> > g_array_append_vals(table_data, ssdt->buf->data, ssdt->buf->len);
> > - mem_addr_offset = build_append_named_dword(table_data,
> > - NVDIMM_ACPI_MEM_ADDR);
> > -
> > bios_linker_loader_alloc(linker,
> > NVDIMM_DSM_MEM_FILE, dsm_dma_arrea,
> > sizeof(NvdimmDsmIn), false /* high memory */);
>
>
> --
> MST
next prev parent reply other threads:[~2018-04-23 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 20:35 [Qemu-devel] RFC: altering the NVDIMM acpi table Schmauss, Erik
2018-04-23 20:57 ` Michael S. Tsirkin
2018-04-23 23:05 ` Michael S. Tsirkin [this message]
2018-04-24 0:28 ` Schmauss, Erik
2018-04-23 21:00 ` Dan Williams
2018-04-23 21:11 ` Michael S. Tsirkin
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=20180424020443-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=erik.schmauss@intel.com \
--cc=imammedo@redhat.com \
--cc=junyan.he@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=robert.moore@intel.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 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.