From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: 4.0/4.1 requests
Date: Thu, 08 Sep 2011 11:17:02 +0100 [thread overview]
Message-ID: <CA8E54AE.20876%keir.xen@gmail.com> (raw)
In-Reply-To: <4E68A4AC02000078000553F2@nat28.tlf.novell.com>
On 08/09/2011 10:19, "Jan Beulich" <JBeulich@suse.com> wrote:
> Hi Keir,
>
> without the old IO-APIC part addressed, I wonder whether we should
> really have the backport of 23805:7048810180de ("IRQ: manually EOI
> migrating line interrupts") in both trees.
It does fix a real bug. Perhaps Andrew could hack up a patch to make it
dependent on IO-APIC version?
> I'd also like you to add 23820:ba75234a6f56 ("bitmap_scnlistprintf()
> should always zero-terminate its output buffer") to 4.0 (I see it's
> already in 4.1), as this not being fixed confuses 'e' debug key output.
Ok.
-- Keir
> Jan
>
next prev parent reply other threads:[~2011-09-08 10:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 9:19 4.0/4.1 requests Jan Beulich
2011-09-08 10:12 ` Jan Beulich
2011-09-08 11:29 ` Keir Fraser
2011-09-08 10:17 ` Keir Fraser [this message]
2011-09-08 10:48 ` Andrew Cooper
2011-09-08 11:11 ` Keir Fraser
2011-09-08 11:44 ` Jan Beulich
2011-09-08 13:18 ` 4.0/4.1 requests - IO-APIC EOI [RFC] Andrew Cooper
2011-09-08 13:40 ` Jan Beulich
2011-09-08 13:56 ` Andrew Cooper
2011-09-09 15:06 ` Re: 4.0/4.1 requests - IO-APIC EOI v2 [RFC] Andrew Cooper
2011-09-09 15:39 ` Jan Beulich
2011-09-09 15:55 ` Andrew Cooper
2011-09-09 16:03 ` Jan Beulich
2011-09-09 16:22 ` Re: 4.0/4.1 requests - IO-APIC EOI v3 [RFC] Andrew Cooper
2011-09-09 16:47 ` Re: 4.0/4.1 requests - IO-APIC EOI v4 [RFC] Andrew Cooper
2011-09-09 16:50 ` Andrew Cooper
2011-09-12 6:50 ` Jan Beulich
2011-09-12 10:15 ` Andrew Cooper
2011-09-12 10:23 ` Jan Beulich
2011-09-12 11:30 ` Keir Fraser
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=CA8E54AE.20876%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.