lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 9 Sep 2008 15:54:16 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Jeremy Fitzhardinge" <jeremy@...p.org>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	"Ingo Molnar" <mingo@...e.hu>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: TARGET_CPUS in assign_irq_vector

On Tue, Sep 9, 2008 at 3:30 PM, Jeremy Fitzhardinge <jeremy@...p.org> wrote:
> On x86-64, the genapic implementations of target_cpus returns
> cpu_online_map.  What if more cpus have yet to come online?  Shouldn't
> it be cpu_possible_map?
>
> Though I'm probably confused.  I don't really know what the intent of
> target_cpus and vector_allocation_domain is.
>
logical mode, vector_allocation_domain will return all online cpus aka
the 8 cpus.

phys_flat mode, vector_allotcation_domain will only the cpumask with
the cpu set..

target_cpus is the cpus that could be possible to used to take vector
and process that irq. so at least it should be online.

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ