All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Xen 4.2 Release Plan / TODO
Date: Wed, 20 Jun 2012 14:07:04 +0100	[thread overview]
Message-ID: <4FE1E718020000780008AD65@nat28.tlf.novell.com> (raw)
In-Reply-To: <4FE1B777.4010407@citrix.com>

>>> On 20.06.12 at 13:43, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
> On 20/06/12 12:29, Ian Campbell wrote:
>> hypervisor, blockers:
>>
>>     * None
> 
> Not certain if this is a blocker or nice-to-have, but we have identified
> a regression with Xen's ability to boot, suppectedly due to c/s
> 25336:edd7c7ad1ad2 "x86: adjust handling of interrupts coming in via
> legacy vectors" on AMD hardware with an MP-BIOS bug claiming that the
> PIT is not connected through the IO-APIC.  Fixing this is next on my
> todo list, and I hope to have a solution available by the end of the week.

Sure this (being a regression) is a blocker. Care to share any
details, e.g. a hypervisor logs with "apic_verbosity=debug" without
and with that c/s?

Jan

  reply	other threads:[~2012-06-20 13:07 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 11:29 Xen 4.2 Release Plan / TODO Ian Campbell
2012-06-20 11:43 ` Andrew Cooper
2012-06-20 13:07   ` Jan Beulich [this message]
2012-06-20 13:19     ` Andrew Cooper
2012-06-20 19:29       ` Andrew Cooper
2012-06-26  8:16         ` Ian Campbell
  -- strict thread matches above, loose matches on Subject: below --
2012-07-02 11:02 Ian Campbell
2012-07-03  7:52 ` Jan Beulich
2012-07-03 10:45   ` Anthony PERARD
2012-07-04 16:42 ` Dario Faggioli
2012-07-04 17:08 ` Roger Pau Monne
2012-07-13  9:55   ` Roger Pau Monne
2012-06-26  8:39 Ian Campbell
2012-06-26 20:31 ` Matt Wilson
2012-06-26 21:09   ` Konrad Rzeszutek Wilk
2012-06-26 22:57     ` Matt Wilson
2012-06-27  8:41       ` Ian Campbell
2012-06-28  8:56       ` Ren, Yongjie
2012-06-27 13:12 ` Jan Beulich
2012-06-27 14:52   ` Ian Campbell
2012-06-27 14:57     ` Jan Beulich
2012-06-27 15:01       ` Ian Campbell
2012-06-27 15:36         ` Jan Beulich
2012-06-28 15:18 ` Tim Deegan
2012-04-10 10:24 Ian Campbell
2012-04-12  9:56 ` George Dunlap
2012-04-12 10:24 ` Dario Faggioli
2012-04-12 11:00   ` Ian Campbell
2012-04-02 10:26 Ian Campbell
2012-04-02 10:39 ` David Vrabel
2012-04-02 10:43   ` Ian Campbell
2012-04-02 11:17 ` George Dunlap
2012-04-02 14:41 ` Stefano Stabellini
2012-04-11 16:11 ` Ian Jackson
2012-04-11 16:13   ` Ian Jackson
2012-04-12  7:42     ` Ian Campbell
2012-04-12  7:35   ` Ian Campbell
2012-04-12  7:59     ` Ian Campbell
2012-04-12 16:37       ` Dan Magenheimer
2012-04-12 16:45         ` Ian Campbell
2012-04-13 15:28           ` Dan Magenheimer
2012-04-13 10:45         ` Ian Jackson
2012-04-13 19:45           ` Dan Magenheimer
2012-04-16 10:16             ` Ian Jackson
2012-04-12  8:16     ` Ian Campbell
2012-04-24 17:52       ` Ian Jackson
2012-03-27  9:34 Ian Campbell
2012-03-27 18:30 ` Shriram Rajagopalan
2012-03-19 10:57 Ian Campbell
2012-03-19 11:25 ` Jan Beulich
2012-03-19 11:33   ` Ian Campbell
2012-03-19 12:02     ` Jan Beulich
2012-03-19 12:13   ` Stefano Stabellini
2012-03-19 12:13 ` George Dunlap
2012-03-19 12:28   ` Ian Campbell
2012-03-20  5:19 ` Matt Wilson
2012-03-20  8:42   ` Ian Campbell
2012-03-22  9:21 ` Ian Campbell
2012-03-22  9:22 ` Ian Campbell
2012-03-22 10:22   ` Stefano Stabellini
2012-03-22  9:35 ` George Dunlap
2012-03-22  9:53   ` Ian Campbell
2012-03-22 10:08     ` George Dunlap
2012-03-22 10:19       ` Ian Campbell
2012-03-22 10:31         ` Keir Fraser
2012-03-22 10:34         ` George Dunlap
2012-03-22 10:38           ` Ian Campbell
2012-03-27  9:33             ` Ian Campbell
2012-03-27 10:19               ` George Dunlap

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=4FE1E718020000780008AD65@nat28.tlf.novell.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xen.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.