From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Marcel Apfelbaum <marcel@redhat.com>,
lersek@redhat.com, qemu-devel@nongnu.org, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH V2 0/4] pci: better support for 64-bit MMIO allocation
Date: Wed, 18 May 2016 17:44:57 +0300 [thread overview]
Message-ID: <20160518174310-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20160518163826.3ca6ae86@nial.brq.redhat.com>
On Wed, May 18, 2016 at 04:38:26PM +0200, Igor Mammedov wrote:
> On Wed, 18 May 2016 17:09:20 +0300
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > On Wed, May 18, 2016 at 03:53:08PM +0200, Igor Mammedov wrote:
> > > On Sun, 15 May 2016 22:23:30 +0300
> > > Marcel Apfelbaum <marcel@redhat.com> wrote:
> > >
> > > > Hi,
> > > >
> > > > First two patches allocate (max_reserved_ram - max_addr_cpu_addressable) range for PCI hotplug
> > > > (for PC Machines) instead of the previous 64-bit PCI window that included only
> > > > the ranges allocated by the firmware.
> > > >
> > > > The next two patches fix 64-bit CRS computations.
> > > I'd would add test case + expected tables as the first 2 patches
> > > and then finish series with expected tables update with fixed 64bit range
> >
> > I don't think we necessarily need this noise when running tests.
> > Adding tests last is OK I think, but I prefer updating expected acpi tables
> > myself as these can't be merged.
> the reason I've asked for tables updating is that it makes
> life of reviewers easier, i.e. reviewer can just run
> test and see a ASL diff before fix and after.
>
> Patches with updates could be discarded during merge.
> /mark them with "DONT APPLY"/
I think a new test will currently fail if expected
is not there though. We might want to fix that
to allow the workflow you describe.
> >
> > > as experiment I've hacked existing piix4 case:
> > >
> > > @@ -744,7 +744,9 @@ static void test_acpi_piix4_tcg(void)
> > > */
> > > memset(&data, 0, sizeof(data));
> > > data.machine = MACHINE_PC;
> > > - test_acpi_one("-machine accel=tcg", &data);
> > > + test_acpi_one("-machine accel=tcg"
> > > + " -device pxb,id=bridge1,bus=pci.0,bus_nr=4"
> > > + " -device ivshmem,bus=bridge1,size=4G,shm", &data);
> > > free_test_data(&data);
> > > }
> > >
> > > And it shows not related to this series, but another pxb issue
> > >
> > > + External (_SB_.PCI0.S18_.PCNT, MethodObj) // Warning: Unresolved method, guessing 0 arguments
> > > ...
> > > @@ -1197,8 +1322,8 @@ DefinitionBlock ("tests/acpi-test-data/pc/DSDT.aml", "DSDT", 1, "BOCHS ", "BXPCD
> > >
> > > Device (S18)
> > > {
> > > - Name (_SUN, 0x03) // _SUN: Slot User Number
> > > Name (_ADR, 0x00030000) // _ADR: Address
> > > + Name (_SUN, 0x03) // _SUN: Slot User Number
> > > Method (_EJ0, 1, NotSerialized) // _EJx: Eject Device
> > > {
> > > PCEJ (BSEL, _SUN)
> > > @@ -1638,6 +1763,7 @@ DefinitionBlock ("tests/acpi-test-data/pc/DSDT.aml", "DSDT", 1, "BOCHS ", "BXPCD
> > > BNUM = Zero
> > > DVNT (PCIU, One)
> > > DVNT (PCID, 0x03)
> > > + ^S18.PCNT ()
> > > }
> > > }
> > > }
> > >
> > > so it's better to have test case in place so that changes to pxb
> > > parts wouldn't go unnoticed and would be observable.
> > >
> > >
> > > Also from above experiment I see that pxb duplicates and uses
> > > the same _PRT method as PCI0, probably should be changed to
> > > something like:
> > >
> > > Method(_PRT)
> > > return ^PCI0._PRT()
> > >
> > > > v1 -> v2:
> > > > - resolved some styling issues (Laszlo)
> > > > - rebase on latest master (Laszlo)
> > > >
> > > > Thank you,
> > > > Marcel
> > > >
> > > > Marcel Apfelbaum (4):
> > > > hw/pc: extract reserved memory end computation to a standalone
> > > > function
> > > > pci: reserve 64 bit MMIO range for PCI hotplug
> > > > acpi: refactor pxb crs computation
> > > > hw/apci: handle 64-bit MMIO regions correctly
> > > >
> > > > hw/i386/acpi-build.c | 127 ++++++++++++++++++++++++++++++++++++---------------
> > > > hw/i386/pc.c | 29 ++++++++----
> > > > hw/pci/pci.c | 16 ++++++-
> > > > include/hw/i386/pc.h | 1 +
> > > > 4 files changed, 127 insertions(+), 46 deletions(-)
> > > >
> >
next prev parent reply other threads:[~2016-05-18 14:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-15 19:23 [Qemu-devel] [PATCH V2 0/4] pci: better support for 64-bit MMIO allocation Marcel Apfelbaum
2016-05-15 19:23 ` [Qemu-devel] [PATCH V2 1/4] hw/pc: extract reserved memory end computation to a standalone function Marcel Apfelbaum
2016-05-16 8:13 ` Igor Mammedov
2016-05-15 19:23 ` [Qemu-devel] [PATCH V2 2/4] pci: reserve 64 bit MMIO range for PCI hotplug Marcel Apfelbaum
2016-05-16 8:24 ` Igor Mammedov
2016-05-16 10:14 ` Marcel Apfelbaum
2016-05-16 14:19 ` Igor Mammedov
2016-05-18 14:07 ` Marcel Apfelbaum
2016-05-18 14:26 ` Igor Mammedov
2016-05-18 14:33 ` Marcel Apfelbaum
2016-05-18 13:59 ` Igor Mammedov
2016-05-18 14:10 ` Laszlo Ersek
2016-05-18 14:11 ` Marcel Apfelbaum
2016-05-18 14:11 ` Michael S. Tsirkin
2016-05-18 14:12 ` Marcel Apfelbaum
2016-05-18 14:31 ` Igor Mammedov
2016-05-18 14:33 ` Marcel Apfelbaum
2016-05-18 14:42 ` Michael S. Tsirkin
2016-05-18 14:52 ` Marcel Apfelbaum
2016-05-18 15:06 ` Michael S. Tsirkin
2016-05-18 14:14 ` Michael S. Tsirkin
2016-05-18 14:43 ` Marcel Apfelbaum
2016-05-18 14:57 ` Michael S. Tsirkin
2016-05-18 15:01 ` Marcel Apfelbaum
2016-05-18 15:30 ` Michael S. Tsirkin
2016-05-15 19:23 ` [Qemu-devel] [PATCH V2 3/4] acpi: refactor pxb crs computation Marcel Apfelbaum
2016-05-15 19:23 ` [Qemu-devel] [PATCH V2 4/4] hw/apci: handle 64-bit MMIO regions correctly Marcel Apfelbaum
2016-05-16 11:19 ` Igor Mammedov
2016-05-16 11:30 ` Marcel Apfelbaum
2016-05-18 14:16 ` Michael S. Tsirkin
2016-05-18 14:30 ` Marcel Apfelbaum
2016-05-18 13:53 ` [Qemu-devel] [PATCH V2 0/4] pci: better support for 64-bit MMIO allocation Igor Mammedov
2016-05-18 14:09 ` Michael S. Tsirkin
2016-05-18 14:38 ` Igor Mammedov
2016-05-18 14:44 ` Michael S. Tsirkin [this message]
2016-05-19 7:40 ` Igor Mammedov
2016-05-18 14:22 ` Marcel Apfelbaum
2016-05-19 9:04 ` Igor Mammedov
2016-05-19 20:23 ` Marcel Apfelbaum
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=20160518174310-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.com \
--cc=marcel@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).