All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Tom Rotenberg <tom.rotenberg@gmail.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Adding another GPE section to an HVM, causes the original GPE to stop functioning
Date: Sun, 18 Oct 2009 17:33:31 +0100	[thread overview]
Message-ID: <C70101EB.17DC5%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <8686c3cd0910180613la4898a0q6a4526d8d6469754@mail.gmail.com>

On 18/10/2009 14:13, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:

> Since i have inserted this new GPE block, the outcome is, that my new
> GPE block is responding OK, however, the old GPE block (the regular
> Xen gpe0 block), isn't responding anymore - thus i can't
> hot-plugqhot-unplug PT devices.
> 
> I have analyzed the qemu logs a little bit, and it looks like, since
> the addition of the new GPE block, Windows for some reason, only
> enables the new gpe block (gpe1 block), and disables the old gpe block
> (regular Xen gpe0 block).
> 
> Can someone please assist me with this issue?

Since you do not set Fadt.gpe1_base, gpe1's events are precisely overlapping
with gpe0's. This is actually a bug, and Windows is interpreting the broken
tables as best it can, by assuming that GPE1 overrides GPE0. Probably you
mean to set Fadt.gpe1_base=(ACPI_GPE0_LEN/2)*8 or something like that.

 -- Keir

  reply	other threads:[~2009-10-18 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 13:13 Adding another GPE section to an HVM, causes the original GPE to stop functioning Tom Rotenberg
2009-10-18 16:33 ` Keir Fraser [this message]
2009-10-18 18:35   ` Tom Rotenberg

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=C70101EB.17DC5%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=tom.rotenberg@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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.