From: William Lee Irwin III <wli@holomorphy.com>
To: long <tlnguyen@snoqualmie.dp.intel.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, tom.l.nguyen@intel.com
Subject: Re: [PATCH]Re:2.6.7-rc3-mm1
Date: Thu, 10 Jun 2004 18:05:58 -0700 [thread overview]
Message-ID: <20040611010558.GC1444@holomorphy.com> (raw)
In-Reply-To: <200406102045.i5AKjDJo017156@snoqualmie.dp.intel.com>
On Wed. June 09, 2004 William Lee Irwin III wrote:
>> The MSI writers have a lot to answer for. Could you test this?
On Thu, Jun 10, 2004 at 01:45:13PM -0700, long wrote:
> The MSI patch has existed in the kernel since 2.6.3 and has been
> validated in both UP and SMP environments. It appears another patch
> (don't know which one) redefined the value of TARGET_CPU, which is
> used by the function msi_address_init() to configure logical
> target CPU. The redefinition of TARGET_CPU without checking its
> usage by other kernel code broke the build.
> Your patch fixes the build but breaks the devices using MSI in
> different architectures supported by the function msi_address_init().
> I have attached a patch that fixes the build and maintains cross
> architecture support for MSI.
I didn't know it was a logical APIC ID that was supposed to go in there.
Well, that ought to fix bugs with MSI and clustered hierarchical DFR too.
-- wli
prev parent reply other threads:[~2004-06-11 1:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 20:45 [PATCH]Re:2.6.7-rc3-mm1 long
2004-06-10 19:57 ` 2.6.7-rc3-mm1 problems (ACPI and others) Grzegorz Kulewski
2004-06-10 20:47 ` Mikael Pettersson
2004-06-10 23:10 ` Pozsar Balazs
2004-06-11 1:05 ` William Lee Irwin III [this message]
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=20040611010558.GC1444@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tlnguyen@snoqualmie.dp.intel.com \
--cc=tom.l.nguyen@intel.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.