[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090309181118.GV25995@parisc-linux.org>
Date: Mon, 9 Mar 2009 12:11:19 -0600
From: Matthew Wilcox <matthew@....cx>
To: Randy Dunlap <randy.dunlap@...cle.com>
Cc: Yu Zhao <yu.zhao@...el.com>,
"jbarnes@...tuousgeek.org" <jbarnes@...tuousgeek.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v10 3/7] PCI: reserve bus range for SR-IOV device
On Mon, Mar 09, 2009 at 11:09:02AM -0700, Randy Dunlap wrote:
> >> static inline __pure u16 virtfn_bdf(struct pci_dev *dev, int id)
> >> {
> >> return (dev->bus->number << 8) + dev->devfn + dev->sriov->offset +
> >> dev->sriov->stride * id;
> >> }
> >>
> >> #define VIRT_BUS(dev, id) (virtfn_bdf(dev, id) >> 8)
> >> #define VIRT_DEVFN(dev, id) (virtfn_bdf(dev, id) & 0xff)
> >>
> >> We rely on GCC to do CSE and not actually invoke virtfn_bdf more than
> >> once.
> >
> > Yes, that's a good idea. Will replace that function with macros.
>
> That's the opposite of most changes lately. I.e., functions (with
> typechecking) are preferred.
There's every bit as much typechecking with the approach I outlined as
there was with the original.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
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