From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] x86: change IO-APIC ack method defaultforsingle IO-APIC systems
Date: Wed, 21 Jan 2009 16:44:45 +0000 [thread overview]
Message-ID: <49775F0D.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C59CFEA3.21AD8%keir.fraser@eu.citrix.com>
>>> Keir Fraser <keir.fraser@eu.citrix.com> 21.01.09 17:32 >>>
>Well, it seems not great to avoid the new ack_type for some unknown bug. And
>noone else has run with your patch and zero other issues with the new
Many people have - all users of SLE10 (from GA over SP1 to SP2), SuSE
10.2, 10.3, 11.0, 11.1, and all betas and RCs so far available for SLE11.
>ack_type have been reported. So this seems to be papering over a rather rare
>and potentially nasty underlying issue. On the other hand, perhaps old
>ack_type is preferable (faster) if we can be sure we're on a system where it
>is safe. Hmmm.
Jan
next prev parent reply other threads:[~2009-01-21 16:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 14:21 [PATCH] x86: change IO-APIC ack method default for single IO-APIC systems Jan Beulich
2009-01-21 14:23 ` Jiang, Yunhong
2009-01-21 14:33 ` [PATCH] x86: change IO-APIC ack method default forsingle " Jan Beulich
2009-01-21 14:35 ` Jiang, Yunhong
2009-01-21 14:37 ` [PATCH] x86: change IO-APIC ack method default for single " Keir Fraser
2009-01-21 14:44 ` [PATCH] x86: change IO-APIC ack method default forsingle " Jan Beulich
2009-01-21 14:35 ` [PATCH] x86: change IO-APIC ack method default for single " Keir Fraser
2009-01-21 14:41 ` Jiang, Yunhong
2009-01-21 14:51 ` [PATCH] x86: change IO-APIC ack method default forsingle " Jan Beulich
2009-01-21 16:32 ` Keir Fraser
2009-01-21 16:44 ` Jan Beulich [this message]
2009-01-22 3:09 ` Tian, Kevin
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=49775F0D.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=keir.fraser@eu.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.