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

[Xen-devel] Re: [PATCH] pvops: Avoid re-alloc_intr_gate of hvm evtchn ca

To: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] pvops: Avoid re-alloc_intr_gate of hvm evtchn callback
From: Frank Pan <frankpzh@xxxxxxxxx>
Date: Sat, 5 Mar 2011 19:45:50 +0800
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jeremy Fitzhardinge <Jeremy.Fitzhardinge@xxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Sat, 05 Mar 2011 03:46:46 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=pg3idPwY6fdIE9p78OmY3FAQydsetrqbBym4Oo85F4A=; b=V6qISrg/jGIAmUAkHP8OyRRyjlt6kst1sfGnF/e3Vti4gMJ+R/FQ4GpF8KlgcVgLGn VFRtdHhmzL0ylBhyCJ7lfWvlQKUUkJWJjiCX0+5YD2fFv71PlBDg2QuHqjPTKqH1MpcB 7C3FQLjgyKcNVg9iqgBvO2NIjpWWoF3AGtFhE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=OXcFozkmeU7bbSlNlTb+Wi3LOdZfOpR8SYskz50DYwYCEPbaD3fIwDPH4Kpy+SUCpl TW7j3NFzzkxrypGCFraLssz171aFzPVtcMOeDJyDw7E7JBxAcwkm7IQFdrZbbfgsIR2z x79Vh8pcTI7Tl9lZijUVbPuUrDJwxCg9Ronng=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1299322472.13328.67.camel@xxxxxxxxxxxxxxxxxxxxx>
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: <AANLkTinL2nYgcA3eL46JriZnNBog-qQEAaA_qQS6wfxk@xxxxxxxxxxxxxx> <1299322472.13328.67.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> Thanks. I presume this is against xen/next-2.6.32? Please always mention
> which branch a patch is for.

FP: Yes, I'll mention it if I have more bugfixes.

> The upstream kernel already has this check, and it came from the
> original commit 38e20b07efd5 "x86/xen: event channels delivery on HVM"
> so it looks like the version in the 2.6.32 branch (b24870f7dd7a) was an
> older revision of that patch which lacked this check.
>
> Perhaps you might find it useful to do a sweep through
>        git://xenbits.xen.org/people/ianc/linux-2.6.git 
> debian/squeeze/pvhvm-2.6.32.24
> comparing it to the xen/next-2.6.32 branch?

FP: I just want a usable version of pvops for doing some research on
migration. Can you suggest a branch which is not too old and a sort of
stable?

> Also your patches need to include a Signed-off-by line in accordance
> with Documentation/SubmittingPatches.

FP: Gmail sucks on line wrapping, so I also attach the patch inside.
Is that ok? If so, where should I put the "Signed-off-by" line? both?

-- 
潘震皓, Frank Pan

Computer Science and Technology
Tsinghua University

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