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: Fri, 20 Aug 2010 11:29:05 +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: Thu, 19 Aug 2010 20:31:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19565.17092.616097.195948@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> <BC00F5384FCFC9499AF06F92E8B78A9E165097298D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <19565.17092.616097.195948@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acs/rL4CR/88krhnTMCln2X6T7lXKQAaUqsQ
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"): 
>> Per my understanding, sci-gpe logic is like
>> [diagram]
>> Currently qemu-xen didn't have 'gep event x OR gpe event y --> sci'
>> logic, it should add this logic level.
> Yes, thanks, I'd understood that.  But:
>> To clear the interrupt:
>> 1). gpe_sts x & gpe_en x --> low gpe event x
> I think you mean "gpe_sts goes low" ?  Since your diagram is in terms
> of levels and I guess "sts" is the actual interrupt source, and
> "sts_en" is the interrupt enable flag.


> So in real hardware, what makes gpe_sts go low ?
> Ian.

ospm will do. Its sequence is (i.e. linux 2.6.32, ospm dispatch control method 
1). clear pge_en x by writing '0' to the bit;
2). asynchronic call control method;
3). clear gpe_sts x by writing '1' to the bit;
4). re-enable gpe_en x by writing '1' to the bit;

Xen-devel mailing list