From: Olaf Hering <olaf@aepfle.de>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: xen-devel@lists.xenproject.org, Juergen Gross <jgross@suse.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] xen: avoid crash in disable_hotplug_cpu
Date: Mon, 10 Sep 2018 17:58:25 +0200 [thread overview]
Message-ID: <20180910175825.683476d9.olaf@aepfle.de> (raw)
In-Reply-To: <4f623671-e1aa-1804-449c-a26b0c4b9ce9@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
Am Fri, 7 Sep 2018 12:56:37 -0400
schrieb Boris Ostrovsky <boris.ostrovsky@oracle.com>:
> I was hoping you'd respond to my question about warning.
>
> root@haswell> xl vcpu-set 3 0
> and in the guest
>
> [root@vm-0238 ~]# [ 32.866955] ------------[ cut here ]------------
> [ 32.866963] spinlock on CPU0 exists on IRQ1!
> [ 32.866984] WARNING: CPU: 0 PID: 14 at arch/x86/xen/spinlock.c:90
> xen_init_lock_cpu+0xbf/0xd0
This happens to work for me, on X5550. Please send your .config.
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2018-09-10 15:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 14:31 [PATCH v4] xen: avoid crash in disable_hotplug_cpu Olaf Hering
2018-09-07 14:34 ` Juergen Gross
2018-09-07 14:34 ` Juergen Gross
2018-09-07 16:56 ` Boris Ostrovsky
2018-09-07 16:56 ` Boris Ostrovsky
2018-09-10 15:58 ` Olaf Hering [this message]
2018-09-10 17:55 ` Boris Ostrovsky
2018-09-10 17:55 ` Boris Ostrovsky
2018-09-10 15:58 ` Olaf Hering
2018-09-11 7:52 ` Olaf Hering
2018-09-11 7:52 ` Olaf Hering
2018-09-11 7:55 ` Juergen Gross
2018-09-11 7:55 ` Juergen Gross
2018-09-11 10:48 ` Olaf Hering
2018-09-11 10:51 ` Juergen Gross
2018-09-11 10:51 ` Juergen Gross
2018-09-11 10:48 ` Olaf Hering
2018-09-11 19:39 ` Boris Ostrovsky
2018-09-11 19:39 ` Boris Ostrovsky
-- strict thread matches above, loose matches on Subject: below --
2018-09-07 14:31 Olaf Hering
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=20180910175825.683476d9.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.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.