[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] xen/x86: Initialize per_cpu(xen_vcpu, 0) a little earlier

To: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>, <david.vrabel@xxxxxxxxxx>, <jgross@xxxxxxxx>
From: David Vrabel <david.vrabel@xxxxxxxxxx>
Date: Wed, 5 Oct 2016 10:44:52 +0100
Cc: linux@xxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxx
Delivery-date: Wed, 05 Oct 2016 09:48:52 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 02/10/16 23:45, Boris Ostrovsky wrote:
> xen_cpuhp_setup() calls mutex_lock() which, when CONFIG_DEBUG_MUTEXES
> is defined, ends up calling xen_save_fl(). That routine expects
> per_cpu(xen_vcpu, 0) to be already initialized.

Applied to for-linus-4.9, thanks.

David

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

References:
- [Xen-devel] [PATCH] xen/x86: Initialize per_cpu(xen_vcpu, 0) a little earlier
  - From: Boris Ostrovsky

Prev by Date: [Xen-devel] [xen-4.6-testing test] 101257: tolerable FAIL - PUSHED
Next by Date: [Xen-devel] [xen-unstable-coverity test] 101279: all pass - PUSHED
Previous by thread: Re: [Xen-devel] [PATCH] xen/x86: Initialize per_cpu(xen_vcpu, 0) a little earlier
Next by thread: [Xen-devel] linux-next: manual merge of the xen-tip tree with the tip tree
Index(es):
- Date
- Thread

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.