From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: yang.zhong@intel.com, peter.maydell@linaro.org, thuth@redhat.com,
qemu-devel@nongnu.org, shannon.zhaosl@gmail.com,
qemu-arm@nongnu.org, Wei Yang <richardw.yang@linux.intel.com>,
philmd@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 2/2] acpi: pci: use build_append_foo() API to construct MCFG
Date: Tue, 21 May 2019 10:34:03 -0400 [thread overview]
Message-ID: <20190521103215-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190521162958.4415d4ac@redhat.com>
On Tue, May 21, 2019 at 04:29:58PM +0200, Igor Mammedov wrote:
> On Mon, 20 May 2019 23:37:22 -0400
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > On Tue, May 21, 2019 at 11:32:49AM +0800, Wei Yang wrote:
> > > build_append_foo() API doesn't need explicit endianness conversions
> > > which eliminates a source of errors and it makes build_mcfg() look like
> > > declarative definition of MCFG table in ACPI spec, which makes it easy
> > > to review.
> > >
> > > Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
> > > Suggested-by: Igor Mammedov <imammedo@redhat.com>
> > > Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> > >
> > > ---
> > > v5:
> > > * miss the reserved[8] of MCFG in last version, add it back
> > > * drop SOBs and make sure bios-tables-test all OK
> > > ---
> >
> >
> > Please do not add two --- separators. It breaks git am.
> that worked just fine for the last xx years and still works for me.
Because you don't use git am?
It's true I often am forced to edit your patches to apply them.
Pls do not do this it makes no sense.
> >
> > One --- should come after the commit log. Anything after that and
> > until diff is ignored anyway.
> That's fine if we wish to commit change log into history, but
> Typically we don't want change log to be committed (as it's useless from history pov),
> hence we put it after separator to get it dropped on applying.
Then you should do
build_append_foo() API doesn't need explicit endianness conversions
which eliminates a source of errors and it makes build_mcfg() look like
declarative definition of MCFG table in ACPI spec, which makes it easy
to review.
Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
Suggested-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
---
v5:
* miss the reserved[8] of MCFG in last version, add it back
* drop SOBs and make sure bios-tables-test all OK
hw/acpi/pci.c | 35 +++++++++++++++++++++++------------
include/hw/acpi/acpi-defs.h | 18 ------------------
2 files changed, 23 insertions(+), 30 deletions(-)
diff --git a/hw/acpi/pci.c b/hw/acpi/pci.c
Anything between --- and diff is ignored. Second --- is poointless and
harmful.
> >
> > > hw/acpi/pci.c | 35 +++++++++++++++++++++++------------
> > > include/hw/acpi/acpi-defs.h | 18 ------------------
> > > 2 files changed, 23 insertions(+), 30 deletions(-)
> > >
> > > diff --git a/hw/acpi/pci.c b/hw/acpi/pci.c
> > > index fa0fa30bb9..49df7b7d54 100644
> > > --- a/hw/acpi/pci.c
> > > +++ b/hw/acpi/pci.c
> > > @@ -30,17 +30,28 @@
> > >
> > > void build_mcfg(GArray *table_data, BIOSLinker *linker, AcpiMcfgInfo *info)
> > > {
> > > - AcpiTableMcfg *mcfg;
> > > - int len = sizeof(*mcfg) + sizeof(mcfg->allocation[0]);
> > > -
> > > - mcfg = acpi_data_push(table_data, len);
> > > - mcfg->allocation[0].address = cpu_to_le64(info->base);
> > > -
> > > - /* Only a single allocation so no need to play with segments */
> > > - mcfg->allocation[0].pci_segment = cpu_to_le16(0);
> > > - mcfg->allocation[0].start_bus_number = 0;
> > > - mcfg->allocation[0].end_bus_number = PCIE_MMCFG_BUS(info->size - 1);
> > > -
> > > - build_header(linker, table_data, (void *)mcfg, "MCFG", len, 1, NULL, NULL);
> > > + int mcfg_start = table_data->len;
> > > +
> > > + acpi_data_push(table_data, sizeof(AcpiTableHeader));
> > > +
> > > + /*
> > > + * PCI Firmware Specification, Revision 3.0
> > > + * 4.1.2 MCFG Table Description.
> > > + */
> > > + /* Reserved */
> > > + build_append_int_noprefix(table_data, 0, 8);
> > > + /* Base address, processor-relative */
> > > + build_append_int_noprefix(table_data, info->base, 8);
> > > + /* PCI segment group number */
> > > + build_append_int_noprefix(table_data, 0, 2);
> > > + /* Starting PCI Bus number */
> > > + build_append_int_noprefix(table_data, 0, 1);
> > > + /* Final PCI Bus number */
> > > + build_append_int_noprefix(table_data, PCIE_MMCFG_BUS(info->size - 1), 1);
> > > + /* Reserved */
> > > + build_append_int_noprefix(table_data, 0, 4);
> > > +
> > > + build_header(linker, table_data, (void *)(table_data->data + mcfg_start),
> > > + "MCFG", table_data->len - mcfg_start, 1, NULL, NULL);
> > > }
> > >
> > > diff --git a/include/hw/acpi/acpi-defs.h b/include/hw/acpi/acpi-defs.h
> > > index f9aa4bd398..57a3f58b0c 100644
> > > --- a/include/hw/acpi/acpi-defs.h
> > > +++ b/include/hw/acpi/acpi-defs.h
> > > @@ -449,24 +449,6 @@ struct AcpiSratProcessorGiccAffinity {
> > >
> > > typedef struct AcpiSratProcessorGiccAffinity AcpiSratProcessorGiccAffinity;
> > >
> > > -/* PCI fw r3.0 MCFG table. */
> > > -/* Subtable */
> > > -struct AcpiMcfgAllocation {
> > > - uint64_t address; /* Base address, processor-relative */
> > > - uint16_t pci_segment; /* PCI segment group number */
> > > - uint8_t start_bus_number; /* Starting PCI Bus number */
> > > - uint8_t end_bus_number; /* Final PCI Bus number */
> > > - uint32_t reserved;
> > > -} QEMU_PACKED;
> > > -typedef struct AcpiMcfgAllocation AcpiMcfgAllocation;
> > > -
> > > -struct AcpiTableMcfg {
> > > - ACPI_TABLE_HEADER_DEF;
> > > - uint8_t reserved[8];
> > > - AcpiMcfgAllocation allocation[0];
> > > -} QEMU_PACKED;
> > > -typedef struct AcpiTableMcfg AcpiTableMcfg;
> > > -
> > > /*
> > > * TCPA Description Table
> > > *
> > > --
> > > 2.19.1
next prev parent reply other threads:[~2019-05-21 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 3:32 [Qemu-devel] [PATCH v5 0/2] Extract build_mcfg Part 2 Wei Yang
2019-05-21 3:32 ` [Qemu-devel] [PATCH v5 1/2] hw/acpi: Consolidate build_mcfg to pci.c Wei Yang
2019-05-21 3:37 ` Michael S. Tsirkin
2019-05-21 14:15 ` Igor Mammedov
2019-05-21 3:32 ` [Qemu-devel] [PATCH v5 2/2] acpi: pci: use build_append_foo() API to construct MCFG Wei Yang
2019-05-21 3:37 ` Michael S. Tsirkin
2019-05-21 14:29 ` Igor Mammedov
2019-05-21 14:34 ` Michael S. Tsirkin [this message]
2019-05-22 8:20 ` Igor Mammedov
2019-05-21 3:44 ` Michael S. Tsirkin
2019-05-21 6:20 ` Wei Yang
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=20190521103215-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=imammedo@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richardw.yang@linux.intel.com \
--cc=shannon.zhaosl@gmail.com \
--cc=thuth@redhat.com \
--cc=yang.zhong@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 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).