All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Lu, Yinghai" <yinghai.lu@amd.com>
Cc: "Andi Kleen" <ak@muc.de>,
	"linux kernel mailing list" <linux-kernel@vger.kernel.org>,
	yhlu.kernel@gmail.com
Subject: Re: Fwd: [PATCH] x86_64: typo in __assign_irq_vector when update pos for vector and offset
Date: Tue, 17 Oct 2006 11:55:34 -0600	[thread overview]
Message-ID: <m18xjeaktl.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <5986589C150B2F49A46483AC44C7BCA412D6E7@ssvlexmb2.amd.com> (Yinghai Lu's message of "Mon, 16 Oct 2006 12:52:06 -0700")

"Lu, Yinghai" <yinghai.lu@amd.com> writes:

>>So to get things going making TARGET_CPUS cpu_online_map looks like
>>the right thing to do.
>
> Yes. but need to other reference to TARGET_CPUS to verify...it doesn't
> break sth.

I just looked and tested and we are fine.

>>My question is are your io_apics pci devices?  Not does the kernel
>>have them.
>
> Yes, I'm testing with 32 amd8132 in the simulator. Or forget about about
> ioapic, and use MSI, and HT-irq directly...?

Ok.  So if want a pci device we can have one :)
Usually what I have seen is that all io_apics except the
first one show up as pci devices.

>>There are a lot of ways we can approach assigning irqs to cpus and
> there
>>is a lot of work there.  I think Adrian Bunk has been doing some work
>>with the user space irq balancer, and should probably be involved.
>
> Right. We need only do needed in kernel space, and leave most to irq
> balancer.

Actually I was just being pragmatic.  Make it work now.  Make it optimal
later :)

Eric

  reply	other threads:[~2006-10-17 17:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16 19:52 Fwd: [PATCH] x86_64: typo in __assign_irq_vector when update pos for vector and offset Lu, Yinghai
2006-10-17 17:55 ` Eric W. Biederman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-17 18:05 Lu, Yinghai
2006-10-16 19:02 Lu, Yinghai
2006-10-16 18:27 Lu, Yinghai
2006-10-16 19:03 ` Eric W. Biederman
2006-10-15  7:29 yhlu
2006-10-15 19:21 ` yhlu
2006-10-16 15:26   ` Fwd: " Yinghai Lu
2006-10-16 18:05     ` Eric W. Biederman
2006-10-16 18:35       ` Andi Kleen
2006-10-16 18:54         ` Eric W. Biederman

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=m18xjeaktl.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yhlu.kernel@gmail.com \
    --cc=yinghai.lu@amd.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.