From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org, anthony@codemonkey.ws, kraxel@redhat.com
Subject: Re: [Qemu-devel] [RFC 0/9] generate dynamic _CRS for motherboard resources
Date: Mon, 17 Feb 2014 13:02:18 +0200 [thread overview]
Message-ID: <20140217110218.GB21925@redhat.com> (raw)
In-Reply-To: <20140217113323.71d18eda@thinkpad>
On Mon, Feb 17, 2014 at 11:33:23AM +0100, Igor Mammedov wrote:
> On Sun, 16 Feb 2014 17:53:45 +0200
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > On Fri, Feb 07, 2014 at 01:51:27PM +0100, Igor Mammedov wrote:
> > > Since introduction of PCIHP, it became problematic to
> > > punch hole in PCI0._CRS statically since PCI hotplug
> > > region size became runtime changeable.
> >
> > What makes it runtime changeable?
> piix machine "acpi-pci-hotplug-with-bridge-support=on" effectively
> changes size of pcihp MMIO region
It adds 4 bytes. Let's just reserve a reasonably sized region,
like 512 bytes.
> >
> > > So replace static hole punching with dynamically consumed
> > > resources in a child device on PCI0 bus. i.e generate
> > > PNP0C02 device as a child of PCI0 bus at runtime and
> > > consume GPE0, PCI/CPU hotplug IO resources in it instead
> > > of punching holes in static PCI0._CRS.
> >
> > It seems that we are being too exact with
> > IO resources here.
> > Can't we roughly reserve 0xae00 to 0xafff
> > and be done with it?
> that would be easiest way for this specific case if we could agree
> for ranges on PIIX/Q35 machines.
>
> But I also use it as excuse to introduce ASL like macros so that
> building dynamic SSDT would be easier i.e. replace template patching
> with single place where dynamic device is defined and its values
> are set in simple and straightforward manner.
We don't need excuses really :)
But the approach itself needs some work IMHO, in particular
ASL like syntax by using macros and varargs is not something to strive
for IMHO :)
Why don't we just pass GArrays around?
crs = build_alloc_crs();
build_append_resource(crs, ....)
Or if you really want this, using array of GArray:
build_append_crs(ssdt,
{
build_alloc_resource(...),
build_alloc_resource(...),
build_alloc_resource(...),
build_alloc_resource(...),
NULL
})
> > > Tested with Windows XPsp3, Vista, Windows Server 2003, 2008, 2012r2.
> > >
> > > PS:
> > > Series adds several ASL like macros to simplify
> > > code for dynamic generation of AML structures.
> > >
> > > Igor Mammedov (9):
> > > Revert "pc: Q35 DSDT: exclude CPU hotplug IO range from PCI bus
> > > resources"
> > > Revert "pc: PIIX DSDT: exclude CPU/PCI hotplug & GPE0 IO range from
> > > PCI bus resources"
> > > Partial revert "pc: ACPI: expose PRST IO range via _CRS"
> > > acpi: replace opencoded opcodes with defines
> > > acpi: add PNP0C02 to PCI0 bus
> > > acpi: consume GPE0 IO resources in PNP0C02 device
> > > acpi: consume CPU hotplug IO resource in PNP0C02 device
> > > pcihp: expose PCI hotplug MMIO base/length as properties of piix4pm
> > > acpi: consume PCIHP IO resource in PNP0C02 device
> > >
> > > hw/acpi/pcihp.c | 28 ++++++
> > > hw/acpi/piix4.c | 1 +
> > > hw/i386/acpi-build.c | 177 ++++++++++++++++++++++++++++++++++--
> > > hw/i386/acpi-dsdt-cpu-hotplug.dsl | 11 ---
> > > hw/i386/acpi-dsdt-pci-crs.dsl | 15 +++-
> > > hw/i386/acpi-dsdt.dsl | 39 --------
> > > hw/i386/q35-acpi-dsdt.dsl | 16 ----
> > > include/hw/acpi/pcihp.h | 4 +
> > > 8 files changed, 214 insertions(+), 77 deletions(-)
>
>
> --
> Regards,
> Igor
next prev parent reply other threads:[~2014-02-17 10:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 12:51 [Qemu-devel] [RFC 0/9] generate dynamic _CRS for motherboard resources Igor Mammedov
2014-02-07 12:51 ` [Qemu-devel] [RFC 1/9] Revert "pc: Q35 DSDT: exclude CPU hotplug IO range from PCI bus resources" Igor Mammedov
2014-02-07 12:51 ` [Qemu-devel] [RFC 2/9] Revert "pc: PIIX DSDT: exclude CPU/PCI hotplug & GPE0 " Igor Mammedov
2014-02-07 12:51 ` [Qemu-devel] [RFC 3/9] Partial revert "pc: ACPI: expose PRST IO range via _CRS" Igor Mammedov
2014-02-07 12:51 ` [Qemu-devel] [RFC 4/9] acpi: replace opencoded opcodes with defines Igor Mammedov
2014-02-16 12:02 ` Michael S. Tsirkin
2014-02-07 12:51 ` [Qemu-devel] [RFC 5/9] acpi: add PNP0C02 to PCI0 bus Igor Mammedov
2014-02-16 12:06 ` Michael S. Tsirkin
2014-02-07 12:51 ` [Qemu-devel] [RFC 6/9] acpi: consume GPE0 IO resources in PNP0C02 device Igor Mammedov
2014-02-16 15:20 ` Michael S. Tsirkin
2014-02-07 12:51 ` [Qemu-devel] [RFC 7/9] acpi: consume CPU hotplug IO resource " Igor Mammedov
2014-02-16 15:39 ` Michael S. Tsirkin
2014-02-07 12:51 ` [Qemu-devel] [RFC 8/9] pcihp: expose PCI hotplug MMIO base/length as properties of piix4pm Igor Mammedov
2014-02-16 15:45 ` Michael S. Tsirkin
2014-02-07 12:51 ` [Qemu-devel] [RFC 9/9] acpi: consume PCIHP IO resource in PNP0C02 device Igor Mammedov
2014-02-16 15:53 ` [Qemu-devel] [RFC 0/9] generate dynamic _CRS for motherboard resources Michael S. Tsirkin
2014-02-17 8:32 ` Gerd Hoffmann
2014-02-17 10:28 ` Michael S. Tsirkin
2014-02-17 10:46 ` Gerd Hoffmann
2014-02-17 11:05 ` Michael S. Tsirkin
2014-02-18 16:36 ` Igor Mammedov
2014-02-18 22:04 ` Laszlo Ersek
2014-02-19 8:59 ` Igor Mammedov
2014-02-17 10:33 ` Igor Mammedov
2014-02-17 11:02 ` Michael S. Tsirkin [this message]
2014-02-18 11:10 ` Igor Mammedov
2014-02-18 11:33 ` Michael S. Tsirkin
2014-02-18 16:30 ` Igor Mammedov
2014-02-17 8:29 ` Gerd Hoffmann
2014-02-18 16:48 ` Igor Mammedov
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=20140217110218.GB21925@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).