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/
Home Products Support Community News


RE: [Xen-devel] [PATCH] Fix hvm vcpu hotplug bug

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] Fix hvm vcpu hotplug bug
From: "Liu, Jinsong" <jinsong.liu@xxxxxxxxx>
Date: Thu, 19 Aug 2010 10:20:22 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Li, Xin" <xin.li@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Wed, 18 Aug 2010 19:21:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19563.58860.249044.209893@xxxxxxxxxxxxxxxxxxxxxxxx>
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: <BC00F5384FCFC9499AF06F92E8B78A9E0B0007FD20@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <19554.43920.11785.97567@xxxxxxxxxxxxxxxxxxxxxxxx> <BC00F5384FCFC9499AF06F92E8B78A9E164C8CB703@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <19563.58860.249044.209893@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acs+3NEOpfgSVEo8SCKoXE7Hp8fbywAY/qEA
Thread-topic: [Xen-devel] [PATCH] Fix hvm vcpu hotplug bug
Ian Jackson wrote:
> Liu, Jinsong writes ("RE: [Xen-devel] [PATCH] Fix hvm vcpu hotplug
> bug"): 
>> I think qemu-xen should add this logic level, so that it can support
>> more gpe events in the future.
> Yes.  But what clears the interrupt ?  Is it edge or level triggered ?

SCI is a shareable level interrupt.
Per my understanding, sci-gpe logic is like

                                                  |------- gpe_sts x
                                        |         |------- gpe_en x
sci int                               |
------------------------------------ OR    ......
(wired to i8259[9] etc)         |
                                        |         |------- gpe_sts y
                                                  |------- gpe_en y

Currently qemu-xen didn't have 'gep event x OR gpe event y --> sci' logic, it 
should add this logic level.

To clear the interrupt:
1). gpe_sts x & gpe_en x --> low gpe event x
2). all gpe events low --> low sci
(low is of logic meaning here, not real electric value)


Xen-devel mailing list