From: Andrew Morton <akpm@osdl.org>
To: Ashok Raj <ashok.raj@intel.com>
Cc: ashok.raj@intel.com, linux-kernel@vger.kernel.org,
tony.luck@intel.com, linux-ia64@vger.kernel.org,
davidm@hpl.hp.com, hch@lst.de
Subject: Re: Fix irq_affinity write from /proc for IPF
Date: Tue, 15 Mar 2005 01:08:26 +0000 [thread overview]
Message-ID: <20050314170826.26c1a7f4.akpm@osdl.org> (raw)
In-Reply-To: <20050314162330.A22861@unix-os.sc.intel.com>
Ashok Raj <ashok.raj@intel.com> wrote:
>
> > Is it not possible for ia64's ->set_affinity() handler to do this deferring?
> >
>
> There are other places where we re-program, and its fine to call the
> current version of set_affinity directly, like when we are doing cpu offline
> and trying to force migrate irqs for ia64.
>
> Changing the default set_affinity() for ia64 would result in many changes,
> this still keeps the same purpose of those access functions, and
> differentiates the proc write cases alone without changing the meaning
> of those handler functions. (and a smaller patch)
>
> this would further complicate the force migrate irq's when we consider
> MSI interrupts as well. Since it would have its own set_affinity, and we need
> to hack into MSI's set affinity handler as well which would complicate things.
OK, just checking.
I'll include this change in the next batch, probably post-2.6.12-rc1, thanks.
prev parent reply other threads:[~2005-03-15 1:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 23:50 Fix irq_affinity write from /proc for IPF Ashok Raj
2005-03-14 23:59 ` Andrew Morton
2005-03-15 0:23 ` Ashok Raj
2005-03-15 1:08 ` Andrew Morton [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=20050314170826.26c1a7f4.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=davidm@hpl.hp.com \
--cc=hch@lst.de \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox