qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: imammedo@redhat.com, qemu-devel@nongnu.org, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/4] acpi: move common parts of the SSDT to the DSDT (and preview of things to come)
Date: Wed, 24 Dec 2014 15:43:41 +0100	[thread overview]
Message-ID: <549AD11D.30204@redhat.com> (raw)
In-Reply-To: <20141224141922.GA28410@redhat.com>



On 24/12/2014 15:19, Michael S. Tsirkin wrote:
> So I'll have to review in detail, overall the patches
> do look pretty clean.

Q35 is broken though (GArray resizing messes up the tables, fixed
locally and caught by bios-tables-test even before trying it out!).  I
hope to send out the fixed version on Saturday (time ticking before
vacation).

> Given the amount of pain caused by cross version migration
> issues, I am inclined to do both: arrange code in a way
> that makes keeping things constant easier, and have
> some solutions for the inevitable time when we'll find we
> have to change things we didn't expect.
> Defense in depth, if you like.
> Makes sense?

It certainly does.  I am only a bit wary because your patches are
basically a workaround (as hinted by the fact that the resulting RSDP is
corrupted---which doesn't matter much in practice, but it's still a red
flashing light!).

So I still would like to see how stuff looks like after Igor's code is
merged.  Until we actually trim the size of the ACPI tables (patch 7),
we do no better / no worse than released versions of QEMU.

And once Igor's code is merged, we actually have an idea of what is left
in the SSDT, and how tricky that code is.  "Not tricky at all" is
perhaps a bit optimistic, a more realistic hope is "not any more tricky
than what we do for devices".

In other words, it's only tricky now because it's new.  We had all sorts
of false starts, but the my patches and Igor's provide enough separation
(mine: fixed vs. variable; Igor's: ASL vs. C) that the future should
reserve less surprises.

I will still review your patches, of course.

Paolo

  reply	other threads:[~2014-12-24 14:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24 13:12 [Qemu-devel] [PATCH 0/4] acpi: move common parts of the SSDT to the DSDT (and preview of things to come) Paolo Bonzini
2014-12-24 13:12 ` [Qemu-devel] [PATCH 1/4] pc: append ssdt-misc.dsl to the DSDT Paolo Bonzini
2014-12-24 13:12 ` [Qemu-devel] [PATCH 2/4] pc: rename ssdt-misc to dsdt-common Paolo Bonzini
2014-12-24 13:12 ` [Qemu-devel] [PATCH 3/4] pc: move common parts of the DSDT " Paolo Bonzini
2014-12-24 13:12 ` [Qemu-devel] [PATCH 4/4] pc: merge DSDT common parts into acpi-dsdt-common.dsl Paolo Bonzini
2014-12-24 13:12 ` [Qemu-devel] [PATCH 5/4] pc: introduce new ACPI table sizing algorithm Paolo Bonzini
2014-12-24 13:12 ` [Qemu-devel] [PATCH 6/4] pc: clean up pre-2.1 compatibility code Paolo Bonzini
2014-12-24 13:12 ` [Qemu-devel] [PATCH 7/4] pc: go back to smaller ACPI tables Paolo Bonzini
2014-12-24 13:17 ` [Qemu-devel] [PATCH 0/4] acpi: move common parts of the SSDT to the DSDT (and preview of things to come) Paolo Bonzini
2014-12-24 14:19 ` Michael S. Tsirkin
2014-12-24 14:43   ` Paolo Bonzini [this message]
2014-12-24 16:15     ` Michael S. Tsirkin
2015-01-19 12:22 ` Paolo Bonzini

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=549AD11D.30204@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=mst@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).