From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Manuel Bouyer <bouyer@antioche.eu.org>
Cc: xen-devel <xen-devel@lists.xenproject.org>, julien.grall@linaro.org
Subject: Re: 4.11.0 RC1 panic
Date: Wed, 25 Apr 2018 09:16:59 +0100 [thread overview]
Message-ID: <92c47b1a-3502-d2e4-8cde-1d23604177d9@citrix.com> (raw)
In-Reply-To: <5AE0272702000078001BE3B3@prv1-mh.provo.novell.com>
On 25/04/2018 07:58, Jan Beulich wrote:
>>>> On 24.04.18 at 18:06, <bouyer@antioche.eu.org> wrote:
>> Hello,
>> I tested xen 4.11.0 rc1 with NetBSD as dom0.
>> I could boot a NetBSD PV domU without problem, but at shutdown time
>> (poweroff
>> in the domU), I got a Xen panic:
>> (XEN) Assertion 'cpu < nr_cpu_ids' failed at
>> ...1/work/xen-4.11.0-rc1/xen/include/xen/cpumask.h:97
>>
>> A xl destroy instead of poweroff gives the same result.
>>
>> This happens with both 32bitsPAE and 64bits domU. This doens't seem to
>> happen with HVM domUs.
>>
>> Attached are a cut-n-paste of the panic, and the output of xl demsg.
> Without line numbers associated with at least the top stack trace entry
> I can only guess what it might be - could you give the patch below a try?
> (This may not be the final patch, as I'm afraid there may be some race
> here, but I'd have to work this out later.)
>
> Jan
>
> --- unstable.orig/xen/arch/x86/mm.c
> +++ unstable/xen/arch/x86/mm.c
> @@ -1255,7 +1255,7 @@ void put_page_from_l1e(l1_pgentry_t l1e,
> {
> for_each_vcpu ( pg_owner, v )
> {
> - if ( pv_destroy_ldt(v) )
> + if ( pv_destroy_ldt(v) && v->dirty_cpu != VCPU_CPU_CLEAN )
> flush_tlb_mask(cpumask_of(v->dirty_cpu));
> }
> }
>
Manuel: As a tangentially related question, does NetBSD ever try to page
out its LDT?
I'm fairly sure this particular bit of code exists solely for the
Windows XP port to PV guests. The code itself is broken as far as the
"feature" goes (as it only works on present => not present PTE changes,
and not for other PTE permissions changes which would also drop the
segdesc typeref), and dropping it would remove one vcpu scalability
limitation for PV guests.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-04-25 8:17 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 16:06 4.11.0 RC1 panic Manuel Bouyer
2018-04-25 6:58 ` Jan Beulich
2018-04-25 8:16 ` Andrew Cooper [this message]
2018-04-25 10:58 ` Manuel Bouyer
2018-04-25 10:42 ` Manuel Bouyer
2018-04-25 14:42 ` Manuel Bouyer
2018-04-25 15:28 ` Jan Beulich
2018-04-25 15:57 ` Manuel Bouyer
2018-04-30 13:31 ` Jan Beulich
2018-05-01 20:22 ` Manuel Bouyer
2018-05-15 9:30 ` Jan Beulich
2018-05-22 11:01 ` Manuel Bouyer
2018-05-22 14:46 ` Jan Beulich
2018-06-10 9:54 ` Jan Beulich
2018-06-10 10:57 ` Manuel Bouyer
2018-06-10 15:38 ` Jan Beulich
2018-06-10 16:32 ` Manuel Bouyer
[not found] ` <5B1D528F020000C104A2FF49@prv1-mh.provo.novell.com>
2018-06-11 9:58 ` Jan Beulich
2018-06-11 10:13 ` Manuel Bouyer
2018-06-12 7:57 ` Jan Beulich
2018-06-12 11:39 ` Manuel Bouyer
2018-06-12 15:38 ` Manuel Bouyer
2018-06-12 15:54 ` Andrew Cooper
2018-06-12 16:00 ` Manuel Bouyer
2018-06-12 16:29 ` Andrew Cooper
2018-06-12 20:55 ` Manuel Bouyer
[not found] ` <5B1FB0E5020000F903B0F0C2@prv1-mh.provo.novell.com>
[not found] ` <5B1FE90D020000F804A5F2B5@prv1-mh.provo.novell.com>
[not found] ` <5B20335B0200008603B30F33@prv1-mh.provo.novell.com>
2018-06-13 6:23 ` Jan Beulich
2018-06-13 8:07 ` Jan Beulich
2018-06-13 8:57 ` Manuel Bouyer
[not found] ` <5B20DC910200000204A693B0@prv1-mh.provo.novell.com>
2018-06-13 9:59 ` Jan Beulich
2018-06-13 10:07 ` Manuel Bouyer
2018-06-13 22:16 ` Manuel Bouyer
[not found] ` <5B2197D3020000F004A75E9B@prv1-mh.provo.novell.com>
2018-06-14 14:33 ` Jan Beulich
2018-06-15 15:01 ` Manuel Bouyer
2018-06-25 8:33 ` Manuel Bouyer
[not found] ` <5B30A8DD0200007003BD270D@prv1-mh.provo.novell.com>
2018-06-26 15:11 ` Jan Beulich
2018-07-03 15:14 ` Jan Beulich
2018-07-03 16:17 ` Manuel Bouyer
2018-07-06 14:26 ` Manuel Bouyer
2018-07-16 10:30 ` Manuel Bouyer
[not found] ` <5B1FECBE0200005C04A5F773@prv1-mh.provo.novell.com>
[not found] ` <5B1FEE270200008403B2CB9D@prv1-mh.provo.novell.com>
[not found] ` <5B1FF4E60200007D03B2D421@prv1-mh.provo.novell.com>
2018-06-13 6:54 ` Jan Beulich
[not found] ` <5B3BA1A6020000F004B7A140@prv1-mh.provo.novell.com>
[not found] ` <5B3F7C2F020000D004BA0458@prv1-mh.provo.novell.com>
[not found] ` <5B4C73C30200007F03CE8FF3@prv1-mh.provo.novell.com>
2018-07-16 11:02 ` Jan Beulich
2018-07-24 15:03 ` Manuel Bouyer
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=92c47b1a-3502-d2e4-8cde-1d23604177d9@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=bouyer@antioche.eu.org \
--cc=julien.grall@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).