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] [PATCH] HVM vcpu hotplug: Fix acpi method NTFY bug

To: "Liu, Jinsong" <jinsong.liu@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] HVM vcpu hotplug: Fix acpi method NTFY bug
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Mon, 01 Feb 2010 08:33:17 +0000
Cc: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, "Zheng, Shaohui" <shaohui.zheng@xxxxxxxxx>, "Ke, Liping" <liping.ke@xxxxxxxxx>
Delivery-date: Mon, 01 Feb 2010 00:33:43 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <EB8593BCECAB3D40A8248BE0B6400A3835ACAE12@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqfEjBdAvKTlDZES9GP92/daWtXOgBn3NcBAABXF2AAAn8xkQBvuV2QAAb4ydAAFXdH4AAK5Ei0
Thread-topic: [Xen-devel] [PATCH] HVM vcpu hotplug: Fix acpi method NTFY bug
User-agent: Microsoft-Entourage/12.23.0.091001
On 01/02/2010 03:31, "Liu, Jinsong" <jinsong.liu@xxxxxxxxx> wrote:

> How about the followed update:
> 1. keep original method NTFY, keep decision_tree to reduce scan loop;
> 2. update method PRSC
>     1). transfer para 'maxvcpus' (comes from config file) from qemu to
> mk_dsdt.c through bios_info;
>     2). at PRSC, only scan 'maxvcpus' vcpus;
> because maxvcpus< 128, no risk for NTFY then.

Well, I'm confused now. #2 is really no more than an optimisation, right?
And #1 contradicts your original patch, which only affected NTFY, and you
claimed was a bug fix.

Is there, or is there not, currently a bug in NTFY? Or some bug in the way
it is called by PRSC?

I mean, if there's no bug, let's leave it alone. At least until 4.0.0 is
done. I still haven't been able to understand your original complaints about
the current NTFY method by the way -- I still firmly believe it is
behaviourally identical to your patched version, for any given pair of
arguments passed to it.

I could be missing something. If so you're going to have spell it out very
slowly and clearly. :-)

 -- Keir



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