linux-kernel - Re: [PATCH 10/21] MSI: Add an arch_msi

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] [day] [month] [year] [list]

Message-ID: <m1mz1wmzkd.fsf@ebiederm.dsl.xmission.com>
Date:	Wed, 28 Mar 2007 22:41:22 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	michael@...erman.id.au
Cc:	linux-pci@...ey.karlin.mff.cuni.cz,
	Greg Kroah-Hartman <greg@...ah.com>,
	"David S. Miller" <davem@...emloft.net>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	linux-kernel@...r.kernel.org, Andrew Morton <akpm@...l.org>,
	daniel.e.wolstenholme@...el.com
Subject: Re: [PATCH 10/21] MSI: Add an arch_msi_supported()

Michael Ellerman <michael@...erman.id.au> writes:

> I agree with most of that. I thought of doing that change, but didn't
> want to have the powerpc code stuck behind a huge pile of driver
> changes.
>
> My only other worry is that at some point we'll get a driver that does
> want to choose the entries it's allocated, and at that point we'll have
> to put back the msix_entry code (or something similar). I don't have any
> idea of when/if that sort of hardware/driver requirement is likely to
> surface though, if it's "not for a while" it might be worth ripping out
> the complexity until we really need it.

Yes.

Allocating everything and just requesting the irqs you really want is
works as well.  So drivers like that would need to be common and the
savings significant before it would really be worthwhile to change
the API back the way it is now.

>> I was tempted to drop nvec as well since our irq numbers are virtual,
>> we could always delay the failure into request_irq.  But there are
>> a few embedded architectures like the arm where the number irqs
>> numbers may stay limited for a long time and if the driver will never
>> use all of the irqs we get to save some resources and some work.  So
>> that makes sense.
>
> I think nvec should stay.

Agreed.

>> So can we please at least move this patch down to the end with the
>> rest of the RTAS arch support?
>> 
>> Moving it towards the end will allow it to be reviewed in the context
>> where it will be used and it will give us a chance to simplify
>> pci_enable_msix before we get there.
>
> I'm happy to move it to the end of the series. I'm also happy to stop
> passing the msix_entry into the arch.
>
> But I don't want to predicate the merge of our powerpc stuff on the
> removal of msix_entry entirely, there's too much risk that we'll slip to
> v23.

Sure.   But if we can kill msix_entry in the same time frame it would
be a good thing.

Eric


-
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/