All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>, <xen-devel@lists.xenproject.org>
Cc: Juergen Gross <jgross@suse.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>, <x86@kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Julien Grall <julien.grall@arm.com>,
	Ingo Molnar <mingo@redhat.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Jan Beulich <JBeulich@suse.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [Xen-devel] [PATCH linux v3 0/9] xen: pvhvm: support bootup on secondary vCPUs
Date: Tue, 26 Jul 2016 14:02:59 +0100	[thread overview]
Message-ID: <57975F83.9090604@citrix.com> (raw)
In-Reply-To: <1469536228-29932-1-git-send-email-vkuznets@redhat.com>

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.

David

  parent reply	other threads:[~2016-07-26 13:03 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 12:30 [PATCH linux v3 0/9] xen: pvhvm: support bootup on secondary vCPUs Vitaly Kuznetsov
2016-07-26 12:30 ` [PATCH linux v3 1/9] x86/xen: update cpuid.h from Xen-4.7 Vitaly Kuznetsov
2016-07-26 12:30 ` Vitaly Kuznetsov
2016-07-26 12:30 ` [PATCH linux v3 2/9] x86/acpi: store ACPI ids from MADT for future usage Vitaly Kuznetsov
2016-07-26 12:30 ` Vitaly Kuznetsov
2017-03-01 19:54   ` Thomas Gleixner
2017-03-01 19:54     ` Thomas Gleixner
2017-03-01 22:04     ` Boris Ostrovsky
2017-03-01 22:04       ` Boris Ostrovsky
2016-07-26 12:30 ` [PATCH linux v3 3/9] xen: introduce xen_vcpu_id mapping Vitaly Kuznetsov
2016-09-02 15:29   ` Julien Grall
2016-09-02 15:29   ` Julien Grall
2016-09-04 21:12     ` Boris Ostrovsky
2016-09-04 21:12     ` Boris Ostrovsky
2016-09-05  9:42     ` Vitaly Kuznetsov
2016-09-05 19:20       ` Stefano Stabellini
2016-09-05 19:20       ` Stefano Stabellini
2016-09-06  8:31         ` Vitaly Kuznetsov
2016-09-06  8:31         ` Vitaly Kuznetsov
2016-09-06 18:09           ` Stefano Stabellini
2016-09-06 18:09           ` Stefano Stabellini
2016-09-07  9:07             ` Vitaly Kuznetsov
2016-09-07  9:10               ` David Vrabel
2016-09-07  9:10               ` David Vrabel
2016-09-07  9:35               ` Julien Grall
2016-09-07  9:35               ` Julien Grall
2016-09-07 11:23                 ` Vitaly Kuznetsov
2016-09-07 11:23                 ` Vitaly Kuznetsov
2016-09-07 12:55                   ` Julien Grall
2016-09-07 12:55                   ` Julien Grall
2016-09-07  9:07             ` Vitaly Kuznetsov
2016-09-08  6:29       ` Wei Chen
2016-09-08  6:29       ` Wei Chen
2016-09-05  9:42     ` Vitaly Kuznetsov
2016-07-26 12:30 ` Vitaly Kuznetsov
2016-07-26 12:30 ` [PATCH linux v3 4/9] x86/xen: use xen_vcpu_id mapping for HYPERVISOR_vcpu_op Vitaly Kuznetsov
2016-07-26 12:30   ` Vitaly Kuznetsov
2016-07-26 12:30 ` [PATCH linux v3 5/9] x86/xen: use xen_vcpu_id mapping when pointing vcpu_info to the shared_info page Vitaly Kuznetsov
2016-07-26 12:30 ` Vitaly Kuznetsov
2016-07-26 12:30 ` [PATCH linux v3 6/9] xen/events: use xen_vcpu_id mapping in events_base Vitaly Kuznetsov
2016-07-26 12:30 ` Vitaly Kuznetsov
2016-07-26 12:30 ` [PATCH linux v3 7/9] xen/events: fifo: use xen_vcpu_id mapping Vitaly Kuznetsov
2016-07-26 12:30 ` Vitaly Kuznetsov
2016-07-26 12:30 ` [PATCH linux v3 8/9] xen/evtchn: " Vitaly Kuznetsov
2016-07-26 12:30 ` Vitaly Kuznetsov
2016-07-26 12:30 ` [PATCH linux v3 9/9] xen/pvhvm: run xen_vcpu_setup() for the boot CPU Vitaly Kuznetsov
2016-07-26 12:30 ` Vitaly Kuznetsov
2016-07-26 13:02 ` [PATCH linux v3 0/9] xen: pvhvm: support bootup on secondary vCPUs David Vrabel
2016-07-26 13:02 ` David Vrabel [this message]
2016-07-26 13:19   ` [Xen-devel] " Vitaly Kuznetsov
2016-07-26 17:36     ` Stefano Stabellini
2016-07-27  9:11       ` Vitaly Kuznetsov
2016-07-27  9:11       ` [Xen-devel] " Vitaly Kuznetsov
2016-07-26 17:36     ` Stefano Stabellini
2016-07-26 13:19   ` Vitaly Kuznetsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57975F83.9090604@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=julien.grall@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=sstabellini@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.