WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Adding another GPE section to an HVM, causes the origin

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Adding another GPE section to an HVM, causes the original GPE to stop functioning
From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
Date: Sun, 18 Oct 2009 20:35:50 +0200
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 18 Oct 2009 11:36:16 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ZXaxonJ787zpjoQQzF+yC/1c00qblv8sLMhZ4sTT7H0=; b=u29dbu2SDYWOvSInEC+h+w/WrBKo81qz+AFQN0Np9WJAxJeTW+PkMQB9b5x5Jzc8fK MxEPutEvyl7B9p0kAk5UEeZY0HCTBf5LVOMw7XENkXDFr/WTzOn3H9CsGZg3nCAlqGCf EIhlvxWZ3eEVGb57uk8T3yOOvxDS4dC7BZins=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=qNk14XTAyR8ai9MsMiNFGm4kpcmysU99hrEplqxYy+KmGqBlBICy8VEdUvMXCYNreX h2x1VYGzqKNmR+c5jthQ4qV9i/yklJLgB8lX73akVXZs85s2aNf0whH4lwjk3E39wETK BrGri2pslmGMTyrZ/1t4MsIPN4k4vHX6vqano=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C70101EB.17DC5%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <8686c3cd0910180613la4898a0q6a4526d8d6469754@xxxxxxxxxxxxxx> <C70101EB.17DC5%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Keir,

You are right! I just set gpe1_base, and it's working like a charm!

Thanks a lot!

Tom

On Sun, Oct 18, 2009 at 6:33 PM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> On 18/10/2009 14:13, "Tom Rotenberg" <tom.rotenberg@xxxxxxxxx> 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
>
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>