All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] pc: drop external DSDT loading
Date: Mon, 12 Aug 2013 23:18:14 +0300	[thread overview]
Message-ID: <20130812201814.GA2713@redhat.com> (raw)
In-Reply-To: <878v06brz6.fsf@codemonkey.ws>

On Mon, Aug 12, 2013 at 02:59:24PM -0500, Anthony Liguori wrote:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
> 
> > On Mon, Aug 12, 2013 at 10:20:41AM -0500, Anthony Liguori wrote:
> >> "Michael S. Tsirkin" <mst@redhat.com> writes:
> >> 
> >> > On Mon, Aug 12, 2013 at 09:01:44AM -0500, Anthony Liguori wrote:
> >> >> This breaks migration and is unneeded with modern SeaBIOS.
> >> >> 
> >> >> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
> >> >
> >> > Hmm don't we want to keep it around for machine types
> >> > 1.4.0 and 1.5.0?
> >> 
> >> Hrm, why?
> >
> > Well this modifies the contents of ROM which
> > is loaded from FW CFG and isn't migrated, correct?
> > If guest is migrated from 1.6 to 1.5
> > while it is loading the ROM,
> > it will likely get a corrupted table.
> 
> No, if you migrate from 1.6 to 1.5 the ROM is untouched.  ROMs aren't
> migrated so it doesn't really matter.

Clarifying this on IRC, what was meant here is that
-acpi is uncommon so bios typically checks and sees nothing
in the ACPI FW CFG entry, and this check is atomic.
So this works, by luck.

> 
> If you migrate from 1.5 while reading the ROM contents, then badness can
> ensue but that's already the case without this patch.
> 
> Regards,
> 
> Anthony Liguori

Well there's a difference between can and will :)
But yes, some future version will likely break it anyway.


Reviewed-by: Michael S. Tsirkin <mst@redhat.com>

> >
> >
> >> Regards,
> >> 
> >> Anthony Liguori
> >> 
> >> >
> >> > By the way, copy stable as well?
> >> > Loading it unconditonally is a cross
> >> > version migration bug that we probably want to fix
> >> > on stable branch - disabling for 1.3.0 and older.
> >> >
> >> >> ---
> >> >> v1 -> v2
> >> >>  - Still load external DSDT for q35
> >> >> ---
> >> >>  hw/i386/pc_piix.c | 1 -
> >> >>  1 file changed, 1 deletion(-)
> >> >> 
> >> >> diff --git a/hw/i386/pc_piix.c b/hw/i386/pc_piix.c
> >> >> index 95c45b8..311574a 100644
> >> >> --- a/hw/i386/pc_piix.c
> >> >> +++ b/hw/i386/pc_piix.c
> >> >> @@ -103,7 +103,6 @@ static void pc_init1(MemoryRegion *system_memory,
> >> >>                                OBJECT(icc_bridge), NULL);
> >> >>  
> >> >>      pc_cpus_init(cpu_model, icc_bridge);
> >> >> -    pc_acpi_init("acpi-dsdt.aml");
> >> >>  
> >> >>      if (kvm_enabled() && kvmclock_enabled) {
> >> >>          kvmclock_create();
> >> >> -- 
> >> >> 1.8.0

  reply	other threads:[~2013-08-12 20:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12 14:01 [Qemu-devel] [PATCH v2] pc: drop external DSDT loading Anthony Liguori
2013-08-12 14:08 ` Andreas Färber
2013-08-12 14:54 ` Michael S. Tsirkin
2013-08-12 15:20   ` Anthony Liguori
2013-08-12 18:09     ` Michael S. Tsirkin
2013-08-12 19:59       ` Anthony Liguori
2013-08-12 20:18         ` Michael S. Tsirkin [this message]
2013-08-14 16:27 ` Anthony Liguori

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=20130812201814.GA2713@redhat.com \
    --to=mst@redhat.com \
    --cc=aliguori@us.ibm.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 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.