qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Reza Jelveh <fishman@saucelabs.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] acpi: add reset register to fadt
Date: Mon, 30 Mar 2015 15:49:36 +0200	[thread overview]
Message-ID: <20150330154936.2503d224@nial.brq.redhat.com> (raw)
In-Reply-To: <CAOVGsrM_weMN+bVihnCEkb=7exJhCBo-r9n1=iadu2RO8ByzsQ@mail.gmail.com>

On Mon, 30 Mar 2015 15:27:26 +0200
Reza Jelveh <fishman@saucelabs.com> wrote:

> On Mon, Mar 30, 2015 at 2:36 PM, Igor Mammedov <imammedo@redhat.com> wrote:
> 
> > you are extending structure beyond of what specified by ACPI 1.0b spec,
> > that might break guests.
> > We probably can't change revision since Windows ACPI implementation
> > is mostly 1.0b based so we are stuck with it.
> > Patch needs to be tested with Windows guests starting with XP.
> >
> 
> Works fine with XP as long as you don't use q35, but i guess that's
> unsupported by xp by default.
what about other windows versions?

> 
> 
> > related issue,
> > adding fields without changing major version to a corresponding
> > one doesn't look correct.
> >
> 
> What do you suggest? saying we support 2.0a just because of introducing
> reset_reg is not really valid is it?
Try to check whether windows works fine with a newer revision,
if it is, we can create revX FADT structure and use in with new machine types.
In that case we could consider implementing rev5 table so it could be reused
in ARM target.

  reply	other threads:[~2015-03-30 13:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-28 14:46 [Qemu-devel] [RFC] acpi: add reset register to fadt Reza Jelveh
2015-03-29 17:38 ` Marcel Apfelbaum
2015-03-30 13:56   ` Paolo Bonzini
2015-03-30 12:36 ` Igor Mammedov
2015-03-30 13:27   ` Reza Jelveh
2015-03-30 13:49     ` Igor Mammedov [this message]
2015-03-30 13:59     ` 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=20150330154936.2503d224@nial.brq.redhat.com \
    --to=imammedo@redhat.com \
    --cc=fishman@saucelabs.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).