From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754451AbcG0JMA (ORCPT ); Wed, 27 Jul 2016 05:12:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:40194 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753345AbcG0JL5 (ORCPT ); Wed, 27 Jul 2016 05:11:57 -0400 From: Vitaly Kuznetsov To: Stefano Stabellini Cc: David Vrabel , xen-devel@lists.xenproject.org, Juergen Gross , Andrew Cooper , x86@kernel.org, linux-kernel@vger.kernel.org, Julien Grall , Ingo Molnar , Jan Beulich , "H. Peter Anvin" , Boris Ostrovsky , Thomas Gleixner Subject: Re: [Xen-devel] [PATCH linux v3 0/9] xen: pvhvm: support bootup on secondary vCPUs References: <1469536228-29932-1-git-send-email-vkuznets@redhat.com> <57975F83.9090604@citrix.com> <87lh0ov8nh.fsf@vitty.brq.redhat.com> Date: Wed, 27 Jul 2016 11:11:52 +0200 In-Reply-To: (Stefano Stabellini's message of "Tue, 26 Jul 2016 10:36:47 -0700 (PDT)") Message-ID: <87zip3tpgn.fsf@vitty.brq.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.95 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Wed, 27 Jul 2016 09:11:56 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Stefano Stabellini writes: > On Tue, 26 Jul 2016, Vitaly Kuznetsov wrote: >> David Vrabel writes: >> >> > On 26/07/16 13:30, Vitaly Kuznetsov wrote: >> >> It may happen that Xen's and Linux's ideas of vCPU id diverge. In >> >> particular, when we crash on a secondary vCPU we may want to do kdump >> >> and unlike plain kexec where we do migrate_to_reboot_cpu() we try booting >> >> on the vCPU which crashed. This doesn't work very well for PVHVM guests as >> >> we have a number of hypercalls where we pass vCPU id as a parameter. These >> >> hypercalls either fail or do something unexpected. To solve the issue we >> >> need to have a mapping between Linux's and Xen's vCPU ids. >> >> >> >> This series solves the issue for x86 PVHVM guests. PV guests don't (and >> >> probably won't) support kdump so I always assume Xen's vCPU id == Linux's >> >> vCPU id. ARM guests will probably need to get proper mapping once we start >> >> supporting kexec/kdump there. >> >> >> >> Changes since v2: >> >> - Use 'uint32_t' for xen_vcpu_id mapping [Julien Grall] >> >> - Rebased to linux-4.7 >> > >> > I already applied v2. If you provide an incremental patch I can queue >> > it for 4.9. >> >> Ok, >> >> in that case we can wait till the real mapping is done for ARM to change >> the type of xen_vcpu_id I guess. > > It would still be nice to make the change. Please send it as an > incremental patch. It is OK if it is queued for 4.9. Sure, will do. -- Vitaly