From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [xen-unstable test] 33690: regressions - FAIL
Date: Mon, 26 Jan 2015 14:49:47 +0000 [thread overview]
Message-ID: <54C6540B.7080506@citrix.com> (raw)
In-Reply-To: <54C63560020000780005967F@mail.emea.novell.com>
On 26/01/15 11:38, Jan Beulich wrote:
>>>> On 26.01.15 at 12:04, <JBeulich@suse.com> wrote:
>>>>> On 24.01.15 at 13:54, <Ian.Jackson@eu.citrix.com> wrote:
>>> test-amd64-amd64-xl-qemut-win7-amd64 7 windows-install fail REGR. vs. 33637
>> Jan 24 00:35:16.262627 (XEN) ----[ Xen-4.6-unstable x86_64 debug=y Not tainted ]----
>> Jan 24 00:35:16.478599 (XEN) CPU: 1
>> Jan 24 00:35:16.478624 (XEN) RIP: e008:[<0000000000000000>] 0000000000000000
>> Jan 24 00:35:16.486596 (XEN) RFLAGS: 0000000000010082 CONTEXT: hypervisor
>> ...
>> Jan 24 00:35:16.678620 (XEN) Xen call trace:
>> Jan 24 00:35:16.678650 (XEN) [<ffff82d0801d36d0>] vpmu_do_interrupt+0x2f/0x8a
>> Jan 24 00:35:16.686605 (XEN) [<ffff82d08015e242>] pmu_apic_interrupt+0x33/0x35
>> Jan 24 00:35:16.698582 (XEN) [<ffff82d080171bf0>] do_IRQ+0x9c/0x624
>> Jan 24 00:35:16.698615 (XEN) [<ffff82d080234062>] common_interrupt+0x62/0x70
>> Jan 24 00:35:16.698653 (XEN) [<ffff82d08012c6fe>] _spin_unlock_irq+0x30/0x31
>> Jan 24 00:35:16.706604 (XEN) [<ffff82d08012bcf1>] __do_softirq+0x81/0x8c
>> Jan 24 00:35:16.706638 (XEN) [<ffff82d08012bd49>] do_softirq+0x13/0x15
>> Jan 24 00:35:16.718591 (XEN) [<ffff82d0801ec4da>] vmx_asm_do_vmentry+0x2a/0x50
> I think I see what the problem here is: Commit 8097616fbd
> ("x86/VPMU: handle APIC_LVTPC accesses") gives the guest
> control over LVTPC.mask regardless of whether the vPMU was
> actually initialized for it. Supposedly in the case above the
> guest is being run with core2_no_vpmu_ops, which in
> particular has .do_interrupt == NULL. It's not immediately
> clear whether vpmu_lvtpc_update() should do the check or its
> (sole) caller. In any event I'm going to revert that commit as
> the primary suspect for causing the regression.
I have just fallen over this as well. I second a revert in the absence
of a clear way to fix the patch.
~Andrew
next prev parent reply other threads:[~2015-01-26 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 12:54 [xen-unstable test] 33690: regressions - FAIL xen.org
2015-01-26 11:04 ` Jan Beulich
2015-01-26 11:38 ` Jan Beulich
2015-01-26 14:49 ` Andrew Cooper [this message]
2015-01-26 14:51 ` Boris Ostrovsky
2015-01-26 14:56 ` Andrew Cooper
2015-01-26 15:08 ` Boris Ostrovsky
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=54C6540B.7080506@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--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.